• After installing the 3.3.2 update, I see a lot of warning within my debug error file:

    PHP Warning: Cannot modify header information - headers already sent in /home/website/public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 688

    Is it possible to fix this issue, please? Thanks!

Viewing 9 replies - 16 through 24 (of 24 total)
  • Thread Starter wabetainfo

    (@wabetainfo)

    Hi @wpmansour,

    Unfortunately, the 3.4.2 update does not fix this issue. I downgraded to 3.3.1 again where this issue does not occur.

    Hi @wpmansour

    Sorry, but I can also confirm the 3.4.2 update does not resolve this issue.

    Plugin Support wpmansour

    (@wpmansour)

    Hi @wabetainfo and @hooter,

    Thank you for your patience. Our team has already started fixing this issue as it only occurs in particular shared server configurations. The fix is in progress and will be included in the next release.

    We truly appreciate your patience and understanding while we work to roll out this update.

    Best Regards

    @davidanderson

    With all due respect could you please put your eyes on this. There are two different topics about this same issue that have been marked as “Resolved” when that is simply not the case and this has been dragging on for over 2 months now.

    Here is the other topic for same issue that is marked as “Resolved”

    https://wordpress.org/support/topic/cannot-modify-header-information-197/

    Thank you.

    Thread Starter wabetainfo

    (@wabetainfo)

    Hi @wpmansour
    You told us that the next release would have included the fix for this issue. I just updated to the 3.5.0 version and this issue is still not fixed. It’s been over 4 months…

    PHP Warning: Cannot modify header information - headers already sent in /home/website/public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692

    @wpmansour

    Same here…I have upgraded 20 client sites to WP-Optimize 3.50 and the issue is still not resolved.

    Plugin Support vupdraft

    (@vupdraft)

    Hi,

    Apologies, we did not manage to get the fix into the latest release. We are still working on it.

    Thread Starter wabetainfo

    (@wabetainfo)

    Thank you @vupdraft for this update. I believe it is worth noting that I experience this issue when wp-cron.php is executed.

    Plugin Support vupdraft

    (@vupdraft)

    Apologies for the delay. Thank you for the additional information and for bearing with us.

    I checked our Git Lab and it’s in progress and has been labelled as “next sprint” so it should not be too much longer (once it’s been completed, it will then go through testing before it is merged)

    We will be providing a fix for this though.

Viewing 9 replies - 16 through 24 (of 24 total)
  • You must be logged in to reply to this topic.