#55240 closed defect (bug) (invalid)
Fatal Error: Cannot redeclare wp_render_duotone_filter_preset()
Reported by: | etilley | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | major | Version: | 5.9.1 |
Component: | Editor | Keywords: | |
Focuses: | Cc: |
Description
Fatal error: Cannot redeclare wp_render_duotone_filter_preset() (previously declared in /home/www/csq1.org/wp-includes/deprecated.php:4224) in /home/www/csq1.org/wp-includes/block-supports/duotone.php on line 393
I woke up to this error on my website that was running fine yesterday... see http://csq1.org
Troubleshooting steps:
- I renamed my plugin folder plugin.hold and tried to reset plugins by running plugin.php (per the instructions) – without success.
- I renamed by theme folder (and child)
The error remains the same.
I did not want to reset the plugins in the database (and potentialing losing my configurations) … that command is “option_value field to: a:0:{}”. Perhaps I should now, but …
I think the problem is with the 5.9.1 /wp-includes/block-supports/duotone.php file ?
So I am creating a bug report. I am running 5.9.1 on PHP 8.0 with 256M of memory. Website is csq1.org
Change History (10)
#3
follow-up:
↓ 5
@
3 years ago
For the moment I don't know if we need to fix this on Core or Gutenberg side (or both).
I think neither.
This sounds like a botched update.
wp_render_duotone_filter_preset
used to be in duotone.php
in 5.9.0, but was moved to deprecated.php
in 5.9.1
For some reason the duotone.php
file was not updated for you during the 5.9.1 update.
If there is a way for you to re-run the update (for example using WP-CLI) or to manually override that duotone.php
file, that should help fix the problem.
#4
@
3 years ago
Hello, @etilley. Thank you for reporting the issue.
I agree with @swissspidy. It looks like there was an issue during update.
#5
in reply to:
↑ 3
@
3 years ago
Replying to swissspidy:
For the moment I don't know if we need to fix this on Core or Gutenberg side (or both).
I think neither.
This sounds like a botched update.
wp_render_duotone_filter_preset
used to be induotone.php
in 5.9.0, but was moved todeprecated.php
in 5.9.1
For some reason the
duotone.php
file was not updated for you during the 5.9.1 update.
If there is a way for you to re-run the update (for example using WP-CLI) or to manually override that
duotone.php
file, that should help fix the problem.
I can upload new 5.9.1 files easily. Which file(s) did not get updated correctly?
I'm afraid that I don't understand what you mean by "override the duotone.php file" ?
#6
follow-up:
↓ 8
@
3 years ago
- Keywords needs-testing removed
I agree with both @Mamaduka and @swissspidy.
Doing a search of where the wp_render_duotone_filter_preset()
function is declared:
- In WP 5.9.1: it's
function
only appears in one place, i.e. in thewp-includes/deprecated.php
file. - In Gutenberg plugin: it does not exist.
The issue then is not in 5.9.1 or Gutenberg. Rather, the issue is an incomplete upgrade to 5.9.1.
@etilley I'd suggest reinstalling 5.9.1 to ensure all new files are present. Why? Since there's an incomplete installation of the duotone file, it's probable other files may not have been updated too.
#7
@
3 years ago
- Milestone 5.9.2 deleted
- Resolution set to invalid
- Severity changed from major to normal
- Status changed from new to closed
Closing this ticket as there's not an issue to resolve with wp_render_duotone_filter_preset()
function within Core or Gutenberg.
Hey @etilley, for your reference, here are a couple of articles on upgrading (or in your case re-upgrading) to a WordPress version:
- Updating WordPress - one-click way which can be done on the WordPress Updates UI in your site's Dashboard by clicking on the "Re-install version 5.9.1" button.
- Upgrading WordPress - Extended Instructions - manual way
#8
in reply to:
↑ 6
@
3 years ago
- Severity changed from normal to major
Replying to hellofromTonya:
I agree with both @Mamaduka and @swissspidy.
Doing a search of where the
wp_render_duotone_filter_preset()
function is declared:
- In WP 5.9.1: it's
function
only appears in one place, i.e. in thewp-includes/deprecated.php
file.- In Gutenberg plugin: it does not exist.
The issue then is not in 5.9.1 or Gutenberg. Rather, the issue is an incomplete upgrade to 5.9.1.
@etilley I'd suggest reinstalling 5.9.1 to ensure all new files are present. Why? Since there's an incomplete installation of the duotone file, it's probable other files may not have been updated too.
Thanks for this ... I notice that the manual update documentation says to manually erase and replace with new files /wp-admin and /wp-includes -
If this is still the correct process, then will try this next. Please confirm...
#10
in reply to:
↑ 9
@
3 years ago
Replying to swissspidy:
Yes that should work.
Thanks - I'll add that I am preferring to rename my \wp-content\plugins directory as plugins_old . I realize that I'm supposed to run \wp-includes\plugins.php to reset plugins - but I can't at present and I want those plugins out of the way so WordPress can make any 5.9.1 updates -without worrying about plugins. Unless you see a red flag - this sounds like the safest approach based on my reading.
Hello @etilley welcome to WordPress Core Trac and thank you for reporting this issue,
Marking for 5.9.2 consideration.
Ping @mamaduka for information. For the moment I don't know if we need to fix this on Core or Gutenberg side (or both).