-
Notifications
You must be signed in to change notification settings - Fork 85
Make sure everything works with FORCE_SSL_ADMIN #48
Comments
Thanks, I think I've fixed it with the patch above. Could you download the source form GitHub ( not WordPress.org) and let me know if this fixes your problem? |
It works for pages, but not the static front page. It looks like the link variable is getting overwritten by another procedure in the code with the If statements. If I add a condition of !$link it works properly. [code]
[/code] Thank you for working on this so fast! I enjoy the plugin especially with the Hueman theme. |
Yeah, I guess I overlooked the new post link. I doubt the login issues are related though. Could you try deactivating this plugin? |
Hi avryl, It seems to be working now. I will do more testing over the week. Thank you for fixing this! Thanks, |
Hi avryl, I discovered another issue. When the AJAX call is done by jQuery it seems it returns "0" from the admin ajax PHP file. It looks like you need to do the AJAX call from http to http and on an https page to https. I will do testing and let you know if I come with code to fix this. Thanks, |
Here is some rough code for fixing the AJAX calls between HTTP and HTTPS. If you are on the home page for example and say New Post on a non-HTTPS connection while requiring HTTPS it will not work. Here is some rough code to fix it. Place it under public function wp_enqueue_scripts(): [code]
[/code] |
Hi. We're working on a completely rewritten 1.x version. If you have time, would you mind testing it with SSL? |
Hi avryl, Sorry for the long response time. I have been working on some stuff at work and haven't had a chance to play with Wordpress. I did manage to test the new version and it is working fine with SSL, but I noticed on another site I have that uses a reverse proxy that the wp_redirect in the code is causing too many redirects. Everything else on my site is fine using IIS Reverse Proxy and URL Rewrite to a Synology with Apache; however, activating this plugin makes the home page unusable when logged in. [code] I removed the if and this line in the if statement and my site was able to edit content on the reverse proxy site. I am going to do some additional testing on my other site as well. Thanks, Edit: 1:08 AM Eastern It looks like when doing this there is a problem with uploading using the Featured Images. I can upload through the admin tool, but not the Front-End Editor. |
Thanks for the reply! I will try to enable SSL myself sometime. But the right behaviour would be to enforce SSL for any editable pages if FORCE_SSL_ADMIN is true, right? This means any singular post or page, and also the front-page if there is one, if the user has the ability to edit. Hopefully this can be fixed before 1.0. |
Hi avryl, I would want to edit pages with complete SSL. My site is running dual HTTPS and HTTP because I am using a self-signed certificate for my editing and administration right now and the content is displayed on HTTP. I didn't want to spend a lot for a certificate that was just going to be used for administration. Anything I edit, upload, or administrate would be SSL. The regular site (for users) would be regular HTTP. I noticed that even without Reverse Proxy I had issues with using straight IIS with an install of the Wordpress 4 with the redirect to HTTPS. I would go to the home page after activating the plugin and the site would go into a redirect loop and my Mac / Safari would say "Too Many Redirects." Thank you for all your work on this. The new editing features look great! Chris Z. |
Hello,
I discovered an issue were if I force my web site to FORCE_SSL_ADMIN that I am unable to save web pages unless the editor opens in a SSL mode on the web site. I have a self-signed certificate with FORCE_SSL_ADMIN and LOGIN enabled which prevents the default editor in both the latest Git and plugin stable release not to work. I came up with some pseudo code to replace in the class file to allow for saving of work in SSL. The editor will open in SSL and then save properly.
Some modifications might have to be made, but this is a rough cut to get going.
[code]
[/code]
Thanks,
Chris Zenzel
The text was updated successfully, but these errors were encountered: