View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000565 | WackoWiki | core | public | 2024-03-31 03:10 | 2024-03-31 03:10 |
| Reporter | brianko | Assigned To | brianko | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Product Version | 6.1.x | ||||
| Target Version | 7.0.x | ||||
| Summary | 0000565: Child pages can be created before parent pages (and do not correctly populate with a parent_id in this scenario) | ||||
| Description | Child pages can be created without the parent page being created first. This in and of itself isn't necessarily a bug, as the parent page (if desired) can be created afterwards. However, a child page created in this manner will never have a correct parent_id associated, as assigning this value isn't retroactive to creating the parent page. | ||||
| Steps To Reproduce | Create a parent page/child page (ensure the parent page does not yet exist). Then, create the "missing" parent page. Do a DB query on the pages just created. The child page will have a parent_id of 0. | ||||
| Additional Information | There are a couple ways to approach this: 1. When creating a child page without an existing parent page, create the parent page as well. Ensure the parent_id is populated correctly. 2. Allow the current behavior, but then retroactively assign a parent_id to the child page once the parent page is created. 3. Disallow creation of child pages with non-existent parent pages. I would suggest #1 would not break existing functionality/customization that depends upon this behavior, and the result would be expected (the Unix mkdir command operates in the same way, creating non-existing dirs down to the child dir if the -p option is specified). | ||||
| Tags | No tags attached. | ||||
