Joomla! Documentation - User contributions [en]

Help5.x:Articles: Options

2024-10-14T01:39:39Z

Topazgb: Added more info for the Article Options

<noinclude><languages /></noinclude>
<translate>

==Description== 
Used to set global defaults for [[#menus|menu items that display articles]]. These default values will be used when 'Use Global' is selected for an option in an Articles menu item.


For example, to show the 'Create Date' for an article in your Articles menu items, then set that option to 'Show' here and it will be the default value.


You do not need to set any of these options. Your Joomla site will work with the default settings.

==How To Access== 
{{rarr|Content,Articles}}
*click the '''Options''' toolbar button
{{anchor|screenshot}}

==Screenshot== 
:[[File:Help-4x-Content-Article-Manager-Options-screen-en.png|800px|none]]

==Form Fields== 
===Articles===
Options used in articles and the menu items [[Help4.x:Menu_Item:_Category_Blog/en#options|Blog]], [[Help4.x:Menu_Item:_Category_List/en#options|List]], [[Help4.x:Menu_Item:_Featured_Articles/en#options|Featured Articles]], [[Help4.x:Menu_Item:_List_All_Categories/en#options|List All Categories]], and [[Help4.x:Menu_Item:_Single_Article/en#options|Single Article]].


'''Layout'''
*'''Choose a Layout'''. Select the default value for Single Article menu items.
*'''Title'''. Show the Article's Title.
*'''Linked Titles'''. Show the title as a link to the article.
*'''Intro Text'''.
**Show: The Intro Text of the article will show when you drill down to the article.
**Hide: Only the part of the article after the Read More break will show.
*'''Position of Article Info'''.
**Above: Puts the article information block above the text.
**Below: Puts the article information block below the text.
**Split: Splits the article information block into 2 separate blocks. One block is above and the other is below the text.
*'''Article Info Title'''. Displays 'Details' on top of the article information block.
'''Category'''
*'''Category'''. Show the Article's Category Title.
**'''Link Category'''. Show the title as a link to that Category.{{-}}Note: You can set this to be either a blog or list layout with the [[Help4.x:Articles:_Options/en#choosealayout|Choose a Layout]] option in the Category Tab.
*'''Parent Category'''. Show the Article's Parent Category Title.
**'''Link Parent Category'''. Show the title as a link to that Category.{{-}}Note: You can set this to be either a blog or list layout with the [[Help4.x:Articles:_Options/en#choosealayout|Choose a Layout]] option in the Category Tab.
'''Associations'''
*'''Associations'''. Show the associated flags or Language Code. [[Help4.x:Multilingual_Associations/en|Multilingual only.]]
**'''Use Image Flags'''. Display language choice as image flags.
'''Author'''
*'''Author'''. Show the author of the Article.
**'''Link to Author's Contact Page'''. Show it as a link to a Contact layout for that author.{{-}}Note: The author must be set up as a [[Help4.x:Contacts:_Edit/en|Contact]]. Also, a link will not show if there is an [[Help4.x:Articles:_Edit/en#createdbyalias|Author Alias]] value for the article.
'''Date'''
*'''Create Date'''. Show the Article's create date.
*'''Modify Date'''. Show the Article's modify date.
*'''Publish Date'''. Show the Article's start publishing date.
'''Options'''
*'''Navigation'''. Show a navigation link 'Prev' or 'Next' when you drill down to the article.
*'''"Read More" Link'''. Show the Read More link to link from the part of the article before the Read More break to the rest of the Article.
*'''Read More with Title'''.
**Show: The article title is part of the Read More link. The link will be in the format "Read More: [article title]".
**Hide: The link will be "Read more".
*'''Read More Limit (characters)'''. The maximum number of characters from the title to include.{{-}}Note: This can prevent the Read More text to become excessively long if the article has a very long title.
*'''Tags'''. Show the tags for each article.
----
*'''Record Hits'''. Record the number of times the article has been viewed.
*'''Hits'''. Show the number of times the article has been displayed by a user.
*'''Unauthorised Links'''.
**Yes: The Intro Text for restricted articles will show. Clicking on the Read more link will require users to log in to view the full article content.
**No: Articles that the user is not authorised to view (based on the viewing access level for the article) will not show.
*'''Positioning of the Links'''.
**Above: Links are shown above the content.
**Below: Links are shown below the content.
{{anchor|editinglayout}}

===Editing Layout=== 
Options of the article editing page.
:[[File:Help-4x-Content-Article-Manager-Options-editing-layout-subscreen-en.png|600px]]
*'''Allow Captcha on submit'''. Select the [[Chunk4x:Extensions_Plugin_Manager_Edit_CAPTCHA_Group/en|captcha plugin]] that will be used in the article submit form. If 'Use Global' is selected, make sure a captcha plugin is selected in [[Help4.x:Site_Global_Configuration/en#captcha|Global Configuration]].
*'''Publishing Options'''. Hide the [[Help4.x:Articles:_Edit/en#publishing|Publishing Options tab]] in the Backend when editing Articles. This means that Backend users will not be able to edit the fields in this tab. It also hides the Metadata tab as well as the Author, Start Publishing and End Publishing fields of the Publishing tab when editing the front end.

These fields will always be set to their default values.
*'''Article Options'''. Hide the [[Help4.x:Articles:_Edit/en#options|Article Options tab]] in the Backend when editing Articles. This means that Backend users will not be able to edit the fields in this tab. These fields will always be set to their default values.
*'''Edit Screen Options'''. Hide the [[Help4.x:Articles:_Edit/en#configureeditscreen|Configure Edit Screen tab]] when editing Articles.
*'''Article Permissions'''. Hide the [[Help4.x:Articles:_Edit/en#permissions|Permissions tab]] when editing Articles.
*'''Multilingual Associations'''. Hide the [[Help4.x:Articles:_Edit/en#associations|Associations tab]] when editing Articles.
*'''Enable Versions'''. Save version history for Articles and Categories.
*'''Maximum Versions'''. The maximum number of versions to store for an Article or Category. If an Article or Category is saved and the maximum number of versions has been reached, the oldest version will be deleted automatically. If set to "0", then versions will never be deleted automatically. [[Help4.x:Components_Version_History/en|Learn more.]]
*'''Frontend Images and Links'''. Hide the Images and Links tab in the Frontend article editor screen.
*'''Administrator Images and Links'''. Hide the [[Help4.x:Articles:_Edit/en#imagesandlinks|Images and Links tab]] in the Backend when editing Articles.
----
*'''URL A Target Window'''. Sets the default value for the target for the first Link in the article. Choices are:
**Open in parent window: Opens the in the main browser window, replacing the current Joomla article.
**Open in new window: Opens the link in a new browser window.
**Open in popup: Opens the link in a popup browser window (without full navigation controls).
**Modal: Opens the link in a modal popup window.
*'''URL B Target Window'''. Sets the default value for the target for the second Link in the article. Same options as URL A.
*'''URL C Target Window'''. Sets the default value for the target for the third Link in the article. Same options as URL A.
----
*'''Intro Image Class'''. Sets the class attribute for an Intro Image selected in the Intro Image field. [https://cassiopeia.joomla.com/help Learn more.]
*'''Full Text Image Class'''. Sets the class attribute for an Full Article Image selected in the Full Article Image field. [https://cassiopeia.joomla.com/help Learn more.]

===Category=== 
Options control how a Category and its articles will show. They are used in categories and the menu items [[Help4.x:Menu_Item:_Category_Blog/en#category|Blog]], [[Help4.x:Menu_Item:_Category_List/en#category|List]], and [[Help4.x:Menu_Item:_List_All_Categories/en#category|List All Categories]].
:[[File:Help-4x-Content-Article-Manager-Options-category-subscreen-en.png|600px]]
{{anchor|choosealayout}}
*'''Choose a Layout'''. Select the default layout to show when you click on a Category link.
*'''Category Title'''. Show the title of the category.
*'''Category Description'''. Show the description for the category.
*'''Category Image'''. Show the category image.
*'''Subcategory Levels'''. Control how many levels of subcategories to show.
*'''Empty Categories'''. Show categories that don't contain any articles or subcategories.
*'''No Articles Message'''. Show a message "There are no articles in this category".
*'''Subcategories Heading'''. Show the Subcategories as subheading on the page.
*'''Subcategories Descriptions'''. Show the descriptions for subcategories.
*'''# Articles in Category'''. Show a count of the total number of articles in each category.
*'''Tags'''. Show the tags for the category.

===Categories=== 
Options control the display of the menu item [[Help4.x:Menu_Item:_List_All_Categories/en#categories|List All Categories]].


[[File:Help-4x-Content-Article-Manager-Options-categories-subscreen-en.png|600px]]
*'''Top Level Category Description'''. Show the description for the top-level category.
*'''Subcategory Levels'''. Control how many levels of subcategories to show.
*'''Empty Categories'''. Show categories that don't contain any articles or subcategories.
*'''Subcategories Descriptions'''. Show the description for subcategories.
*'''# Articles in Category'''. Show a count of the total number of articles in each category.

===Blog/Featured Layouts=== 
Options control the layout of the menu items [[Help4.x:Menu_Item:_Category_Blog/en#blog|Blog]], [[Help4.x:Menu_Item:_Featured_Articles/en#blog|Featured Articles]], and [[Help4.x:Menu_Item:_List_All_Categories/en#blog|List All Categories]].


[[File:Help-4x-Content-Article-Manager-Options-blog-featured-layout-subscreen-en.png|600px]]
*'''# Leading Articles'''. Number of Articles to show using the full width of the main display area. "0" means that no Articles will show when using the full width. If an Article has a "Read more..." break, only the part of the text before the break (the Intro text) will display.
*'''Leading Article Class'''. You can add any CSS class for your own styling ideas. Add a border on top with class boxed.{{-}}For image position use for example image-left, image-right. Add image-alternate for alternate ordering of intro images.
*'''# Intro Articles'''. Determines the number of Articles to display after the leading Article. These Articles will display in the number of columns set in the Columns parameter below. If an Article has a "Read more..." break, only the text before the break (Intro text) will display, followed by a "Read more..." link. The order in which to display the articles is determined by the Category Order and Article Order parameters below.
*'''Article Class'''. You can add any CSS class for your own styling ideas. Add a border on top with class boxed.{{-}}For image position use for example image-left, image-right. Add image-alternate for alternate ordering of intro images.
*'''# Columns'''. The number of columns to use in the Intro Articles area. This is normally between 1 and 3 (depending on the template you are using). If 1 is used, the Intro Articles will display using the full width of the display area, just like the Leading Articles.
*'''Multi Column Direction'''. In multi-column blog layouts, whether to order articles Down the columns or Across the columns.
<ul>
*Down: Order articles going down the first column and then over to the next column, for example:
<ul>
{| class="wikitable"
|-
!colspan="3"|article 1
|-
| article 2
| article 4
| article 6
|-
| article 3
| article 5
| article 7
|}
</ul>
</ul>
<ul>
*Across: Order articles going across the columns and then back to the first column, for example:
<ul>
{| class="wikitable"
|-
!colspan="3"|article 1
|-
| article 2
| article 3
| article 4
|-
| article 5
| article 6
| article 7
|}
</ul>
</ul>
*'''# Links'''. The number of Links to display in the Links area of the page. These links allow a User to link to additional Articles, if there are more Articles than can fit on the first page of the Blog Layout.
*'''Include Subcategories'''.
**None: Only articles from the current category will show.
**All: All articles from the current category and all subcategories will show.
**1-5: All articles from the current category and subcategories up to and including that level will show.
*'''Linked Intro Image'''. If Yes, a click on the intro image shows the article.

===List Layouts=== 
Options control the layout of the menu items [[Help4.x:Menu_Item:_Category_List/en#listlayouts|List]] and [[Help4.x:Menu_Item:_List_All_Categories/en#listlayouts|List All Categories]].


[[File:Help-4x-Content-Article-Manager-Options-list-layout-subscreen-en.png|600px]]
*'''Display Select'''. Show the Display # control that allows the user to select the number of articles to show.
*'''Filter Field'''. Show a text field in the Frontend where a user can filter the articles.{{-}}Options in the Backend menu item edit.
**Hide: Don't show a filter field.
**Title: Filter on article title.
**Author: Filter on the author's name.
**Hits: Filter on the number of article hits.
**Tags: Filter on the article tags.
**Month (published): Filter on the month of published articles.
*'''Table Headings'''. Show a heading in the article list in the Frontend.
*'''Date'''. Show a date in the list.
**Hide: Don't show any date.
**Created: Show the created date.
**Modified: Show the date of the last modification.
**Published: Show the start publishing date.
*'''Hits'''. Show the number of hits for articles.
*'''Author'''. Show the name of the author.
*'''# Articles to List'''. Number of articles shown in the list.

===Shared=== 
Options shared by the menu items [[Help4.x:Menu_Item:_Category_Blog/en#blog|Blog]], [[Help4.x:Menu_Item:_Category_List/en#listlayouts|List]], and [[Help4.x:Menu_Item:_Featured_Articles/en#blog|Featured Articles]].


[[File:Help-4x-Content-Article-Manager-Options-shared-subscreen-en.png|600px]]
*'''Category Order'''.
**No Order: Articles are ordered only by the Article Order, without regard to Category.
**Title Alphabetical: Categories are displayed in alphabetical order (A to Z).
**Title Reverse Alphabetical: Categories are displayed in reverse alphabetical order (Z to A).
**Category Order: Categories are ordered according to the Order column entered in [[Help4.x:Articles:_Categories/en#ordering|Articles: Categories]].
*'''Article Order'''.
**Most Recent First: Articles are displayed starting with the most recent and ending with the oldest.
**Oldest First: Articles are displayed starting with the oldest and ending with the most recent.
**Title Alphabetical: Articles are displayed by Title in alphabetical order (A to Z).
**Title Reverse Alphabetical: Articles are displayed by Title in reverse alphabetical order (Z to A).
**Author Alphabetical: Articles are displayed by Author in alphabetical order (A to Z).
**Author Reverse Alphabetical: Articles are displayed by Author in reverse alphabetical order (Z to A).
**Most Hits: Articles are displayed by the number of hits, starting with the one with the most hits and ending with the one with the least hits.
**Least Hits: Articles are displayed by the number of hits, starting with the one with the least hits and ending with the one with the most hits.
**Ordering: Articles are ordered according to the Order column entered in [[Help4.x:Articles/en#ordering|Articles]].
**Ordering Reverse: Articles are ordered reverse to the according of the Order column entered in [[Help4.x:Articles/en#ordering|Articles]].
*'''Date for Ordering'''. The date used when articles are sorted by date.
**Created: Use the article created date.
**Modified: Use the article modified date.
**Published: Use the article start publishing date.
*'''Pagination'''. Pagination provides page links at the bottom of the page that allow the User to navigate to additional pages. These are needed if the Articles will not fit on one page.
**Hide: Pagination links not shown. Note: Users will not be able to navigate to additional pages.
**Show: Pagination links shown if needed.
**Auto: Pagination links shown if needed.
*'''Pagination Summary'''. Show the current page number and total pages (e.g., "Page 1 of 2") at the bottom of each page.
*'''Featured Articles'''.
**Show: Display featured articles and non-featured articles.
**Hide: Display only non-featured articles.
**Only: Display only featured articles.

===Integration=== 
Options control how Articles integrate News Feeds, Routing, Custom Fields, and Workflow.


[[File:Help-4x-Content-Article-Manager-Options-integration-subscreen-en.png|600px]]


'''News Feeds'''
*'''RSS Feed Link'''. If set to Show, a Feed Link will show up as a feed icon in the address bar of most browsers.
*'''Include in Feed'''.
**Intro Text: Only the article's intro text will show in the feed.
**Full Text: The entire text of the article will show in the feed.
*'''"Read More" Link'''. Show a "Read more" link in the feed.
'''Routing'''
*'''Remove IDs from URLs'''. Remove the database id of articles in a link.
'''Custom Fields'''
*'''Edit Custom Fields'''. Enable the creation of custom fields. [[Help4.x:Fields:_Edit/en|Learn more.]]
'''Workflow'''
*'''Enable Workflow'''. Use customised workflows to manage articles. [[J4.x:Workflow/en|Learn more.]]
{{anchor|permissions}}

===Permissions=== 
This section lets you set up the default [[Access_Control_List/en|Access Control List]] permissions for all articles in all categories.
:[[File:Help-4x-Content-Article-Manager-Options-permissions-subscreen-en.png|600px|none]]
To change the permissions for articles and categories, do the following.
#Select the '''Group''' by clicking its title located on the left.
#Find the desired '''Action'''.
#*'''Configure ACL & Options'''. Users can edit the options and permissions.
#*'''Configure Options Only'''. Users can edit the options exept the permissions.
#*'''Access Administration Interface'''. Users can access user administration interface.
#*'''Create'''. Users can create articles and categories.
#*'''Delete'''. Users can delete articles and categories.
#*'''Edit'''. Users can edit articles and categories.
#*'''Edit State'''. User can change the published state and related information.
#*'''Edit Own'''. Users can edit own created articles and categories.
#*'''Edit Custom Field Value'''. Users can edit any value of custom fields submitted in articles and categories.
#*'''Manage Workflows'''. Users can manage workflows.
#*'''Execute Transition'''. Users can execute transitions.
#Select the desired permission for the action you wish to change.
#*'''Inherited'''. Inherited for users in this Group from the [[Help4.x:Site_Global_Configuration/en#permissions|Global Configuration]] permissions.
#*'''Allowed'''. Allowed for users in this Group.{{-}}Note: If this action is Denied at one of the higher levels, the Allowed permission here will not take effect. A Denied setting cannot be overridden.
#*'''Denied'''. Denied for users in this Group.
#Click '''Save''' in '''Toolbar''' at top. When the screen refreshes, the Calculated Setting column will show the effective permission for this Group and Action.

==Toolbar== 
At the top of the page you will see the toolbar shown in the [[#screenshot|Screenshot]] above.
*'''Save'''. Saves the articles options and stays in the current screen.
*'''Save & Close'''. Saves the articles options and closes the current screen.
*'''Close'''. Closes the current screen and returns to the previous screen without saving any modifications you may have made.
*'''Toggle Inline Help'''. Show help text below some options.
*'''Help'''. Opens this help screen.

==Quick Tips== 
*If you are a beginning user, you can just keep the default values here until you learn more about using global options.
*If you are an advanced user, you can save time by creating good default values here. When you set up menu items and create articles, you will be able to accept the default values for most options.
*All values set here can be overridden at the menu item, category, or article level.

==Related Information== 
{{:Chunk4x:Help_screen_related_Articles/en}}

</translate>
{{Cathelp|5.0|Article Manager Help Screens|Content Help Screens}}

Installing Joomla on Debian Linux

2024-08-27T20:18:13Z

Topazgb: added 5.x icon

{{needs|technical review|Needs updating to latest Joomla, PHP, MySQL Versions}}

== Preface ==
This document guides you through the manual installation of Joomla! on ''Debian GNU Linux'' or one of its derivatives such as ''Ubuntu'', ''Knoppix'' or ''GRML''. Note that this guide applies to Joomla! {{JVer|2.5}} {{JVer|3.5}} {{JVer|3.6}} {{JVer|4.x}} {{JVer|5.x}} . It has been successfully tested on Debian 4.0 [Etch], Debian 5.0 [Lenny], Ubuntu 8.04 LTS [Hardy Heron], Ubuntu 10.10 [maverick] and Ubuntu 11.10 (Oneiric Ocelot). It will work for all Debian-based Linux distributions as well.

Also note that this guide assumes you're installing Joomla! in a single hosting environment, running PHP as module. If you want to run multiple websites as a web hosting service provider, for security reasons you should consider setting up an suPHP (php5-cgi, libapache2-mod-suphp) environment, where every virtual Apache host runs under its own UID.

== Installing Joomla! ==
=== Prerequisites ===
You will need to install Apache2, ''mysql-server-5.0'', ''mysql-client-5.0'' and ''php5'' in order to have a web server for Joomla!.

=== Which Stack Should I Choose? ===
* [[Installing_Joomla_on_Debian_Linux#XAMPP|XAMPP]] automatically configures ownership.
* [[Installing_Joomla_on_Debian_Linux#LaMp|LaMp]] requires use of the ''chown'' command.
* [[Installing_Joomla_on_Debian_Linux#BitNami_Joomla.21_stack|BitNami Joomla! Stack]] is free, self-contained and automatically configures the LAMP stack and Joomla!

== XAMPP ==
Download [https://sourceforge.net/projects/xampp/files/XAMPP%20Linux/ XAMPP] for Linux to your your Home folder.

=== Install XAMPP ===
Open Terminal and enter:

<syntaxhighlight lang="bash">
sudo tar xvfz xampp-linux-1.8.3.tar.gz -C /opt
</syntaxhighlight>

(Replace ''xampp-linux-1.8.3.tar.gz'' with the version of XAMPP you downloaded).

This installs Apache2, MySQL and PHP as well as an FTP server.

<syntaxhighlight lang="bash">
sudo /opt/lampp/lampp start
</syntaxhighlight>

and
<syntaxhighlight lang="bash">
sudo /opt/lampp/lampp stop
</syntaxhighlight>

...starts/stops all the services.

=== Test Your XAMPP Localhost Server ===
Open your Browser and point it to
http://localhost
The ''index.php'' will redirect to
http://localhost/xampp

There you will find instructions on how to change default usernames and passwords. On a PC that does not serve files to the Internet or LAN, changing the defaults is a personal choice.

=== Multiple Versions of XAMPP ===
It can be useful to have access to several versions of XAMPP on your PC. (To have available different versions of PHP for testing.) XAMPP doesn't make this easy but it is possible - see [https://stackoverflow.com/questions/47498835/installing-two-versions-of-php-with-xampp-on-ubuntu-system "how to" article]. (For Linux only.)

=== Get Joomla ===
Download the latest Joomla installation zip [https://downloads.joomla.org/us/]

Unzip to your hard drive

Connect to localhost with XAMPP's FTP client
Default
nobody
lampp

Use FTP to create a folder for your Joomla on the localhost server

FTP the unpacked Joomla installation files to the newly-created Joomla folder.

'''Important'''
* The XAMPP installation sets the correct Ownership of the files and permissions.
* Using the ''chown'' command will cause ownership problems with XAMPP.
* Using Nautilus to manipulate folders/files on localhost will cause ownership problems with XAMPP.

=== Configure Joomla ===
In your Browser type:
http://localhost/yournewjoomlafolder

In the first Joomla installation screen if error reporting is shown as on then:

In your Terminal type
<syntaxhighlight lang="bash">
sudo gedit /opt/lampp/etc/php.ini
</syntaxhighlight>

In the ''php.ini'' file, locate
<syntaxhighlight lang="ini">
error_reporting =
</syntaxhighlight>
And change the value to
<syntaxhighlight lang="ini">
error_reporting = E_ALL & ~E_NOTICE & ~E_DEPRECATED
</syntaxhighlight>

Also locate
<syntaxhighlight lang="ini">
display_errors = On
</syntaxhighlight>
And change the value to
<syntaxhighlight lang="ini">
display_errors = Off
</syntaxhighlight>

Stop then restart XAMPP for the new settings to take effect.

FTP layer is '''not''' needed

'''Database info'''

'''Host''': ''localhost''

'''Database name''': ''test''
:''(XAMPP will automatically create a database of the name you specify).''

'''Default Database user''': ''root''
:There is no Password for '''Database user''': ''root''.

Administrator password is your choice.

Installing Sample Data is recommended for the novice user.

After installation delete the installation directory and point your Browser to:
http://localhost/yournewjoomlafolder
or
http://localhost/yournewjoomlafolder/administrator

=== Create a Link in the Ubuntu Menu ===
'''To create a GUI for XAMPP connected to your Ubuntu menu'''

Open up the Terminal and type
<syntaxhighlight lang="bash">
sudo gedit /usr/share/applications/xampp-control-panel.desktop
</syntaxhighlight>

Then copy the following into the gedit and save.

<syntaxhighlight lang="ini">
[Desktop Entry]
Encoding=UTF-8
Name=XAMPP Control Panel
Comment=Start and Stop XAMPP
Exec=gksudo "python /opt/lampp/share/xampp-control-panel/xampp-control-panel.py"
Icon=/usr/share/icons/Tango/scalable/devices/network-wired.svg
Terminal=false
Type=Application
Categories=GNOME;Application;Network;
StartupNotify=true
</syntaxhighlight>

'''N.B.''' Ubuntu 11.10 needs ''python-glade2'' installed in order to run the GUI. ''python-glade2'' can be found in the Ubuntu Software Center.

== LaMp ==
You will find instructions on [https://wiki.debian.org/LaMp wiki.debian.org]. Make sure that you have installed ''bzip2'' for extracting the downloaded Joomla! package.

You can check this by the following command:
<syntaxhighlight lang="bash">
$ dpkg -l | grep bzip2
</syntaxhighlight>

Note that the dollar sign '$' shell prompt is indicating you're a ''regular user''. We will later see a hash mark (#) shell prompt, which indicates that you're the super user ''root'' after issuing an ''su'' or ''sudo''. The first policy for a secure Linux system administration on the command line (but under X also) is to issue commands with the lowest permission as possible.

If ''bzip2'' is not installed, you won't get an output. Then you can quickly install it via aptitude:
<syntaxhighlight lang="bash">
$ su -c "aptitude install bzip2"
</syntaxhighlight>

Here we see the first command executed with root permissions, because a regular user is not allowed to install new software. The '-c' option passes the following command to ''su'' and hereafter it terminates instead of switching to a root shell.

=== Configure PHP5 ===
In the pre -install check (you get to that when the install is complete and are setting up Joomla at the web page), Output Buffering was On and it's recommended that it should be Off. To do so:
edit /etc/php5/apache2/php.ini , comment out this line: output_buffering = 4096 , by putting a ';' in front. it'll look like this when done:
;output_buffering = 4096

There were also warnings on the install screen regarding ''suhosin''. To make the suggested changes, edit this file:
/etc/php5/conf.d/suhosin.ini
I set these:
<pre>
suhosin.post.max_array_index_length = 256
suhosin.post.max_totalname_length = 8192
suhosin.post.max_vars = 2048
suhosin.request.max_array_index_length = 256
suhosin.request.max_totalname_length = 8192
suhosin.request.max_vars = 2048
</pre>

=== Configure MySQL ===
It is time to create a database for Joomla! You can do this by the following commands:
mysqladmin -u root -p create joomla

Replace ''joomla'' with the name of choice for Joomla!'s database.

Now create a MySQL user different from root for Joomla!'s database. First enter into MySQL system with:
mysql -u root -p
Then at the ''mysql>'' prompt, enter the following. Make sure you replace ''joomla'' with the name of Joomla!'s database from above. Replace ''yourusername'' with the user name you choose for the MySQL user accessing Joomla!'s database, and replace ''yourpassword'' with your password of choice for the MySQL user.
<syntaxhighlight lang="bash">
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES, \
LOCK TABLES ON joomla.* TO 'yourusername'@'localhost' IDENTIFIED BY 'yourpassword';
</syntaxhighlight>
Activate the settings and quit : [ there will be a mysql> prompt:
FLUSH PRIVILEGES;
\q

After disconnecting from the database server, you should remove the login information of your just new created MySQL user by editing MySQL's history file.
vi ~/.mysql_history

You can use any editor of your choice such as ''nano'', ''vi'' or ''emacs'' that is installed on your system.

=== Get Joomla! Source ===
Now it is time to download the Joomla! sources. Currently you will find download links on the [https://downloads.joomla.org/us/ Joomla Downloads] page. For version 1.5.11, you may do the following from command line, assuming your current working directory is your home folder ''/home/user'':
<syntaxhighlight lang="bash">
$ wget http://joomlacode.org/gf/download/frsrelease/10209/40306/Joomla_1.5.11-Stable-Full_Package.tar.bz2
$ cd /var/www
$ su
# mkdir -m 0755 joomla
# cd joomla
# tar -xvjf /home/user/Joomla_1.5.11-Stable-Full_Package.tar.bz2
</syntaxhighlight>

for 1.7 use this wget line:
wget http://joomlacode.org/gf/download/frsrelease/15278/66553/Joomla_1.7.0-Stable-Full_Package.tar.bz2
Check http://joomlacode.org/gf/project/joomla/frs/ for an updated package.

Here is the first time we see this hash mark (#) shell prompt. We call ''su'' without any options, because we want to issue root commands more than only one time. Calling ''su'' that way will prompt us for the super user's password and then change the actual shell environment, respectively $UID and $EUID.

=== Set Ownership and Permissions ===
If you want to allow writing in the entire Joomla folder, simply do:

<syntaxhighlight lang="bash">
chown -R www-data:www-data /var/www/joomla
</syntaxhighlight>

If you want a more restrictive approach, do this instead:
<pre>
chown -R root:root /var/www/joomla
cd /var/www/joomla
PLACES='
administrator/backups
administrator/components
administrator/modules
administrator/templates
cache
components
images
images/banners
images/stories
language
mambots
mambots/content
mambots/editors
mambots/editors-xtd
mambots/search
media
modules
templates
'
for i in $PLACES; do chown -R www-data:www-data $i; done
</pre>

Now set file and directory permissions:
<syntaxhighlight lang="bash">
find /var/www/joomla -type f -exec chmod 0644 {} \;
find /var/www/joomla -type d -exec chmod 0755 {} \;
</syntaxhighlight>

=== Configure Joomla! ===
Open your web browser, and point it to http://localhost/joomla. Replace ''localhost'' with your servers IP or domain name if it you are installing on a remote system.

You will be guided through the final steps of setting up Joomla!, have your MySQL user, password and database name available.

When you reach the final screen with congratulations on installing Joomla!, remove the installation directory. From root terminal:
<syntaxhighlight lang="bash">
# rm -rf /var/www/joomla/installation/
# exit
$
</syntaxhighlight>

And that's it! Now you can log into the Administrator interface of your fresh installed Joomla!.

== BitNami Joomla! Stack ==

=== What is BitNami Joomla! Stack? ===
BitNami Joomla! Stack is an all-in-one installer that makes it easy to install Joomla on your computer. It is free, easy to use and self-contained. That means it bundles and automatically configures every piece of software (dependency) necessary to run Joomla for development or production purposes, including Apache, MySQL and PHP.
You can [https://bitnami.com/stack/joomla download the latest version of BitNami Joomla! stack] for Windows, Linux and OS X.

=== Installing Joomla! Stack ===
Regardless of which operating system you are running (Windows/Linux/Mac), the install process is the same.

Find the installer you just downloaded. The filename will be similar to ''bitnami-joomla-VERSION-linux-installer.run''. Double click on the icon to launch the installer.

Note: If you are using Linux you will have to give executable permissions to the file first, using this command:
chmod +x /path/to/bitnami-joomla-VERSION-linux-installer.run

[[File:Joomla_welcome.png]]

Click ''Forward''.

[[File:Joomla_components.png]]

Select the components you want to install. If you are not sure, leave the default components checked. Click ''Forward'' when you are done.

[[File:Joomla_directory.png]]

Now it will ask where you want to install the program. Provide the location where you want to install the BitNami Joomla! stack and click ''Forward'' when you are done.

[[File:Joomla_userdata.png]]

The user and password you provide here will be used to create the Administrator account in Joomla! Click ''Forward'' when done.

[[File:Joomla_sitename.png]]

Type in the name you want to use for your Joomla site, and click ''Forward''.

[[File:JoomlaReadytoinstall.png]]

The installer is now ready to begin the installation process. Click ''Forward''.

[[File:JoomlaCopyingfiles.png]]

Wait a minute while the installer copies the files and configures your Joomla! installation.

[[File:Joomlafinalscreen.png]]

Joomla! is now set up and ready to be used. Click ''Finish'' to launch the application.

[[File:Joomlaapplicationscreen.png]]

You can now log in using the username and password you provided during the installation.
<noinclude>[[Category:Installation]][[Category:Server setup local]][[Category:Server configurations]]<noinclude>

Joomla! CMS versions

2024-03-20T23:44:01Z

Topazgb: British date format

<noinclude><languages /></noinclude>
{{Joomla version|version={{CurrentSTSVer4|maintenance}}|comment='''<translate> Bridge Version</translate>'''}}
{{Joomla version|version={{CurrentSTSVer5|maintenance}}|comment='''<translate>  Stable Version</translate>'''}}

<translate>
Check for the latest Joomla! CMS version. If you are not on the latest release, read the release notes to see if you need to upgrade. If a release is being made in order to address security issues then it is strongly advised that you upgrade as soon as possible. You can see the release history of each series in the table below. Click the '''version history link''' in the notes column to find details on exact release date, release notes and package and MD5s.</translate>

<translate>
*Normally, you should use the latest version of Joomla! for a new site unless you have a specific reason not to.</translate>
<translate>
*The latest version can be downloaded from [https://downloads.joomla.org Joomla! Downloads site].</translate>
<translate>
* Make sure you subscribe to the [https://developer.joomla.org/security-centre.html Joomla! Security Announcements] feed. This RSS feed is used to make announcements, including the availability of new releases, that could affect the security of your site. You have the option to subscribe to this feed by RSS or email.</translate>
<translate>
* If you are running an earlier release of the current version (for example, you are running 3.1.6 and the current version is 3.4.1), you should upgrade to the current version. Each minor release fixes a number of bugs and security issues. It is always good practice to upgrade to the latest maintenance version as a first step in troubleshooting a problem and fixing any newly discovered security issues.</translate>
<translate>

* See the [https://developer.joomla.org/roadmap.html Joomla! Project Roadmap] for the time frames of all future releases.</translate>
<translate>
==Joomla! CMS Versions== 
</translate>
{| border=1 cellpadding=2 cellspacing=0 style="text-align:center; border-collapse:collapse; border-color:#000;"
| rowspan=2 style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
CMS Version</translate>
| rowspan=2 style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
Available</translate>
| colspan=2 style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
Support</translate>
| style='display:none;' |
| rowspan=2 style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
End of Life</translate>
| rowspan=2 style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
Upgrade Type</translate>
| rowspan=2 style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
Notes</translate>
| rowspan=2 style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
Latest Release</translate>
|-
| style='display:none;' |
| style='display:none;' |
| style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
Bugs</translate>
| style="text-align:center; background-color:#4a86e8; font-weight:bold;" | <translate>
Security</translate>
| style='display:none;' |
| style='display:none;' |
| style='display:none;' |
| style='display:none;' |
|-
| style="background-color:#d9ead3; font-weight:bold;" | 5.0
| style="background-color:#d9ead3;" | [[File:Checkmark.png|center]]
| style="background-color:#d9ead3;" | [[File:Checkmark.png|center]]
| style="background-color:#d9ead3;" | [[File:Checkmark.png|center]]
| style="background-color:#d9ead3;" | 5.1 release
| style="background-color:#d9ead3;" | <translate>  One-click</translate>
| style="background-color:#d9ead3;" | <translate>  Recommended for all new installations [[S:MyLanguage/Joomla 5.0 version history|Joomla! 5.0 version history]]</translate>
| style="background-color:#d9ead3;" | {{CurrentSTSVer5|maintenance}}
|-
| style="background-color:#d9ead3; font-weight:bold;" | 4.4
| style="background-color:#d9ead3;" | [[File:Checkmark.png|center]]
| style="background-color:#d9ead3;" | [[File:Checkmark.png|center]]
| style="background-color:#d9ead3;" | [[File:Checkmark.png|center]]
| style="background-color:#d9ead3;" | 17th Oct 2025
| style="background-color:#d9ead3;" | <translate>  Migration to Joomla! 5.0</translate>
| style="background-color:#d9ead3;" | <translate>  Upgrade to {{CurrentSTSVer5|maintenance}} now [[S:MyLanguage/Joomla 4.4 version history|Joomla! 4.4 version history]]</translate>
| style="background-color:#d9ead3;" | {{CurrentSTSVer4|maintenance}}
|-
| style="background-color:#f4cccc; font-weight:bold;" | 4.3
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | 4.4 release
| style="background-color:#f4cccc;" | <translate> One-click</translate>
| style="background-color:#f4cccc;" | <translate> Upgrade to {{CurrentSTSVer4|maintenance}} now [[S:MyLanguage/Joomla 4.3 version history|Joomla! 4.3 version history]]</translate>
| style="background-color:#f4cccc;" | 4.3.4
|-|-
| style="background-color:#f4cccc; font-weight:bold;" | 4.2
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | 4.3 release
| style="background-color:#f4cccc;" | <translate>  One-click</translate>
| style="background-color:#f4cccc;" | <translate>  Upgrade to {{CurrentSTSVer4|maintenance}} now [[S:MyLanguage/Joomla 4.2 version history|Joomla! 4.2 version history]]</translate>
| style="background-color:#f4cccc;" | 4.2.9
|-
| style="background-color:#f4cccc; font-weight:bold;" | 4.1
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | 4.2 release
| style="background-color:#f4cccc;" | <translate> One-click</translate>
| style="background-color:#f4cccc;" | <translate> Upgrade to {{CurrentSTSVer4|maintenance}} now [[S:MyLanguage/Joomla 4.1 version history|Joomla! 4.1 version history]]</translate>
| style="background-color:#f4cccc;" | 4.1.5
|-
| style="background-color:#f4cccc; font-weight:bold;" | 4.0
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | 4.1 release
| style="background-color:#f4cccc;" | <translate> Migration from Joomla! 3.10</translate>
| style="background-color:#f4cccc;" | <translate> Upgrade to {{CurrentSTSVer4|maintenance}} now [[S:MyLanguage/Joomla 4.0 version history|Joomla! 4.0 version history]]</translate>
| style="background-color:#f4cccc;" | 4.0.6
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.10
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | 17.08.2023
| style="background-color:#f4cccc;" | <translate> One-click from Joomla! 3.9</translate>
| style="background-color:#f4cccc;" | <translate> Recommended for migration to Joomla! 4 [[S:MyLanguage/Joomla 3.10 version history|Joomla! 3.10 version history]]</translate>
| style="background-color:#f4cccc;" | {{CurrentSTSVer|maintenance}}
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.9
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate> 3.10 release</translate>
| style="background-color:#f4cccc;" | <translate> One-click</translate>
| style="background-color:#f4cccc;" | <translate> Upgrade to {{CurrentSTSVer|maintenance}} now [[S:MyLanguage/Joomla 3.9 version history|Joomla! 3.9 version history]]</translate>
| style="background-color:#f4cccc;" | 3.9.28
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.8
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate> 3.9 release</translate>
| style="background-color:#f4cccc;" | <translate> One-click</translate>
| style="background-color:#f4cccc;" | <translate> Upgrade to {{CurrentSTSVer|maintenance}} now [[S:MyLanguage/Joomla 3.8 version history|Joomla! 3.8 version history]]</translate>
| style="background-color:#f4cccc;" | 3.8.13
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.7
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate> 3.8 release</translate>
| style="background-color:#f4cccc;" | <translate> One-click</translate>
| style="background-color:#f4cccc;" | <translate>

Upgrade to {{CurrentSTSVer|maintenance}} now [[S:MyLanguage/Joomla 3.7 version history|Joomla! 3.7 version history]]</translate>
| style="background-color:#f4cccc;" | 3.7.5
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.6
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
3.7 release</translate>
| style="background-color:#f4cccc;" | <translate>
One-click</translate>
| style="background-color:#f4cccc;" | <translate>
Upgrade to {{CurrentSTSVer|maintenance}} now [[S:MyLanguage/Joomla 3.6 version history|Joomla! 3.6 version history]]</translate>
| style="background-color:#f4cccc;" | 3.6.5
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.5
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
3.6 release</translate>
| style="background-color:#f4cccc;" | <translate>
One-click</translate>
| style="background-color:#f4cccc;" | <translate>
Upgrade to {{CurrentSTSVer|maintenance}} now [[S:MyLanguage/Joomla 3.5 version history|Joomla 3.5 version history]]</translate>
| style="background-color:#f4cccc;" | 3.5.1
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.4
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
3.5 release</translate>
| style="background-color:#f4cccc;" | <translate>
One-click</translate>
| style="background-color:#f4cccc;" | <translate>

Upgrade to {{CurrentSTSVer|maintenance}} now [[Joomla 3.4 version history]]</translate>
| style="background-color:#f4cccc;" | 3.4.8
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.3
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
3.4 release</translate>
| style="background-color:#f4cccc;" | <translate>
One-click</translate>
| style="background-color:#f4cccc;" | <translate>
Upgrade to {{CurrentSTSVer|maintenance}} now</translate> <translate>

[[Joomla 3.3 version history]]</translate>
| style="background-color:#f4cccc;" | 3.3.6
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.2
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
Oct 2014<ref>Bug fixes will cease April 2014, security fixes only, see [https://community.joomla.org/blogs/leadership/raising-the-bar-on-security.html Raising The Bar On Security]. <blockquote>"Also, for the six months after Joomla! 3.3 is released, the Joomla! Project will be releasing Security Updates for both 3.2 '''and''' 3.3 so any new vulnerabilities can be promptly patched with a one-click update without the need to immediately update to Joomla! 3.3, giving you time to request your hosting provider to update their PHP version."</blockquote></ref></translate>
| style="background-color:#f4cccc;" | <translate>
One-click</translate>
| style="background-color:#f4cccc;" | <translate>
Upgrade server's PHP to 5.3.10 or greater and upgrade to {{CurrentSTSVer|maintenance}} now [[Joomla 3.2 version history]]</translate>
| style="background-color:#f4cccc;" | 3.2.7
|-
| style="background-color:#f4cccc; font-weight:bold;" | 3.1
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
Dec 2013</translate>
| style="background-color:#f4cccc;" | <translate>
One-click</translate>
| style="background-color:#f4cccc;" | <translate>
Upgrade to {{CurrentSTSVer|maintenance}} now</translate> <translate>
[[Joomla 3.1 version history]]</translate>
| style="background-color:#f4cccc;" | 3.1.6
|-
| style="background-color:#f4cccc; width:100px; font-weight:bold;" | 3.0
| style="background-color:#f4cccc; width:100px;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc; width:100px;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc; width:100px;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc; width:100px;" | <translate>
May 2013</translate>
| style="background-color:#f4cccc; width:100px;" | <translate>
One-click</translate>
| style="background-color:#f4cccc; width:306px;" | <translate>
Upgrade to {{CurrentSTSVer|maintenance}} now [[Joomla 3.0 version history]]</translate>
| style="background-color:#f4cccc;" | 3.0.4
|-
| style="background-color:#f4cccc; font-weight:bold;" | 2.5
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
December 31st, 2014</translate>
| style="background-color:#f4cccc;" | <translate>
Migration to 3.x</translate>
| style="background-color:#f4cccc;" | <translate>
Upgrade to</translate> {{CurrentSTSVer}} <translate>
now</translate> <translate>
[[Joomla 2.5 version history]]</translate>
| style="background-color:#f4cccc;" | {{CurrentLTSVer|maintanence}}
|-
| style="background-color:#f4cccc; font-weight:bold;" | 1.7
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
Feb 2012</translate>
| style="background-color:#f4cccc;" | <translate>
Migration to 3.x</translate>
| style="background-color:#f4cccc;" | <translate>
Plan to migrate to {{CurrentSTSVer|maintenance}} now [[Joomla 1.7 version history]]</translate>
| style="background-color:#f4cccc;" | 1.7.5
|-
| style="background-color:#f4cccc; font-weight:bold;" | 1.6
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
Aug 2011</translate>
| style="background-color:#f4cccc;" | <translate>
Migration to 3.x</translate>
| style="background-color:#f4cccc;" | <translate>
Plan to migrate to {{CurrentSTSVer|maintenance}} now [[Joomla 1.6 version history]]</translate>
| style="background-color:#f4cccc;" | 1.6.6
|-
| style="background-color:#f4cccc; font-weight:bold;" | 1.5
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
Sept 2012</translate>
| style="background-color:#f4cccc;" | <translate>
Migration to 3.x</translate>
| style="background-color:#f4cccc;" | <translate>
Plan to migrate to {{CurrentSTSVer|maintenance}} now [[Joomla 1.5 version history]]</translate>
| style="background-color:#f4cccc;" | <translate>
EOL at 1.5.26</translate>
|-
| style="background-color:#f4cccc; font-weight:bold;" | 1.0
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | [[File:X-mark.png|center]]
| style="background-color:#f4cccc;" | <translate>
22 July 2009</translate>
| style="background-color:#f4cccc;" | <translate>
Migration to 3.x</translate>
| style="background-color:#f4cccc;" | <translate>
Plan to migrate to {{CurrentSTSVer|maintenance}} now</translate>
| style="background-color:#f4cccc;" | <translate>
EOL at 1.0.15</translate>
|}
<noinclude>
<references />
<translate>
[[Category:Joomla! versions]]</translate>
</noinclude>

J3.x:Access Control List Tutorial

2023-08-18T15:11:32Z

Topazgb: Undo revision 1010302 by Chuyentt (talk)

<noinclude><languages /></noinclude>
{{Joomla version|version=3.x|comment=<translate>
series </translate>}}
{{-}}
<translate>
==Separate ACL for Viewing and Doing== 
</translate>

<translate>
The Joomla ACL system can be thought of as being divided into two completely separate systems. One system controls what things on the site Users can ''view''. The other controls what things Users can ''do'' (what actions a User can take). The ACL for each is set up differently.</translate>

<translate>
===Controlling What Users Can See=== 
</translate>

<translate>
The setup for controlling what Users can see is done as follows:
* Create a set of Access Levels according to the Categories and/or the combination of categories you wish only logged in Users to see. N.B. Do not assign any User groups to the new Access Levels at this point.</translate>

<translate>
* Create a User Group, with 'Registered' as parent, for each Access Level. Using the same names for the User Groups as the Access Levels will prevent confusion later.</translate>

<translate>
* Edit your new Access Levels and assign the correct (new) User Group to each one. You may also wish to assign the Super User Group (and/or the other default User Groups but not 'Guest' User Group) to all your new Access Levels</translate>

<translate>
* Assign each item to be viewed to one Access Level. Items include content items (articles, contacts, and so on), menu items, and modules.</translate>

<translate>
Any time a User is about to view an item on a Joomla page, the program checks whether the User has access to the item, as follows:</translate>
<translate>
# Creates a list of all the Access Levels that the User has access to, based on all Groups that the User belongs to. Also, if a group has a parent group, access levels for the parent group are also included in the list.</translate>
<translate>
# Checks whether the Access Level for the item (article, module, menu item, and so on) is on that list. If yes, then the item is displayed to the User. If no, then the item is not displayed.</translate>

<translate>
Note that Access Levels are set separately for each Group and are not inherited from a group's parent group.</translate>

<translate>
===Controlling What Users Can Do=== 
</translate>

<translate>
The system for setting up what Users in a User Group can do -- what actions they can take on a given item -- is set up with the Permissions tab of Global Configuration and the Permissions tab of the Options screen of each component. Permissions can also be set up at the Category level for core components and at the Article level for articles.</translate>

<translate>
* If you wish logged in Users to Create, Delete, Edit State or Edit Own for specific Categories then:</translate>
<translate>
** Create a User Group with the Parent as one of your User Groups that has Access to the Category(or Categories) you wish this new User Group to modify.</translate>
<translate>
**Assign your new User Group to the appropriate Access Level(s). Then change the required permissions for your new User Group either Globally or per Category/Article.</translate>
<translate>
***When creating a User Group it is good practice to select a parent group that has less permissions than needed for the new group. This is because it is easier to elevate permissions per Component/Category/Article that the extra permissions are needed for than it is to remove permissions from the other Components/Categories/Articles.</translate>
<translate>
****''(Example: You have ten Categories but you want Create permissions for just one. If you set Global permissions to Allow Create for that group you would need to remove Create permission for all those categories. And you would need to remove the Create permission for that group with any new Category that you add at a later date.)''</translate>
<translate>
**Only create a User Group with one of the default User Groups as parent if none of them have the exact permissions that you need and you wish all Categories</translate>

<translate>
Note that this set up is independent of the setup for viewing but a User Group needs to be assigned to the appropriate Access Level(s) in order for the User in that Group to use those Permissions.</translate>

<translate>
When a User wants to initiate a specific action against a component item (for example, edit an article), the system (after checking the Group the User is in has access) checks the permission for this combination of User, item, and action. If it is allowed, then the User can proceed. Otherwise, the action is not allowed.</translate>

<translate>
The remainder of this tutorial discusses how we control what Users can do -- what action permissions they have.</translate>

<translate>
==Actions, Groups, and Inheritance== 
</translate>

<translate>
The other side of ACL is granting permissions to Users to take actions on objects.</translate>

{| class="wikitable"
!style="width:20%;"|
!<translate>
3.x series</translate>
|-
!<translate>
Groups and Actions</translate>
|<translate>
Actions allowed for each group are defined by site administrator.</translate>
|-
!<translate>
Permission Scope</translate>
|<translate>
Permissions can be set at multiple levels in hierarchy: Site, Component, Category, Object.</translate>
|-
!<translate>
Permission Inheritance</translate>
|<translate>
Permissions can be inherited from parent Groups and parent Categories</translate>
|}

<translate>
===How Permissions Work=== 
</translate>

<translate>
There are four possible permissions for actions, as outlined below:</translate>

<translate>
* '''Not set''': Defaults to "deny" but, unlike the Deny permission, this permission can be overridden by setting a child group or a lower level in the permission hierarchy to "Allow." This permission only applies to the Global Configuration permissions.</translate>
<translate>
* '''Inherit''': Inherits the value from a parent Group or from a higher level in the permission hierarchy. This permission applies to all levels except the Global Configuration level.</translate>
<translate>
* '''Deny''': Denies this action for this level and group. '''IMPORTANT''' This also denies this action for all child groups and all lower levels in the permission hierarchy. Putting in Allow for a child group or a lower level will not have any effect. The action will always be denied for any child group member and for any lower level in the permission hierarchy.</translate>
<translate>
* '''Allow''': Allows this action for this level and group and for lower levels and child groups. This does not have any effect if a higher group or level is set to Deny or Allow. If a higher group or level is set to Deny, then this permission will always be denied. If a higher group or level is set to Allow, then this permission will already be allowed.</translate>
{{anchor|hierarchylevels}}
<translate>
===Permission Hierarchy Levels=== 
</translate>

<translate>
Action permissions in version 2.5+ can be defined at up to four levels, as follows:</translate>
<translate>
# '''Global Configuration''': determines the default permissions for each action and group.</translate>
<translate>
# {{rarr|Component Options,Permissions}}: can override the default permissions for this component (for example, Articles, Menus, Users, Banners, and so on).</translate>
<translate>
# '''Category''': can override the default permissions for objects in one or more categories. Applies to all components with categories, including Articles, Banners, Contacts, News Feeds, and Web Links.</translate>
<translate>
# '''Article''': Can override the permissions for a specific article. This level only applies to articles. Other components only allow the first three levels.</translate>

<translate>
====Global Configuration==== 


This is accessed from {{rarr|System,Global Configuration,Permissions}}. This screen allows you set the top-level permission for each group for each action, as shown in the screenshot below.</translate>

[[Image:Screenshot_global_acl_J3_tutorial-<translate>
en</translate>.png]]

<translate>
The options for each value are Inherited, Allowed, or Denied. The Calculated Setting column shows you the setting in effect. It is either Not Allowed (the default), Allowed, or Denied.</translate>

<translate>
You work on one Group at a time by opening the slider for that group. You change the permissions in the Select New Settings drop-down list boxes.</translate>

<translate>
Note that the Calculated Setting column is not updated until you press the Save button in the toolbar. To check that the settings are what you want, press the Save button and check the Calculated Settings column.</translate>

<translate>
====Component Options and Permissions==== 
</translate>
<translate>
This is accessed for each component by clicking the Options icon in the toolbar. This screen is similar to the Global Configuration screen above. For example, clicking the Options toolbar icon in the Menu Manager shows the Menus Configuration below.</translate>
[[Image:Screenshot_menu_acl_J3_tutorial-<translate>
en</translate>.jpg]]

<translate>
Access to Options is only available to members of groups who have permission for the Configure action in for each component. In the example above, the Administrator group has Allowed permission for the Configure option, so members of this group can access this screen.</translate>

<translate>
====Category==== 


Category permissions are accessed in the Category Manager: Edit Category screen, in a tab at the top of the screen. This screen has five permissions, as shown below.</translate>

[[Image:Screenshot_category_acl_j3_tutorial-<translate>
en</translate>.png]]

<translate>
In these screens, you work on the permissions for one User Group at a time. In the example above, we are editing the permissions for the Administrator group.</translate>

<translate>
Note that the Configure and Access Component actions do not apply at the category level, so those actions are not included.</translate>

<translate>
Note also that Categories can be arranged in a hierarchy. If so, then action permissions in a parent category are inherited automatically by a child category. For example, if you had a category hierarchy of {{rarr|Animals,Pets,Dogs}}, then the full permission level hierarchy for an article in the Dogs category would be as follows:</translate>
<translate>
* Global Configuration
* {{rarr|Article Manager,Options,Permission}}
* Animals Category
* Pets Category
* Dogs Category
* specific article</translate>

<translate>
====Article==== 
</translate>
<translate>
Permissions for a single article are accessed in the {{rarr|Article Manager,Edit Article}} screen, again in a slider at the bottom of the screen. This screen has three actions:</translate>

[[Image:j3x_acl_tutorial_article_manager_article_permissions-<translate>
en</translate>.png]]

<translate>
Again, you edit each group by clicking on it to open the slider for that group. You can then change the permissions under the Select New Setting column. To see the effect of any changes, press the Save button to update the Calculated Setting column.</translate>

<translate>
Note that the Configure, Access Component, and Create actions do not apply at the article level, so these actions are not included. Permission to create an article is set at one of the higher levels in the hierarchy.</translate>

<translate>
===Access Levels=== 
</translate>

<translate>
Access Levels in 3.x series are simple and flexible. The screen below shows the Special Access Level.</translate>
[[Image:j3x_acl_tutorial_viewing_levels-<translate>
en</translate>.png|center]]
<translate>
Simply check the box for each group you want included in that level. The Special Access Level includes the Manager, Author, and Super Users groups. It also includes child groups of those groups. So, Administrator group is included, since it is a child group of the Manager group. The Editor, Publisher, and Shop Suppliers groups are included, since they are child groups of Author. (Note that we could check all of the child groups if we wanted and it wouldn't hurt anything).</translate>

<translate>
Once Access Levels are created, they are used in the same way as in version 1.5. Each object in the Frontend is assigned an Access Level. If the level is Public, then anyone may access that object. Otherwise, only members of groups assigned to that access level may access that object. Access levels are assigned to Menu Items and to Modules. Each one can only be assigned to one access level.</translate>

<translate>
For example, the screen below shows the Edit Menu Item screen with the list of available access levels.</translate>

[[Image:j3x_acl_tutorial_edit_menu_item_level_dropdown-<translate>
en</translate>.png|center]]

<translate>
==Default ACL Setup== 
</translate>

<translate>
When Joomla! is installed, these are set to their initial default settings. We will discuss these initial settings as a way to understand how the ACL works.</translate>

<translate>
===Default Groups=== 
</translate>

<translate>
Version 3.x allows you to define your own Groups. When you install version 3.x, it includes a set of default groups, shown below are the basic default User groups. (Additional default User groups are installed with sample data.)</translate>

[[Image:Screenshot_usergroupsl_acl_J3_tutorial-<translate>
en</translate>.png|center]]

<translate>
The arrows indicate the child-parent relationships. As discussed above, when you set a permission for a parent group, this permission is automatically inherited by all child groups. The Inherited, and Allowed permissions can be overridden for a child group. The Denied permission cannot be overridden and will always deny an action for all child groups.</translate>

<translate>
===Global Configuration=== 
</translate>

<translate>
Joomla! version 2.5 will install with the same familiar Backend permissions as that of version 1.5. However, with 2.5, you can easily change these to suit the needs of your site.</translate>

<translate>
As discussed earlier, the permissions for each action are inherited from the level above in the permission hierarchy and from a group's parent group. Let's see how this works. The top level for this is the entire site. This is set up in the {{rarr|Site,Global Configuration,Permissions}}, as shown below.</translate>

[[Image:Screenshot_global_acl_J3_tutorial-<translate>
en</translate>.png]]

<translate>
The first thing to notice are the ten Actions: Site Login, Admin Login, Offline Access, Super User, Access Administration Interface, Create, Delete, Edit, Edit State. and Edit Own. These are the actions that a User can perform on an object in Joomla. The specific meaning of each action depends on the context. For the Global Configuration screen, they are defined as follows:</translate>

<translate>
;Site Login : Login to the Frontend of the site


;Admin Login : Login to the Backend of the site</translate>

<translate>
;Offline Access : Login to the Frontend of the site when the website site is offline (when Global Configuration setting "Site Offline" is set to Yes)</translate>

<translate>
; Super User : Grants the User "Super User" status. Users with this permission can do anything on the site. Only Users with this permission can change Global Configuration settings (this screen). These permissions cannot be restricted. It is important to understand that, if a User is a member of a Super User group, any other permissions assigned to this User are irrelevant. The User can do any action on the site. However, Access Levels can still be assigned to control what this group sees on the site. (Obviously, a Super User can change Access Levels if they want to, so Access Levels do not totally restrict what a Super User can see.)</translate>

<translate>
;Access Component: Open the component manager screens (User Manager, Menu Manager, Article Manager, and so on)</translate>

<translate>
;Create : Create new objects (for example, Users, Menu Items, Articles, Web Links, and so on)</translate>

<translate>
;Delete : Delete existing objects</translate>

<translate>
;Edit : Edit existing objects</translate>

<translate>
;Edit State : Change object state (Publish, Unpublish, Archive, and Trash)</translate>

<translate>
;Edit Own : Edit objects that you have created.</translate>

<translate>
Each Group for the site has its own slider which is opened by clicking on the group name. In this case (with the sample data installed), we have the standard 7 groups that we had in version 1.5 plus two additional groups called "Shop Suppliers" and "Customer Group." Notice that our groups are set up with the same permissions as they had in version 1.5. Keep in mind that we can change any of these permissions to make the security work the way we want. Let's go through this to see how it works.</translate>

<translate>
* '''Public''' has everything set to "Not set", as shown below.</translate>{{-}}[[Image:Screenshot_global_acl_public_J3_tutorial-<translate>
en</translate>.png]]
<translate>
**This can be a bit confusing. Basically, "Not Set" is the same as "Inherited." Because Public is our top-level group, and because Global Configuration is the top level of the component hierarchy, there is nothing to inherit from. So "Not Set" is used instead of "Inherit."</translate>
<translate>
**The default in this case is for no permissions. As you would expect, the Public group has no special permissions. Also, it is important to note that, since nothing is set to Denied, all of these permissions may be overridden by child groups or by lower levels in the permission hierarchy.</translate>

<translate>
* '''Guest''' is a 'child' group of the Public group has everything set to 'Inherited'</translate> {{-}}[[Image:Screenshot_global_acl_guest_J3_tutorial-<translate>
en</translate>.png]]
<translate>
** This is the default 'Guest User Group' in the User Manager options and the Group that (non logged in) visitors to your site are placed in.</translate>

<translate>
* '''Manager''' is a "child" group of the Public group. It has Allowed permissions for everything except Access Component and Super User. So a member of this group can do everything in the front and Backend of the site except change Global Permissions and Component Options.</translate> {{-}}[[Image:Screenshot_global_acl_manager_J3_tutorial-<translate>
en</translate>.png]]

<translate>
* '''Administrator''' group members inherit all of the Manager permissions and also have Allowed for Access Component. So members of this group by default can access the Options screens for each component.</translate> {{-}}[[Image:Screenshot_global_acl_administrator_J3_tutorial-<translate>
en</translate>.png]]

<translate>
* '''Registered''' is the same a Public except for the Allow permission for the Site Login action. This means that members of the Registered group can login to the site. Since default permissions are inherited, this means that, unless a child group overrides this permission, all child groups of the Registered group will be able to login as well.</translate> {{-}}[[Image:Screenshot_global_acl_registered_J3_tutorial-<translate>
en</translate>.png]]

<translate>
* '''Author''' is a child of the Registered group and inherits its permissions and also adds Create and Edit Own. Since Author, Editor, and Publisher have no Backend permissions, we will discuss them below, when we discuss Frontend permissions.</translate>{{-}}[[Image:Screenshot_global_acl_author_J3_tutorial-<translate>
en</translate>.png]]

<translate>
* '''Editor''' is a child of the Authors group and adds the Edit permission.</translate> {{-}}[[Image:Screenshot_global_acl_editor_J3_tutorial-<translate>
en</translate>.png]]

<translate>
* '''Publisher''' is a child of Editor and adds the Edit State permission.</translate>{{-}}[[Image:Screenshot_global_acl_publisher_J3_tutorial-<translate>
en</translate>.png]]

<translate>
* '''Shop Suppliers''' is an example group that is installed if you install the sample data. It is a child group of Author.</translate>

<translate>
* '''Customer Group''' is an example group that is installed if you install the sample data. It is a child group of Registered.</translate>

<translate>
* '''Super Users''' group has the Allow permission for the Super User action. Because of this, members of this group have Super User permissions throughout the site. They are the only Users who can access and edit values on the Global Configuration screen. Users with permission for the Super User action have some special characteristics:</translate>
<translate>
:* If a User has Super User permissions, no other permissions for this User matter. The User can perform any action on the site.</translate>
<translate>
:* Only Super Users can create, edit, or delete other Super Users or groups.</translate>

<translate>
There are two important points to understand from this screen. The first is to see how the permissions can be inherited from the parent Group. The second is to see how you can control the default permissions by Group and by Action.</translate>

<translate>
This provides a lot of flexibility. For example, if you wanted Shop Suppliers to be able to have the ability to login to the Backend, you could just change their Admin Login value to "Allowed." If you wanted to not allow members of Administrator group to delete objects or change their state, you would change their permissions in these columns to Inherited (or Denied).</translate>

<translate>
It is also important to understand that the ability to have child groups is completely optional. It allows you to save some time when setting up new groups. However, if you like, you can set up all groups to have Public as the parent and not inherit any permissions from a parent group.</translate>

<translate>
===Component Options and Permissions=== 
</translate>

<translate>
Just looking at the Global Configuration screen above, it would appear that the Administrator group and the Manager group have identical permissions. However, in version 1.5 Administrators can do everything except Global Configuration, whereas Managers are not permitted to add Users or work with menu items. That is also true in the default version 2.5 configuration. Let's see how this is accomplished.</translate>

<translate>
If we navigate to {{rarr|Users,User Manager}} and click the Options button in the toolbar, we see the screen below:</translate>

[[Image:screenshot_acl_tutorial_20110111-09-<translate>
en</translate>.png|center|]]
[[Image:screenshot_acl_tutorial_20110111-10-<translate>
en</translate>.png|center|]]

<translate>
This screen is the same as the Global Configuration Permissions screen, except that these values only affect working with Users. Let's look at how this works.</translate>

<translate>
First, notice that the Administrator group has Allow permission for the Admin action and the Manager group has Deny permission for this action. Remember that the Admin action in the Global Configuration screen gives the group "Super User" permissions. In this screen, the Admin action allows you to edit the Options values. So, the Administrator group can do this but the Manager group cannot.</translate>

<translate>
Next, notice that the Administrator has Inherit for the Manage action and the Manager group has Deny permission. In this screen, the Manage action gives a group access to the User Manager. Since the Administrator has Allow for the Manage action by default, then the Inherit permission here means they inherit the Allow permission for the Manage action. Since the Manager group has Deny permission for the Manage action, members of the Manager group cannot access the User Manager and therefore cannot do any of the other User-related actions.</translate>

<translate>
If you look at the Options for {{rarr|Menus,Menu Manager}}, you will see the same default settings as for the User Manager. Again, the Administrator group can manage and set default permissions for Menu Manager objects whereas the Manager group cannot.</translate>

<translate>
In short, we can see that the different permissions for the Administrator and Manager groups are set using the {{rarr|Options,Permissions}} forms on the User Manager and Menu Manager screens.</translate>

<translate>
It is also important to understand that this same {{rarr|Options,Permissions}} form for setting default permissions is available for all Joomla! objects, including Media Manager, Banners, Contacts, News Feeds, Redirect, Search Statistics, Web Links, Extensions, Modules, Plugins, Templates, and Language. So you now have the option to create User groups with fine-tuned sets of Backend permissions.</translate>

<translate>
===Frontend Permissions=== 
</translate>

<translate>
Default permissions for the Frontend are also set using the Options form. Let's look at {{rarr|Content,Article Manager,Options,Permissions}}. First, let's look at the permissions for Manager, as shown below.</translate>
[[Image:screenshot_acl_tutorial_20110111-11a-<translate>
en</translate>.png|center|frame]]
<translate>
Manager has allowed permission for all actions except Configure. So members of the Manager group can do everything with Articles except open the Options screen.</translate>

<translate>
Now let's look at Administrator, as shown below.</translate>
[[Image:screenshot_acl_tutorial_20110111-12a-<translate>
en</translate>.png|center|frame]]
<translate>
Administrator has Allowed for Configure, so Administrators can edit this Options screen.</translate>

<translate>
Both groups can create, delete, edit, and change the state of articles.</translate>

<translate>
Now, let's look at the groups Publisher, Editor, and Author and see how their permissions are set.</translate>

<translate>
Authors only have Create and Edit Own permissions, as shown below.</translate>
[[Image:screenshot_acl_tutorial_20110112-07-<translate>
en</translate>.png|center|frame]]
<translate>
This means that Authors can create articles and can edit articles they have created. They may not delete articles, change the published state of articles, or edit articles created by others.</translate>

<translate>
Editors have the same permissions as Authors with the addition of permission for the Edit action, as shown below.</translate>
[[Image:screenshot_acl_tutorial_20110112-08-<translate>
en</translate>.png|center|frame]]
<translate>
So Editors can edit articles written by anyone.</translate>

<translate>
Publishers can do everything Editors can do plus they have permission for the Edit State action, as shown below.</translate>
[[Image:screenshot_acl_tutorial_20110112-09-<translate>
en</translate>.png|center|frame]]
<translate>
So Publishers can change the published state of an article. The possible states include Published, Unpublished, Archived, and Trashed.</translate>

<translate>
All of these groups have Inherit permission for Configure and Access Component. Remember that Author is a child of the Registered group, and Registered does not have any default permissions except for Login. Since Registered does not have permission for Configure and Access Component, and since Author's permission for these actions is "Inherited", then Author does not have these permissions either. This same permission is passed from Author to Editor and from Editor to Publisher. So, by default, none of these groups are allowed to work with articles in the Backend.</translate>

<translate>
It is important to remember that these permissions are only default settings for categories and articles and for any child groups that are created. So they can be overridden for child groups, for categories, and for specific articles.</translate>

<translate>
Also, note that there are no Denied permissions for any actions in the default settings. This allows you to add Allowed permissions at any level. Remember, once you have an action set for Denied, this action will be denied at all lower levels in the hierarchy. For example, if you set the Admin Login for Registered to Denied (instead of Allowed), you could not grant Publishers Allowed permissions for this action.</translate>

<translate>
=== Article Manager and Actions Diagram === 
</translate>

<translate>
The diagram below shows how each action in the permissions form relates to the various options on the Article Manager screen.</translate>

[[Image:screenshot_acl_tutorial_20110111-16-<translate>
en</translate>.png|center|]]

<translate>
* '''Configure''' allows you to view and change the Options for the component.</translate>
<translate>
* '''Access Component''' allows you to navigate to the Article Manager. Without this permission, no other actions are possible.</translate>
<translate>
* '''Create''' allows you to add new articles.</translate>
<translate>
* '''Delete''' allows you to delete trashed articles. Note that the Delete icon only shows in the toolbar when you have the "Select State" filter set to "Trash."</translate>
<translate>
* '''Edit''' allows you to edit existing articles.</translate>
<translate>
* '''Edit State''' allows to you Publish, Unpublish, Archive, or Trash articles.</translate>
<translate>
* '''Edit Own''' is the same as Edit except that it only applies to articles written by you.</translate>

<translate>
==Allowing Guest-Only Access to Menu Items and Modules== 
</translate>

<translate>
Version 1.6 introduced the ability to create a View Access Level that is only for guests of the site (meaning a User who is not logged in). The example below shows how you can set up this new feature.
''(N.B. Steps 1 to 3 are not needed for Joomla! 3.x as they exist in the default install.)''</translate>

<translate>
#Create a new User group called Guest. Make it a child of the Public group as shown below.</translate> [[Image:screenshot_acl_tutorial_20110112-01-<translate>
en</translate>.png|center|frame]]
<translate>
# Create a new access level called Guest and grant only the Guest group access to this level, as shown below.</translate>[[Image:screenshot_acl_tutorial_20110112-02-<translate>
en</translate>.png|center|frame]]
<translate>
# Navigate to {{rarr|User Manager,Options,Component}} and change the Guest User Group from the default value of "Public" to "Guest", as shown below.</translate>
[[Image:screenshot_acl_tutorial_20110112-04-<translate>
en</translate>.png|center|frame]]
<translate>
Now, if we assign a menu item, module, or other object to the Guest access level, only non-logged in Users will have access. For example, if we create a new menu item with access level of Guest, as shown below,</translate>
[[Image:screenshot_acl_tutorial_20110112-05-<translate>
en</translate>.png|center|frame]]
<translate>
This menu item will only be visible to non-logged-in visitors to the site.</translate>

<translate>
If required other User groups like Author can be granted access in the Guest access level, this would allow Authors to view articles in the Frontend for editing.</translate>

<translate>
'''N.B. Login/logout in Frontend (''for changing data in session'') to see the change.'''</translate>

<translate>
==Using Permission and Group Levels Together== 
</translate>

<translate>
As discussed above, it is possible to define groups in a hierarchy, where each child group inherits action permissions (for example, the create permission) from its parent group. Action permissions are also be inherited from the permission level above. For example, a permission in the Article Manager is inherited from the same permission in the Global Configuration, and a permission in a child Category is inherited from the parent Category permission.</translate>

<translate>
This dual inheritance can be confusing, but it can also be useful. Let's consider an example as follows. We have a school with a group hierarchy of {{rarr|Teachers,History Teachers,Assistant History Teachers}}. We also have a category hierarchy of {{rarr|Assignments,History Assignments}}. We want History Teachers and Assistant History Teachers to have the following permissions:</translate>

<translate>
* both groups can create new articles only in the History Assignments category.</translate>

<translate>
* only History Teachers (not Assistant History Teachers) can Publish or otherwise have Edit State permission.</translate>

<translate>
This ACL scheme is easy to implement. The diagram below shows how this would be set up for the Create Action.</translate>

[[Image:Acl example diagram1 20091018-<translate>
en</translate>.png|center|]]

<translate>
In the diagram, the Permission Hierarchy is shown down the left side and the Group hierarchy is shown across the top. Permissions are inherited down and to the right, as shown by the arrows. To implement the desired permissions, we leave the Global Configuration blank (Not Set) for all three groups. Similarly, in the Article Manager and Assignments Category, we leave the Create permission to Inherit for all the groups. As shown in the diagram, this means that these groups do not have Create permission for articles in general or for articles in the Assignments group.</translate>

<translate>
To sum up so far, we have not set any special permissions to get to this point. Now, in the History Assignments category permissions screen, we set the Create permission to Allow for the History Teachers group. This setting overrides the Soft (Implicit) Deny that we had by default and gives members of this group permission to create content (articles and child categories) for this category. This Allow setting also is inherited by the Assistant History Teachers group.</translate>

<translate>
Next, we need to grant History Teachers the Edit State permission while denying this permission to Assistant History Teachers. This is done as shown in the diagram below.</translate>

[[Image:Acl example diagram2 20091018-<translate>
en</translate>.png|center|]]

<translate>
This configuration is the same as the one above except that this time we set the Edit State permission in the History Assignments category to Deny for the Assistant History Teachers group. This means that Assistant History Teachers will not be able to Publish or Unpublish articles in this category.</translate>

<translate>
Note that this was accomplished by setting just two permissions in the History Assignments category: Allow for the History Teachers group and Deny for the Assistant History Teachers group.</translate>

<translate>
==ACL Action Permission Examples== 


Here are some examples of how you might set up the ACL for some specific situations.</translate>

<translate>
===Backend Article Administrator=== 
</translate>

<translate>
'''Problem'''</translate>

<translate>
We want to create a group called "Article Administrator" with Backend permissions only for articles and not for any other Backend menu options. Members of this group should be able to use all of the features of the article manager, including setting article permissions.</translate>

<translate>
'''Solution'''</translate>

<translate>
# Create a new group called Article Administrator and make its parent group Public, as shown below.</translate>[[Image:screenshot_acl_tutorial_20110112-10-<translate>
en</translate>.png|center|frame]] <translate>
Because its parent group is Public, it won't have any permissions by default.</translate>
<translate>
# In {{rarr|Users,Access Levels}}, edit the Special Access level to add the new group. That way they can get access to the Backend menu items and modules (This assumes that the modules for the admin menu and quick icons have the Special Access level assigned to them, which is the default.)</translate> [[Image:screenshot_acl_tutorial_20110112-11-<translate>
en</translate>.png|center|frame]] <translate>
By default, the Backend menu items and modules are set to Special access, so if you forget to add the new group to the Special access level, you won't see any modules or menu items when you log in as a User of the new group.</translate>
<translate>
# In {{rarr|Site,Global Configuration,Permissions}}, click on the Article Administrator group and change the permissions to Allowed for the following actions: Admin Login, Create, Delete, Edit, Edit State, and Edit Own. The screen below shows what will show before you press Save.</translate> [[Image:screenshot_acl_tutorial_20110112-12-<translate>
en</translate>.png|center|frame]]<translate>
After you save, the Calculated Permissions should show as shown below.</translate>[[Image:screenshot_acl_tutorial_20110112-13-<translate>
en</translate>.png|center|frame]]<translate>
Note that the permission for the Access Component is Inherited, which translates to Not Allowed. This is important. This means that this group will only be able to access components if we give the group "Allowed" permission for Access Component. So we only have to change the one component we want to give them access to and don't have to change any settings for the components where we don't want them to have access. If we had a case where we wanted to give a group access to everything except for one component, we could set the default to Allowed and then set the one component to Denied. Also note that we did not give the group Site Login permission, so Users in this group will not be able to log into the Frontend. (If we wanted to allow that, we would just change the permission to Allowed for Site Login.)</translate>
<translate>
# In {{rarr|Article Manager,Options,Permissions}}, change permissions to Allowed for this group for the Access Component action, as shown below.</translate>[[Image:screenshot_acl_tutorial_20110112-14-<translate>
en</translate>.png|center|frame]]<translate>
All of the other desired permissions are inherited.</translate>

<translate>
That's all you need to do. Members of this group can login to the Backend and do everything in Article Manager but can't do anything else in the Backend. For example, the screen below shows what a User in the Article Manager will see when they login to the Backend.</translate>[[Image:screenshot_acl_tutorial_20110112-15-<translate>
en</translate>.png|center|frame]]

<translate>
==ACL View Access Levels Examples== 
</translate>

<translate>
A basic concept of using Access Levels is that all items with the same Access will be viewable by the same group of Users. In other words, if two items have the same Access, you can't have one viewable by one User and not viewable by another User. On the other hand, it is easy to have one Group view any number of items with different Access levels.</translate>

<translate>
Similarly, each Group has exactly the same combination of Access levels, but one User can be a member of more than one group. Depending on the situation, you may want to have Users only in one Group or you may need to have a User in more than one Group.</translate>

<translate>
This means that we may need to group our items so that items so that all items in a group have the same level of sensitivity. Here are some examples.</translate>

<translate>
===Hierarchical Example=== 
</translate>
<translate>
In this example, Access levels are hierarchical, for example, like government security clearance codes. Say for example we have the following sets of classified documents: Classified, Secret, and Top Secret. Users have corresponding clearance codes. Users with Classified clearance can only see Classified documents and cannot see Secret or Top Secret. Users with Secret clearance can see Classified and Secret documents but not Top Secret. Users with Top Secret can see all documents.</translate>

<translate>
In this case, you would create three Access levels: Classified, Secret, and Top Secret and the same three Groups. Users would only be members of one group, as follows:</translate>

{| style="border-spacing:0;"
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
User</translate>
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Group</translate>
| style="border:0.0007in solid #000000;padding:0.0382in;"| <translate>
Access Levels</translate>

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| C1, C2, C3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Classified</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| <translate>
Classified</translate>

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| S1, S2, S3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Secret</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| <translate>
Classified, Secret</translate>

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| TS1, TS2, TS3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Top Secret</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| <translate>
Classified, Secret, Top Secret</translate>

|}

<translate>
In this case, all Users are in exactly one group, but some groups have access to more than one Access Level of items. In other words, we have a one-to-one relationship between Users and groups, but a one-to-many relationship between Groups and Access Levels.</translate>

<translate>
===Team Security Example=== 
</translate>

<translate>
Another possible use case is a set of non-hierarchical teams. Let's say we have three teams, T1, T2, and T3. Some Users are only on one team, but others might be on two or more teams. In this case, we could set up our Access Levels and Groups by team. Documents for each team have the access level for that team, and the Group for the team has only the one access level. When a User is on more than one team, they get added to the group for each team, as follows:</translate>

{| style="border-spacing:0;"
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
User</translate>
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Description</translate>
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Group</translate>
| style="border:0.0007in solid #000000;padding:0.0382in;"| <translate>
Access Levels</translate>

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| U1
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Team 1 member</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| T1
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| T1

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| U2
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Team 2 member</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| T2
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| T2

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| U3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Team 3 member</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| T3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| T3

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| U1-2
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Member of teams 1 and 2</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| T1, T2
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| T1, T2

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| U1-3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Member of teams 1 and 3</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| T1, T3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| T1, T3

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| U1-2-3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Member of teams 1,2, and 3</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| T1,T2, T3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| T1, T2, T3

|}

<translate>
===Hybrid Example=== 
</translate>

<translate>
In a real-world situation, you might have a combination of these two arrangements. Say for example we have Managers and Staff. Staff can only see Staff documents and Managers can see Manager and Staff documents. Both types of Users can be assigned to teams as well, in which case they can see all of the documents for that team. In addition, say that Managers can access some, but not all, team documents. Staff can only access team documents if they are members of that team.</translate>

<translate>
In this example, we could set up the following Access Levels:</translate>

{| style="border-spacing:0;"
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Access Level</translate>
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Description</translate>
| style="border:0.0007in solid #000000;padding:0.0382in;"| <translate>
Groups</translate>

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Manager</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Non-team manager documents</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| <translate>
Manager</translate>

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Staff</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Non-team staff documents</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| <translate>
Manager, Staff</translate>

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Team1</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Sensitive Team1 documents (no access outside team)</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| <translate>
Team1</translate>

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Team1-Manager</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Team1 documents that can be accessed by all managers</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| <translate>
Team1, Manager</translate>

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Team2</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Sensitive Team2 documents (no access outside team)</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| <translate>
Team2</translate>

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Team2-Manager</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Team2 documents that can be accessed by all managers</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| <translate>
Team2, Manager</translate>

|}

<translate>
Then, Users could be assigned to groups as follows:</translate>

{| style="border-spacing:0;"
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
User Type</translate>
| style="border:0.0007in solid #000000;padding:0.0382in;"| <translate>
Group</translate>

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Manager on no teams</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| <translate>
Manager</translate>

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Staff on no teams
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Staff

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Manager on team 1</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| <translate>
Manager, Team1</translate>

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Staff on team 1</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| <translate>
Staff, Team1</translate>

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Manager on teams 1 and 2</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| <translate>
Manager, Team1, Team2</translate>

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| <translate>
Staff on teams 1 and 2</translate>
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| <translate>
Staff, Team1, Team2</translate>
|}

<noinclude>
<translate>

[[Category:Joomla! 1.6]]
[[Category:Joomla! 2.5]]
[[Category:Joomla! 3.x]]
[[Category:Tutorials]]
[[Category:Access Control]]
[[Category:Access Management]]
</translate>
</noinclude>

Installing Joomla on Debian Linux

2022-12-08T12:04:04Z

Topazgb: /* Preface */ added 4.x

{{needs|technical review|Needs updating to latest Joomla, PHP, MySQL Versions}}

== Preface ==
This document guides you through the manual installation of Joomla! on ''Debian GNU Linux'' or one of its derivatives such as ''Ubuntu'', ''Knoppix'' or ''GRML''. Note that this guide applies to Joomla! {{JVer|2.5}} {{JVer|3.5}} {{JVer|3.6}} {{JVer|4.x}}. It has been successfully tested on Debian 4.0 [Etch], Debian 5.0 [Lenny], Ubuntu 8.04 LTS [Hardy Heron], Ubuntu 10.10 [maverick] and Ubuntu 11.10 (Oneiric Ocelot). It will work for all Debian-based Linux distributions as well.

Also note that this guide assumes you're installing Joomla! in a single hosting environment, running PHP as module. If you want to run multiple websites as a web hosting service provider, for security reasons you should consider setting up an suPHP (php5-cgi, libapache2-mod-suphp) environment, where every virtual Apache host runs under its own UID.

== Installing Joomla! ==
=== Prerequisites ===
You will need to install Apache2, ''mysql-server-5.0'', ''mysql-client-5.0'' and ''php5'' in order to have a web server for Joomla!.

=== Which Stack Should I Choose? ===
* [[Installing_Joomla_on_Debian_Linux#XAMPP|XAMPP]] automatically configures ownership.
* [[Installing_Joomla_on_Debian_Linux#LaMp|LaMp]] requires use of the ''chown'' command.
* [[Installing_Joomla_on_Debian_Linux#BitNami_Joomla.21_stack|BitNami Joomla! Stack]] is free, self-contained and automatically configures the LAMP stack and Joomla!

== XAMPP ==
Download [https://sourceforge.net/projects/xampp/files/XAMPP%20Linux/ XAMPP] for Linux to your your Home folder.

=== Install XAMPP ===
Open Terminal and enter:

<syntaxhighlight lang="bash">
sudo tar xvfz xampp-linux-1.8.3.tar.gz -C /opt
</syntaxhighlight>

(Replace ''xampp-linux-1.8.3.tar.gz'' with the version of XAMPP you downloaded).

This installs Apache2, MySQL and PHP as well as an FTP server.

<syntaxhighlight lang="bash">
sudo /opt/lampp/lampp start
</syntaxhighlight>

and
<syntaxhighlight lang="bash">
sudo /opt/lampp/lampp stop
</syntaxhighlight>

...starts/stops all the services.

=== Test Your XAMPP Localhost Server ===
Open your Browser and point it to
http://localhost
The ''index.php'' will redirect to
http://localhost/xampp

There you will find instructions on how to change default usernames and passwords. On a PC that does not serve files to the Internet or LAN, changing the defaults is a personal choice.

=== Multiple Versions of XAMPP ===
It can be useful to have access to several versions of XAMPP on your PC. (To have available different versions of PHP for testing.) XAMPP doesn't make this easy but it is possible - see [https://stackoverflow.com/questions/47498835/installing-two-versions-of-php-with-xampp-on-ubuntu-system "how to" article]. (For Linux only.)

=== Get Joomla ===
Download the latest Joomla installation zip [https://downloads.joomla.org/us/]

Unzip to your hard drive

Connect to localhost with XAMPP's FTP client
Default
nobody
lampp

Use FTP to create a folder for your Joomla on the localhost server

FTP the unpacked Joomla installation files to the newly-created Joomla folder.

'''Important'''
* The XAMPP installation sets the correct Ownership of the files and permissions.
* Using the ''chown'' command will cause ownership problems with XAMPP.
* Using Nautilus to manipulate folders/files on localhost will cause ownership problems with XAMPP.

=== Configure Joomla ===
In your Browser type:
http://localhost/yournewjoomlafolder

In the first Joomla installation screen if error reporting is shown as on then:

In your Terminal type
<syntaxhighlight lang="bash">
sudo gedit /opt/lampp/etc/php.ini
</syntaxhighlight>

In the ''php.ini'' file, locate
<syntaxhighlight lang="ini">
error_reporting =
</syntaxhighlight>
And change the value to
<syntaxhighlight lang="ini">
error_reporting = E_ALL & ~E_NOTICE & ~E_DEPRECATED
</syntaxhighlight>

Also locate
<syntaxhighlight lang="ini">
display_errors = On
</syntaxhighlight>
And change the value to
<syntaxhighlight lang="ini">
display_errors = Off
</syntaxhighlight>

Stop then restart XAMPP for the new settings to take effect.

FTP layer is '''not''' needed

'''Database info'''

'''Host''': ''localhost''

'''Database name''': ''test''
:''(XAMPP will automatically create a database of the name you specify).''

'''Default Database user''': ''root''
:There is no Password for '''Database user''': ''root''.

Administrator password is your choice.

Installing Sample Data is recommended for the novice user.

After installation delete the installation directory and point your Browser to:
http://localhost/yournewjoomlafolder
or
http://localhost/yournewjoomlafolder/administrator

=== Create a Link in the Ubuntu Menu ===
'''To create a GUI for XAMPP connected to your Ubuntu menu'''

Open up the Terminal and type
<syntaxhighlight lang="bash">
sudo gedit /usr/share/applications/xampp-control-panel.desktop
</syntaxhighlight>

Then copy the following into the gedit and save.

<syntaxhighlight lang="ini">
[Desktop Entry]
Encoding=UTF-8
Name=XAMPP Control Panel
Comment=Start and Stop XAMPP
Exec=gksudo "python /opt/lampp/share/xampp-control-panel/xampp-control-panel.py"
Icon=/usr/share/icons/Tango/scalable/devices/network-wired.svg
Terminal=false
Type=Application
Categories=GNOME;Application;Network;
StartupNotify=true
</syntaxhighlight>

'''N.B.''' Ubuntu 11.10 needs ''python-glade2'' installed in order to run the GUI. ''python-glade2'' can be found in the Ubuntu Software Center.

== LaMp ==
You will find instructions on [https://wiki.debian.org/LaMp wiki.debian.org]. Make sure that you have installed ''bzip2'' for extracting the downloaded Joomla! package.

You can check this by the following command:
<syntaxhighlight lang="bash">
$ dpkg -l | grep bzip2
</syntaxhighlight>

Note that the dollar sign '$' shell prompt is indicating you're a ''regular user''. We will later see a hash mark (#) shell prompt, which indicates that you're the super user ''root'' after issuing an ''su'' or ''sudo''. The first policy for a secure Linux system administration on the command line (but under X also) is to issue commands with the lowest permission as possible.

If ''bzip2'' is not installed, you won't get an output. Then you can quickly install it via aptitude:
<syntaxhighlight lang="bash">
$ su -c "aptitude install bzip2"
</syntaxhighlight>

Here we see the first command executed with root permissions, because a regular user is not allowed to install new software. The '-c' option passes the following command to ''su'' and hereafter it terminates instead of switching to a root shell.

=== Configure PHP5 ===
In the pre -install check (you get to that when the install is complete and are setting up Joomla at the web page), Output Buffering was On and it's recommended that it should be Off. To do so:
edit /etc/php5/apache2/php.ini , comment out this line: output_buffering = 4096 , by putting a ';' in front. it'll look like this when done:
;output_buffering = 4096

There were also warnings on the install screen regarding ''suhosin''. To make the suggested changes, edit this file:
/etc/php5/conf.d/suhosin.ini
I set these:
<pre>
suhosin.post.max_array_index_length = 256
suhosin.post.max_totalname_length = 8192
suhosin.post.max_vars = 2048
suhosin.request.max_array_index_length = 256
suhosin.request.max_totalname_length = 8192
suhosin.request.max_vars = 2048
</pre>

=== Configure MySQL ===
It is time to create a database for Joomla! You can do this by the following commands:
mysqladmin -u root -p create joomla

Replace ''joomla'' with the name of choice for Joomla!'s database.

Now create a MySQL user different from root for Joomla!'s database. First enter into MySQL system with:
mysql -u root -p
Then at the ''mysql>'' prompt, enter the following. Make sure you replace ''joomla'' with the name of Joomla!'s database from above. Replace ''yourusername'' with the user name you choose for the MySQL user accessing Joomla!'s database, and replace ''yourpassword'' with your password of choice for the MySQL user.
<syntaxhighlight lang="bash">
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES, \
LOCK TABLES ON joomla.* TO 'yourusername'@'localhost' IDENTIFIED BY 'yourpassword';
</syntaxhighlight>
Activate the settings and quit : [ there will be a mysql> prompt:
FLUSH PRIVILEGES;
\q

After disconnecting from the database server, you should remove the login information of your just new created MySQL user by editing MySQL's history file.
vi ~/.mysql_history

You can use any editor of your choice such as ''nano'', ''vi'' or ''emacs'' that is installed on your system.

=== Get Joomla! Source ===
Now it is time to download the Joomla! sources. Currently you will find download links on the [https://downloads.joomla.org/us/ Joomla Downloads] page. For version 1.5.11, you may do the following from command line, assuming your current working directory is your home folder ''/home/user'':
<syntaxhighlight lang="bash">
$ wget http://joomlacode.org/gf/download/frsrelease/10209/40306/Joomla_1.5.11-Stable-Full_Package.tar.bz2
$ cd /var/www
$ su
# mkdir -m 0755 joomla
# cd joomla
# tar -xvjf /home/user/Joomla_1.5.11-Stable-Full_Package.tar.bz2
</syntaxhighlight>

for 1.7 use this wget line:
wget http://joomlacode.org/gf/download/frsrelease/15278/66553/Joomla_1.7.0-Stable-Full_Package.tar.bz2
Check http://joomlacode.org/gf/project/joomla/frs/ for an updated package.

Here is the first time we see this hash mark (#) shell prompt. We call ''su'' without any options, because we want to issue root commands more than only one time. Calling ''su'' that way will prompt us for the super user's password and then change the actual shell environment, respectively $UID and $EUID.

=== Set Ownership and Permissions ===
If you want to allow writing in the entire Joomla folder, simply do:

<syntaxhighlight lang="bash">
chown -R www-data:www-data /var/www/joomla
</syntaxhighlight>

If you want a more restrictive approach, do this instead:
<pre>
chown -R root:root /var/www/joomla
cd /var/www/joomla
PLACES='
administrator/backups
administrator/components
administrator/modules
administrator/templates
cache
components
images
images/banners
images/stories
language
mambots
mambots/content
mambots/editors
mambots/editors-xtd
mambots/search
media
modules
templates
'
for i in $PLACES; do chown -R www-data:www-data $i; done
</pre>

Now set file and directory permissions:
<syntaxhighlight lang="bash">
find /var/www/joomla -type f -exec chmod 0644 {} \;
find /var/www/joomla -type d -exec chmod 0755 {} \;
</syntaxhighlight>

=== Configure Joomla! ===
Open your web browser, and point it to http://localhost/joomla. Replace ''localhost'' with your servers IP or domain name if it you are installing on a remote system.

You will be guided through the final steps of setting up Joomla!, have your MySQL user, password and database name available.

When you reach the final screen with congratulations on installing Joomla!, remove the installation directory. From root terminal:
<syntaxhighlight lang="bash">
# rm -rf /var/www/joomla/installation/
# exit
$
</syntaxhighlight>

And that's it! Now you can log into the Administrator interface of your fresh installed Joomla!.

== BitNami Joomla! Stack ==

=== What is BitNami Joomla! Stack? ===
BitNami Joomla! Stack is an all-in-one installer that makes it easy to install Joomla on your computer. It is free, easy to use and self-contained. That means it bundles and automatically configures every piece of software (dependency) necessary to run Joomla for development or production purposes, including Apache, MySQL and PHP.
You can [https://bitnami.com/stack/joomla download the latest version of BitNami Joomla! stack] for Windows, Linux and OS X.

=== Installing Joomla! Stack ===
Regardless of which operating system you are running (Windows/Linux/Mac), the install process is the same.

Find the installer you just downloaded. The filename will be similar to ''bitnami-joomla-VERSION-linux-installer.run''. Double click on the icon to launch the installer.

Note: If you are using Linux you will have to give executable permissions to the file first, using this command:
chmod +x /path/to/bitnami-joomla-VERSION-linux-installer.run

[[File:Joomla_welcome.png]]

Click ''Forward''.

[[File:Joomla_components.png]]

Select the components you want to install. If you are not sure, leave the default components checked. Click ''Forward'' when you are done.

[[File:Joomla_directory.png]]

Now it will ask where you want to install the program. Provide the location where you want to install the BitNami Joomla! stack and click ''Forward'' when you are done.

[[File:Joomla_userdata.png]]

The user and password you provide here will be used to create the Administrator account in Joomla! Click ''Forward'' when done.

[[File:Joomla_sitename.png]]

Type in the name you want to use for your Joomla site, and click ''Forward''.

[[File:JoomlaReadytoinstall.png]]

The installer is now ready to begin the installation process. Click ''Forward''.

[[File:JoomlaCopyingfiles.png]]

Wait a minute while the installer copies the files and configures your Joomla! installation.

[[File:Joomlafinalscreen.png]]

Joomla! is now set up and ready to be used. Click ''Finish'' to launch the application.

[[File:Joomlaapplicationscreen.png]]

You can now log in using the username and password you provided during the installation.
<noinclude>[[Category:Installation]][[Category:Server setup local]][[Category:Server configurations]]<noinclude>

Pre-Update Check

2022-09-09T08:06:37Z

Topazgb: Changed to UK English gray to grey

<noinclude><languages /></noinclude>
<translate> New to Joomla! 3.10.x is the Pre-Update Check. This view of the Joomla Update component shows technical specifications of the server the site is on and core and third-party extensions that use the Update Server in a list form.</translate>

<translate>

To navigate to the Pre-Update Check page:
*Select {{rarr|Administrator,Components,Joomla Update,Live Update tab}}.
*If you don´t see the Pre-Update Check page, verify that the site is on the Joomla Next Update Channel. {{rarr|Administrator,Components,Joomla Update,Options,Update Channel}}. Select ''Joomla Next'', then ''Save & Close''.
*Verify that the Pre-Update Check tab is selected.
</translate>

<translate>
== Technical Specifications == </translate>
<translate>

The top portion of the Pre-Update Check shows whether your current server environment is compatible with the current target version Joomla for both the required PHP and database settings. The data on the [https://downloads.joomla.org/technical-requirements Technical Requirements] page show the specs we are checking against.</translate>

[[File:php_and_database_settings-<translate> en</translate>.png|border|800px|<translate> Required PHP and Database Settings portion of the Pre-Update Check Component</translate>]]
[[File:Recommended_php_settings-<translate> en</translate>.png|border|800px|<translate> Recommended PHP Settings portion of the Pre-Update Check Component</translate>]]

<translate>

What's important is to check if anything is red and not compatible with Joomla 4.x. If it isn't, you'll need to talk to your host or change hosts before migrating to Joomla 4.x. Migration is a great time to change hosts. See the [[S:MyLanguage/Why Migrate|Migration Funnel]] for more information on planning and step-by-step instructions.</translate>

<translate>
== Extensions Pre-Update Check == </translate>
<translate>

The extension portion of the Pre-Update Check component polls third-party extensions.</translate>

<translate>

The list is broken into sections based on the ''targetplatform'' tag, the extensions you are or are not using. For developers, see [[S:MyLanguage/Deploying an Update Server|Deploying an Update Server]] for more information about these tags and how to deploy an Update Server. For more information about the Joomla Update System, see the [https://extensions.joomla.org/support/knowledgebase/submission-requirements/joomla-update-system-requirement/ Joomla! Update System Requirement] and [https://docs.joomla.org/Help39:Extensions_Extension_Manager_Update Extensions Extension Manager Update] pages.</translate>

<translate>

By clicking the '''More Detail''' link to the right in each colour heading, you can see additional information about the extensions installed on your site.</translate>

[[File:pre_upgrade_checker_error-<translate> en</translate>.png|border|800px|<translate> Update Information Unavailable</translate>]]

<translate>

The extensions listed here do not yet support the Joomla Update system or at least do not have an ''targetplatform'' tag that indicates support for the selected target Joomla Version. (See [[Deploying an Update Server]]) Please contact the developer of the listed extensions to make sure they are compatible with 4.x.</translate>

[[File:pre_upgrade_checker_warning-<translate> en</translate>.png|border|800px|<translate> Update Required</translate>]]

<translate>

The extensions listed here require an update to work correctly on 4.x. Please contact the developer of the listed extensions to make sure whether you have to update the component before or after the upgrade.</translate>

[[File:pre_upgrade_checker_ok-<translate> en</translate>.png|border|800px|<translate> No Update Required</translate>]]

<translate>

The extensions listed here claim to be 4.x compatible and no update is required.</translate>

<translate>
== What is it about that ''Potential Upgrade Issue'' == 


Plugins with the types ''system'', ''user'', ''authentication'', ''actionlog'' and ''twofactorauth'' could be triggered while we are processing the upgrade. When there is a critical issue within that plugins that could result into a broken upgrade and make the site unusable. For that reason any plugin from that type that is not explicitly listed as compatible has to be even more carefully reviewed before you hit the upgrade button. It is '''strongly''' recommended to disable the plugins in question and to check with the original developer.</translate>

[[File:Pre_upgrade_checker_popup-<translate> en</translate>.png|200px|<translate> The popup warning for potential upgrade issue</translate>]]

<translate>
On the ''Live Update'' Tab you will be presented again with the full list of potential breaking extensions.</translate>

[[File:Live_upgrade_tab_errors-<translate> en</translate>.png|border|800px|<translate> The Live Update message on potential breaking extensions</translate>]]

<translate>
It is '''strongly''' recommended to disable all extensions including the plugins listed here before you run the upgrade because the extensions listed here seem not to be compatible with your target version but could break your upgrade.</translate>

<translate>
You know what you are doing? You want to choose to ignore the warnings and run the upgrade anyway. You can do so by checking the checkbox. As that is taking your site at risk of breaking without an easy recovery, this is the last time to remind you to take a backup!</translate>
<translate>
== Questions and Answers == </translate>
<translate>

Let's break this down into some questions and answers.</translate>

<translate>

'''Q: What do the tags mean?'''</translate>

<translate>

A: The green '''No Update Required''' tag means that the extension has been tagged by the developer that the extension as ready for Joomla 4. It ''should'' migrate with the one-click from 3.10.x to 4.x. Verifying with the developer is suggested.</translate>

<translate>

The red '''Update Information Unavailable''' tag means that the extension has not added compatibility information the extension. Check with the developer on the migration path from 3.10.x to 4.x.</translate>

<translate>

The yellow/orange '''Yes (x.x.x)''' tag means that the extension has been tagged by the developer that the extension may need an update in order to be compatible with Joomla 4. Update the extension and see if it turns to a green (Yes). If it doesn't, check with the developer on the migration path from 3.10.x to 4.x.</translate>

<translate>

The grey '''Missing Compatibility Tag''' means that the extension doesn't have a tag '''or''' does not use the Update Server. The developer hasn't said yes or no or needs an update. In some cases, a package may have been installed and the component portion has a tag but the additional plugins or modules are missing tags. As always, you'll need to check with each extension developer to verify the migration path from 3.10.x to 4.x.</translate>

<translate>

'''Q: What about templates?'''</translate>

<translate>

A: Because of the changes in Joomla 4, your template may or may not be compatible with Joomla 4. The core templates like Protostar, Beez3, Beez5 and so on will ''convert'' to the new Cassiopeia template on the one click and the older templates will be completely removed.</translate>

<translate> If you're using a template from a third-party developer that is not compatible with Joomla 4, you'll need to change your default template to Protostar (or Beez3) before you do the one-click migration. If you have older administrator templates or core templates, uninstall all of them except whichever of the core templates you will set as default. This includes Bluestork, Hathor, the other Beez templates. Keep Isis as the administrator template. Keep either your compatible third-party template, Protostar or Beez3 as default. Uninstall the rest.</translate>

<translate>

'''Q: Can I uninstall plg_content_geshi?'''</translate>

<translate>

A: Yes. This is leftover from the 2.5 life cycle and '''must''' be uninstalled.</translate>

<translate>

'''Q: What about all that FOF, fef, etc.?'''</translate>

<translate>

A: Many extensions in the red or yellow/orange headings '''will/may''' make it through the one-click and migrate fine. It is recommended that you go to {{rarr|Extensions,Manage,Manage}} and check all extensions. Typically the ones authored by Joomla will migrate on the one click. Typically the Akeeba extensions will too. Again, check with extension developers to verify the migration path on '''all''' third-party extensions.</translate>

<translate>

'''Q: Does the Extensions Pre-Update Check show all the extensions installed on my site?'''</translate>

<translate>

A: The Pre-Update Check will show all extensions. Only extensions that use the Update Server are given compatibility information. Those extensions that do not use the Update Server will show in the list with the '''Missing Compatibility Tag'''.</translate>

<translate>
== Summary == </translate>
<translate>

From a migration perspective, it is my belief that the Pre-Update Check should be used a guide. You'll want to have a second tab open with {{rarr|Extensions,Manage,Manage}} open in order to uninstall any extensions or check who they're authored by so you can contact third-party extension developers on the migration path they've established to migrate their extensions.</translate>

<noinclude>
<translate>

[[Category:Joomla!_4.x]]
[[Category:Version 4.x FAQ]]
</translate>
</noinclude>

Help4.x talk:Menu Item: Category List

2022-06-23T08:58:19Z

Topazgb: comment

List Layout image looks wrong for J4 ?
--Topazgb 03:58, 23 June 2022 (CDT)

Installing Joomla on Debian Linux

2022-06-06T15:16:31Z

Topazgb: /* Get Joomla */

{{needs|technical review|Needs updating to latest PHP/MySQL Versions}}

== Preface ==

This document guides you through the manual installation of Joomla! on '''Debian GNU Linux''' or one of its derivatives such as '''Ubuntu''', '''Knoppix''' or '''GRML'''. Note that this guide applies to Joomla! {{JVer|2.5}} {{JVer|3.5}} {{JVer|3.6}}. It has been successfully tested on Debian 4.0 [Etch], Debian 5.0 [Lenny], Ubuntu 8.04 LTS [Hardy Heron], Ubuntu 10.10 [maverick] and Ubuntu 11.10 (Oneiric Ocelot). It will work for all '''Debian''' based Linux distribution as well.

Also note that this guide assumes, you're installing Joomla! in a '''single hosting''' environment, running PHP as module. If you want to run multiple web sites as a web hosting service provider, for security reasons you should consider setting up an suPHP (php5-cgi, libapache2-mod-suphp) environment, where every virtual Apache host runs under its own UID.

== Installing Joomla! ==
=== Prerequisites ===
You will need to install apache2, mysql-server-5.0, mysql-client-5.0 and php5 in order to have a web-server for Joomla!.

=== Which stack should I choose? ===

- [[Installing_Joomla_on_Debian_Linux#XAMPP|XAMPP]] automatically configures ownership.

- [[Installing_Joomla_on_Debian_Linux#LaMp|LaMp]] requires use of the CHOWN command.

- [[Installing_Joomla_on_Debian_Linux#BitNami_Joomla.21_stack|BitNami Joomla! Stack]] is free, self-contained and automatically configures the LAMP stack and Joomla!

== XAMPP ==
Download [http://sourceforge.net/projects/xampp/files/XAMPP%20Linux/ XAMPP] for Linux to your your Home folder.

=== Install XAMPP ===
Open Terminal and enter:

<source lang="bash">
sudo tar xvfz xampp-linux-1.8.3.tar.gz -C /opt
</source>

(replace ''xampp-linux-1.8.3.tar.gz'' with the version of XAMPP you downloaded).

This installs ... Apache2, mysql and php5 as well as an ftp server.

<source lang="bash">
sudo /opt/lampp/lampp start
</source>

and
<source lang="bash">
sudo /opt/lampp/lampp stop
</source>

starts/stops all the services

=== Test your XAMPP localhost server ===
Open your Browser and point it to
http://localhost
The index.php will redirect to
http://localhost/xampp

There you will find instructions on how to change default usernames/passwords. On a PC that does not serve files to the Internet or LAN then changing the defaults is personal choice.

=== Multiple Versions of XAMPP ===
It can be useful to have access to several versions of XAMPP on your PC (e.g to have available different versions of PHP for testing). XAMPP doesn't make this easy but it is possble - see [https://stackoverflow.com/questions/47498835/installing-two-versions-of-php-with-xampp-on-ubuntu-system "how to" article here] (for Linux only).

=== Get Joomla ===
Download the latest Joomla installation zip [http://www.joomla.org/download.html]

Unzip to your hard drive

Connect to localhost with Xampp's FTP client
Default
nobody
lampp

Use FTP to create a folder for your Joomla on the localhost server

FTP the unpacked Joomla installation files to the newly created Joomla folder.

'''Important:'''
* The XAMPP installation sets the correct Ownership of the files and permissions.
* Using the '''CHOWN command''' will '''cause Ownership problems with xampp'''.
* '''Using nautilus''' to manipulate folders/files on localhost will '''cause Ownership problems with xampp'''.

=== Configure Joomla ===
In your Browser type
http://localhost/yournewjoomlafolder

In the first Joomla installation screen if error reporting is shown as on then:

In your Terminal type
<source lang="bash">
sudo gedit /opt/lampp/etc/php.ini
</source>

In the <tt>php.ini</tt> file, locate
<source lang="ini">
error_reporting =
</source>
And change the value to
<source lang="ini">
error_reporting = E_ALL & ~E_NOTICE & ~E_DEPRECATED
</source>

Also locate
<source lang="ini">
display_errors = On
</source>
And change the value to
<source lang="ini">
display_errors = Off
</source>

Stop then restart xampp for the new settings to take effect

FTP layer is NOT needed

'''Database info'''

'''Host''': <code>localhost</code>

'''Database name''': <code>test</code>
:<code>(Xampp will automatically create a database of the name you specify).</code>

'''Default Database user''': <code>root</code>
:There is no Password for '''Database user''': <code>root</code>.

Administrator password is your choice.

Installing Sample Data is recommended for the novice user.

After installation delete the installation directory and point your Browser to:
http://localhost/yournewjoomlafolder
or
http://localhost/yournewjoomlafolder/administrator

=== Create a link in the Ubuntu menu ===
'''To create a GUI for XAMPP connected to your Ubuntu menu'''

Open up the Terminal and type
<source lang="bash">
sudo gedit /usr/share/applications/xampp-control-panel.desktop
</source>

Then copy the following into the gedit and save.

<source lang="ini">
[Desktop Entry]
Encoding=UTF-8
Name=XAMPP Control Panel
Comment=Start and Stop XAMPP
Exec=gksudo "python /opt/lampp/share/xampp-control-panel/xampp-control-panel.py"
Icon=/usr/share/icons/Tango/scalable/devices/network-wired.svg
Terminal=false
Type=Application
Categories=GNOME;Application;Network;
StartupNotify=true
</source>

'''N.B.''' Ubuntu 11.10 needs ''python-glade2'' installed in order to run the GUI. ''python-glade2'' can be found in the Ubuntu Software Center.

== LaMp ==
You will find instructions on [http://wiki.debian.org/LaMp wiki.debian.org]. Make sure that you have installed bzip2 for extracting the downloaded Joomla! package.

You can check this by the following command:
<source lang="bash">
$ dpkg -l | grep bzip2
</source>

Note that the dollar sign '$' shell prompt is indicating you're a ''regular user''. We will later see a hash mark (#) shell prompt, which indicates that you're the super user ''root'' after issuing an '''su''' or '''sudo'''. The first policy for a secure linux system administration on the command line (but under X also) is to issue commands with the lowest permission as possible.

If bzip2 is not installed, you won't get an output. Then you can quickly install it via aptitude:
<source lang="bash">
$ su -c "aptitude install bzip2"
</source>

Here we see the first command executed with root permissions, because a regular user is not allowed to install new software. The '-c' option passes the following command to '''su''' and hereafter it terminates instead of switching to a root shell.

=== Configure PHP5 ===
in the pre install check [ you get to that when the install is complete and are setting up Joomla at the web page ], Output Buffering was On and it's recommended that it should be Off .to do so
edit /etc/php5/apache2/php.ini , comment out this line: output_buffering = 4096 , by putting a ';' in front. it'll look like this when done:
;output_buffering = 4096

there were also warnings on the install screen regarding suhosin . to make the suggested changes, edit this file:
/etc/php5/conf.d/suhosin.ini
I set these :
<pre>
suhosin.post.max_array_index_length = 256
suhosin.post.max_totalname_length = 8192
suhosin.post.max_vars = 2048
suhosin.request.max_array_index_length = 256
suhosin.request.max_totalname_length = 8192
suhosin.request.max_vars = 2048
</pre>

=== Configure MySQL ===
It is time to create a database for Joomla! You can do this by the following commmands:
mysqladmin -u root -p create joomla

You may replace ''joomla'' with the name of choice for Joomla!'s database.

Now create a MySQL user different from root for Joomla!'s database. first enter into mysql system with:
mysql -u root -p
Then at the 'mysql>' prompt enter the following. Make sure you replace ''joomla'' with the name of Joomla!'s database from above. Replace ''yourusername'' with the user name you choose for the MySQL user accessing Joomla!'s database, and replace ''yourpassword'' with your password of choice for the MySQL user.
<source lang="bash">
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES, \
LOCK TABLES ON joomla.* TO 'yourusername'@'localhost' IDENTIFIED BY 'yourpassword';
</source>
Activate the settings and quit : [ there will be a mysql> prompt:
FLUSH PRIVILEGES;
\q

After disconnecting from the database server, you should remove the login information of your just new created MySQL user by editing MySQL's history file.
vi ~/.mysql_history

You can use any editor of your choice such as '''nano''', '''vi''' or '''emacs''' that is installed on your system.

=== Get Joomla! source ===
Now it is time to download the Joomla! sources. Currently you will find download links on the [http://joomlacode.org/download.html joomlacode.org] download page. For version 1.5.11, you may do the following from command line, assuming your current working directory is your home folder '''/home/user''':
<source lang="bash">
$ wget http://joomlacode.org/gf/download/frsrelease/10209/40306/Joomla_1.5.11-Stable-Full_Package.tar.bz2
$ cd /var/www
$ su
# mkdir -m 0755 joomla
# cd joomla
# tar -xvjf /home/user/Joomla_1.5.11-Stable-Full_Package.tar.bz2
</source>

for 1.7 use this wget line:
wget http://joomlacode.org/gf/download/frsrelease/15278/66553/Joomla_1.7.0-Stable-Full_Package.tar.bz2
You may want to check http://joomlacode.org/gf/project/joomla/frs/ for an updated package.

Here is the first time we see this hash mark (#) shell prompt. We call '''su''' without any options, because we want to issue root commands more than only one time. Calling '''su''' that way will prompt us for the super user's password and then change the actual shell environment, repectively $UID and $EUID.

=== Set ownerships and permissions ===
If you want to allow writing in the entire joomla folder, simply do

<source lang="bash">
chown -R www-data:www-data /var/www/joomla
</source>

If you want a more restrictive approach, do this instead:
<pre>
chown -R root:root /var/www/joomla
cd /var/www/joomla
PLACES='
administrator/backups
administrator/components
administrator/modules
administrator/templates
cache
components
images
images/banners
images/stories
language
mambots
mambots/content
mambots/editors
mambots/editors-xtd
mambots/search
media
modules
templates
'
for i in $PLACES; do chown -R www-data:www-data $i; done
</pre>

Now set file and directory permissions:
<source lang="bash">
find /var/www/joomla -type f -exec chmod 0644 {} \;
find /var/www/joomla -type d -exec chmod 0755 {} \;
</source>

=== Configure Joomla! ===
Open your favourite web-browser, and point it to the page http://localhost/joomla. Replace ''localhost'' with your servers IP or domain name if it you are installing on a remote system.

You will be guided through the final steps of setting up Joomla!, have your MySQL user, password and database name available.

When you reach the final screen with congratulations on installing Joomla!, you should remove the installation directory. From root terminal:
<source lang="bash">
# rm -rf /var/www/joomla/installation/
# exit
$
</source>

And that's it! Now you can login into the admin interface of your fresh installed Joomla! 1.5.9.

== BitNami Joomla! stack ==

=== What is BitNami Joomla! Stack? ===
BitNami Joomla! Stack is an all-in-one installer that makes it easy to install Joomla on your computer. It is free, easy to use and self-contained. That means it bundles and automatically configures every piece of software (dependency) necessary to run Joomla for development or production purposes, including Apache, MySQL and PHP.
You can download the latest version of BitNami Joomla! stack for Windows, Linux and OS X at http://bitnami.org/stack/joomla.

=== Installing Joomla! Stack ===
Regardless of which operating system you are running (Windows / Linux / Mac), the install process is the same.

Download the latest version of Joomla! Stack from the [http://bitnami.org/stack/joomla BitNami website].

Find the installer you just downloaded (the filename will be similar to bitnami-joomla-VERSION-linux-installer.run. Double click on the icon to launch the installer.

Note: If you are using Linux you will have to give executable permissions to the file first, using this command:
chmod +x /path/to/bitnami-joomla-VERSION-linux-installer.run

[[File:Joomla_welcome.png]]

Click "Forward".

[[File:Joomla_components.png]]

Select the components you want to install. If you are not sure, leave the default components checked. Click "Forward" when you are done.

[[File:Joomla_directory.png]]

Now it will ask where do you want to install the program. Provide the location where you want to install the BitNami Joomla! stack and click "Forward" when you are done.

[[File:Joomla_userdata.png]]

The user and password you provide here will be used to create the admin account in Joomla! Click "Forward" when you are done.

[[File:Joomla_sitename.png]]

Type in the name you want to use for your Joomla site, and click "Forward".

[[File:JoomlaReadytoinstall.png]]

The installer is now ready to begin the installation process. Click "Forward".

[[File:JoomlaCopyingfiles.png]]

Wait a minute while the installer copies the files and configures your Joomla! installation.

[[File:Joomlafinalscreen.png]]

Joomla! is now set up and ready to be used. Click "Finish" to launch the application.

[[File:Joomlaapplicationscreen.png]]

You can now log in using the username and password you provided during the installation.
<noinclude>[[Category:Installation]][[Category:Server setup local]][[Category:Server configurations]]<noinclude>

Installing Joomla on Debian Linux

2022-06-05T22:27:38Z

Topazgb: /* Multiple Versions of XAMPP */

{{needs|technical review|Needs updating to latest PHP/MySQL Versions}}

== Preface ==

This document guides you through the manual installation of Joomla! on '''Debian GNU Linux''' or one of its derivatives such as '''Ubuntu''', '''Knoppix''' or '''GRML'''. Note that this guide applies to Joomla! {{JVer|2.5}} {{JVer|3.5}} {{JVer|3.6}}. It has been successfully tested on Debian 4.0 [Etch], Debian 5.0 [Lenny], Ubuntu 8.04 LTS [Hardy Heron], Ubuntu 10.10 [maverick] and Ubuntu 11.10 (Oneiric Ocelot). It will work for all '''Debian''' based Linux distribution as well.

Also note that this guide assumes, you're installing Joomla! in a '''single hosting''' environment, running PHP as module. If you want to run multiple web sites as a web hosting service provider, for security reasons you should consider setting up an suPHP (php5-cgi, libapache2-mod-suphp) environment, where every virtual Apache host runs under its own UID.

== Installing Joomla! ==
=== Prerequisites ===
You will need to install apache2, mysql-server-5.0, mysql-client-5.0 and php5 in order to have a web-server for Joomla!.

=== Which stack should I choose? ===

- [[Installing_Joomla_on_Debian_Linux#XAMPP|XAMPP]] automatically configures ownership.

- [[Installing_Joomla_on_Debian_Linux#LaMp|LaMp]] requires use of the CHOWN command.

- [[Installing_Joomla_on_Debian_Linux#BitNami_Joomla.21_stack|BitNami Joomla! Stack]] is free, self-contained and automatically configures the LAMP stack and Joomla!

== XAMPP ==
Download [http://sourceforge.net/projects/xampp/files/XAMPP%20Linux/ XAMPP] for Linux to your your Home folder.

=== Install XAMPP ===
Open Terminal and enter:

<source lang="bash">
sudo tar xvfz xampp-linux-1.8.3.tar.gz -C /opt
</source>

(replace ''xampp-linux-1.8.3.tar.gz'' with the version of XAMPP you downloaded).

This installs ... Apache2, mysql and php5 as well as an ftp server.

<source lang="bash">
sudo /opt/lampp/lampp start
</source>

and
<source lang="bash">
sudo /opt/lampp/lampp stop
</source>

starts/stops all the services

=== Test your XAMPP localhost server ===
Open your Browser and point it to
http://localhost
The index.php will redirect to
http://localhost/xampp

There you will find instructions on how to change default usernames/passwords. On a PC that does not serve files to the Internet or LAN then changing the defaults is personal choice.

=== Multiple Versions of XAMPP ===
It can be useful to have access to several versions of XAMPP on your PC (e.g to have available different versions of PHP for testing). XAMPP doesn't make this easy but it is possble - see [https://stackoverflow.com/questions/47498835/installing-two-versions-of-php-with-xampp-on-ubuntu-system "how to" article here] (for Linux only).

=== Get Joomla ===
Download the latest Joomla installation zip [http://www.joomla.org/download.html]

Unzip to your hard drive

Connect to localhost with an FTP client
Default
nobody
lampp

Use FTP to create a folder for your Joomla on the localhost server

FTP the unpacked Joomla installation files to the newly created Joomla folder.

'''Important:'''
* The XAMPP installation sets the correct Ownership of the files and permissions.
* Using the '''CHOWN command''' will '''cause Ownership problems with xampp'''.
* '''Using nautilus''' to manipulate folders/files on localhost will '''cause Ownership problems with xampp'''.

=== Configure Joomla ===
In your Browser type
http://localhost/yournewjoomlafolder

In the first Joomla installation screen if error reporting is shown as on then:

In your Terminal type
<source lang="bash">
sudo gedit /opt/lampp/etc/php.ini
</source>

In the <tt>php.ini</tt> file, locate
<source lang="ini">
error_reporting =
</source>
And change the value to
<source lang="ini">
error_reporting = E_ALL & ~E_NOTICE & ~E_DEPRECATED
</source>

Also locate
<source lang="ini">
display_errors = On
</source>
And change the value to
<source lang="ini">
display_errors = Off
</source>

Stop then restart xampp for the new settings to take effect

FTP layer is NOT needed

'''Database info'''

'''Host''': <code>localhost</code>

'''Database name''': <code>test</code>
:<code>(Xampp will automatically create a database of the name you specify).</code>

'''Default Database user''': <code>root</code>
:There is no Password for '''Database user''': <code>root</code>.

Administrator password is your choice.

Installing Sample Data is recommended for the novice user.

After installation delete the installation directory and point your Browser to:
http://localhost/yournewjoomlafolder
or
http://localhost/yournewjoomlafolder/administrator

=== Create a link in the Ubuntu menu ===
'''To create a GUI for XAMPP connected to your Ubuntu menu'''

Open up the Terminal and type
<source lang="bash">
sudo gedit /usr/share/applications/xampp-control-panel.desktop
</source>

Then copy the following into the gedit and save.

<source lang="ini">
[Desktop Entry]
Encoding=UTF-8
Name=XAMPP Control Panel
Comment=Start and Stop XAMPP
Exec=gksudo "python /opt/lampp/share/xampp-control-panel/xampp-control-panel.py"
Icon=/usr/share/icons/Tango/scalable/devices/network-wired.svg
Terminal=false
Type=Application
Categories=GNOME;Application;Network;
StartupNotify=true
</source>

'''N.B.''' Ubuntu 11.10 needs ''python-glade2'' installed in order to run the GUI. ''python-glade2'' can be found in the Ubuntu Software Center.

== LaMp ==
You will find instructions on [http://wiki.debian.org/LaMp wiki.debian.org]. Make sure that you have installed bzip2 for extracting the downloaded Joomla! package.

You can check this by the following command:
<source lang="bash">
$ dpkg -l | grep bzip2
</source>

Note that the dollar sign '$' shell prompt is indicating you're a ''regular user''. We will later see a hash mark (#) shell prompt, which indicates that you're the super user ''root'' after issuing an '''su''' or '''sudo'''. The first policy for a secure linux system administration on the command line (but under X also) is to issue commands with the lowest permission as possible.

If bzip2 is not installed, you won't get an output. Then you can quickly install it via aptitude:
<source lang="bash">
$ su -c "aptitude install bzip2"
</source>

Here we see the first command executed with root permissions, because a regular user is not allowed to install new software. The '-c' option passes the following command to '''su''' and hereafter it terminates instead of switching to a root shell.

=== Configure PHP5 ===
in the pre install check [ you get to that when the install is complete and are setting up Joomla at the web page ], Output Buffering was On and it's recommended that it should be Off .to do so
edit /etc/php5/apache2/php.ini , comment out this line: output_buffering = 4096 , by putting a ';' in front. it'll look like this when done:
;output_buffering = 4096

there were also warnings on the install screen regarding suhosin . to make the suggested changes, edit this file:
/etc/php5/conf.d/suhosin.ini
I set these :
<pre>
suhosin.post.max_array_index_length = 256
suhosin.post.max_totalname_length = 8192
suhosin.post.max_vars = 2048
suhosin.request.max_array_index_length = 256
suhosin.request.max_totalname_length = 8192
suhosin.request.max_vars = 2048
</pre>

=== Configure MySQL ===
It is time to create a database for Joomla! You can do this by the following commmands:
mysqladmin -u root -p create joomla

You may replace ''joomla'' with the name of choice for Joomla!'s database.

Now create a MySQL user different from root for Joomla!'s database. first enter into mysql system with:
mysql -u root -p
Then at the 'mysql>' prompt enter the following. Make sure you replace ''joomla'' with the name of Joomla!'s database from above. Replace ''yourusername'' with the user name you choose for the MySQL user accessing Joomla!'s database, and replace ''yourpassword'' with your password of choice for the MySQL user.
<source lang="bash">
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES, \
LOCK TABLES ON joomla.* TO 'yourusername'@'localhost' IDENTIFIED BY 'yourpassword';
</source>
Activate the settings and quit : [ there will be a mysql> prompt:
FLUSH PRIVILEGES;
\q

After disconnecting from the database server, you should remove the login information of your just new created MySQL user by editing MySQL's history file.
vi ~/.mysql_history

You can use any editor of your choice such as '''nano''', '''vi''' or '''emacs''' that is installed on your system.

=== Get Joomla! source ===
Now it is time to download the Joomla! sources. Currently you will find download links on the [http://joomlacode.org/download.html joomlacode.org] download page. For version 1.5.11, you may do the following from command line, assuming your current working directory is your home folder '''/home/user''':
<source lang="bash">
$ wget http://joomlacode.org/gf/download/frsrelease/10209/40306/Joomla_1.5.11-Stable-Full_Package.tar.bz2
$ cd /var/www
$ su
# mkdir -m 0755 joomla
# cd joomla
# tar -xvjf /home/user/Joomla_1.5.11-Stable-Full_Package.tar.bz2
</source>

for 1.7 use this wget line:
wget http://joomlacode.org/gf/download/frsrelease/15278/66553/Joomla_1.7.0-Stable-Full_Package.tar.bz2
You may want to check http://joomlacode.org/gf/project/joomla/frs/ for an updated package.

Here is the first time we see this hash mark (#) shell prompt. We call '''su''' without any options, because we want to issue root commands more than only one time. Calling '''su''' that way will prompt us for the super user's password and then change the actual shell environment, repectively $UID and $EUID.

=== Set ownerships and permissions ===
If you want to allow writing in the entire joomla folder, simply do

<source lang="bash">
chown -R www-data:www-data /var/www/joomla
</source>

If you want a more restrictive approach, do this instead:
<pre>
chown -R root:root /var/www/joomla
cd /var/www/joomla
PLACES='
administrator/backups
administrator/components
administrator/modules
administrator/templates
cache
components
images
images/banners
images/stories
language
mambots
mambots/content
mambots/editors
mambots/editors-xtd
mambots/search
media
modules
templates
'
for i in $PLACES; do chown -R www-data:www-data $i; done
</pre>

Now set file and directory permissions:
<source lang="bash">
find /var/www/joomla -type f -exec chmod 0644 {} \;
find /var/www/joomla -type d -exec chmod 0755 {} \;
</source>

=== Configure Joomla! ===
Open your favourite web-browser, and point it to the page http://localhost/joomla. Replace ''localhost'' with your servers IP or domain name if it you are installing on a remote system.

You will be guided through the final steps of setting up Joomla!, have your MySQL user, password and database name available.

When you reach the final screen with congratulations on installing Joomla!, you should remove the installation directory. From root terminal:
<source lang="bash">
# rm -rf /var/www/joomla/installation/
# exit
$
</source>

And that's it! Now you can login into the admin interface of your fresh installed Joomla! 1.5.9.

== BitNami Joomla! stack ==

=== What is BitNami Joomla! Stack? ===
BitNami Joomla! Stack is an all-in-one installer that makes it easy to install Joomla on your computer. It is free, easy to use and self-contained. That means it bundles and automatically configures every piece of software (dependency) necessary to run Joomla for development or production purposes, including Apache, MySQL and PHP.
You can download the latest version of BitNami Joomla! stack for Windows, Linux and OS X at http://bitnami.org/stack/joomla.

=== Installing Joomla! Stack ===
Regardless of which operating system you are running (Windows / Linux / Mac), the install process is the same.

Download the latest version of Joomla! Stack from the [http://bitnami.org/stack/joomla BitNami website].

Find the installer you just downloaded (the filename will be similar to bitnami-joomla-VERSION-linux-installer.run. Double click on the icon to launch the installer.

Note: If you are using Linux you will have to give executable permissions to the file first, using this command:
chmod +x /path/to/bitnami-joomla-VERSION-linux-installer.run

[[File:Joomla_welcome.png]]

Click "Forward".

[[File:Joomla_components.png]]

Select the components you want to install. If you are not sure, leave the default components checked. Click "Forward" when you are done.

[[File:Joomla_directory.png]]

Now it will ask where do you want to install the program. Provide the location where you want to install the BitNami Joomla! stack and click "Forward" when you are done.

[[File:Joomla_userdata.png]]

The user and password you provide here will be used to create the admin account in Joomla! Click "Forward" when you are done.

[[File:Joomla_sitename.png]]

Type in the name you want to use for your Joomla site, and click "Forward".

[[File:JoomlaReadytoinstall.png]]

The installer is now ready to begin the installation process. Click "Forward".

[[File:JoomlaCopyingfiles.png]]

Wait a minute while the installer copies the files and configures your Joomla! installation.

[[File:Joomlafinalscreen.png]]

Joomla! is now set up and ready to be used. Click "Finish" to launch the application.

[[File:Joomlaapplicationscreen.png]]

You can now log in using the username and password you provided during the installation.
<noinclude>[[Category:Installation]][[Category:Server setup local]][[Category:Server configurations]]<noinclude>

Installing Joomla on Debian Linux

2022-06-05T21:56:45Z

Topazgb: /* Get Joomla */

{{needs|technical review|Needs updating to latest PHP/MySQL Versions}}

== Preface ==

This document guides you through the manual installation of Joomla! on '''Debian GNU Linux''' or one of its derivatives such as '''Ubuntu''', '''Knoppix''' or '''GRML'''. Note that this guide applies to Joomla! {{JVer|2.5}} {{JVer|3.5}} {{JVer|3.6}}. It has been successfully tested on Debian 4.0 [Etch], Debian 5.0 [Lenny], Ubuntu 8.04 LTS [Hardy Heron], Ubuntu 10.10 [maverick] and Ubuntu 11.10 (Oneiric Ocelot). It will work for all '''Debian''' based Linux distribution as well.

Also note that this guide assumes, you're installing Joomla! in a '''single hosting''' environment, running PHP as module. If you want to run multiple web sites as a web hosting service provider, for security reasons you should consider setting up an suPHP (php5-cgi, libapache2-mod-suphp) environment, where every virtual Apache host runs under its own UID.

== Installing Joomla! ==
=== Prerequisites ===
You will need to install apache2, mysql-server-5.0, mysql-client-5.0 and php5 in order to have a web-server for Joomla!.

=== Which stack should I choose? ===

- [[Installing_Joomla_on_Debian_Linux#XAMPP|XAMPP]] automatically configures ownership.

- [[Installing_Joomla_on_Debian_Linux#LaMp|LaMp]] requires use of the CHOWN command.

- [[Installing_Joomla_on_Debian_Linux#BitNami_Joomla.21_stack|BitNami Joomla! Stack]] is free, self-contained and automatically configures the LAMP stack and Joomla!

== XAMPP ==
Download [http://sourceforge.net/projects/xampp/files/XAMPP%20Linux/ XAMPP] for Linux to your your Home folder.

=== Install XAMPP ===
Open Terminal and enter:

<source lang="bash">
sudo tar xvfz xampp-linux-1.8.3.tar.gz -C /opt
</source>

(replace ''xampp-linux-1.8.3.tar.gz'' with the version of XAMPP you downloaded).

This installs ... Apache2, mysql and php5 as well as an ftp server.

<source lang="bash">
sudo /opt/lampp/lampp start
</source>

and
<source lang="bash">
sudo /opt/lampp/lampp stop
</source>

starts/stops all the services

=== Test your XAMPP localhost server ===
Open your Browser and point it to
http://localhost
The index.php will redirect to
http://localhost/xampp

There you will find instructions on how to change default usernames/passwords. On a PC that does not serve files to the Internet or LAN then changing the defaults is personal choice.

=== Multiple Versions of XAMPP ===
It can be useful to have access to several versions of XAMPP on your PC (e.g to have available different versions of PHP for testing). XAMPP doesn't make this easy but it is possble - see [http://www.jamesbrice.com/multiple-xampp-versions "how to" article here] (for Linux only).

=== Get Joomla ===
Download the latest Joomla installation zip [http://www.joomla.org/download.html]

Unzip to your hard drive

Connect to localhost with an FTP client
Default
nobody
lampp

Use FTP to create a folder for your Joomla on the localhost server

FTP the unpacked Joomla installation files to the newly created Joomla folder.

'''Important:'''
* The XAMPP installation sets the correct Ownership of the files and permissions.
* Using the '''CHOWN command''' will '''cause Ownership problems with xampp'''.
* '''Using nautilus''' to manipulate folders/files on localhost will '''cause Ownership problems with xampp'''.

=== Configure Joomla ===
In your Browser type
http://localhost/yournewjoomlafolder

In the first Joomla installation screen if error reporting is shown as on then:

In your Terminal type
<source lang="bash">
sudo gedit /opt/lampp/etc/php.ini
</source>

In the <tt>php.ini</tt> file, locate
<source lang="ini">
error_reporting =
</source>
And change the value to
<source lang="ini">
error_reporting = E_ALL & ~E_NOTICE & ~E_DEPRECATED
</source>

Also locate
<source lang="ini">
display_errors = On
</source>
And change the value to
<source lang="ini">
display_errors = Off
</source>

Stop then restart xampp for the new settings to take effect

FTP layer is NOT needed

'''Database info'''

'''Host''': <code>localhost</code>

'''Database name''': <code>test</code>
:<code>(Xampp will automatically create a database of the name you specify).</code>

'''Default Database user''': <code>root</code>
:There is no Password for '''Database user''': <code>root</code>.

Administrator password is your choice.

Installing Sample Data is recommended for the novice user.

After installation delete the installation directory and point your Browser to:
http://localhost/yournewjoomlafolder
or
http://localhost/yournewjoomlafolder/administrator

=== Create a link in the Ubuntu menu ===
'''To create a GUI for XAMPP connected to your Ubuntu menu'''

Open up the Terminal and type
<source lang="bash">
sudo gedit /usr/share/applications/xampp-control-panel.desktop
</source>

Then copy the following into the gedit and save.

<source lang="ini">
[Desktop Entry]
Encoding=UTF-8
Name=XAMPP Control Panel
Comment=Start and Stop XAMPP
Exec=gksudo "python /opt/lampp/share/xampp-control-panel/xampp-control-panel.py"
Icon=/usr/share/icons/Tango/scalable/devices/network-wired.svg
Terminal=false
Type=Application
Categories=GNOME;Application;Network;
StartupNotify=true
</source>

'''N.B.''' Ubuntu 11.10 needs ''python-glade2'' installed in order to run the GUI. ''python-glade2'' can be found in the Ubuntu Software Center.

== LaMp ==
You will find instructions on [http://wiki.debian.org/LaMp wiki.debian.org]. Make sure that you have installed bzip2 for extracting the downloaded Joomla! package.

You can check this by the following command:
<source lang="bash">
$ dpkg -l | grep bzip2
</source>

Note that the dollar sign '$' shell prompt is indicating you're a ''regular user''. We will later see a hash mark (#) shell prompt, which indicates that you're the super user ''root'' after issuing an '''su''' or '''sudo'''. The first policy for a secure linux system administration on the command line (but under X also) is to issue commands with the lowest permission as possible.

If bzip2 is not installed, you won't get an output. Then you can quickly install it via aptitude:
<source lang="bash">
$ su -c "aptitude install bzip2"
</source>

Here we see the first command executed with root permissions, because a regular user is not allowed to install new software. The '-c' option passes the following command to '''su''' and hereafter it terminates instead of switching to a root shell.

=== Configure PHP5 ===
in the pre install check [ you get to that when the install is complete and are setting up Joomla at the web page ], Output Buffering was On and it's recommended that it should be Off .to do so
edit /etc/php5/apache2/php.ini , comment out this line: output_buffering = 4096 , by putting a ';' in front. it'll look like this when done:
;output_buffering = 4096

there were also warnings on the install screen regarding suhosin . to make the suggested changes, edit this file:
/etc/php5/conf.d/suhosin.ini
I set these :
<pre>
suhosin.post.max_array_index_length = 256
suhosin.post.max_totalname_length = 8192
suhosin.post.max_vars = 2048
suhosin.request.max_array_index_length = 256
suhosin.request.max_totalname_length = 8192
suhosin.request.max_vars = 2048
</pre>

=== Configure MySQL ===
It is time to create a database for Joomla! You can do this by the following commmands:
mysqladmin -u root -p create joomla

You may replace ''joomla'' with the name of choice for Joomla!'s database.

Now create a MySQL user different from root for Joomla!'s database. first enter into mysql system with:
mysql -u root -p
Then at the 'mysql>' prompt enter the following. Make sure you replace ''joomla'' with the name of Joomla!'s database from above. Replace ''yourusername'' with the user name you choose for the MySQL user accessing Joomla!'s database, and replace ''yourpassword'' with your password of choice for the MySQL user.
<source lang="bash">
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES, \
LOCK TABLES ON joomla.* TO 'yourusername'@'localhost' IDENTIFIED BY 'yourpassword';
</source>
Activate the settings and quit : [ there will be a mysql> prompt:
FLUSH PRIVILEGES;
\q

After disconnecting from the database server, you should remove the login information of your just new created MySQL user by editing MySQL's history file.
vi ~/.mysql_history

You can use any editor of your choice such as '''nano''', '''vi''' or '''emacs''' that is installed on your system.

=== Get Joomla! source ===
Now it is time to download the Joomla! sources. Currently you will find download links on the [http://joomlacode.org/download.html joomlacode.org] download page. For version 1.5.11, you may do the following from command line, assuming your current working directory is your home folder '''/home/user''':
<source lang="bash">
$ wget http://joomlacode.org/gf/download/frsrelease/10209/40306/Joomla_1.5.11-Stable-Full_Package.tar.bz2
$ cd /var/www
$ su
# mkdir -m 0755 joomla
# cd joomla
# tar -xvjf /home/user/Joomla_1.5.11-Stable-Full_Package.tar.bz2
</source>

for 1.7 use this wget line:
wget http://joomlacode.org/gf/download/frsrelease/15278/66553/Joomla_1.7.0-Stable-Full_Package.tar.bz2
You may want to check http://joomlacode.org/gf/project/joomla/frs/ for an updated package.

Here is the first time we see this hash mark (#) shell prompt. We call '''su''' without any options, because we want to issue root commands more than only one time. Calling '''su''' that way will prompt us for the super user's password and then change the actual shell environment, repectively $UID and $EUID.

=== Set ownerships and permissions ===
If you want to allow writing in the entire joomla folder, simply do

<source lang="bash">
chown -R www-data:www-data /var/www/joomla
</source>

If you want a more restrictive approach, do this instead:
<pre>
chown -R root:root /var/www/joomla
cd /var/www/joomla
PLACES='
administrator/backups
administrator/components
administrator/modules
administrator/templates
cache
components
images
images/banners
images/stories
language
mambots
mambots/content
mambots/editors
mambots/editors-xtd
mambots/search
media
modules
templates
'
for i in $PLACES; do chown -R www-data:www-data $i; done
</pre>

Now set file and directory permissions:
<source lang="bash">
find /var/www/joomla -type f -exec chmod 0644 {} \;
find /var/www/joomla -type d -exec chmod 0755 {} \;
</source>

=== Configure Joomla! ===
Open your favourite web-browser, and point it to the page http://localhost/joomla. Replace ''localhost'' with your servers IP or domain name if it you are installing on a remote system.

You will be guided through the final steps of setting up Joomla!, have your MySQL user, password and database name available.

When you reach the final screen with congratulations on installing Joomla!, you should remove the installation directory. From root terminal:
<source lang="bash">
# rm -rf /var/www/joomla/installation/
# exit
$
</source>

And that's it! Now you can login into the admin interface of your fresh installed Joomla! 1.5.9.

== BitNami Joomla! stack ==

=== What is BitNami Joomla! Stack? ===
BitNami Joomla! Stack is an all-in-one installer that makes it easy to install Joomla on your computer. It is free, easy to use and self-contained. That means it bundles and automatically configures every piece of software (dependency) necessary to run Joomla for development or production purposes, including Apache, MySQL and PHP.
You can download the latest version of BitNami Joomla! stack for Windows, Linux and OS X at http://bitnami.org/stack/joomla.

=== Installing Joomla! Stack ===
Regardless of which operating system you are running (Windows / Linux / Mac), the install process is the same.

Download the latest version of Joomla! Stack from the [http://bitnami.org/stack/joomla BitNami website].

Find the installer you just downloaded (the filename will be similar to bitnami-joomla-VERSION-linux-installer.run. Double click on the icon to launch the installer.

Note: If you are using Linux you will have to give executable permissions to the file first, using this command:
chmod +x /path/to/bitnami-joomla-VERSION-linux-installer.run

[[File:Joomla_welcome.png]]

Click "Forward".

[[File:Joomla_components.png]]

Select the components you want to install. If you are not sure, leave the default components checked. Click "Forward" when you are done.

[[File:Joomla_directory.png]]

Now it will ask where do you want to install the program. Provide the location where you want to install the BitNami Joomla! stack and click "Forward" when you are done.

[[File:Joomla_userdata.png]]

The user and password you provide here will be used to create the admin account in Joomla! Click "Forward" when you are done.

[[File:Joomla_sitename.png]]

Type in the name you want to use for your Joomla site, and click "Forward".

[[File:JoomlaReadytoinstall.png]]

The installer is now ready to begin the installation process. Click "Forward".

[[File:JoomlaCopyingfiles.png]]

Wait a minute while the installer copies the files and configures your Joomla! installation.

[[File:Joomlafinalscreen.png]]

Joomla! is now set up and ready to be used. Click "Finish" to launch the application.

[[File:Joomlaapplicationscreen.png]]

You can now log in using the username and password you provided during the installation.
<noinclude>[[Category:Installation]][[Category:Server setup local]][[Category:Server configurations]]<noinclude>

J3.x:After going to 4.1,1 or 3.10.7 some users can't login anymore

2022-03-30T12:56:10Z

Topazgb: add links

'''According to users in the forum this method does not fix the problem''' https://forum.joomla.org/viewtopic.php?p=3656713#p3656713

 '''The fix is''' https://www.akeeba.com/news/1750-do-not-install-the-joomla-4-1-1-and-3-10-7-updates.html

==Errors reported== 

Some users can't login after they have been able to login without entering a PW right after the update to 4.1.1 or 3.10.7.

==Versions affected== 
{{tip|This pertains only to Joomla! version(s): '''4.1.1 & 3.10.7'''|title=General Information}} 

==What is the cause== 

After the update the Joomla Core binds the user on login to the authentication provider. But when your first login is with an none primary update provider like the Cookie (Remember Me) after logging out the user can login again.

==How to fix== 

When you still have a SuperUser who can login into the backend, please go to: Users -> Manage -> "Username" -> Authentication Method -> Set to "None"

When you don't have a Super User who can login into the backend please go to the #__users table for the user and clear the value that's set in the "authProvider" column.

There will also be a 3.10.8 and 4.1.2 update that will apply the fix on all affected users and protect against the issue in the first place.

__NOTOC__

J4.x talk:Assorted Issues

2022-03-15T11:35:20Z

Topazgb:

Contents #2 https://docs.joomla.org/J4.x:Assorted_Issues#A_page_displays_with_no_styling. notice the full stop (period) at the end? It needs removing to make the link resolve. But I can't edit it.
--Topazgb 11:24, 14 March 2022 (CDT)

Fixed that - and I should know that Titles should not end with a full stop.

lol. I should have realised that the contents auto generated and all I needed to do was edit the text.
--Topazgb 06:35, 15 March 2022 (CDT)

J4.x talk:Assorted Issues

2022-03-14T16:24:53Z

Topazgb: Page needs editing but I can't edit the contents menu

Talk:Installing Joomla

2022-01-12T23:07:15Z

Topazgb: Created page with "2.5 no longer supported --~~~~"

2.5 no longer supported
--Topazgb 17:07, 12 January 2022 (CST)

Chunk30:ArticleOptions-tab-integration

2021-10-12T19:08:59Z

Topazgb: Spelling

<noinclude><languages /></noinclude>
<translate>===Integration=== </translate>
<translate>
These options control the display of other extensions.</translate>
:[[Image:Help30-Content-Article-Manager-Options-integration-options-subscreen-<translate>
en</translate>.png]]{{-}}

<translate>
*'''Show Feed Link.''' (Show/Hide) Whether to Show or Hide a link to a news feed (RSS Feed). If set to Show, a Feed Link will show up as a feed icon in the address bar of most modern browsers.</translate>
<translate>
*'''Include in Feed.''' (Intro Text/Full Text) If Intro Text, only the article's intro text will show in the feed. Otherwise, the entire text of the article will show.</translate>
<translate>
*'''Show "Read More".''' (Show/Hide) Show or Hide a "Read more" link in the newsfeed.</translate>
<translate>

*'''URL Routing.''' (Legacy/Modern) Modern routing enables advanced features but may change your URLs. Legacy routing ensures full compatibility for existing sites. This is configured per component.</translate>
<translate>

*'''Enable Custom Fields.''' (Yes/No) Enable the creation of custom fields.</translate>

Pre-Update Check

2021-08-24T10:11:25Z

Topazgb: Added extra instructions to move past the pre update check

<noinclude><languages /></noinclude>
<translate> New to Joomla! 3.10.x is the Pre-Update Check. This view of the Joomla Update component shows technical specifications of the server the site is on and core and third-party extensions that use the Update Server in a list form.</translate>

'''To navigate to the Update-screen:'''
*Click the 'Live Update' tab.

<translate>

'''To navigate to the Pre-Update Check-screen:'''
*Click in the top bar {{rarr|Components,Joomla! Update}} menu item.
*If you don´t see the Pre-Update Check-screen click on the '''Check for Updates''' button or clear cache and refresh the page.</translate>

<translate>
== Technical Specifications == </translate>
<translate>

The top portion of the Pre-Update Check shows whether your current server environment is compatible with the current target version Joomla for both the required PHP and database settings. The data on the [https://downloads.joomla.org/technical-requirements Technical Requirements] page show the specs we are checking against.</translate>

[[File:php_and_database_settings-<translate> en</translate>.png|border|800px|<translate> Required PHP and Database Settings portion of the Pre-Update Check Component</translate>]]
[[File:Recommended_php_settings-<translate> en</translate>.png|border|800px|<translate> Recommended PHP Settings portion of the Pre-Update Check Component</translate>]]

<translate>

What's important is to check if anything is red and not compatible with Joomla 4.x. If it isn't, you'll need to talk to your host or change hosts before migrating to Joomla 4.x. During a migration is a great time to change hosts. See the [[S:MyLanguage/Why Migrate|Migration Funnel]] for more information on planning and step-by-step instructions.</translate>

<translate>
== Extensions Pre-Update Check == </translate>
<translate>

The extension portion of the Pre-Update Check component pulls third-party extensions.</translate>

<translate>

The list is broken into sections based on the ''targetplatform'' tag, the extensions you are or are not using. For developers, see [[S:MyLanguage/Deploying an Update Server|Deploying an Update Server]] for more information about these tags and how to deploy an Update Server. For more information about the Joomla Update System, see the [https://extensions.joomla.org/support/knowledgebase/submission-requirements/joomla-update-system-requirement/ Joomla! Update System Requirement] and [https://docs.joomla.org/Help39:Extensions_Extension_Manager_Update Extensions Extension Manager Update] pages.</translate>

<translate>

By clicking the '''More Detail''' link to the right in each colour heading, you can see additional information about the extensions installed on your site.</translate>

[[File:pre_upgrade_checker_error-<translate> en</translate>.png|border|800px|<translate> Update Information Unaviable</translate>]]

<translate>

The extensions listed here do not support yet the Joomla Update system or atleast do not have an targetplatform tag that indicates support for the selected target Joomla Version. (see [[Deploying an Update Server]]) Please contact the developer of the listed extensions to make sure they are compatible with 4.x</translate>

[[File:pre_upgrade_checker_warning-<translate> en</translate>.png|border|800px|<translate> Update Required</translate>]]

<translate>

The extensions listed here require an update to work correctly on 4.x. Please contact the developer of the listed extensions to make sure whether you have to update the component before or after the upgrade.</translate>

[[File:pre_upgrade_checker_ok-<translate> en</translate>.png|border|800px|<translate> No Update Required</translate>]]

<translate>

The extensions listed here claim to be 4.x compatible and no update is required.</translate>

<translate>
== What is it about that ''Potential Upgrade Issue'' == 


Plugins with the type ('system', 'user', 'authentication', 'actionlog', 'twofactorauth') could be triggered while we are processing the upgrade. When there is a critical issue within that plugins that could result into a broken upgrade and make the site unusable. For that reason any plugin from that type that is not explicite listed as compatible has to be even more carefully reviewed before you hit the upgrade button. It is '''strongly''' recommended to disable the plugins in question and to check with the original developer.</translate>

[[File:Pre_upgrade_checker_popup-<translate> en</translate>.png|200px|<translate>The popup warning for potencial upgrade issue</translate>]]

<translate>
On the ''Live Update'' Tab you will be preseted again with the full list of potential breaking extensions.</translate>

[[File:Live_upgrade_tab_errors-<translate> en</translate>.png|border|800px|<translate>The Live Update message on potential breaking extensions</translate>]]

<translate>
It is '''strongly''' recommended to disable all extensions including the plugins listed here before you run the upgrade because the extensions listed here seem not to be compatible with your target version but could break your upgrade.</translate>

<translate>
You know what you are doing? You want to choose to ignore the warnings and run the upgrade anyway you can do so by checking the checkbox. As that is taking your site at risk of breaking without an easy recovery this is the last time to remind you to take a backup!</translate>
<translate>
== Questions and Answers == </translate>
<translate>

Let's break this down into some questions and answers.</translate>

<translate>

'''Q: What do the tags mean?'''</translate>

<translate>

A: The green '''No Update Required''' tag means that the extension has been tagged by the developer that the extension as ready for Joomla 4. It ''should'' migrate with the one-click from 3.10.x to 4.x. Verifying with the developer is suggested.</translate>

<translate>

The red '''Update Information Unavailable''' tag means that the extension has not added compatibility information the extension. Check with the developer on the migration path from 3.10.x to 4.x.</translate>

<translate>

The yellow/orange '''Yes (x.x.x)''' tag means that the extension has been tagged by the developer that the extension may need an update in order to be compatible with Joomla 4. Update the extension and see if it turns to a green Yes. If it doesn't, check with the developer on the migration path from 3.10.x to 4.x.</translate>

<translate>

The gray '''Missing Compatibility Tag''' means that the extension doesn't have a tag '''or''' does not use the Update Server. The developer hasn't said yes or no or needs an update. In some cases, a package may have been installed and the component portion has a tag but the additional plugins or modules are missing tags. As always, you'll need to check with each extension developer to verify the migration path from 3.10.x to 4.x.</translate>

<translate>

'''Q: What about the Joomla core components?'''</translate>

<translate>

A: Joomla core extensions will migrate from 3.10.x to 4.x on the one-click with these exceptions:</translate>

<translate>

The language packs are not yet ready for Joomla 4 (as of September 2020). Over time, they will be. If your site depends on other language packs, wait to migrate until all the language packs are ready.</translate>

<translate>

The Weblinks component is not yet ready for Joomla 4 (as of September 2020). If you're going to continue using Weblinks in your Joomla 4 site, wait to migrate until the Weblinks component is ready.</translate>

<translate>

'''Q: What about templates?'''</translate>

<translate>

A: Because of the changes in Joomla 4, your template may or may not be compatible with Joomla 4. The core templates like Protostar, Beez3, Beez5, and so on will ''convert'' to the new Cassiopeia template on the one click and the older templates will be completely removed.</translate> <translate> If you're using a club template from a third-party developer that is not compatible with Joomla 4, you'll need to change your default template to Protostar (or Beez3) before you do the one-click. If you have older administrator templates or core templates, it's recommended to uninstall all of them except whichever of the core templates you will set as default. This includes Bluestork, Hathor, the other beez templates. You will keep Isis as the administrator template. You will keep either your compatible third-party template, Protostar or Beez3 as default. You will uninstall the rest.</translate>

<translate>

'''Q: Can I uninstall plg_content_geshi?'''</translate>

<translate>

A: Yes. This is leftover from the 2.5 life cycle and '''must''' be uninstalled.</translate>

<translate>

'''Q: What about all that FOF, fef, etc.?'''</translate>

<translate>

A: Many extensions in the red or yellow/orange headings '''will/may''' make it through the one-click and migrate fine. It is recommended that you go to Extensions→Manage→Manage and check all extensions. Typically the ones authored by Joomla will migrate on the one click. Typically the Akeeba extensions will too. Again, check with extension developers to verify the migration path on '''all''' third-party extensions.</translate>

<translate>

'''Q: Does the Extensions Pre-Update Check show all the extensions installed on my site?'''</translate>

<translate>

A: The Pre-Update Check will show all extensions. Only extensions that use the Update Server are given compatibility information. Those extensions that do not use the Update Server will show in the list with the '''Missing Compatibility Tag'''.</translate>

<translate>
== Summary == </translate>
<translate>

From a migration perspective, it is my belief that the Pre-Update Check should be used a guide. You'll want to have a second tab open with ''Extensions→Manage→Manage'' open in order to uninstall any extensions or check who they're authored by so you can contact third-party extension developers on the migration path they've established to migrate their extensions.</translate>

<noinclude>
<translate>

[[Category:Joomla!_4.x]]
[[Category:Version 4.x FAQ]]
</translate>
</noinclude>

Talk:Planning Migration - Joomla 1.5 to 3

2021-05-17T23:45:01Z

Topazgb:

Perhaps this should be Archived as it is far easier to create a Joomla 3.x from scratch ?
--Topazgb 04:08, 1 October 2018 (CDT)

https://docs.joomla.org/Joomla_1.5_to_3.x_Step_by_Step_Migration is more extensive anyway
--Topazgb 18:45, 17 May 2021 (CDT)

Moving the site among directories/sub-directories

2021-03-29T21:00:40Z

Topazgb: edited path for logs file

<noinclude><languages /></noinclude>
<translate>
Many times you install Joomla in a sub-directory and then want to move it to a higher level directory, here's a short tutorial on how to do it.</translate>

<translate>
Say you have installed Joomla in the following folder: public_html/tryjoomla.</translate>
<translate>
Now that you are satisfied with the site, you'll want to move to public_html.</translate>

<translate>
1. Move all the files from the sub-directory (i.e., public_html/tryjoomla) to the upper level directory (i.e., public_html). You can use your favourite FTP client or the control panel that your hosting service provides.</translate>

<translate>
2. Download and open the configuration.php file in a text editor.</translate>

<translate>
3. Simply remove the tryjoomla folder name from the path. Look for the following lines</translate>

<source lang="php">
var $live_site = '';
var $log_path = '/home/username/public_html/tryjoomla/administrator/logs';
var $tmp_path = '/home/username/public_html/tryjoomla/tmp';
var $ftp_root = 'public_html/tryjoomla';
</source>

<translate>
Change to:</translate>

<source lang="php">
var $live_site = '';
var $log_path = '/home/username/public_html/administrator/logs';
var $tmp_path = '/home/username/public_html/tmp';
var $ftp_root = 'public_html';
</source>

<translate>
N.B.
The $live_site variable rarely needs to be given a value. But if it was given a value during installation then edit that path as well.</translate>

<source lang="php">
var $live_site = 'http://www.example.com/tryjoomla';
</source>
<translate>
Change to:</translate>
<source lang="php">
var $live_site = 'http://www.example.com';
</source>

<translate>
4. Check your site's .htaccess file. The subfolder should be removed there as well. The RewriteBase directive should be commented out. Check for a RewriteRule that contains the old subdirectory.</translate>

<translate>
5. Verify that no redirect orders to the old subdirectory are in place in your hosting control panel.</translate>

<translate>
If you have cache enabled, login to the administrator backend (which will now be at http://www.example.com/administrator and not http://www.example.com/tryjoomla/administrator). Go to Tools -> Clean Cache and delete all cache files.</translate>

<noinclude>
<translate>

[[Category:Administration FAQ]]
[[Category:Installation FAQ]]
[[Category:Update Working Group]]
</translate>
</noinclude>

Moving the site among directories/sub-directories

2021-03-27T21:30:59Z

Topazgb: edited path for logs file

<noinclude><languages /></noinclude>
<translate>
Many times you install Joomla in a sub-directory and then want to move it to a higher level directory, here's a short tutorial on how to do it.</translate>

<translate>
Say you have installed Joomla in the following folder: public_html/tryjoomla.</translate>
<translate>
Now that you are satisfied with the site, you'll want to move to public_html.</translate>

<translate>
1. Move all the files from the sub-directory (i.e., public_html/tryjoomla) to the upper level directory (i.e., public_html). You can use your favourite FTP client or the control panel that your hosting service provides.</translate>

<translate>
2. Download and open the configuration.php file in a text editor.</translate>

<translate>
3. Simply remove the tryjoomla folder name from the path. Look for the following lines</translate>

<source lang="php">
var $live_site = '';
var $log_path = '/home/username/public_html/tryjoomla/administrator/logs';
var $tmp_path = '/home/username/public_html/tryjoomla/tmp';
var $ftp_root = 'public_html/tryjoomla';
</source>

<translate>
Change to:</translate>

<source lang="php">
var $live_site = '';
var $log_path = '/home/username/public_html/public html folder/logs';
var $tmp_path = '/home/username/public_html/tmp';
var $ftp_root = 'public_html';
</source>

<translate>
N.B.
The $live_site variable rarely needs to be given a value. But if it was given a value during installation then edit that path as well.</translate>

<source lang="php">
var $live_site = 'http://www.example.com/tryjoomla';
</source>
<translate>
Change to:</translate>
<source lang="php">
var $live_site = 'http://www.example.com';
</source>

<translate>
4. Check your site's .htaccess file. The subfolder should be removed there as well. The RewriteBase directive should be commented out. Check for a RewriteRule that contains the old subdirectory.</translate>

<translate>
5. Verify that no redirect orders to the old subdirectory are in place in your hosting control panel.</translate>

<translate>
If you have cache enabled, login to the administrator backend (which will now be at http://www.example.com/administrator and not http://www.example.com/tryjoomla/administrator). Go to Tools -> Clean Cache and delete all cache files.</translate>

<noinclude>
<translate>

[[Category:Administration FAQ]]
[[Category:Installation FAQ]]
[[Category:Update Working Group]]
</translate>
</noinclude>

Talk:How to control module display when linking to an article with no menu item

2021-03-10T10:11:47Z

Topazgb: /* How to control module display with no menu item */

== How to control module display with no menu item ==

Mod OnAnyPage, a moduie available from the [http://extensions.joomla.org/component/option,com_mtree/task,viewlink/link_id,6418/Itemid,35/ extensions directory], makes it possible to control on which pages a module is displayed regardless of the normal Joomla system of menu assignment of modules. Part of the functionality is that a module can be displayed only with one or more specific articles, whether or not those articles are associated with a menu item. In most cases, using this module will be an easier, quicker and better solution than what is explained in the article.

Added this to the article. Thanks for the tip! [[User:Dextercowley|Mark Dexter]] 19:13, 12 November 2008 (EST)

Looks like this module has been unpublished for non-GPL compliance. Should it be removed from the article? [[User:betweenbrain|Matt Thomas]] 11:38, 14 October 2009 (EST)

If that is the case, I would think we should remove it. Thanks. [[User:Dextercowley|Mark Dexter]] 15:48, 14 October 2009 (UTC)
---

Broken link

How do you assign a module to specific pages?

2020-12-01T10:45:56Z

Topazgb: Fixed typo fix. Changed ISs to ID's

<noinclude><languages /></noinclude>
<translate>
Navigate to {{rarr|Extensions,Module Manager}}. Select the module you want to assign and edit it.</translate>

<translate>
In Joomla! 3.x this is found in the Menu Assignment tab of the module.</translate>

<translate>
You can choose between ''On all pages'', ''No pages'', ''Only on the pages selected'', ''On all pages except those selected'' from the List. To assign to some but not all pages choose the third option and select the menu links that you want the module associated with.</translate>

<translate>
'''Notes:'''</translate>
<translate>
* If your module is assigned to a position that does not exist in the template used to display a page, the module will not appear even if it is assigned to a specific page. ''(Unless {loadmodule} or {loadposition} are used in the Article [https://docs.joomla.org/How_do_you_put_a_module_inside_an_article%3F How do you put a module inside an article?])''</translate>
<translate>
* If your module is not published/enabled it will not appear even if assigned to a page.</translate>
<translate>
* You cannot assign a module to a URL link. This is because URL links do not have Itemids assigned to them.</translate>
<translate>
* You cannot ''directly'' assign modules to pages that are only linked via content (for example, a link from one article to another) or other, non-menu modules (for example, a link to an article from a module), because these also do not have Item ID's. One work-around for this problem is to have an unpublished menu that contains links to the items you wish to link through non-menus. This will create an itemid that can be included in the url you link to.</translate>

<translate>
== Advanced options == 
</translate>
<translate>
There are several [http://extensions.joomla.org/extensions/access-a-security/modules-management extensions in JED] that give advanced options when assigning modules.</translate>

<noinclude>
<translate>

[[Category:FAQ]]
[[Category:Administration FAQ]]
[[Category:Getting Started FAQ]]
[[Category:Module Management]]
</translate>
</noinclude>

How do you recover or reset your admin password?

2020-09-10T09:03:29Z

Topazgb: edit grammar.

<noinclude><languages /></noinclude>
{{version|2.5,3.x,4.x}}
{{tip|text=<translate>
This page is only for Joomla! 2.5 and higher versions. If you are still using Joomla! 1.5 </translate> [[S:MyLanguage/J1.5:How_do_you_recover_or_reset_your_admin_password%3F|<translate>
instructions can be found here</translate>]].|title=<translate>
Joomla! 1.5 Password Recovery</translate>}}

<translate>

Normally, you can add, edit and delete users and passwords from the back-end User Manager. To do this, you must be logged in as a member of the Super Administrator group.


In some situations, this may not be possible. For example, your site may have been "hacked" and had the passwords or users changed. Or perhaps the person who knew the passwords is no longer available. Or maybe you have forgotten the password that was used.


In these cases, it is still possible to alter the Joomla! database so you can log back in as a Super Administrator. These are the possible methods available to Joomla! administrators.
</translate>

<translate>
== Method 1: configuration.php file == 
</translate>
<translate>

If you have access to your <code>configuration.php</code> file for the Joomla installation on your server, then you can recover the password using the following method:


1. Using an FTP program connect to your site. Find the configuration.php file and look at the file permissions. If the permissions are 444 or some other value, then change the permissions of the configuration.php file to 644. This will help prevent issues when uploading the changed configuration.php file later in this process.


2. Download the configuration file.


3. Open the configuration.php file that was downloaded in a text editor such as notepad++ and add this line
</translate>

public $root_user='myname';

<translate>

to the bottom of the list where myname is a username with administrator access that you know the password for. A username that is ai the Author User Group view access level or higher can also be used in place of a username with administrator access.


4. Save the configuration.php file and upload it back to the site. You may leave the permissions on the configuration.php file at 644.


This user will now be a temporary super administrator.


5. Login to the back end and change the password of the administrator user you don't have the password for or create a new super admin user.
If you create the new user you may want to block or delete the old user depending on your circumstances.
</translate>

<translate>

6. When finished, make sure to use the "Click here to try to do it automatically" link that appears in the alert box to remove the line that was added to the configuration.php file. If using the link was not successful, then go back and delete the added line from your configuration.php file using a text editor. Upload the configuration.php file back to the site.
</translate>

<translate>

7. Using your FTP program verify the file permissions of the configuration.php file, they should be 444. If you manually removed the added line, then change the file permissions on the configuration.php file to 444.


If you have no users who know their passwords and you can't utilize front end registration you may need to make a change in your database as outlined below in this document.
</translate>

<translate>

== Method 2: Direct Editing of Database == 
If the methods above did not work, you have two other options, both of which require working with the MySQL database directly.
</translate>

<translate>
===Change the Password in the Database=== 
If the admin user is still defined, the simplest option is to change the password in the database to a known value. This requires that you have access to the MySQL database using phpMyAdmin or another client.
</translate>
{{warning|<translate>
These instructions show how to manually change a password to the word</translate> - "secret"|title=<translate>
Make sure you change your password once you regain access</translate>}}

<translate>
# Navigate to phpMyAdmin and select the database for the Joomla! site in the left-hand drop-down list box. This will show the database tables on the left side of the screen.
# Find and click on the table with "_users" appended in the list of tables (note: you may have a prefix that is not jos_, simply go to the _users table for your prefix).
# Click on the "Browse" button in the top toolbar. This will show all of the users that are set up for this site.</translate>
<translate>
# Find the user whose password you want to change and press the Edit icon for this row.
# A form will display that allows you to edit the password field. Copy the value</translate> <source lang="sql">d2064d358136996bd22421584a7cb33e:trd7TvKHx6dMeoMmBVxYmg0vuXEA4199</source> <translate>
into the password field and press the ''Go'' button. phpMyAdmin should display the message "Affected rows: 1". At this point, the password should be changed to '''"secret"'''.
# Log in with this user and password and change the password of this user to a secure value. Check all of the users using the User Manager to make sure they are legitimate. If you have been hacked, you may want to change all of the passwords on the site.</translate>

<translate>
===Add a New Super Administrator User=== 
If changing the password won't work, or you aren't sure which user is a member of the Super Administrator group, you can use this method to create a new user.
</translate>

<translate>
# Navigate to phpMyAdmin and select the database for the Joomla! site in the left-hand drop-down list box. This will show the database tables on the left side of the screen.
# Press the "SQL" button in the toolbar to run an SQL query on the selected database. This will display a field called "Run SQL query/queries on database <your database>".</translate>
<translate>
# Delete any text in this field and copy and paste the following query below and press the ''Go'' button to execute the query and add the new Administrator user to the table.
# Use the SQL query below to add another administrator account.</translate>

{{warning|<translate>
The following code uses jos31_ as the table name prefix which is only an example table prefix. The prefix when you first installed Joomla is '''RANDOM''' or what you set it specifically too. You will need to change all occurrences of '''jos31_'''(your install set prefix) found in the code below to the prefix your installation is using.</translate> |title=<translate>
Make sure you match your db table prefix!</translate>}}

'''<translate>
SQL code for use with Joomla</translate> {{JVer/multi|2.5, 3.x, 4.x}} '''

<source lang="sql">INSERT INTO `jos31_users`
(`name`, `username`, `password`, `params`, `registerDate`, `lastvisitDate`, `lastResetTime`)
VALUES ('Administrator2', 'admin2',
'd2064d358136996bd22421584a7cb33e:trd7TvKHx6dMeoMmBVxYmg0vuXEA4199', '', NOW(), NOW(), NOW());
INSERT INTO `jos31_user_usergroup_map` (`user_id`,`group_id`)
VALUES (LAST_INSERT_ID(),'8');
</source>

<translate>

At this point, you should be able to log into the back end of Joomla! with the username of "admin2" and password of "secret". After logging in, go to the User Manager and change the password to a new secure value and add a valid e-mail address to the account. If there is a chance you have been "hacked", be sure to check that all users are legitimate, especially any members of the Super Administrator group.
</translate>

{{warning|<translate>
Warning: The password values shown on this page are public knowledge and are only for recovery. Your site may be hacked if you do not change the password to a secure value after logging in. Be sure you change the password to a secure value after logging in.</translate>}}

<translate>
The examples above change the password to "secret". Two other possible values are shown below:</translate>
<pre>
- password = "this is the MD5 and salted hashed password"
------------------------------------------------------
- admin = 433903e0a9d6a712e00251e44d29bf87:UJ0b9J5fufL3FKfCc0TLsYJBh2PFULvT
- secret = d2064d358136996bd22421584a7cb33e:trd7TvKHx6dMeoMmBVxYmg0vuXEA4199
- OU812 = 5e3128b27a2c1f8eb53689f511c4ca9e:J584KAEv9d8VKwRGhb8ve7GdKoG7isMm
</pre>

<noinclude><translate>
[[Category:FAQ]][[Category:Administration FAQ]][[Category:Getting Started FAQ]] [[Category:User Management]]</translate></noinclude>

How do you recover or reset your admin password?

2020-09-10T08:59:14Z

Topazgb: correcting grammar. An ftp program connects to but when using an ftp program you connect to. When using something the singular of what you are using is used not the plural.

<noinclude><languages /></noinclude>
{{version|2.5,3.x,4.x}}
{{tip|text=<translate>
This page is only for Joomla! 2.5 and higher versions. If you are still using Joomla! 1.5 </translate> [[S:MyLanguage/J1.5:How_do_you_recover_or_reset_your_admin_password%3F|<translate>
instructions can be found here</translate>]].|title=<translate>
Joomla! 1.5 Password Recovery</translate>}}

<translate>

Normally, you can add, edit and delete users and passwords from the back-end User Manager. To do this, you must be logged in as a member of the Super Administrator group.


In some situations, this may not be possible. For example, your site may have been "hacked" and had the passwords or users changed. Or perhaps the person who knew the passwords is no longer available. Or maybe you have forgotten the password that was used.


In these cases, it is still possible to alter the Joomla! database so you can log back in as a Super Administrator. These are the possible methods available to Joomla! administrators.
</translate>

<translate>
== Method 1: configuration.php file == 
</translate>
<translate>

If you have access to your <code>configuration.php</code> file for the Joomla installation on your server, then you can recover the password using the following method:


1. Using an FTP program connect to your site. Find the configuration.php file and look at the file permissions. If the permissions are 444 or some other value, then change the permissions of the configuration.php file to 644. This will help prevent issues when uploading the changed configuration.php file later in this process.


2. Download the configuration file.


3. Open the configuration.php file that was downloaded in a text editor such as notepad++ and add this line
</translate>

public $root_user='myname';

<translate>

to the bottom of the list where myname is a username with administrator access that you know the password for. A username that is at the Author level or higher can also be used in place of a username with administrator access.


4. Save the configuration.php file and upload it back to the site. You may leave the permissions on the configuration.php file at 644.


This user will now be a temporary super administrator.


5. Login to the back end and change the password of the administrator user you don't have the password for or create a new super admin user.
If you create the new user you may want to block or delete the old user depending on your circumstances.
</translate>

<translate>

6. When finished, make sure to use the "Click here to try to do it automatically" link that appears in the alert box to remove the line that was added to the configuration.php file. If using the link was not successful, then go back and delete the added line from your configuration.php file using a text editor. Upload the configuration.php file back to the site.
</translate>

<translate>

7. Using your FTP program verify the file permissions of the configuration.php file, they should be 444. If you manually removed the added line, then change the file permissions on the configuration.php file to 444.


If you have no users who know their passwords and you can't utilize front end registration you may need to make a change in your database as outlined below in this document.
</translate>

<translate>

== Method 2: Direct Editing of Database == 
If the methods above did not work, you have two other options, both of which require working with the MySQL database directly.
</translate>

<translate>
===Change the Password in the Database=== 
If the admin user is still defined, the simplest option is to change the password in the database to a known value. This requires that you have access to the MySQL database using phpMyAdmin or another client.
</translate>
{{warning|<translate>
These instructions show how to manually change a password to the word</translate> - "secret"|title=<translate>
Make sure you change your password once you regain access</translate>}}

<translate>
# Navigate to phpMyAdmin and select the database for the Joomla! site in the left-hand drop-down list box. This will show the database tables on the left side of the screen.
# Find and click on the table with "_users" appended in the list of tables (note: you may have a prefix that is not jos_, simply go to the _users table for your prefix).
# Click on the "Browse" button in the top toolbar. This will show all of the users that are set up for this site.</translate>
<translate>
# Find the user whose password you want to change and press the Edit icon for this row.
# A form will display that allows you to edit the password field. Copy the value</translate> <source lang="sql">d2064d358136996bd22421584a7cb33e:trd7TvKHx6dMeoMmBVxYmg0vuXEA4199</source> <translate>
into the password field and press the ''Go'' button. phpMyAdmin should display the message "Affected rows: 1". At this point, the password should be changed to '''"secret"'''.
# Log in with this user and password and change the password of this user to a secure value. Check all of the users using the User Manager to make sure they are legitimate. If you have been hacked, you may want to change all of the passwords on the site.</translate>

<translate>
===Add a New Super Administrator User=== 
If changing the password won't work, or you aren't sure which user is a member of the Super Administrator group, you can use this method to create a new user.
</translate>

<translate>
# Navigate to phpMyAdmin and select the database for the Joomla! site in the left-hand drop-down list box. This will show the database tables on the left side of the screen.
# Press the "SQL" button in the toolbar to run an SQL query on the selected database. This will display a field called "Run SQL query/queries on database <your database>".</translate>
<translate>
# Delete any text in this field and copy and paste the following query below and press the ''Go'' button to execute the query and add the new Administrator user to the table.
# Use the SQL query below to add another administrator account.</translate>

{{warning|<translate>
The following code uses jos31_ as the table name prefix which is only an example table prefix. The prefix when you first installed Joomla is '''RANDOM''' or what you set it specifically too. You will need to change all occurrences of '''jos31_'''(your install set prefix) found in the code below to the prefix your installation is using.</translate> |title=<translate>
Make sure you match your db table prefix!</translate>}}

'''<translate>
SQL code for use with Joomla</translate> {{JVer/multi|2.5, 3.x, 4.x}} '''

<source lang="sql">INSERT INTO `jos31_users`
(`name`, `username`, `password`, `params`, `registerDate`, `lastvisitDate`, `lastResetTime`)
VALUES ('Administrator2', 'admin2',
'd2064d358136996bd22421584a7cb33e:trd7TvKHx6dMeoMmBVxYmg0vuXEA4199', '', NOW(), NOW(), NOW());
INSERT INTO `jos31_user_usergroup_map` (`user_id`,`group_id`)
VALUES (LAST_INSERT_ID(),'8');
</source>

<translate>

At this point, you should be able to log into the back end of Joomla! with the username of "admin2" and password of "secret". After logging in, go to the User Manager and change the password to a new secure value and add a valid e-mail address to the account. If there is a chance you have been "hacked", be sure to check that all users are legitimate, especially any members of the Super Administrator group.
</translate>

{{warning|<translate>
Warning: The password values shown on this page are public knowledge and are only for recovery. Your site may be hacked if you do not change the password to a secure value after logging in. Be sure you change the password to a secure value after logging in.</translate>}}

<translate>
The examples above change the password to "secret". Two other possible values are shown below:</translate>
<pre>
- password = "this is the MD5 and salted hashed password"
------------------------------------------------------
- admin = 433903e0a9d6a712e00251e44d29bf87:UJ0b9J5fufL3FKfCc0TLsYJBh2PFULvT
- secret = d2064d358136996bd22421584a7cb33e:trd7TvKHx6dMeoMmBVxYmg0vuXEA4199
- OU812 = 5e3128b27a2c1f8eb53689f511c4ca9e:J584KAEv9d8VKwRGhb8ve7GdKoG7isMm
</pre>

<noinclude><translate>
[[Category:FAQ]][[Category:Administration FAQ]][[Category:Getting Started FAQ]] [[Category:User Management]]</translate></noinclude>

Backup Basics for a Joomla! Web Site

2020-08-20T23:49:20Z

Topazgb:

<noinclude><languages /></noinclude>
<translate>
Always keep a recent backup of your site. Accidents happen, but there are many other reasons to have your backup files handy before the need arises. '''N.B. backups should not be used to restore a hacked site because the hack could have been on the site for some time could have been backed up with the site.'''</translate>

<translate>
The causes of data loss are many. Joomla sites can be compromised by malicious attackers if the site administrator has not paid attention to security or in cases when hackers bypass the best security. Joomla! is designed for teamwork, and even good editors can make an error that harms the site.</translate>

<translate>
There are many reasons website administrators need to revert the site to a previous working state.</translate>

<translate>
Practice both backup and restore. Nobody should wait for an emergency to test their skills and tools for dealing with an emergency. Very often people create a backup of something that is empty or corrupted and discover that none of their critical data was backed up. Nobody likes a ship that sinks with empty lifeboats. It's also wise to practice getting people out of the lifeboats and into a new working system.</translate>

<translate>
Having a backup is not just about accidents; a person well versed in backup can help with safe development of new features. Backup and restore help web managers create a staging website where new changes can be practiced without risking the production website. The clone can be created on a local machine acting as a test server or any other folder or web hosting account supporting the SQL and PHP versions used by the site you've backed up.</translate>

<translate>
It's easy for anyone to mix up their live site and staging site, so change the color of your staging site template to remind developers that the staging site is not live to the public.</translate>

<translate>
== Back Up a Joomla Website Using Akeeba (Common method) == 
</translate>

<translate>
This is the preferred method using the Akeeba Backup Extension.</translate>
<translate>
* Akeeba Backup produces a ''.jpa'' file.</translate>
<translate>
* The compressed ''.jpa'' file contains all the Website's files and the content of the database.</translate>
<translate>
* The ''.jpa'' file also includes an installer.</translate>
<translate>
* Akeeba's ''kickstart.php'' unpacks the ''.jpa'' file.</translate>
<translate>
* You then run the installer and install your site like a Joomla install.</translate>
<translate>
* The installer changes the configuration for restoring to a different location and prompts for the new database details.</translate>

<translate>
You can download the Akeeba Backup extension from the [https://extensions.joomla.org/extensions/extension/access-a-security/site-security/akeeba-backup/ Joomla extension directory]. There is a link to full instructions there as well.</translate>

<translate>

== Backup Two-Part Method == 
</translate>

<translate>
There are two parts to a complete back up of your Joomla site. They are:</translate>

<translate>
# The database information, most often found in your MySQL database.</translate>
<translate>
# The files and folders on your website, as hosted on most static HTML websites.</translate>

<translate>
If you do not backup your files and database, your backup is incomplete.</translate>

<translate>
=== Database Backup === 
</translate>

<translate>
One of the first steps to backup your Joomla site is to close the site to the public, backup the files and then re-open the site. The steps from [https://docs.phpmyadmin.net/en/latest/index.html the phpMyAdmin documentation] omit this much needed operation. Go to {{rarr|Joomla Administrator,Global Configuration,Site}} tab, set ''Site Offline'' = 'Yes''.</translate>

<translate>
This will then change the ''configuration.php'' file in the root of your Joomla website.</translate>

<translate>
An administrator will need to use your hosting control panel to view that file or use FTP to download and view the file. Inside the ''configuration.php'' file you can find the name of your database that will need backing up.</translate>

<translate>
Look for the line with code resembling <code>var $db = 'x1234';</code> or <code>public $db = 'x1234';</code> Where ''x1234'' is the name of your database.</translate>

<translate>
Using the logon information for your server or hosting company open the phpMyAdmin tool. Open the database and look for the table named ''users'' and then click the icon to ''view'' the data in that table.</translate>

<translate>
You should see the names of staff who have accounts on your Joomla site. This view provides you the confidence that you are about to backup the correct database.</translate>

<translate>
Click the ''export'' tab, then ''Go''.</translate>

<translate>
Your browser will download your database into an SQL file.</translate>

<translate>
Find where you browser put that file, then move the file to a much more secure drive or location.</translate>

<translate>
Server SQL databases can be backed up without phpMyAdmin and instead using the SQL command line. If you know how to do that, you're most likely not in need of this documentation.</translate>

<translate>
It is recommended that you back up the database at least twice per week or even everyday (and more) if you have an active site.</translate>

<translate>=== File System Backup === </translate>

<translate>
Continue with your site offline, see above. Your Joomla folder and files can be backed up by downloading them with an FTP utility or using the file manager of your web hosting company. Both of these file options work, neither is better.</translate>

<translate>
FTP tools move thousands of Joomla files and use more time. The FTP process can be slow and interrupted. Most hosting companies provide a control panel for taking thousands of files in one folder and then creating a zip file very quickly.</translate>

<translate>
This means your site is offline for a shorter amount of time and you have only one zip file. Go to your hosting control panel and look for their file manager icon.</translate>

<translate>
If you use your hosting file manager, practice using that interface to select your server folder and creating a zip file. Download the zip file locally and then expand it locally to to see what files are inside that zip file. This option also let's you expand the same zip file for restoration to a staging site.</translate>

<translate>
Backing up the Joomla files with FTP is no different than backing up a static HTML website. Download all the files and folders that exist in the main Joomla directory. The downloaded location is a folder on your local computer. Be sure that the file and directory structure remains the same as it is in the live site. When you restore the files, you will use the FTP utility to upload the files to a new server.</translate>

<translate>
'''As soon as you've downloaded your files, via zip or FTP, change your site to be online.'''</translate>

<translate>
== More Backup Documentation == 
</translate>

<translate>
Most administrators of a Joomla website have access to their MySQL data using the GUI interface called phpMyAdmin, see [https://docs.phpmyadmin.net/en/latest/faq.html#how-can-i-backup-my-database-or-table How can I backup my database or table?] for more information.</translate>

<translate>
There are several automated backup extensions for Joomla! located in the [https://extensions.joomla.org/ Joomla! Extensions Directory]. Here is a link for [https://extensions.joomla.org/extension/?searchall=backup&controller=filter Joomla! Backup Extensions].</translate>

<translate>
When servers are hosted in the same building as the staff, the web administrators should make extra care to store the backup copies of the database and files in a different building. Fire, theft, water or other damage often wipes out the live website '''and''' backups. On a regular basis the web administrators should burn both the database and files to a CD or save to an external hard drive off site.</translate>

<translate>
== Special Notes == 
</translate>

<translate>
=== Two Factor Authentication (2FA) === 
</translate>

<translate>
If you use two factor authentication (available since Aug 2014) and you are locked out of your site, you can rename the folder ''plugins/twofactorauth'' to ''twofactorauth.BAK'' and log in to your site's back-end. Then disable all plugins under the ''twofactorauth'' group. Finally, rename the ''plugins/twofactorauth.BAK'' folder of your site to ''twofactorauth''.</translate>
<translate>
*See also the [[S:MyLanguage/J3.x:Two_Factor_Authentication|Two Factor Authentication]] tutorial.</translate>

<noinclude>
<translate>

[[Category:Tutorials]]
[[Category:Security]]
[[Category:Incoming External Link]]
</translate>
</noinclude>

Backup Basics for a Joomla! Web Site

2020-08-20T23:46:55Z

Topazgb:

<noinclude><languages /></noinclude>
<translate>
Always keep a recent backup of your site. Accidents happen, but there are many other reasons to have your backup files handy before the need arises. '''N.B. backups should not be used to restore a hacked site because the hack could have been on the site for some time could have been backed up with the site.'''</translate>

<translate>
The causes of data loss are many. Joomla sites can be compromised by malicious attackers if the site administrator has not paid attention to security or in cases when hackers bypass the best security. Joomla! is designed for teamwork, and even good editors can make an error that harms the site.</translate>

<translate>
There are many reasons website administrators need to revert the site to a previous working state.</translate>

<translate>
Practice both backup and restore. Nobody should wait for an emergency to test their skills and tools for dealing with an emergency. Very often people create a backup of something that is empty or corrupted and discover that none of their critical data was backed up. Nobody likes a ship that sinks with empty lifeboats. It's also wise to practice getting people out of the lifeboats and into a new working system.</translate>

<translate>
Having a backup is not just about accidents; a person well versed in backup can help with safe development of new features. Backup and restore help web managers create a staging website where new changes can be practiced without risking the production website. The clone can be created on a local machine acting as a test server or any other folder or web hosting account supporting the SQL and PHP versions used by the site you've backed up.</translate>

<translate>
It's easy for anyone to mix up their live site and staging site, so change the color of your staging site template to remind developers that the staging site is not live to the public.</translate>

<translate>
== Back Up a Joomla Website Using Akeeba == 
</translate>

<translate>
This is the preferred method using the Akeeba Backup Extension. (Common method)</translate>
<translate>
* Akeeba Backup produces a ''.jpa'' file.</translate>
<translate>
* The compressed ''.jpa'' file contains all the Website's files and the content of the database.</translate>
<translate>
* The ''.jpa'' file also includes an installer.</translate>
<translate>
* Akeeba's ''kickstart.php'' unpacks the ''.jpa'' file.</translate>
<translate>
* You then run the installer and install your site like a Joomla install.</translate>
<translate>
* The installer changes the configuration for restoring to a different location and prompts for the new database details.</translate>

<translate>
You can download the Akeeba Backup extension from the [https://extensions.joomla.org/extensions/extension/access-a-security/site-security/akeeba-backup/ Joomla extension directory]. There is a link to full instructions there as well.</translate>

<translate>

== Backup Two-Part Method == 
</translate>

<translate>
There are two parts to a complete back up of your Joomla site. They are:</translate>

<translate>
# The database information, most often found in your MySQL database.</translate>
<translate>
# The files and folders on your website, as hosted on most static HTML websites.</translate>

<translate>
If you do not backup your files and database, your backup is incomplete.</translate>

<translate>
=== Database Backup === 
</translate>

<translate>
One of the first steps to backup your Joomla site is to close the site to the public, backup the files and then re-open the site. The steps from [https://docs.phpmyadmin.net/en/latest/index.html the phpMyAdmin documentation] omit this much needed operation. Go to {{rarr|Joomla Administrator,Global Configuration,Site}} tab, set ''Site Offline'' = 'Yes''.</translate>

<translate>
This will then change the ''configuration.php'' file in the root of your Joomla website.</translate>

<translate>
An administrator will need to use your hosting control panel to view that file or use FTP to download and view the file. Inside the ''configuration.php'' file you can find the name of your database that will need backing up.</translate>

<translate>
Look for the line with code resembling <code>var $db = 'x1234';</code> or <code>public $db = 'x1234';</code> Where ''x1234'' is the name of your database.</translate>

<translate>
Using the logon information for your server or hosting company open the phpMyAdmin tool. Open the database and look for the table named ''users'' and then click the icon to ''view'' the data in that table.</translate>

<translate>
You should see the names of staff who have accounts on your Joomla site. This view provides you the confidence that you are about to backup the correct database.</translate>

<translate>
Click the ''export'' tab, then ''Go''.</translate>

<translate>
Your browser will download your database into an SQL file.</translate>

<translate>
Find where you browser put that file, then move the file to a much more secure drive or location.</translate>

<translate>
Server SQL databases can be backed up without phpMyAdmin and instead using the SQL command line. If you know how to do that, you're most likely not in need of this documentation.</translate>

<translate>
It is recommended that you back up the database at least twice per week or even everyday (and more) if you have an active site.</translate>

<translate>=== File System Backup === </translate>

<translate>
Continue with your site offline, see above. Your Joomla folder and files can be backed up by downloading them with an FTP utility or using the file manager of your web hosting company. Both of these file options work, neither is better.</translate>

<translate>
FTP tools move thousands of Joomla files and use more time. The FTP process can be slow and interrupted. Most hosting companies provide a control panel for taking thousands of files in one folder and then creating a zip file very quickly.</translate>

<translate>
This means your site is offline for a shorter amount of time and you have only one zip file. Go to your hosting control panel and look for their file manager icon.</translate>

<translate>
If you use your hosting file manager, practice using that interface to select your server folder and creating a zip file. Download the zip file locally and then expand it locally to to see what files are inside that zip file. This option also let's you expand the same zip file for restoration to a staging site.</translate>

<translate>
Backing up the Joomla files with FTP is no different than backing up a static HTML website. Download all the files and folders that exist in the main Joomla directory. The downloaded location is a folder on your local computer. Be sure that the file and directory structure remains the same as it is in the live site. When you restore the files, you will use the FTP utility to upload the files to a new server.</translate>

<translate>
'''As soon as you've downloaded your files, via zip or FTP, change your site to be online.'''</translate>

<translate>
== More Backup Documentation == 
</translate>

<translate>
Most administrators of a Joomla website have access to their MySQL data using the GUI interface called phpMyAdmin, see [https://docs.phpmyadmin.net/en/latest/faq.html#how-can-i-backup-my-database-or-table How can I backup my database or table?] for more information.</translate>

<translate>
There are several automated backup extensions for Joomla! located in the [https://extensions.joomla.org/ Joomla! Extensions Directory]. Here is a link for [https://extensions.joomla.org/extension/?searchall=backup&controller=filter Joomla! Backup Extensions].</translate>

<translate>
When servers are hosted in the same building as the staff, the web administrators should make extra care to store the backup copies of the database and files in a different building. Fire, theft, water or other damage often wipes out the live website '''and''' backups. On a regular basis the web administrators should burn both the database and files to a CD or save to an external hard drive off site.</translate>

<translate>
== Special Notes == 
</translate>

<translate>
=== Two Factor Authentication (2FA) === 
</translate>

<translate>
If you use two factor authentication (available since Aug 2014) and you are locked out of your site, you can rename the folder ''plugins/twofactorauth'' to ''twofactorauth.BAK'' and log in to your site's back-end. Then disable all plugins under the ''twofactorauth'' group. Finally, rename the ''plugins/twofactorauth.BAK'' folder of your site to ''twofactorauth''.</translate>
<translate>
*See also the [[S:MyLanguage/J3.x:Two_Factor_Authentication|Two Factor Authentication]] tutorial.</translate>

<noinclude>
<translate>

[[Category:Tutorials]]
[[Category:Security]]
[[Category:Incoming External Link]]
</translate>
</noinclude>

Backup Basics for a Joomla! Web Site

2020-08-20T17:44:57Z

Topazgb: added warning about restoring a hacked site

<noinclude><languages /></noinclude>
<translate>
Always keep a recent backup of your site. Accidents happen, but there are many other reasons to have your backup files handy before the need arises. '''N.B. backups should not be used to restore a hacked site because the hack could have been on the site for some time could have been backed up with the site.'''</translate>

<translate>
The causes of data loss are many. Joomla sites can be compromised by malicious attackers if the site administrator has not paid attention to security or in cases when hackers bypass the best security. Joomla! is designed for teamwork, and even good editors can make an error that harms the site.</translate>

<translate>
There are many reasons website administrators need to revert the site to a previous working state.</translate>

<translate>
Practice both backup and restore. Nobody should wait for an emergency to test their skills and tools for dealing with an emergency. Very often people create a backup of something that is empty or corrupted and discover that none of their critical data was backed up. Nobody likes a ship that sinks with empty lifeboats. It's also wise to practice getting people out of the lifeboats and into a new working system.</translate>

<translate>
Having a backup is not just about accidents; a person well versed in backup can help with safe development of new features. Backup and restore help web managers create a staging website where new changes can be practiced without risking the production website. The clone can be created on a local machine acting as a test server or any other folder or web hosting account supporting the SQL and PHP versions used by the site you've backed up.</translate>

<translate>
It's easy for anyone to mix up their live site and staging site, so change the color of your staging site template to remind developers that the staging site is not live to the public.</translate>

<translate>
==Backing up a Joomla Website (Common Method)== 
</translate>

<translate>
=== Akeeba === 
</translate>

<translate>
* Akeeba Backup produces a ''.jpa'' file.</translate>
<translate>
* The ''.jpa'' file contains all the folders/files and database files.</translate>
<translate>
* The ''.jpa'' file also contains an installer.</translate>
<translate>
* Akeeba's ''kickstart.php'' unpacks the ''.jpa'' file.</translate>
<translate>
* You then run the installer and install your site like a Joomla install.</translate>
<translate>
* The installer changes the configuration for restoring to a different location and prompts for the new database details.</translate>

<translate>
After you create the Database for your Joomla download and install Akeeba, it can be download from [https://extensions.joomla.org/extensions/extension/access-a-security/site-security/akeeba-backup/ Joomla extension directory]. There is a link to full instructions there as well.</translate>

<translate>
== Two part method == 
</translate>

<translate>
There are two parts to a complete back up of your Joomla site. They are:</translate>

<translate>
# The database information, most often found in your MySQL database.</translate>
<translate>
# The files and folders on your website, as hosted on most static HTML websites.</translate>

<translate>
If you do not backup your files and database, your backup is incomplete.</translate>

<translate>
=== Database Backup—Part 1 === 
</translate>

<translate>
One of the first steps to backup your Joomla site is to close the site to the public, backup the files, and then re-open the site. The steps from phpmyadmin.net omit this much needed operation. Go to the backend of your Joomla control panel, under global configuration, under the site tab, set "site offline" = yes.</translate>

<translate>
This will then change the look of your ''configuration.php'' file in the root of your Joomla website.</translate>

<translate>
An administrator will need to use your hosting control panel to view that file or use FTP to download and view the file. Inside the ''configuration.php'' file you can find the name of your database that will need backing up.</translate>

<translate>
Look for the line with code resembling <code>var $db = 'x1234';</code> or <code>public $db = 'x1234';</code> Where ''x1234'' is the name of your database.</translate>

<translate>
Using the logon information for your server or hosting company open the PhpMyAdmin tool. Open the database and look for the table named "users" and then click the icon to "view" the data in that table.</translate>

<translate>
You should see the names of staff who have accounts on your Joomla site. This view provides you the confidence that you are about to backup the correct database.</translate>

<translate>
Click the export tab, then go.</translate>

<translate>
Your browser will download your database into an SQL file.</translate>

<translate>
Find where you browser put that file, then move the file to a much more secure drive or location.</translate>

<translate>
Server SQL databases can be backed up without PhpMyAdmin and instead using the SQL command line. If you know how to do that, you're most likely not in need of this documentation.</translate>

<translate>
It is recommended to back up the database at least twice per week or even everyday (and more) if you have an active site.</translate>

<translate>=== File System Backup—Part 2 === </translate>

<translate>
Continue with your site offline, see above. Your Joomla folder and files can be backed up by downloading them with an FTP utility or using the file manager of your web hosting company. Both of these file options work, neither is better.</translate>

<translate>
FTP tools move thousands of Joomla files and use more time. The FTP process can be slow and interrupted. Most hosting companies provide a control panel for taking thousands of files in one folder and then creating a zip file very quickly.</translate>

<translate>
This means your site is offline for a shorter amount of time, and you have only one zip file. Go to your hosting control panel and look for their file manager icon.</translate>

<translate>
If you use your hosting file manager, practice using that interface to select your server folder and creating a zip file. Download the zip file locally and then expand it locally to to see what files are inside that zip file. This option also let's you expand the same zip file for restoration to a staging site.</translate>

<translate>
Backing up the Joomla files with FTP is no different than backing up a static HTML website. Download all the files and folders that exist in the main Joomla directory. The downloaded location is a folder on your local computer. Be sure that the file and directory structure remains the same as it is in the live site. When you restore the files, you will use the FTP utility to upload the files to a new server.</translate>

<translate>
'''As soon as you've downloaded your files via zip or FTP, change your site to be online.'''</translate>

<translate>
== More Backup Documentation == 
</translate>

<translate>
Most administrators of a Joomla website have access to their MySQL data using the GUI interface called PhpMyAdmin, see [https://phpmyadmin.readthedocs.org/en/latest/faq.html#how-can-i-backup-my-database-or-table How can I backup my database or table?] for more information.</translate>

<translate>
There are several automated backup extensions for Joomla! located in the [http://extensions.joomla.org Joomla! Extensions Directory]. Here is a link for [http://extensions.joomla.org/extensions/extension?searchall=backup&controller=filter Joomla! Backup Extensions].</translate>

<translate>
When servers are hosted in the same building as the staff, the web administrators should make extra care to store the backup copies of the database/files in a different building. Fire, theft, water or other damage often wipes out the live website AND backups. On a regular basis the web administrators should burn both the database and files to CD or save to an external hard drive off site.</translate>

<translate>
==Special Notes== 
</translate>

<translate>
=== Two Factor Authentication (2FA) === 
</translate>

<translate>
If you use two factor authentication (available since Aug 2014) and you are locked out of your site, you can rename the folder plugins/twofactorauth to twofactorauth.BAK and log in to your site's back-end. Then disable all plugins under the ''twofactorauth'' group. Finally, rename the plugins/twofactorauth.BAK folder of your site back to twofactorauth.</translate>
<translate>
*See also: [[S:MyLanguage/J3.x:Two_Factor_Authentication|Tutorial Two Factor Authentication]]</translate>

<translate>
=== Automated Backup Tools === 
</translate>

<translate>
==== Akeeba ==== 
</translate>

<translate>
* Akeeba Backup produces a ''.jpa'' file that you should download to a safe location that's not on your webhost or webserver.</translate>
<translate>
* The ''.jpa'' file contains all the folders/files and database files.</translate>
<translate>
* The ''.jpa'' file also contains an installer</translate>

<translate>
These paragraphs are about backup, but it's worth a quick note that the Akeeba restore process is a fast guided process similar to a setup wizard.</translate>

<translate>
Place two files on a new webhost.</translate>

<translate>
a) your ''.jpa'' file and b) Akeeba's ''kickstart.php'' program.</translate>

<translate>
You then use a browser to launch the restore process and unpack the ''.jpa'' file.</translate>

<translate>
Please read the Akeeba restore documentation.</translate>

<translate>
Akeeba and other backup extensions can be downloaded from the [https://extensions.joomla.org/extensions/extension?search=backup JED]</translate>

<noinclude>
<translate>

[[Category:Tutorials]]
[[Category:Security]]
[[Category:Incoming External Link]]
</translate>
</noinclude>

Split menus

2020-07-24T18:29:29Z

Topazgb: Added link

<noinclude><languages /></noinclude>
<translate>

{{Chunk:Split menus/en}}

===Further information=== 
* [[J3.x:Creating_a_submenu|Creating a submenu]]


[[Category:Landing Pages]][[Category:Glossary]]
</translate>

Talk:Updating Joomla (Manual Method)

2020-06-04T13:37:54Z

Topazgb:

This method is Obsolete and (in many case) can break a site.
--Topazgb 06:16, 23 September 2018 (CDT)

--[[User:Sozzled|Sozzled]] ([[User talk:Sozzled|talk]]) 19:28, 2 June 2020 (CDT)

Please remove this article. It is confusing to novice users. There is no "supported" method to "manually" update J! 3.''x''.

{{deprecated|1.0}}

--Topazgb 08:37, 4 June 2020 (CDT)
Yep was obsolete at least 2 years ago

Help310:Content Article Manager

2019-11-28T23:25:23Z

Topazgb: English title got defaced

<noinclude><languages /></noinclude>

<translate>
==Description== </translate>
<translate>
The Article Manager is used to find, mark featured, add and edit articles. </translate>

<translate>
==How to access== </translate>
<translate>
*Click the Articles icon in the [[S:MyLanguage/Help30:Site_Control_Panel|Control Panel]]</translate>
<translate>
*Select {{rarr|Content,Articles}} from the drop-down menu of the '''''Joomla! Administrator Panel'''''.</translate>
<translate>
*Click the '''Articles''' link while viewing [[S:MyLanguage/Help30:Components Content Categories|Categories]], [[S:MyLanguage/Help30:Content_Featured_Articles|Featured Articles]] or another link in the sidebar.</translate>

<translate>
==Screenshot== </translate>
[[Image:Help30-Content-Article-Manager-screen-<translate>
en</translate>.png|800px|Article Manager]]

<translate>
==Column Headers== 
</translate>
<translate>

In the table containing Articles, these are the different columns shown below.</translate>
[[File:Help30-Article-Manager-columns-<translate>
en</translate>.png|800px|Article Columns Header]]{{-}}
{{Chunk30:colheader|Ordering/<translate>
en</translate>}}
{{Chunk30:colheader|Checkbox/<translate>
en</translate>}}
{{Chunk30:colheader|Status-Feature/<translate>
en</translate>}}
{{Chunk30:colheader|Title/<translate>
en</translate>}}
{{Chunk30:colheader|Access/<translate>
en</translate>}}
{{Chunk30:colheader|Author/<translate>
en</translate>}}
{{Chunk30:colheader|Language/<translate>
en</translate>}}
{{Chunk30:colheader|Date/<translate>
en</translate>}}
{{Chunk30:colheader|Hits/<translate>

en</translate>}}
{{Chunk30:colheader|Votes/<translate>

en</translate>}}
{{Chunk30:colheader|Ratings/<translate>

en</translate>}}
{{Chunk30:colheader|Id/<translate>
en</translate>}}

<translate>
=== Column Filters === 
</translate>
{{Chunk30:Column_Filtering_Sort_Number/<translate> en</translate>|ID descending}}
[[Image:Help30-colheader-Column-filter-id-descending-number-<translate>
en</translate>.png]]{{-}}
{{Chunk30:Column_Filtering_Sort_Number_Description/<translate> en</translate>}}
{{Chunk30:colheader|Order/<translate>
en</translate>}}
{{Chunk30:colheader|Ascending/<translate>
en</translate>}}
{{Chunk30:colheader|DisplayNum/<translate>
en</translate>}}

<translate>

==List Filters== 
</translate>
<translate>
The '''List Filters''', above on the left, and other filters as detailed below are in the left, bottom sidebar. These filters are a series of controls that let you limit what items show in the manager screen. More than one filter may be entered. In this case, only items that meet all of the filter conditions will show on the list.</translate>

{{Chunk30:colheader|List Filter/<translate>
en</translate>}}
{{Chunk30:colheader|Select Status/<translate>
en</translate>}}
{{Chunk30:colheader|Select Category/<translate>
en</translate>}}
{{Chunk30:colheader|Select Access/<translate>
en</translate>}}
{{Chunk30:colheader|Select Author/<translate>
en</translate>}}
{{Chunk30:colheader|Select Language/<translate>
en</translate>}}
{{Chunk30:colheader|Select Tags/<translate>

en</translate>}}
{{Chunk30:colheader|Select Max Levels/<translate>
en</translate>}}
{{Chunk30:colheader|Manager Pagination/<translate>
en</translate>}}

<translate>
==Toolbar== 
</translate>
<translate>

At the top you will see the toolbar:</translate>

[[Image:Help30-New-Edit-Publish-Unpublish-Featured-Archive-Checkin-Trash-Batch-Options-Help-toolbar-<translate>
en</translate>.png]]

<translate>

The functions are:</translate>
{{Chunk30:Help_screen_toolbar_icon_New/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Edit/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Publish/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Unpublish/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Featured/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Unfeature/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Archive/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Checkin/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Batch/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Trash/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Help/<translate>
en</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Options/<translate>
en</translate>}}

<translate>=== Batch Process ===
</translate>
{{Chunk30:Help_screen_column_header_Batch_Process_Articles/<translate>en</translate>}}

<translate>
==Custom Fields== 
</translate>
<translate>

If you want to know how to use Custom Fields, click [[S:MyLanguage/J3.x:Adding_custom_fields|Adding Custom Fields]]</translate>
<translate>
==Quick Tips== 
</translate>
<translate>
* If Joomla is installed without sample data, one article category called "Uncategorised" is created automatically. If you want to use other categories for articles, you should create them before trying to add articles.</translate>
<translate>
* To see trashed and archived articles, set the Status filter to All.</translate>
<translate>
* To change the ordering of articles within a category, click on the Ordering column heading to sort by this column. Also, it is easier to see the ordering if you filter on the desired category.</translate>

<translate>
==Related Information== 
</translate>
<translate>
* To add or edit Articles: [[S:MyLanguage/Help30:Content_Article_Manager_Edit|Article Manager: New/Edit]]</translate>
<translate>
* To manage Categories: [[S:MyLanguage/Help30:Components_Content_Categories|Category Manager]]</translate>
<translate>
* To manage Featured Articles: [[S:MyLanguage/Help30:Content_Featured_Articles|Article Manager: Featured Articles]]</translate>

{{cathelp|3.0,3.1,3.2,3.3,3.4,3.5,3.6,3.7,3.8,3.9|Article Manager Help Screens|Content Help Screens}}

Help310:Content Article Manager

2019-11-28T23:18:44Z

Topazgb: Undo revision 643920 by Topazgb (talk)

<noinclude><languages /></noinclude>

<translate>
==Okunyonyola== </translate>
<translate>
Waano tugenda okukulaga bwonyinza okusobola oku wandika , ekiwandiiko nokuchichusamu </translate>

<translate>
==How to access== </translate>
<translate>
*Click the Articles icon in the [[S:MyLanguage/Help30:Site_Control_Panel|Control Panel]]</translate>
<translate>
*Select {{rarr|Content,Articles}} from the drop-down menu of the '''''Joomla! Administrator Panel'''''.</translate>
<translate>
*Click the '''Articles''' link while viewing [[S:MyLanguage/Help30:Components Content Categories|Categories]], [[S:MyLanguage/Help30:Content_Featured_Articles|Featured Articles]] or another link in the sidebar.</translate>

<translate>
==Screenshot== </translate>
[[Image:Help30-Content-Article-Manager-screen-<translate>
en</translate>.png|800px|Article Manager]]

<translate>
==Column Headers== 
</translate>
<translate>

In the table containing Articles, these are the different columns shown below.</translate>
[[File:Help30-Article-Manager-columns-<translate>
en</translate>.png|800px|Article Columns Header]]{{-}}
{{Chunk30:colheader|Ordering/<translate>
en</translate>}}
{{Chunk30:colheader|Checkbox/<translate>
en</translate>}}
{{Chunk30:colheader|Status-Feature/<translate>
en</translate>}}
{{Chunk30:colheader|Title/<translate>
en</translate>}}
{{Chunk30:colheader|Access/<translate>
en</translate>}}
{{Chunk30:colheader|Author/<translate>
en</translate>}}
{{Chunk30:colheader|Language/<translate>
en</translate>}}
{{Chunk30:colheader|Date/<translate>
en</translate>}}
{{Chunk30:colheader|Hits/<translate>

en</translate>}}
{{Chunk30:colheader|Votes/<translate>

en</translate>}}
{{Chunk30:colheader|Ratings/<translate>

en</translate>}}
{{Chunk30:colheader|Id/<translate>
en</translate>}}

<translate>
=== Column Filters === 
</translate>
{{Chunk30:Column_Filtering_Sort_Number/<translate> en</translate>|ID descending}}
[[Image:Help30-colheader-Column-filter-id-descending-number-<translate>
en</translate>.png]]{{-}}
{{Chunk30:Column_Filtering_Sort_Number_Description/<translate> en</translate>}}
{{Chunk30:colheader|Order/<translate>
en</translate>}}
{{Chunk30:colheader|Ascending/<translate>
en</translate>}}
{{Chunk30:colheader|DisplayNum/<translate>
en</translate>}}

<translate>

==List Filters== 
</translate>
<translate>
The '''List Filters''', above on the left, and other filters as detailed below are in the left, bottom sidebar. These filters are a series of controls that let you limit what items show in the manager screen. More than one filter may be entered. In this case, only items that meet all of the filter conditions will show on the list.</translate>

{{Chunk30:colheader|List Filter/<translate>
en</translate>}}
{{Chunk30:colheader|Select Status/<translate>
en</translate>}}
{{Chunk30:colheader|Select Category/<translate>
en</translate>}}
{{Chunk30:colheader|Select Access/<translate>
en</translate>}}
{{Chunk30:colheader|Select Author/<translate>
en</translate>}}
{{Chunk30:colheader|Select Language/<translate>
en</translate>}}
{{Chunk30:colheader|Select Tags/<translate>

en</translate>}}
{{Chunk30:colheader|Select Max Levels/<translate>
en</translate>}}
{{Chunk30:colheader|Manager Pagination/<translate>
en</translate>}}

<translate>
==Toolbar== 
</translate>
<translate>

At the top you will see the toolbar:</translate>

[[Image:Help30-New-Edit-Publish-Unpublish-Featured-Archive-Checkin-Trash-Batch-Options-Help-toolbar-<translate>
en</translate>.png]]

<translate>

The functions are:</translate>
{{Chunk30:Help_screen_toolbar_icon_New/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Edit/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Publish/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Unpublish/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Featured/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Unfeature/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Archive/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Checkin/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Batch/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Trash/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Help/<translate>
en</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Options/<translate>
en</translate>}}

<translate>=== Batch Process ===
</translate>
{{Chunk30:Help_screen_column_header_Batch_Process_Articles/<translate>en</translate>}}

<translate>
==Custom Fields== 
</translate>
<translate>

If you want to know how to use Custom Fields, click [[S:MyLanguage/J3.x:Adding_custom_fields|Adding Custom Fields]]</translate>
<translate>
==Quick Tips== 
</translate>
<translate>
* If Joomla is installed without sample data, one article category called "Uncategorised" is created automatically. If you want to use other categories for articles, you should create them before trying to add articles.</translate>
<translate>
* To see trashed and archived articles, set the Status filter to All.</translate>
<translate>
* To change the ordering of articles within a category, click on the Ordering column heading to sort by this column. Also, it is easier to see the ordering if you filter on the desired category.</translate>

<translate>
==Related Information== 
</translate>
<translate>
* To add or edit Articles: [[S:MyLanguage/Help30:Content_Article_Manager_Edit|Article Manager: New/Edit]]</translate>
<translate>
* To manage Categories: [[S:MyLanguage/Help30:Components_Content_Categories|Category Manager]]</translate>
<translate>
* To manage Featured Articles: [[S:MyLanguage/Help30:Content_Featured_Articles|Article Manager: Featured Articles]]</translate>

{{cathelp|3.0,3.1,3.2,3.3,3.4,3.5,3.6,3.7,3.8,3.9|Article Manager Help Screens|Content Help Screens}}

Help310:Content Article Manager

2019-11-28T23:17:05Z

Topazgb: Undo revision 636198 by Matynjr (talk)

<noinclude><languages /></noinclude>

<translate>
==Description== </translate>
<translate>
Waano tugenda okukulaga bwonyinza okusobola oku wandika , ekiwandiiko nokuchichusamu </translate>

<translate>
==How to access== </translate>
<translate>
*Click the Articles icon in the [[S:MyLanguage/Help30:Site_Control_Panel|Control Panel]]</translate>
<translate>
*Select {{rarr|Content,Articles}} from the drop-down menu of the '''''Joomla! Administrator Panel'''''.</translate>
<translate>
*Click the '''Articles''' link while viewing [[S:MyLanguage/Help30:Components Content Categories|Categories]], [[S:MyLanguage/Help30:Content_Featured_Articles|Featured Articles]] or another link in the sidebar.</translate>

<translate>
==Screenshot== </translate>
[[Image:Help30-Content-Article-Manager-screen-<translate>
en</translate>.png|800px|Article Manager]]

<translate>
==Column Headers== 
</translate>
<translate>

In the table containing Articles, these are the different columns shown below.</translate>
[[File:Help30-Article-Manager-columns-<translate>
en</translate>.png|800px|Article Columns Header]]{{-}}
{{Chunk30:colheader|Ordering/<translate>
en</translate>}}
{{Chunk30:colheader|Checkbox/<translate>
en</translate>}}
{{Chunk30:colheader|Status-Feature/<translate>
en</translate>}}
{{Chunk30:colheader|Title/<translate>
en</translate>}}
{{Chunk30:colheader|Access/<translate>
en</translate>}}
{{Chunk30:colheader|Author/<translate>
en</translate>}}
{{Chunk30:colheader|Language/<translate>
en</translate>}}
{{Chunk30:colheader|Date/<translate>
en</translate>}}
{{Chunk30:colheader|Hits/<translate>

en</translate>}}
{{Chunk30:colheader|Votes/<translate>

en</translate>}}
{{Chunk30:colheader|Ratings/<translate>

en</translate>}}
{{Chunk30:colheader|Id/<translate>
en</translate>}}

<translate>
=== Column Filters === 
</translate>
{{Chunk30:Column_Filtering_Sort_Number/<translate> en</translate>|ID descending}}
[[Image:Help30-colheader-Column-filter-id-descending-number-<translate>
en</translate>.png]]{{-}}
{{Chunk30:Column_Filtering_Sort_Number_Description/<translate> en</translate>}}
{{Chunk30:colheader|Order/<translate>
en</translate>}}
{{Chunk30:colheader|Ascending/<translate>
en</translate>}}
{{Chunk30:colheader|DisplayNum/<translate>
en</translate>}}

<translate>

==List Filters== 
</translate>
<translate>
The '''List Filters''', above on the left, and other filters as detailed below are in the left, bottom sidebar. These filters are a series of controls that let you limit what items show in the manager screen. More than one filter may be entered. In this case, only items that meet all of the filter conditions will show on the list.</translate>

{{Chunk30:colheader|List Filter/<translate>
en</translate>}}
{{Chunk30:colheader|Select Status/<translate>
en</translate>}}
{{Chunk30:colheader|Select Category/<translate>
en</translate>}}
{{Chunk30:colheader|Select Access/<translate>
en</translate>}}
{{Chunk30:colheader|Select Author/<translate>
en</translate>}}
{{Chunk30:colheader|Select Language/<translate>
en</translate>}}
{{Chunk30:colheader|Select Tags/<translate>

en</translate>}}
{{Chunk30:colheader|Select Max Levels/<translate>
en</translate>}}
{{Chunk30:colheader|Manager Pagination/<translate>
en</translate>}}

<translate>
==Toolbar== 
</translate>
<translate>

At the top you will see the toolbar:</translate>

[[Image:Help30-New-Edit-Publish-Unpublish-Featured-Archive-Checkin-Trash-Batch-Options-Help-toolbar-<translate>
en</translate>.png]]

<translate>

The functions are:</translate>
{{Chunk30:Help_screen_toolbar_icon_New/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Edit/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Publish/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Unpublish/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Featured/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Unfeature/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Archive/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Checkin/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Batch/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Trash/<translate>
en</translate>|<translate>
article</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Help/<translate>
en</translate>}}
{{Chunk30:Help_screen_toolbar_icon_Options/<translate>
en</translate>}}

<translate>=== Batch Process ===
</translate>
{{Chunk30:Help_screen_column_header_Batch_Process_Articles/<translate>en</translate>}}

<translate>
==Custom Fields== 
</translate>
<translate>

If you want to know how to use Custom Fields, click [[S:MyLanguage/J3.x:Adding_custom_fields|Adding Custom Fields]]</translate>
<translate>
==Quick Tips== 
</translate>
<translate>
* If Joomla is installed without sample data, one article category called "Uncategorised" is created automatically. If you want to use other categories for articles, you should create them before trying to add articles.</translate>
<translate>
* To see trashed and archived articles, set the Status filter to All.</translate>
<translate>
* To change the ordering of articles within a category, click on the Ordering column heading to sort by this column. Also, it is easier to see the ordering if you filter on the desired category.</translate>

<translate>
==Related Information== 
</translate>
<translate>
* To add or edit Articles: [[S:MyLanguage/Help30:Content_Article_Manager_Edit|Article Manager: New/Edit]]</translate>
<translate>
* To manage Categories: [[S:MyLanguage/Help30:Components_Content_Categories|Category Manager]]</translate>
<translate>
* To manage Featured Articles: [[S:MyLanguage/Help30:Content_Featured_Articles|Article Manager: Featured Articles]]</translate>

{{cathelp|3.0,3.1,3.2,3.3,3.4,3.5,3.6,3.7,3.8,3.9|Article Manager Help Screens|Content Help Screens}}

Help310 talk:Content Article Manager

2019-11-28T22:31:29Z

Topazgb: Created page with "Top title says Okunyonyola Appears not to be translating it to English correctly --~~~~"

Top title says
Okunyonyola

Appears not to be translating it to English correctly
--Topazgb 16:31, 28 November 2019 (CST)

Backup Basics for a Joomla! Web Site

2019-07-09T18:22:28Z

Topazgb: Adjusted parra headings

<noinclude><languages /></noinclude>
<translate>
Always keep a recent backup of your site. Accidents happen, but there are many other reasons it helps to have your backup files handy before the need arises.</translate> 
<translate>
The causes of data loss are many. Joomla sites can be compromised by malicious attackers if the site administrator has not paid attention to security, or in rare cases when hackers bypass the best security. Joomla! is designed for teamwork, and even good editors can make an error to harm the site.</translate> 
<translate>
There are many reasons website administrators need to revert the site back to a previous working state.</translate>

<translate>
Practice both backup and restore. Nobody should wait for an emergency to test their skills and tools for dealing with an emergency. Very often people create a backup of something that is empty or corrupted, and discover that none of their critical data was really backed up in the first place. Nobody likes a ship that sinks with empty lifeboats, and it's also wise to practice getting people out of the lifeboats and into a new working system.</translate> 
<translate>
Having a backup is not just about accidents, because a person well versed in backup can help with safe development of new features. Backup and restore help web managers create a staging website where new changes can be practiced without risking the production website. The clone can be created on a local machine acting as a test server, or any other folder or web hosting account supporting the SQL and PHP versions used by the site you've backed up.</translate> 
<translate>
It's easy for anyone to mix up their live site and staging site, so change the color of your staging site template to remind developers that the staging site is not live to the public.</translate>

<translate>
==Backing up a Joomla website (common method)== 
</translate>

<translate>
==== Akeeba ==== 
</translate>

<translate>
* Akeeba Backup produces a .jpa file</translate>
<translate>
* The .jpa file contains all the folders/files and database files.</translate>
<translate>
* The .jpa file also contains an installer</translate>
<translate>
* Kickstart.php (from Akeeba) unpacks the .jpa file</translate>
<translate>
* You then run the installer and install your site like a Joomla install</translate>
<translate>
* The installer changes the configuration for restoring to a different location and prompts for the new database details.</translate>

<translate>
After you create the Database for your Joomla download and install Akeeba, it can be download from [https://extensions.joomla.org/extensions/extension/access-a-security/site-security/akeeba-backup/ Joomla extension directory]. There is a link to full instructions there as well.</translate>

<translate>
== Two part method == 
</translate>

<translate>
There are two parts to a complete back up of your Joomla site. They are:</translate>

<translate>
# The database information, most often found in your mysql database.</translate>
<translate>
# The files and folders on your website, as hosted on most static html websites.</translate>

<translate>
If you do not backup your files and database, your backup is incomplete.</translate>

<translate>
==== Database Backup Part 1 of 2 ==== 
</translate>

<translate>
One of the first steps to backup your Joomla site is to close the site to the public, backup the files, and then re-open the site. The steps from phpmyadmin.net omit this much needed operation. Go to the backend of your Joomla control panel, under global configuration, under the site tab, set "site offline" = yes.</translate> 
<translate>
This will then change the look of your configuration.php file in the root of your Joomla website.</translate> 
<translate>
An administrator will need to use your hosting control panel to view that file or use FTP to download and view the file. Inside configuration.php you can find the name of your database that will need backing up.</translate> 
<translate>
Look for the line with code resembling <code>var $db = 'x1234';</code> or <code>public $db = 'x1234';</code> Where ''x1234'' is the name of your database.</translate>

<translate>
Using the logon information for your server or hosting company open the PhpMyAdmin tool. Open the database and look for the table named "users" and then click the icon to "view" the data in that table.</translate> 
<translate>
You should see the names of staff who have accounts on your Joomla site. This view provides you the confidence that you are about to backup the correct database.</translate> 
<translate>
Click the export tab, then go.</translate> 
<translate>
Your browser will download your database into an SQL file.</translate> 
<translate>
Find where you browser put that file, then move the file to a much more secure drive or location.</translate>

<translate>
Server SQL databases can be backed up without PhpMyAdmin and instead using the SQL command line. If you know how to do that, you're most likely not in need of this documentation.</translate>

<translate>
It is recommended to back up the database at least twice per week or even everyday (and more) if you have an active site.</translate>

<translate>==== File System Backup Part 2 of 2 ==== </translate>

<translate>
Continue with your site offline, see above. Your joomla folder and files can be backed up by downloading them with an FTP utility or using the file manager of your webhosting company. Both of these file options work, neither is better.</translate>

<translate>
FTP tools move thousands of Joomla files and use more time. The FTP process can be slow and interrupted. Most hosting companies provide a control panel for taking thousands of files in one folder and then creating a zip file very quickly.</translate> 
<translate>
This means your site is offline for a shorter amount of time, and you have only one zip file. Go to your hosting control panel and look for their file manager icon.</translate>

<translate>
If you use your hosting file manager, practice using that interface to select your server folder and creating a zip file. Download the zip file locally and then expand it locally to to see what files are inside that zip file. This option also let's you expand the same zip file for restoration to a staging site.</translate>

<translate>
Backing up the Joomla files with FTP is no different than backing up a static HTML website. Download all the files and folders that exist in the main Joomla directory. The downloaded locaiton is a folder on your local computer. Be sure that the file and directory structure remains the same as it is in the live site. When you restore the files, you will use the FTP utility to upload the files to a new server.</translate>

<translate>
'''As soon as you've downloaded your files via zip or FTP, change your site to be online.'''</translate>

<translate>
== More Backup Documentation == 
</translate>

<translate>
Most administrators of a Joomla website have access to their MySQL data using the GUI interface called PhpMyAdmin, see [https://phpmyadmin.readthedocs.org/en/latest/faq.html#how-can-i-backup-my-database-or-table How can I backup my database or table?] for more information.</translate>

<translate>
There are several automated backup extensions for Joomla! located in the [http://extensions.joomla.org Joomla! Extensions Directory]. Here is a link for [http://extensions.joomla.org/extensions/extension?searchall=backup&controller=filter Joomla! Backup Extensions].</translate>

<translate>
When servers are hosted in the same building as the staff, the web administrators should make extra care to store the backup copies of the database/files in a different building. Fire, theft, water or other damage often wipes out the live website AND backups. On a regular basis the web administrators should burn both the database and files to CD or save to an external hard drive off site.</translate>

<translate>
==Special Notes== 
</translate>

<translate>
=== 2FA (Two factor authentication) === 
</translate>

<translate>
If you use 2 factor authentication (available since Aug 2014) and you are locked out of your site you can rename the folder plugins/twofactorauth to twofactorauth.BAK and log in to your site's back-end. Then disable all plugins under the "twofactorauth" group. Finally, rename the plugins/twofactorauth.BAK folder of your site back to twofactorauth.</translate>
<translate>
*See also: [[S:MyLanguage/J3.x:Two_Factor_Authentication|Tutorial Two Factor Authentication]]</translate>

<translate>
=== Automated Backup Tools === 
</translate>

<translate>
==== Akeeba ==== 
</translate>

<translate>
* Akeeba Backup produces a .jpa file that you should download to a safe location that's not on your webhost or webserver.</translate>
<translate>
* The .jpa file contains all the folders/files and database files.</translate>
<translate>
* The .jpa file also contains an installer</translate>

<translate>
These paragraphs are about backup, but it's worth a quick note that the Akeeba restore process is a fast guided process similar to a setup wizard.</translate> 
<translate>
Place 2 files on a new webhost.</translate> 
<translate>
a) your JPA file and b) Kickstart.php (from Akeeba)</translate> 
<translate>
You then use a browser to launch the restore process and unpack the .jpa file.</translate> 
<translate>
Please read the Akeeba restore documentation.</translate>

<translate>
Akeeba and other backup extensions can be downloaded from the [https://extensions.joomla.org/extensions/extension?search=backup JED]</translate>

<noinclude>
<translate>

[[Category:Tutorials]]
[[Category:Security]]
[[Category:Incoming External Link]]
</translate>
</noinclude>

Backup Basics for a Joomla! Web Site

2019-07-09T18:19:08Z

Topazgb: Added Akeeba common method

<noinclude><languages /></noinclude>
<translate>
Always keep a recent backup of your site. Accidents happen, but there are many other reasons it helps to have your backup files handy before the need arises.</translate> 
<translate>
The causes of data loss are many. Joomla sites can be compromised by malicious attackers if the site administrator has not paid attention to security, or in rare cases when hackers bypass the best security. Joomla! is designed for teamwork, and even good editors can make an error to harm the site.</translate> 
<translate>
There are many reasons website administrators need to revert the site back to a previous working state.</translate>

<translate>
Practice both backup and restore. Nobody should wait for an emergency to test their skills and tools for dealing with an emergency. Very often people create a backup of something that is empty or corrupted, and discover that none of their critical data was really backed up in the first place. Nobody likes a ship that sinks with empty lifeboats, and it's also wise to practice getting people out of the lifeboats and into a new working system.</translate> 
<translate>
Having a backup is not just about accidents, because a person well versed in backup can help with safe development of new features. Backup and restore help web managers create a staging website where new changes can be practiced without risking the production website. The clone can be created on a local machine acting as a test server, or any other folder or web hosting account supporting the SQL and PHP versions used by the site you've backed up.</translate> 
<translate>
It's easy for anyone to mix up their live site and staging site, so change the color of your staging site template to remind developers that the staging site is not live to the public.</translate>

<translate>
==Backing up a Joomla website (common method)== 
</translate>

<translate>
==== Akeeba ==== 
</translate>

<translate>
* Akeeba Backup produces a .jpa file</translate>
<translate>
* The .jpa file contains all the folders/files and database files.</translate>
<translate>
* The .jpa file also contains an installer</translate>
<translate>
* Kickstart.php (from Akeeba) unpacks the .jpa file</translate>
<translate>
* You then run the installer and install your site like a Joomla install</translate>
<translate>
* The installer changes the configuration for restoring to a different location and prompts for the new database details.</translate>

<translate>
After you create the Database for your Joomla download and install Akeeba, it can be download from [https://extensions.joomla.org/extensions/extension/access-a-security/site-security/akeeba-backup/ Joomla extension directory]. There is a link to full instructions there as well.</translate>

<translate>
== Two part method == 
</translate>

<translate>
There are two parts to a complete back up of your Joomla site. They are:</translate>

<translate>
# The database information, most often found in your mysql database.</translate>
<translate>
# The files and folders on your website, as hosted on most static html websites.</translate>

<translate>
If you do not backup your files and database, your backup is incomplete.</translate>

<translate>
== Database Backup Part 1 of 2 == 
</translate>

<translate>
One of the first steps to backup your Joomla site is to close the site to the public, backup the files, and then re-open the site. The steps from phpmyadmin.net omit this much needed operation. Go to the backend of your Joomla control panel, under global configuration, under the site tab, set "site offline" = yes.</translate> 
<translate>
This will then change the look of your configuration.php file in the root of your Joomla website.</translate> 
<translate>
An administrator will need to use your hosting control panel to view that file or use FTP to download and view the file. Inside configuration.php you can find the name of your database that will need backing up.</translate> 
<translate>
Look for the line with code resembling <code>var $db = 'x1234';</code> or <code>public $db = 'x1234';</code> Where ''x1234'' is the name of your database.</translate>

<translate>
Using the logon information for your server or hosting company open the PhpMyAdmin tool. Open the database and look for the table named "users" and then click the icon to "view" the data in that table.</translate> 
<translate>
You should see the names of staff who have accounts on your Joomla site. This view provides you the confidence that you are about to backup the correct database.</translate> 
<translate>
Click the export tab, then go.</translate> 
<translate>
Your browser will download your database into an SQL file.</translate> 
<translate>
Find where you browser put that file, then move the file to a much more secure drive or location.</translate>

<translate>
Server SQL databases can be backed up without PhpMyAdmin and instead using the SQL command line. If you know how to do that, you're most likely not in need of this documentation.</translate>

<translate>
It is recommended to back up the database at least twice per week or even everyday (and more) if you have an active site.</translate>

<translate>== File System Backup Part 2 of 2 == </translate>

<translate>
Continue with your site offline, see above. Your joomla folder and files can be backed up by downloading them with an FTP utility or using the file manager of your webhosting company. Both of these file options work, neither is better.</translate>

<translate>
FTP tools move thousands of Joomla files and use more time. The FTP process can be slow and interrupted. Most hosting companies provide a control panel for taking thousands of files in one folder and then creating a zip file very quickly.</translate> 
<translate>
This means your site is offline for a shorter amount of time, and you have only one zip file. Go to your hosting control panel and look for their file manager icon.</translate>

<translate>
If you use your hosting file manager, practice using that interface to select your server folder and creating a zip file. Download the zip file locally and then expand it locally to to see what files are inside that zip file. This option also let's you expand the same zip file for restoration to a staging site.</translate>

<translate>
Backing up the Joomla files with FTP is no different than backing up a static HTML website. Download all the files and folders that exist in the main Joomla directory. The downloaded locaiton is a folder on your local computer. Be sure that the file and directory structure remains the same as it is in the live site. When you restore the files, you will use the FTP utility to upload the files to a new server.</translate>

<translate>
'''As soon as you've downloaded your files via zip or FTP, change your site to be online.'''</translate>

<translate>
== More Backup Documentation == 
</translate>

<translate>
Most administrators of a Joomla website have access to their MySQL data using the GUI interface called PhpMyAdmin, see [https://phpmyadmin.readthedocs.org/en/latest/faq.html#how-can-i-backup-my-database-or-table How can I backup my database or table?] for more information.</translate>

<translate>
There are several automated backup extensions for Joomla! located in the [http://extensions.joomla.org Joomla! Extensions Directory]. Here is a link for [http://extensions.joomla.org/extensions/extension?searchall=backup&controller=filter Joomla! Backup Extensions].</translate>

<translate>
When servers are hosted in the same building as the staff, the web administrators should make extra care to store the backup copies of the database/files in a different building. Fire, theft, water or other damage often wipes out the live website AND backups. On a regular basis the web administrators should burn both the database and files to CD or save to an external hard drive off site.</translate>

<translate>
==Special Notes== 
</translate>

<translate>
=== 2FA (Two factor authentication) === 
</translate>

<translate>
If you use 2 factor authentication (available since Aug 2014) and you are locked out of your site you can rename the folder plugins/twofactorauth to twofactorauth.BAK and log in to your site's back-end. Then disable all plugins under the "twofactorauth" group. Finally, rename the plugins/twofactorauth.BAK folder of your site back to twofactorauth.</translate>
<translate>
*See also: [[S:MyLanguage/J3.x:Two_Factor_Authentication|Tutorial Two Factor Authentication]]</translate>

<translate>
=== Automated Backup Tools === 
</translate>

<translate>
==== Akeeba ==== 
</translate>

<translate>
* Akeeba Backup produces a .jpa file that you should download to a safe location that's not on your webhost or webserver.</translate>
<translate>
* The .jpa file contains all the folders/files and database files.</translate>
<translate>
* The .jpa file also contains an installer</translate>

<translate>
These paragraphs are about backup, but it's worth a quick note that the Akeeba restore process is a fast guided process similar to a setup wizard.</translate> 
<translate>
Place 2 files on a new webhost.</translate> 
<translate>
a) your JPA file and b) Kickstart.php (from Akeeba)</translate> 
<translate>
You then use a browser to launch the restore process and unpack the .jpa file.</translate> 
<translate>
Please read the Akeeba restore documentation.</translate>

<translate>
Akeeba and other backup extensions can be downloaded from the [https://extensions.joomla.org/extensions/extension?search=backup JED]</translate>

<noinclude>
<translate>

[[Category:Tutorials]]
[[Category:Security]]
[[Category:Incoming External Link]]
</translate>
</noinclude>

Portal talk:Beginners

2019-05-30T17:13:17Z

Topazgb:

{{archived_talk_pages}} 
In the [http://forum.joomla.org/viewtopic.php?f=303&t=848903&p=3185783#p3246874 forum], Gloria superbee requested a correction to remove the duplicate word ''when'':

''One way is to learn by working with the sample data which can be installed '''when when''' installing Joomla!''

== Edit Requests 21 Apr 2015 00:48 ==

Please correct:

Maybe you are a seasoned Information Technology professional, but you have never Joomla! before.

to

Maybe you are a seasoned Information Technology professional, but you have never '''used''' Joomla! before.

Done thanks
MATsxm

---------------
'''Edit request'''

The link for the Forum Post Assistant is https://forum.joomla.org/viewtopic.php?f=621&t=582860 it contains a link to the lates fpa
--Topazgb 12:13, 30 May 2019 (CDT)

Testing Joomla! patches

2019-04-12T09:45:09Z

Topazgb: Added additional instructions

<noinclude><languages /></noinclude>
<translate>
In all software there are mistakes that need to be fixed, this is also the case in Open Source software like Joomla!. The source code of Joomla! is centrally located on the internet, making it accessible to everyone. Anyone who spots a bug or issue with Joomla! can report it. A guide to Filing bugs and issues can be found here: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]]
Reported bugs will be solved and eventually need testing. This page explains how you can contribute to the Joomla project by testing proposed solutions. You do not need to have any coding knowledge, you do need a Joomla installation to test on.
A Quick Reference Guide for testing is available at: [[S:MyLanguage/Testing Joomla! patches QuickReferenceGuide|Testing Joomla! patches QuickReferenceGuide]]</translate>

<translate>
=== The Joomla staging code === 
</translate>
<translate>
The Joomla staging code is the most recent code that is being worked on. All bugfixes and new features are applied to this code.


The Joomla staging code is located at https://github.com/joomla/joomla-cms, this is the code that needs to be installed. How that is done is explained a little further under [[#Preparing to test|Preparing to test]].</translate>

<translate>
=== The issue-tracker === 
</translate>
<translate>
The issue-tracker for Joomla is located here: https://issues.joomla.org</translate>

[[File:joomla_issue_tracker-<translate>
en</translate>.png|800px]]

<translate>
The list shows the tracker items from new to old but the order can be changed by using the filters under Search tools. All items in the tracker, that have a patch, have a version number beside the title.
* PR-staging: This is Joomla 3.8.x
* PR-4.0-dev: This is Joomla 4.0</translate>

<translate>
These labels will change in the future as new versions come and old versions go.


The status is important and this is an explanation:</translate>

<translate>
'''New''' - Immediately after an issue is reported it receives this status. When you find a bug, create a description how to reproduce the bug. People who are testing the issue then know how to test the patch.</translate>

<translate>
'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.</translate>

<translate>
'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.</translate>

<translate>
'''Ready to commit''' - The patch has been successfully tested and the code can be committed.</translate>

<translate>
'''Closed''' - This status is for all issues that need no further action.</translate>

<translate>
Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.</translate>

<translate>
Basically you start testing issues that have the status "Pending".</translate>

<translate>

=== Preparing to test === 
</translate>
<translate>
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.</translate>

<translate>
==== Create folder ==== 
</translate>
<translate>
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.</translate>

<translate>
==== Download Joomla! ==== 
</translate>
<translate>
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''</translate>

[[File:joomla_github-<translate>
en</translate>.png]]

<translate>
This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.</translate>

<translate>
Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data


This is important so everybody uses the same data to test!


The installation folder does not have to be removed, this way you can easily reinstall everything if needed.</translate>

<translate>

=== Download Patch Tester === 
</translate>
<translate>
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page] and after that can be installed via the Extension manager in Joomla.</translate>

<translate>
To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].</translate>

<translate>
=== Setup Patch Tester === 
</translate>
<translate>
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.</translate>

[[File:patchtester_repo-<translate>
en</translate>.png]]

<translate>

On the second tab called GitHub Authentication you can enter your GitHub username and password or token if you use a token.
</translate>

[[File:patchtester_details-<translate>
en</translate>.png]]

<translate>

Note: If you have enabled Two-Factor Authentication for your GitHub account, you will need to create a personal access token at https://github.com/settings/applications and enter that in the GitHub token field.
</translate>

<translate>
After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.</translate>

<translate>
You are now ready to start testing.


Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.</translate>

<translate>

=== Installing Patch === 
</translate>
<translate>
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:


[#4308] - Fixed event dispatching inconsistencies leading to incomplete API


Beside the # is the ID and behind the - sign comes the title.</translate>

<translate>
After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced</translate>

<translate>
=== Recording test results === 
</translate>
<translate>

After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.


It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.
</translate>

[[File:New_testthis_button-<translate>
en</translate>.png|The new Test This button and how to use it]]

<translate>
=== Revert patch === 
</translate>
<translate>
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.


If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.</translate>

<translate>

== Videos== 
</translate>
<translate> Learn How to test patch with this video series ''How to "Patch Test" Joomla! code'':</translate>
<translate> *Part 1: Introduction</translate>
{{#widget:YouTube|id=zmnWkMisdJk}}

<translate> *Part 2: Neard Web Server setup</translate>
{{#widget:YouTube|id=Tqj-BAmPGLA}}

<translate> *Part 3: Sample issue testing.</translate>
{{#widget:YouTube|id=s881RLaFO8U}}

<translate>
== Link== 
</translate>
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

Bug Tracking Process

2019-04-12T09:10:47Z

Topazgb: Testing is always done on the staging version so that other merged patches are included in the test.

<noinclude><languages /></noinclude>
<translate> This article documents the current Joomla! bug tracking process from the time a new bug is reported to the time it is closed.</translate>

<translate> Joomla! bugs are tracked in the [https://issues.joomla.org/ Joomla! Issue Tracker], this Tracker is for issues with supported Joomla Versions. Recommended version is '''J{{CurrentSTSVer|minor}}'''.</translate>
<translate>
==Helping out== 
</translate>

<translate> You do ''not'' need to be a member of the Joomla! Bug Squad to help fix bugs in Joomla. [[S:MyLanguage/Filing bugs and issues|Anyone can report bugs]], test patches, or submit patches. If you want to help with resolving bugs, go to the [https://issues.joomla.org/ Tracker]. You can help resolve Open issues as outlined below. You can create and submit patches for Confirmed issues. Or you can help test Pending issues. To report about what you have done, login with a Github account and add a comment. You'll be amazed at how much impact you can have and how good it feels to contribute to the Joomla! project.</translate>
<translate>

If you have any questions, or are interested in joining the [[S:MyLanguage/Portal:Bug_Squad|JBS]], please contact [mailto:bugsquad@community.joomla.org The Bug Squad Coordinators].</translate>
<translate>
===Testing Pre releases=== 
</translate>
<translate>

Before a stable release of Joomla is released the update needs testing. This is a simple process:
# Install the Staging release of Joomla https://github.com/joomla/joomla-cms in a subfolder or on localhost (you can use a copy of a production site but '''never test on a live production site''').
# Navigate to the Options of the Joomla! Update component and set the 'Update server' to 'Test'. [[S:MyLanguage/Help38:Components Joomla Update|Components Joomla Update]]
# When a Joomla pre release is ready for testing, log into your test site and install the Update. Then test the site works as expected. Please report any errors/bugs on the [https://issues.joomla.org/ Joomla! Issue Tracker]
</translate>
<translate>

==Reporting Issues== </translate>
[[Image:ReportingIssues.png|ReportingIssues.png]]

<translate>

The process is normally started in one of two ways: the bug is added to the respective tracker, or a user reports the bug in the [https://forum.joomla.org/viewforum.php?f=728 Joomla! Bug Forum] for the given maintenance release.</translate>

<translate>

=== Issues reported on the forum === 
</translate>

<translate> JBS members scan the forums to determine when issues need to be put into the tracker. If the issue can be reproduced, is clearly a bug, and there are step-by-step instructions for how to reproduce it, it can be entered into the tracker with a status of Confirmed. If it is not as clear-cut, it can be entered with a status of Open, so that other JBS members will know it needs further investigation.</translate>
<translate>
=== Issues directly reported to the tracker === 
</translate>

<translate>
When an issue is added to the tracker, the status could be depending on the situation;
# New
# Confirmed
# Pending
If the issue needs more investigation, then it should be set to New. If the issue (1) is a bug and (2) can be reproduced and (3) has good test instructions, it should be set to Confirmed. If it meets the three Confirmed criteria and also has a good patch attached, it should be set to Pending. See below for more information about the status codes.</translate>

<translate>
=== Issue Priorities === 
</translate>

<translate> [[S:MyLanguage/Bug and Issue Tracker Priority|Why most issues are priority 3]], or Medium. The artifacts are prioritized according to the following characteristics:</translate>

<translate>
'''Critical (1):'''
The trunk is not working at all. Significant parts of the source are broken preventing key operations. Examples would be login, installation, extension installers, javascript errors that prevent you from moving a save or similar action, etc. Also includes the generation of Fatal PHP errors and major security issues in a prerelease (Security issues for a stable release should NOT be reported in the tracker but instead reported to the security team security@joomla.org).</translate>

<translate>
'''Urgent (2):'''
Parts of the source are obstructing operation in a serious way or causing a major loss in advertised function. Examples would includes PHP notices and warnings and reported javascript errors. Major issues will also typically prevent the release cycle from moving from Beta to Release Candidate (RC), or Release Candidate to General Availability (GA).</translate>

<translate>
'''Medium (3):'''
Issues that are hindering advertised behavior but the application is still workable. Examples would include parameters not working as advertised, language files not loading as expected, etc.</translate>

<translate>
'''Low (4):'''
Minor loss of function and generally annoying behavior. May include less common platform or browser specific problems that while they may be technically major in those environments, they represent a minority. Also include missing translation strings.</translate>

<translate>

'''Very low (5):'''
Cosmetic problems, misspelled words, graphically misaligned object, less common issues with parameters, etc.</translate>

<translate>
== Resolving Issues == 
</translate>

<translate> The bug squad takes care of the Joomla releases. For example, that means getting the 3.4, 3.5, ... etc releases ready by fixing problems that come up. The idea is to make the release increasingly stable and take care of issues that come up. At the same time, it is vitally important not to break anything that is working. That's called software regression and it's not something you want at this stage.</translate>
<translate>

In the trackers there are several common statuses, mainly: new, confirmed, pending, ready to commit.</translate>

* <translate> '''New''' means it's reported, but it hasn't been determined for sure whether it is a real bug or not. Many Open issues are not actually bugs. If the issue fits into one of the categories below, then the status is changed as indicated and the bug is closed:</translate>
** <translate> Cannot be reproduced. We have tried the same thing the reported did but the software appears to work correctly. (In many cases, more information is needed to be able to reproduce a bug. See "Information Required" below.) Change status to '''Unconfirmed Report'''.</translate>
** <translate> Has already been reported in a different issue number. Change status to '''Duplicate report''' and add the number on the duplicates tab.</translate>
** <translate> Is a known limitation of the software. Change status to '''Known issue'''.</translate>
** <translate> Is a feature request, a mistake made by a user, or is the way the software is intended to work. Change status to '''Expected Behaviour'''.</translate>
** <translate> Is a bug with an extension or some other external program or a server issue that will not be addressed. Change status to '''Closed''' and leave a comment explaining the reason.</translate>
* <translate> '''Information Required''' is used if we need more information ''from the person who reported the issue'' to decide about the issue. For example, there are questions about how to reproduce the problem or other questions about the issue. If we get the information we need, then we can continue processing the issue. If we don't get the information within two weeks, then we can change the status to Unable to confirm (or another of the closed status codes if that is more applicable).</translate>
* <translate> '''Needs Review''' is used if we need a PLT Member or CMS Maintainer for a review / decision. This is different from Information Required, which means that we need more information from the person who reported the issue.</translate>
* <translate> '''Confirmed''' means that JBS has confirmed that this issue is a bug in Joomla! that should be fixed. That's when the JBS tries to solve it or consults with the development team about a solution. ''At this point there should be clear step-by-step test instructions that indicate how to reproduce the problem.''</translate>
* <translate> '''Pending''' means that a patch has been submitted. Every Pending issue should have instructions that tell the tester how to reproduce the problem and make sure the patch fixes the problem.</translate>
* <translate> '''Ready to commit''' means that (in general) two separate people have successfully tested the same patch file, and it works correctly with the patch. Note that, for some issues that are more complex or higher impact, we may need more than two people to test or may need to test on multiple platforms. For simple issues, such as fixing typos in language strings or comments, one tester is enough.</translate>
* <translate>
'''Fixed in Code Base''' means that, after reviewing the code, the JBS commit coordinators have determined that the patch is good and the change has been committed to the Joomla! code-base. At this point, it will be part of the next Joomla! maintenance release.
The '''Easy Test'''-mark is not a dedicated status, it is more a label to show Pending issues with easy test instructions.</translate>

<translate> The flowchart below provides a visual guide to how the process for resolving bugs works.</translate>

[[Image:ResolvingIssues.png|ResolvingIssues.png]]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
</noinclude>

J3.x talk:Updating Joomla (Update Method)

2018-10-12T21:01:23Z

Topazgb: Created page with "you can update the Joomla CMS using the install method. Links to old out of date info https://docs.joomla.org/J3.x:Updating_Joomla_(Install_Method) The link needs to be https..."

you can update the Joomla CMS using the install method.

Links to old out of date info https://docs.joomla.org/J3.x:Updating_Joomla_(Install_Method)
The link needs to be https://docs.joomla.org/J3.x:Upgrading_from_Joomla_3.4.x_to_3.5 . But It can't be edited

User talk:Topazgb

2018-10-11T12:03:53Z

Topazgb: /* your change on the updating from 3.4 to 35 article */

== Joomla! 3.0 - Getting Started with Joomla! page ==

Hi Topazgb, thanks for contributing to the wiki page, [[Getting Started with Joomla!‎]].

I have undone your edit twice on the part where you call Joomla! 3.0 an LTS version. Joomla! 3.0 is not an LTS version and support will end for 3.0 shortly, about April 25, 2013. Please refer to, the Joomla! [[Release and support cycle]].

There is too much confusion already about what is and what will be supported and for how long. 3.0, 3.1, 3.2 are all STS versions with a rough 7 months of support. The 3.0, 3.1, and 3.2 versions will be working towards the 3.5 version which will be an LTS (Long Term Support) version. 3.5 is estimated to be released end of March, 2014. Thanks! -- [[User:Hutchy68|Tom Hutchison]] ([[User talk:Hutchy68|talk]]) 23:50, 10 March 2013 (CDT)

----------------------

3.0, 3.1, 3.2 are Short Term Releases that have Long Term Support
"support for 3.x ends in 2016." http://www.joomla.org/download.html
3.0, 3.1, 3.2 are all 3.x and therefore as support for them ends in 3 years time they are by definition LTS.

:No, this is incorrect. 3.0, 3.1, and 3.2 releases will cease to be developed any further upon the release of the next STS version. The extra month is security only updates. From this point on, documentation will cease for all STS's upon the release of the next STS, for example, 3.0 documentation will become 3.1 documentation. The project will not continue to document versions of an STS once it has hit end of life. This has been an issue of great confusion because it gives those who install an STS version a sense they are up-to-date when in fact they are not once the next STS version is released. Take care --- [[User:Hutchy68|Tom Hutchison]] ([[User talk:Hutchy68|talk]]) 08:08, 11 March 2013 (CDT)

:PS, I see where you are getting your information from, I'll let Nick know the page needs to be clearer, in reference to 3.x. [[User:Hutchy68|Tom Hutchison]] ([[User talk:Hutchy68|talk]]) 08:12, 11 March 2013 (CDT)

--------
Documentation for 3.0 releases may well 'cease to be developed any further' but they will still be LTS by virtue of the fact of the one click upgrades. As stated in the other wiki page

"The 3.x series will have over 4 years of support as well. 3.0 to 3.1 to 3.5 will be one-click upgrades" http://docs.joomla.org/Joomla_3.0_FAQ

The terms Short Term Release and Long Term Support are not mutually exclusive. 3.0 is a Short Term Release which has Long Term Support.

:I think you are getting caught up in the semantics of release vs. version vs. series. I've changed the wording of the page you're referencing. Short Term Release, guessing you mean Short Term Support, has also been referred to as Standard Term Support. Another confusing term to use, but the upgrade functions in administrator view call it Short Term Support, so the switch to "Short" from "Standard" was made.

:The '''series''' itself will have Long Term Support but '''only if user upgrades from STS to STS to STS(there was an extra STS added last year) then LTS'''. Each individual version(release if you want), has its own support life cycle then dies. 7 months for STS versions, 27 months(maybe a bit more) for LTS versions.

:To say to someone, 'Joomla! 3.0 has Long Term Support' gives users and developers the wrong information. Especially the case for the casual user because it gives a false sense of security. Once J3.1 is released, all of J3.0 support will end and users of J3.0 could be vulnerable to security issues unless they click to upgrade to J3.1. Something the user must do on their own. We are aware of the issues and confusion over STS vs LTS vs Version vs Series. Perhaps, 'The Joomla! 3.x series will have Long Term Development?' might be a better way to phrase it.

:Take care -- [[User:Hutchy68|Tom Hutchison]] ([[User talk:Hutchy68|talk]]) 16:25, 11 March 2013 (CDT)

-------

"I've changed the wording of the page you're referencing. Short Term Release, guessing you mean Short Term Support, has also been referred to as Standard Term Support"

Then you are guessing wrong. There is a difference between Short Term Release and Short Term Support. And is the use of Short Term Support instead of Short Term Release that is incorrect. And no it is not semantics because accurate definition is important.

"Once J3.1 is released, all of J3.0 support will end and users of J3.0 could be vulnerable to security issues unless they click to upgrade to J3.1."

Not accurate because 3.0 will be supported by virtue of the fact that the 'one click upgrade' once 3.1 is released. And all Joomla versions are "vulnerable to security issues unless they click to upgrade"

The page I edited -- wrongly describes 3.0 as STS when it is Short Term Release and has Long Term Support by virtue of the 'one click upgrade'.

We shall have to agree to differ on this ... and I give up on trying to explain why you are wrong.

== Upgrade 1.5 -> 3 page ==

There is a bad link in your [[How do I upgrade from Joomla! 1.5 to 3.x?#Manual method|instructions for a manual upgrade]] from 1.5 -> 3. I’ve reformatted the other links to include the name of the extension so they can be searched for if JED break the links, but there’s still one that doesn’t link to an extension page. What extension did you mean?

[[User:Moilleadóir|Moilleadóir]] ([[User talk:Moilleadóir|talk]]) 02:50, 11 March 2014 (CDT)

:Have updated the link. Joomla archived extensions does not appear to exist any more so I put a direct link to the authors download page. Thanks
:--Topazgb 06:06, 11 March 2014 (CDT)

== updating the https://docs.joomla.org/J3.x:To_access_the_Template_Manager ==

Thanks for the update but could you please make the updates for all mentions about "Manager" as well as the image. 
Thanks

I tried but could not edit them

Hmmm strange... 
I will have a look later 
thanks anyway ;)

Please see the screenshots
http://www.weblinksonline.co.uk/joomladocs/edit%20jdocs%2001.JPG
http://www.weblinksonline.co.uk/joomladocs/edit%20jdocs%2002.JPG

There were multiple inclusions + few things to fix/update. 
Thanks 
([[User:MATsxm|MATsxm]] ([[User talk:MATsxm|talk]]) 07:24, 9 October 2015 (CDT))

== your change on the updating from 3.4 to 35 article ==

Hello, 

I removed your change "If you HAVE the ability to unpack the archive on the server, please see Method C", as you have to use Method C if you CAN'T unpack the archive on the server.
 

Happy Easter!
 

-----------------------
Yes ... as soon as I saw the revert I realised I had misread it.

([[User:Sandra97|Sandra97]] ([[User talk:Sandra97|talk]]) 17:37, 27 March 2016 (CDT))

----------

Hello,

I reverted your latest change on the page as it wasn't correct. For method B, you upload the package from downloads and then install it from the Joomla Update Component, so what was mentioned was correct.

Thanks

([[User:Sandra97|Sandra97]] ([[User talk:Sandra97|talk]]) 22:54, 9 October 2018 (CDT))

-------------
My edit was correct for two reasons
1. When the url is clicked it uses the browser to download the update package and thus by-pass the server restrictions that cause the update to fail.
2. When the url is clicked the browser downloads the correct update package. But if the user visits the download page they can (because of human error) download the wrong package. Userers can break their site if they use the wrong package.

You are making the error of assuming that if Joomla can't download the update package then clicking the hyperlink won't work. When the 'Update' button is clicked Joomla uses the server to download the package ... but if the hyperlink is clicked then a new browser window/tab is opened and the browser handles the download.

If the browser (when the hyperlink is clicked) does not download the package then the browser will not down loaded if it is navigated to by https://downloads.joomla.org

My edit was correct. I was one of a few people that spent a whole Easter weekend testing the Upload&Update tab
--Topazgb 05:16, 10 October 2018 (CDT)

---

Thanks for your explanation! I just republished your edits.

Sandra

--------

The other wasn't wrong per se but not necessarily the best for the reasons stated. Perhaps it needs to include both methods of reaching the update package ? With an explanation of why clicking the hyperlink rules out human error.

---

Can be a good idea. The more information we can provide, the easier it will be for users.

-----

OK added a couple of lines. Thought too much would confuse things. Methinks methods A and B should be switched with each other because
Uploading the package to the /tmp file only needs to be done when the Upload&Update tab fails. If you concur ... could you please do it because I can't do it without messing the translation tags.

---

I'll do as soon as I can. I'm currently travelling and won't be available all days and with few availabilities during the next 10 days.

---

Update: I switched A and B. Tell me if it's ok for you like that. Thans!

---

Yah that looks good and is more logical. Sorry I don't understand the language tags enough to have done it myself.

--Topazgb 07:03, 11 October 2018 (CDT)

User talk:Topazgb

2018-10-10T21:54:18Z

Topazgb: /* your change on the updating from 3.4 to 35 article */ suggestion for rearranging the order.

J3.x:Upgrading from Joomla 3.4.x to 3.5

2018-10-10T21:44:10Z

Topazgb: Added details about the update url link.

<noinclude><languages /></noinclude>
 {{note|<translate>

'''Please note!'''</translate>
<translate>

Updating to Joomla 3.5 can no longer be done through the extension manager. 
You must now update through the Joomla! Update component (or by manual action as indicated below).</translate>|type=serious}}

{{tip|title=<translate>
Before updating, always take a [[S:Mylanguage/Backup Basics for a Joomla! Web Site|backup]] and don’t forget to test it.</translate>}}
<noinclude>{{Joomla version|version=3.x}}</noinclude>
<translate>
==Update by using the Joomla! Update component (recommended)== 
</translate>
<translate>
Preferably you update your Joomla! Installation by using the Joomla! Update component</translate> <translate>
If you don't know how to use the Joomla! update component, please see: [[S:MyLanguage/Help34:Components_Joomla_Update|Joomla! Update Component]].</translate>{{-}}

{{tip|title=<translate>
Caveat!</translate>|<translate>
If you're using '''OpCache''' with the setting '''opcache.revalidate_freq''' with a number greater than 1, some of the classes (like JVersion) might be cached from a previous request and thus make the update script fail. Set '''opcache.revalidate_freq''' to 0 in that case and retry.</translate>|type=serious}}

<translate>
==Update when you can't use the Joomla! Update component== 
</translate>
<translate>
If you can’t update your Joomla! Installation using the Joomla! Update component because of hosting limitations or connection issues then you will need to follow these steps:

'''N.B.''' Clicking the "Update url" link in '''Components'''{{rarr}}'''Joomla Update''' opens a new browser window/tab. This allows the browser to by-pass the server and directly download the correct update package.</translate>
<translate>
#Method A</translate> {{-}}
<translate>
##Go to '''Components'''{{rarr}}'''Joomla Update'''. Click the "Update url" link and save the update package to your computer.</translate>
<translate>
##Copy the update package (that you just downloaded) to the sites /tmp folder (note the path is set in the Joomla Global Configuration - make sure it's in the correct directory) {{-}}(N.B. this method only works with the update package that the Joomla! Update component discovers. It will not work for other update packages or the Joomla full package. It also requires an internet connection to the Joomla Update XML file).</translate>
<translate>
##Go to '''Components'''{{rarr}}'''Joomla Update'''. The Joomla! Update component will use the update package from your /tmp folder.</translate>
<translate>
#Method B {{-}}</translate>
<translate>
##Go to '''Components'''{{rarr}}'''Joomla Update'''. Click the "Update url" link and save the update package to your computer.</translate>
<translate>
##Go to '''Components'''{{rarr}}'''Joomla Update'''{{rarr}} '''Upload & Update tab'''</translate>
<translate>
##'''Browse''' to the file then '''Upload & Install'''</translate>
<translate>
#Method C{{-}}Only use this method if method A and method B fail:</translate>
<translate>
##Download the update package from https://downloads.joomla.org</translate>
<translate>
##Extract the download package on your computer</translate>
<translate>
##Using your favorite FTP software, upload the folders and files at the root of the website or in the folder where your Joomla! installation is located. ('''NOTE:''' If you are using Filezilla, click on "Replace" for all, if you are using WinSCP, click on upload and then allow override for all. The FTP software will overwrite the existing files and add the new ones.)</translate>
<translate>
##Please see https://gist.github.com/mbabker/d7bfb4e1e2fbc6b7815a733607f89281</translate>

<translate>

==Resources== 
</translate>
<translate>
'''See also: [[S:MyLanguage/J3.x:Updating from an existing version|Updating from an existing version]].'''</translate>

<noinclude>
[[Category:Version 3.x FAQ{{#translation:}}]]
[[Category:Version 3.5 FAQ{{#translation:}}]]
[[Category:Version 3.5.0 FAQ{{#translation:}}]]
[[Category:Joomla! 3.x{{#translation:}}]]
[[Category:Joomla! 3.5{{#translation:}}]]
[[Category:Update{{#translation:}}]]
[[Category:FAQ{{#translation:}}]]
</noinclude>

User talk:Topazgb

2018-10-10T14:33:22Z

Topazgb:

User talk:Topazgb

2018-10-10T10:16:46Z

Topazgb: /* your change on the updating from 3.4 to 35 article */

J3.x:Upgrading from Joomla 3.4.x to 3.5

2018-10-10T00:17:43Z

Topazgb: corrected way to download the correct update package

<noinclude><languages /></noinclude>
 {{note|<translate>

'''Please note!'''</translate>
<translate>

Updating to Joomla 3.5 can no longer be done through the extension manager. 
You must now update through the Joomla! Update component (or by manual action as indicated below).</translate>|type=serious}}

{{tip|title=<translate>
Before updating, always take a [[S:Mylanguage/Backup Basics for a Joomla! Web Site|backup]] and don’t forget to test it.</translate>}}
<noinclude>{{Joomla version|version=3.x}}</noinclude>
<translate>
==Update by using the Joomla! Update component (recommended)== 
</translate>
<translate>
Preferably you update your Joomla! Installation by using the Joomla! Update component</translate> <translate>
If you don't know how to use the Joomla! update component, please see: [[S:MyLanguage/Help34:Components_Joomla_Update|Joomla! Update Component]].</translate>{{-}}

{{tip|title=<translate>
Caveat!</translate>|<translate>
If you're using '''OpCache''' with the setting '''opcache.revalidate_freq''' with a number greater than 1, some of the classes (like JVersion) might be cached from a previous request and thus make the update script fail. Set '''opcache.revalidate_freq''' to 0 in that case and retry.</translate>|type=serious}}

<translate>
==Update when you can't use the Joomla! Update component== 
</translate>
<translate>
If you can’t update your Joomla! Installation using the Joomla! Update component because of hosting limitations or connection issues then you will need to follow these steps:</translate>
<translate>
#Method A</translate> {{-}}
<translate>
##Go to '''Components'''{{rarr}}'''Joomla Update'''. Click the "Update url" link and save the update package to your computer.</translate>
<translate>
##Copy the update package (that you just downloaded) to the sites /tmp folder (note the path is set in the Joomla Global Configuration - make sure it's in the correct directory) {{-}}(N.B. this method only works with the update package that the Joomla! Update component discovers. It will not work for other update packages or the Joomla full package. It also requires an internet connection to the Joomla Update XML file).</translate>
<translate>
##Go to '''Components'''{{rarr}}'''Joomla Update'''. The Joomla! Update component will use the update package from your /tmp folder.</translate>
<translate>
#Method B {{-}}</translate>
<translate>
##Go to '''Components'''{{rarr}}'''Joomla Update'''. Click the "Update url" link and save the update package to your computer.</translate>
<translate>
##Go to '''Components'''{{rarr}}'''Joomla Update'''{{rarr}} '''Upload & Update tab'''</translate>
<translate>
##'''Browse''' to the file then '''Upload & Install'''</translate>
<translate>
#Method C{{-}}Only use this method if method A and method B fail:</translate>
<translate>
##Download the update package from https://downloads.joomla.org</translate>
<translate>
##Extract the download package on your computer</translate>
<translate>
##Using your favorite FTP software, upload the folders and files at the root of the website or in the folder where your Joomla! installation is located. ('''NOTE:''' If you are using Filezilla, click on "Replace" for all, if you are using WinSCP, click on upload and then allow override for all. The FTP software will overwrite the existing files and add the new ones.)</translate>
<translate>
##Please see https://gist.github.com/mbabker/d7bfb4e1e2fbc6b7815a733607f89281</translate>

<translate>

==Resources== 
</translate>
<translate>
'''See also: [[S:MyLanguage/J3.x:Updating from an existing version|Updating from an existing version]].'''</translate>

<noinclude>
[[Category:Version 3.x FAQ{{#translation:}}]]
[[Category:Version 3.5 FAQ{{#translation:}}]]
[[Category:Version 3.5.0 FAQ{{#translation:}}]]
[[Category:Joomla! 3.x{{#translation:}}]]
[[Category:Joomla! 3.5{{#translation:}}]]
[[Category:Update{{#translation:}}]]
[[Category:FAQ{{#translation:}}]]
</noinclude>

Talk:Planning Migration - Joomla 1.5 to 3

2018-10-01T09:08:35Z

Topazgb: Created page with "Perhaps this should be Archived as it is far easier to create a Joomla 3.x from scratch ? --~~~~"

Perhaps this should be Archived as it is far easier to create a Joomla 3.x from scratch ?
--Topazgb 04:08, 1 October 2018 (CDT)

How do you put a module inside an article?

2018-09-24T13:36:49Z

Topazgb: Tidy syntax

<noinclude><languages /></noinclude>
<noinclude>{{Joomla version|version=2.5|time=and after|comment=<translate>
series</translate>}}</noinclude>
<translate>

You will usually want to associate modules with articles in some way. The modules are allocated to module positions and the module positions appear somewhere on the Web page as determined by the template. However, it is sometimes useful to have a module actually embedded within the article. Joomla core provides two ways to do that: loadposition and loadmodule.
</translate>

<translate>
Syntax:</translate>
*{loadposition position'[style]}
*{loadmodule mod_type,the title,[style]}

<translate>
==loadposition== 
To insert a module inside an article, you publish the module to a position and load that position in the article as follows:
</translate>

<translate>

#Create a module and set its position to '''''myposition'''''. '''''myposition''''' can be any value that doesn't conflict with an existing template position. Type in the position '''''myposition''''' and press enter instead of selecting it from the drop-down list.
</translate>
<translate>

#Assign the module to '''All''' the Menu Items. This will make sure that it always appears, no matter how the visitor got to the article. The module will not show unless you put the command to load the module in an [[S:MyLanguage/article|article]].
#Edit the articles where you want this module to appear and insert the text '''''{loadposition myposition}''''' in the article at the place where you want the module.
</translate>

{{dablink|<translate>
*Note that this only works when the [[S:MyLanguage/Help25:Extensions_Plugin_Manager_Edit#Content_-_Load_Modules|''Content - Load Module'' plugin is enabled]]. If this plugin is disabled, the text ''{loadposition myposition}'' shows unchanged in the article.


Also, the name of the position should be all lowercase. CamelCapitalization will fail.</translate>}}

<translate>
==loadmodule== 
An alternative to "{loadposition xx}" is the "{loadmodule yyy}" variation which is handled by the same plugin.
</translate>

<translate>

In this case the plugin looks for the first module who's '''type''' matches the string 'yyy'. So you could load a "mod_login" module by placing {loadmodule login} in your text. If you wish to load a specific instance of a module, because you have more than one login module e.g. titled as Login 1, Login 2, etc. you have to use {loadmodule mod_modType, modTitle} where mod_'''modType''' would be mod_login and '''modTitle''' is name/title given to your instance of that module. So in the example above you end up with '''{loadmodule mod_login Login 2}'''. You can also add the style that is used for rendering the module. To do so, add the style as the third parameter like {loadmodule login,login2,xhtml}. If you don't add a style, then "none" is used.
</translate>

<translate>===Modules within Modules=== </translate>
<translate>

It is possible in Joomla! 2.5+ and Joomla! 3.x+ to include a module within a "Custom HTML" module. They are processed by content plugins in the same way as articles.
</translate>

<translate>

To make this work, the option '''Prepare content''' must be enabled as shown in this screenshot.
</translate>

[[File:j3x_custom_html_prepare_content_option-<translate>
en</translate>.png||<translate>
Showing the Prepare Content option in a Custom HTML module.</translate>]]

<translate>

You should remember when doing this that you might experience formatting issues as the "chrome" of the "Custom HTML" module will surround the "chrome" of the included module potential having undesirable effects of the formatting or layout.
</translate>

<noinclude>
<translate>

[[Category:Content Management FAQ]]
[[Category:Article Management FAQ]]
</translate>
</noinclude>

Talk:Updating Joomla (Manual Method)

2018-09-23T11:16:04Z

Topazgb: Created page with "This method is Obsolete and (in many case) can break a site. --~~~~"

This method is Obsolete and (in many case) can break a site.
--Topazgb 06:16, 23 September 2018 (CDT)

Talk:How do you put a module inside an article?

2018-09-20T14:42:03Z

Topazgb: /* loadmodule section needs some clarifications */

very helpfull
thank you

== loadmodule section needs some clarifications ==

In the section for loadmodule a few things aren't clear to me.

# How do I determine the name of the module in {loadmodule yyy}?
# In your example for two modules with same name, it's not clear to me why the module name is the 3rd parameter and why you use the term "login" for the 2nd parameter.
# Your example(s) don't show how to handle a module name with spaces in it. Do I just enclose in " " or? Use an example with a space in the name would make this clearer.

[[User:JAz|JAz]] ([[User talk:JAz|talk]]) 17:37, 20 February 2018 (CST)

Modules can not have the same name (Title). If the Title has a space in it then that is handled by the Title Alias. The Title Alias is auto generated on first save but can be edited.

How do you put a module inside an article?

2018-09-19T10:00:25Z

Topazgb: title-alias defines the module by name because it is the title-alias that is used to identify it not the title.

<noinclude><languages /></noinclude>
<noinclude>{{Joomla version|version=2.5|time=and after|comment=<translate>
series</translate>}}</noinclude>
<translate>

You will usually want to associate modules with articles in some way. The modules are allocated to module positions and the module positions appear somewhere on the Web page as determined by the template. However, it is sometimes useful to have a module actually embedded within the article. Joomla core provides two ways to do that: loadposition and loadmodule.
</translate>

<translate>
Syntax:</translate>
*{loadposition position[, style]}
*{loadmodule module[, title-alias[, style]]}

<translate>
==loadposition== 
To insert a module inside an article, you publish the module to a position and load that position in the article as follows:
</translate>

<translate>

#Create a module and set its position to '''''myposition'''''. '''''myposition''''' can be any value that doesn't conflict with an existing template position. Type in the position '''''myposition''''' and press enter instead of selecting it from the drop-down list.
</translate>
<translate>

#Assign the module to '''All''' the Menu Items. This will make sure that it always appears, no matter how the visitor got to the article. The module will not show unless you put the command to load the module in an [[S:MyLanguage/article|article]].
#Edit the articles where you want this module to appear and insert the text '''''{loadposition myposition}''''' in the article at the place where you want the module.
</translate>

{{dablink|<translate>
*Note that this only works when the [[S:MyLanguage/Help25:Extensions_Plugin_Manager_Edit#Content_-_Load_Modules|''Content - Load Module'' plugin is enabled]]. If this plugin is disabled, the text ''{loadposition myposition}'' shows unchanged in the article.


Also, the name of the position should be all lowercase. CamelCapitalization will fail.</translate>}}

<translate>
==loadmodule== 
An alternative to "{loadposition xx}" is the "{loadmodule yyy}" variation which is handled by the same plugin.
</translate>

<translate>

In this case the plugin looks for the first module who's '''type''' matches the string 'yyy'. So you could load a "mod_login" module by placing {loadmodule login} in your text. If you wish to load a specific instance of a module, because you have more than one login module e.g. titled as Login 1, Login 2, etc. you have to use {loadmodule mod_modType, modTitle} where mod_'''modType''' would be mod_login and '''modTitle''' is name/title given to your instance of that module. So in the example above you end up with '''{loadmodule mod_login Login 2}'''. You can also add the style that is used for rendering the module. To do so, add the style as the third parameter like {loadmodule login,login2,xhtml}. If you don't add a style, then "none" is used.
</translate>

<translate>===Modules within Modules=== </translate>
<translate>

It is possible in Joomla! 2.5+ and Joomla! 3.x+ to include a module within a "Custom HTML" module. They are processed by content plugins in the same way as articles.
</translate>

<translate>

To make this work, the option '''Prepare content''' must be enabled as shown in this screenshot.
</translate>

[[File:j3x_custom_html_prepare_content_option-<translate>
en</translate>.png||<translate>
Showing the Prepare Content option in a Custom HTML module.</translate>]]

<translate>

You should remember when doing this that you might experience formatting issues as the "chrome" of the "Custom HTML" module will surround the "chrome" of the included module potential having undesirable effects of the formatting or layout.
</translate>

<noinclude>
<translate>

[[Category:Content Management FAQ]]
[[Category:Article Management FAQ]]
</translate>
</noinclude>

J3.x talk:Editing a template with Template Manager

2018-08-20T12:49:31Z

Topazgb: Created page with "There needs to be a mention that Template customisation can be made on Admin as well as site templates. But I can't edit because of translation restrictions. Can someone ple..."

There needs to be a mention that Template customisation can be made on Admin as well as site templates. But I can't edit because of translation restrictions. Can someone please edit it ?