TYPO3 Core

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/75384

Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/75384

Patch set 4 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/75384

Is there any reason why this change is necessary/better than the current state? I really like the hash method and would hate to see this just disappear without a way to enable it via configuration.

Jan Delius wrote in #note-6:

Is there any reason why this change is necessary/better than the current state? I really like the hash method and would hate to see this just disappear without a way to enable it via configuration.

Interesting. Until now I only heard exactly the opposite. Can you elaborate why you like hashed folders more?

Helmut Hummel wrote in #note-7:

Interesting. Until now I only heard exactly the opposite. Can you elaborate why you like hashed folders more?

I think that's more a matter of faith, rather than people really preferring one or the other here for some reason.

I myself like that you as an end user can't see at first glance from which extensions anything is loaded. Sure, experienced users can still see something like that, but that doesn't bother either. In addition, I like when the base paths are uniformly long. But as already mentioned above, these are simply personal preferences.

As a developer, I don't see any real advantages to making the URL more readable. That's why maybe an option (in composer.json?) would be the best option here.

Patch set 5 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/75384

Personally, I really loved the change to the hash. A decade old discusion with my integrator(s) ended finally and they finally have been forced to not use hardcoded paths in templates and markups. Countless debuging time of customer reported issues because of renamed images and resources and hardcoded usage in extension resources. Finally ended.

We had no issues with that in any project so far. I'm still curious if someone can really state a use-case where the revert is the only option and not only to mitigate long-term bad habits.

Patch set 6 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/75384

Patch set 7 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/75384

@Helmut Hummel Should we just abandon this patch?
We've started working on this at the dev days 2022, but it seems like there's no real interest to switch back from hashes to readable paths.