MODx Bug/Feature Tracker and Feature Requests
Welcome to the MODx CMS Tracker. Please choose the appropriate project from the drop down menu and provide as much information as possible regarding your server environment and browser. Thanks!
FS#89 — no visual warning when using an existing alias
Attached to Project —
MODx
Opened by Remon (Remon) - Monday, 24 October 2005, 01:15PM
Last edited by Jeff Whitfield (Bravado) - Saturday, 19 November 2005, 02:29AM
Opened by Remon (Remon) - Monday, 24 October 2005, 01:15PM
Last edited by Jeff Whitfield (Bravado) - Saturday, 19 November 2005, 02:29AM
| Task Type | Bug Report |
|---|---|
| Category | Core Distribution |
| Status | Closed |
| Assigned To |
Jeff Whitfield (Bravado) |
| Operating System | Linux |
| Severity | Medium |
|---|---|
| Priority | Normal |
| Reported Version | TP3.2 |
| Due in Version | 0.9.5 |
| Due Date | Undecided |
| Percent Complete |
|
Details
Hi,Using Firefox on a linux box, I got this behaviour that when trying to set an allias for an existing document which allready exists (the allias) the document isn't saved, but instead the page "hangs", nothing happens.
After reloading and reopening the page for editing, the allias name is in the allias field, but the renderer still doesn't use the alias (of course :-) )
By the way, very nice feature this "friendly alias path", solved this issue more or less (I have documents with the same name on a multilingual site, so this new feature is a great solution!)
Have a nice day,
Remon
This task depends upon
This task blocks these from closing
Went to demo site manager, home page, copied alias (index).
Went to other tricks page, edited, pasted alias in (index) and saved. No warning.
So, when aliases are set to off, we get no warning. However this is a problem if you later reallize you need to turn them on and you've got duplicate aliases.
When use doc aliases are set to on, you do get the JS warning as expected.
So in a way, the issue is resolved, but in a sub-optimal way that can lead to other problems later.
Suggestion for 0.9.1: i
If FURL is set to off on the config, disable the form field. Add a help text link to the side: Why is this disabled? Clicking the link would then pop show a help explanation (scriptaculos effect, of course!) and offer a link to the just turn them on without leaving where you currently are.
The "hanging" problem was due a Firefox problem, after reconfiguring this problem has gone for me!
The suggestion you make is very helpfull indeed!
Thanks