Typo3 Backend
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Typo3 Backend

on

  • 6,889 views

 

Statistics

Views

Total Views
6,889
Views on SlideShare
6,871
Embed Views
18

Actions

Likes
0
Downloads
42
Comments
0

1 Embed 18

http://www.slideshare.net 18

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Typo3 Backend Presentation Transcript

  • 1. CMS & Typo3
      • Module 3: The administration interface
      • < [email_address] >
  • 2. CMS & Typo3: Module 3 The administration interface
    • Session index:
      • The extension system in Typo3
      • Modules and functions in Typo3
      • The template system Templavoilà
      • Basic concepts of Typoscript language
      • Development of new extensions
  • 3. CMS & Typo3: Module 3 The administration interface
    • 1 . The extension system
      • Typo3 allows its evolution and modification based on an extension system that provides a clean and high flexibility.
      • Extensions are specific developments that can keep dependences with other external or system extensions:
        • For instance, an extension that implements LDAP queries and synchronization and another that provides LDAP user login using the other.
        • Categorization or taxonomy systems that depends on tt_news standard extension.
  • 4. CMS & Typo3: Module 3 The administration interface
    • Extensions can be from several types (or a combination of them)
      • Backend extensions, Backend modules, Frontend modules, Frontend Plugins, Misc and services.
    • They can be Imported, Installed, and Loaded.
  • 5. CMS & Typo3: Module 3 The administration interface
    • To “Import extensions”.
      • Import of new extensions through the web interface with connectivity to the remote repository.
      • It is also possible by uploading the t3x Typo3 extension package from a local file.
    • To install extensions you will select the imported extension, but pending of installation marked with the grey bullet.
  • 6. CMS & Typo3: Module 3 The administration interface
    • Each extension knows the modifications that has to do in the database, from the installation point of view, when installing, and when creating from the beginning.
    • They must have specified the variables to be configured to ask for them in the configuration
    • This extension settings can be modified after the installation accessing the module Tools > Admin extensions selecting the extension name.
  • 7. CMS & Typo3: Module 3 The administration interface
    • 2. Modules and functions in Typo3
      • Powerful organization of stored contents in the Page Tree using the web module :
        • Pages and page contents ( articles, plugins, ... )
        • Orientation to page in the Information system structure..
        • Specific functionalities of the Content Tree can
      • Besides of visible content elements, other components are stored (configuration data, access control lists)
      • To recover information stored in extension registers, FE plugins are used.
      • PageTV module (templavoilà) is replacing the standard page
  • 8. CMS & Typo3: Module 3 The administration interface
      • The administration interface is divided into tree parts ( in its most typical skin ) :
        • Left menu: show the main modules and its functions.
        • Page Tree or Filesystem structure for navigation in Web and Filelist modules.
        • Content area: space for each specific function.
      • Once selected any function of the web module, the information displayed is related to the node in which we are in the content tree.
      • It is necessary to configure in user preferences User > Setup the extended visualization methods to be able to use all the configuration fields.
  • 9. CMS & Typo3: Module 3 The administration interface
    • Common icons:
      • New content or page:
      • Edit and edit properties:
      • Delete content or page:
      • Page:
      • Storage folder:
      • Preview content:
      • Save:
      • Save and close:
      • Close w/o save:
  • 10. CMS & Typo3: Module 3 The administration interface
    • From page operation the strict content management is done:
      • Creation, edition and deletion of pages.
      • Creation, edition and deletion of page contents.
      • It will be the most used function for editors.
    • The module pageTV replaces and extends the behavior of page and adapts the page areas to the structure defined in the DS ( vs. the approach based on static columns of page module )
  • 11. CMS & Typo3: Module 3 The administration interface
    • User management in Backend and Frontend
      • Typo3 keeps a separate control of users and groups for access to BE and FE.
      • This has inconvenients for having a centralized access control to contents based on groups.
        • Alternative based on extending the system to use the same groups in backend and frontend in a common LDAP directory ( ldap_gua , ldap_auth and ldap_sync extensions )
      • A single autentication system (CAS) for multiple environments single sign-on support :
        • Installation of the Central Authentication
        • Extensións cas_login e cas_auth
  • 12. CMS & Typo3: Module 3 The administration interface
    • From List operation all the registers of each page can be handled:
      • Configuration elements ( LDAP servers, domains, etc )
      • Templates and Templavoilá objects
      • Users and groups
      • Extension registers to be shown in frontend by plugins ( tt_news, tt_news_records)
  • 13. CMS & Typo3: Module 3 The administration interface
    • From Access function the ACL (Access Control Lists) can be managed:
      • A ACL is a set of 5 elements that configures if a user group is allowed to:
        • See the page
        • Create subpages
        • Create page contents
        • Edit page contents
        • Delete the page
  • 14. CMS & Typo3: Module 3 The administration interface
    • Module Filelist or access to fileadmin directory:
      • Direct access to resources stored in the web server directory “WEB_BASE_ROOT /fileadmin/”
      • To allow file direct download depending of the Apache server configuration could be needed to modify the VirtualHost.
      • Some extensions extend the behavior of the filelist module, adding meta information about images ( dam_extension )
  • 15. CMS & Typo3: Module 3 The administration interface
    • Available functions in admin tools module:
      • Users admin: management of user and user groups.
      • Extension manager: Install and management of extensions.
      • Database check: Statistics, references and indexing.
      • Configuration: TCA and Typoscript tree configuration.
      • Installation: Install wizard tool
      • Log: Access and history changes
  • 16. CMS & Typo3: Module 3 The administration interface
    • 3. The template system Templavoilà
      • Allows an easy adaptation of graphical design to the website and the organization of the areas that the page structure consists of.
      • Translates static HTML of each page type to dynamic content structures
      • Mapping process = DS ( Data Structures ) + TO ( Template Objects ) creation
      • The Templavoilà documentation ( Futuristic Template building ) replaces the Modern Template Building tutorial
        • http://typo3.org/documentation/document-library/tutorials/doc_tut_ftb1/current/
  • 17. CMS & Typo3: Module 3 The administration interface
    • Steps to integrate a new design
      • Add the HTML resources ( code, CSS, images and javascript ) to the fileadmin module, in the templates directory
      • Access the function Web > Templavoilà
      • Start the start new site wizard , selecting as the main template the uplodaded HTML template
      • Start the mapping process of the different content elements blocks
      • Edit header parts and save DS + TO
      • Add Typoscript configuration of the defined elements as typoscript obect path and set the template to the specific pages that use it.
  • 18. CMS & Typo3: Module 3 The administration interface
    • 4. Typoscript configuration language
      • Allows the configuration of elements in a variable namespace in different levels in the content tree.
      • Typoscript code can be added in web template module or in the associated field in page properties
      • Other standard use of typoscript is filling in variables $lib.myvar defined in Templavoilà templates
      • Documentation on Typoscript syntax: Typoscript Reference TSRef:
        • http://typo3.org/documentation/document-library/core-documentation/
  • 19. CMS & Typo3: Module 3 The administration interface
      • Typoscript for menu generation example:
        • lib.mainMenu = HMENU
        • lib.mainMenu.1 = TMENU
        • lib.mainMenu.1 {
        • NO.allWrap = <div class=&quot;menu1-level1-no&quot;> | </div>
        • NO.stdWrap.htmlSpecialChars = 1
        • ACT = 1
        • ACT.stdWrap.htmlSpecialChars = 1
        • ACT.allWrap = <div class=&quot;menu1-level1-act&quot;> | </div> }
        • lib.mainMenu.2 = TMENU
        • lib.mainMenu.2 {
        • NO.allWrap = <div class=&quot;menu1-level2-no&quot;> | </div>
        • NO.stdWrap.htmlSpecialChars = 1 }
  • 20. CMS & Typo3: Module 3 The administration interface
      • Typoscript basic example
        • /* We have defined lib.myVar typoscript object path in tv */
        • lib.myVar = TEXT
        • lib.myVar.value = Hello world
  • 21. CMS & Typo3: Module 3 The administration interface
    • Typoscript usage for an specific tt_content load:
        • lib.footer = CONTENT
        • lib.footer.table = tt_content
        • lib.footer.select.pidInList=130
        • lib.footer.select.uidInList=62
    • More complex examples of typoscript would be added for multilanguage settings, real url, or advanced extension configuration.
  • 22. CMS & Typo3: Module 3 The administration interface
    • Frontend plugins
      • The installation of new functionalities will be done getting the modules from the TER
      • These content types would be extensions as tt_news , tt_news_category, macina_banners or gl_taxonomy , for instance.
      • The element that fetches the registers will be configured to recover elements in which presentation templates are defined.
  • 23. CMS & Typo3: Module 3 The administration interface
    • Frontend plugins and registers for tt_news extension
      • tt_news extension allows to add registers to the system with an specific structure, to be fetched and showed in pages by special page contents called plugins .
      • In the plugin settings the selection criteria, and presentation mode will be defined ( list, latest, single, archive, ... )
      • To edit single registers we would use Web > List function
      • We will set specific templates to set the HTML that we want to produce, getting from standard template:
        • .../typo3conf/ext/tt_news/pi/news_template.tmpl
  • 24. CMS & Typo3: Module 3 The administration interface
    • New extension creation with kickstarter
      • Install kickstarter extension
      • Select make new extension in EM menu
      • Give it a name or extension key and press update
      • Now we can use the view result option to see the generated files with their code.
        • With the write button the extension will be stored under typo3conf/ext directory
        • Using Download as a file we can generate a bundled package with the new extension.
  • 25. CMS & Typo3: Module 3 The administration interface
      • General info stored in ext_emconf.php :
        • Title, description, category, state, dependencies, author
      • Setup languages locallang.xml:
      • New database tables ext_tables.php, tca.php and ext_tables.sql
      • Extend existing tables (analog to previous but with existing tables
      • Frontend Plugins
      • Backend modules