I was thinking that when someone did create a layout by typing in entity/numeric
, we could use a submit handler to switch it to the expected use: a layout at node/%
with a visibility condition limiting it to the single entity, either by ID or path.
That way nobody needs to learn a new behavior, but we deliver the feature we intended, and it will work closer to how they expect.
This is a follow-up to both https://github.com/backdrop/backdrop-issues/issues/2636 and https://github.com/backdrop/backdrop-issues/issues/5433#issuecomment-100...
From @docwilmot:
What if we automatically fixed this for the user? Meaning if a user types in entity/numeric we automatically converted this to entity/% and added a condition for entity id = numeric ?
from @jenlampton:
Can we add a condition for path instead of entity ID? I feel like that's going to be more in line with what people expect to happen.
We should also add a message saying "A condition has been added for this layout to match the path you entered" so that people don't think it's a bug.
Recent comments
Hmm... I was able to reproduce this issue when I thought it would work. Wuold you mind opening an issue in the queue?
How to order a view by its aggregated value
Hi Robert. I'm looking at D7 issues about this - apparently this is possible since 10 years ago, which means the functionality is there, but there may be some issues with the way your view is...
How to order a view by its aggregated value
Not sure of the procedure. Can I upload/import a partial .po file to the Backdrop Translation server or does it have to be a complete export from my site?
Ubercart in Danish?