new 2.2.18 version bugs and break-ups

  • Resolved scriptorium

    (@scriptorium)


    9 years ago

    Hello Rogier,
    I just updated the plugin to the last 2.2.18 version and immediately I got problems:
    1/ instead of what was mentioned on the admin plugin settings front-end, there was htaccess rules set, but these were not detected
    2/ moreover, except for the version number 2.2.18 instead of the 2.1.18 present in my htaccess file, the rules shown by the plugin to be inserted in the htacces file was buggy:
    instead of the original:
    RewriteRule ^(.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
    this line was proposed:
    RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
    3/ I changed the version number and the above line and … broke everything up in the htacces and in the plugin settings since the permanent HTTP Strict Transport Security was not recognized any more!
    4/ I reverse the line back to the previous one and it worked
    5/ I checked it up while removing all lines referring to simplessl in my htaccess file, setting the file rights to 644 and letting the plugin updating the htaccess by itself. And I was right: the buggy $ was not there!
    6/ An another bug: since the 2.2.13 you’ve added a “check if the mixed content fixer is functioning on the front end”. Good, but the fact is with the 2.2.18 version the front-end shows The mixed content is activated, but not functioning at the front end.
    Strange! since my ssl lock is green indicating there’s no mix content
    7/ I checked the debug option in the settings tab and had a look to the result. Here it is:

    loading options...
    plugin version: 2.2.18
    pluginurl: https://www.scriptorium-albi.fr/wp-content/plugins/really-simple-ssl/
    testing for ssl...
    https://www.scriptorium-albi.fr/wp-content/plugins/really-simple-ssl/ssl-test-page.php
    SSL test page loaded successfully
    ssl type: LOADBALANCER
    --- force ssl: FALSE
    testing htaccess rules...
    htaccess rules test success.
    checking if .htaccess can or should be edited...
    rules already added in .htaccess.
    no siteurl/homeurl defines in wpconfig
    converting siteurl and homeurl to https
    Detected Yoast seo plugin
    No conflict issues with Yoast SEO detected

    Seems everything fine but there’s something wrong!
    8/ I unchecked the Enable javascript redirection to ssl since I consider it to be more troubleshooting than resolving the problems. Once written in the htacces access file the rules are set up for all and ever. I do not need to see messages that the plugin has been reverse to javascript ruling if set in htacces (I know it works fine and I have remove any of my mixed content for a while), unless the plugin can not read any more the file of course.
    Well I hope this would be helpful to you. For I have solved the problems by myself it is now up to you to check what might have happened.
    Good luck to you.
    Regards.
    Gilles

    https://www.ads-software.com/plugins/really-simple-ssl/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    Hi Gilles,

    Thanks for the feedback. That $ in the code has been there since 2.2 at least. You’re the first that reports issues with it. I could remove it, if I can be reasonably certain other users do not suffer from it.

    That check on the mixed content fixer is just that: an extra check which might indicate issues with other plugins. If the plugin for some reason cannot find the comment in the source, it assumes there might be something wrong. This can also be caused by a plugin that removes comments, for example. It is just a tool to discover issues, not a core function. I’ll think about ways to make this check more solid.

    Thread Starter scriptorium

    (@scriptorium)

    Hi Rogiers,
    Thanks for your fast answer.
    As for the $ in the code I’m surprised since the plugin is regularly updated meaning this should have happened to any of the updates of the 2.2 branch or at least to one of them.
    Regarding the check mixed content fixer I do not see any more the animation during the checking meaning I cannot check any pages any more from the plugin admin page.
    2 “bugs” or “dysfunctions” with the same version cannot be a coincidence. Rather I have installed or uninstalled something that broke your plugin -this I can’t believe for you’ve submitted 2 or 3 updates within a few days only, if I’m not wrong- or rather this very update has something specific. That’s only some theoretical thoughts.
    Anyway, thanks again.
    Regards.
    Gilles

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    The mixed content scan in the back-end was removed, as it wasn’t really usefull anymore. I’m planning to introduce it again, but then with a scan for external domains that cannot be loaded on ssl, which is gives issues on a lot of sites.

    I’ll do some tests concerning you comments. Thanks.

    Rogier

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘new 2.2.18 version bugs and break-ups’ is closed to new replies.

Tags