WordPress CMS VS TYPO3 – PART 3 of 4

WordPress CMS VS TYPO3 – PART 3 of 4

• WAM
• General
• Wednesday - 20 . September . 2017

WordPress CMS VS Typo3 the other facts. We were the last time when building a page stopped. The current score is 1: 5 For WordPress and we have actually not done much.

5. Upload or edit images

Uploading images is extremely easy on both systems. Differences exist here simply in the file construction. Typo3 actually has a big advantage.Here you can create and use individual orders for the corresponding images. So if you want to use eg images for “the team”, you can create a folder in the fileadmin with the name Team and integrate the pictures into the page. This is of course very useful for site operators, as it is always clear where the pictures are stored.

WordPress CMS looks different. In this case WordPress simply creates folders with date names and pushes all pictures into these folders. Surely you can also integrate the pictures on the pages, but it is clear that it is different.

Editing, that means you can cut the pictures but only in WordPress. That’s not what Typo3 can do. Here only the quality of the pictures can be changed.

Here we also have to give both systems a point, because the data structure is really great at Typo3.

2: 6 for WordPress

6. Extensions or plug-in administration

Both systems have extensions. At Typo3 they are called “Extensions” and at WordPress CMS “Plug-ins”. Both extend the basic system with various functions. Unfortunately we do not know exactly how many extensions there are for Typo3.

We estimate about 6000 – 9000 . The WordPress system drives here even larger guns, it should rumschwirren about 40000 plug-ins in the network.

Problem is, not every extension fits into every Typo3. The reason is the updates, but more later.

The even bigger problem, however, is the usually very complicated configuration or integration of the extensions into an existing page. The laymen get to 90% not out. Partly very abstract commands have to be built into the system. In addition, extensions are offered in the Extensions Manager that are not compatible with the system used. If a somewhat inexperienced user simply clicks away the warning as often happens, the system may be paralyzed.

Yes, yes, to reassure all Typo3 supporters, WordPress does not have that clean plug-ins. However, these are still 99.9% compatible. And we have not been able to paralyze a page with a plug-in.

2: 7 for WordPress CMS

7. Updates and security

Now we have to admit that we have not had to save a page created with Typo3. This has happened several times in WordPress CMS.

Since WordPress has been exposed to a variety of hacking attacks, the developers have come a long way. Nevertheless, WordPress CMS is often attacked, unfortunately, it can also be attributed to the laziness of the users here. If updates are not made, WordPress is open like a barn door.Although updating WordPress is so easy, it is not. Clicking on Updates Install and the system does it all by itself.

With Typo3 you have to dive into the matter a bit more. Depending on the installation, the data must first be made available on the server. If this is not done you can not do any system updates. In addition, what we take a pity on are these brutal version jumps. Since it may happen that an older version can only be updated by massive interventions or not at all. Strangely enough, WordPress does not have this problem at all. There are versions that are already 5 or more years, always brought up to date.But in terms of safety Typo3 can not be beat.

3: 7 for WordPress CMS

In the actual update function WordPress is the leader, with 2 clicks everything is up-to-date, no matter which version you are currently using.

3: 8 for WordPress CMS

8. Server support

That with the servers is such a thing, Typo3 definitely does not run on any server. Here you have to turn something on the individual screws on the server so that the system runs well and stable. But once you’ve done that, you can run tens of Typo3 installations on a source (source file).This saves space and is very convenient for server admins because of the simplified updates.

The PHP versions must also be correct for Typo3 , otherwise it will not work.

WordPress can be installed on any server box as long as there is enough database and space. There are hardly any problems with databases or PHP systems. We have not received a server on which it is not running yet. Even with a hoster like 1und1, and that should mean something.

4: 9 for WordPress CMS

9. Mobile Handling

Even administrators have a right to mobile handling. It is a pity that this function is not available in the Typo3 backend. So, as a site operator of a Typo3 site, you are thrown into using either a laptop / PC or at least a tablet.

Something like that should be feasible in our opinion in the age of mobile devices. The frontend is of course another matter, because you can determine with your template itself whether this is supported or not.

With WordPress, the developers seem to be a few steps ahead of them again. Here you can do everything with any device, which also works on the monitor. Even on the beach in the sun you can write a report again.

Whether this is comfortable, to write a report on a small keyboard of the smartphone, we leave it a question. But it works, at least.

Also all themes that you get directly from WordPress are responsive. You do not need to worry about the mobile presentation.

4:10 for WordPress

WordPress CMS VS Typo3

– Those were the facts why it’s getting harder and harder for Typo3.

But we are not yet conclusive, it comes even more in the following days.

  Ja, ich habe die Datenschutzerklärung zur Kenntnis genommen und bin damit einverstanden, dass die von mir angegebenen Daten elektronisch erhoben und gespeichert werden. Meine Daten werden dabei nur streng zweckgebunden zur Bearbeitung und Beantwortung meiner Anfrage genutzt.