Dimitris Grammatikogiannis
Dimitris Grammatikogiannis
@XhmikosR since the node-sass is officially deprecated ( https://github.com/sass/node-sass#node-sass ) could the team move forward with this one?
> Any change to a URL that will give a 404 (or some other error) where it previously gave a 200 is a break in backwards compatibility Not if the...
Educate people and then they will be fine. Tell them to create a sitemap of the old site, create another on when they'll upgrade to the new system. Then explain...
@brianteeman I'm guessing here that anyone that wants to move to the new router (**is not forced to do so**) understands the impact of that change.
@bembelimen I wouldn't enable that **before** fixing the counter to work nicely for repeatable fields. BTW the project should review the fields compatibility with repeatable fields and patch what's broken...
> as the problem is the same with textareas Yes, the initialization of that script is missing the listener for subform add/removal part > the spreading over all fields? There...
> it will be more of an issue with this field - and I see an issue whereby the capabilities of a custom field are not in sync with an...
@richard67 my comment is still valid, introducing this without support for repeatable fields is plain wrong 😑
@fancyFranci please reconsider merging this PR as the complete refactoring probably can't happen in the 4.x
@laoneo the js code is passed inside the urlparams. In order that code to be come executable there’s an eval() and there is the problem, in sort the id of...