HTTPS issue with AAM’s CSS files

  • We switched to HTTPS and found that for some weird reason only AAM plugin has issues loading its CSS files /css/vendor.min.css and /css/aam.css on the backend.
    We tried everything, and the only solution was to manually edit ‘advanced-access-manager/application/Backend/tmpl/metabox/iframe-header.php’ and change at rows 25-26: “<?php echo AAM_MEDIA; ?>” to “/wp-content/plugins/advanced-access-manager/media”

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

    (@vasyltech)

    @hexaae,

    Hm, AAM uses WordPress core function plugins_url to determine the correct URL to the plugin’s directory. My only guess would be that they way that was chosen to switch to HTTPS protocol is not completely correct because it is not recognized by WP core.

    Keep me posted.
    Regards

    Hi there,

    Was there any solution found to this? I have been having the exact same issue on a site. My site shows this mixed content message and refuses to load the vendor.css [advanced-access-manager/media/css/vendor.min.css] and aam.css [advanced-access-manager/media/css/aam.css] – all the rest load fine.

    Is there any chance these two are hardcoded in the plugin?

    I haven’t confirmed this – but my thought is that if the site URL is defined in the database as ‘http’ and then instead of using WordPress Settings > General to set as ‘http’, if it’s overridden in wp-config.php and assigned as ‘https’ – I wonder if then the AAM_MEDIA already has been set to ‘http’ because that’s what’s in the database had when it was defined.

    I also see the same http being loaded for the svg logo and that also sits in the media directory. so it seems to be related to the AAM_MEDIA definition.

    @vasyltech any thoughts?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘HTTPS issue with AAM’s CSS files’ is closed to new replies.