Tagged: x
-
AuthorPosts
-
November 7, 2016 at 7:51 am #1247058
fabiofavaParticipantHi Folks!
Since a while (can’t specify exactly when) I’m having the error below, couple times a day, on my WP Site. Since it’s related with the X-Theme and here is the place I always find solutions, I hope someone could help around it:
PHP Warning: Cannot modify header information – headers already sent by (output started at /home/pproadm/public_html/fabiofava.com/wp-content/themes/x/page.php:17) in /home/pproadm/public_html/fabiofava.com/wp-includes/pluggable.php on line 1174
I’ve been digging around at the Forum & KB but didn’t find any mention.
Below is /x/page.php:17
<?php x_get_view( x_get_stack(), ‘wp’, ‘page’ ); ?>
Below is /wp-includes/pluggable.php :1174
header(“Location: $location”, true, $status);
Please let me know if is there something else I can do.
Thank you and best regards.
November 7, 2016 at 8:39 am #1247129
ThaiModeratorHi There,
In this case, would you mind providing us with login credentials so we can take a closer look? To do this, you can make a post with the following info:
– Link login to your site
– WordPress Admin username / Password
– FTP AccountDon’t forget to select Set as a private reply. This ensures your information is only visible to our staff.
Thanks.
November 7, 2016 at 9:09 am #1247161
fabiofavaParticipantThis reply has been marked as private.November 7, 2016 at 10:18 am #1247289
RupokMemberHi there,
You can just create a account or just give your one.
Thanks!
November 7, 2016 at 11:28 am #1247400
fabiofavaParticipantThis reply has been marked as private.November 7, 2016 at 12:52 pm #1247511
RupokMemberHi there,
I have checked your site but couldn’t see such warning anywhere. Are you still facing this or just happened randomly? Note that such warning caused by plugin when same thing called twice. Like if you are using two different plugins for same purpose or something like that. This warning should be gone if you disable WP_DEBUG mode.
You can do this by opening
wp-config.phpand updating :define( 'WP_DEBUG' , true );to
define('WP_DEBUG', false);Hope this helps.
November 7, 2016 at 1:12 pm #1247528
fabiofavaParticipantThanks Rupok but it was already set to “false” before.
Any other help?
November 7, 2016 at 3:47 pm #1247720
DarshanaModeratorHi there,
You’re running PHP V5.4.x on your server. Please contact your hosting provider and ask them to update your PHP version to at least PHP v5.6.0 or above to avoid any incompatibility issues as WordPress recommends it.
Let us know how it goes.
Thanks!November 7, 2016 at 4:46 pm #1247763
fabiofavaParticipantThanks Darshana! But my host insists in keeping PHP 5.4, they say there’s a very horrible vulnerability in PHP 5.6 so they cannot upgrade (I know they should, but they just don’t).
Anyway I don’t think this is the cause for the error I’m having. We should focus on discovering and cleaning this error. I’m pretty sure PHP 5.4 have nothing with this.
I still hope you guys can help me to track and solve that.
November 7, 2016 at 10:17 pm #1248120
RupokMemberHi there,
Please point us where you are getting the error. Meantime, if your WP_DEBUG is already set to false then maybe your PHP error_reporting is enabled. You can place
error_reporting(0);instead ofdefine(‘WP_DEBUG’, false);on your config file.Cheers!
November 8, 2016 at 2:18 am #1248336
fabiofavaParticipantThanks Rupok, but this doesn’t seem to be a solution. Ignore erros is not to eliminate them. I would prefer to have it solved for real, instead of just ignoring. Please let me know if is there any real solution, thanks.
November 8, 2016 at 2:58 am #1248372
ChristopherModeratorHi there,
Actually there is no error. It’s warning and warnings are not errors and they don’t have effect on your site. You can add
error_reporting(0)in wp-config.php file to hide warnings.Hope it helps.
November 8, 2016 at 3:51 am #1248416
fabiofavaParticipantOk thanks anyway. Just funny that this line comes on a file called “error_log”…
November 8, 2016 at 5:06 am #1248491
ChristianModeratorYou’re welcome.
November 8, 2016 at 8:36 am #1248709
fabiofavaParticipantThis reply has been marked as private. -
AuthorPosts
- <script> jQuery(function($){ $("#no-reply-1247058 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>
