- This topic has 7 replies, 3 voices, and was last updated 7 years, 2 months ago by
.
-
Posts
-
hello
after install the theme for first time, i got those lines on the header in adimn panelWarning: Cannot modify header information – headers already sent by (output started at /home2/****0/public_html/******.com/wp-content/themes/magazine-plus/inc/hook/custom.php:2) in /home2/******/public_html/******.com/wp-includes/option.php on line 828
Warning: Cannot modify header information – headers already sent by (output started at /home2/******/public_html/******.com/wp-content/themes/magazine-plus/inc/hook/custom.php:2) in /home2/******/public_html/******.com/wp-includes/option.php on line 829
thanks
Hello @ibra,
While we have tested the theme with the latest theme version, no such issue is seen on our side.
Please verify that the theme has been properly downloaded and installed in your website.
Also, try deactivating any third-party plugins if you have any installed and activated in the site.
Write back to us if the steps above does not resolve the issues and we will assist you further.
Hope this Helps,
Best Regards !!
This is definitely a theme-level problem, as I’m also encountering the same problem on the primary controller. In addition, this is also rendering the wp-admin controller inaccessible (paths abbreviated in stack trace):
Warning: session_start(): Cannot send session cookie – headers already sent by (output started at ~/airport_raceway/wp-content/themes/magazine-plus/inc/hook/custom.php:2) in ~/airport_raceway/wp-content/plugins/awesome-studio/monoframe/social-login.php on line 265
Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at ~/airport_raceway/wp-content/themes/magazine-plus/inc/hook/custom.php:2) in ~/airport_raceway/wp-content/plugins/awesome-studio/monoframe/social-login.php on line 265
Warning: Cannot modify header information – headers already sent by (output started at ~/airport_raceway/wp-content/themes/magazine-plus/inc/hook/custom.php:2) in ~/airport_raceway/wp-includes/pluggable.php on line 1179
The two 3rd-party plugins referenced in the call stack are used on other installations of WP on the same server, and those instances are functioning quite well.
Clearly you’ve got an incompatibility with the changes made to WordPress 4.7.2 and you need to upgrade your code (proper unit testing would help prevent this from happening). I’m in the process of tracking down why your theme is sending headers before it should be, but users shouldn’t have to fix something you’re supposed to support.
Hello @factorone33,
We apologize for the incontinence, however while we have tested the theme with the latest WordPress version ( Version 4.7.2 ) with the PHP Version 5.4.13 in the server, we were unable to find the issue on our side.
For further debug, please try switching to default themes and check if the issue still occurs in your site.
If the issue is not resolved, please provide us the details on WordPress version & PHP version in the server you are using the theme, that would help us to test further and debug the issue further.
Also, please be assured that we do put our highest level of efforts for optimizations and error debug ( if any ) in the theme core files. so, any noted issues in the theme will be resolved with the theme update.
Best Regards !!
Hello @@factorone33,
Quick Update for the issue :
We would also like to inform you that we have also tested the latest theme version with WordPress latest version ( Version 4.7.2 ) and PHP Version 7.0.13 without any issues.
Best Regards !!
First off, my apologies for the terse commentary yesterday. That was a bit over-the-top (to say the least).
Secondly, some more background info on my scenario. The environment uses PHP 7.0 on shared hosted space (Bluehost). I currently can’t revert to the default theme as I can’t access the admin due to header conflicts for the wp-admin controller.
I’m currently trying to recreate the issue in a local environment to try and step through the call stack.
Hello @factorone33,
Thank you very much for sharing the details with us. We will surely be testing the theme latest version in the similar server setup environment.
If any issues found in the theme, the issues will be resolved with future updates.
Thank you for the co-operation,
Best Regards !!
Hello @factorone33,
Although we are not getting any such errors, we have tested the theme if the setup environment as discussed above and updated the sections in the code that we suspect might have caused the issue in your website.
Please update the theme to the latest available version ( version. 1.0.6 ) and check to see if it resolves your issues.
If you have any further queries / issues, please feel free to post them here.
Thank you for the patience,
Best Regards !!
- You must be logged in to reply to this topic.
