Editor broken after update

Just to add, I tried running in recovery mode as well. When I try to reach the plugin screen, I get a WP error screen that just says “Invalid post type.”

On the installed plugins screen, the plugin shows the following error (wordpress also sent me an email indicating a fatal error occured in this plugin):

Error Details
=============
An error of type E_ERROR was caused in line 281 of the file /home/dh_9fgryu/palmsout.net/wp-content/plugins/custom-css-js/includes/admin-screens.php. Error message: Uncaught TypeError: unserialize(): Argument #1 ($data) must be of type string, array given in /home/dh_9fgryu/palmsout.net/wp-content/plugins/custom-css-js/includes/admin-screens.php:281
Stack trace:
#0 /home/dh_9fgryu/palmsout.net/wp-content/plugins/custom-css-js/includes/admin-screens.php(281): unserialize(Array)
#1 /home/dh_9fgryu/palmsout.net/wp-content/plugins/custom-css-js/includes/admin-screens.php(352): CustomCSSandJS_Admin->get_options(3151)
#2 /home/dh_9fgryu/palmsout.net/wp-includes/class-wp-hook.php(310): CustomCSSandJS_Admin->manage_posts_columns(‘type’, 3151)
#3 /home/dh_9fgryu/palmsout.net/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters(”, Array)
#4 /home/dh_9fgryu/palmsout.net/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#5 /home/dh_9fgryu/palmsout.net/wp-admin/includes/class-wp-posts-list-table.php(1387): do_action(‘manage_custom-c…’, ‘type’, 3151)
#6 /home/dh_9fgryu/palmsout.net/wp-admin/includes/class-wp-list-table.php(1766): WP_Posts_List_Table->column_default(Object(WP_Post), ‘type’)
#7 /home/dh_9fgryu/palmsout.net/wp-admin/includes/class-wp-posts-list-table.php(1421): WP_List_Table->single_row_columns(Object(WP_Post))
#8 /home/dh_9fgryu/palmsout.net/wp-admin/includes/class-wp-posts-list-table.php(829): WP_Posts_List_Table->single_row(Object(WP_Post), 0)
#9 /home/dh_9fgryu/palmsout.net/wp-admin/includes/class-wp-posts-list-table.php(805): WP_Posts_List_Table->_display_rows(Array, 0)
#10 /home/dh_9fgryu/palmsout.net/wp-admin/includes/class-wp-list-table.php(1676): WP_Posts_List_Table->display_rows()
#11 /home/dh_9fgryu/palmsout.net/wp-admin/includes/class-wp-list-table.php(1603): WP_List_Table->display_rows_or_placeholder()
#12 /home/dh_9fgryu/palmsout.net/wp-admin/edit.php(495): WP_List_Table->display()
#13 {main}
? thrown

Hello Haldan,

would you run this SQL query in your database and copy/paste me the output: SELECT * FROM wp_postmeta WHERE post_id = 3151;? On my test website the output looks as follows:

MariaDB [wp_ccj]> SELECT * FROM wp_postmeta WHERE post_id = 12581;
+———+———+————+—————————————————————————————————————————————————+
| meta_id | post_id | meta_key | meta_value |
+———+———+————+—————————————————————————————————————————————————+
| 1118 | 12581 | _edit_lock | 1701283245:1 |
| 1119 | 12581 | _edit_last | 1 |
| 1120 | 12581 | options | a:5:{s:4:”type”;s:6:”header”;s:7:”linking”;s:8:”internal”;s:8:”priority”;s:1:”5″;s:4:”side”;s:20:”frontend,admin,login”;s:8:”language”;s:2:”js”;} |
| 1121 | 12581 | _active | yes |
+———+———+————+—————————————————————————————————————————————————+
4 rows in set (0.000 sec)

I had to change wp_postmeta to match the name of the corresponding table in my db, but this is what I got

meta_id|post_id|meta_key|meta_value|8030|3151|_vp_words_count|23|8033|3151|_edit_last|1|8034|3151|options|a:5:{s:4:”type”;s:6:”header”;s:7:”linking”;s:8:”internal”;s:8:”priority”;s:1:”5″;s:4:”side”;s:8:”frontend”;s:8:”language”;s:3:”css”;}|8035|3151|_edit_lock|1638504092:1

Would you install the plugin’s 3.45.1 version from here and see if that solves the error?

I still cannot replicate the error on my test website, so I’m not sure if the fix in the 3.45.1 version will work, but it’s worth a try.

Not the original user in this thread, but I was having a similar issue on a local development site, and found this thread. The 3.45.1 update linked above worked perfectly for me.

@diana_burduja Thanks for the update! I didn’t see this until @dylanabbott replied, so thanks Dylan.

So far, the update appears to have fixed the issue for me. I will update if something changes. In the past, the problem occasionally appeared to have fixed itself (I.e., I could briefly access the list of custom codes and edit them), but any refreshing of the page or reaccess would lead to the problem appearing again. So far with the update this is no longer the case. Fingers crossed!