Right. So how do we fix that? Is there not a variable we can pass into the template that will follow the MODx config?
And on the snippet hokey cokey (in, out, in, out, shake it all about)..
While I agree that [[DateTime]] is pointless, DateTime can also be fed a value (eg document’s published date) and a preferred format can be set. There are actually two different DateTimes in existence; I think the one I added to the Repo is not the one in MODx. I believe that in a best-practice blog, you’d have a date on the blog entry page in the same format as on Ditto’s listing, and would use a different template. I don’t think we want to overcomplicate MODx’s demo site with extra templates etc, so my final decision is that DateTime can go - I just want to remind people that it’s not just about outputting the current time.
PoweredBy and ListRelated can also go, but the main reason would be that we’re not using them.
Therefore anything we add should also be ’used’:
NewsManager etc - Sure. How about we configure this to edit the ’Features’ section, which would help demonstrate that it’s not just about adding news?
Most of the others make sense too. I would like to see Custom Alias logic in the core.
But.
WebUser Signup Notification: Would require reminding people to change the default admin email address. In fact, looking at the code, that has an address hardwired into itself rather than using the User 1 email address (or the "from" address that is set in MODx config). Mind, User 1’s email address is "Your email goes here" which will presumably cause mail to error. In fact, it’s such a can of worms that it would need to be "off" by default, and as such I’m not convinced there’s a benefit in including it.
-
MODX Staff
- 12,272 Posts
Let’s skip the web reminder email thing on creating a new webuser. That’d make a great addition to a "content pack" if we ever get around to doing those/that.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
-
☆ A M B ☆
- 24,524 Posts
I’m not real happy with "modx_charset". It leaves us stuck with the same explicit naming convention as the etomite_charset name did. Why not something more generic like "site_charset"? Then we can call MODx bluedonefuzzy if we want to with no problems.
Jared an I made a snippet that does the UltimateParent thing and SectionRoots thing plus reverse id lookup in one snippet.
Maybe that could be used instead of ultimate parent or next to it.
its not in the repository yet so I attache it here.
-
MODX Staff
- 12,272 Posts
Any objections to switching to site_charset or default_charset?
Also, what really reamains to change on the demo content? I suppose the Comments info needs to be rewritten...
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me