-
MODX Staff
- 12,272 Posts
The default content should not install any snippets or plugins imo. We originally had it do it for the custom snippets that were with the original content, like the 404 forum. Now that it’s (being) converted to an eForm, it’s not gonna be necessary. I even think the associated chunk templates should be part of the base content install in fact.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
Just stopping by to say very nice going guys. I can see lot’s of cool changes and fixes taking place.
Keep up the good work.
Quote from: PaulGregory at Sep 18, 2006, 04:00 PMSee: http://modxcms.com/forums/index.php/topic,7185.0.html for images. Ryan’s been working hard making MODxLight-beta work in IE etc (which was indeed full of bugs).
Thanks Paul, that’s great now I can go and test this one
Really a very cool things to have a "flat" and light design !
But I think I’ll go with the Black theme
My bad for not reading the Development and Coding forums
.: COO - Commerce Guys - Community Driven Innovation :.
MODx est l'outil id
I’m pleased that we’re able to take the time to polish 0.9.5; getting the default content right is a big job but once it is done it should be easier to maintain for 0.9.7 etc. I know there wasn’t the time to update things when 0.9.2.1 came out. I know individuals have been able to update all the snippets themselves, but many turn to the forums first before finding out if there’s a new and better solution. That’s one of the reasons I’ve deliberately removed all reference to "New" and "Updated" in the snippet and plugin descriptions.
The one thing I keep in mind throughout all this process is the huge leap that people will see on the OpenSourceCMS demo, and the fact that it will be easier to point people to a best-practice example site using modern snippets.
The biggest item left to do is changing the blog. Is this waiting on finding whether Ditto 1.1 is ready?
In other news, DropMenu, NewsFeed and PageTrail are now gone on .it . I’ve found 3 more snippets that do not seem to be used in any of the templates. Obviously, we *can* have default (optional) snippets that aren’t used in the default content, so this is now a question of whether these 3 snippets should stay in the core distro:
PoweredBy
It seems none of the templates actually use this snippet which claims to be "A little link to MODx" but in fact doesn’t output a link at all - instead it outputs text including the MODx version number.
Declaring to the public which version of software you’re running is typically not a good idea, so it seems OK to kill off this snippet.
Breadcrumbs 0.9d
Configurable breadcrumb page trail navigation. The third most downloaded resource in the Repo.
I’d therefore favour keeping it in the optional snippets, but I can equally see the case for dropping it because people can clearly find it easily in the Repo.
ListRelated "1.0 beta 1"
Ryan’s version of Jared’s eto snippet, which differs from Dimmy’s version of the same snippet. (Dimmy’s version is in the Repo). I’d therefore favour ditching it.
I have updated all of the AjaxSearch calls in the sample content to work correctly on modx.it
-
MODX Staff
- 12,272 Posts
Good call Kyle.
Let’s keep breadcrumbs in (or whatever version is most appropriate). We should also probably selectively choose a few other "high value" snippets as well. I’d like to see an example/explanation of @INHERIT being used too, as that’s just too dang handy in general.
Nuking ListRelated and PoweredBy is fine by me.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
-
MODX Staff
- 12,272 Posts
Kyle... any chance you could get the search highlighting plugin to work too?
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
The other Top 5 snippet is MaxiGallery. I am not comfortable making that part of the ’official’ core install (because it breaks awasy from core document structure principles) but it would look nice in the OpenSourceCMS demo.
Agree on @INHERIT.
Quote from: kylej at Sep 19, 2006, 09:10 AM
If a user decides to install the default content but none of the snippets, the default content will look like garbage. So somehow we should probably make sure the required snippets/plugins/etc.. get installed when the default content is checked.
The best method of indicating this would be to check all the required snippets etc and gray out the option of changing them until the basic content is selected. I don’t know how much fuss that would be to change.
MODX Staff
