I just upgraded to V 2.4.1.  In the edit window from the front end when you attempt to hit "save" it acts like the apply button in the backend of joomla.  The item is saved right away but the window does not close.

I can confirm this bug.

Website: gettingourcountryback.org

Using Firefox 3.6.10 on Kubuntu Linux 10.04 - KDE 4.5.1

Editing from the front end of the site.

When writing a new article and clicking save it saves fine, but leaves the form open as when you click "Apply" in the back-end. It should save and close the window.

This is makes adding articles to a site more difficult for users that are not tech-savvy.

Can anyone else confirm this behaviour?

This is not a bug. This how it was designed. You can close the window by clicking cancel or the modal close button.

I understand what you are saying, but there is a logical break here.

In the backend, clicking save closes the editing window. There, you have one more button called Apply.

In teh front, the Apply button is missing, and the Save button do not close the editing window.

This is what I would call bad usability. Whatever you do, make sure that you do it the same way all places.

OK you can rename "Save" button to "Apply" if you find it so important. Also as you mentioned you are on frontend not on backend it is not the same. At backend save button redirects you to the list of the items. This does not apply to front end.

Svein Wisnaes said:I understand what you are saying, but there is a logical break here. In the backend, clicking save closes the editing window. There, you have one more button called Apply.

In teh front, the Apply button is missing, and the Save button do not close the editing window.

This is what I would call bad usability. Whatever you do, make sure that you do it the same way all places.

The expected action in the frontend is that the save button closes the window and return you to the page where you clicked on the edit link.

In other words: it should save-and-close.

As the edit window covers the website, I understand that an apply button do not make too much sense. So the right button is Save. But as it do not make sense to have an apply button, it does not make sense to have a different button work the same way. When you click on the save button, you need to get the window closed so you can see the site. Forcing people to click one more time to get to that is not the right way to go about things.

I normally never assume that I am representative for the majority of users. Normally, I am absolutely not representative for the majority :-) But in this case I think that the vast majority expect the window to close when they click on save and gets confused when they have to click on cancel to close it.

Remember - a lot of people have monitors with limited vertical space - mine is 1280x800 - and if you have Firefox with an extra toolbar, you suddenly have about 600 pixels available of vertical space. This means you loose a bit of information and need to scroll. And in a scenario like this, things should definitely behave consistently.

I would put it this way: If you find the Apply function so important, it is better that you add an Apply button and make sure the Save button saves and closes the window.

Maybe you are right. Maybe this what most of users expects. But this is how it works. If you do not like it you can implement your own solution and commit it so we can add this. But in any case this is NOT a bug (you confirmed it is!). You can post your feature requests to the corresponding forum section.

Svein Wisnaes said:The expected action in the frontend is that the save button closes the window and return you to the page where you clicked on the edit link.
In other words: it should save-and-close.

As the edit window covers the website, I understand that an apply button do not make too much sense. So the right button is Save. But as it do not make sense to have an apply button, it does not make sense to have a different button work the same way. When you click on the save button, you need to get the window closed so you can see the site. Forcing people to click one more time to get to that is not the right way to go about things.

I normally never assume that I am representative for the majority of users. Normally, I am absolutely not representative for the majority :-) But in this case I think that the vast majority expect the window to close when they click on save and gets confused when they have to click on cancel to close it.

Remember - a lot of people have monitors with limited vertical space - mine is 1280x800 - and if you have Firefox with an extra toolbar, you suddenly have about 600 pixels available of vertical space. This means you loose a bit of information and need to scroll. And in a scenario like this, things should definitely behave consistently.

I would put it this way: If you find the Apply function so important, it is better that you add an Apply button and make sure the Save button saves and closes the window.

If I was a programmer, I would do exactly that :-) But yes, as you have said that this is how you have designed it, it is not a bug as it would appear to be in the first place.

I will add it as a feature request and I think you should seriously considering adding the Apply button plus changing the Save function so that it works more the way people expect it to. After all, software should make things easier? :-)

Thank you for your time. The feature request will be there soon.

Eehh.... I am looking for the "Feature request" section, but can not see any. *confused*

I have been trying to find out if JoomlaWorks has a bug tracker somewhere where we can add bugs and feature requests in a normal way instead of the forum where it is impossible to track the development of things?

This might be working as designed, but how about an indication on the popup that the item has been saved? There is the little flash and of course the window below shows a message, but there is no indicator that it's been saved on the popup itself, which is important for a novice user. It would be awesome if a little indicator appeared next to the save button.

Scott, how did you resolve this (if at all) and what modules are you using on your site? My K2 blog does not look like yours. Thanks :)

The Cancel button does not seem to do anything. Also, my edit doesn't open in a modal window, but in full screen. I am using user templates, could this be part of the problem?

Thanks,

Josh


Lefteris Kavadas said:This is not a bug. This how it was designed. You can close the window by clicking cancel or the modal close button.

Hi. Probably you have some javascript errors in your page which prevent K2 working as it should.



jsmith1611 said:The Cancel button does not seem to do anything. Also, my edit doesn't open in a modal window, but in full screen. I am using user templates, could this be part of the problem?
Thanks,

Josh


Lefteris Kavadas said:This is not a bug. This how it was designed. You can close the window by clicking cancel or the modal close button.

I have exactky the same problem. The editor covers the whole screen. Looks like the article is saved, but if I click on CANCEL absolutely nothing happens. There is no way to close the editor and get back to site content. Anybody knows how to solve this?