Fatal error: Cannot declare class AIOS_Abstracted_Ids

Hi @grandya

It seems you have copied the website code from other place and still the .user.in or .htaccess file have reference to copied file aios-bootstrap.php and as per that it calls two time file from different path.

It is a recently identified issue and we tried to solve it. Please upload the zip as Add new plugin and replace it with existing AIOS plugin.

https://gofile.io/d/QNwe88

This fix is going to be in the next release.

Hi @hjogiupdraftplus

Thank you for providing the corrected version.
The error was resolved after activation.

However, an error occurred during the setup, and after checking in debug mode, the entire site became inoperable with the following message.

Fatal error: Cannot declare class AIOS_Abstracted_Ids, because the name is already in use in?/home/********/public_html/***.*****.***/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-abstract-ids.php?on line?11

Notice: Function is_embed was incorrectly called. Conditional query tags do not work before the query is executed. Before that, it always returns false. See ?Debugging WordPress for more information. (This message was added in version 3.1.0) in?/home/********/public_html/***.*****.***/wp-includes/functions.php?on line?5857

Notice: Function is_search was incorrectly called. The conditional query tag does not work before the query is executed. Before that, it always returns false. See ?Debugging WordPress for more information. (This message was added in version 3.1.0) in?/home/********/public_html/***.*****.***/wp-includes/functions.php?on line?5857

A critical error has occurred at this site.

Perhaps the unbootable error has been resolved, but it may remain without complete removal. Thank you again for your time and help.

As for the earlier matter, I no longer get the error. perhaps it is due to the cache.Thank you for your support! Thank you for your support. We look forward to working with you in the future.

I am having this same issue. Deleting the plugin and reinstalling did not fix the issue. Please advise.

I also having this issue now, same as @blairw deleting and reinstalling is not fixing the issue.

Update:
Fixed mine by correcting the file location on the user.ini file from the root folder.

• This reply was modified 1 year, 5 months ago by rapp.

Hi @blairw @anjorapp

Just deleting and reinstalling it do not solve issue, yes user.ini have old path when you copied and it from different location that file gets added also that is why it try redeclare the class.

Please upload the below zip file as Add new plugin and replace it with existing AIOS plugin.

https://www.dropbox.com/s/sljxpohn5870awn/all-in-one-wp-security-and-firewall.zip?dl=0

This fix is going to be in the next release.

This issue has been affecting my site. When I update my live site with the staging site (which has the latest plugin) I get this error message:

“Fatal error: Cannot declare class AIOS_Abstracted_Ids, because the name is already in use in [ ] /all-in-one-wp-security-and-firewall/classes/wp-security-abstract-ids.php on line 11”

Is there a new fix in the pipeline?

Hi @donmcleman

This issue is fixed in AIOS 5.2.0 There is no new fix for it.

So please cross-check again if you have a live site with an older version while you are updating from the staging site with the latest version files included also can be issue.

You have the staging and live site on the same hosting server and the staging site copied wp-config.php , user.ini, .htaccess file have still path of the staging site for aios-bootstrap.php file please cross check.

Regards

Thank you. I’m not sure how it works now but it works. Both sites did have the latest plugin. I downloaded a new copy of the plugin on the live site and then when I deployed the staging copy there was no problem. I also changed the file permissions on wp-config.php, which had been too low. I don’t know what the solution was, but it works now so thank you!

Hi @donmcleman

Glad to know It works now. As said AIOS 5.2.0 has solved this issue.

It might be one of the sites ( main or staging) has an older version than 5.2.0 which is the issue.

Regards