Мнение о TYPO3

typo27 · 02.05.2009, 06:28

Privet,
some good things (not mentioned yet in this discussion) for typo3:

*Very rich system configuration - take a look at install tool/all configuration
*export/import page tree, subtree together with content elements and list items.
*ACL - unlimited frontend and backend groups, controling access to backend modules, pages, to tables and even to table columns, to content elements and plugins.
*extension development - kickstarter allows using web interface to define new or extend existing DB tables and some more things; kickstarter generates all needed files for the system: php files, sql files, tca files (used for tables and columns definition so in the system it is possible to operate with new entities and properties), language label files, TYPOSCRIPT configuration files.

*TYPOSCRIPT - strength is: thousands of configuration parameters control website behavior. Extensions also provide TYPOSCRIPT constants (in some extensions hundreds of those). TYPOSCRIPT is inherited in child pages, in any child page it is possible to redefine TYPOSCRIPT - so some website sections can behave differently. TYPOSCRIPT can contain conditions - so website can act differently depending on usergroup, browser, page tree, or some other condition. TYPOSCRIPT can overwrite all plugin labels in any language. TYPOSCRIPT can hold userfuncs, GIFBUILDER (see next point). And this TYPOSCRIPT - huge amount of constants - can be written into file, and file can be used in any typo3 installation.

*GIFBUILDER -rich image creator - allows to define graphics to menus, content element headers, content elements or just create plain graphics. Since GIFBUILDER is part of TYPOSCRIPT, it can be also inherrited in child pages or can be written to file and used in any typo3 installation.

Crol, you preffer to write plain php?
So just put a marker in template file (###MARKER###), write almost plain file.php and in TYPOSCRIPT just write smth like this:
page.1.template.subparts.MARKER = PHP_SCRIPT
page.1.template.subparts.MARKER.file = file.php

and if you want to show something else in case of specific usergoup, add condition:
[usergroup = 7]
page.1.template.subpats.MARKER.file = another_file.php
[end]

Don't you see how flexible TYPO3 is?

Похожие темы
Тема	Автор	Раздел	Ответов	Последнее сообщение
Typo3 и шаблоны... и новичек!	Aha	Вопросы выбора CMS	14	23.02.2014 23:16
Настройки параметров ImageMagick для TYPO3 на FreeBSD и Linux	Valery Romanchev	Мастер-класс	9	25.06.2013 22:38
UPD: Требуется специалист(ы) по Typo3 в Rich Media Development.	Pavel Antonov	Работа и заказы / Job Offer and Request	0	20.05.2008 13:59
Требуется специалист(ы) по Typo3 удаленно	Pavel Antonov	Работа и заказы / Job Offer and Request	4	12.07.2006 12:46
Несколько вопросов по TYPO3	Александр Д.	Общие вопросы	11	26.01.2006 19:29

02.05.2009, 06:28	#1
typo27 Новенький Регистрация: 30.01.2008 Сообщений: 27	Privet, some good things (not mentioned yet in this discussion) for typo3: Very rich system configuration - take a look at install tool/all configuration export/import page tree, subtree together with content elements and list items. ACL - unlimited frontend and backend groups, controling access to backend modules, pages, to tables and even to table columns, to content elements and plugins. extension development - kickstarter allows using web interface to define new or extend existing DB tables and some more things; kickstarter generates all needed files for the system: php files, sql files, tca files (used for tables and columns definition so in the system it is possible to operate with new entities and properties), language label files, TYPOSCRIPT configuration files. TYPOSCRIPT - strength is: thousands of configuration parameters control website behavior. Extensions also provide TYPOSCRIPT constants (in some extensions hundreds of those). TYPOSCRIPT is inherited in child pages, in any child page it is possible to redefine TYPOSCRIPT - so some website sections can behave differently. TYPOSCRIPT can contain conditions - so website can act differently depending on usergroup, browser, page tree, or some other condition. TYPOSCRIPT can overwrite all plugin labels in any language. TYPOSCRIPT can hold userfuncs, GIFBUILDER (see next point). And this TYPOSCRIPT - huge amount of constants - can be written into file, and file can be used in any typo3 installation. GIFBUILDER -rich image creator - allows to define graphics to menus, content element headers, content elements or just create plain graphics. Since GIFBUILDER is part of TYPOSCRIPT, it can be also inherrited in child pages or can be written to file and used in any typo3 installation. Crol, you preffer to write plain php? So just put a marker in template file (###MARKER###), write almost plain file.php and in TYPOSCRIPT just write smth like this: page.1.template.subparts.MARKER = PHP_SCRIPT page.1.template.subparts.MARKER.file = file.php and if you want to show something else in case of specific usergoup, add condition: [usergroup = 7] page.1.template.subpats.MARKER.file = another_file.php [end] Don't you see how flexible TYPO3 is?