Closed (outdated)
Project:
Page Manager
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
31 Jan 2016 at 18:32 UTC
Updated:
25 Jul 2026 at 01:49 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
berdirComment #3
tim.plunkettThe way forward for the UI is pretty clear. But what should we do for pages that are programmatically defined? Or if we don't write an upgrade path? (Though we probably should!)
Do we throw an exception, trigger an error, skip it and use an assert()?
Here's a patch for the exception.
Comment #5
tim.plunkettComment #6
tim.plunkettComment #7
berdirI posted the content of my upgrade path function in #2352959: Arguments step -1: Make it possible to generate paths with it..
The exceptions seems a bit tricky. Something might case a route rebuild during update.php, e.g. entity updates that trigger views re-save that in turn trigger a route rebuild...
Comment #8
berdirTwo more things:
* Apparently people are trying to create a patch with just "/" as the path. We need to validate and prevent that. See #2623592: Error with page manager.
* Second, the show-link-or-not detection on the overview page doesn't work with {slug}'s. It displays those as a link and they will obviously not work then.
Comment #9
tim.plunkettFixed #8. Didn't include an upgrade path. Still not sure about the exceptions.
Comment #11
tim.plunkettUhhh, okay?
That would pass tests. What's so special about "?
Comment #12
tim.plunkettComment #13
dobrzyns commentedRe-rolling patch.
Comment #15
blackiceuaCanceled
Comment #16
blackiceuaComment #17
blackiceuaRe-rolling patch.
Comment #18
blackiceuaComment #19
japerryPage Manager 8.x-1.x is no longer supported, closing.