[appareas]

You! ARE! Awesome! 🙂
Thanks a lot not only for your amazing professional support but also for your patience!
So this was a real need for me:
https://wordpress.org/support/topic/awesome-and-best-support-ever/

Have e nice time,
Jürgen

PS: Are you actually an employee of catchthemes.com? If not, the company should really thank you! 😉

[appareas]

Hallo Skandha,

great! Now the issue is solved – thank you so much!
Please, be so kind to tell me what you´ve done.
That was only the test-site, i have to transfer this to my development environment.

Kindly regards,
Jürgen

[appareas]

Hi Skandha,

i have sent the information.

Kind Regards,
Jürgen

[appareas]

…no, unfortunately not. 🙁
Please be so kind to try

webmaster@stoeberbox.**

Thanks a lot!

[appareas]

Thanks a lot, please contact under info@appareas.**

Kind Regards,
Jürgen

[appareas]

Unfortunately, no success. I deactivated all plugins and activated only the Classic Editor – same result.

I’ve already done a full reinstall of WordPress twice, including deleting the database and using a new one to rule out the possibility of the WordPress installation being broken. After reinstalling and using a new database, the problem continues to be reproducible – when activating the Classic Editos, WordPress will exit with the above error message when saving or updating the page.

The message “headers already sent by” in the second error indicates that a save is tried several times. This coincides with my observations, because despite the error message, the change of the page is saved.

Thank you for your help!

[appareas]

Thanks for the hint! Thanks to you I was able to carry out the update.
Here in Germany we have a saying – “who can read, is clearly in the advantage.” 🙂 I think I should actually read something more intense.

Unfortunately, the problem with the Classic Editor with the update has not been resolved. 🙁

Thanks again and best regards!

[appareas]

Many thanks for your help!
In the meantime I found out that it is probably due to the plugin “Classic Editor”. If I deactivate the Classic Editor and work with Gutenberg, error messages will no longer appear. This is a big problem for me because I work with HTML5 / CSS3 and do not use Gutenberg.

In addition, a new problem has emerged today. When updating to the offered version 3.8.1 I receive the error message:

Undefined index: package in /homepages/28/d642563536/htdocs/eichholz/wp-admin/includes/class-theme-upgrader.php on line 374

An error occurred while updating Parallax Frame Pro: update package not available.

Thank you for your effort.

[Author]

Posts