Aqua3

Light Responsive Template for Joomla 3.x

List of All Tags (Page Header)

joomla

  • A listing of useful Additional Components for Joomla 3.x used on this demo site.

    • eXtplorer (file management in Joomla backend)
    • JCE editor (advanced text editor with handy enhancements)
    • OSmap sitemap
    • Akeeba Admin Tools
    • Akeeba Backup
    • XCloner Backup
    • Kunena
    • JCH Optimize
    • JotCache
  • What determines your home page?

    When you install Joomla! by default it has a menu link to the frontpage component (Featured Blog layout) as the home page. However, any content, component or other link can be used as the home page.

    Changing the Home Page

    • Navigate to any Menu you have and any Menu Item in there.
    • Select it (check-mark).
    • Now, in the top bar in the Administrator panel, you see a star labeled "Home"
    • Click on it, and you're set to have that item as Home
  • The correct way to do this is through the Joomla language files.

    The main login page for Joomla is through the 'com_users' component and the 'mod_login' module.

    If you look at the templates for any component or module, you'll see they have code sections like so:

    <?php echo JText::_('MOD_LOGIN_VALUE_USERNAME') ?>
    <?php echo JText::_('COM_USERS_LOGIN_USERNAME_LABEL') ?>

    This is basically saying 'insert the translated text for WHATEVERSTRING here'. This translated text is stored in the appropriate language file, which will be in '/language/LANG/LANG.com_users.ini' for the 'com_users' component, etc. LANG by default is 'en-GB', so probably for you in '/language/en-GB/en-GB.com_users.ini' you'll find a line like:

    COM_USERS_LOGIN_USERNAME_LABEL="User Name"

    Now, you could edit that file right there. This will appear straight away on your site, and will handle multi-language properly. But again, this wouldn't survive upgrades very well (when Joomla releases a new version, that changes that language file and it will overwrite your changes).

    To handle upgrades, they added a new feature since Joomla 1.6 for language overrides. You can add overrides for ANY language file (any component/module/etc) into a separate overrides location, in '/language/overrides/LANG.override.ini'. For example, add the line:

    COM_USERS_LOGIN_USERNAME_LABEL="Usr"

    Now you've overridden that language string. Add lines for MOD_LOGIN_VALUE_USERNAME etc as well to override the login module and other strings as needed.

    Now if you upgrade Joomla, you'll get any changes to those login templates, but won't lose your text changes. You can apply this same process for each language your site is provided in, the overrides will live happily side by side. This will also work for 3rd party components and modules, as long as they're using JText::_() for string output - which they should be.

  • Check your Apache configuration first

    In order to make use of the htaccess file, you first need to make sure your Apache server is configured correctly for use with mod_rewrite. In your apache httpd.conf, make sure you have the following set so that the mod_rewrite engine is actually loaded:

    # Dynamic Shared Object (DSO) Support
    LoadModule rewrite_module libexec/apache22/mod_rewrite.so

    WARNING:
    If you are using Virtual Hosts in Apache, then your directory settings should include the following "Options FileInfo" or the htaccess rewrite rules will not work! Your directory setting should look something like this:

    <Directory "/usr/local/www/mysite">
        AllowOverride All
        Options FollowSymLinks
        Order allow,deny
        Allow from all
    </Directory>

    or at the very least:

    <Directory "/usr/local/www/mysite">
        AllowOverride FileInfo
        Options FollowSymLinks
        Order allow,deny
        Allow from all
    </Directory>

    Restart Apache after saving the settings.

    Joomla Security Documentation

    On the Joomla documentation site there is a very good article on the .htaccess file:
    http://docs.joomla.org/Htaccess_examples_%28security%29

    You will also find an example htaccess file there from the Akeeba developer with many security enhancements. It is now in version 3.3., with all changes commented:

    NOTE: The Akeeba Admin Tools has an option called ".htaccess Maker", which helps you give your site the best overall protection. Create a sophisticated, secure .htaccess with an easy GUI. You don't have to be an expert. Or even know what a .htaccess file is.

    http://codereview.appspot.com/4528051/diff/1/joomla-master-htaccess.txt

    You may also want to check the Joomla Security and Performance FAQs:
    http://docs.joomla.org/Security_and_Performance_FAQs

    Since Joomla 1.5.23 changes in .htaccess file improve the mod_rewrite processing speed by at least a factor of three, achieved by re-arranging the rule order, and optimising the RegEx patterns. In particular, the new code eliminates a large number of slow and unnecessary disk reads for requests that will never be rewritten to the index.php script.

    NOTE: the htaccess.txt file is used for Apache servers, use the web.config.txt file if you run IIS

    Standard htaccess file

    ##
    # @package        Joomla
    # @copyright    Copyright (C) 2005 - 2012 Open Source Matters. All rights reserved.
    # @license        GNU General Public License version 2 or later; see LICENSE.txt
    ##
    ##
    # READ THIS COMPLETELY IF YOU CHOOSE TO USE THIS FILE!
    #
    # The line just below this section: 'Options +FollowSymLinks' may cause problems
    # with some server configurations.  It is required for use of mod_rewrite, but may already
    # be set by your server administrator in a way that dissallows changing it in
    # your .htaccess file.  If using it causes your server to error out, comment it out (add # to
    # beginning of line), reload your site in your browser and test your sef url's.  If they work,
    # it has been set by your server administrator and you do not need it set here.
    ##
    ## Can be commented out if causes errors, see notes above.
    Options +FollowSymLinks
    ## Mod_rewrite in use.
    RewriteEngine On
    ## Begin - Rewrite rules to block out some common exploits.
    # If you experience problems on your site block out the operations listed below
    # This attempts to block the most common type of exploit `attempts` to Joomla!
    #
    # Block out any script trying to base64_encode data within the URL.
    RewriteCond %{QUERY_STRING} base64_encode[^(]*\([^)]*\) [OR]
    # Block out any script that includes a <script> tag in URL.
    RewriteCond %{QUERY_STRING} (<|%3C)([^s]*s)+cript.*(>|%3E) [NC,OR]
    # Block out any script trying to set a PHP GLOBALS variable via URL.
    RewriteCond %{QUERY_STRING} GLOBALS(=|\[|\%[0-9A-Z]{0,2}) [OR]
    # Block out any script trying to modify a _REQUEST variable via URL.
    RewriteCond %{QUERY_STRING} _REQUEST(=|\[|\%[0-9A-Z]{0,2})
    # Return 403 Forbidden header and show the content of the root homepage
    RewriteRule .* index.php [F]
    #
    ## End - Rewrite rules to block out some common exploits.
    ## Begin - Custom redirects
    #
    # If you need to redirect some pages, or set a canonical non-www to
    # www redirect (or vice versa), place that code here. Ensure those
    # redirects use the correct RewriteRule syntax and the [R=301,L] flags.
    #
    ## End - Custom redirects
    ##
    # Uncomment following line if your webserver's URL
    # is not directly related to physical file paths.
    # Update Your Joomla! Directory (just / for root).
    ##
    # RewriteBase /
    ## Begin - Joomla! core SEF Section.
    #
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    #
    # If the requested path and file is not /index.php and the request
    # has not already been internally rewritten to the index.php script
    RewriteCond %{REQUEST_URI} !^/index\.php
    # and the request is for something within the component folder,
    # or for the site root, or for an extensionless URL, or the
    # requested URL ends with one of the listed extensions
    RewriteCond %{REQUEST_URI} /component/|(/[^.]*|\.(php|html?|feed|pdf|vcf|raw))$ [NC]
    # and the requested path and file doesn't directly match a physical file
    RewriteCond %{REQUEST_FILENAME} !-f
    # and the requested path and file doesn't directly match a physical folder
    RewriteCond %{REQUEST_FILENAME} !-d
    # internally rewrite the request to the index.php script
    RewriteRule .* index.php [L]
    #
    ## End - Joomla! core SEF Section.

  • The robots.txt file is a small file located in the root folder of your Joomla site. The file contains instructions to the search engines on what to index and what to leave out.

    Rules are only for Disallow

    The robots.txt file is a part of the Robots EXCLUSION Protocol and as such "Allow" is NOT a part of the standard syntax. Robots.txt is all about what to DISALLOW. Bad bots of course ignore the robots.txt file, so the robots.txt file is no protection against misbehaving bots or hacking scripts. Other methods should be employed for that, such as the htaccess file or other.

    robots-txt-joomla

    Robots.txt is NOT about security!
    Most bad bots will NOT respect the robots.txt file, so again,  robots.txtis not about security. It is about telling nice, well-behaving search bots what they can an cannot crawl and index on your site.

    Some people confuse the robots.txt file with the .htaccess file. The difference is significant. The robots.txt file only gives instructions to search engines - and most search engines respect it.The .htaccess file, on the other hand is used to reconfigure the settings of your Apache server, redirect URLs and other server related tasks.

    The robots.txt file and SEO

    As mentioned, the robots.txt file is in your site root folder. It contains info on which folders should be indexed and not. It can also include information about your XML sitemap.

    1. Remove exclusion of certain images folders

    By default the robots.txt file in Joomla excludes the images folder. If you want to have some images indexed by the search engines (for example images included in articles), it is a good plan to put them into a specific folder, e.g. /images/article-images and then to allow crawling of ONLY that subfolder.

    To make this effective, open your robots.txt file and then add disallow lines for every folder that you do NOT want indexed.

    Disallow: /images/subfolder-a
    Disallow: /images/subfolder-b
    Disallow: /images/subfolder-c, etc.

    So, by NOT including a Disallow rule for the /images/article-images subfolder, Google and others will start indexing your article-images on the next crawl of your site, but leave out the disallowed subfolders.

    2. Add a reference to your sitemap.xml file

    If you have a sitemap.xml file (and you should have!), include the following line in your robots.txt file:

    sitemap:http://www.mydomain.com/sitemap.xml

    Naturally, this line needs to be adjusted to fit your domain and sitemap file. In my case, I use the Xmap component to create the Sitemap XML file automatically.

    So, the line looks like this:

    sitemap:http://www.mydomain.com.net/component/option,com_xmap/lang,en/sitemap,1/view,xml/

    Robots.txt specifics

    Remove the trailing slashes from the folders if you want to completely disallow those folders from being crawled. As long as you dont have any files with those names!

    Example: "GET /administrator" would not be stopped by
    Disallow: /administrator/, because robots.txtis based on 'prefix match' beginning at the root "/"

    Disallow: /admin on the other hand would disallow any URL with the prefix /admin including:
    /admin
    /adminisrator
    /administrator/
    /adminibator
    /admin/
    /admin.html
    /admin.php

    It simply matches the prefix of the URL beginning at the root.
    Again, this will not prevent any robot from access, it simply asks them to "please not go there" . For real protection you may want to use server side commands like .htaccess or equivalent.

  • There's a good article here on the difference between the System Cache Plugin and the Global Configuration Cache.

    It's best to leave all caching disabled while developing. If you make changes and don't see them it could be because caching is enabled.

    The cache can be cleared at Site > Maintenance > Clear Cache

    Caching is usually only useful for sites with lots of content and visitors, but might help some extensions and templates load faster. Give it a try. If you don't notice a difference in page load speed disable it.

    An excellent 3rd party cache solution is JotCache (available through the JED).

  • The Joomla Administrator Components drop-down menu list can become long enough that it runs off the page.

    The Advanced Administrator Menu by Andrew Eddie fixes this problem by splitting the Components Menu into separate shorter menus.

    Full instructions here.

    Don't forget to unpublish the default Admin Menu Module and publish the Advanced Administrator Menu Module.

  • While a Joomla website is offline it might be nice to customize the default offline page to include a company logo and custom message.
    The file templates/system/offline.php contains the markup that will be displayed when a Joomla site is offline.

    If there is a file named offline.php in your template folder it will override the default offline file templates/system/offline.php.

    Copy templates/system/offline.phpto your template folder:

    templates/your-template-folder/offline.php

    Then customize the copied file.

    The offline message can be changed in Site > Global Configuration.

    Custom Offline Image

    Near the top of offline.php there is this code:

    <img src="/images/joomla_logo_black.jpg" alt="Joomla! Logo" align="middle" />

    This could be edited to something like:
    <img src="/templates/template-name/images/your-image.jpg" alt="Your Alt Text" align="middle" />

  • favicon-joomla.jpgThe Joomla favicon can be changed to your own favicon.

    The Joomla favicon can be found at:

    [Joomla root] templates/yourTemplate/favicon.ico

    For an Administrator template it will be located at:

    [Joomla root] administrator/templates/yourTemplate/favicon.ico

    It is also possible that the favicon is in the root of the Joomla site or the images folder. It depends on the template programming.

    One way to determine where the favicon is being pulled from is to view the source code of your page. 

    Look for something like this in the head section of the code:

    <link rel="shortcut icon"
    href="http://www.yoursite.com/templates/yourTemplate/favicon.ico" />

    NOTE:
    Browsers cache the favicon and some don't flush the favicon easily. You may need to clear the browser cache and possibly reboot the browser to clear the old favicon from the browser cache. FireFox stores the favicon locally, you may need the FireFox Favicon Picker add-on to change it afterwards.

    TIP:
    I find the favicon generator tool helpful to convert images to favicons.

  • Which Joomla Access  Levels are included in the "Special" group?

    A: "Special" is every registered user with Access Level of author and higher.

  • Joomla has four front end user groups and three back end user groups. User permissions are set in: Site > User Manager

    Front End User Groups

    There are four Front-end User Groups available in a standard Joomla installation:

    Registered: The Registered User Group comprises those users who have completed the registration process.

    As a Registered User they have the access permission to log in to the web site, view all Content that is set as Registered Access as well as Public Access Content.

    By default Registered Users are able to configure their own User Profile, submit a Web Link, view/rate Content Items with a Registered Classification,

    Author: The Author User Group inherits the access permissions of the Registered User Group and in addition, its members are allowed to create a new Content Item for the Front-end of the web site.

    A new Menu Item link will need to be added to one of the web site Menus to allow the Author to access this function.

    Editor:The Editor User Group inherits the access permissions of the Author User Group and, in addition, its members are allowed to edit all published Content Items for the Front-end of the web site, and to review and edit (where appropriate) any new Content Item that has yet to be published.

    A new Menu Item link will need to be added to one of the web site Menus to allow the Editor to access any unpublished Content Items. These are created in the menu Menu Manager >menuname > new Menu Item

    Publisher: The Publisher User Group inherits the access permissions of the Editor User Group, and in addition, its members are allowed to publish new Content Items to the Front-end of the web site. In addition the Publisher can control existing published Content Items and Unpublish them if necessary by direct entry into the Content Item itself.

    A new Menu Item link will need to be added to one of the web site Menus to allow the Publisher to access any unpublished Content Items.These are created in the menu Menu Manager >menuname > new Menu Item

    Back End User Groups

    There are three Back-end User Groups available in a standard Joomla installation.

    As administration User Groups they have the access permission to log in to the web site as well as to the Administrator Back-end - via a separate log in process. They can view all Content that is Classified as Registered Access, Public Access, as well as Special Access.

    Manager: The Manager User Group inherits the access permissions of the Publisher User Group in the Front-end of the web site and, in addition, its members are allowed access to the Administrator Back-end (Control Panel) via a separate log in.

    In the Control Panel a Manager can access the following Administrator Menus and associated functions:

    • Site:
      • Media Manager
      • Preview.
      • Statistics
    • Menu:
      • Access and edit existing Menus
    • Content:
      • Content by Section
      • All Content
      • Static Content Manager,
      • Section Manager,
      • Category Manager
      • Front Page Manager
      • Archives Manager.
      • Page Impressions
    • Help (general), including System Info.

    Administrator: The Administrator User Group inherits the access permissions of the Manager User Group and in addition an Administrator has the following permissions:

    • Site:
      • Trash Manager,
      • User Manager (may create/edit/delete any user of the same level or below – all except Super Administrator.
    • Menu:
      • Menu Manager
    • Modules:
      • Site Modules
      • Administrator Modules
    • Components
      • Banners
      • Contacts
      • Mass Mail Not available although it appears in this menu
      • News Feeds
      • Polls
      • Syndicate
      • Web Links
    • Mambots:
      • Site Mambots
    • Installers
      • Components
      • Modules
      • Mambots

    Super Administrator:The Super Administrator User Group has total access permission – that is for all Back-end administration and all Front-end functions.

    All the functions accessed by the Administrator User Group plus:

    • Site:
      • Global Configuration
      • Language Manager
      • Template Manager
        • Site
        • Administration
      • User Manager (may create/edit any type of user, may delete any user except Super Administrator.
    • Components:
      • Mass Mail
    • Messages:
      • Inbox
      • Configuration
    • System:
      • Version Check
      • Global Checkin
      • System Information

    Content Access Classification:

    In Joomla Content is classified by who can view/access it. There are three levels of Content Access Classification:

    • Public- open to all visitors to the web site.
    • Registered- restricted to all seven Registered User Groups of the web site.
    • Special- restricted to all User Groups except Guest and Registered.

    NOTE: The Special Classification uses the individual Group's authority levels to determine precisely what Special Access is actually permitted.

  • List of Joomla Menu Item Types for layout testing:

    Contacts

    • List All Contact Categories
      Shows a list of contact categories within a category.
    • List Contacts in a Category
      This view lists the contacts in a category.
    • Single Contact
      This links to the contact information for one contact.
    • Featured Contacts
      This view lists the featured contacts.

    Articles

    • Archived Articles
      Display all archived articles.
    • Single Article
      Display a single article.
    • List All Categories
      Shows a list of all the article categories within a category.
    • Category Blog
      Displays article introductions in a single or multi-column layout.
    • Category List
      Displays a list of articles in a category.
    • Featured Articles
      Show all featured articles from one or multiple categories in a single or multi-column layout.
    • Create Article
      Create a new article

    Search

    • Search Form or Search Results
      Display search results.

    Smart Search

    • Search
      The default search layout.

    Newsfeeds

    • List All News Feed Categories
      Show all the news feed categories within a category.
    • List News Feeds in a Category
      Show all news feeds within a category.
    • Single News Feed
      Show a single news feed.

    Tags

    • Tagged Items
      This links to a list of items with specific tags.
    • Compact list of tagged items
      List of items that have been tagged with the selected tags
    • List of all tags
      This links to a detailed list of all tags

    Users Manager

    • Login Form
      Displays a Login Form
    • User Profile
      Displays a User Profile
    • Edit User Profile
      Edit a User Profile
    • Registration Form
      Displays a Registration Form
    • Username Reminder Request
      Displays a Username Reminder Request
    • Password Reset
      Displays a request to Reset Password

    Weblinks

    • List All Web Link Categories
      Show all the web link categories within a category.
    • List Web Links in a Category
      Displays a list of weblinks for a category
    • Submit a Web Link
      Display a form to submit a web link in the frontend.

    Wrapper

    • Iframe Wrapper
      Displays a URL in an Iframe

    System Links

    • External URL
      An external or internal URL.
    • Menu Item Alias
      Create an alias to another menu item.
    • Text Separator
      A text separator.
    • Menu Heading
      A heading for use within menus, useful when separating menus with a separator.
  • You define the user permission level upon registration in the Global Configuration. On a site using user Article Submissions it can be helpful to give the user "Author" permission when they register.

    By default users are assigned the "registered" permission which does not allow them to submit Articles. The site admin would manually assign the user front-end Author permissions (or above: editor, publisher) in the User Manager. This could become tedious.

    To set the permission level that new registered users will be assigned go to:

    Site > Global Configuration [Site]

    Set New User Registration Type to the desired level.

    config-user-settings

    This is a new feature since Joomla 1.5 which used to require a core hack in Joomla 1.0.

  • The Read More link only shows if the article is displayed on a Category Blog type of page (where the introductions to many articles are shown).

    If the article is displaying by itself (using an "Article > Single Article" menu type), then the "Read More" link does not show.

  • Pages available only for logged in users will present an error when the user logs out:

    An error has occurred.
    The requested page cannot be found.
    404Category not found
    If the difficulties persist, please contact the System Administrator of this site and report the error below.

    In this case, all you need to modify is the redirect in the Login module Module Manager.  For example, once user logs out I want the user to be redirected to back my homepage.

    1. Login to your Joomlaadministrator panel.
    2. Click on Extensions >Module Manager
    3. Click and edit your Login module.
    4. Under Basic Options, set a redirect page in the value for – Logout Redirection Page.
    5. Logout Redirection Page =  Main Menu – Home
    6. Save the Login module.

    Now you can refresh your website. Test the logout function and it should work. On logout it should redirect you back to the default homepage.

  • Copyright © 2009 YourSite.com. All Rights Reserved.
    Joomla! is Free Software released under the GNU/GPL License.
     
    The text above appears at the bottom of the default Joomla installation.
    It is contained in the Module named Footer.
    1. In Joomla Administrator got to Extensions > Module Manager.
    2. Use the Select Position pulldown to select the Footer position.
    3. Click the green check mark to the right of the Footer Module.
    4. The green check mark should change to a red X. The module is now disabled.
    Note: There may be other content at the bottom of the template inserted by the template designer.This will usually need to be removed manually. The file that usually contains this content is templates/yourtemplate/index.php
  • There's a really simple fix to this problem.

    • Go to Components > JCE > Configuration > Formatting (third down on the left)
    • Set Use Template CSS to No

    That stops it following the css of your Default Template.

  • Locked out of the Joomla admin? The password can be reset with the aid of phpMyAdmin in cPanel.

    If you can't get into the Joomla admin and you know your password hasn't changed you may have been hacked. The directions below will get you back in, but your site should be checked over for other problems.

    Instructions

    Run this SQL query on the Joomla database using phpMyAdmin:

    UPDATE `jos_users` SET `password` = MD5( 'new_password' ) WHERE `jos_users`.`username` = "user_name" ;

    Where  'new_password' is the new password and "user_name" is the user name.

    In this case the password should be unencrypted as it will be encrypted by the MD5( 'new_password' ) in the SQL. 

    This will create a password which will allow you to login. For best security the password should be re-entered in the User Manager to add the "salt". The "salt" is a random string added after the MD5 encrypted password (with a colon separating). (md5encryptedpassword:salt)

    reset-admin-pass-phpmyadmin

    1. enable GeShi plugin from your plugin manager: Content - Code Highlighter
    2. edit the settings in your editor to allow code display
    3. edit the settings in the global article parameters/filter to allow admin to insert code in article
    4. check the PRE property in your template [css file(s)] to see if its set to display your code properly

    If all steps from 1 to 4 are done or checked and found OK then move to using the feature:

    1. in your editor create new article then insert your code between
      <pre xml:lang="[the language code]"> .. put your code in here .. </pre>
    2. make sure to choose the type of code , here is an example:
      <pre xml:lang="css"> // this to show css code format
    3. Allowed languages format code are :
      actionscript, ada, apache, asm, asp, bash, c, c_mac, caddcl, cadlisp, cdfg, cpp, csharp, css, delphi, html4strict, java, javascript, lisp, lua, mpasm, nsis, objc, oobas, oracle8, pascal, perl, php, python, qbasic, sas, smarty, vb, vbnet, visualfoxpro, xml
      and the end tag is always the same </pre>
    4. apply and check the article on your live website (NOT IN PREVIEW MODE) , if there is still a problem then go to next step
    5. click the html button in your editor to check the article source code , and make sure that the <pre>.... </pre> not affected by a <span> or <p class =""> tags , if so , correct it to show exactly how you typed them and apply again and check on your site , if needed then again recheck your editor settings to allow displaying code or even recheck all steps from 1 to 4 up here
  • Sometimes you suddenly get a huge white space below the article on the front page of Joomla (i.e. the Menu Item assigned to Default Home in the Menu manager). It happens only on the home page, all other pages are fine. You check everything to no avail - the huge white space is still there...

    I have had this happen several times on several Joomla sites, and each time I went crazy looking for clues (having forgotten because of the time eleapsed), so I decided to write it down for future reference.

    You check all divs in the CSS and in the index.php, but all is fine and nothing changes... Before you go crazy trying to find the cause, check the simple solution below. It is just the Menu Item assigned to Home which has somehow gotten corrupted.

    Solution

    • Temporarily assign a different Menu Item as Default Home page in the Menu Manager
    • Delete the Menu Item which has the problem
    • Remove that item from the Trash
    • Recreate the orignal Menu Item
    • Assign Default Home to it
    • All is well again
  • Menu Items selections available under System Links:

    The Text Separator is styled in the template under span.separator.

    Explanation Menu Item Alias

    Sometimes you want to create more than one link to a given item. Let's say you have an article that you want to show up as sub-navigation under Item A and under Item B on your menu.

    In the old days you would create two identical articles, linking one to Item A and the other to Item B. Which meant when the page's content changed, you had to change it in two places.

    You could also create two links, one from Menu Item A and the other from Menu Item B, to the same piece of content. But now you have two different URLs for the same page. That can lose you points in search engines.

    The Menu Item Alias solves both problems:

    1. Create the original menu link to a piece of content as you normally would.
    2. When you're ready to create the alias, click the New button in the Menu Manager for the menu of your choice. The next screen shows a list of options (like link to article, category blog, wrapper, login, etc). The very last item on this screen is the alias option. Choose that.
    3. Enter a title for the link (i.e. the clickable text that appears on screen). Choose the page to which you wish to direct this link from the drop down on the right. Note that the alias field here is used in SEF URLs (search engine friendly URLs) if they are enabled.
    4. Save. Now when you click your new link, you are "redirected" to the original location of this page. There's just one link for the page itself, one set of content to manage.

    The Menu Item Alias is a second link to an already configured Menu Item elsewhere. That means it will have the same article options as the original, so you cannot change what details display or not. If you want to set different display option, you will still need to create a second separate item.

  • Joomla System Messages are displayed in the area just above the content, until you refresh the page (or close the message using the X). System Messages wil be displayed when you save an article, when you vote (rate) an article, etc. They can also be very informative with error displays, for example when a component, module or plugin makes a boo-boo. The Aqua3 template for Joomla 3.x incorporates the standard Bootstrap styles for system messages (peach for alert, red for error, green for success, blue for info).

    An example is shown in the image below:

    system-messages

  • With the release of version 3.1 Joomla now has is a Tagging system, which is dynamic and works across content-types. This means that tagging (attaching labels to things on your website, like the tag "tags" above this article) is not limited to articles anymore, but can be used  in contacts, feeds, weblinks, etc. Thus Tags allow you to create lists, blogs, or other layouts that combine articles with other content types any way you like. You can dynamically create the tags from the content as well, without having to specifically navigate to the Tags component first.

    Tags in Jooma 3.1

    • Tags can be used to group, organize and display website items independently from categories or component limitations.
    • Adding a new tag is quite easy and similar to adding a new article. Just go to Tags component, then click on New, and fill in the information within the tabs. Or dynamically add the tag from the piece you are working on by just typing it in and hitting Enter. It will be automatically added to the Tags component.
    • One of the great features about the Tags implementation is that tags can be nested. One Tag can have a single parent tag and multiple child tags. This allows you to organize tags better and also to display a large number of related tags easier.
    • Each tag can also be associated with an image (full image), as well as with a teaser image.
    • Each component can tag (if the option is added by the developer).
    • You can display the tags via menu items. Once you've selected a menu item type, you can select any tag from the Tag drop-down box. Each selected tag is then aggregated within the field and can be deselected by clicking the x next to it.
    • If you just want to display the tags that contain all the items, you can use the Menu Items options and Match Type by All. There are also a number of other advanced options.

    Tags Menu Items

    There are three layouts under Tags when you create a Menu Item:

    • Tagged Items - Links to a list of items with specific tags (Blog Style).
    • Compact List of Tagged Items - Links to a compact list of items with specific tags (List).
    • List of All Tags - Links to a detailed list of all tags (List, Blog style if desired).

    How to use the Tag Menu lists:

    1. Select one of the Menu Options
    2. Select one or more tags to be used
    3. Select Type.
      The
      Type field allows you to narrow down the selection made and select only the components types that you would like to display (which contain the selected tags).
      You can of course select as many or as few as you want
      .
      The options are:
          • Article
          • Article Category
          • Contact
          • Content Category
          • Newsfeed
          • Newsfeed Category
          • User
          • Tag
          • Weblink
          • Weblinks Category

    Tags modules

    In addition to the available Menu Items there are 2 tags modules, which can be viewed from the Modules Layouts menu:

    • Popular Tags
      The Popular Tags module displays the most commonly used tags, optionally within specific time periods.
    • Similar Tags
      The Similar Tags module displays links to other items with similar tags. The closeness of the match can be specified.

    Additional features

    The Tags feature has the main component and also a Smart Search plugin for Tags (enable in Extensions >> Plug-in Manager)

  • The “Read More” function is exclusive to the Category Blog Menu Item Type. So if you enable the Read More function and then ask why it doesn't show up in a Single Article or Featured Articles Menu Item Type, it's because it's only available for the Category Blog.

  • Sometimes you want to create more than one link to a given item in your Joomla site. Let's say you have an article that you want to show up as subnavigation under Item A and Item B on your menu.

    You could create two identical articles, linking one to Item A and the other to Item B. We used to do that in the static HTML days. Unfortunately, that generally meant that you had a maintenance nightmare, since when the page's content changed, you had to change it in two places.

    With Joomla, you could create two links, one from Item A and the other from Item B, to the same piece of content. This works, but now you have two different URLs for the same page. That can lose you points in search engines.

  • Joomla uses a specific folder for images used in Articles and other content items. The folder is here:
    joomla-root/images/

    The images folder is where content images start. User created folders can be nested within the images folder. The level above contains system images that should not be deleted.

    When uploading an image using a third party text editor such as JCE the images folder becomes the upload root. But you can set another images root in JCE if you want to keep your images elsewhere.

    If you have many images to upload it's faster to FTP to the images folder than to use the Media Manager.

    The images folder is also used by third party extensions to store media such as audio and video files.

    You might wonder why the images folder isn't named articles. Many third party extensions depend on this naming and would fail if the name was changed.

RDC Web Design | Copyright © Aqua3, 2018