mdxthemes.com: What's going on?

Quote from: sottwell at Aug 16, 2014, 06:36 AM

Well, I am not able to work with this theme (Collab). Attempting to open some of the resources causes a Manager white-page. This is on Revo 2.3.1.

Hello Suzan,

Thanx for testing the template system/framework.

I think you forgot to reinstall the addon colorpicker. Its mentioned in the template installation instructions. You will be able to edit the theme resources once the colorpicker addon is reinstalled.

The styling depends on the theme resource selected. I am working on Collab video for 2.3.1. I had created a video for MDx Aaron Theme (Link: http://www.youtube.com/watch?v=BePi_F1Z-hc ) but its an old MODX version. Will post the video once done.

Update: MDx Collab Quickstart Package installation video

https://www.youtube.com/watch?v=qkI9kkT2Gng&feature=youtu.be [ed. note: trussframework last edited this post 9 years, 8 months ago.]

An interesting post. We purchased this template too, and had problems using it. In the end, we gave up & just reverse engineered the design and installed in Modx normally as any other html template.

But Sottwell's comments are interesting. Absolutely, this is a "full on" thing, it changes the manager and much more. We did eventually get a version up and running, but there there was no way to add Template variables to Article resources - like the manager functionality was changed.

On a general note, I'd be interested to know if this is they way people want Modx to go. It's very convenient to unplug something with lots of pretty custom manager pages etc, but the key attraction of Modx is that it is stable, the core remains intact. It would be terrible if Modx became like Wordpress - lots of 3rd party developers developing lots of add ons which just conflict with each other, alter core files and break the site when installing updates.

Unfortunately this will happen with any third-party extras system. The third party can do pretty much whatever he wants. The only thing stopping it is community pressure and negative feedback.

True. Having experienced 3rd party "Modx" templates a couple of times, I'm leaving them well alone.

I packaged up two very simple templates using the ThemePackagerComponent, and it turned out to be problematic, so I withdrew them from the repository. Once I figure out how to simply package a couple of templates, maybe some supporting chunks, and the theme css files, I'll try again.

@Susan - Let me know if you want me to create a MyComponent config file for you.

The thing I have against MyComponent for themes is that I like to have my support files in assets/themes/themename/, not assets/components/themename/. Actually the config file isn't a problem, it's remembering where I have to put everything.

Someday, you'll be able specify a path in the config file.

That said, I think it's a pretty widespread convention to put all extra files in assets/components/componentname and core/components/componentname. That's certainly where I'd look for them.

You can also put them where you like and modify the build.transport.php sources array to make sure they're found. MC won't touch the built.transport.php file once it exists.