This project is read-only.

Is Orchard.List still deprecated in 1.7.x ?

Topics: Administration, Customizing Orchard, General, Installing Orchard
Mar 20, 2014 at 11:13 AM
Edited Mar 20, 2014 at 11:15 AM
Its module.txt mentions 1.7.2 but it is under Deprecated Modules in 1.7.x orchard.sln .
But in 1.x it is not deprecated ???

Shoudn't we get rid of deprecated modules in 1.7.3 and 1.8.
Mar 20, 2014 at 8:21 PM
Correct, it was rewritten for 1.x by Sipke and is back as a supported and recommended module.
Mar 20, 2014 at 8:30 PM
Edited Mar 20, 2014 at 8:30 PM
It seems to be same code in 1.7.x so it is ok for 1.7.x also ?
Mar 21, 2014 at 5:45 PM
What is differences between Orchard.List and Orchard taxonomies?
I read before that Orchard.List has been replaced with Orchard.Taxonomies.
Mar 21, 2014 at 10:15 PM
Edited Mar 21, 2014 at 10:15 PM
Totally different, search on wikipedia for Taxonomy.
The only problem of List is that it uses the old Container concept, List should have be rewritten using projections to allow some dynamic vision....
Mar 21, 2014 at 10:16 PM
Edited Mar 21, 2014 at 10:17 PM
Orchard.Lists enables you to create and manage lists of content items, while Taxonomies enables you to create taxonomies and terms, and associate those terms with content items (amongst other things).
Depending on what you need, Taxonomies may be better suited than Lists. Or vice versa. And then there's Projections, which also enables you to render lists of content items.
Try them out and see what would best suit your need.

We should however update the documentation once 1.8 ships, since the deprecated status of Lists is definitely deprecated. :)
Mar 21, 2014 at 10:17 PM
@Christian possibly, I haven't checked.
Mar 21, 2014 at 10:19 PM
So in 1.7.x it's also not deprecated ? Because they still appear under deprecated modules.
Mar 21, 2014 at 10:23 PM
Edited Mar 21, 2014 at 10:24 PM
@Sipke thank, List are always useful , especially in your new version, and many people won't migrate to 1.8 in actual conditions, so it would be better to correct and put them out of deprecated in 1.7.x.
Mar 22, 2014 at 12:10 AM
Maybe. On the other hand, it would mean we would have to support it in 1.7.x as well when issues are found.
Out of curiosity, how do you know many people won't migrate to 1.8?
Mar 22, 2014 at 5:12 AM
Edited Mar 22, 2014 at 11:45 PM
From various exchanges with people managing real time sites.
And until 1.x Is fixed in the 1.8 version it is not easy to move because code is changing each and every day , You have to change your code for db new vision but the tests you make one day are no more valid the next one.
And if you are in a phase where you need to add new features, without a dev team, you add them to the stable code...
So as Sebastien has already told, I think there should be 1.7.3 and 1.7.4 may be 1.7.5.