Forums

[resolved] [Plugin: All in One SEO Pack] how to debug problems with this plugin? (7 posts)

  1. Ovidiu
    Member
    Posted 8 months ago #

    hi there.
    I know, wpmu is not supported but maybe you can still help me out.
    unfortunately I might have an imcompativle plugin, as this plugin ,breaks the wp-signup.php page within wpmu. it only loads a blank page if this plugin is active, the sourcecode ends with:

    <!-- all in one seo pack 1.4.7 ob_start_detected [-1,-1] -->

    I have checked the code of your plugin a little, and if I understand this right, it stops because it detects possbile problems with other plugins.
    how could I debug this problem? I'd like to find out which plugin it conflicts with...

    if possible without deactivating all plugins one by one :-(

    http://wordpress.org/extend/plugins/all-in-one-seo-pack/

  2. hallsofmontezuma
    Member
    Posted 8 months ago #

    "how to debug" - deactivate all plugins and reactivate them one by one

  3. Ovidiu
    Member
    Posted 8 months ago #

    unfortunately, this doesn't work with wpmu. too many active plugins :-( and there is also a mu-plugins folder, where plugins are automatically activated.

    besides, a lot of plugins affect all blogs served by this instance, so I would break a lot of blogs, or have to put all blogs into maintenance mode.

    I was just looking for an easy way out, maybe by adding some code that prints out what conflict was detected?
    I mean this plugin detects a possible conflict? then halts its own execution and prints out <!-- all in one seo pack 1.4.7 ob_start_detected [-1,-1] --> instead?

    like I said, I know its not this plugins fault, I jsut need some help :-)

  4. hallsofmontezuma
    Member
    Posted 8 months ago #

    Do you have logging turned on?

  5. Ovidiu
    Member
    Posted 8 months ago #

    yepp.

    2009-03-09 14:55:03 another plugin interfering?
    2009-03-09 14:55:03 detected output handler default output handler

    ok, can you help me understand that? I mean it must be something within another plugin that is detected, so what could I grep for?

    i.e. grep -R -i 'somethingtogrepfor' web/

  6. hallsofmontezuma
    Member
    Posted 8 months ago #

    try: find . | xargs grep "ob_start"

  7. Ovidiu
    Member
    Posted 8 months ago #

    k, managed to try now. the above find was way too long...

    - renamed the plugins folder, no change, the wp-signup.php page still doesn't work.
    - moved all plugins out of the mu-plugins folder except for the maintenance plugin which I used to set the site into maintenance mode and the AIO plugin, signup page still broken.
    - changed the main blog theme, still broken :-(

    what further debugging can I do?

Reply

You must log in to post.

About this Topic