gtmotor,
Which Permalink structure do you want to use? (I read in your post that it fails with any other than the default. But for troubleshooting, which one is your preferred one?)
Would you post a link to the website with the error message in the upper left corner, and/or would you post a copy of the error message text that is appearing on the screen?
Which (if any) of the ideas on this page do you think might be relevant? http://codex.wordpress.org/Using_Permalinks
Regards,
Morgan
It only display ‘error’ text. the rest is white blank page.
Well, my preferred one would be “Post Name” permalink.
Any solution?
Thank you, mjassen.
On my installation, turning on the “Post name” permalinks choice also causes the posts to not be viewable — in my case causes the whole page to become an 404 error message.
I’m talking about my test on my site just so there is a comparison of what happens on another site.
Some more results of testing on my site:
On the “Permalink Settings” portion of the dashboard, when I choose the “Post Name” radio button is and click the “Save Changes” button, then appears at the top of the “Permalink Settings” page, highlighted in yellow, the words: “You should update your .htaccess now”. And also at this time, at the bottom of the “Permalink Settings” page, appears a message telling some more details how to update my .htaccess page.
So my further questions:
Do you get this same “… .htaccess …” related messages on your “Permalink Settings” page, at the moment when you change the permalink settings to “Post Name” and click the “Save Changes” button?
What do you see when at that moment when clicking on the “Save Changes” button?
If you have write permission switched off for htaccess then you need to allow write access (using the “tweaks” tab) then change your permalinks then disable write access again – saves you having to manually update your htaccess.
Despite that, I also get this “error” business due to links.
Seems my links are being rewritten from having a # to %23 and so i have loads of 404s for myurl.com/%23 and eventually users get blocked then everyone gets blocked.
I can’t determine which plugin or how this happens i only know it’s this plugin blocking things and it happens every few weeks to me. Anyone else keep getting this error message?
BigElsk, what you suggested is working (enable-disable write access). Now I can use the permalink again. Thank You for your support.
Mjassen, you might want to try BigElsk’s advice.
Turned out its now giving “error” page again when clicking on the link using permalink.
Any other suggestions?
Thank You.
In the dashboard, in the permalinks settings, what messages appear on the page when the radio button is toggled from “Default” to “Post Name” and the “Save Changes” button is clicked?
Does this message appear at the top of the page at that time?:
You should update your .htaccess now.
Do these two messages then appear at the bottom of the page at that time?:
If your .htaccess file were writable, we could do this automatically, but it isn’t so these are the mod_rewrite rules you should have in your .htaccess file. Click in the field and press CTRL + a to select all.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /html/mopress/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /html/mopress/index.php [L]
</IfModule>
Or if not, what messages do appear at that time?
@mjassen If you allow /htaccess and wp-config.php write access you don’t get a message when you change permalinks because WP can update .htaccess for you.
I had to switch off 404 detection to get around this “error” because the client was pulling his hair out (and almost mine too). The issue was that somehow, the # (back to top) links on my menu bar are being received on the server as myurl.com/%23 and hence it throws a 404. Too many 404’s and people get blocked and see the “error” – I switched off 404 detection (unwillingly) and haven’t had the problem since (fingers crossed).
Would like to actually fix this though so i can use the 404 detection feature…
Hope that helps!
