Description
Upon attempting to clone a location, a page reload is necessary to view the cloned location. If the cloned location has any assets, then when click it you will be taken to a loading screen that never finishes loading. UI elements cannot be interacted with. Manual intervention in the sqlite database is required to restore the room to a usable state (deleted all shapes in cloned location).
Steps to reproduce the behavior:
- Installed planarally according to fully manual installation on website.
- cd into server directory and run 'python3 planarally.py'
- Using browser, go to localhost:8000, create new user and create a new room from scratch.
- Click the settings gear, select assets, and upload an asset. Drag and drop onto the default location ('start')
- Click on the location icon (compass) and select the settings gear next to the 'start' location. Select the 'admin' submenu and click on 'Clone this location'.
- No new location appears. After reloading the page, the cloned location in visible in the location menu. The original is on the left, the new one is on the right.
- Click on the new location.
Expected behavior
The cloned location appearing beside the original location without requiring a page reload. When accessing a location with assets, I am able to do so without putting the room into a continuous loading screen.
Version Information
- OS: Ubuntu 26.04 LTS
- Browser: Mozilla Firefox
- Version: 149.0.2
- Planarally version: 2026.1.2 (Commit c677f97)
- Python version: 3.13.15
Additional context
I believe that this issue may be related to the more minor problem that occurs whenever a room is cloned. When cloning a room with no assets, a page reload is still necessary to view the newly created room, but after reloading the newly created room it is accessible & seems to have all the correct information (checked by creating basic tokens, positioning them & adding a tracker to one). Whenever a location is cloned, an exception occurs, and when accessing a cloned location with assets, more exceptions occur (I did not dump stack traces because I understand that to be in poor form for a bug report, but if they might be useful I can add them).
Description
Upon attempting to clone a location, a page reload is necessary to view the cloned location. If the cloned location has any assets, then when click it you will be taken to a loading screen that never finishes loading. UI elements cannot be interacted with. Manual intervention in the sqlite database is required to restore the room to a usable state (deleted all shapes in cloned location).
Steps to reproduce the behavior:
Expected behavior
The cloned location appearing beside the original location without requiring a page reload. When accessing a location with assets, I am able to do so without putting the room into a continuous loading screen.
Version Information
Additional context
I believe that this issue may be related to the more minor problem that occurs whenever a room is cloned. When cloning a room with no assets, a page reload is still necessary to view the newly created room, but after reloading the newly created room it is accessible & seems to have all the correct information (checked by creating basic tokens, positioning them & adding a tracker to one). Whenever a location is cloned, an exception occurs, and when accessing a cloned location with assets, more exceptions occur (I did not dump stack traces because I understand that to be in poor form for a bug report, but if they might be useful I can add them).