Recently attempted to move storage to Amazon S3 and it started off fine, until i got the following error:

Technical Details

TypeError: Illegal offset type in isset or empty (0)

#0 /var/www/vhosts/domain.com/httpdocs/system/File/File.php(651): IPS\File::getClass()

#1 /var/www/vhosts/domain.com/httpdocs/system/Output/Javascript/Javascript.php(766): IPS\File::get()

#2 /var/www/vhosts/domain.com/httpdocs/system/Dispatcher/Standard.php(103): IPS\Output\Javascript::getLanguageUrl()

#3 /var/www/vhosts/domain.com/httpdocs/system/Dispatcher/Front.php(871): IPS\Dispatcher\Standard::baseJs()

#4 /var/www/vhosts/domain.com/httpdocs/system/Dispatcher/Front.php(146): IPS\Dispatcher\Front::baseJs()

#5 /var/www/vhosts/domain.com/httpdocs/system/Dispatcher/Dispatcher.php(126): IPS\Dispatcher\Front->init()

#6 /var/www/vhosts/domain.com/httpdocs/index.php(16): IPS\Dispatcher::i()

#7 {main}

These details only show because you are logged in as an administrator. You can view them again later in the System Logs section of the AdminCP.

Código de error: EX0

Nothing is accessible now, not even the ACP to clear cache as it's instructed on the error message.

There was a similar issue to this in 2022 but doing what was suggested there (removing datastore folder, etc) did not resolve the issue.

The constants file looks like this if matters:

\define( 'REDIS_ENABLED', false );
\define( 'STORE_METHOD', 'Database' );
\define( 'STORE_CONFIG', '[]' );
\define( 'CACHE_METHOD', 'None' );
\define( 'CACHE_CONFIG', '[]' );

Any solutions or suggestions is greatly appreciated.

THank you in advance!

Your site appears to be accessible on this end. Have you since resolved this?

 

Your site appears to be accessible on this end. Have you since resolved this?

Of course, I had to reinstall and rebuild the data base and the site returned, now after rebuilding the data base, I have the following problem...

it happens everytime I want to see the reputation history in a profile however this happens only in two profiles, any idea how to fix this?,

The site is in the version 5.0.4

I would really appreciate your help.

Technical Details

OutOfRangeException: (0)

#0 /var/www/vhosts/domain.com/httpdocs/applications/core/modules/front/members/profile.php(805): IPS\Patterns\ActiveRecord::load()

#1 /var/www/vhosts/domain.com/httpdocs/system/Dispatcher/Controller.php(128): IPS\core\modules\front\members\profile->reputation()

#2 /var/www/vhosts/domain.com/httpdocs/applications/core/modules/front/members/profile.php(130): IPS\Dispatcher\Controller->execute()

#3 /var/www/vhosts/domain.com/httpdocs/system/Dispatcher/Dispatcher.php(169): IPS\core\modules\front\members\profile->execute()

#4 /var/www/vhosts/domain.com/httpdocs/index.php(16): IPS\Dispatcher->run()

#5 {main}

Edited March 23Mar 23 by Fernando S.

I would need to know which users in order to take a look. If you can provide these, we can see whats going on for you.

 

I would need to know which users in order to take a look. If you can provide these, we can see whats going on for you.

Of course, what exactly do you need of the profiles? Also, i was checking out the profiles from the admin panel and i saw this other problem.

 

reinstall and rebuild the data base

Before we go too far, could you please clarify what you mean here? From the error provided, it sounds like you may be missing data.

 

Before we go too far, could you please clarify what you mean here? From the error provided, it sounds like you may be missing data.

Yes, when I did the report of the first technical problem that is expossed in the main post of this same topic, the site went totally broken and unaccessible when a transferring of files to the Amazon S3 storage was in process, nothing was functional... even the ACP...

After that I tried to restore the site using the backup but when transferring once again the files to the S3 storage, the site went totally broken and unaccesible a second time.

Thats being said... the final solution that I found to deal with the problem of the files transferring to the S3 storage was by reinstalling the suite from scratch and then make a database rebuild.

Of course... stuff was missing but I was able to recover 90% of the posts... however some problems appeared in the profiles (the ones i came to report latelly) where there is a desync in the content counts due to the small lost of the rest of the posts.

Edited Tuesday at 08:43 PM4 days by Fernando S.

 

Thats being said... the final solution that I found to deal with the problem of the files transferring to the S3 storage was by reinstalling the suite from scratch and then make a database rebuild.

Of course... stuff was missing but I was able to recover 90% of the posts... however some problems appeared in the profiles (the ones i came to report latelly) where there is a desync in the content counts due to the small lost of the rest of the posts.

This segment sounds like the database rebuild was manual and may not be complete. Which would create problems that you're seeing now on sporadic profiles/users. If that is the case, the only way to resolve these issues would be restore completely back to where the data is either all missing or all together. Mismatched data restores will create problems.

 

This segment sounds like the database rebuild was manual and may not be complete. Which would create problems that you're seeing now on sporadic profiles/users. If that is the case, the only way to resolve these issues would be restore completely back to where the data is either all missing or all together. Mismatched data restores will create problems.

Thank you very much for your response, I'll try to complete the restoration since the data base is not thropwing me more information to recover.

I'll work on it tonight and i let you know the results.