Tag Info

New answers tagged

1

The function is_wp_error checks if the given var is an instance of WP_Error class (soruce code as WP 4.2.2): function is_wp_error( $thing ) { return ( $thing instanceof WP_Error ); } As you can see, if the given variable is a instance of WP_Error class, the function returns true, even if the object is empty. Your $error variable is a WP_Error ...


1

Comment type is similar to post type, because it allow to query only a specific type of comments, just like post type allow to query one or more post types. And just like core post types (page, post) there are core comment type as well: 'comment', 'pingback', 'trackback'. A difference between the two is that, by default, WP_Query do not fetch post types ...


0

Remove the website URL field Remove any comment form allowed tags Configure discussion settings so all comments must be approved by admin Disable anyone can register setting Add a captcha to your comment form as a last resort I think they are looking for forms which include the words email, website and comments so if you remove all those words you should ...


1

One surprisingly useful solution to foil most spam-bots is to use a honeypot. Put an extra entry field into your comment forms, and then hide it with css. Normal users won't fill it in because they won't ever even see it. Based on that, you can safely assume that anytime an entry is made with that field filled, that it's a bot and you can just discard/mark ...


-1

The Simple Security Firewall has 100% catch rate on automated spambots without analysing the contents of the spam or any IP addresses etc. It doesn't need to. Plugin: https://wordpress.org/plugins/wp-simple-firewall/ Enable the Comments Filter feature, and then turn on the spambot anti-spam. Within that section, you can set it to outright reject the spam ...


0

Ok, I found the problem. It was WordPress Move Comments plug-in's issue and the problem solved by disabling this plugin. I'll say this problem to the developers today.


0

Find all the functions "get_avatar" used in your theme folder. Identify the wrong calls echo get_avatar($comment,$size='48',$default='<path_to_url>' ); or echo get_avatar($comment,48,'<path_to_url>' ); If you find these,then change it to echo get_avatar( $comment, 48 ); . Hope this gonna help you :)


1

It's strange that you want to use comments pagination where the comment links are without the comments pagination base. But you can try this (untested): /** * Remove the comments pagination base from comments links */ ! is_admin() && add_filter( 'get_comment_link', function( $link, $comment, $args ) { if( $args['per_page'] ) $link = ...


0

You need to 301 redirect the old URLs. This can be done by using Custom Permalinks plugin which automatically updates the 301 version of the URL and thus helping the Facebook plugin to recognise and restore the likes and comments.


0

There's also this plugin that handles the issue beautifully.


0

The comment form is generated from another domain via the iframe. While I was accessing the iframe using jQuery content() it returned me Permission denied to access. It means the Jetpack is Cross Site Scripting protected and you cannot edit the placeholder.


3

There is no "safe" way to edit core files; if you do you will need to check and repeat the edition after every update. Not recommended at all. Instead of editing core files, you could use any of the actions and filters available. For example, pre_comment_on_post (example code not tested): add_action( 'pre_comment_on_post', function( $post_id ) { if( ...


0

Your action is called whenever comments.php loads because you're explicitly running it with do_action. Both the function and add_action should be in functions.php, and do_action should be removed entirely.


0

Thanks for raising this issue, it interests me as well. After searching everywhere for an acceptable solution, this is how I approach the problem on my site, at least for now: comment_reply_link(array_merge( $args, array('depth' => $depth, 'max_depth' => '25' ))) If you change '25' to, say, '1000', this will give you pretty much 'infinite replies', ...


1

Use the proper charset in you website according with the characters you use, that is the correct solution from my point of view. What your are trying is some work around that don't fix the real issue. You must note that UTF-8 is the standard enconding recommend for internet nowdays. ISO-8859-1 was considered the standard for 4.01, although most of the ...



Top 50 recent answers are included