stoberov

Hi Rogier,

I fully understand and I have little doubt efforts have been made to ensure the plugin works out of the box for everyone.

For what it’s worth, I’d like to share that the site’s original files (including functions.php) have not been modified, nor .htaccess has been tweaked manually.

Looking at the installed plugins, most are really “innocent”, and of the bigger ones, only All In One WP Security seems to me like something that may cause trouble (its settings modify .htaccess).

That’s about it for now – great job with your extension still!

Hi Mark,

Yes, I pressed the button before changing the site address (99% sure).
In fact, I have a copy of the site from a few days ago that is running on a different domain without Really Simple SSL – and I’ve just double-checked that both WordPress Address and Site Address inputs display with HTTP there. For that 1% possibility that I carelessly updated manually one of the two inputs with no apparent reason – apologies.

With this in mind, once I installed & activated Really Simple Plugin earlier today only the WordPress Address field got updated to (or simply stayed) HTTPS.

I hope this helps somehow.

Hey,

I just had absolutely the same issue – installed & activated the plugin > “Activate SSL” button > a 500 Error > still the SSL seemed to be working, only there was the big alert message in Admin area.

At that time, I found this answer and thought to add the constant in wp-config.php myself. But then I noticed I hadn’t updated the second URL as shown here:

Image

Once I changed HTTP to HTTPS in Site Address, the warning was gone.

Hope that helps!

• This reply was modified 7 years, 1 month ago by stoberov.

Hi, I just got an email from a client, who experienced the same issue – “wp.template is not a function”. I noticed the button was visible when logged in, but disappeared after logging out, so suspected this could be an issue with the cache.

Now, I’m not really sure if that’s a coincidence, but client migrated the site to a new server a few days ago. I thought it may be a good idea to deactivate and activate again the caching plugin on the site – W3 TOTAL CACHE.

EUREKA! This “fixed” the button.

Wonder if this would fix it for you, too.

Hi, I have the same question raised by a client. Did you hear anything on this?

Looking for just the same thing :/