[done] Back to displayimage from editOnePic

[johnwr]

When editing a picture with editOnePic.php (using link from displayimage.php), I can set title, description etc. Then I press Apply Modifications, and the info is saved. This works as a charm using latest CVS as of today (1.3).

But how can I get back to the displayimage.php without pressing my browser's back button twice? If I want to update the next picture in my album (or see the results), I have to navigate all the way back to the picture again from home.

Shouldn't there be some kind of "back to displayimage.php" feature there? Even maybe the breadcrumb?

I know I can use the mass setting feature of the album (editpics.php) instead, but sometimes these texts are best set when browsing.

John

[Casper]

Hi,

Good point.  One way is to make the thumb a clickable link back to the displaypic, by doing this;

In editOnepic.php, find (line 228);

Code Select Expand

<img src="$thumb_url" class="image" border="0"><br />

Change it to;

Code Select Expand

<a href="$thumb_link"><img src="$thumb_url" class="image" border="0"></a><br />


I will discuss with Gaugau and other devs worth of putting this in main code.

[Casper]

Probably a better way would be to make this change, which adds a back button, that returns to the pic display;

Find;

Code Select Expand

<td colspan="3" align="center" class="tablef">
                       <input type="submit" value="{$lang_editpics_php['apply']}" name="submitDescription" class="button">
               </td>

Change it to;

Code Select Expand

<td colspan="3" align="center" class="tablef">
                       <input type="submit" value="{$lang_editpics_php['apply']}" name="submitDescription" class="button">
              <br><a href="$thumb_link" class="button">$lang_back</a></td>

@gaugau, would one or both these be worth putting in the cvs.  No language changes required, and will help with nav from this page.
I can do the above if you like, but I suspect there is a better way.

[Tarique Sani]

Go ahead, add both and  commit it

[Casper]

fixed and committed.

[johnwr]

Great, works fine.

But when I continue to comment on files I find that the same applies to the multisetting feature of editpics.php.
When finishing updating texts, there might be a "Back" button next to the "Apply modifications" there as well?

John

[Casper]

From editpic.php the 'album list' link takes you back to the category page.

[johnwr]

So it does... Sorry, hadn't seen that...

[CasaDelGato]

Looks like the "Back" button hasn't made it into 1.3 yet.

What would be REALLY nice, is if the "Edit Description" button on the "DisplayImage.php" page would just insert the EditOnePic panel, say between the image and the filmstrip.
This would let me see the full size image, make my changes, click "Apply", and then just click on the next image.
It would make life so much easier to be able to QUICKLY edit the images after a batch add.
   Edit->Apply->Next, etc...

[Casper]

Looks like the "Back" button hasn't made it into 1.3 yet.

It is there, in editonepic, under the 'apply modifications' button.

[CasaDelGato]

Yes it is.  I hadn't updated with the latest code from CVS yet.
It's still kinda awkward when updating lots of pics, and things get rather weird when you are moving pics between albums.
If you change the album, and click on "Back", it takes you to the new album (of course).
This is rather annoying when you need to move a set of pictures from one album to another.

[Casper]

If you change the album, and click on "Back", it takes you to the new album (of course).

Good point, I actually hadn't thought of that.

This is rather annoying when you need to move a set of pictures from one album to another.

If you are doing several from the same album, why not use the 'edit pics' from the album, rather than 'editonepic'.  You can go through the album, choosing which pics to move where, and then just click the 'modify' once.

[Joachim Müller]

clicking "back" is a bad idea when using html forms that submit data to the database, or more generally speaking: when changing dynamic content. Nothing that can be done about this...

GauGau

[Casper]

I think CasaDelGato was refering to the 'Back' button I added to editOnepic.php, not the back button on the browser.

[Joachim Müller]

sorry, I didn't notice that one - my apologies to CasaDelGato then.

In my opinion the back button will confuse many users (they may not realize they have to click "apply" first, and the term "back" is usually "not so good" because you don't know where exactly you're going to be sent back to; some may think it means "undo"). I suggest removing the back button for the cpg1.3.0 release and add a feature to the next version with a tick box that says "return to pic view after changes have been saved" (checked by default) or make the back button only show up if the form has been submit at least once. Sorry I have to be a spoiler on this...

GauGau

P.S. The back button is currently not coppermine standards compliant. If we decide to keep it in, it should be made compliant.

[CasaDelGato]

I suggest removing the back button for the cpg1.3.0 release and add a feature to the next version with a tick box that says "return to pic view after changes have been saved" (checked by default)
Oooh, I like that.  Just PLEASE have the pic view it returns to be the one that it was started from - NOT the new album if the pics album was changed.  (Just show the "next" pic since the "current" one no longer exists there.)

[Casper]

Removed from CVS.

[johnwr]

So, what your saying is that if someone want to edit several pictures in an album using editOnepic in the cpg1.3.0 release, he/she has to aither use the browsers backbutton with care, or navigate back to that album again from home.
Isn't it better to keep the backbutton functionality (then of course coppermine standards compliant), and instead add the proposed tick box functionality to the next versions featurelist?

I for one use the current backbutton alot, and will miss it...
The issue could perhaps be eased somewhat if the breadcrumb is added to editOnepic?

Of course CasaDelGato's suggestion from his first post in this thread sounds nice and solves this best. But it is definately a bigger issue, perhaps for 1.3.1?

John

[Casper]

You can always add it yourself, just add the code mentioned earlier.

[johnwr]

Yes, I will of course do that. It just feels a shame to remove a working (and used) feature, but you're the bosses...