Conflict with Advanced Access Manager (AAM)

  • Resolved hexaae

    (@hexaae)


    1 year, 9 months ago

    I built some offline HTTP sites with the Advanced Access Manager (AAM) plugin installed… then migrated them online to a new site with SSL certificate and added Really Simple SSL (RSSSL) to be sure and prevent any potential mixed-content errors…

    Well, the problem is that for all the sites where I used RSSL after AAM was installed, I experienced this annoying issue with AAM (got its HTTP requests blocked) resulting in no CSS loaded for this plugin in the backend, making its UI unusable (see this other thread): HTTPS and AAM CSS files: mixed contents issue | www.remarpro.com
    To make its UI work again I have to disable RSSSL, and in case remove the forced SSL lines from my wp-config.php.

    Could you please investigate the compatibility of your RSSL plugin with AAM installed? Both are precious and useful WP plugins to have installed.

    P.S. I tried also “One Click SSL” and got no trouble whatsoever with AAM instead.

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

    (@rogierlankhorst)

    Possibly the AAM plugin still uses http for its requests. For performance reasons the RSSSL plugin does not fix mixed content in the back-end, but you can enable the back-end mixed content fixer in the settings. Better would be to get AAM to load over https.

    Possibly re-saving the settings in AAM helps.

    I will take a look at the plugin as well.

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    We use this plugin as well on some of our sites, without any problems. So it seems to be some sort of specific configuration that causes it.

    I just did some checks on the AAM plugin, and it loads the css files in the recommended way, with plugins_url(). WordPress will use the site_url to pass the correct protocol. When Really Simple SSL is activated, and you have activated SSL, your site url should be https. You can check this in your general settings. (settings/general).

    What is the error you see in the console when you have this issue? (for the console, right click on screen, “inspect”, “console”). Is it a single site or multisite installation?

    Hi @hexaae,

    We haven’t heard from you in a while, is the issue resolved? If you still need our help, just let us know!

    Please provide us with the additional information my colleague requested so that we can investigate further.

    Kind regards, Kim van Dijk

    Thread Starter hexaae

    (@hexaae)

    Sorry for long delay.

    @rogierlankhorst

    Thanks for your reply, I can give you temporary limited admin access to a building site where I can still reproduce the issue with AAM…

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    @hexaae I’m sorry, as per the forum rules it is not allowed to share any kind of access. An alternative method is not describe step by step which settings you use, or maybe export your settings and post them here or email them to us (support(at)really-simple-ssl.com).

    If it’s a setting this should enable us to reproduce the issue.

    Plugin Support jarnovos

    (@jarnovos)

    Hi @hexaae,

    Have there been any further updates regarding the matter? We would be glad to take a closer look at the described behavior, if we know how to replicate it on our end.

    Kind regards, Jarno

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Conflict with Advanced Access Manager (AAM)’ is closed to new replies.