Why does my IP get blocked by the server?
The blocking occurs by the servers firewall when there are too many guesses at a login in a certain period of time for ftp, cpanel and webmail.
If you don't recall guessing at logins, then it can be caused by two things:
- You have an email program that has the wrong login credentials. Some email programs will automatically retry logging in when it fails to connect so that can trigger the firewall.
- You have a virus on your computer that is attempting to login. If none of the above are the reason for the block, then you should run a virus scan on any computer that can connect to your site from the given IP.
How do I fix the following error:
"Warning: session_start(): Cannot send session cache limiter - headers already sent"
The session start error usually means that an extra character (usually a space) has been added at the beginning or end of a file. If it is at the beginning, it will be easy to find since the first character should always be <. If it is at the end, you will need to move your cursor to the very end of the file and backspace until you reach the > character. The difficult part in fixing this problem is in finding the correct file. Always start with the last one you edited, the one in the url or the one mentioned in the error. Those are the most likely.
Page displays unexpected T_STRING
Php uses apostophes ( ' ) as control characters. If it encounters one where it shouldn't be, an error is generted. When writing text for a page, many people use contractions like what's instead of what is. The apostrophe in what's will cause this failure since the php code wasn't expecting to find it there. To get around this, add a backward slash (\) before the apostrophe so that it is what\'s. The file the error is in and the line number it can be found at is given in the error. It will be something like:
Page displays unexpected T_STRING in /home/some path/some_file.php on line X,
meaning, in this example, the error is in some_file.php at line X.
Why do my secure pages display a message that states, "This page contains both secure and nonsecure items?"
Secure and non-secure content, or mixed content, means that a webpage is trying to display elements using both secure (HTTPS/SSL) and non-secure (HTTP) web server connections. This often happens with online stores or financial sites that display images, banners, or scripts that are coming from a server that is not secured.
The nonsecure link that is causing the problem will have to be found and either removed or edited so that it works with secure pages.
In 2015, Google started a push to get all sites to use ssll for the whole site. Since that time, they have greatly increased their efforts and this type of error is seen more and more. The best solution is to convert the shop to run in full-ssl-mode. For newer shops, this is just a matter of changing the configure files. But for older shops, additional code changes may be needed since they were not designed to run this way.
