Paul

Try re-updating your permalinks and make sure you have .htaccess set and that there are WordPress inserted rules.

Yes… at least that’s how I do it. Check this link if that’s how you want to do it.

Yeah, you’ll have to check with your host.

It’s a WordPress bug. You can try intalling the hotfix plugin to temporarily address the issue until it’s fixed in the next WordPress core release.

Oh yeah, re-updating Permalink might also do the trick.

Because your permalink looks okay, just that the server can’t find or doesn’t know how to find the page it suppose to go to. Check if your root folder have a .htaccess file via FTP or if your using cPanel’s File Manager, open your domain’s folder and make sure that the “Show hidden files” option is checked. Find the file within the folder, if it’s there, open it and check if it has an entry of something like…

# 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>

# END WordPress

You are right. Something will go wrong.
It would be much safer to separate the database of the live site from the testing site.

Highly likely if you didn’t do anything on the WordPress site before it happened.

Try deactivating the plugin that may have to do with post/page editing. Update your post and check. If the post gets updated, then you have your culprit. If not, try deactivating other plugins (one by one) and try updating your post again.

It seems to be a .htaccess issue. Check that first.

I don’t think there’s a whitespace in %post name%. It should be %postname%. Try removing the space. As it will spit out Bad Request or Not found error.

1. Make a subdomain of your main domain.
2. Export database of live site and save it.
3. Create a new database and database user.
4. Restore/Import the backup/exported database sql file to the newly created database.
5. Change all URL reference to your live site to the new subdomain URL by sql query (check this link on how to do that).
6. Copy (not Move) over the files from your live site to your subdomain folder.
7. Edit the wp-config.php, replace DB_NAME, DB_USER, DB_PASSWORD (maybe also your Authentication Unique Keys). Then save the file.
8. Visit your subdomain’s URL and finish the WordPress installation. (Create admin user, site name, etc.)
9. Login to admin panel, go to Settings > Privacy and tick “I would like to block search engines, but allow normal visitors” radio button. If you want, you can also add robots.txt in the root folder disallowing all spiders on your subdomain folder.
10. Done! That is, if I haven’t missed a step. Lol.

WordPress automatically changes the .htaccess when you update your permalinks. In case it cannot, you will have to check it with your host. Usually the dot files (like .htaccess) may be found in the root folder. If you’re using cPanel, tick the ‘Show hidden files’ checkbox before opening the domain’s folder in File Manager.

If your theme supports WP Menus you can check the docs on WP Nav Menus. Otherwise, you will have to code this in your theme or functions file.

Your p tag’s text is wrapped in a span with inline style font-size: small; remove that first as it will override your styles from an external file. Either check you theme how this is generated or perhaps a plugin you might have installed.