WordPress.org

1. nicollb
   Member
   Posted 10 months ago #

   I'm not sure if this is the correct place to ask this, or if I should send it to woothemes forums. I'm using Headlines on several sites in a multisite network (woothemes); I installed sitewide tags and now when the admins/editors/authors on the individual sites try to update a post, they get errors much like this:

   Warning: Invalid argument supplied for foreach() in /home/famvin/public_html/famvin-org/wp-content/themes/headlines/functions/admin-custom.php on line 359

   Warning: Cannot modify header information - headers already sent by (output started at /home/famvin/public_html/famvin-org/wp-content/themes/headlines/functions/admin-custom.php:359) in/home/famvin/public_html/famvin-org/wp-includes/pluggable.php on line 934

   the updates are completed -- but the message is problematic and interrupts workflow and upsets them.

   There is some sort of conflict, I think between some code in the theme (or the Woo Framework) and the plugin, I think. Ideas on how to get at the cause of the problem?

   I will check at WooThemes to see if there are answers there (I've checked in the past, but maybe something has popped up recently);

2. Andrea_r
   team pirate
   Posted 10 months ago #

   Well the error message is related to the theme.

3. nicollb
   Member
   Posted 10 months ago #

   Yeah - I thought so. And, it's not the theme of the "tags" blog that the plugin creates (that's set at 2011 right now).

   It related to the function from the plugin that posts to the tags blog though because it only occurs when I have the plug activated and functioning.

4. Andrea_r
   team pirate
   Posted 10 months ago #

   and you're network activating the sitewide tags plugin?

5. nicollb
   Member
   Posted 10 months ago #

   Yes. AFAIK that is the only way to use it.

   It is something between the plugin and the theme I think. And only when the post is updated, not on the original post.

6. Ron Rennick
   MultiSite Guru
   Posted 10 months ago #

   Check and see if you accidentally added a blank line to the top or bottom of the SWT plugin.

7. nicollb
   Member
   Posted 10 months ago #

   I looked at the plugin code (which was installed using the automatic install)

   There was a blank line after the final ?> (or at least a carriage return/line feed)

   I removed that final line/return.

   Retried.

   Results were slightly different, but essentially the same: Line 367 instead of 359)

   Warning: Invalid argument supplied for foreach() in /home/famvin/public_html/famvin-org/wp-content/themes/headlines/functions/admin-custom.php on line 367

   Warning: Cannot modify header information - headers already sent by (output started at /home/famvin/public_html/famvin-org/wp-content/themes/headlines/functions/admin-custom.php:367) in /home/famvin/public_html/famvin-org/wp-includes/pluggable.php on line 934

8. Ron Rennick
   MultiSite Guru
   Posted 10 months ago #

   Try switching themes and see if you have the error. If not, then it's something in the theme that isn't happy with SWT.

9. nicollb
   Member
   Posted 10 months ago #

   I have checked using another site in the network, and it is the theme... or rather, I suspect it is the Woo Framework which is at the core of the theme for most of the sites on the network.

   I'll push it from that angle.

10. nicollb
    Member
    Posted 9 months ago #

    OK -- after further testing and deliberations, this appears to be theme related, but the theme that is causing it is not Headlines, Coffeebreak, or other non-woothemes themes I have tried. The error only occurs when the tags blog is using Twenty-Eleven and the subdomains use a wootheme. Interesting. I changed the tags blog theme to 2010 and now all works well.

    Not sure how or where to report this.

11. Ron Rennick
    MultiSite Guru
    Posted 9 months ago #

    You may want to look over what hooks are used in TwentyEleven and the wootheme(s) and see if there's a conflict. If you do track down what it is, you may want to approach the guys at woo about it.

12. nicollb
    Member
    Posted 9 months ago #

    I'll take a swing at it -- obviously TwentyEleven uses more or different hooks than TwentyTen did (TwentyTen works fine).

    I'll post back if I find it.

Reply

You must log in to post.