Ticket #1209 (new defect)

Opened 13 years ago

Last modified 13 years ago

Cancel button in the "Add media piece" and "Add reference" pages

Reported by: teemu Owned by:
Priority: major Milestone:
Component: generic Version:
Keywords: Cc:
Time planned: Time remaining:
Time spent:

Description (last modified by teemu) (diff)

The cancel button in the Add media piece page should take you to the page where you got to this page. Compare this to "back" button, except that in the case of "Add media pece" page the back button doesn't work right, either.

Same problem in the "Add reference" page.

Change History

comment:1 Changed 13 years ago by teemu

  • Description modified (diff)
  • Summary changed from Cancel button in the "Add media piece" page to Cancel button in the "Add media piece" and "Add reference" pages

comment:2 Changed 13 years ago by teemu

  • Owner changed from anonymous to teemu
  • Status changed from new to assigned

comment:3 Changed 13 years ago by tarmo

  • Owner teemu deleted
  • Priority changed from minor to major
  • Status changed from assigned to new

comment:4 Changed 13 years ago by pjotr

The "Add media piece" page "cancel" button can be changes to behave that way.

But for other cases - for example "reference". We are using "base_view" and "base_edit" there, and changing the action of "cancel" button might also affect all the other components of the system.

So, in content section we have these "content_add and choose" pages, but in other places it is not that way. At the moment the default action is - take user back to the folder he has started from(if we want to break the logic of the system - then we have to implement the new one that will work for all the things - not start making some chaotic changes that can backfire later).

comment:5 Changed 13 years ago by pjotr

(In [1511]) References #1209, this one does the trick for media pieces cancel button

comment:6 Changed 13 years ago by jukka

There seems to be two senses for 'cancel' and both have good reasons to exist.

  1. Cancel-as-back, when navigating pages like lemill_content_add, where you have to select one path and if it turns out wrong, cancel goes back to where path selection was made. The premise in these is that just choosing paths hasn't made any changes to existing stuff.
  2. Cancel-as-cancel-modifications, where you press cancel because you feel that changes you made were stupid or you really don't want to be creating new object X. In this case most important thing is that you are told that your changes were canceled and that canceled stuff is really gone. The page where you end up isn't so important.

This week I've been trying to get that functionality 2. to work and it works quite well, except when canceling whole editing process when editing existing mmedia, presentations or pilot object, as they save their state when chapters are changed. (Good thing is that they at least note that change is done.)

The problem with adding Cancel-as-back to pieces, references and resources(?) is that lemill_content_add -page, which would be the page where user got there from, doesn't have links to anywhere but forward. I've thought that in most of the cases cancellation is done in sense 2 and currently cancel-buttons take to content-front page when creating pieces, references and resources. If they took to lemill_content_add, that page would need some way to get out of there without adding new content.

comment:7 Changed 13 years ago by jukka

Me stupid. lemill_content_add has this text and I just can't read:

If you are not sure which option to choose you can have a look at the _FAQ_ or you may _go back_ to the previous page.

Well, then it should be bigger. :)

Note: See TracTickets for help on using tickets.