Here we go again! After shifting my website to another host, some things just didn’t work right. I attempted to make a WordPress post but got a 403 File Permission error. Other than that, my entire WordPress website is running smoothly. I could view the post and pages, I could log into the dashboard and bring up the add post page.<\/p>\n
But when I attempted to preview or make a post, my server elicit a 403 File Permission error. Tried a few times but if it didn\u2019t work, it wouldn\u2019t work. I recall I had some similar issues some years back, giving my blog a quick searched showed a different error that I encountered, a 404 file not found error. That time it was far worse, because no post would show up!<\/p>\n
This time it is just not able to make any preview or post. Other than that, my WordPress was rather fine. There are two possible scenarios to this issue:<\/p>\n
1) The server folder permission was set incorrectly
\n2) Plugins causing conflict within WordPress<\/p>\n
Since I made a move of this WordPress installation to a new web hosting server, perhaps some folder permission was set incorrectly. There are two ways to look through the file or folder permission, one by using the FTP Filezilla software, or by logging in directly into your web host control panel file manager.<\/p>\n
Some of the folders to look through were:<\/p>\n
\n\/
\n|- index.php
\n|- wp-admin<\/b>
\n| `- wp-admin.css
\n|- wp-blog-header.php
\n|- wp-comments-post.php
\n|- wp-commentsrss2.php
\n|- wp-config.php
\n|- wp-content<\/b>
\n| |- cache
\n| |- plugins
\n| |- themes
\n| `- uploads
\n|- wp-cron.php
\n|- wp-includes<\/b>
\n`- xmlrpc.php\n<\/p><\/blockquote>\nI was also surprised to see some folder with permission levels of 777 when running through the folders. Having permission levels off 777 is akin of open your house door wide open allow any Tom, Dick or Harry into your living room. And since the internet has many unsavory characters you wouldn\u2019t want them into your house without a legitimate reason. It was best to revert those permission levels to 755 for some security reason. Going through the folders took a while it was quite a manual process. For security sake it has to be done.<\/p>\n
Next it was time to check the plugins. The right way to do this was to disable all the plugins and switch each one on and then make a preview or test post and see if the 403 File Permission error crop up. I was kind of tired from the process and took a little short cut and disabled the usual suspects. Made a preview, and hey, the preview worked.<\/p>\n
So it was a plugin issue, so now it was time to switch on each plugin one by one and make preview post to check it was working. Strangest thing was, I switched on every plugin that I switched off earlier and there was no issue at all!<\/p>\n
Perhaps the plugins need to be switch off then on again to reset its parameters after changing web host. But this was just a guess. As long as it works and no more pesky 403 file permission error when making a WordPress post, I don\u2019t have to find out the reason for this misbehaving plugins.<\/p>\n","protected":false},"excerpt":{"rendered":"
Here we go again! After shifting my website to another host, some things just didn’t work right. I attempted to make a WordPress post but got a 403 File Permission error. Other than that, my entire WordPress website is running smoothly. I could view the post and pages, I could log into the dashboard and …<\/p>\n