Elias Schwerdtfeger

great to hear! Not sure how it’s possible that the upgrade didn’t start, but we can create a check for this.

Thank you for the quick and dirty solution, which worked great on another site too. 👍

As for the php warning: it’s just a warning, so you can ignore it, but we’ll fix it in the next release.

That’s what I expected.

OFFTOPIC: PLEASE, WordPress, PLEASE give me in a support forum a working forum software without your incredible annoying forked up editor gadget, which I disabled in the Dashboard immediately after my first try of using it! I lose half an hour of my limited life time by losing all I typed after submitting. The fact that I’m unable to save the text as a whole don’t make my life better.

Okay, much less text now.

[Sun Aug 04 10:13:55.487963 2024] [php7:notice] [pid 101909] [client xx.xx.xx.xx:37134] WordPress database error Unknown column 'statistics.device_id' in 'group statement' for query SELECT COUNT(*) AS value, device as device_id FROM spam_burst_statistics as statistics\n\t\t\t\t\t\t\t\t\t\tWHERE statistics.bounce = 0 AND statistics.time > '1712257883' AND statistics.time < '1722815999' \n\t\t\t\t\t\t\t\t\t\tGROUP BY statistics.device_id ORDER BY value DESC LIMIT 4 made by require('wp-blog-header.php'), wp, WP->main, WP->parse_request, do_action_ref_array('parse_request'), WP_Hook->do_action, WP_Hook->apply_filters, rest_api_loaded, WP_REST_Server->serve_request, WP_REST_Server->dispatch, WP_REST_Server->respond_to_request, burst_get_data, burst_goal_statistics->get_goals_data, referer: http://xxxx.xxxxxx.xx/wp-admin/admin.php?page=burst

If you disable comments and trackbacks in the WP dashboard, options, discussion (they may be named different in english, I use a german WP version), you set a default for new posts (which you can overwrite for any post), but do not change the comment settings for the published posts. So, the older posts are still open for commenting — and for the pest of the internet, spam.

The most painful solution is, to edit every recent post in WP and unset the comment options. If you are technically competent and do not “fear” a simple SQL query, you can use a SQL query to set the comment_status and the ping_status for all posts in your post table to closed, which should work for you. (The following SQL statement is for WP 2.3.x, it may be different on older WP versions.)

UPDATE your_table_prefix_posts
SET comment_status = "closed",
ping_status = "closed"

Of course: Backup before doing low-level stuff in the WP database!

If you cannot access your database on SQL level (and don’t have a phpMyAdmin or something similar available), there may be another help. I remember that there is a plugin, which closes pings and comments for posts automatically, if they are older than one month. But I never tried it…

How can I confirm that all files were correctly copied? ANd if they are not, what do I do?

Just do upload the files again. If your FTP client allows you to save a protocol of the transmission or to write a logfile, do it and take a look into the file, if not, use a client which gives you this option. If you see no messages suggesting an error in this log, your upload seems to be fine and the files are correctly copied.

I could resolve my problem by installing the “Tiny MCE Advanced” plugin. Now I’ve got an avanced WYSIWYG, which is not exactly what I wanted, but it works for me (and hopefully for my co-authors, which is much more important).

There is still a minor problem. To use the plugin version of the Tiny MCE, I have to deactivate the AdBlocker plugin in my Epiphany browser. With AdBlocker, the JavaScript does not load, but this seems to be a problem in the AdBlocker implementation. With Opera, the plugin works out of the box.

If you do not have a WYSIWYG editor with 2.3.2, try the plugin. It helps me, and it may help you.

Similar problem, visual editor does not appear after upgrade from wp 2.3.1 to 2.3.2. It worked without problems on the same server configuration with wp 2.3.1.

Of course, visual editing is enabled. To be totally sure, I uploaded the tar to the server, extracted it there, deleted the old installation and copied the 2.3.2 files. But it does not help.

The tabs “visual” and “code” do appear, but no wysiwyg editor in them. It is a simple textarea, and without the controls from the code editor. The problem do occur with the browsers Epiphany and Opera in the newest version.

The javascript error console from Epiphany says: “editorTemplate has no properties”.

I could not test it with MS Internet Explorer, because there is no linux version of the IE. Epiphany uses the same engine as Mozilla, but in another GUI.

I’m sure that it is a bug. It may occur only under strange conditions on the server. If anyone else get the same problem, we should check our webserver’s configurations to find the reason for this problem.