Forum Replies Created

Viewing 14 replies - 1 through 14 (of 14 total)
  • Thread Starter shoulders1024

    (@shoulders1024)

    • A clarification. I Re-Checked, the wordfence code present in the “root” .htaccess is also not removed when I deactivate WF.
    • The code .in the user.ini is also not removed when I deactivate WF.
    • I would expect all code to be removed similar to W3C Total Cache.
    • Disable Code execution for uploads directory is checked.
    • When I deactivate WF, I select Keep all Wordfence tables and data

    My Migration involved using the the cpanel WHM Transfer tool so the website was moved as is. It was only when I got to the new server I started making everything for LiteSpeed. For instance by disabling and then re-enabling W3C Total Cache, the rule were removed and then re-added but the LiteSpeed Variant.

    For wordfence I disabled it and then manually deleted the code in php.ini the user.ini and the .htaccess , then re-anable and re-run the configuration wizard whihc then added in the relevant code into the .htaccess and created a user.ini

    I hope this helps

    Thanks

    Thread Starter shoulders1024

    (@shoulders1024)

    is it a bug that when i flush using the <post> option as above it comes back and says

    Success: The page is flushed from cache successfully.

    However, the item being flush is actually a page. I think this particular function needs a little bit of a tidy up, especially the instructions/syntax at the top of the function.

    I will sort out a review shortly. Thanks again.

    Thread Starter shoulders1024

    (@shoulders1024)

    that worked, i assume the page is actually flushed because I got the response

    Success: The page is flushed from cache successfully.

    should the command instruction be written as follows:

    usage: wp w3-total-cache flush ( [all] | [post --post_id=<id>] | [page --permalink=<post-permalink>] )

    thanks for the help, i will add this to my notes.

    Thread Starter shoulders1024

    (@shoulders1024)

    no success, just an error message telling me the usage of the command indicating that the command I used was wrong

    Thread Starter shoulders1024

    (@shoulders1024)

    using

    /usr/local/bin/ea-php83 /home/myaccount/wp-cli.phar --path=/home/myaccount/public_html w3-total-cache flush --post_id=816

    I got the response

    usage: wp w3-total-cache flush <cache> [--post_id=<id>] [--permalink=<post-permalink>]

    thanks

    Thread Starter shoulders1024

    (@shoulders1024)

    I submitted the support form thing in the backend from wordpress to you guys and now the website is working again. no settings have been changed.

    back to the drawing board 🙁

    Thread Starter shoulders1024

    (@shoulders1024)

    I spoke too soon and the issue is back. I have not cleared the cache this time to allow for proper diagnosis. so about 4 weeks of it running fine and then the pages get the garbled output.

    I do have an error in a PHP file related to a menu override (i think) to allow microsoft store links but I also think I have this issue before I added that mod. This error occurs when the site is working and when it is not, so I don’t thin it is that.

    -Sep-2025 15:41:32 UTC] PHP Warning: Undefined array key "host" in /home/<MYACCOUNT>/public_html/wp-includes/canonical.php on line 717

    I am at a loss, it might something silly I have done or not done but if you can give me some pointers that would be helpful.

    Workaround above

    don’t seem to be valid now.

    Thread Starter shoulders1024

    (@shoulders1024)

    @vmarko So far the corrupted page output has not returned so the ZLIB mod_php flag’s position in the .htaccess is important as mentioned above.

    Workarounds / Fixes

    • Disabled GZIP in both cPanel multi-php and Total Cache
    • Don’t run on a server using mod_php
    • Move the Total Cache code after the cPanel mod_php code in the htaccess file
    • I am sure there are more examples…
    Thread Starter shoulders1024

    (@shoulders1024)

    @vmarko thanks for such a quick response.

    While testing, I have reset the cache so it would be a little pointless at this time and I am not sure it would be safe to post it. I could potential email over or PM the website address if it fails again. It is an interesting issue.

    I do not have any other otpimization on this site. I do have divi and it compresses the content like all of my other sites. This might the the only one where I use the cPanel php.ini manager where it adds rules to user.ini, php.ini, .htaccess.

    Here is an interesting thought that I am working with.

    Settings

    • The servers main php.ini has zlib.output_compression = Off
    • The cpanel local php.ini has zlib.output_compression = Off
    • The cpanel htaccess has php_flag zlib.output_compression Off
    • I am using page cache.
    • GZip is enabled in total cache settings which adds the deflate rules into the htacess.
    • The cpanel code in the htaccess is after the Total cache rules

    What I think is happening

    I think that the php.ini is setting the content-encoding header to off, then your total cache code is turning the code back on because of the deflate/compression rules, but then the php_flag zlib.output_compression Off in the htaccess is then turning the content-encoding back off because this rule is parsed after your total cache rules in the htaccess file.

    So the pages are compress/gzipped but the relevant header is no longer present when the payload is sent to the browser.

    The inconsistent nature might be due to the page cache getting purged or updated by something. I am not sure about this thought.

    Potential solutions

    • disabled the php_flag zlib.output_compression Offin the cpanel .htaccess file.
      or
    • move the cpanel rules to above the total cache rules

    So it might be the fact that cpanel is still using mod_php as there are unexpected results when using php flags in the htaccess.

    Currently trying
    I have currently commented out the php_flag zlib.output_compression Offrule in the cpanel .htaccess file and so far so good.

    @nikdow I sent you some information by your contact form.

    Thread Starter shoulders1024

    (@shoulders1024)

    It has now worked and downloaded 10 new reviews

    Thanks

    Thread Starter shoulders1024

    (@shoulders1024)

    another member said he had the same issue but the post was deleted if that helps.

    Thread Starter shoulders1024

    (@shoulders1024)

    I agree that just unpublishing with no way of knowing what the issue is (other than a security issue) does not help the open source community to fix these issues and keep extensions alive.

Viewing 14 replies - 1 through 14 (of 14 total)