Viewing 11 replies - 1 through 11 (of 11 total)
  • Jorge Luiz

    (@jluizsouzadev)

    First off, do you have any previous backups? If not, to do right now for avoiding headache.

    Have you already actived the WP debugging?

    If not, take look at this documentation to do so. That way you’ll can get more detailed error messages.

    • This reply was modified 3 months ago by Jorge Luiz.
    Thread Starter Anomn

    (@segurihost)

    Hello. Yes, I activated debug but there’s no file created. The error is only in browser console (javascript)

    define( ‘WP_DEBUG’, true );
    define( ‘WP_DEBUG_LOG’, true );

    threadi

    (@threadi)

    Which theme are you using? Try switching to a standard theme like TwentyTwentyFive.

    Thread Starter Anomn

    (@segurihost)

    I tried to do that too. I cant solve this. This happened after the last update, but it happended a few days after update. It is so weird. I changed the theme, deactivated all plugins, etc.

    The most weird thing is I cloned site with wp toolking into staging subdomin and everything worked normal. So I cloned to staging and then I cloned the staging to the official website, but it doesnt work u.u

    • This reply was modified 3 months ago by Anomn.
    threadi

    (@threadi)

    Have you tried to use a different browser? It is possible that a domain-specific browser add-on is interfering with something on the page.

    Thread Starter Anomn

    (@segurihost)

    Yes. I used firefox and chrome. Both with safe mode too. I tried everything :/.

    there are different javascript errors between staging and official but is the same site. It doesn’t make sense.

    Jorge Luiz

    (@jluizsouzadev)

    Are you using React on your WP site at all? Some plugin, theme or both.

    Please, take carefully a look at the article bellow.

    Upgrading to React 18 and common pitfalls of concurrent mode

    WordPress 6.2 ships with version 18 of?React, the?JavaScript?library used to build the?Block?Editor and all custom blocks. It comes with several new features, improvements, and?bug?fixes, including a new rendering algorithm, called concurrent mode. (#45235)

    In concurrent mode, React performs?UI?updates faster, and keeps the web page responsive. When it works on a large and complex UI update, it can still process all user input (mouse events, scrolling, keyboard events) in real-time, concurrently with the work it’s already doing.

    However, it also introduces some potential pitfalls that developers need to be aware of, and which may break some components that rely on the precise timing of events and state updates. These pitfalls affect only a small set of complex and specialized React code. Unless your code relies on the specific timing of state updates, it’s almost certain that your code will continue to work without any changes.

    Thread Starter Anomn

    (@segurihost)

    No react in plugins or themes. Remember I deactivated all plugins and changed the theme to Twenty Twenty-Five

    Did you chance anything in wp-includes directory? Are you sure?

    Futher information:

    What is the wordpress wp-includes folder for?

    Thread Starter Anomn

    (@segurihost)

    No, anything was changed. We dont change core files.

    Is there only the error message reported in the begining from this thread? Or are there other ones too?

Viewing 11 replies - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.