/image/jit-recipe/filepath/photo.jpg.webp, so you just add .webp at the end of existing JIT requests, everything else stays the same. JIT will then create a webp from the file "/image/jit-recipe/filepath/photo.jpg".Any good?
It's just a proof of concept for now, did not pushed it to the repo yet. But it works. Haven't tested it yet with caching disabled and you need to use a
mode, even if it is a direct display, to get a webp file.What I don't like about this approach - but that goes for JIT in general - is that you don't get file sizes with JIT-generated images into your XML/presentation to inform user about the file size, if such information is appropriate or legit.
picture element, I don't have a live example as of now, only tested the recipes.
it only happens when you have 'error_reporting_all' => 'yes', in the config.php
ok. @cylkee the get_magic_quotes_gpc is non-essential to SCMS, easy transition to PHP 8 in this regard, actually petertron's ready for PHP 8 SCMS 3 already has that solved.
I actively use it too but honestly it's getting harder to justify with the lack of support and community :( @wdebusschere what headless CMS do you use?
I agree. Also about what @cylkee wrote, I want to further elaborate on that, but my recent idea was to create a common SCMS rolling edition ("RE"), which would contain regular updates and improvements on the go. Very much like you have linux distros, there are LTS versions which is the current SCMS, and then rolling distros or in-between LTS releases. And anything good from RE could be potentially taken into the next official SCMS LTS release, should that later on happen. Anyway, it's a fresh idea, I'm still in the dark about versioning RE etc. I would not even mind to dump PHP 7 compatibility in RE in favor of PHP 8 / not having redundant code for older PHP versions.
2.7.x version, but that did not go very long. For my part I’d love to see a stable 2.7.x version with all the necessary fixes. 2.7.10 has some nasty bugs and I have a local copy with some hot fixes, but that’s not a very nice state to have symphony in. Personally I don’t care ver much about 3.0.0 since I was never able to get it to run at all, and I expect a lot of problems with extensions. So keeping 2.7.x working, also with PHP 8, should be the first priority in my opinion.
I've tested @petertron 's SCMS 3 version about a month ago, there were no problems with installing it and running under PHP 8. But that was only pure SCMS 3, with no additional extensions and I haven't tried out everything in the backend. All of this I plan to do, also want to make additional fixes when I'll found any, e.g. symphonycms/symphonycms#2926 bugs me a lot, but that's the least concern to fix. I am optimistic about having a running updated SCMS version. I also find quite intriguing @pointybeard 's extended SCMS version, will check that one as well. Anyway, I want to start with some extensions update, like the mentioned multiupload field, I only have to play a bit with git repo there; webp support I should have already nailed, want to deploy it on a live site, will send you link then.
About the idea of expanding or supporting community, I think I really miss some full fledged tutorials e.g. on how to build a site, how to constitute xsl templates the best way / best practices for xsl, example code etc. Maybe I was not on official site in years for that matter and forgot (I mostly browse API docs there and no other content for some time now), I am sure you can find lots of bits of informations on xsl in forum post but maybe nothing sumarized in one - even if a long - article. Maybe I know a trick or two about XSLT, but I am always happy to improve. Or on how to create your own extension etc. I think, if such a content does not exist yet, it would have its value and it could live easily outside offic. symphony site, which is not being updated for the time being. I find good documentation is the cornerstone for a growing potential of every project. I believe it takes a lot of effort to create such or any documentation at all.