> By default, elog enties are sorted by their ID number.  When viewing a logbook in Full or Summary, they are
> shown in strict order of ID.  In Threaded, entries are shown in strict order of ID for the latest entry of each
> thread, and then previous entries (in reply to) back from the latest one.  
> 
> In collapsed mode, it is only the starting entry of each thread is shown (or the latest one if "collapse to
> last" chosen, but that's a detail).
> 
> I have a couple of logbooks where I'd like the default sorting to be by another numeric attribute that I enter. 
> 
> Now this works fine in Full or Summary mode.  In threaded mode (e.g. default for this forum, where every entry
> is shown but are grouped by thread), it works in as much as all the entres are there and in order, but it
> doesn't quite look the same as when sorting by ID - the replies are not each offset further right beneath the
> entry it is in reply to, but all just slightly offset to the first entry.  
> 
> If you try to [completely] collapse the threaded mode to just one line per threaded topic - it doesn't.  Looks
> (almost) the same as threaded.
> 
> I was hoping to get the list of entries collapsed to one line per thread, in order of the numeric attribute, but
> I cannot seem to get this to happen.   Have I missed something here?  Or is it possible at all?

This is not possible at the moment, but I will add it to the wish list.

> > By default, elog enties are sorted by their ID number.  When viewing a logbook in Full or Summary, they are
> > shown in strict order of ID.  In Threaded, entries are shown in strict order of ID for the latest entry of each
> > thread, and then previous entries (in reply to) back from the latest one.  
> > 
> > In collapsed mode, it is only the starting entry of each thread is shown (or the latest one if "collapse to
> > last" chosen, but that's a detail).
> > 
> > I have a couple of logbooks where I'd like the default sorting to be by another numeric attribute that I enter. 
> > 
> > Now this works fine in Full or Summary mode.  In threaded mode (e.g. default for this forum, where every entry
> > is shown but are grouped by thread), it works in as much as all the entres are there and in order, but it
> > doesn't quite look the same as when sorting by ID - the replies are not each offset further right beneath the
> > entry it is in reply to, but all just slightly offset to the first entry.  
> > 
> > If you try to [completely] collapse the threaded mode to just one line per threaded topic - it doesn't.  Looks
> > (almost) the same as threaded.
> > 
> > I was hoping to get the list of entries collapsed to one line per thread, in order of the numeric attribute, but
> > I cannot seem to get this to happen.   Have I missed something here?  Or is it possible at all?
> 
> This is not possible at the moment, but I will add it to the wish list.

OK, Thanks Stefan.

> > Well I didn't crash the server this time, and I could invert the image in the demo logbook by doing two rotations.
> > But, this is elog v2.9.0-2435, and I am using v2.9.2-2475.  And I remember there was a recent issue about the image manipulation at some point, so I went to the
> > download section to read the subversion listing to find where this occurred.  But you've changed subversion!  I couldn't find my way around it, so I not only could
> > I find the changefile that showed what happened for each subversion issue, but even how I could download the current (or indeed any past) subversion issue.
> > 
> > As far as I can recall, you made a change, I reported an issue, and you undid the change, or partially undid it.  Do you know when this was?  Could it be relivent?
> 
> I upgraded to V2.9.2, so please try again.
> 
> /Stefan

I can confirm this bug in V2.9.2. Also after submitting the entry, the orginal image is being displayed, with no rotation, resizing etc...

> I can confirm this bug in V2.9.2. Also after submitting the entry, the orginal image is being displayed, with no rotation, resizing etc...

Have you tried on the Demo logbook on the PSI server or on your installation. I just attached an image to this entry, rotated it twice, reduced its size 
and it works fine. The point is that I have to reproduce your bug in order to fix it, but it seems I cannot.

/Stefan

I've noted that you did your test with a PNG while he was reporting about a problem with a PDF. I'll give it a try with your server

Regards

Andreas

Cool: while it worked fine when I've created the entry, it stops working when I EDIT the entry that had been rotated! Actually it sometimes works and sometimes not.

As a workaround you can always go to "1:1" and then retry to rotate. That worked here.

Andreas

PS: I've noticed that the thumbnail PNG file only updated in the List view after I did a reload. I'm using Firefox 10.0.11 ESR on SL6.0.

 Hi all

Tested browsers on my SL6.4 desktop computer are Firefox 17.07, Konqueror 4.3.4. Here the rotation and rescaling is all wonky and the changes are  not saved when submitting the entry.

On my Android mobile phone (Chrome 28.0.1500.64) the images rotate and rescale nicely, but the changes are not saved aswell. I tried to force reloading and clearing my cache with all of the browsers.

The elogs I tested are served from Ubuntu 10.04.4 LTS and Debian 3.2.46-1 x86_64 running IM 6.5.7-8 and 6.7.7-10 respectively.

Martin

[13 Nov]
As my threads have lots of replies, I end up with a forest of ">" characters which makes it difficult to read
earlier quoted entries (what with word-wrapping of the browser).
I thought to replace the ">"s by a simple date entry prepended to the start of each reply. - much as I have 
given at the top of this initial entry.

So this is what I put in the config file:

....
Time format = %a %d %b %y
Date format = %d %b
Prepend on reply = [$date] \n
...

The time is used in the string for the Thread display.

Only I don't get the date, with the date format, prepended to replies but the time, in the time format, as

[Wed 13 Nov 13]

Now this is hardly a disaster, but any ideas why the date formatting is being ignored?

> [13 Nov] > As my threads have lots of replies, I end up with a forest of ">" characters which makes it difficult to read > earlier quoted entries (what with word-wrapping of the browser). > I thought to replace the ">"s by a simple date entry prepended to the start of each reply. - much as I have > given at the top of this initial entry. > > So this is what I put in the config file: > > .... > Time format = %a %d %b %y > Date format = %d %b > Prepend on reply = [$date] \n > ... > > The time is used in the string for the Thread display. > > Only I don't get the date, with the date format, prepended to replies but the time, in the time format, as > > [Wed 13 Nov 13] > > Now this is hardly a disaster, but any ideas why the date formatting is being ignored?

https://midas.psi.ch/elogs/Forum/67405

Why all the > Characters?  Maybe back off the version as stated in above link?  Not sure about the date issue.