finddavidr
Member
Posted 1 year ago #
Hey guys,
I've recently started a new site but am having problems with the permalinks.
When I change it to month/year/example-post I get 31/12 with no words in the url.
I can get all sorts of variations, but as soon as I try to include %postname%, I only get the %post_id%.
All I want is to have my post urls read site.com/%post_id%/%postname%/.
Thanks in advance for the help!
webdevsonline
Member
Posted 1 year ago #
/%post_id%/%postname%/ works perfectly on my relatively vanilla test wordpress, I get /number/post-name/ coming up fine.
Do you have any plugins which effect your permalinks? such as wp-ecommerce?
Is your htaccess file writeable + set up?
finddavidr
Member
Posted 1 year ago #
I only have one plugin installed so far which I doubt would be clashing with the coding.
.htaccess file is writeable and set up so I don't know what else it could be.
Have you tried:
- deactivating all plugins to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s).
- switching to the Twenty Eleven theme to rule out any theme-specific problems.
- resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.
finddavidr
Member
Posted 1 year ago #
Just tried turning off all plugins and changing the theme but none of that's causing the problem. I keep getting site.com/31/31 for the test post url.
/%post_id%/%postname%/ works perfectly on my relatively vanilla test wordpress, I get /number/post-name/ coming up fine.
Ditto. I cannot replicate the problem.
finddavidr
Member
Posted 1 year ago #
Thanks for your help anyway Esmi.
I've tried rewriting the .htaccess again and it's not working. I can get absolutely any permalink I want with the sole exception being %postname%. Is there anything I can do to find out why this isn't working?
Or better yet, has anyone got a quick fix for this?
Thanks
webdevsonline
Member
Posted 1 year ago #
Try testing on another wordpress on something like WAMP - if you're currently testing live, maybe its a host issue?