| Summary: | Folder/file rename results in Orion responses being displayed in the editor | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Maciej Bendkowski <maciej.bendkowski> | ||||||
| Component: | Client | Assignee: | Malgorzata Janczarska <malgorzata.tomczyk> | ||||||
| Status: | RESOLVED WORKSFORME | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | malgorzata.tomczyk | ||||||
| Version: | 4.0 | ||||||||
| Target Milestone: | 4.0 RC1 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
This is not only for folders that are projects but for all top-level folders. The reason is because after renaming we are redirected to /workspace/mtomczyk/project/FolderName instead of /file/mtomczyk/FolderName. Fixed Created attachment 236545 [details]
Error responses in the editor
I've encountered a similar problem today, where a folder rename did not update the page resource, hence the error response was displayed in the editor (see attachment).
Sorry, I meant file not folder. The page resource file name should have been updated to 'subjecta.js', but was kept the same. Steps to reproduce: 1. Click the parent folder (in my case mailer). 2. Select the file, but don't click it. 3. Hit F2, and rename. And this only happens on the mini-nav view. Project-nav doesn't have this problem. This doesn't happen any more. |
Created attachment 235921 [details] Rename error response 1. Create a project 'A'. 2. Navigate into the project. 3. Move up to the parent folder. 4. Notice, project information should be still rendered on the right-hand side, while the navigator changes. 5. Rename project 'A' top-level folder. 6. Notice how the editor renders the server response (see attachment).