Good call!
Sorry we couldn’t help you get that one going though – I have no idea at all what the problem might be, unless there’s something really odd about the way they setup their hosting accounts.
I had the same problem in my personal blog and i had to go back to 01-02-2005 version which works.
The latest version doesnt work.
Thanks for the opportunity.
I also have the referrer problem. I tried all possible suggestions I’ve found about firewalls, anti-virus, and browser settings. ‘info.php’ example above shows referrers are not being blocked. I have not been able to activate any plugins. My setup is: Win2K, Apache 2.0.52, PHP 5.0.3, MySQL 4.1.8, WP 1.2.2. I also tried the hacks modifying the ‘check_admin_referrer’ function to no avail. Help.
and you’ve renamed the .htaccess file?
This is going to come off as being snippy, but I no longer care because I’ve had enough.
I’ve tried everything in this thread. No of it works. I don’t know what the problem is, but it is NOT the host. This stuff used to work, why not now? I know that referers IS WORKING because I checked using the info.php trick. The referers came back just fine on that.
Conclusion: it isn’ the host. It isn’t my firewall. It isn’t my browser. The only thing left is WP. Not to mention that everytime I hit the website the siteurl kept getting reset back to http (not even a colon) despite me a) trying to reset it in the admin area and b) resetting it in phpMyAdmin.
I have tried repeatedly to get some help, but … oh what’s the use…….
In the meantime it’s no longer any fun and I’ve taken it all offline. Maybe I’ll come back, but there’s a lot that needs to be done first.
So long and thanks for all the fish.
Tg
TG, the .htaccess file was causing that exact problem for someone else – have you tried renaming it or deleting it to get it out of the loop, *then* fixing the siteurl setting in phpMyAdmin before trying WP again?
Pah! I must be a bloomin idiot…. I could have sworn I said “I’ve tried everything in this thread.”
Oh, wait I did.
Yeees… and still it doesnt’ take. But it’s all OK, I’ve “corrected” the issue by clearing out the entire directory. I no longer have the problem.
And in case anyone cares: http://mosquito.wordpress.org/view.php?id=678
http://mosquito.wordpress.org/view.php?id=677
irritatingly yours,
Tg
Sarcasm is an appealing trait in a person.
The reason I was double-checking (particularly the part about hitting phpMyAdmin after renaming the htaccess file before going back into WP) is because that exact problem (and I do mean *exact*) has been solved twice now, and nowhere at all (until just now) did you mention anything about doing it. You mentioned doing “everything”, but you also mention every other suggested fix – except that one.
Good luck.
“Sarcasm is an appealing trait in a person.” — first, I’m not a person, I’m a gnome, secondly apparently it’s the only way a gnome is going to get any kind of attention. I’m just glad I only had to resort to sarcasm. The next step would have been murder. Litteraly.
I’m sooo sorry, I didn’t mention everything I had tried. I figured that by saying I had tried everything in the thread, that, well, it meant I tried everything.
OK, so here goes:
delete/rename .htacces – check
reset using phpMyAdmin – check
deleted directories & reloaded them- check
deleted config file – check
verified referers work using info.php – check
disabled firewall – check
checked FF referers setting – check
I’m left with the same two options jose was at at the top:
a- change to other weblog
b- change my provider host.
But I’ll add c to the list.
c- dump bloggin all together.
I’ll take door number three please.
And luck has nothing to do with it.
Tg
Moderator
James Huff
(@macmanx)
Volunteer Moderator
How about doors #4 and #5, which are also part of “everything” in this thread?
Door #4: Access your site from someone else’s computer (a computer at work, perhaps). Do you see the errors?
Door #5: Install a fresh copy of WP (do not overwrite your current installation, make a separate installation). Can you recreate the errors?
Well, I’m sorry you don’t have the patience to keep trying. You say it’s something that started happening out of the blue, and we already know that having http as the value for siteurl causes the problem, we just have to figure out why WP is resetting it on you. And if you’ve been able to duplicate the error at every machine you’ve tried, it’s obviously a hosting issue. Whether whatever they changed exposes an actual bug in WP or not, it is a reversible situation – somehow.
And without someone experiencing the potential bug (you, but not anymore), how do you expect it to be fixed? Maybe Jose’s problem is caused by the exact same thing yours is (he’s looking for a different host now, as far as I know), and the same fix (when it’s found) will work for you.
Anyways, have a better day tomorrow.
oh, right of course *it must* be a host issuie because it certanly *couldn’t* be a coding issue. Mea culpa. I have the patience to try things I HAVE BEEN TRYING to get some help. Her, and on IRC. No one would. Out of frustration I decided to toss in the towel until WP is ready.
macmanx – I tried it from work too… still no good. and for a fresh install… that’s exactly what it was… no wait, that’s not 100% true… it was a fresh Jan 3 nightly install upgraded to Jan 8 — the Jan 3 worked just fine, it’s the Jan 8 one that stopped working. Hence my assertion that it is a WP code issue, and how it came to “suddenly” stop working.
You’ve got me thinking now though……
grrrr. thought you had something there for a sec macmanx. I grabbed the latest nightly (Jan 13) and uploaded it. Still same problem. Sigh…..
Tg
Moderator
James Huff
(@macmanx)
Volunteer Moderator
And you installed Jan 13 fresh? You don’t entirely make that clear. My best guess would be that it came from upgrading.
You guys, last time I had this problem, it was because of the faulty wp-login.php file. It would keep resetting the url to http: so when you try to activate a plugin or do anything else that requires sending referrer it wouldn’t work. I simply fixed this problem by restoring the URL with phpMyAdmin like Rust mentioned above and then commenting out these lines in wp-login.php:
// If someone has moved WordPress let's try to detect it
//if ( dirname('http://' . $_SERVER['HTTP_HOST'] . $_SERVER['PHP_SELF']) != get_settings('siteurl') )
// update_option('siteurl', dirname('http://' . $_SERVER['HTTP_HOST'] . $_SERVER['PHP_SELF']) );
That should do the magic! 🙂
