Another interesting test we just ran.
We published a post today but purposely did not use Blog Post Linking as a test. A comment was submitted by an admin and it shows normally.
Canvas theme has not yet been updated.
link to post (log in first):
https://members.wayned.com/online-students-john-lamendola-part-7
but all posts previous to this one still have the exact same comments as discussed earlier? that would be even more confusing…
think I asked this before, but no caching?
unfortunately, I am on business trip until Thursday night with limited ability to do deep dives… hopefully Andy can look in AM… can you post the contents of the single.php file here? probably need to zip it up…
but all posts previous to this one still have the exact same comments as discussed earlier? that would be even more confusing…
Yes, but we try to link every single post to the forum. This makes it easier for the main instructor to reply to his students. Those post were probably linked on posting but didn’t connect for some reason.
think I asked this before, but no caching?
yes, correct, no caching plugins we learned that lesson a few years back.
can you post the contents of the single.php file here?
yes, will post, it’s short so may not need to zip. Actually may need the theme-comments.php. Can post whatever you’d like as well as grant admin access, just let me know. hope your business trip is going well.
single.php:
<?php
/**
* Single Post Template
*
* This template is the default page template. It is used to display content when someone is viewing a
* singular view of a post (‘post’ post_type).
* @link http://codex.wordpress.org/Post_Types#Post
*
* @package WooFramework
* @subpackage Template
*/
// Nathan: If user doesn’t have access, redirect to join page
for ($i = 0; $i < count($posts); $i += 1) {
$p = $posts[$i];
if (!memb_hasPostAccess($p->ID)) {
header(‘Location: /join/’);
exit;
}
}
get_header();
?>
<!– #content Starts –>
<?php woo_content_before(); ?>
<div id=”content” class=”col-full”>
<div id=”main-sidebar-container”>
<!– #main Starts –>
<?php woo_main_before(); ?>
<section id=”main”>
<?php
woo_loop_before();
if (have_posts()) { $count = 0;
while (have_posts()) { the_post(); $count++;
woo_get_template_part( ‘content’, get_post_type() ); // Get the post content template file, contextually.
}
}
woo_loop_after();
?>
</section><!– /#main –>
<?php woo_main_after(); ?>
<?php get_sidebar(); ?>
</div><!– /#main-sidebar-container –>
<?php get_sidebar(‘alt’); ?>
</div><!– /#content –>
<?php woo_content_after(); ?>
<?php get_footer(); ?>
While I wait for @mr-papa to return and go down the template path he was looking at I have a couple of questions…
Firstly – and I don’t believe this has been stated – has it been like this since day one of using the plugin? Or did it just begin happening at some point…?
Blog Linking works by adding post-processing logic to the creation of a blog post. This is done using WordPress standard filter and action hooks which allow plugins to add in their own code at strategic points. So we use it for blog linking. Other plugins could, for example, use it to add pre-created content, add formatting data, include images etc., all kinds of things. The big question is – does your site have any other plugins active that also operate on blog post creation that might be interfering in some unknown way? So is anything being triggered at blog post publish time that night have a knock-on effect?
This is a unique report of what is a pretty well used plugin and experience shows that this often leads to a hidden conflict with another plugin.
Firstly – and I don’t believe this has been stated – has it been like this since day one of using the plugin? Or did it just begin happening at some point…?
We’ve been using Blog Post Linking for years, even before it became a plugin. It has worked as expected for quite some time and we’ve only noticed the issue somewhat recently, it just began happening at some point.
The big question is – does your site have any other plugins active that also operate on blog post creation that might be interfering in some unknown way? So is anything being triggered at blog post publish time that night have a knock-on effect?
Great question. I will research this and get back to you. I don’t think any of ours have a role in post creation. What type of plugin would fall into this category? Membership plugin? Quiz plugin?
this often leads to a hidden conflict with another plugin.
We haven’t added any new plugins in quite some time. I would say not since after noticing the problem but I’ll try to confirm this. Possibly an update to an existing plugin or even a WP update conflict with an existing plugin is the cause? Will continue searching for clues. appreciate all the help.
If it were something like this then it can be hard to track down. Often it comes down to deactivating plugins – trying the task – reactivate one at a time etc. Which can be difficult for some websites of course,
As I said above – anything that touches publishing – no matter how small. So membership plugin – probably not. Formatting or advertising plugin – possibly. If you are using something that notifies social networks of a new post – that would be a good example. Or a more obscure SEO plugin as well (and I say obscure because we know we are good with the more popular ones).
And at the end of the day this may not be the problem – bit it is where I personally would start looking. Especially anything that might have been added or changed coinciding with the problem happening,
Sorry it’s been a while, did not mean to be gone so long but had a wisdom tooth extracted a few days before the holiday and then just took it easy and recovered. I’m back at it again today. Hope all of you had a wonderful holiday.
edit from earlier. I believe I found the problem plugin.
Looks to be BadgeOS.
testing more to confirm.