Main failures of popular CMS

Question

CMS

In fact, many of us have worked with popular CMS (especially for online store engines). What disadvantages and inconveniences (which caused the most headaches) have you ever met? We are talking about development for these engines and not the user interface and so on. Only inside.

Answer 1

The main disadvantage of all popular CMS is that they are written in PHP.

Answer 2

1C-Bitrix is ​​a synonym for a headache, because you would not wish even an enemy to write your own components. The pain is slightly relieved after a lot of practice, but does not go away.

Answer 3

The cons are the same everywhere - shitty code, shitty API, huge resource requirements, poor documentation, difficulties with deployment and synchronization.

Answer 4

Security:
they like to break the popular and post recipes on the net. In addition, it is easier to break because. there are source codes
Weight: similar CMS like to provide EVERYTHING, as a result the set of functions, classes grows up to rather impressive values. It also leads to thick OOP, MVC and it will not be easy to figure out such code ...
Speed: CMS does not know what it will be used for, however, it must be scalable (in terms of functionality). As a result, modularity appears, simple APIs, common data structures, which almost completely cuts off any opportunities for optimizations.
Stability: The above problems often lead to engine 'hacks' which in turn make the engine unstable.

Answer 5

Drupal + Ubercart
The only drawback is 1 - you need an intelligent programmer :)
If you have it, there are no drawbacks. You can do anything and everything

Answer 6

A few words about WA Shop-Script.
Of the minuses, this is sometimes an idiotic code, I don’t even know what it’s called when php4 is put into a class and supposedly consider refractoring over. The second point is a huge number of files, but if you understand the structure, then working with them is pretty clear. The third is that there are a lot of templates, smart is used as a template engine, but everything that concerns the output is in them, there is practically no code in PHP except for pagination and error messages. The quality of the frontend is poor, the library used seems to be from 2005 to manage the selectors.
Actually, plus one if you constantly use this system for development, then if the hands are correct, all the jambs associated with the templates are corrected and only the admin panel remains from the shopscript, which, by the way, is quite convenient.
In terms of resources, the system is not particularly gluttonous, on a normal shared hosting everything works stably ~ 500 unique ones per day.
With caution, you should treat the bundle with 1c out of the box, it does not fill in pictures from 1c, additional options for the product size, color turns into several products.
In general, the product is rather strange, and it is rather difficult to start working with it, then you get used to it ))

Answer 7

Everyone likes Joomla, but I just can’t crawl to version 1.5.

Answer 8

Any popular CMS is a food processor.
It is more difficult to understand it than in a mixer, blender and specialized scripts.
No matter how much you trim, there are always unused functions, and the speed \ convenience of work and development is appropriate.
Unlike homemade, you need to be prepared for the fact that there will be compatibility problems with components and modules when updating.
As for the shops. If you do it for yourself or constantly work on a project, then you can take any engine and bring it to mind. Just write everything down so that you can repeat it when the next version of the engine is released ... For one-time clients, it is better to take paid engines, where everything that is in demand has already been done and at a normal level.