danieltj

Okay not to worry. Try step 3 at this link and see if that works for you. You can keep the change I suggested in your .htaccess file or revert it. It doesn’t matter.

https://wordpress.stackexchange.com/a/20274

That should do the trick for you. Again, if not though come back and just ask. ??

No worries, do come back if there is anything else you need with your site.

Hm, is this for all posts and pages or just posts? Maybe opening up your .htaccess file in the root of your site and pasting the code here?

It could be to do with the fact that WordPress being in the main root of your file server directory will take all requests it can unless explicitly specified. So instead of just using the relative path, use an absolute path like so: –

ErrorDocument 404 https://www.mydomainname.com/error/new404.html

See if that works for you and come back if it doesn’t.

Really you need to asking your host because this can vary depending on their setup they have. The best thing to do though is make sure that the domain has all the name servers and DNS info pointing to the right place.

Then you need to change your domain settings in your sites Dashboard to the new domain. However this will bring your site down if the new test domain isn’t pointing to the right place.

But yep, ask your host. You shouldn’t have to do much but the things you’ll need to change will vary depending on who you are with. If you get stuck on the WordPress side though, come back and ask by all means. ??

Can you check what your permalinks are in the admin area? Go to the Dashboard > Settings > Permalinks. What are they set to there?

Can you try downloading a fresh package from the WooThemes site and copying the file across onto your server? It might have been an odd file that has glitched in an update or something.

Also, could you paste the line of code here that is causing the problem. If you paste line 38 between back ticks, then we can see what’s actually playing up.

No problem, was a pleasure to help out. Was a team effort for sure!

??

Not sure you’d be able to allow it per logged in user, but what you could do is prevent people from directly accessing it. So if I were to go to yourwebsite.com/wp-content/ I’d get a 403 forbidden error message.

To do this you can create a new file called .htaccess and simple write inside the file: –
deny from all

Save it and upload it to your /wp-content/ folder. It’ll still allow you to reference things from it so images will still show up. The only different is that directly going to anything in that folder will be blocked.

Do you have access to your site via FTP?

If you do, download the latest version of WordPress from the homepage of this site and upload that file (located within /wp-includes/functions.php) to that exact location on the server. What may have happened is when updating, WordPress may not have been able to overwrite the file and left the old one (maybe).

Try that and see if it works for you. If not then come back.

Haha no worries I’ll check back if a get an email about a new post to this topic and help if needed. It should be pretty easy and straight forward. Like I said, you can do it over and over again if you have a backup. Just delete and start again if anything goes wrong. Good luck! ??

No problem. Yes sorry for the confusion. You still create the new database and import your SQL export into it but you don’t need to change any values inside it. I only added that in in case you were using a new domain name.

So basically follow my instructions but disregard the following line, ignore it: –

Change the domain/url location in the options table of your new database that you crated during this process to match the domain you’ll be using to access the new site.

Oh in that case if the domain is staying the same then you don’t need to edit the database. Leave it as is. Unfortunately I’ll be busy with personal things but I’ll check back as regularly as I can and I’ll subscribe to the post for notifications if you post back so don’t worry! ??

It’s saying you have database tables missing from your database. Have you accessed your database directly and deleted anything or changed anything at all recently? Or even deleted a plugin from your website perhaps?

Check in your wp-content folder to see if there are any files there that are that big. The only thing that should be used for storage etc is that folder so it’s likely a plugin may be backing itself up but taking up a lot of room perhaps.

You’ll need to check it via your control panel or via FTP (root/wp-content/) and check each subfolder. WordPress by itself is tiny and wouldn’t normally cause that big of a backup.