Hi,
Had you changed all the links from http to https in the database.
” I have forced it using config” what did you did in the config file? Can you please explain?
Thanks
define(‘FORCE_SSL_ADMIN’, true);
changed URL in settings to https://
server setup run site in https://
You have to change URLs in the WordPress database; forcing https in wp-config.php or .htaccess or on the server does not change current URLs in the database. Use interconnectit.com WordPress Serialized PHP Search Replace Tool
Wouldn’t the define(‘FORCE_SSL_ADMIN’, true); direct all to load in https://
Changing the URL in setting to https:// should have done same.
Was told perhaps MTU packets..Although works fine on my network connecting to other installs in https://
I have tried to connect on five computers, 3 networks…same blue text links in https://…http:// works fine
Wouldn’t the define(‘FORCE_SSL_ADMIN’, true); direct all to load in https:// Changing the URL in setting to https:// should have done same.
Absolutely not.
We’re talking about the database and/or hardcoded links in theme files. I’ve dealt with this more times than I can remember.
1) Use the developer tools in Firefox (or Firebug) or Chrome or Safari or IE to see the errors with specific images.
2) You may need to change URLs of media items in the post/page content to https. Search RegEx is a good plugin to be able to search and replace (optionally with grep) through all posts, pages, excerpts, comments, titles and meta. And, interconnectit.com WordPress Serialized PHP Search Replace Tool can be used to find/replace in the entire database, i.e. metadata, GUIDs and widget content, etc.
3) You may need to change to a relative path for images in CSS files, i.e. background-image: url(http://example.com/themes/wp-content/theme/images/image.jpg) to background-image: url(images/image.jpg)
4) You may need to remove the http from absolute paths in php theme files, i.e. change 'http://example.com/image.jpg' to '//example.com/image.jpg'; that will allow your resources to default to https.
So Mark, by placing the https:// in front of the URL on any install should bring up all files in https and admin will work as normal. It’s ins’t necessary to change database values. I have never done this before and it works on all others…
If you are familiar with NGINX, that would help…I think it’s an internal issue. Thanks for posting.
re-write rules maybe…with NGINX..so I may need to manually change database. I’m really not liking that option.
