xvilar
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Cannot declare class WP_Automatic_Updater after 5.6 upgradeYes @macmanx … I’ve changed theme and I still see the error… I’ve to re-check it again because we have W3Total Cache and I don’t remember if I cleanup cachés before trying with default theme.
Thnx. Cheers
Forum: Fixing WordPress
In reply to: Cannot declare class WP_Automatic_Updater after 5.6 upgradeThanks @macmanx …. yes, like that. I was able to switch themes in dashboard, and also enbale or disable plugins… everything seems to be working fine but the Updates section… Dashboard -> Updates. Then in the screen you can see the ‘pending’ updates is where I get the error; only there:
“Fatal error: Cannot declare class WP_Automatic_Updater, because the name is already in use in .. wp-admin/includes/class-wp-upgrader.php on line 2773”
I’ll try HealthCheck plugin in order to take a look… but as told it seems the discontinued raw theme (Wave themes) should be the cause…
I’ll come back with findings on Health Check. Thanks!
Forum: Fixing WordPress
In reply to: Cannot declare class WP_Automatic_Updater after 5.6 upgradeI’ve tried manually resetting the plugins, and with noone activated, I get the same error.
I’ve also forced the default theme to activate, and I get the same error.
Despite this, I think it’s a theme mistake… the site uses Raw Theme from Wave themes (http://www.wave-themes.com/demo/raw/main/) and I think it has been discontinued (whole Wave themes ‘company’ seem to be ‘closed’)
¿? Thanks!
- This reply was modified 5 years, 4 months ago by xvilar.
Forum: Fixing WordPress
In reply to: Cannot declare class WP_Automatic_Updater after 5.6 upgradeThnx @macmanx we’ll try this… I’ll come back with the results. Cheers
Forum: Fixing WordPress
In reply to: Can’t See BackendThanks to Khahina… It was about a problem with the “db_version” in wp_options ddbb table. Here’s the explanation:
http://www.clickonf5.org/2247/solution-database-upgrade-required/
For Version 4.7, the database version (db_version in wp_options) changed to 38590, and the Trac revision was 39524.
I’ve updated a site from 4.6 to 4.7 and the db_version remained the old one (37965) so you have to change mannually the db_version to 38590
I think it’s a bug of the upgrade process. I hope ww.wp.xz.cn people solve it!
Thanks. Regards.
Forum: Fixing WordPress
In reply to: HTTP Error 500 triyng to access wp-admin after upgrade to 4.7!!Thanks Stapolin and Khahina… It was about the problem khahina told us: the db_version
For Version 4.7, the database version (db_version in wp_options) changed to 38590, and the Trac revision was 39524.
I’ve updated a site from 4.6 to 4.7 and the db_version remained the old one (37965) so you have to change mannually the db_version to 38590
I think it’s a bug of the upgrade process. I hope ww.wp.xz.cn people solve it!
Thanks. Regards.
Forum: Fixing WordPress
In reply to: HTTP Error 500 triyng to access wp-admin after upgrade to 4.7!!BTW front end is up and running ok
¿?
Forum: Fixing WordPress
In reply to: Can’t See BackendMe also!!! Error 500 after upgrade to 4.7
/wp-admin/upgrade.php?_wp_http_referer=%2Fwp-admin%2F
¿?¿
Thnx blupace! (I change pwd every 7 or 8 days 🙂 )
Cheers!
Thanks blupace, which anti-malware have you used? Thanks. Cheers.
thanks a lot!
Blupace I’m glad to hear you solved the prob… please could you tell us which other WP core files also changed? Thanks. Cheers!
It’s a kind of injection it’s done in the file wp-includes\nav-menu.php
So you’ve to take a look at that file and search for
“///istart” and “///iend”
and delete the content between both lines…
First of all do a copy of the file… just in case.
Take a look at:
http://www.xdude.com/malicious-code-istart-preg_replace-on-nav-menu-php-line-465/I don’t know how to mitigate this hacking completly… it happens each 6 or 7 days …
Cheers.
solved
Got it… an infected file 🙁 thanks to 1and1 people who help me! 🙂