Susan Boggler wrote:
... due to the fact that you are using the article creation date for the event date, this seems to me to be confusing two different things. It would seem preferable to define the event date separately, it will give you a lot more flexibility.
Resources has a core calendar field plugin, it would seem to me better to use this to define the event date, and keep it separate from the article creation date. If you put all your event articles into a category called 'events' then you can specify the ordering of all the articles within the category, it will be up to you to arrange the articles in the way you want.
You got the idea... but that is the special thing about Resources core dates. It is actually build and designed around its two core dates. Section, Type and Module params do work with those only! In the early days of Resources, i already raised my complaint about this "different" approach. I was always missing the same usage/storage that J! core had.
If you deal with resources list order options and content-list module... you have to use the core fields "create" and "expire". I also use a modified calendar field... for better user input and display options... this extra field stores/overwrites the core fields. So, nothing had to be hacked or changed in Resources archtiecture and logic. That would have to much impact on upgrades!
Also, it was easy to utilize the existing option "Show only future articles..." this was half the way to go... I only had to ADD my "timeperiod" to limit/cap the list. Result is a working "Upcoming Events (for this month)" module.
Susan Boggler wrote:
...
With the featured items modules you can display the articles using this ordering. The only way the modules would fall short of what you want to do is that they do not at the moment support the calendar field, you would need to add the date also as a text field for it to show up.
As I mentioned earlier... the same issue is with Resources modules and params. I guess, it will never change for v1.5.x. It is the way it works. We have to use the two core dates (plus modification date)
In the past, I also opened a feature request for a CUSTOM/CALENDAR date field selection in modules. Makes sense to me, and would open a lot of possibilities. But that means it has to be optional for every core dates appearance in the code... maybe a technical challenge
Susan Boggler wrote:
...
We are thinking about creating some new modules that specifically support Mighty Extensions, which would then automatically support all the field types, this really depends on when there is going to be a new Mighty Extensions Resources for Joomla 1.7. They do seem to be planning this eventually, so eventually this should happen.
Currently, they (2) do work on the new Resources 6G, codename "black ice" ... early stages, but we already got some technical teasers Unfortunately, "Sergey" had to find and recruit new staff people! The next 2 months will bring new infos... Finally, there is light on the end of the tunnel. I will spend as much as sparetime in conversations and discussion with "Sergey" about the new version, its features and improvements.
