Joomla code structure principle, execution flow

joomla-Installation

1. Download source code

2. Unzip to Apache publishing directory

3. Visit http://xxx/installation/index.php According to the actual situation

4. Follow each step of the instructions, MySQL library to establish first, FTP can be temporarily not open

5. Delete the installation files

Joomla Code Structure

joomla 2.5 main directory Structure ├─administrator     #  daemon Section ├─cache              #  to store the cache, you need to keep writable ├─components         #  components, one folder per component, usually com_**├─images             #  picture Resources, uploaded files will be stored here, so to keep writable ├─language           #  Language Pack directory, the name that corresponds to the components, plugin, or module names to take effect │  ├─en-gb           #  such as:language/en-gb/en-gb.com_content.ini│   └─overrides      #  starting from 2.5, the language text can be rewritten in the background, the language information being rewritten exists in the location ├─libraries          # joomla's core class library requires a deep API to read inside the code ├─logs               #  log directory, to keep writable ├─modules            #  the location of the installed module ├─plugins           #   location of the installed plug-in ├─templates         #  the location of the installed templates, each subdirectory corresponds to a template │   ├─atomic         # atomic is a typical template, suitable for beginners │   │  ├─css         # css directory, the style files about the template are put here │   │  ├─html        #  components and modules have a default template (Tmpl directory), The main template has permissions to rewrite them, overriding the template here │  │  ├─images│  │  ├─js│  │   └─language    #  templates can have configuration parameters in the background, and the language packs for the parameters will be placed here │  │       └─en-GB│  └─system         #  All templates are based on the system template and do not modify it │      ├─css│       ├─html│      └─images└─tmp                #   temporary directory, need to maintain a writable configuration.php    #  configuration file containing database and site settings information .htaccess             #  without it, pseudo-static links cannot be implemented in Apache web.config            #  without it, the pseudo-static link component directory structure can not be implemented in IIS7, one com_ Components for users of chestnuts: ├─com_users            # user components, One of the most important components in Joomla │  ├─controllers       #  control set │   ├─helpers           # helpers for storing auxiliary classes and functions    │  ├─models            #  Model Set │   │  └─forms          #  Joomla2.5 start, forms can be configured based on XML, and forms is the specified configuration directory  &Nbsp; │  └─views             #   View Set │      ├─login         #   Login Page View │      │  │  metadata.xml│       │  │  view.html.php      #  View Logic, The role is a bridge between model and template │      │  │  view.json.php       #  If there are parameter Format=json on the URL, this view logic is used, and so on │      │   └─tmpl                 #  default template, which is introduced by the view │      │           default.php   #  one of the templates │      │           default.xml   #  you need to select Menu type when adding menus in the background, does the component appear on the menu depending on the file │       │          default_login.php         # default.php sub-template, introduced by LoadTemplate │       │          default_logout.php

Joomla code structure principle, execution flow