Okay well I wanted to test it out quickly so I plugged it into a template real fast. After pressing submit, I get this error:
The requested URL /blog/comment_container// was not found on this server.
But when I refresh my page, the comment is there, submitted and whatnot. So I dont know what happened…. :\
Trying this out again somewhere new…. and getting a new problem. So many things about this are pretty unclear. Here are the things I believe need to be far more specific:
In the settings for the extension, it asks for the “URL to your Comment Container template.” Is this asking for the template used to display your blog post, comments, and comment form? Or is it asking for the AJAX template that we’re adding for this to work.
In the ajax template, first line, you have this:
{exp:ajax_comments container="comments_container" template="blog/comments_container"}
This is very confusing. The first thing is asks for is the name of the DIV you used to embed the ajax comment form. However, what template is it asking for. Because you call the ajax template “comments_container” in your example, I almost wonder if that top line is asking for itself. It asks for a template and by default, you give it the NAME OF THE TEMPLATE THAT LINE IS CURRENTLY IN. Is this:
template=”blog/comments_container”
also asking for the template used to display blog posts, comments, and the comment form?
Currently, what happens is I press submit, my whole entire comments section gets erased… and it looks like it starts to come back but then i get taken to a page with plain text that seems to consist of the user names and email addresses for people that submitted comments.
Please try and clarify EXACTLY WHAT things this plugin is looking for and where. It may help if you dont repeat the same words for so many different things (like “comments_container”)
Okay, I’ve updated the instructions. Sorry they are confusing 😕. There are two templates: 1) Main template - Which I’ve called it “comments” under the template group “blog” 2) AJAX Template - Which I’ve called it “ajax_comments_template” under the template group “blog”
Inside the Main Template there should be a div container and I’ve named that “comments_container” and inside that div container should be an embed to the AJAX Template.
Inside the AJAX Template should be the plugin code and the parameter “container” is asking for the name of the div you setup in the Main Template. In this case it’s called “comments_container”. The “template” parameter is asking for the name of the AJAX Template and in this case it’s called “ajax_comments_template”.
Then the extension setting is asking for the full URL to the AJAX Template which in this case should be something like: http://example.com/blog/ajax_comments_template/” or http://www.example.com/index.php/blog/ajax_comments_template/”.
That’s as best as I can explain things 😕.
Let me know if you’ll need more help, I’m a very patient guy and will get this to work for you 😊.
My site is pretty much down for maintenance. I’ve disabled most of the features that would get people to my blog stuff. This makes for a nice testing environment while I work on my new ajax powered site.
That being said, I’m happy to say that I got it to work. However, there is a glitch in the code somewhere. For example, post a comment here:
http://www.whoisjimothy.com/blog/article/get_cape_wear_cape_fly/
It works quite well. I know because I removed the URL from the address bar, posted a comment, and saw the comment appear. The address bar wasnt refilled so I know there was no page refresh. However, post a comment on this entry:
http://www.whoisjimothy.com/blog/article/two_new_kittens_at_my_house/
After posting the comment, it gets successfully inserted but instead of returning to the page, you get a weird blank page with some odd code showing up. I think that the plugin fails to encode the URI correctly when submitting the comment, or when returning to the page. I’m willing to bet that if i deleted a few comments from that entry, it would work. Let me know if this helps, because I’m sure that this could popup randomly for some poeple and have no idea why
Thanks for the plugin though 😊 I’m excited because this was the biggest hurdle with my new site. The only other possible hurdle I can think of is…. get ready for this…
Searching. We need an ajax search plugin now 😊 It’s not necessary. A good archives page can eliminate the need for it, but it would be nice, dont ya think?
I dont know… but its causing some very odd behavior. Even before a comment is posted. For example, highlight some people’s name and you’ll see their email address. That is NOT good, because their email address is absolutely not supposed to be displayed. I know those people didn’t enter their email address as their website URL. In fact, I know most of them didn’t post a website URL at all. Could be that either an email address is messing it up, or a URL.
I realize this is a bit old, but I’m hoping the developer is still checking this thread.
I set this up and am not getting any errors, however comments are being posted normally (with a page refresh).
One thing I had a question about was the sample comment template in the documentation doesn’t have a closing {/exp:ajax_comments} tag anywhere… should it?
Also, I’m using .htaccess to strip out index.php and my template folder, so I’m hoping that doesn’t have anything to do with my problem. The URL I have in the Extension Settings page is:
http://example.com/template/
The “true” path is http://example.com/index.php/folder/template/ but when I used this URL, the page refreshed at http://example.com/index.php/folder/template/url_title instead of just http://example.com/template/url_title like I want it to, so I thought that might be the reason why it’s refreshing.
Lastly, I’m using EE v1.6.8, and am curious as to whether the jQuery include is necessary since I know EE now ships with it installed.
How does the plugin handle embedded comments in which variables are passed in the comments tag via: weblog=’{segment_1}’ url_title=’{embed:url_title}’. On a site I’m working on those are used, so there is no separate comment page. After reviewing the plugin code, I went in the template and wrote the needed script.
$('#comment_form').ajaxify({
target:'#comments-embed',
forms:'#comment_form',
link: 'core/comments_single/{segment_3}/',
event: 'submit',
method: 'POST'
});
The div’s id ‘comments-embed’ for the container holding the embedded comments_single template, the forms id is dictated by EE, the return link is build using a segment variable. For testing I first used the plugin/extention. But in both cases it is resulting in a page refresh… not an update of the comments on the page vieuwed. Making a bare bones example using the plugin codeexample It redicrects to the embed template
Does anyone have an idea ?
Hi,
I released another AJAX comments solution - a plugin called AJAX Babble. It supports pagination, scrolling newly submitted comment into view and triggering search for certain comment through URL.
I realize this is a bit old, but I’m hoping the developer is still checking this thread.
I set this up and am not getting any errors, however comments are being posted normally (with a page refresh).
One thing I had a question about was the sample comment template in the documentation doesn’t have a closing {/exp:ajax_comments} tag anywhere… should it تفعيل Windows 8.1?
Also, I’m using .htaccess to strip out index.php and my template folder, so I’m hoping that doesn’t have anything to do with my problem. The URL I have in the Extension Settings page is:تفعيل Windows 8.1
This is my best Activation windows 8.1: تفعيل Windows 8.1
The “true” path is http://example .com/index.php/folder/template/ but when I used this URL, the page refreshed at http://example .com/index.php/folder/template/url_title instead of just http://example .com/template/url_title like I want it to, so I thought that might be the reason why it’s refreshing تفعيل Windows 8.1.
Lastly, I’m using Windows 8.1, and am curious as to whether the jQuery include is necessary since I know EE now ships with it installed.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.