ce_kevinw

Hi allochtonta,

I’m not familiar with the 503.3, exceeded limit error. It sounds like it may be an error message specifically for Hostgator.

If you haven’t yet looked at their documentation, be sure to start here:
https://support.hostgator.com/articles/specialized-help/technical/wordpress/how-to-install-wordpress

If you’ve been using that guide and getting the error, it may be time to contact Hostgator support. I’ve Googled the 503.3 exceeded limit error, and there really isn’t much out there on the issue.

Hi dgthompson24,

If you’re getting a blank page on a php script, most likely the php script is having a problem and generating an error. Your current setup is not showing any error messages. This is good so that your users don’t see any errors, but is bad when you want to troubleshoot the issue. Seeing the error message is your next step in debugging this issue. To see the error, you can either review the error_log file in the php script’s directory, or, enable display_errors in your php.ini file.

A blank page at localhost/website/blog could also be a Directory Index issue. What happens if you visit localhost/website/blog/index.php?

Any further details you can provide will be helpful, thanks!

Hi platmack,

We could speculate on where your files need to go, and what files/folders (such as traffic.php), but for the best solution it may be time to contact your host. They can give you a solid answer on where your files need to go, if you need to setup a redirect, etc.

This article may help as well:

Hi LTDV,

I’ve seen .htaccess files hacked quite a bit, and I feel confident in resolving these issues.

Can you post you .htaccess file so we can look at the code?

Hi compustrat. My intuition was off. If you’ve got several other sites running on your local machine, then it sounds like you know where files need to be uploaded to : )

Good luck, let us know how it goes!

Hi kaspr,

Glad to see that you’ve been able to narrow it down to WP-POSTRATINGS. At this point, you would need to find out what exactly in WP-POSTRATINGS is causing the problem. That is going to be a lot easier said than done. Contacting the developer of the plugin may help, but I assume it is going to require getting knee deep into the code and analyzing what exactly it is doing and finding which function is causing the problem.

The plugin does have a forum, but it does not look to be too active any longer:
https://forums.lesterchan.net/index.php?board=17.0

I hope I didn’t cause any confusion.

Is it easier to install it into the same mySLQ database as my old one in a new folder?

Your MySQL database generally lives in a different part of the server compared with the rest of your website files. Your database is not in the files and folders that contain your WordPress application files, so when you reference your database and new folders, it is a little confusing.

For example, your WordPress files may be in:
/home/username/public_html
While your database may be in:
/var/lib/mysql/username_database

You don’t have ftp access to /var/lib/mysql/, so you can’t create folders within your MySQL database folder.

Yes, It is easier to start with a fresh database rather than share a database with another install of WordPress.

When you move WordPress to a new folder, you also have to modify a few of the files as well to let WordPress know it is in a new place. Read over this article for help moving your site to a different folder:

https://codex.www.ads-software.com/Moving_WordPress

Yes, any plugins you install are actually installed within your WordPress files on the server your website is on. The only thing saved on your computer is if you download a plugin or theme off the Internet, but once you upload it and install it onto your WordPress site, the file you downloaded is no longer needed. So you can access your WordPress from any computer and it will have any themes, plugins, etc. that you have installed onto your website.

Jan is right, with WordPress if you are not collecting any personal data the only page(s) you may need protected are the Admin pages. If you already have an SSL then it wouldn’t hurt to set up your site with it as it may make your visitors feel safer, but if no personal data such as credit cards, passwords, addresses, etc. are being shared then it isn’t really necessary.

Interesting, while other plugins can modify the .htaccess file, this is the default .htaccess:

# BEGIN WordPress

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

# END WordPress

The only difference is that yours has the top index.php rewrite which the default does not. I don’t know if that is what is causing it, but you may want to try commenting out that line (just put a # before it) to see if the first index RewriteRule is causing the issue. You can also try removing the .htaccess altogether, again by renaming it and not deleting it so can you easily re-apply it if the problem still persists.

Kevin

Hello,

While generally a 403 error is based off the permissions of the file or the .htaccess, if it is only from one computer then the files themselves are likely fine.

Check this page for ideas on how to resolve the issue on the computer: https://www.pcerrorsfix.com/fix-error-403 as it could be an issue with the registry or the host file on the computer.

Kevin

getting a WordPress is already installed message, I have changed the table prefix to wp1_ so it should be a blank space with no install, right?

The “WordPress is already installed” message may be pertaining to files already, not the WordPress database. Changing the table prefix is not going to affect the folder WordPress is installed at, so be sure to install WordPress in a clean folder.

I hope this helps!

kaspr, you have me stumped… On the blank page, if you view the page source, are you able to see anything after the title?

Hi kaspr. To confirm, you checked your error_logs and are not seeing anything in there?

If that is the case, then it may be something within the logic of the code. This is more difficult to troubleshoot. You may need to examine the code and do some testing. For example, at certain points in the script, echo variables to the screen and ensure they are what you’re expecting them to be.