- May 10, 2014 at 12:12 pm #198937kegnumParticipant
I have had a problem on 1 of my three sites since the last update. They all have the same plugin and theme… so I’m not sure why it only is happening to the one site. Anyway, whenever I publish a post it publishes and goes to a blank white screen and says this…
Warning: Cannot modify header information – headers already sent by (output started at /home1/name/public_html/mywebsite.com/wp-content/plugins/nxs-snap-pro-upgrade/nxs-snap-pro-upgrade.php:15) in /home1/name/public_html/mywebsite.com/wp-admin/post.php on line 235
Warning: Cannot modify header information – headers already sent by (output started at /home1/name/public_html/mywebsite.com/wp-content/plugins/nxs-snap-pro-upgrade/nxs-snap-pro-upgrade.php:15) in /home1/name/public_html/mywebsite.com/wp-includes/pluggable.php on line 1121
When I refresh the page, it brings me back to the list of my recent posts and everything is ok.May 11, 2014 at 10:08 am #199610RuralinfoParticipant
I am having the exact problem since the update.. Everything is posting, but after every post publish I get the same error as kegnum above..May 13, 2014 at 10:14 am #201018StefanParticipant
Here the same errorMay 14, 2014 at 11:41 am #201643VargParticipant
Same Problem here 🙁May 14, 2014 at 7:59 pm #201878Jimmy DearingParticipant
I guess they don’t look at their forums for any issues.. They also aren’t answering their own trouble tickets as I submitted one on Sunday and haven’t heard a word back from them!May 16, 2014 at 1:58 pm #202969kegnumParticipant
They will fix it. I have had several issues over the years. It really can’t helped when you are dealing with so many different social sites. They have fixed every one. There was even one occasion when the programer logged into my WP site personally to fix an issue.
Have faith this company has on of the best customer service teams I have seen with WP plugins. They may not answer right away on their forum but it’s better that they fix this issues than give you lip service.
BTW there was just an update where this issue was fixed for me 😉May 16, 2014 at 2:44 pm #202998NextScripts.comParticipant
This issue has been fixed in the verison 3.3.7
- You must be logged in to reply to this topic.