Thread Starter
tamar
(@tamar)
Okay, this is still bugging me as I really want to show this blog post to people…
From reading through the archives, this bug existed in 1.x and probably has something to do with the syntax of this line in wp-pass.php:
setcookie(‘wp-postpass_’ . COOKIEHASH, $_POST[‘post_password’], time() + 864000, COOKIEPATH);
What can I try?
So far –
1. I deactivated all of my plugins (yes, all).
2. I changed the password.
But it looks like something that may have been inherited from a previous version: http://wordpress.org/support/topic/14408?replies=5
Am I right and can someone help?
Thread Starter
tamar
(@tamar)
Hey, sorry to bump, but I’m really in need for assistance here.
Thread Starter
tamar
(@tamar)
Bump… do the WP developers ever come by here to fix problems addressed here? I’m not gonna give up 😛
Thread Starter
tamar
(@tamar)
I even changed hosts (for unrelated reasons) and NO LOVE.
Thread Starter
tamar
(@tamar)
Hello, is anyone home?
This is still an issue for me. I changed themes, I removed all plugins, this issue is STILL there. Has nobody encountered this yet or is nobody here a programmer who is able to fix it or at least acknowledge the problem?
I am having the same exact issue & like you I am not finding documentation anywhere that anyone has given a resolution to this. Can someone out there please come up with something before some of us decide to start using another blogging program???
Thread Starter
tamar
(@tamar)
Truthfully, I don’t think anyone uses it which is why nobody here can offer any suggestions on it. 🙁
Sorry, I don’t think most of us who try to help out here use the passwording stuff. And as for the devs, no, they don’t spend any time “helping out” here….
Well, I can replicate the issue when trying to password protect a Page as opposed to a Post, for what that’s worth.
Have you had a look at http://trac.wordpress.org/ to see if this is a known bug? If not, *please* be encouraged to log it there so the developers are aware of it and can fix it (no, they don’t hang out here much).
Well, here it is: http://trac.wordpress.org/ticket/3445
We’ll see what happens.
Works for me using the Default theme and both WP 2.0.5 and WP 2.0.6 beta 1
One thing that could be causing this is if your Blog URL is set to something that is automatically redirected. Say that your Blog URL is http://example.com/ but http://example.com/ forwards to http://www.example.com/ In that case, the form’s POST would get wiped. But you’d likely have a lot more problems than this, if that were the case.
I use no redirection. I’m using 2.0.5.
Just tried with Default theme. Same thing. You’re welcome to have a look at http://www.solo-technology.com/blog – try the Disclaimer page link
[Update: I’ve spammed a bunch of updates over on the trac ticket]
After more testing and a lot more spamming of the related trac report, I’ve realized that this feature works fine on a new install of 2.0.5.
Thus, I’m willing to bet it’s probably a plugin induced issue.
tamar – are you running wp-cache plugin?
Thread Starter
tamar
(@tamar)
HandySolo, no I am not. It was giving me problems (on a completely different blog) and I decided I wouldn’t be using it again.
However, regarding markjaquith’s mention of redirection, I have the following in the particular site’s .htaccess:
Options +FollowSymlinks
RewriteEngine on
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
I’m not sure if that’s causing it. But I definitely needed that as my wp-admin page wasn’t working without it.
