Thomas Hunziker
Thomas Hunziker
> 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...
> (is not forced to do so) We will be forcing it with 4.0. It's not optional at all.
@mbabker Michael, I'm not saying to keep the old URLs working forever. I just want to have a way site admins realistically can redirect the old URLs to the new...
> but if it is possible, could a link migrator automatically create 301 redirects with our component redirect??? That's what I suggested in the initial issue description. But done in...
Last night I was thinking about an approach where we would add a temporary argument `$forceLegacy` to `JRouter::parse()` which would then override the legacy/experimental parameter setting. With that, we could...
I probably don't understand the sentence. With temporary I mean we could add that argument with 3.7 and deprecate it right away again for 4.0 when the legacy routing is...
You can't add it to the interface, that's true. But as far as I know the component routers could have that additional optional parameter both in J3 and J4. It...
This could be done in a smilar way like we do in com_content, optionally showing items from subcategories (see https://github.com/joomla/joomla-cms/blob/staging/components/com_content/models/articles.php#L355-L381)
If you only moved the "Featured" filter to set it using GET, that works as well with: `/administrator/index.php?option=com_content&view=articles&filter[featured]=1`.