[[Template core/global/global/includeCSS is throwing an error. This theme may be out of date.

[AlexWebsites]

I can't seem to figure this out and the entire site is offline. I was in the middle of an S3 move of theme resources back to to the server and its been hanging on a move in progress for two days. I checked the cron job and ran the task manually twice, then this error. 

I tried to set into recovery mode and also permission set via constants.php file. I use redis and my datastore folder is empty. I've checked the database and no issues.

Access updated

[Jim M]

As you’re missing files, that would be the first thing you need to resolve. Is the queue task running and taking a while to complete or are you getting an error?

[AlexWebsites]

I just downloaded all from S3 and uploaded to /uploads.

This is the only thing that was moving:

Is there a way to flush cache or change constants.php?

admin panel showing me:

[[Template core/admin/global/globalTemplate is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

 

[AlexWebsites]

30 minutes ago, Jim M said:

As you’re missing files, that would be the first thing you need to resolve. Is the queue task running and taking a while to complete or are you getting an error?

I can't even get into the ACP anymore. Files are there on the server and S3. Maybe something in the database not synching?

[Adlago]

18 minutes ago, AlexWebsites said:

I can't even get into the ACP anymore. Files are there on the server and S3. Maybe something in the database not synching?

Can you restore the previous contents of the uploads folder?

[AlexWebsites]

4 minutes ago, Adlago said:

Can you restore the previous contents of the uploads folder?

I restored everything from S3 to the uploads folder, the rest was there. I suppose I could from a backup but is there something in that folder that would cause this? I think this is a path/cache issue that hasn’t completed.

Probably something in the database.

I'm looking at the database and the core_cache table has (not sure if normal):

Edited April 22 by AlexWebsites

[Adlago]

3 minutes ago, AlexWebsites said:

I restored everything from S3 to the uploads folder, the rest was there. I suppose I could from a backup but is there something in that folder that would cause this? I think this is a path/cache issue that hasn’t completed.

Probably something in the database.

Before this action of yours, you had access to ACP, and issues with CSS templates only.

[AlexWebsites]

Just now, Adlago said:

Before this action of yours, you had access to ACP, and issues with CSS templates only.

Yes had access and no CSS issues. I was moving from S3 back to /uploads and felt like it was taking too long. I hit the task and then got these errors/theme issues.

[Adlago]

6 minutes ago, AlexWebsites said:

Yes had access and no CSS issues. I was moving from S3 back to /uploads and felt like it was taking too long. I hit the task and then got these errors/theme issues.

I had a similar issue when I used data storage with cookies-free domain - When I started the process of loading resources to the main domain, my site was stuck with no CSS...And a field for resources with a message that they are currently inactive.
Manually starting tasks did not help.
I think I re-started the data storage change process, and then the previous task completed and the site recovered.

[AlexWebsites]

I do see datastore regenerating

[Jim M]

Would recommend disabling Redis for testing purposes as it looks like you have template cache enabled. Would then ensure that all your folders are correctly writable to ensure everything is able to write/delete/regenerate.

[AlexWebsites]

What's the best way to disable redis in contstants.php? Is it just set to false? This is what I have now:

<?php

\define( 'LONG_REQUEST_TIMEOUT', 60 );

\define( 'REDIS_ENABLED', true );
\define( 'STORE_METHOD', 'Redis' );
\define( 'STORE_CONFIG', '[]' );
\define( 'CACHE_METHOD', 'Redis' );
\define( 'REDIS_CONFIG', '{"server":"127.0.0.1","port":6379,"password":""}' );
\define( 'SUITE_UNIQUE_KEY', '########' );
\define( 'IPS_FOLDER_PERMISSION', '0777' );
\define( 'FOLDER_PERMISSION_NO_WRITE', '0755' );
\define( 'IPS_FILE_PERMISSION', '0666' );
\define( 'FILE_PERMISSION_NO_WRITE', '0644' );

 

[Jim M]

You can just comment the lines out or copy/paste them somewhere else. The lines being:

\define( 'REDIS_ENABLED', true );
\define( 'STORE_METHOD', 'Redis' );
\define( 'STORE_CONFIG', '[]' );
\define( 'CACHE_METHOD', 'Redis' );
\define( 'REDIS_CONFIG', '{"server":"127.0.0.1","port":6379,"password":""}' );
\define( 'SUITE_UNIQUE_KEY', '########' );

 

[Adlago]

32 minutes ago, AlexWebsites said:

What's the best way to disable redis in contstants.php? Is it just set to false? This is what I have now:

<?php

\define( 'LONG_REQUEST_TIMEOUT', 60 );

\define( 'REDIS_ENABLED', true );
\define( 'STORE_METHOD', 'Redis' );
\define( 'STORE_CONFIG', '[]' );
\define( 'CACHE_METHOD', 'Redis' );
\define( 'REDIS_CONFIG', '{"server":"127.0.0.1","port":6379,"password":""}' );
\define( 'SUITE_UNIQUE_KEY', '########' );
\define( 'IPS_FOLDER_PERMISSION', '0777' );
\define( 'FOLDER_PERMISSION_NO_WRITE', '0755' );
\define( 'IPS_FILE_PERMISSION', '0666' );
\define( 'FILE_PERMISSION_NO_WRITE', '0644' );

 

Try this

<?php

\define( 'LONG_REQUEST_TIMEOUT', 60 );

\define( 'REDIS_ENABLED', true );
\define( 'STORE_METHOD', 'FileSystem' );
\define( 'STORE_CONFIG', '{"path":"/home/your account/public_html/datastore"}' );
\define( 'CACHE_METHOD', 'None' );
\define( 'CACHE_CONFIG', '[]' );
\define( 'SUITE_UNIQUE_KEY', '########' );
\define( 'IPS_FOLDER_PERMISSION', '0777' );
\define( 'FOLDER_PERMISSION_NO_WRITE', '0755' );
\define( 'IPS_FILE_PERMISSION', '0666' );
\define( 'FILE_PERMISSION_NO_WRITE', '0644' );

 

[AlexWebsites]

1 hour ago, Adlago said:

Try this

<?php

\define( 'LONG_REQUEST_TIMEOUT', 60 );

\define( 'REDIS_ENABLED', true );
\define( 'STORE_METHOD', 'FileSystem' );
\define( 'STORE_CONFIG', '{"path":"/home/your account/public_html/datastore"}' );
\define( 'CACHE_METHOD', 'None' );
\define( 'CACHE_CONFIG', '[]' );
\define( 'SUITE_UNIQUE_KEY', '########' );
\define( 'IPS_FOLDER_PERMISSION', '0777' );
\define( 'FOLDER_PERMISSION_NO_WRITE', '0755' );
\define( 'IPS_FILE_PERMISSION', '0666' );
\define( 'FILE_PERMISSION_NO_WRITE', '0644' );

 

Did not work. 😔

[Jim M]

I've moved this to a ticket so we can look further into this to see what we can do for you here. Please watch your email for further correspondence.

[AlexWebsites]

I imported a dump of the database into a new database to test. I removed the constants.php. The site came up. I added redis and downloaded a fresh copy of constants.php. I connected and the site went haywire again. I deleted everything in datastore and it came back up.

I now connected the old database with the new constants file (redis on) and the site is up and running.

We'll see how it goes. I manually moved from S3. 

I must have done something by running the cron to fast...