mvied
Forum Replies Created
-
What settings do you have enabled?
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] [Plugin: WordPress HTTPS (SSL)] 500 after 3.2 installTry deleting the plugin and reinstalling the latest version. I hotfixed this issue.
No matter what you do, https://baseballthinktank.com/wp-login.php?redirect_to=http%3A%2F%2Fbaseballthinktank.com%2Fwp-admin%2F&reauth=1 will never work. Any time you login via HTTPS in WordPress, hitting the admin panel over HTTP will log you out. That login URL’s redirect_to parameter is set to an HTTP address, so immediately after logging in you’re redirect to the HTTP admin panel, which logs you out immediately.
It’s the first question in the FAQ.
This is from 3 months ago. It’s not the same code, or problem.
This is literally the first question in the FAQ.
I’ve put 3.1.2 back as the stable version. You can downgrade to any version at any time. I should have a fix out soon.
I’ve rolled back to 3.1.2 for the time being. I have a pretty good idea of what’s going on. I’ll have a development version to test when I get some time to debug.
You’re talking about something completely different now. What about your initial issue?
Also, the dev version is the same as the current version. I pushed it out today.
After the page loads, an
<object>tag with the favicon in thedataattribute is created at the end of thebodytag. Since the tag does not appear in the source code, it’s safe to say that JavaScript is adding this in.Try disabling plugins until it stops. It’s possible that it’s not one plugin, it could be a conflict with two plugins, or a plugin and your theme.
Well, the easy way is to use CSS to hide it. I put an ID on it, so you should be able to say
#wordpress-https.postbox { display: none; }somewhere in your theme or admin stylesheets.Post a link. I can probably tell you where it’s at.
Yeah, you were definitely hitting PHP’s memory limit in that case.
This particular plugin isn’t written in a way that it can work with my plugin. It could, but it’s not. The author is not using the right filters.
Check your server’s error logs.