the log in for WordPress on the site doesn’t work with WordPress’ main site
Let’s start with this. What exactly do you mean by “WordPress’ main site”?
this means that activating Askimet is impossible, as the Askimet log in requires the actual WordPress account, not the site login which isn’t recognised despite being WordPress
I’m not sure what you mean by an “actual WordPress account”. Furthermore, to get an Akismet API key, all you need to do is submit your email address and create a username and password, so whatever an “actual WordPress account” is, this should be no obstacle to activating Akismet.
I am confused by your post, but my guess is that you are confusing WordPress.com with WordPress.org, when in fact they are completely separate. A self-hosted WordPress.org site has nothing to do with WordPress.com unless you are using a package like Jetpack which ports WordPress.com functionality into WordPress.org installations.
I’ve been reading up since…. so I’m in the right place. http://www.wordpress.com is the main site, this is for the hosted WordPress. 😉 Yes, I’m confused.
I still can’t seem to activate Askimet without a WordPress login from the settings. Weird. I’ve found something re the customisation “session expired” login here – http://wordpress.org/support/topic/your-session-has-expired-please-log-in-again-ad-infinitum/page/2?replies=33
As a note I’ve just tried the solution above and it just makes the customise page grey with nothing previewed. Weird.
And now I’ve borked my website and I’ve no idea how… I only logged out!
I’ve been reading up since…. so I’m in the right place. http://www.wordpress.com is the main site, this is for the hosted WordPress. 😉 Yes, I’m confused.
A couple of important terminology points:
(1) WordPress.com is not the “main site”. It is the home of WordPress.com blogs. You do not have a WordPress.com blog so you should disregard that entirely.
(2) What you have is not a “hosted” WordPress blog, but a “self-hosted” WordPress blog. A “hosted” blog implies a WordPress.com blog, because you sign up for a ready-made installation that is “hosted” on the WordPress.com servers. A “self-hosted” blog is installed on a hosting account that you control.
As for Akismet: to get an API key, go here to sign up: provide your email address and pick a username and password. Once you get an API key, you insert that in the API key field at Plugins > Akismet.
1) Thanks. Got that now.
2) OK, great. Cheers.
Askimet, I’ll do that. If I could get my site running again. From out of what appears to be nowhere I’m getting a 403 Forbidden Error for the entire site. All I did was change the General Settings Site Address from http://www.bowendesign.com to http://bowendesign.com and back again, as per the solution to the main problem. Any ideas?
edit; ok, now this is confusing. Changing it to http://bowendesign.hosting5.idnet.net means I can see my site again, but http://www.bowendesign.com seems to be giving an error. Argh.
Argh, this is driving me nuts. Tried reinstalling, nothing. Tried deleting .htaccess, nothing. Looked at permissions, all seem fine. If anyone can help or suggest anything, please do.
edit – OK, strangely I can access http://www.bowendesign.com/?page_id=44 and other links apart from the home page. Links to the images now seem broken. Erk.
You can access the entire site?
Strange. Wonder if I’ve triggered some security setting as I can’t get anything than a 404 error on this computer.
Thanks for checking, btw. Much appreciated!
edit – my browser was redirecting me automatically. Duh. Thanks for checking. Put it down to tiredness.
I’ll keep this open as my preview issues are unresolved for now. If there’s any kind mods… erm… delete the 403 mess for my own sanity lol.
All of the pages I clicked on worked fine. Flushing your DNS on your computer might do the trick.
