What are the (dis)advantages of Pimcore?

Question

I am looking for a CMS based on Zend Framework and I read about Pimcore. Now I have some questions about it:

• Does anyone have experience with this CMS?
• Wh

Answer 1

I think, pimcore is a very good solution for someone with zf-experience. Good documentation, good community, small learning curve.

One disadvantage: there is no frontend because you have to write your own controllers and views. But this can be a big advantage if you hate customizing frontends (like typo3 with all the css you have to customize).

Answer 2

Now its already version 1.4.4.

I am using it for some time, for all my web projects. It is really an excellent core for developing various projects.

I think that the biggest advantage is that there is no frontend module. You just make custum one. And I had no problems so far updateing the pimcore, becase you only update backend, and really nothing can go wrong if you havent changed core. Maybe some miner updates on frontend are needed but i had no such exemple for now.

Other advanategs: - plugin development is nice arhitectured, and you can use extjs for almost any purpose. Since version 1.4.3. you can also put your views and controllers in plugin, so you dont have to code like login and other stuff more than once. - WebDav for Assets managment - pixlr for image editing - very good page and subpage editing (you actualy see page how it looks while editing), you can develop custom elements of page easily - community and pimcore team is very helpful on forum - ...

Disadvantages: - people that are not really in to computers find it difficult to edit simple page, people that like to explore a bit and are not afraid to click and try fond it interesting (you have to learn custumer in beginning)

For me its very inutiutive, but I am a programmer.

If you have Zend Framework background I think its very good choice. After a year of usege on my projects I am very satisfied that I decided to use and learn Pimcore.

Answer 3

Pimcore rocks as an advanced enterprise cms, ams, pims, what have you. We have been using it in a corporate environment as our asset management system since v1.2 and are using v1.4.1 right now and loving it.

General Disadvantages (when compared to the run of the mill popular cms's like joomla/drupal/wordpress etc):

1. Steeper development learning curve, need to know zend framework and extjs if you want to modify the admin area or add plugins (although i consider most of the older cms's to be a nightmare to develop on).
2. Advanced admin UI, Not end user friendly for standard cms tasks like adding a page. Not immediately clear how to add a page, add to custom navigations, etc.
3. Coder required to get it setup and really use it to its potential.
4. Backend plugin work requires both front-end/extjs/ajax knowledge and backend/php/xend framework/mysql knowledge.
5. Runs best on a dedicated machine, needs lots of processing and power for the zend framework to be fast and putting on shared hosting requires some tweaking to get working.
6. Still early product so some things like branding the admin and other minor stuff is not that flexible yet. Not everything is completely easily modifiable without touching the core yet.
7. Not a ton of themes or add-ons yet.
8. A little tough to contribute, can't just fork it on github etc.
9. No front end login/registration/members area module, you need to code it yourself if you need front end user authentication as of present.

Advantages:

1. From an architectural standpoint it is super powerful and extensible and can do anything with it since it is completely based on an object/asset/document model with an API to use those objects and a plugin architecture to customize the admin. This is a great model for a catalog of items, which most cms's revolve around but not limiting in any way.
2. Coding is pleasant using the Pimcore API and Zend Framework/ExtJS and fairly bug free for major features.
3. Lots of built in features out of the box that enterprise systems need like users/groups/permissions, versions, scheduling, cacheing, cdn, and i18n internationalization.
4. Lots of wow factor user interface stuff in the admin using ExtJS framework like drag and drop, grids, editing objects.
5. Modern website editing features/flexibility with in place editing, drag and drop/reorder content, content blocks, snippets and so on.
6. Not very many roadblocks or limiting factors, basically it's open to anything you want to do and rarely do you run into something that is a complete road block requiring editing core files.
7. Most use cases are covered and flexible enough to allow improvements and customization without being a nightmare.
8. Built in upgrading mechanism.
9. Plugin architecture.
10. PHP Unit testing plugin.
11. Built in admin UI for creating extensible classes and objects.
12. Admin UI for laying out the screens that allow editing object data using many preconfigured ui controls like textboxes, sliders, checkboxes, etc.

Even though Pimcore in early phases it is an excellent enterprise cms framework and will handle any task but be prepared to dive into code figure out stuff as you go. I'm sure this will change as it matures and they make it easier for people to contribute code and open up a marketplace for addons. Currently I wouldn't say it's a replacement for regular websites using wordpress or drupal with tons of themes and addons and end user UI fanciness for normal website cms operations. But since you are a coder and don't mind writing your addons using extjs and zend then it's well worth the flexibility in my mind. My recommendation right now is to go with concrete5 if you want a modern Zend MVC CMS website replacement that is easy to use but still pleasant to develop on. Over time pimcore will give all cms's a run for their money though due to it's awesome architecture.

Hope that helps!