WordPress.org

Ready to get started?Download WordPress

Forums

[Plugin: WordPress MU Sitewide Tags Pages] Posting error (4 posts)

  1. David Jay
    Member
    Posted 2 years ago #

    I get the following error when I publish a post on a sub-blog

    Catchable fatal error: Object of class WP_Error could not be converted to string in /home/xxxx/public_html/mydomain.com/wp-includes/post.php on line 4356

    The post is published on the sub-blog but it does not show up on the tags blog (or the tags blog RSS feed).

    I am running BuddyPress on the site as well. The tags blog is using the Genesis News theme.

    I get the same error on all sub-blogs regardless of the theme. If deactivate Sitewide tags I do not get the error.

    I am running super cache as well as testing a bunch (its a development site) of wpmudev plugins (their global tags and post indexer are deactivated - they were active).

  2. Ron Rennick
    MultiSite Guru
    Posted 2 years ago #

    The best suggestion I can give you is turn everything off but SWT and test. Then turn on one plugin at a time and re-test to find which one is conflicting.

    I have yet to see a theme conflict with SWT, so I would only recommend looking for an issue there if all else fails.

  3. David Jay
    Member
    Posted 2 years ago #

    I fixed it. At least so far. Here is what I did.

    I deactivated plugins (all but a core ones) one-by-one but the issue still persisted. I then un-installed MU sitewide tags and re-installed it and I was able to publish blog posts just fine. I have since re-activated most of the plugins without a problem. So it seems best to activate Sitewide Tags before activated other plugins if you have the choice.

    I will update this if the problem occurs again after installing another plugin.

  4. Ron Rennick
    MultiSite Guru
    Posted 2 years ago #

    I will update this if the problem occurs again after installing another plugin.

    If you have a problem after installing another plugin, the person you should be contacting is the author of the other plugin. The fact that SWT was showing you you had an error doesn't mean that SWT was causing the error.

    There are over 17,000 plugins in the repo. It's not possible for one person to support them all. With that number, there are going to be conflicts between plugins.

Topic Closed

This topic has been closed to new replies.

About this Topic