Order elements in object relations in content/edit

Author Message

Damien MARTIN

Tuesday 12 October 2010 8:21:01 am

Hi there,

I currently have a class with an "object relations".

But my problem is that : when I'm in content/edit, the list of possible objects is unordered (a single selection dropdown list)

For exemple :

  • Mario
  • Luigi
  • Koopa
  • Bowser

Instead of :

  • Bowser
  • Koopa
  • Luigi
  • Mario

If the length of the list was small it will doesn't matter... but the list is 300+ elements.

I already tried using sorting method in the folder view (because all the elements are in the same folder) but it has no effects.

And has it is a view inside ez (and not an overrided node), I can't simply alter template.

Is there a way to force elements sorting ? (using code or configuration files)

Thanks in advance,

Damien

Damien Pobel

Tuesday 12 October 2010 9:53:14 am

Hi Damien,

Hum, your problem is weird, because if you look at the edit template of object relations datatype, the fetch function used to retrieve the possible elements has the sort_by parameter set to name. Perhaps you use an old version of eZ Publish without this behaviour or an override of this template ?

Cheers,

Damien
Planet eZ Publish.fr : http://www.planet-ezpublish.fr
Certification : http://auth.ez.no/certification/verify/372448
Publications about eZ Publish : http://pwet.fr/tags/keywords/weblog/ez_publish

Maxime Thomas

Tuesday 12 October 2010 9:58:15 am

Hi,

A kind of solution / to try :

The object relations normally do follow the sort you set in the back office.

So :

1 - Get in the folder / container content of your 300 nodes

2 - Sort those by the criteria you want it to be sort (for example, by class or name)

3 - Go back in your content with the relation attribute

This has to work.

Maxime Thomas
maxime.thomas@wascou.org | www.wascou.org | http://twitter.com/wascou

Company Blog : http://www.wascou.org/eng/Company/Blog
Technical Blog : http://share.ez.no/blogs/maxime-thomas

Damien MARTIN

Friday 15 October 2010 1:20:25 am

Hi,

I tryed to setup the sort type in administration : I went to my folder and setted it up to "Name" "Ascending".

When I'm in the administration siteaccess and in content/edit, elements are sorted correctly.

When I'm in the public siteaccess and in content/edit, elements are not sorted correctly.

For information I'm running eZ 4.2.0

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 18 2025 02:04:58
Script start
Timing: Jan 18 2025 02:04:58
Module start 'layout'
Timing: Jan 18 2025 02:04:58
Module start 'content'
Timing: Jan 18 2025 02:04:59
Module end 'content'
Timing: Jan 18 2025 02:04:59
Script end

Main resources:

Total runtime0.8540 sec
Peak memory usage4,096.0000 KB
Database Queries63

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0059 589.2578152.6406
Module start 'layout' 0.00590.0030 741.898439.4844
Module start 'content' 0.00890.8437 781.3828607.4141
Module end 'content' 0.85270.0013 1,388.796916.1250
Script end 0.8539  1,404.9219 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00350.4147160.0002
Check MTime0.00150.1779160.0001
Mysql Total
Database connection0.00070.082910.0007
Mysqli_queries0.790592.5652630.0125
Looping result0.00060.0704610.0000
Template Total0.825396.620.4127
Template load0.00200.229920.0010
Template processing0.823396.414220.4117
Template load and register function0.00010.012310.0001
states
state_id_array0.00090.107010.0009
state_identifier_array0.00080.093920.0004
Override
Cache load0.00170.1961480.0000
Sytem overhead
Fetch class attribute can translate value0.00060.064530.0002
Fetch class attribute name0.00130.151070.0002
XML
Image XML parsing0.00160.189230.0005
class_abstraction
Instantiating content class attribute0.00000.001880.0000
General
dbfile0.00130.1470280.0000
String conversion0.00000.000940.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1node/view/full.tplfull/forum_topic.tplextension/sevenx/design/simple/override/templates/full/forum_topic.tplEdit templateOverride template
4content/datatype/view/ezimage.tpl<No override>extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tplEdit templateOverride template
4content/datatype/view/ezxmltext.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tplEdit templateOverride template
7content/datatype/view/ezxmltags/paragraph.tpl<No override>extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tplEdit templateOverride template
2content/datatype/view/ezxmltags/li.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/li.tplEdit templateOverride template
2content/datatype/view/ezxmltags/ul.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/ul.tplEdit templateOverride template
1content/datatype/view/ezxmltags/link.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/link.tplEdit templateOverride template
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 22
 Number of unique templates used: 8

Time used to render debug report: 0.0001 secs