By olafmol on

Hello,

our company currently uses MODx a lot for websites with CMS and custom modules. Our customers (and we) love the quick setup and development capabilities of MODx (we can set up a basic site in about 30 minutes), the power of TemplateVariable's, and the way we can integrate custom PHP code in "modules" in the backend CMS. Also the site structure tree view is very important.

What we're currently missing in MODx are a few important things for bigger websites: versioning, workflow, integrated multi-language front-end support, and multi-portal support (multi-portal: manage multiple seperate websites from 1 CMS).

I was wondering if Drupal 6.x gives us these options, and the ones we already have in MODx (especially the site structure tree view). Are there some additional modules we need to install to have the needed functionality or can we use a basic installation?

Olaf

⋅ Categories: Drupal 6.x

Comments

olafmol’s picture

olafmol commented

oh yes, i forgot to mention that having sitecontent-structure automatically corresponding with menu-structure is very important for our clients. When they create a subpage in the menu this should automatically create the corresponding content-page.

Olaf

olafmol’s picture

olafmol commented

nobody?

adhiarta’s picture

adhiarta commented

* New Core - 097 sports a completely new core, written from the ground-up. It uses the database modeling framework, xPDO.

* Completely configurable - run multiple sites on one core install, install the core outside of webroot, pick any name for the manager and assets directories, change and restructure every manager menu option.

* New parser - fully and infinitely recursive without using regex and no more eval().

* Improved caching options - goodbye 5000 page limit, hello any caching system you so desire to implement. This makes MODx an even better candidate for larger sites with lots of traffic. Also, any Element can now be specified to be treated as a cached or non-cached. There's even a clean path to completely override the default caching system to implement large-scale caching code like memcached.

* Override everything & lose nothing - as implied by the previous bullet, you can now extend or override any part of the MODx core cleanly and simply, all the while maintaining a clean upgrade path for future releases.

* New Transport Packages - Installing just got a whole lot easier. Create custom distributions and more.

* Contexts - this allows developers to assign different views of your site based on pretty much any criteria. This means native multi-sites, subdomains, running the core outside of webroot

* Core logging - Provides various error levels and output targets including ECHO, HTML, and FILE. You can also use it in add-ons for audit logs, error logs, debugging, or other logging needs.

* Unified, simple tags - supports calls to MODx resources broken across multiple lines, cached calls within cached calls, and allows PHx-like modifiers to be attached to any Element (Snippet, Chunk, TV, Etc.). And yes, the upgrade system for legacy sites takes care of changing over the old ones, in case you're curious.

* The Manager is MODx - we've created the new Manager for the MODx system by using the MODx API, ExtJS 2.1, and Smarty templates, as a demonstration of the flexibility of the new core and API.

* Completely new user system - all permissions are now handled via a robust. Attribute Based Access Control (ABAC) security model. There is built-in emulation of the old security model and your existing security setups for both the manager and webusers should be ported over fine during upgrades.

* Remote Transport Packaging - Install resources by downloading them from custom providers - either MODx-driven or 3rd party - from directly within the Manager.

* New Static Resources - now you can manage files on the filesystem (even outside of webroot) within the Manager.

* New Symlink Resources - exact clones of other resources in your site tree in as many places as you'd like.

* Support versioning, workflow