• Hello,

    Today, I had to modify a widget using JavaScript code because WordPress widgets cannot be saved. It consistently results in an error stating that the response was not in the correct JSON format.

    Standard troubleshooting steps (reinstalling WordPress, updating permalinks, etc.) had no effect.

    However, I noticed that another site using the same theme is experiencing the same issue. Crucially, deactivating all plugins also makes no difference.

    I was able to edit the widgets without issues as recently as early last week. The problem clearly arose after the latest theme update.

    Please fix this.

    Thank you.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hello @michalrama

    A simple way to identify the cause is to temporarily switch to one of the default classic Twenty Twenty themes and check whether the issue persists. If it does, this would indicate that the problem is most likely related to a plugin or site configuration.
     
    Could you please try this and let me know the result?

    Thread Starter michalrama

    (@michalrama)

    Hello @cteduard

    The Twenty Twenty theme allows for widget editing (even though the list is limited), yet the problem persists.

    And as I mentioned, deactivating all plugins doesn’t help. I thought the issue might be the PHP version, but I have a third site using this theme that runs on PHP 8.3 (not 8.5), and it doesn’t work there either.

    I honestly don’t know what is causing this problem or why it was working fine just a week ago.

    Thread Starter michalrama

    (@michalrama)

    Hello @cteduard

    Has there been any recent change to the theme that could be affecting this? It wouldn’t be the first time a minor update broke something.

    • This reply was modified 2 weeks, 4 days ago by michalrama. Reason: Accidental re-insertion of the same answer

    Hello @michalrama,

    As you have confirmed that temporarily switching themes does not resolve the issue, this indicates that the theme is not the cause. If Blocksy or one of its updates were responsible, the issue would no longer occur when another theme is active.

    As this does not appear to be a theme-related issue, we are unfortunately unable to investigate it further. I recommend reviewing the overall setup for any plugins, custom code or server-side configuration that could be causing the problem.

    Thanks,
    Eduard

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

You must be logged in to reply to this topic.