Anyone good at Wordpress?

86JR · 2 Oct 2013 at 15:44

Just spent half an hour doing a little rant and published it on my new blog.

When I click "view post" it comes up with

Uh oh
Not Found

Oh, no! The page you requested could not be found. Perhaps searching will help...

And it comes up with the same message when I go up a level to /posts/ (or /p in my case).

Any ideas? My first post worked but this doesn't?

86JR · 2 Oct 2013 at 15:48

Ok I fixed it using default permalinks. I don't like the structure but at least it works.

Before I had /p/post_name (awesome for SEO)
now I have /p=11 (post number) (rubbish for SEO)

superleeds27 · 6 Oct 2013 at 20:13

twoblacklines said:
Ok I fixed it using default permalinks. I don't like the structure but at least it works.

Before I had /p/post_name (awesome for SEO)
now I have /p=11 (post number) (rubbish for SEO)

To have the /p/post_name you need to change your HTACCESS after editing the permalinks settings

unwashed potato! · 7 Oct 2013 at 08:46

is this locally run atm? i've never needed to play with htaccess on wordpress when run on server as it deals with this just fine.

Addicted · 7 Oct 2013 at 08:59

Fairly sure the answer is no said:
is this locally run atm? i've never needed to play with htaccess on wordpress when run on server as it deals with this just fine.

Same here, used to run around 100 WP sites, never had to change anything, sounds like a permissions issue in all honesty.

gord · 7 Oct 2013 at 10:01

Addicted said:
Same here, used to run around 100 WP sites, never had to change anything, sounds like a permissions issue in all honesty.

Wordpress should warn you when you change the permalinks structure whether it has permission to edit the htaccess or not. If it doesn't it will give you the code to copy and paste into the file yourself. Some environments don't let the application write into the file due to security.

86JR · 16 Oct 2013 at 16:58

It is on a TSOhost cloud server.