Open GoogleCodeExporter opened 8 years ago
which dashlet are you refering?
Original comment by ecm.exp...@gmail.com
on 14 Feb 2012 at 11:17
fme-gallery-plus-dashlet-0.5.1.jar
Sorry for the incomplete bug report.
Original comment by lucas.pa...@gmail.com
on 14 Feb 2012 at 11:23
I have the same setup (Windows7, Alfresco4.0c, lucene search engine) but I can
not reproduce the problem, i.e. the images are updated when I change the sort
order.
What are your other settings - can you attach a screenshot of the configuration
dialog?
Do you see any Javascript errors in your browser?
Original comment by Florian....@gmail.com
on 16 Feb 2012 at 8:59
That was a test server I removed everything so can't provide feedback on this
configuration anymore sorry.
However I reproduced the bug on my prod server:
ubuntu, alfresco4.0c, solr
Can't provide screenshot since I've modified it to make it work it wouldn't
make sense.
However:
I installed the javascript console extension.
I retrieved the code from gallery.get.js and made a few modifications to adapt
it to console code. (notified with //CHANGED in attached file).
Sorting "asc" retrieve a whole JSON, first one is woman3.png (Alice Beecher's
profile image :) )
Sorting with "desc" produces the same result.
Original comment by lucas.pa...@gmail.com
on 17 Feb 2012 at 8:59
Attachments:
Hi,
there seems to be a problem with sorting in Solr using short QNames
http://code.google.com/p/fme-alfresco-extensions/issues/detail?id=14#c2
jan
Original comment by ecm.exp...@gmail.com
on 17 Feb 2012 at 9:08
Oh. So maybe my test server was with solr too then... That would explain the
failure.
As I said I worked around this bug by sorting in javascript code. Which implies
handling the startindex/maxcount in javascript too in gallery.get.js.
It's less performant for lucene users and isn't hard for you to rewrite but if
you want it I can clean my personal comments and give it under the licence of
your choice (would be ASF licence I guess).
Original comment by lucas.pa...@gmail.com
on 17 Feb 2012 at 10:49
Original issue reported on code.google.com by
lucas.pa...@gmail.com
on 14 Feb 2012 at 10:00