Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter luciusv

    (@luciusv)

    First of all, thank you for your responses.

    The issue has now been resolved. The root cause was corruption in some translation files (.po and .php files) that were generated from the corresponding .mo files. These corrupted files, likely damaged during the migration from one server to another, were preventing both access to the WordPress backend and the general functionality of the site.

    To resolve the issue, I deleted the corrupted translation files. Since these files are automatically regenerated from the .mo files, they were successfully recreated without any further intervention. This fixed the errors and restored full access to the backend as well as the proper functionality of the website.

    • This reply was modified 4 months ago by luciusv.

    Hello, we found a workaround for this problem. Clearly, there is something wrong with the default editor. We installed Gutenberg (I know it’s supposed to be the default editor, but for some reason, it simply doesn’t work) as a plugin, and everything worked fine. So, I suggest downloading Gutenberg as a plugin and waiting for a fix.

    Thread Starter luciusv

    (@luciusv)

    We discovered that the problem was related to the popup plugin in our theme. Apparently this popup plugin is incompatible with CF7.

Viewing 3 replies - 1 through 3 (of 3 total)