Jens Külzer
Jens Külzer
IMHO it is not a missing feature, but a bug. Yes, it is possible to have multiple categories with the same name. And even if you don't use that personally...
I am _not_ satifsfied with the way this issue is handled here from a communication point of view. While "not satisfied" is more an euphemism. In fact it upsets me...
> The recommendation to harden the MODX 2.x is from the past when Composer didn't even exist. Then this part of hardening docs should also be changed for the 3.x...
I would really appreciate a solution which mitigates that issue when doing the jump from 2.x to 3.x, automatically would be the best way. I can think of a script,...
My thoughts so far: - we should create a _config check_ for the 2.x branch, which checks if the installation is hardenend and warns that the upcoming 3.x version won't...
I am already working on that, because most of the problems have already been solved with the updater extra. As this extra does not make sense any more for the...
more general: shouldn't all the action icons from above the resource tree go down into the context sections? There is already a plus-icon for adding new documents at the context...
The Updater Extra (not actively maintained any more) did it with the github tags, which worked very well - i don't really see a need for an extra backend endpoint...
Unfortunately thats still an issue and its still a bug. If you have two different categories with the same name, gitify will sort every element into the first category (lowest...
So that has been merged #417