Support » Plugin: Translate Multilingual sites - TranslatePress » Warning with 2022 Theme and Editor (Beta)

  • Resolved costaconsciencia

    (@costaconsciencia)


    Hi, I am just started to build my first website with the new page builder wishing the twenty-two theme..

    Everything seems to work fine so far, but I get a warning when selecting “edit site” (The new in theme live editor)

    Any idea? I know, its still beta but already useable..

    Warning: Attempt to read property “ID” on null in /homepages/22/XXX/htdocs/clickandbuilds/XXX/wp-content/plugins/translatepress-multilingual/includes/class-translation-manager.php on line 500

    Warning: Attempt to read property “post_status” on null in /homepages/22/XXX/htdocs/clickandbuilds/XXX/wp-content/plugins/translatepress-multilingual/includes/class-translation-manager.php on line 502

    Warning: Attempt to read property “ID” on null in /homepages/22/XXX/htdocs/clickandbuilds/XXX/wp-content/plugins/translatepress-multilingual/includes/class-translation-manager.php on line 504

    Warning: Cannot modify header information – headers already sent by (output started at /homepages/22/XXX/htdocs/clickandbuilds/XXX/wp-content/plugins/translatepress-multilingual/includes/class-translation-manager.php:500) in /homepages/22/XXX/htdocs/clickandbuilds/XXX/wp-admin/admin-header.php on line 9

Viewing 4 replies - 1 through 4 (of 4 total)
  • The same problem that I have on my website. With version 2.3.1. something is ok. With the newest version 2.3.3. appear the error.

    Plugin Support Alex

    (@alexcozmoslabs)

    Hi,

    I tried to replicate with the Twenty Twenty-Two theme, but the issue wasn’t encountered. Could you give me more details, maybe screenshots, about what exactly you are using and how I should replicate the behavior?

    • This reply was modified 2 months ago by Alex.
    Thread Starter costaconsciencia

    (@costaconsciencia)

    Its when using the beta version editor (edit site), not in the default block editor..

    Plugin Support Alex

    (@alexcozmoslabs)

    Hi,

    My suggestion is to wait for the final version and let us know then if the issue will still be there.

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