This should be possible to implement but there are complications:
1. List fields would be ordered by the value of the options not the displayed text
2. Multi-select fields would give meaningless results
3. There would be a slight performance hit.

Another place it could be used is in the category list view where you could sort by clicking the column headings.

I'll look into it - but its likely to be a few weeks before its available.

I think it could be limit to certain type of custom fields in the first place like text fields maybe checkbox (fields is check or not)
And yes of course the performance have to be considered.

It couldn't be a checkbox with multiple options - i.e. a field with more than one checkbox since there would be more than one value stored in the same field.

I've added it to the TODO list - hopefully for version 1.1.0

Hi, happy new year !
Any news about this because we have a loooot of project whch need this possibility

Thanks

I had been struggling to find a mechanism to do this but have now got it working for the core fields - next step is to configure the menu item, pass the parameters through and do the extra database join.

I'm going to start with a single ordering option i.e. just by one column/custom field and not with a secondary choices (I'll use the Joomla default sorting options here instead).

I hope to have something for you to play with in the next couple of days

Yessss ! We can't wait to see this ! And yes we understand the difficulty to create this after having make a little exploration of all of this.

I have something for you to experiment with - I'll update the development build for you to try at https://www.easylayouts.net/support/discussions/latest-build-of-easylayouts

At present it allows you to sort articles in featured view, category blog and category list views. If it does what you need then I can look at extending this to modules too.

We have try and.... Now in menu linik edition in back office we just have Details and Custom fields Condition fields tabs with Js error : "ReferenceError: setCustomfieldChoice is not defined" and the ordering don't work. Tested on 3 websites (2 dev and 1 very fresh)

That's interesting - the function should be available.

Can you try unzipping and uploading this file to administrator/components/com_easylayouts/models/fields/elscustomfieldformeunitemconstraint.php - does that resolve the issue?

Ok we get the "full" backoffice menu screen but the ordering still don't work :-/

Can you give me access to the dev site so I can check the queries it uses. It works fine on my development servers

I give you acces to a fresh Joomla but we have a real project bugged too but we will see aftrer because we have done a lot of other things on it and it don't work as well on this fresh

• Blog articles
  
• Add a date fields in group and applicates to the category (check if show on blog view) and add a custom date to the articles
  
• add Easylaout and create Blog and blog:article view > the custom field is not reachable related to the ordring mis-function, I suspect this of course
  
• Modified the home view as a blog view and override the ordering
  

Where Does I make an mistake?

Here the other website access in real condition.

I've looked at the dev site and installed eXtplorer so I could add comments in the code.

I found the issue - I had assumed (incorrectly) that there would be filtering involved if the page was ordered so without it the re-ordering was ignored. It works ok on the dev server now (the file I changed was plugins/system/easylayouts/easylayouts.php)

Can you check your issues are resolved by that change? Thanks

Yeah it seems OK : I go testing this changed file on our real project website
Do you know why I have the "No suitable custom fields" in custom fields widget in blog:article layout on this dev website ?

On our real project :

• Ordering is OKay
  
• We have definetly lost the custom fields on category intro article
  

So I'm not sure what I prefer : custom fields showing or ordering

It seems OK ! I have other issue I'll post in issue section ;-)