If you attempt to create a menu entry for a node at /about, you can enter about into the menu UI, and it knows that's an alias. The menu entry it saves is actually for the system path, at node/2.
Could we do something similar for layouts? Many people who are new to backdrop try to put in an aliased path for the layout instead of the system path. Would it be possible check the path table, and do a switcheroo for them if we find a match?
For example, if they entered about we could
* lookup the matching system path of node/2, then
* realize that there's a system path of node/%, and
* rewrite that field as node/% for them.
This might have to be done with ajax as soon as they tab out of that field, since the contexts in the next question need to be added dynamically too...
Recent comments
Oof. Just hit this part of my converstion to Backdrop. I'm surprised that there's no smooth path for this since, I thought, Media module was pretty commonly used in D7. Nothing from me,...
Upgrade from Drupal 7 with Media CKEditor
Thanks for the response and probably good info for someone, but you're correct that it's not really what I was looking for. I need to be able to run code and that code determines which...
How to programmatically change layout?
I ran into this problem again, now I understand, I can simply edit View and changing the filter option „Remember the Last Selection“. Unlike Drupal, Backdrop use Views for the Content page, I...
Incorrect filter behavior on the /admin/content page