In thinking about this issue, I'm leaning towards ditching the
"friendly" URLs and using the integer IDs as resource identifiers as
is typical in most rails apps. The current implementation complicates
this and other issues without delivering much value. Plus, it
violates the cardinal rule of URLs, which is that they shouldn't change.
I'm going to start this change tonight, so if anyone has any
objections, please speak up.
Cheers from NYC,
Luke
On Mar 31, 2007, at 1:20 PM, James Kebinger wrote:
Hello everyone, in fixing the in-place editing of titles (http://
dev.rousette.org.uk/ticket/486) on the individual context and
project pages, it looks like I've uncovered a larger issue - when
you edit the name of project, its url changes. If you do this from
the project page, you're now at a page with an invalid url, so
anything else you do on that page will cause an error.
So I'm opening up for discussion how you want to handle this from a
user experience point of view. The options I've thought of are:
1) ditch the in place editing
2) issue a redirect when the name is changed in this manner
(canceling out the benefit of the in place editor...)
3) create the page with urls by project id instead of name so they
won't be affected and sweep through the page to change other
affected fields (ie the project field in the new action form)
from a technical standpoint, it looks l like 3 is fairly easy to do
(its possible to use an RJS with an Inplace-editor), but the url
will still be "broken" so if the user were to hit reload or do
something else and hit "back" there would be an error..
any thoughts?
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
