Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • in reply to: Error after install #31193
    factorone33
    Participant

    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.

    in reply to: Error after install #31079
    factorone33
    Participant

    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.

Viewing 2 posts - 1 through 2 (of 2 total)