View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 6029 | Composr | core | public | 2024-10-26 21:15 | 2024-11-15 00:56 |
| Reporter | PDStig | Assigned To | PDStig | ||
| Priority | normal | Severity | feature | ||
| Status | assigned | Resolution | open | ||
| Summary | 6029: Add support for using resource GUID in place of id in URLs / page-links | ||||
| 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. | ||||
| 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. | ||||
| Tags | Roadmap: v11 | ||||
| Attach Tags | |||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
|
|
Maybe a way to do this is to add a new get_param_id('param', 'content_type') (similar to get_param_string('param') except it auto-validates the given information and returns the resource ID (or if Commandr is not installed, it just returns the parameter value). 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. |
