View more context

 

dorsetdigital

(depending on the target date for composer 1.11 of course)

dorsetdigital

It might be worth raising an issue on Framework as a heads-up. There may be solutions with classmap, etc. or it might be that the classes can be updated accordingly, but it would be good to be ahead of what could confuse a lot of people!

dorsetdigital

Especially since composer is now the de-facto way of managing CMS 4

lerni

I'll get some sleep now - If somebody raises an issue for this, ping me - otherwise I'll tomorrow

lerni

anybody 'll try with the upcommings?

lerni

https://github.com/silverstripe/silverstripe-framework/issues/9357

Show 1 attachment(s)
GitHub  
From composer v1.11+ autoloading just works if psr-4 compliant · Issue #9357 · silverstripe/silverstripe-framework

Affected Version 4.4.4 and 4.5.0-rc2 - most probable all 4.x Description If you run composer with --optimize-autoloader it'll throw Deprecation Notices with 1.10-dev like Deprecation Notice: Cl...

Hide attachment content
clodeindustrie

Hi, is there a quick way to toggle visibility of a cms field? or do I need to write up some JS myself?