Forum Replies Created

Viewing 15 replies - 1 through 15 (of 118 total)
  • Hello, I have the same issue on one of my sites:

    
    [Fri Feb 26 12:06:31.099266 2021] [proxy_fcgi:error] [pid 88901:tid 140343483721472] [client 86.201.188.131:0] AH01071: Got error 'PHP message: PHP Warning:  rmdir(<redacted>/public_html/wp-content/cache/wpo-cache/<redacted>): Directory not empty in /<redacted>/public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 835PHP message: PHP Warning:  rmdir(<redacted>/public_html/wp-content/cache/wpo-cache/<redacted>): Directory not empty in <redacted>/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 835PHP message: PHP Warning:  rmdir(<redacted>/public_html/wp-content/cache/wpo-cache/<redacted>): Directory not empty in /<redacted>/public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 835PHP message: PHP Warning:  rmdir(/<redacted>/public_html/wp-content/cache/wpo-cache): Directory not empty in /<redacted>/public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 835', referer: <redacted>/wp-admin/plugins.php
    

    Does someone have any guidance on how to solve this?
    Thank you.

    • This reply was modified 7 months, 3 weeks ago by Francesco.
    • This reply was modified 7 months, 3 weeks ago by Francesco.
    Thread Starter Francesco

    (@fcolombo)

    Thank you @chouby for your reply.

    I have tried re-saving the term where the link is correct, but it doesn’t help.

    I’ve also tried re-estabilish the link via the autocomplete from the term where the link is correct, and re-saving, but also doesn’t help.

    And about the autocomplete, unfortunately it doesn’t work for the terms where there is no link. It spins and either finds zero terms, or only lists the other unrelated terms that have the same issue.

    For one term, the autocomplete suggests two lines which are the same term.

    I’ve now also noticed that some of the inter-links displayed in admin don’t match with the frontend.

    There’s something very odd and I can’t quite wrap my head around it. It’s been like that for a while unfortunately. Any help or ideas you could suggest would be very welcome, Chouby.

    Thanks in advance.

    Thread Starter Francesco

    (@fcolombo)

    To add to my findings, in the wp_terms table I can see a list of categories and tags.
    The categories and tags that got unlinked show with their original slug.
    Then, I can see a series of pll_string (such as pll_55c08684bc2b3), which might be the interconnected categories processed by PLL.
    So should I intervene in this table, and how?

    Thread Starter Francesco

    (@fcolombo)

    Hello and happy new year 🙂
    I’m just wondering if someone had any idea about this issue. Any help appreciated!

    Thread Starter Francesco

    (@fcolombo)

    Hi @markwolters ,

    Just checking in because I think I’m getting confused and I don’t know if there’s an actual issue, and if the issue is with my hosting provider, or with the plugin, or with both.

    I have troubleshot a little further, and here are the results:

    • Activating the “Force HTTPS” from cPanel works, but the RSSSL plugin shows the notification that no 301 redirects have been set-up, so I’m not sure if it’s a tight solution. The loadbalancer test page still does not load.
    • I’ve tested in .htaccess the snippet I posted in my previous post (Code1, see below), and it seems to work; but the plugin still throws the error about no 301 .htaccess enabled, and the loadbalancer test page still says that there are “too many redirects”.
    • The hosting company has got back to me with a generic helpdesk https redirect reply, and suggested I try with Code2 (will post below). The end result was the same as with Code1: it seems to work, but the plugin doesn’t “recognise” it, and the loadbalancer test page still fails.
    • I’ve deactivated all plugins and tried with an empty .htaccess, but the default snippet that RSSSL attempts to add fails the test

    So I don’t really know what else to do apart from giving up and staying with the WordPress 301 redirection.

    Is there anything I can provide for you to see if this is a compatibility issue with my server configuration and the plugin?

    Thanks in advance

    Code1

    
    # BEGIN rlrssslReallySimpleSSL rsssl_version[3.0.5]
    <IfModule mod_rewrite.c>
    RewriteEngine on
    RewriteCond %{HTTPS} !=on [NC]
    RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$
    RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/[0-9a-zA-Z_-]+$
    RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
    RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
    </IfModule>
    # END rlrssslReallySimpleSSL
    

    Code2

    
    RewriteEngine On
    RewriteBase /
    RewriteCond %{HTTPS} off
    RewriteCond %{HTTP:X-Forwarded-Proto} !https
    RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
    
    Thread Starter Francesco

    (@fcolombo)

    Quick update @markwolters

    Switching the “force HTTPS” option via cPanel doesn’t work – it throws an error.

    Digging around, I found a backup of an old version of .htaccess, which starts with this line from an old version of your plugin:

    
    # BEGIN rlrssslReallySimpleSSL rsssl_version[3.0.5]
    <IfModule mod_rewrite.c>
    RewriteEngine on
    RewriteCond %{HTTPS} !=on [NC]
    RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$
    RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/[0-9a-zA-Z_-]+$
    RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
    RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
    </IfModule>
    # END rlrssslReallySimpleSSL
    

    Considering that the .htaccess redirect used to work, should I try with this snippet instead?
    What do those conditions mean?

    Thread Starter Francesco

    (@fcolombo)

    Thank you @markwolters

    I will go through again the .htaccess file, the various subfolders, etc.

    And will follow up with the hosting provider, too.

    Should I be enabling the “force HTTPS” option in cPanel by the way? At the moment it’s OFF.

    Thread Starter Francesco

    (@fcolombo)

    @markwolters thank you.
    I can confirm the main site is working correctly on https://, and also that there’s no .htaccess file in the /plugins directory.
    I’m really sorry for the back and forth. Could you think of anything else that might be causing the issue?

    Thread Starter Francesco

    (@fcolombo)

    Thanks for clarifying @markwolters .

    I’ve added this at the bottom of wp-config.php:

    
    //Begin Really Simple SSL Load balancing fix
    $server_opts = array("HTTP_CLOUDFRONT_FORWARDED_PROTO" => "https", "HTTP_CF_VISITOR"=>"https", "HTTP_X_FORWARDED_PROTO"=>"https", "HTTP_X_FORWARDED_SSL"=>"on", "HTTP_X_FORWARDED_SSL"=>"1");
    foreach( $server_opts as $option => $value ) {
      if ((isset($_ENV["HTTPS"]) && ( "on" == $_ENV["HTTPS"] )) || (isset( $_SERVER[ $option ] ) && ( strpos( $_SERVER[ $option ], $value ) !== false )) ) {
        $_SERVER[ "HTTPS" ] = "on";
      }
    }
    //END Really Simple SSL
    

    Then I switched on the .htacccess 301 redirect from the RSSSL Plugin config page, and I still get the message that the rule test was unsuccessful.

    Debug still shows /wp-content/plugins/really-simple-ssl/testssl/loadbalancer/ssl-test-page.html as having too many redirects.

    Is there anything else you’d recommend I try?

    Thanks for your time so far Mark.

    Thread Starter Francesco

    (@fcolombo)

    Hello @markwolters ,

    Thank you for your reply.

    There’s nothing added by RSSSL in my wp-config.

    I’m confused – the KB link you posted refers to multisite installations and domain mapping, which is not my case. Should I still be adding that snippet to wp-config?

    Thread Starter Francesco

    (@fcolombo)

    I think the bit of code that needs manipulating is at line 286 of /public/class-lfc-public.php:

    
    		$html .= '<div class="fb-comments" data-width="' . $width . '" data-href="' . get_permalink() . '" data-numposts="' . $count . '" data-colorscheme="' . $color . '" data-order-by="' . $order . '"></div>';
    

    There should be a way so that get_permalink() returns the URL without http:// and/or https://.

    Thread Starter Francesco

    (@fcolombo)

    Forget it – That one seems to be controlled by YOAST itself, not the theme.
    I got confused.
    Nevermind!

    Will edit a template instead 🙂

    Thread Starter Francesco

    (@fcolombo)

    Hey @nikeo ,

    I found it in the WP customiser after installing the latest Hueman.

    See this screenshot: https://imgur.com/qHK6Hp4

    Maybe it got introduced inadvertently?

    Thread Starter Francesco

    (@fcolombo)

    Hi @waebi ,

    Thank you for your input and advises. I ended up setting up staging environments and running possible different scenarios, and in the end the upgrade went smoothly – Much easier than I thought.

    For the benefit of anyone else in a similar situation, I basically:

    • Did a full backup.
    • Set up a staging environment for the old set up, to compare visual differences once the upgrade was finished.
    • Started with a fresh, virgin child theme (empty style.css and functions.php).
    • Run the upgrade.
    • Went through the WP Customizer options one by one, and in many cases had to deactivate / reactivate any option to see changes being implemented (logos, previous colour schemes, etc)
    • Recreated widgets like “AxlTabs” (now Hueman Tabs), etc.
    • Added only the still relevant bits of CSS customisation to my child style.css.
    • Added more customisation to functions.php.
    • Removed plugins that provide functionalities now embedded in the theme, such as lazy loading or minification.

    I think that’s pretty much the checklist I run through.
    Good luck everyone, and thank you Press Customizr for keeping this wonderful theme so well oiled and for making it so good.

    I noticed the same thing as reported by OP and also in the Loom video posted above..

Viewing 15 replies - 1 through 15 (of 118 total)