5
No, that is all you need to do - exp_comments has no other dependencies when it comes to "closed" comments.
If you were deleting "open" comments, you'd want to recount the site's statistics afterwards (as exp_channel_titles has a comment_total column).
4
I am developer of zeal smart members. To solve your problem, Please Open file: system > ExpressionEngine > third_party > smart_members > libraries > sm_lib.php
Search for this function: function update_static_fields($member_id, $post_data)
Change the code from:
if(isset($custom_data))
{
$this->EE->member_model->update_member($...
3
You can adjust comment notifications in the particular Channel's preferences.
Administration > Channels > Edit Preferences (choose the appropriate Channel)
Then scroll down to "Notification Preferences"
EE Docs
3
Saw your post in meta - maybe a new answer which distills the entire thread you and Anna have created will be of help?
You do need two templates. The first will begin your document, and then list each channel entry, and then close the document. Within that template's channel:entries loop, you will embed your "comments" template, which will run once for ...
3
I see that you have your member group preferences set, how about the channel preferences - Moderate comments [yes | no] for the channel in question?
2
With a custom extension, you could. Just use the insert_comment_end hook, then do something like this:
if(ee()->input->is_ajax_request())
{
ee()->extensions->end_script = TRUE;
$data['comment_id'] = $comment_id;
$data['moderated'] = $comment_moderate;
echo json_encode($data);
}
2
This is not currently possible with any of the wysiswyg editors for EE. Have you considered making a feature request?
2
I usually do all of my AJAX form submissions with the jquery ajax form plugin. This allows you to customize the experience for your users here is the link to the plugin its very simple to implement.
http://malsup.com/jquery/form/
Hope this helps!
2
This is likely because the comment notification uses not the database entry for the comment, but the POSTed comment data. The insert_comment_insert_array hook only affects what gets inserted into the database.
2
If you're logged out, you shouldn't see anything, so make sure you're logged in. Second, this tag needs to be on a single entry page and it will try to figure out your entry ID by:
Checking to see if you used an entry_id= or url_title= parameter on the {exp:comment:notification_links} tag
Checking the URI to see if the entry ID shows up there
So, if your ...
2
It looks like this page is breaking because of the edit comment functionality combined with PHP/HTML in a comment.
See comment #322268: he's got PHP-style and HTML tags in his comment, which all seem to be escaped properly, but when that same comment content is replicated in the hidden block for comment editing (.edit-comment), your page source code is ...
1
One likely possibility to check first:
Make sure the Guests member group (which is essentially any non-logged-in users) have permission to post comments.
In EE2 you'd go to Admin > Member Groups > Guests
and look for Comment Posting Privileges
Not positive, but in EE3 I believe this member group setting is called Submit Comments
https://docs....
1
Both the comment:entries and comment:form tags accept an entry_id parameter, so there's no reason you can't have multiple forms on a page, so long as you pass the correct entry_id to each.
You might also run into variable collisions, since you'll need to use them inside of a channel:entries loop, so you may need to embed the comments/form and pass the ...
1
Do you only need login to post said comments?
Perhaps all you need is Disqus? Modules already available : CX Disqus Comments, Alternatives
Of course, by outsourcing your comments and social login to Discus (or another) you will lose the overhead of managing and developing an EE userbase, however if you wanted to sync your users so they can also log into ...
1
Here are some things that could cause this to fail:
Front-end caching such as Varnish or CloudFlare. Make sure that your cache layer is set to not cache URLs with a get parameter named ACT in them, for instance:
http://example.com/index.php?ACT=123
This is the URL format that is used to submit comments. The number will vary depending on the version of EE ...
1
If you are developing locally (e.g. using the “localhost” domain) you may get this security error on comments submission. To test commenting during local development, try to set "Require IP Address and User Agent for Posting" to "No" in Admin -> Security and Privacy -> Security and Sessions.
1
I was having the same problem. Mine is related to Structure and there is a known fix.
https://support.ellislab.com/bugs/detail/20559/comment-display-is-incorrect
1
Just closing the loop. I did file a bug report here and it was accepted.
1
It's the dynamic parameter.
If you set it to no, EECMS will not filter the comments to the entry on URL.
{exp:comment:entries channel="jobs" orderby="name" sort="asc" limit="2000"}
1
Why not to used :visited pseudo selectors and fragment identifiers on the links to comments?
On the list of entries:
{exp:channel:entries channel="news" limit="10"}
[...]
<a href="{title_permalink="channel/archives"}#{recent_comment_date format="%Y-%m-%d"}">link</a>
[...]
{/exp:channel:entries}
On the comments:
{exp:comment:...
1
The email field is used for guest comments only. For registered and logged in members who comment, that field will be NULL. So for a given entry_id, you need to gather email addresses from the exp_members table, as well as any values from the email column if your site allows guests to comment.
1
Yes. CP::set_variable was deprecated in EE 2.6.
I'm submitting a fix to the addon's github repository
1
Try this, and instead of hiding output2 after the dom has loaded add style="display:none;" to #output2 in the html.
$(document).ready(function() {
var options = {
target: '#output2', // target element(s) to be updated with server response
beforeSubmit: showRequest, // pre-submit callback
success: showResponse ...
1
I believe that's generally located in the General Channel Settings, and would need to be set per channel, which makes sense, since comments can be turned on and off per channel. See image:
1
It'd be a tall order to synchronize activity on any third party social network and your EE site; if you absolutely need a unified experience, pick one and forget about the EE comments module.
How is it a tall order? Imagine Facebook Frank leaving a comment on your Facebook site, which Local Site Larry (who doesn't have a Facebook account) responds to via ...
1
If the members who is testing the comments are in the group super-admins or another one which has been set to exclude its members from the comment moderation, the status of their comments will always be open.
1
No, but since the free version is just an embed script with js and html, all you need to do is add it to your template where you want it to appear on the page.
Here's an example embed code:
<!-- START: Livefyre Embed -->
<div id="livefyre-comments"></div>
<script type="text/javascript" src="http://zor.livefyre.com/wjs/v3.0/javascripts/...
1
You also need these...
Control Panel Access Preferences
Can access ADD-ONS section: Yes
Can access ADD-ONS: Modules: Yes
1
What if you just drop the type parameter?
<script src="http://mysite.com/?ACT=jquery"></script>
<script src="http://mysite.com/?ACT=comment_editor"></script>
1
Try adding dynamic="no" to your exp:comment:entries tag. I would also add the channel="" parameter to the tag:
{exp:comment:entries sort="desc" entry_id="{embed:entry_id}" dynamic="no" channel="XXXX"}
Also, confirm that {embed:entry_id} is printing out the correct ID in your embed.
If that doesn't work, make sure your exp:comment:entries is NOT inside a ...
Only top voted, non community-wiki answers of a minimum length are eligible
