#6029 - Add support for using resource GUID in place of id in URLs / page-links
-
By PDStig
- Added
- 13 views
| Identifier | #6029 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Add support for using resource GUID in place of id in URLs / page-links |
| Status | Open |
| Tags |
Roadmap: v11 (custom) |
| Handling member | Deleted |
| Addon | core |
| Description | Allow the ability to specify a GUID in IDs for resources instead of the raw database record ID.
This has several advantages: * Any time database ID records need to be re-mapped (e.g. the importer), existing page-links or raw ID references will break. * This is a first step towards GUID migration for v12. * Now that resource GUIDs are cryptographically secure when generated, it is unlikely hackers can guess them. |
| Steps to reproduce | |
| Additional information | As part of our ID deprecation, consider the following:
* Implement this for v11.0 * Make this the default way we present IDs in URLs and page-links in v11.1 (but still allow numeric IDs); deprecate support for numeric IDs * Remove support for numeric IDs completely in v12. |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
And then add another function for returning a URL-based ID (such as in build_url) which would either be a moniker, GUID, or resource ID depending on what we request in the function (and if Commandr is available).
We will need to come up with a more robust solution for v12 which does not rely on Resource-fs.