Wondering if this will always be free? See why free is better.
Started by TalonDOD, November 22, 2021, 01:47:12 PM
Quote from: Kindred on November 22, 2021, 05:22:25 PMclear your smf cache (delete all the data* files in the cache directory)
Quote from: Steve on November 23, 2021, 07:27:02 AMHow about Admin -> Maintenance -> Routine -> Empty the file cache ?Don't know if that will help.
Quote from: Kindred on November 23, 2021, 11:44:40 AMyou have DIFFERENT errors.1- to fix the session error. Change the cookie name. This will FORCE everyone to log in new and establish a new session. This should fix things for users who won't/can't/don't clear their browser cache2- You had an error with the cache file being corrupt. You deleted the cache files (all files starting with data in the cache directory). Has the corrupted cache file error re-occured since doing that?fix both those problems first. Those are easy to fix.3- you have a login problem that causes a white screen of death (a white screen with no text at all)THIS one is more complicated -- and you being on GoDaddy means that it's going to be even more difficult than it needs to be (note: GoDaddy sucks, plain and simple)However.... to start with. A WSOD is a SERVER SIDE error.if the system is even half-way configured correctly, the WSOD will result in an entry in the server error log that will indicate WHAT is causing the error. We can't debug too much more without that information.
Quote from: Kindred on November 23, 2021, 03:08:03 PMno, the WSOD will not reflect in the SMF error log, because php itself is crashing.You need to get the server error log. It's usually a file called errorlog. or error.log.If, for some bizarre reason, GoDaddy is NOT recording server errors, then you need to have them turn it on.That error in the SMF error log is something else entirely.
QuoteSetup PHP error loggingWhen troubleshooting PHP errors, you will want to review your PHP logs. If you don't have PHP logs to review, use the following process to set up logging:Note: For WordPress and Managed WordPress error logging please see Enable debugging to display errors in WordPress. You should always backup your site before making any changes to your site. Locate your PHP initialization file. Edit the file. (cPanel / Plesk / VPS) Place the following line in your initialization file: error_log = /path/to/your/webroot/php_error.log error_log is the PHP function that will tell the web server to output your logs to a new file. /path/to/your/webroot/php_error.log is the path to your new log. Make sure to replace /path/to/your/webroot with the actual path your hosting account uses. What is my absolute path? (cPanel / Plesk). Create the a file named php_error.log in the in the webroot of your hosting. Restart your PHP processes.(cPanel / Plesk).Next Steps: Review your php_error.log for error details. (cPanel / Plesk / VPS)More info For more information about PHP error logs, visit PHP.net.
Quote from: TalonDOD on November 25, 2021, 09:59:59 PMI think Godaddy is just jacked up.
Quote from: shadav on Yesterday at 07:26:24 AMlmfao what steve said unfortunately though, hostgator isn't much better either