Furry stuff, oekaki stuff, and other stuff.
You are not logged in.
I've noticed that WP responds differently depending on its absolute url. I discovered this recently when I went to my website, but due to a series of actions that aren't relevant here, left off the "www" from the front of the URL. All the other pages on my site work (including phpBB), but WP refused to allow me to log in, claiming "invalid password." Worse, when I do "recover password" it sends out a password with a link to the site AS IT WAS VISITED (that is, without the "www" on the front). As a result, when I click the link in the password recovery Email, OP comes back with "invalid code."
As an example, if I log into "http://www.ninechime.com/coonikaki/index.php" then load the page without the "www" on the front, it will show me as logged out. I can then log in again to "http://ninechime.com/coonikaki/index.php" and if I log out of "http://www.ninechime.com/coonikaki/index.php" I will still be logged into "http://ninechime.com/coonikaki/index.php"
I think this is a problem. It's certainly a peculiarity.
My own site was probably forbidding me from logging in because I am the site owner, and I was already logged in (albeit to an alternate URL).
Offline
ponyhome wrote:
My own site was probably forbidding me from logging in because I am the site owner, and I was already logged in (albeit to an alternate URL).
I just had a try on my own Kaki' and like you suggest
the login with www does not apply to the login without
www, but I can still login to the one without www no
problem, even if logged into the first URL as owner.
I can not find a combination that stops me logging in.
(actually handy for testing accounts/permissions, thanks!)
I get the same result in firefox & internet explorer,
the site makes a separate cookie for each URL type.
Have you tried clearing all cookies? (Maybe one is stuck)
Failing that I guess a mod rewrite in .htaccess could catch all traffic that
visits 'http://' and make sure it arrives at 'http://www.' or maybe there
would be something that can be done using the cookies section of the
'hacks.php' file in '\resource' folder?. (I've not looked much at that yet)
Offline
This is a domain issue, and the outcome depends on how the web browser accepts cookies. By default, a browser will only allow cookies to be used on the same domain, so if you precede a URL with "www", the browser will only use the cookie with that domain.
There are ways to fix this on your own oekaki by using a server redirect, or by editing the Wacintaki hacks file so cookies can be shared across across all sub domains on the same server. If you're visiting someone else's oekaki, there's nothing you can do, because if you strip off the "www", you are technically looking at a completely different web site with the same content.
If you are getting login issues, then you may have to clear your cookies. Wacintaki (unfortunately) uses 2 cookies, and they must be in sync.
Password recovery should work, though, as the link given in the e-mail is the one in the Wacintaki config file. It makes no difference which domain you were visiting.
Offline