Issue after upgrade
-
Hello
After upgrading your plugin today i have now this message
Cannot modify header information – headers already sent by (output started at /home/xxxxx/public_html/wp-content/plugins/widgets-on-pages/public/class-widgets-on-pages-public.php:98) in /home/xxx/public_html/wp-content/themes/rudyboy/404.php on line 2
Cannot modify header information – headers already sent by (output started at /home/xxxxx/public_html/wp-content/plugins/widgets-on-pages/public/class-widgets-on-pages-public.php:98) in /home/xxx/public_html/wp-content/themes/rudyboy/404.php on line 3
Thank you for your support
-
I had a similar issue. The widgets vanished from my homepage. It also gave me problems with saving pages and posts βΒ I was getting the white screen of death.
Luckily I was able to find an older version of the plugin and could roll back. Unfortunately it lost my column settings and I had to restore them manually. Grrr.
-
This reply was modified 9 years, 2 months ago by
gorky5.
Hey, Oh dear, I had not seen this in any testing… and I did thoroughly test as it was a major upgrade.
Do you have a link to the site @neoseeyou?
@gorky5 Sorry to hear this, also. You can roll back to v0.0.12 and you should not lose any widgets. Are you saying this did not work?
Are you able to confirm that you are on v1.0.1 (or this was with v1.0.1)? I initially pushed v1.0.0 out and this did have a problem where no widgets showed, due to a strange upgrade process that I could not test until I pushed to the wp.org. This was fixed within 2 minutes.
Sorry again for any problems, and I’m very keen to help you get this sorted.
and yes i confirm that i have the latest version 1.0.1
I tried 1.0.0 version and same error messages appeared too
-
This reply was modified 9 years, 2 months ago by
alpha2.
Ok i will try to contact you on twitter
Just to add some information, each time i try to save a post or page i have these warnings
Warning: Cannot modify header information – headers already sent by (output started at /home/xxx/public_html/wp-content/plugins/widgets-on-pages/public/class-widgets-on-pages-public.php:98) in /home/xxx/public_html/wp-admin/post.php on line 197
Warning: Cannot modify header information – headers already sent by (output started at /home/xxx/public_html/wp-content/plugins/widgets-on-pages/public/class-widgets-on-pages-public.php:98) in /home/xxx/public_html/wp-includes/pluggable.php on line 1179
Side note to both toddhalfpenny and @neoseeyou and it’s a serious one: No one here should offer anyone to access their site via logging in.
https://make.ww.wp.xz.cn/support/handbook/forum-welcome/#the-bad-stuff
That’s going too far and anyone taking advantage of that offer risks getting into real trouble on this site.
I get that the user wants to sort this out but do not make that offer in the forums and do not accept it if someone asks.
Meant to ping @toddhalfpenny with that last one. π
Understood @jdembowski, thanks for the heads-up.
@neoseeyou – are you able to give some info as to the WP version and theme (and it’s version) please?Hi Todd. Thanks for your help with this.
I had upgraded to 1.0.1, and rolled back to 0.0.12.
I didn’t lose any actual widgets, but the settings for the optional sidebars were no longer saved after the upgrade/downgrade, and I had to manually re-enter their names.
Using the WP-Rollback plugin, I did briefly test 1.0.0 to see if that worked, but encountered the same problems. When I went back to 0.0.12 I once again had to rebuild my columns. I’m not sure if there’s still an option for extra sidebars in the newer version (I think it was missing from the settings page but I’m reluctant to check again).
Just to let you know, I didn’t get the same error as @neoseeyou when saving posts/pages. I just got a white screen, and it didn’t save my edits. I tried disabling all other plugins but that didn’t make a difference. All is fine under the older version, so I’ll stick with that for now.
Thanks for the extra info @gorky5.
If you could provide me with details on your theme and version I will try to reproduce.
The extra sidebara in v1.0.1 are now stored using custom post types (the ironic reasoning is that I have more control in persisting these), and these are now under a new “Widgets in Pages” top level menu item.For info I have rolled the stable tag back to 0.0.12 until I have worked out why my tests didn’t throw up either of these issues.
*It’s like hockey referee day…*
@gorky5 Per the Forum Welcome please start your own topic.
https://ww.wp.xz.cn/support/plugin/widgets-on-pages/#new-post
Intruding on someone elses topic is considered rude here and as you said, you’re not getting the same error.
ok @jdembowski understood
Thanks
@toddhalfpenny : i have last wp version and my theme is a child theme from twenty thirteen
-
This reply was modified 9 years, 2 months ago by
alpha2.
Here’s some info on how the original poster can get that info here.
- Provide a link using http://pasetbin.com/ log of the web server error log. I suggest a registered account there so you can delete it later if you choose.
- Create and post a link to your
phpinfo();output. That can often give the author some good details. - Install the Send System Info plugin and get the data to the author that way.
- Enable WP_DEBUG and log that output to a file and share that file.
Those are some steps that can get the author the info needed to sort this out.
Apologies to @neoseeyou. Didn’t mean to crash your party.
@toddhalfpenny, I’ll duck out of this thread now. For info, I’m on the latest WP, 4.7.3βen_GB, and I’m using a TruePixel child theme. I’ll wait for a new version of the plugin, and if I encounter any issues I’ll start a new topic.
@gorky5 for my personnal point of view, you’re welcome to this thread ahah
@neoseeyou – I think I have spotted the issue, it appears to be only affecting on a theme-by-theme basis.
If I post up a link to some updated file would you be happy to replace those in the existing plugins directory? You would need FTP access for this.
Of course, if you’re not comfortable with this I understand. -
This reply was modified 9 years, 2 months ago by
The topic ‘Issue after upgrade’ is closed to new replies.