Follow SMF on Twitter.
Started by snadge, April 12, 2017, 07:26:01 AM
Quote from: Kindred on May 01, 2017, 10:21:36 PMI see the FAQ on how to load a fresh set of files
QuoteThe Repair Settings Tool (repair_settings.php) can be used to repair some of the most crucial settings on your forum, such as database information, file paths, and URLs. The tool can be used to repair an SMF installation sufficiently enough so that an administrator can then log in and fix any other problems.
QuoteIt looks like an attempt to put the blame on us however I can confirm that we do not have any reported issues like that on the server. Additionally, the core dumps as mentioned earlier are not created from the server itself. I do understand the situation you are going back and forth. What you are willing to do seems like a good plan. Usually every CMS saves the posts, users and every information like that in the database and not in the website's files. What you are aiming to do sounds like it will pinpoint the issue and it will help you solve them.Kind regards,
Quote from: Illori on May 02, 2017, 04:13:50 PMthe person that replied to you is a total and complete idiot. a core dump is created from the server there is no way for the SMF to create one. you can even google it to learn more. your host is a moron and i would be looking for a new host and leave them ASAP.
Quote from: Arantor on May 03, 2017, 07:14:57 AMThey don't think PHP core dumping is a problem? Wut.
Quote from: snadge on May 03, 2017, 07:05:42 AMMy last thing to try is to back up the forum in softaculous, reset...wait...see if core dumps appear...if so then restore and move hosts if they dont fix the issue, and lose posts made whilst used after reset...which is no biggy as I only have a couple of regular users...at 90% of the time there are only ME logged in with about 2-5 guests viewing the forum...?
QuoteCritical Error!Cannot connect to the database server with the supplied data.If you are not sure about what to type in, please contact your host.Access denied for user '***'@'localhost' (using password: YES)