Jim M

If this is a test site, I would presume you don't have traffic so this would be expected. Click around a bit on the front-end and tasks should run.

You would want to ask your hosting provider for assistance here with our backup if you attempted an upgrade of your live site. It is not recommended to upgrade live sites unless you are comfortable with errors that may come during a Beta phase.

The 403 is coming from your server. You would want to check your configuration. These seem like permission errors at the bottom. Please make sure that your MySQL user has full permissions. The top looks like you already tried to do an upgrade but it failed, did you restore at any point?

Glad you're seeing some progress. Please let us know where you end up 🙂

Is the new database you created _test? (left out the prefix for your privacy). If so, please check what database you restored to as it is empty. You will also want to check your conf_global.php file as the current one is connecting to your other database as well.

Did you delete your previous database used for version 5 before restoring your version 4 database? You don’t want to restore over that as there would still be remnants of version 5 left. You want to delete the old version 5 database or create a new database to restore to.

When restoring your database did you restore it over your version 5 database or dump the database and perform a restore? If the former, I would try the doing the latter as this states that the table already exists in the current state so the database can't create it.

Please feel free to check your download from the Client Area and let us know if the files are missing. They are not from my test licenses but of course, anything can happen 🙂 .

The init.php file is a source code file, so you'll want the most recent one from the Client Area. If it is still failing after upload, we will need the new error message involved. Appreciate the willingness to move forward. I do want to take a minute here to explain the errors Marc mentioned. Two issues were posted, one below is about missing files (access to code) and one about a missing database table. Class "IPS\core\modules\admin\moderation\" not found That means the software could not find the module (code) in question being referenced. This is typically because files were not fully uploaded, corrupted, are out of date, or your server does not have access. If there are more files on your server which are empty, like the init.php file, this may stem from your FTP client or something corrupting files on the server during upload or otherwise. --- The other below, is about missing a database table: IPS\Db\Exception: Table 'sitefolder_dev.core_theme_editor_settings' doesn't exist (1146) That database table should be there from the start. It is a version 5 database table so was created to run the software. Something beyond the software has either corrupted or deleted the database table. (note: we're not pointing fingers and saying you did it, we're just relaying the information here 🙂 . weird things happen with servers, we've seen and continue to see our fair share, just ask out Cloud team 😄 ). ---- Now, with the information provided from you, Marc opted to try and fix the first issue about the missing software files to see if that rendered any easier path forward with the database issue. You're more than welcome to ask questions before doing an action. We like for you to understand why an action is being performed. However, if you give us an error that a file is missing, we're going to want to have you upload all files again as not only does this resolve the issue 99% of the time (it also shouldn't make the issue worse), it also will hopefully prevent us from playing leapfrog with issues down the line. As if one file is missing/out of date, many could be as well. Hope that explains things a bit more.

While I agree and apologize that I could further explained the reason why I asked if the upgrade was completed (people tend to state they upgraded when in reality, they uploaded files, so I wanted to ensure the upgrader was ran and completed). I want to assure you that we do not post questions or statements without reason. Afterall, resolving your issue as quickly as possible is in both of our best interest 🙂 . Often, there are questions we need to ask to understand how you got there, try things to proceed, etc... This is all in the process of supporting you and I understand, it feels like treading water at times because it isn't resolving your issue; answering questions and crossing possible issues off the list, proceeds us to that end goal of resolution. I am sorry to hear that you feel you are being ignored, that is not our intention. While we understand you have an issue here, there are many steps to getting to resolve it and suggestions. However, as mentioned above, there are limitations to the beta program. With those, we need your help so we can help you. Answering our questions, trying the steps we ask, providing error messages, etc... This is all part of the support process 🙂 . The beta program also is limited in support, and this is a new major software (aka new problems to us) so while, I apologize, it may not be the most immediate resolution, we are indeed trying to assist you and learn about version 5 issues as we go. Thank you for providing these. Please check your init.php file in your installations root. It is empty. This is creating the problem. Please reupload this file.

You can obfuscate any sensitive information, give us a file location of the server error log on your FTP access, or post it in the notes area of the Client Area access details page if it's a 1 line error. I'm afraid, beta software is not yet fully supported so would not get fully escalated via normal means at this time. If the previous mentioned does not suit you, a restore back before this issue started should be done.

Please check your error logs. If it is PHP suppressing the error, we will need to know what it is.

If you have uploaded files you will want to try to re-try the upgrader. If you're getting errors we would need to know those errors. We cannot assist without further info. Keep in mind, as the software is still in beta that these things will happen and restoring and trying again is common. Please be respectful to those trying to assist you.

Did you run the upgrader?

Think there is confusion here as you have 2 issues in the topic: Related to your version 5 beta test site. Quoting someone here on our Community. My colleague's reply was related to #2. He was asking if there were any errors in your browser's console when attempting to quote. You can view this by clicking F12 -> Console. --- The quote above which I made of your Template error is related to version 5 Beta. You should see something related to this in ACP -> Support -> System Log.

Would recommend clearing your browser cache and disabling any extensions as I am using the same browser/version without issues here.

I cannot reproduce this. What browser?

The theme being an unmodified theme? Just wanted to verify

I forgot how unforgiving old school games were but give the scum of the world some time and they'll develop an aim bot for the spammer bots 😄

You will continue to be able to use version 4. We will make an announcement when we will require version 5. However, that is likely once version 4 is no longer supported and version 5 has matured. While I'm sure many clients will jump into version 5. We respect that some will want to wait for it to mature or have third party services they need updated, etc... With that said, we likely will have a cutoff period once version 4 is no longer supported as technology has to keep innovating and remaining secure 🙂 . When that is though, I don't think we have a date in mind as we are still in version 5 beta phase.

Blocks are cached when a user views it for the duration set. There is no background tasks updating data based on that timeframe.

I would encourage to post information about the slow down then rather than Google Pagespeed. What is causing it? If you're having MySQL slow downs due to queries, post the slow log as that is definable information our developers can ingest and see if there is an issue on our end 🙂 . As mentioned though, there is a lot involved on the server end. Ensure that your server is performing like a production instance to ensure your comparison of V4 to V5 is accurate. Also, ensure you're not making large changes, i.e. adding more blocks to a page or something similar which may (prior to caching) cause a performance hit. Ultimately, we want to help you and avoid scaring people with grand, vague statements. If there's an issue, let's work together to fix it 🙂 .

While the answer is "yes, performance is a factor of SEO", it is not THE sole factor. If you have horrible content but a performant page, you aren't going to rank higher. Performance is something to keep in mind and bring up when you're testing but I think the key thing is not get obsessed and bogged down on particular results. Especially, with a tool that is impacted by so many other things like Google Pagespeed. If you're also not testing in a production environment, these are considerations to also keep in mind as Pagespeed factors in items which are impacted by the server.

Did you just do the install or upgrade? If so, it is included then.

I am not estimating this task but as a project manager in another life, I used to tell my people when they say something was "not very difficult to add": "6 ten minute tasks keeps you an hour away from something meaningful. Time adds up." 🙂 Also, have to keep in mind it is not just the initial development, testing, and releasing but the after support as well.