Site broken since update to 3.2.4

Hi Mathias,

Thanks for reaching out.

I’ve tried to replicated the issue in local environment. However, it’s functioning properly. Can you please let me know which theme and grids you’re using?

Also, it will be great if you can share a screenshot with us.

Regards
Owadud

Hello Owadud,
thanks for the reply. I’m using the Theme TwentyTwenty with an up to date wordpress 6.4.3 and PHP 8.2.16.

The update went smooth (from 3.2.3 to 3.2.4), so no errors were shown. Also in my wordpress and server logs I see no problems. Here is a small screenshot of a site from the comment icon, that is now missing. Before the update it looked like this, after like this. But also the headings are completely wrong sized, the spacing between images and text broken – so the site looks just unusable. This is just to demonstrate the issue.
That is in the block “Post List #2”.

I hope that you can help me with that issue.

Thanks ans many greetings

Mathias

Hi @mathse ,

I have also tried to generate the issue on my local but could not produce any. Its working fine here on both the latest and the previous version. an image for reference. Would you please share the url of your site having the issue. So that we can check the issue thoroughly and give you a proper solution.

Hi @aamzahid,

thanks for your testing and the reply. I also worked on the problem and it was on my side. With the latest update you seem to be switched from using PHP functions to read files from the dist to using WP_FILESYSTEM.

This wasn’t initialized correctly in my case. I found the solution here, where the following is mentioned:

When determining how to best read/write to files, WordPress will write a dummy file to the wp-content dir. It will then check to see if the file owner of the newly created file (which should be the user that the webserver is running as) matches the file owner of the wp-admin/includes/file.php file. If they don’t match, then WordPress tries to access everything via ftp or something similar instead of just reading/writing to the filesystem directly. Would you be able to check if this is the case in your install?

In my case wp-content was not writable, so wordpress failed to perform the above check. I fixed this and now everything works fine.

Thanks for the support here and many greetings

Mathias

Glad to hear that your issue has been resolved and it’s working fine .

Same deal for me. It will certainly be the permissions on my server. Easiest fix for me will be to roll back to 3.2.3. How can I do this?

You can download the previous version from the WordPress Directory > Advance View > Scroll down > Select the version and Download. image for your reference

Here is the direct download link – PostX.