FAQ

Home | Setup | FAQ | History | Reset

Welcome to the official FAQ for WordPress plugin Admin SSL.  If you have a question, comment or bug report, please add a comment to the Admin SSL home page.  However, before you do so, please read the FAQ below.

I enabled SSL and my site is inaccessible – what should I do?

If you ignore the warnings on the Admin SSL configuration page, and enable it without having a valid Private SSL certificate installed, then your site will be inaccessible.  Please read the instructions here to reset Admin SSL.

Why does the visual editor stop working?

This is due to a bug in the TinyMCE editor that comes with WordPress itself.  It has been fixed in WordPress 2.5.1, so it is strongly recommended that you upgrade to that version.

For more information please go here.  Alternatively, you could use a different editor like WYMeditor, using the simple-wymeditor plugin.

Why does K2's live commenting stop working?

This issue is due to a conflict between Admin SSL's output buffering and K2′s. The quick-and-dirty fix (I haven't found an issue with it yet) is this: comment out the output buffering in lines 30 and 34 in:
/wp-content/themes/k2/comments-ajax.php.

As far as I can see from the K2 code this won't do anything drastic, but I can't say that 100%.

Why does my Dashboard display as insecure?

As of version 1.0 of Admin SSL this will only happen if you have added 'wp-admin/' to the Additional URLs section of the Admin SSL configuration page.

Since WordPress 2.5, it is possible to have a plugin that displays on the Dashboard.  If that plugin references an image, stylesheet or script file using HTTP rather than HTTPS then your browser will tell you that the Dashboard page is only partially encrypted.

As with the TinyMCE issue above, this is not a problem with Admin SSL, but with plugins that do not support HTTPS.  I'm afraid that all you can do is put up with it, or ask the plugin author to support HTTPS.

How do I use debug mode?

You should never need to use this unless requested by me for troubleshooting purposes.

Admin SSL has a built-in debug mode which can be enabled in admin-ssl.php by changing the DEBUG constant from 'false' to 'true'.  Once you have done this, create a file called 'debug.log' in your admin-ssl/ directory and give it global read/write permissions (on a Linux machine, type 'chmod 777 debug.log').

While debug mode is enabled Admin SSL will display a message on all admin screens – you should not leave it enabled for a long period of time because otherwise the log file will grow to be enormous.  Log entries are added for all pageviews, for guests as well as registered users.

3 Responses to “FAQ”


Leave a Reply

Archives

Categories