gdawkins

If you’re on a Linux server you won’t want 777 permissions since Apache reads that as a security flaw. 644 permissions will be fine. The RewriteRule should be fine as long as this .htaccess file is in your artists folder (along with your wordpress install).

At this point it’ll be hard to pinpoint the issue without going through some troubleshooting steps which is a lot easier with access to the actual server. Perhaps someone else here could help you but I’d suggest seeking professional help so that you can give full access to the server to someone who works with these problems and knows how to troubleshoot them. For example, a problem like this could easily be solved within an hour with access to the server.

Yes, he did switch it on and the permalinks were reading as https://julianbensonmanagement.com/artists/PAGENAME and giving 404’s, which is why he went back to the default permalinks for now.

I think the lack of the .htaccess file may do the trick though so lets see how he comes out after that.

@pixelpie
Just remember to change your permalinks back to the custom structure you were trying to use so we can test it again after you’ve added the .htaccess file.

No, default as in the kind of .htaccess file a default install of wordpress would have.

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

@ipstenu
He hasn’t been using the default permalinks, he just switched to them, he’s trying to use a custom permalink structure that doesn’t seem to be working.

/%category%/%postname%/

Is the one he wants.

@pixelpie
Go ahead and create a default .htaccess file for your /artist directory if you’re missing one.

There should be a .htaccess file in the /artists directory.

However, I think the problem is the lack of a / on the end of the URL’s in the database. Try adding a / to the end and see if that helps.

Ok, which URL’s do you have in your database?

Can you please copy/paste your .htaccess code here.

Yes, but what is your domain name so that I can take a look at the site?

What’s the new domain name with the 404 errors on it?

Have you logged into your admin section and clicked “Save” for your permalink structure?

The full URL to your current wordpress blog:

For example: https://example.com/blog

Yes, in your wp_options table you’ll need to update your “SiteURL” row on page 1 and your “Home” row on page 2. You’d usually use phpMyAdmin to do so.

I forgot to mention, this is just for cases where you’ve changed your domain name or directory structure of the wordpress install. If you’re using the same domain and didn’t change directories then you won’t need to worry about this step.

Have you logged into your admin section and clicked “Save” for your permalink structure? Also, you can double check that you have the right information in your .htaccess file, a default wordpress .htaccess should look like:

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

Don’t forget to update the two entries in your database’s wp_options table as well.

Hey Ipstenu,

What if I want to automatically rebuild them in the database?

After uploading the database to the new server the permalink_structure is correct:
/%year%/%monthnum%/%day%/%postname%/

That part doesn’t change, so what is it that actually changes when the “Save” button is clicked in the admin section and where can I manually update those in the database so that I don’t have to login to the admin section to do it?

I appreciate the help,

Gary

You can’t (by default at least) map the addon domain to a chosen folder in Plesk unfortunately.

Awesome ipstenu,

Thanks for the support. Looks like I’ve got some reading to do.

Thanks again!