Leaderboard

@nurkka RockShell can run without PW, but not all commands. Most need PW to be installed, but often that's just necessary (because it makes no sense without) or convenient (because it's harder to develop something without having PW magic on board). What you describe makes sense and it is definitely on my list. If anyone finds time to add this I'd be super happy to add it.

@bernhard outstanding! Many thanks!

Thank you Bernhard for clarifying your point of view again in such detail. Ultimately, you are of course right and many editors actually no longer allow the insertion of images. When I sometimes look at the output, I understand exactly why 🙂 In this project I will have to administer large parts myself, therefore it could have been a short cut. but then and for now - I'll have to do it "right" from the start. Since I can reuse the blocks, it will probably pay off

You can check the online status here: https://downforeveryoneorjustme.com/kuenstlerischepraxis.at As Gideon So wrote, you should contact your hoster to find out what's going on.

@herr rilke Practically the first thing I did was to change the display of the settings through adding my own CSS. Load your own CSS to the backend and try: .rpb-settings table tbody {display:grid; grid-template-columns: repeat(6, 1fr);} .rpb-settings table tbody td {display:block;} Looks something like this: CSS is sometimes better than a whole lotta change to code!

Hey @FireWire I've added the following to RockSettings v2.2.3 public function ___uninstall(): void { rockmigrations()->deleteFields("tags=RockSettings"); rockmigrations()->deleteTemplates("tags=RockSettings"); }

Thx, looking forward to seeing what you build with it 🙂 Thx for the good description! Please check v1.4.2!