For those who are waiting : At github is my typesetter fork for php8.0 - full functioning alpha3 - and beta1 with jquery 3.60 -  it will get some enhacements until summer. Please post issues there.

Dear mabu

Thank you so much for this fork. I use it in 2 installations since a few weeks without any problems so far. Great work!

The integration of bootstrap5 (as in bootscore) is rather complicated, because it needs scssphp 1.10.1 (dart-sass) .

I will have to modify the css.php and the scss.php - either use 1.2.1 for bootstrap 4 and 1.10.1. for bootstrap5 -  or only the latter. I am not sure that i will be able to do that in the  near future, because i do not have licensed tools which cost. I stand here alone, and neither the other developers nor You (!) do anything in this direction (for example a push for the css.php).

Sorry Mabu, but I am mainly a frontend developer and definitely don't have enough php skills to fully understand the typesetter code well enough to work on it. But if there is something to do with html or css, let me know and then I can see if my skills are good enough to help with it.

HM... You could develop a free template (sidebar - canvas )  - so i do not stand alone...(and make Yourself popular)

OK, I'll try. Could take some time of course, but will do it. Do you have a schedule, when this version of typesetter should be production ready?

First of all : Typesetter is GPL2 - use it at Your own rsik. You can edit the version in the addon.ini and in the common.php (for customers like "tp53-creisi-p8".

The momentary version is ready for php8. The version in summer will be for php8.0 and 8.1 (and hopefully with scssphp1.10.0). A CMS is never completely safe because of unknown holes in the apache/nginx and in php (now: 8.0.14) and in Javascript.

The developers at github/typesetter let it run through some tools which are licensed, and i still found some deprecations because they still support 5.6...!

I will not buy a license for phpstorm (60 Eu / year) and others because i use it only for 2 private websites..and have a strong WAF and a backup (but not been cracked since 5.2)! I have also a wiki which is more important for me.

 

Just finished my first free template and uploaded it to typesettercms.com...

Interesting template :

A. You use Extra Content : Footer_column_1..3 in template.php. Can You please use Circles_column1..3 instead - because of possible conflicts with other existing templates.

B.  Can You please also add (not absolutley necessary)

[FrontEndFramework]
name = Css
version = 3

to the addon.ini

This is for registration of the template (new in TP5.2) - from installer.php. For bootstrap 4 it would be

[FrontEndFramework]
name = Bootstrap
version = 4

OK, I'll do that as soon as I have some time. The template also uses header, header content, sidebar and social media buttons. I assume these contents must also be replaced with "custom" Extra Content and must be generated when installing the template?

This is necessary for editable areas in Extra-content. The standard bootstrap4-template uses  Footer_Column_1...3 with unavoidable auto-registration algorithm (which i havent found out yet).

P.S. Can You make the sidebar compatible with simple-blog, so that we would have another template beside h5 and nedstrap.

Ah ok. Always thought, those Extra Contents are a part of Typesetter itself.

What does it need for the sidebar to be compatible with simple blog? And I hope, it isn't a problem, that the template doesn't use any bootstrap (I'm not so much a fan of those frameworks and never worked with bootstrap nor another one...)

A. Extra contents like editable footer-areas need manual registration, otherwise You get an error like  {{Missing extra content "Cir_foot_Column_2"}}  in the footer

B. I was was successful with   Cir_foot_Column_1..3

and      <?php       gpOutput::Get('Extra','Side_Menu');         gpOutput::GetAllGadgets();               ?> as in h5

You used \gp\tool\Output::GetExtra('Side_Menu');   in newer Typesetter(change) it is gpOutput::Get('Extra','Another Area');

Bootstrap-4 uses for example in settings :  gpOutput::GetGadget('Simple_Blog');

P.S. 'The heading "Blog" is then rather big. Something like div.gpArea_Simple_Blog h3 {font-size:20px;}; (in the Layout-editor) may help

Thanks. I'll take care of it next week, won't have time over the week end.

Made the update as proposed and hope, everything is ok now... As for the blog, only changed the font-size of the heading "Blog". Not sure, what else it needs, but maybe I'll have a further look in future.

Great - seems to function . The footers  were auto installed under Extra Content - a new Typesetter 5.2 - feature (not of  the bootstrap4 template as i thought).

My notice about styling of the BLOG was mainly for users who use the blog.  div.gpArea_Simple_Blog is an entry point for further styling.

I think i will also make css-demo template with crush in my tp8-version, so that users understand how to use crush with css(prefixes).

Another point is the scssphp, which gives me a compilation errror with bootstrap modal and px-rem in 1.10.0...

Bootstrap5 has no vendor prefixes, and an integration with scss-php 1.10.0 (because of dart)  and crush will take a time.

 

So I just was lucky then that everything worked in the beta version without errors, because I didn't use Bootstrap nor any Bootstrap function? Didn't use crush either, always have worked with compass, but not using scss functions of Typesetter. I guess, there are many functions of Typesetter I never used...

Are you sure about that:

You used \gp\tool\Output::GetExtra('Side_Menu');   in newer Typesetter(change) it is gpOutput::Get('Extra','Another Area');

Because of this thread (last answer from Juergen):

https://www.typesettercms.com/Forum?show=t2769&postid=11588%23post_11588

I am a bit confused right now.

The above mentioned post is a discussion with  $page->jQueryCode .= ' ... ' ; and about time. There is a simpler time-plugin at github, whose Javascript can be embedded in the head or with an automatic executed settings.php.

* GetExtra is a hook. I had another discussion with Juergen about this theme, and there is a discussion with Josh about this theme : <?php gpOutput::Get('Extra','Side_Menu2'); ?> and another posting here.

In the case of the cases You must test both (evtl. the code is or was tolerant - though deprecated).