Closed orchardbot closed 9 years ago
@Piedone commented:
Good idea! I'd also prefix the module name with deprecated. It's ugly but worth it to prevent anybody new from using those modules.
@bleroy commented:
Changing a module's name: bad, bad, bad idea. This will make all the tables invalid. Welcome back :)
@bleroy commented:
Or you meant the pretty name? If so, then yes, why not, although I'd prefer one marker, and the UI to render a prefix depending on it, rather than change the pretty name in the manifest.
@Piedone commented:
Yes, I meant just the name written in the Module.txt.
erik_oppedijk commented:
Maybe first start with the description?
I do like the idea for the marker, so the dashboard can display additional information about the use of deprecated modules.
@Piedone commented:
MJost commented:
How to proceed here? I think it is a small things with a huge impact for people who are new to Orchard.
So how about just prefixing the display name of those modules and their features with "Deprecated - " that are deprecated? And prefix their description with "See documentation for deprecation information."
I was thinking the same.
Could also change the Category, so they are all grouped together in the Modules screen.
Even better.
Good idea.
Is this the complete list?
I think yes.
This will be solved as part of #5271.
erik_oppedijk created: https://orchard.codeplex.com/workitem/20001
When in the admin Module selection screen, all modules seem equal, there is no indication to the end user.
There is no indication that lists, media, mediapicker and rules are deprecated. Possible solution: add the word deprecated to the module.txt FeatureDescription: Deprecated: A basic container-enabled content type.