CPT-onomies: Using Custom Post Types as Taxonomies
[resolved] admin-post.js and css over https issue (2 posts)

  1. mtomic
    Posted 2 years ago #

    Hi guys,

    I have

    define('FORCE_SSL_LOGIN', true);
    define('FORCE_SSL_ADMIN', true);

    in wp-config.php file.
    When I edit a CPT, I get the following errors in my browser console
    /wp-admin/post.php?post=xxxx&action=edit was loaded over HTTPS, but ran insecure content from http://xxxx/wp-content/plugins/cpt-onomies/js/admin-post.js?ver=3.8.1 and '/wp-admin/post.php?post=xxxx&action=edit' was loaded over HTTPS, but ran insecure content from 'http://xxxx/wp-content/plugins/cpt-onomies/css/admin-post.css?ver=3.8.1' files should also be loaded via https.

    Without those 2 files, my CPT edit page is broken. Any ideas?


  2. Rachel Carden
    Plugin Author

    Posted 2 years ago #

    Hmm. Are you still having problems with this?

    It's hard for me to test this. I made a couple of changes to admin.php. Can you tell me if this worked for you?

    Here are the changes listed out. Just a few changes to the admin_register_styles_and_scripts() function.

    You can see the updated filed on WordPress SVN or my Github account.


Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic