Update Failed after changing Permalinks

Dashboard –> Settings –> Permalinks

Just use the custom permalink selector and click (toggle off) the ‘parts’ within the little buttons or blocks that you don’t want. Save!

It’s not real clear and my old eyes really can’t see that but mouse over one and click it. It will either add that item or take it away.

Sometimes Permalinks will get ‘stuck’ or confused also. If that happens to you then try setting them to plain, save, and then set them to what you really want. I’m real old school on some of this stuff and years ago I was taught that little trick… it’s still handy.

‘lo JNash,

yes, I’ve tried the ‘reset’ of stuck-permalinks you’ve described above. –to no avail.
I’ve also selected custom, and chosen the elements via buttons below. If they are set to anything but the default, I’m unable to add/edit pages.

here’s a Youtube video of a fresh install WP5.1.1 rolling straight into demo of add new page= success then fail after changing permalinks.

• This reply was modified 5 years, 8 months ago by grepzen.

Maybe I’m not looking at that right but you are adding a post the first time and a page the second. Right?

Would you mind trying that same exercise with a post this time? And then did you notice the index.php/ added to the custom URL? I must have glossed over that until I saw the video.

Maybe you might add that on and use those option buttons under custom itself instead of using the selector for post name only. See how that works.

I’m trying to find out how to rid the permalinks of the need for index.php/ in the URL but for now… any port in a storm.

• This reply was modified 5 years, 8 months ago by JNashHawkins.
• This reply was modified 5 years, 8 months ago by JNashHawkins.

‘lo JNash,

First, you! are a gawt damn genius!

I did try it again.
1) I was able to create new postes AND new pages w/ base/default/stock config.
2) After changing Permalink to Post Name, I was still UNABLE to create new posts, or pages.

so.. why are you so gawt damn’d amazing?
because after adding /index.php/%postname%/ to the permalinks, it all WORKED!

Seriously JNH, thank you for your mind, your time and your patience.

I still wana call this a bug, but you definitely nailed the work-a-round.

mad UPs to you Sir -Thank You

[RESOLVED]

[SYMPTOMS]
On default/stock config, unable to add/edit post and pages after changing permalink settings.

[RESOLUTION]
prepend desired permalink setting with “/index.php/”

What kind of funky stuff do you have in your .htaccess file?

here’s a new yt-video of the full run including fails to create new posts or pages.

here’s the bone-stock .htaccess created by WP:

# BEGIN WordPress                                                                                                                                                 │
<IfModule mod_rewrite.c>                                                                                                                                          │
RewriteEngine On                                                                                                                                                  │
RewriteBase /                                                                                                                                                     │
RewriteRule ^index\.php$ - [L]                                                                                                                                    │
RewriteCond %{REQUEST_FILENAME} !-f                                                                                                                               │
RewriteCond %{REQUEST_FILENAME} !-d                                                                                                                               │
RewriteRule . /index.php [L]                                                                                                                                      │
</IfModule> 

I’ve had the same issue, with the same fix working. Given the above stock .htaccess, how might I change the rewrite rules so I can drop the nasty index.php?

Those are the default rules. With that ruleset you should not need index.php in the first place.

The only reason I know of that requires index.php in the URL like that is running on a Microsoft server with IIS. I can’t think of a reason an Apache server wouldn’t work without it.

If those rewrite rules are there to strip the need for index.php in the url, perhaps this means the .htaccess isn’t be respected?

Just experienced this issue myself.

As per @dnlhoust my issue was that the ..html/.htaccess file was not being respected.

Fix:
Updated httpd.conf “AllowOverride None” -> “AllowOverride All”
restarted webserver