Hallo, eine Kundin schreibt mir, weil Ihr Provider ab Dezember PHP 7.2 nicht mehr unterstützt.
Kann sie mit Typesetter 5.1 auf die derzeit empfohlene PHP-Version umstellen?

Vielen Dank für eine Info!

 

english version:

A client is writing me that the provider will not support php 7.2 anymore. Can we change to the recommended php-version with typesetter 5.1?

Only the Master-RC 5.2 at https://github.com/Typesetter/Typesetter  is php 7.4 ready

But how can the client do that?

The normal way is : rename the directory /include to ___include.old  and copy the new include-directory from the harddisk with a ftp-client like filezilla-portable into the root. Also do the same with the gpconfig.php in the root.

If You want to use newer templates, You can do the same with the templates-directory (better matched to the new scss-version) . You can also overrrite the templates and so keep Your own templates.

Please make a backup before under Tools in the cms ! Typesetter has no inbuild update-function.

Thank you!! Only, i wonder about:

Typesetter has no inbuild update-function.

There is such a function, but it doesn't offer more than 5.1

I run several installations of Typesetter 5.1 with php 7.4 and haven't encountered any problems so far. mabu, do you know what the problems are with Typesetter 5.1 running with php 7.4? And is Typesetter RC 5.2 safe for production use?

If You switch the debugging on in the gpconfig.php and in the cms, You will see ....

5.1 has also minor errors and a security -Problem with phpmailer, for which i have written a plugin.

It has an old ckeditor, an old  less-compiler and an old scss-compiler which is not ready for bootstrap 4.

RC5.2 is ready for production - why 5.2 it is not published? - the developer is evtl. busy ?

You may also  put this question at github

Thank you mabu :-) If I turn on the debugging, I see a lot of notices when I try to login into Admin concerning less compiler. But no errors or notices in the frontend.

I'm more concerned about the security-problems with phpmailer... So if RC5.2 is production ready, updating might be a good idea...