Joomla! Documentation - User contributions [en]

GSoC 2022 Project Ideas

2022-04-02T14:39:59Z

Rjharishabh: /* Project Description */

{{Top portal heading|color=white-bkgd|text-color=#333|title=
Welcome to Joomla GSoC 2022 Projects Page }}
[[Image:Gsoc2016.png|150px|center|link=GSoC 2020]]

Welcome to the [[GSoC_2022|Joomla Google Summer of Code (GSoC) 2022]] projects page.

If you are interested in participating as a student please review the materials on applying that are available at [https://developers.google.com/open-source/gsoc/faq Google]. We strongly encourage you to ask questions about process and projects on our [https://groups.google.com/forum/#!forum/jgsoc joomla-gsoc mailing list] and join our
[https://glip.com/joomla public Glip / Ringcentral chat tool].

'''''Note: The GSoC 2022 projects are displayed in no particular order'''''

==Project I: Workflow/scheduler ==

===Project Description===
With Joomla! 4.0 and 4.1 two new features were implemented into Joomla!: the workflow and the task scheduler. In this project both features should be combined. Workflow transitions which are then executed by the scheduler when they are scheduled.Therefore the user interface of the articles extension has to be extended + different task/workflow plugins need to be created.
As a student, here is the list of things expected from you as deliverable for the project:
*Deliver an user interface suggestion for com_content how the user interface can look like for pre-defining transition chains.
*Implement the user interface in com_content
*Deliver a task plugin to execute the transitions via the scheduler extension

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript
*Nice to have: Understanding of the Joomla! Scheduler and workflow extension

===Difficulty===
*Medium

===Project Type===
*Large [350 Hrs]

===Mentors===
*Yatharth Vyas
*Tushar
*Benjamin
*Christiane

[[Image:Gsoc2016.png|30px|center]]

==Project II: Guided Tour==

===Project Description===

In Joomla! are certain workflows needed to do certain tasks. Currently, users have to read the documentation if they’re new and want to know how they can achieve different things. This project should implement the functionality of guided tours in Joomla!. A tour is a click-through path which the user can follow to fulfill certain tasks like creating an article. So on the one hand Joomla! core should deliver basic tours for users to use core functionality without the need to read the documentation. On the other hand, it should be possible to create their own tours (e.g. as administrators for system operators), copy and change existing tours or allow 3rd party developers to ship their own tours when their extension will be installed.

The project has a history: https://docs.joomla.org/Guided_Tour

Now we want to make the project ready for the next Joomla Version.

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript

===Difficulty===
*Easy

===Project Type===
*Medium [175 Hrs]

===Mentors===
*Patrick Jackson
*Eyvaz Ahmadzada
*Jatin Salve

[[Image:Gsoc2016.png|30px|center]]

==Project III: SEO ==

===Project Description===
Joomla! 4.0 is built around a lot of SEO improvements. In this project you should implement additional basic SEO features.
As a student, here is the list of things expected from you as deliverable for the project:
*Review the current Joomla! 4 version and find out existing SEO features
*Define and propose new useful features which we can ship in future Joomla! Versions
*Implement features agreed with your mentor

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript
*Nice to have: SEO experience

===Difficulty===

*Medium

===Project Type===
*Medium [175 Hrs]

===Mentors===
*Christopher Wagner
*Philip Walton
*Shivam Rajput

[[Image:Gsoc2016.png|30px|center]]

==Project IV: Accessibility Plugin ==

===Project Description===
Joomla uses an accessibility Plugin. This Plugin should be foked and re-written completely.

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript

===Difficulty===

*Medium

===Project Type===
*Medium [175 Hrs]

===Mentors===
*Achilleas Papageorgiou
*Viviana Menzel
*Kumar Shivam

[[Image:Gsoc2016.png|30px|center]]

==Project V: Schema.org==

===Project Description===
Currently Joomla! uses inline microdata for adding rich snippets. The drawback of this implementation is that it’s hard coded (can’t be changed from the backend, only by overrides) and it is very generic. With this project, Joomla! should switch to a schema.org JSON+LD implementation which is configurable via the backend (e.g in article, category view).
As a student, here is the list of things expected from you as deliverable for the project:
*Suggest and implement a JSON+LD library
*Implement article/menu/category/… parameter interface to add rich snippets to articles.
*Output the rich snippets dynamically in the frontend

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript

===Difficulty===

*Hard

===Project Type===
*Large [350 Hrs]

===Mentors===
*Niels
*Richard Faith
*Anurag Kumar
*Rishabh Ranjan Jha

[[Image:Gsoc2016.png|30px|center]]

[[Image:Gsoc2016.png|50px|center]]

<noinclude>
[[Category:Google Summer of Code 2022]]
[[Category:Google Summer of Code]]
</noinclude>

J4.x:Creating a Simple Module

2021-05-22T18:07:21Z

Rjharishabh: Typo

<noinclude><languages /></noinclude>
{{Joomla version|version=4.x|comment=><translate> Tutorial</translate>}}
{{-}}
{{Top portal heading|color=white-bkgd|icon=file-code-o|icon-color=#5091cd|size=5x|text-color=#333|title=<translate> Creating a Simple Module for Joomla 4.x</translate>}}
{{-}}

<translate> This is a tutorial on how to Create a simple module for Joomla Version 4x.</translate>
<translate>
== Introduction == 
</translate>
<translate> Joomlaǃ 4 provides five types of extensionsː</translate>
* '''[[S:MyLanguage/Component|<translate> Components</translate>]]''' <translate> A component is the main part of the site. A component handles data manipulation as well as input and storage into the database. A component on most sites is the primary focus of the page.</translate>
* '''[[S:MyLanguage/Module|<translate> Modules</translate>]]''' <translate> A module is an add-on to the site that extends the functionality. A module usually occupies a secondary portion of the web page and is not considered the primary focus of a page. It can be displayed on different positions and you can choose on which active menu items it should be displayed. Modules are lightweight and flexible extensions. They are used for small bits of the page that are generally less complex and are able to be seen across different components.</translate>
* '''[[S:MyLanguage/Plugin|<translate> Plugins</translate>]]''' <translate> A Plugin manipulates output that is already generated by the system. It typically does not run as separate part of the site. It takes data from other sources (i.e. the content) and manipulates this data before displaying. A plugin typically work behind the scenes.</translate>
* '''[[S:MyLanguage/Languages|<translate> Languages</translate>]]''' <translate> Probably the most basic extensions are languages. In essence the language package files consist of key/value pairs, which provide the translation of static text strings, assigned within the Joomla! source code.</translate>
* '''[[S:MyLanguage/Templates|<translate> Templates</translate>]]''' <translate> A template is basically the design of your Joomla! powered website.</translate>

<translate> Joomla! 4 is constructed using five different applications:</translate>
<translate>
* Installation (used for installing Joomla and have to delete after installation);
* Administrator (backend - used for managing content);
* Public or site (frontend - used for displaying content);
* CLI (used for accessing Joomla on the command line and for cron jobs);
* API (web services - used for creating APIs for machine accessible content);</translate>
<translate>

The installation application is used once. The administrator and public are used through the concept of ''components'' with ''modules''. Each module has a single entry point located in the ''modules'' and accordingly ''administrator/modules'' directory. This entry point is called <tt>''mod_modulename/mod_modulename.php''</tt> (the ''mod_'' prefix is a historical trace). The entry point for the login module is for example ''/mod_login/mod_login.php''.</translate>

<translate>
=== Requirements === 
</translate>
<translate> You need Joomla! 4.x installation available to use for this tutorial ([https://github.com/joomla/joomla-cms/releases Download latest release here])</translate>

<translate> You can download Joomla! 4 at [https://github.com/joomla/joomla-cms/releases GitHub], on the [https://developer.joomla.org/nightly-builds.html Developer website] or you can create a free website at https://launch.joomla.org.</translate>

<translate>

== Creating a simple module/Developing a Basic Module - Part 1 == 
</translate>
<translate> You can see many examples of modules in the standard Joomla! install. For example:</translate>
<translate>
* Menus
* Latest News
* Login form
* and many more.</translate>

<translate> This tutorial will explain how to create a simple module. Through this tutorial you will learn the basic file structure of a Joomlaǃ 4 module. This basic structure can then be expanded to produce more elaborate modules.</translate>

<translate>
=== File Structure === 
</translate>
<translate> There are a few basic files that are used in the standard pattern of module development:</translate>
<translate> * <tt>mod_foo.php</tt> - This file is the main entry point for the module. It will perform any necessary initialization routines, call helper routines to collect any necessary data, and include the template which will display the module output.</translate>
<translate> * <tt>mod_foo.xml</tt> - This file contains information about the module. It defines the files that need to be installed by the Joomla! installer and specifies configuration parameters for the module.</translate>
<translate> * <tt>tmpl/default.php</tt> - This is the module template. This file will take the data collected by mod_foo.php and generate the HTML to be displayed on the page.</translate>
<translate> * <tt>language/en-GB/mod_foo.ini</tt> and <tt>language/en-GB/mod_foo.sys.ini</tt>- This are the files that provide the text in United Kingdom English.</translate>

<translate>

=== Creating mod_foo.php === 
</translate>
<translate> The <tt>mod_foo.php</tt> file will perform following tasks:</translate>
<translate> * Import the class <tt>ModuleHelper</tt> to the current scope. We need it later for displaying the output.</translate>
<translate> * Include the template to display the output.</translate>

<translate> The helper class is imported to our current scope at the begin of the file.</translate>

<source lang="php">use Joomla\CMS\Helper\ModuleHelper;</source>

<translate> Last we include the template to display the output via</translate>

<source lang="php">require ModuleHelper::getLayoutPath('mod_foo', $params->get('layout', 'default'));</source>

<translate>
==== Completed mod_foo.php file ==== 
</translate>
<translate> The complete <tt>mod_foo.php</tt> file is as follows:</translate>

<source lang="php">
<?php
/**
* @package [PACKAGE_NAME]
*
* @author [AUTHOR] <[AUTHOR_EMAIL]>
* @copyright [COPYRIGHT]
* @license GNU General Public License version 2 or later; see LICENSE.txt
* @link [AUTHOR_URL]
*/

// No direct access to this file
defined('_JEXEC') or die;

use Joomla\CMS\Helper\ModuleHelper;

require ModuleHelper::getLayoutPath('mod_foo', $params->get('layout', 'default'));

</source>

<translate> ''Side note''ː In Joomla 3x you usually used a line like <tt>$moduleclass_sfx = htmlspecialchars($params->get('moduleclass_sfx'));</tt>. You don't need this anymore. See this PRː https://github.com/joomla/joomla-cms/pull/17447.</translate>

<translate> The one line that we haven’t explained so far is the first line <tt>defined('_JEXEC') or die;</tt>. This line checks to make sure that this file is being included from the Joomla application. This is necessary to prevent variable injection and other potential security concerns.</translate>

<translate>
=== Creating tmpl/default.php === 
</translate>
<translate> The <tt>default.php</tt> file is the template which displays the module output.</translate>

<translate>
==== Completed tmpl/default.php file ==== 
</translate>
<translate> The code for the tmpl/default.php file is as follows:</translate>

<source lang="php">
<?php
/**
* @package [PACKAGE_NAME]
*
* @author [AUTHOR] <[AUTHOR_EMAIL]>
* @copyright [COPYRIGHT]
* @license GNU General Public License version 2 or later; see LICENSE.txt
* @link [AUTHOR_URL]
*/

// No direct access to this file
defined('_JEXEC') or die;

echo '[PROJECT_NAME]';

</source>

<translate> An important point to note is that the template file has the same scope as the <tt>mod_foo.php</tt> file. It means that a variable can be defined in the <tt>mod_foo.php</tt> file and then used in the template file without any extra declarations or function calls.</translate>

<translate>
=== Creating mod_foo.xml === 
</translate>
<translate> The <tt>mod_foo.xml</tt> file is the installation file. Most entries are self-explanatory.</translate>

<translate>
==== Completed mod_foo.xml file ==== 
</translate>
<translate> The code for the <tt>mod_foo.xml</tt> file is as follows:</translate>

<source lang="xml">

<?xml version="1.0" encoding="utf-8"?>
<extension type="module" version="4.0" client="site" method="upgrade">
<name>MOD_FOO</name>
<creationDate>[DATE]</creationDate>
<author>[AUTHOR]</author>
<authorEmail>[AUTHOR_EMAIL]</authorEmail>
<authorUrl>[AUTHOR_URL]</authorUrl>
<copyright>[COPYRIGHT]</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<version>1.0</version>
<description>MOD_FOO_XML_DESCRIPTION</description>
<files>
<filename module="mod_foo">mod_foo.php</filename>
<folder>tmpl</folder>
<folder>language</folder>
<filename>mod_foo.xml</filename>
</files>
</extension>

</source>

<translate>
=== Creating the language files === 
</translate>
<translate> The files <tt>language/en-GB/mod_foo.ini</tt> and <tt>language/en-GB/mod_foo.sys.ini</tt> are used to translate text in the frontend and in the backend. Note that the language file structure has been updated in Joomla 4, and language prefixes on the individual files in a language folder are no longer required.</translate>

<translate> The code for <tt>language/en-GB/mod_foo.sys.ini</tt> is as follows:</translate>

<source lang="xml">

MOD_FOO="[PROJECT_NAME]"
MOD_FOO_XML_DESCRIPTION="Foo Module"

</source>

<translate> The code for <tt>language/en-GB/mod_foo.ini</tt> is as follows:</translate>

<source lang="xml">

MOD_FOO="[PROJECT_NAME]"
MOD_FOO_XML_DESCRIPTION="Foo Module"

</source>

<translate> The <tt>.sys.ini</tt> file is used to translate the description of the extension upon installation, where as the <tt>.ini</tt> file is used to translate the remaining strings and the description when viewing your extension.</translate>

<translate> More information about language files can be found [[S:MyLanguage/Specification_of_language_files|here]].</translate>

<translate>

== Test your module == 
</translate>
<translate> Now you can zip all files and install them via the Joomla Extension Manager. </translate>
<translate> After that you can choose your module in the module manager, when you create a new site module.</translate>
{{-}}
[[File:moduletutorial1-<translate> en</translate>.png|700px|center]]
{{-}}
[[File:moduletutorial2-<translate> en</translate>.png|700px|center]]

<translate> In the frontend, you will see your module like displayed in the next image.</translate>
{{-}}
[[File:moduletutorial3-<translate> en</translate>.png|700px|center]]

<translate>
== Conclusion == 
</translate>
<translate> Module development for Joomla is a fairly simple, straightforward process. Using the techniques described in this tutorial, an endless variety of modules can be developed with little hassle.</translate>

<translate> You can find boilerplates hereː</translate>
* https://github.com/joomla-extensions/boilerplate/tree/master/module
<translate> The sample files for this Tutorial can be found hereː</translate>
* https://github.com/astridx/boilerplate/tree/tutorial/tutorial/modules

<translate>

== Add a helper class using namespaces - Part 2== 
</translate>

<translate>
=== Requirements === 
</translate>
<translate> You need Joomla! 4.x for this tutorial (as of writing currently Joomla! 4.0.0-alpha6-dev)</translate>

<translate>
== Namespaces == 
</translate>
<translate> With PHP 5.3, the namespaces came into their own. In other programming languages for a long time in use, these small structures now also help us with the clarity of our code.</translate>

<translate> Namespaces are separate areas in which certain logical things (in our case, classes, interfaces, functions, and constants) can live. These areas provide encapsulation of the code and prevent name conflicts.</translate>

<translate> Let's take a look how to use them in Joomla 4. We use the helper file for this.</translate>

<translate>
=== File Structure === 
</translate>
<translate> We will create/change the following files:</translate>
<translate>
* <code>Helper/FooHelper.php</code> - This is the file we use here as an example. We have to create it.
* <code>mod_foo.php</code> - In this file, we will mainly load the namespace.
* <code>tmpl/default.php</code> - In this file, we will demonstrate how the data of a helper can be displayed.
* <code>mod_foo.xml</code> - We create a new directory with a new file. This must be installed during the installation. For this we have to specify them in this file.</translate>

<translate>
=== Creating Helper/FooHelper.php === 
</translate>
<translate> Our new helper class should belong to a namespace. We achieve this with the following code. It is important, that this line is at the beginning of the file.</translate>

<source lang="php">namespace Joomla\Module\Foo\Site\Helper;</source>

<translate> Then we create a simple class with a simple method. Of course you can do a lot more here. Take a look at the Joomla core methods. Here are many examples. They show you first-hand what options you have.</translate>

<translate>
==== Completed Helper/FooHelper.php ==== 
</translate>
<translate> The complete <tt>FooHelper.php</tt> file is as follows:</translate>

<source lang="php">
<?php
/**
* @package Joomla.Site
* @subpackage mod_foo
*
* @copyright Copyright (C) 2005 - 2019 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
*/

namespace Joomla\Module\Foo\Site\Helper;

// No direct access to this file
defined('_JEXEC') or die;

/**
* Helper for mod_foo
*
* @since 4.0
*/
class FooHelper
{
/**
* Retrieve foo test
*
* @param Registry $params The module parameters
* @param CMSApplication $app The application
*
* @return array
*/
public static function getText()
{
return 'FooHelpertest';
}
}

</source>

<translate>

=== Editing mod_foo.php === 
</translate>
<translate> Our new helper class is imported to our current scope at the beginning of the file.</translate>

<source lang="php">use Joomla\Module\Foo\Site\Helper\FooHelper;</source>

<translate> Last use the helper file for testing if it is loaded correctlyː</translate>

<source lang="php">$test = FooHelper::getText($params, $app);</source>

<translate>
==== Completed mod_foo.php file ==== 
</translate>
<translate> The complete <tt>mod_foo.php</tt> file is as follows:</translate>

<source lang="php">

<?php
/**
* @package [PACKAGE_NAME]
*
* @author [AUTHOR] <[AUTHOR_EMAIL]>
* @copyright [COPYRIGHT]
* @license GNU General Public License version 2 or later; see LICENSE.txt
* @link [AUTHOR_URL]
*/

// No direct access to this file
defined('_JEXEC') or die;

use Joomla\CMS\Helper\ModuleHelper;
use Joomla\Module\Foo\Site\Helper\FooHelper;

$test = FooHelper::getText();

require ModuleHelper::getLayoutPath('mod_foo', $params->get('layout', 'default'));

</source>

<translate>
=== Editing tmpl/default.php === 
</translate>
<translate> In this file you make only a small change to demonstrate in the frontend that your helper file is working properly. You only add the value of the variable at the end of the current output.</translate>

<source lang="php">echo '[PROJECT_NAME]' . $test;</source>

<translate>
==== Completed tmpl/default.php ==== 
</translate>
<translate> The complete <tt>tmpl/default.php</tt> file is as follows:</translate>

<source lang="php">
<?php
/**
* @package [PACKAGE_NAME]
*
* @author [AUTHOR] <[AUTHOR_EMAIL]>
* @copyright [COPYRIGHT]
* @license GNU General Public License version 2 or later; see LICENSE.txt
* @link [AUTHOR_URL]
*/

// No direct access to this file
defined('_JEXEC') or die;

echo '[PROJECT_NAME]' . $test;

</source>

<translate>
=== Editing mod_foo.xml === 
</translate>
<translate> First you have to add a line, so that the namespace is set automatically in Joomla. After this change, you have to re-install your module. A simple change in an already installed module is not enough. If you are doing local development you can also delete the files libraries/autoload_psr4.php and it will automatically be re-created. After inserting and installing, the namespace is known by the loader <tt>JPATH_LIBRARIES . '/autoload_psr4.php'</tt>.</translate>

<source lang="xml"><namespace>Joomla\Module\Foo</namespace></source>

<translate> Joomla! should copy your helper file when installing the module. So Joomla! needs to know your helper file. For this, you need to add the following line to your XML file.</translate>

<source lang="xml"><folder>Helper</folder></source>

<translate>
==== Completed mod_foo.xml ==== 
</translate>
<translate> The complete <tt>mod_foo.xml</tt> file is as follows:</translate>

<source lang="xml">

<?xml version="1.0" encoding="utf-8"?>
<extension type="module" version="4.0" client="site" method="upgrade">
<name>MOD_FOO</name>
<creationDate>[DATE]</creationDate>
<author>[AUTHOR]</author>
<authorEmail>[AUTHOR_EMAIL]</authorEmail>
<authorUrl>[AUTHOR_URL]</authorUrl>
<copyright>[COPYRIGHT]</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<version>1.0</version>
<description>MOD_FOO_XML_DESCRIPTION</description>
<namespace>Joomla\Module\Foo</namespace>
<files>
<filename module="mod_foo">mod_foo.php</filename>
<folder>tmpl</folder>
<folder>Helper</folder>
<folder>language</folder>
<filename>mod_foo.xml</filename>
</files>
</extension>

</source>

<translate>
== Test your module == 
</translate>
<translate> Now you can zip all files and install them via the Joomla Extension Manager.</translate>
<translate> After that you can choose your module in the module manager, when you create a new site module.</translate>

<translate> In the frontend you will see your module like displayed in the next image. The text from your helper file is displayed.</translate>
{{-}}
[[File:moduletutorial23-<translate> en</translate>.png|700px|center]]

<translate>
== Conclusion == 
</translate>
<translate> As you can see, once you get a bit into the namespaces, they are not that complicated anymore. In big projects they can bring a lot of benefits. However, we should plan namespaces, as otherwise it will soon be more time-consuming.</translate>

<translate> You can find boilerplates hereː</translate>
* https://github.com/joomla-extensions/boilerplate/tree/master/module
<translate> The sample files for this Tutorial can be found hereː</translate>
* https://github.com/astridx/boilerplate/tree/tutorial/tutorial/modules

<translate>

== Customizationː Add parameters via form fields - Part 3 == 
</translate>

<translate>
=== Requirements === 
</translate>
<translate> You need Joomla! 4.x for this tutorial (as of writing currently Joomla! 4.0.0-alpha6-dev)</translate>

<translate>
== Customization with form fields and parameters == 
</translate>
<translate> Form fields give a great deal of customization in Joomla and for modules are the sole way of allowing the user to tweak the module to the needs of their site.</translate>

<translate> In this case we are going to extend our previous example using a url field for inserting a domain that we can use as link in the front end. To allow this to happen we will use the [[S:MyLanguage/URL_form_field_type|URL Form Field]] type.</translate>

<translate> After that, we insert parameters that allow to use standard functionality of Joomla.</translate>

<translate> Let's take a look on how to use them in Joomla 4.</translate>

<translate>
=== File Structure === 
</translate>
<translate> We will change the following files:</translate>
<translate>
* <tt>mod_foo.xml</tt> - This is the file where we add the fields.
* <tt>tmpl/default.php</tt> - In this file demonstrate how the data of a field can be used.
* <tt>language/en-GB/en-GB.mod_foo.ini</tt> - Here we use a language string so that the field can be labeled correctly in different languages.</translate>

<translate>
=== Editing mod_foo.xml === 
</translate>
<translate> First we set a custom parameter.</translate>

<source lang="xml">

<field
name="domain"
type="url"
label="MOD_FOO_FIELD_URL_LABEL"
filter="url"
/>

</source>

<translate> Then we insert Joomla default fields, so that we can use cache, moduleclass-suffix and layouts.</translate>

<source lang="xml">
<field
name="layout"
type="modulelayout"
label="JFIELD_ALT_LAYOUT_LABEL"
class="custom-select"
/>

<field
name="moduleclass_sfx"
type="textarea"
label="COM_MODULES_FIELD_MODULECLASS_SFX_LABEL"
rows="3"
/>

<field
name="cache"
type="list"
label="COM_MODULES_FIELD_CACHING_LABEL"
default="0"
>
<option value="1">JGLOBAL_USE_GLOBAL</option>
<option value="0">COM_MODULES_FIELD_VALUE_NOCACHING</option>
</field>

<field
name="cache_time"
type="number"
label="COM_MODULES_FIELD_CACHE_TIME_LABEL"
default="0"
/>

<field
name="cachemode"
type="hidden"
default="itemid"
>
<option value="itemid"></option>
</field>

</source>

<translate>
==== Completed mod_foo.xml ==== 
</translate>
<translate> The complete <tt>mod_foo.xml</tt> file is as follows:</translate>

<source lang="xml">

<?xml version="1.0" encoding="utf-8"?>
<extension type="module" version="4.0" client="site" method="upgrade">
<name>MOD_FOO</name>
<creationDate>[DATE]</creationDate>
<author>[AUTHOR]</author>
<authorEmail>[AUTHOR_EMAIL]</authorEmail>
<authorUrl>[AUTHOR_URL]</authorUrl>
<copyright>[COPYRIGHT]</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<version>1.0</version>
<description>MOD_FOO_XML_DESCRIPTION</description>
<namespace>Joomla\Module\Foo</namespace>
<files>
<filename module="mod_foo">mod_foo.php</filename>
<folder>tmpl</folder>
<folder>Helper</folder>
<folder>language</folder>
<filename>mod_foo.xml</filename>
</files>
<config>
<fields name="params">
<fieldset name="basic">
<field
name="domain"
type="url"
label="MOD_FOO_FIELD_URL_LABEL"
filter="url"
/>
</fieldset>
<fieldset name="advanced">
<field
name="layout"
type="modulelayout"
label="JFIELD_ALT_LAYOUT_LABEL"
class="custom-select"
/>
<field
name="moduleclass_sfx"
type="textarea"
label="COM_MODULES_FIELD_MODULECLASS_SFX_LABEL"
rows="3"
/>
<field
name="cache"
type="list"
label="COM_MODULES_FIELD_CACHING_LABEL"
default="0"
>
<option value="1">JGLOBAL_USE_GLOBAL</option>
<option value="0">COM_MODULES_FIELD_VALUE_NOCACHING</option>
</field>
<field
name="cache_time"
type="number"
label="COM_MODULES_FIELD_CACHE_TIME_LABEL"
default="0"
/>
<field
name="cachemode"
type="hidden"
default="itemid"
>
<option value="itemid"></option>
</field>
</fieldset>
</fields>
</config>
</extension>

</source>

<translate>
=== Editing tmpl/default.php === 
</translate>
<translate> We can use the value of the parameter for creating a hyperlink in the frontend. We can access the value via the variable $params.</translate>

<source lang="php">$domain = $params->get('domain', 'https://www.joomla.org');</source>

<translate> Later we set use this value for creating the hyperlink.</translate>

<source lang="php">

<a href="<?php echo $domain; ?>">
<?php echo '[PROJECT_NAME]' . $test; ?>
</a>

</source>

<translate>
==== Completed tmpl/default.php file ==== 
</translate>
<translate> The complete <tt>tmpl/default.php</tt> file is as follows:</translate>

<source lang="php">

<?php
/**
* @package [PACKAGE_NAME]
*
* @author [AUTHOR] <[AUTHOR_EMAIL]>
* @copyright [COPYRIGHT]
* @license GNU General Public License version 2 or later; see LICENSE.txt
* @link [AUTHOR_URL]
*/

// No direct access to this file
defined('_JEXEC') or die;

$domain = $params->get('domain', 'https://www.joomla.org');
?>

<a href="<?php echo $domain; ?>">
<?php echo '[PROJECT_NAME]' . $test; ?>
</a>

</source>

<translate>
=== Editing language/en-GB/en-GB.mod_foo.ini === 
</translate>
<translate> Here we can specify the text for the English version of the field label.</translate>

<source lang="php">MOD_FOO_FIELD_URL_LABEL="Url"</source>

<translate>
==== Completed language/en-GB/en-GB.mod_foo.ini ==== 
</translate>
<translate> The complete <tt>language/en-GB/en-GB.mod_foo.ini</tt> file is as follows:</translate>

<source lang="php">

MOD_FOO="[PROJECT_NAME]"
MOD_FOO_XML_DESCRIPTION="Foo Module"
MOD_FOO_FIELD_URL_LABEL="Url"

</source>

<translate>
== Test your module == 
</translate>
<translate> Now you can zip all files and install them via the Joomla Extension Manager.</translate>
<translate> After that you can choose your module in the module manager, when you create a new site module.</translate>

<translate> In the backend, you will see your module like displayed in the next image.</translate>

<translate> In the basic tab, you will see the custom field where you can insert a domain. The text for the label is fetched from the language file.</translate>
{{-}}
[[File:moduletutorial31-<translate> en</translate>.png|700px|center]]

<translate> In the advanced tab, you will see all default options except the cache mode because of this is a hidden field.</translate>
{{-}}
[[File:moduletutorial32-<translate> en</translate>.png|700px|center]]

<translate> In the frontend, you will see your module like displayed in the next image. The text form your helper file is displayed and you should see a hyperlink.</translate>
{{-}}
[[File:moduletutorial33-<translate> en</translate>.png|700px|center]]

<translate>
== Conclusion == 
</translate>
<translate> Form fields give the user an easy way to customize the module to their sites settings. This allows the modules scope to be increased.</translate>

<translate> You can find boilerplates hereː</translate>
* https://github.com/joomla-extensions/boilerplate/tree/master/module
<translate> The sample files for this Tutorial can be found hereː</translate>
* https://github.com/astridx/boilerplate/tree/tutorial/tutorial/modules
<translate> See this issue for possible future changes:</translate>
* https://github.com/joomla/joomla-cms/pull/23553

<translate>

== Use Install, Update and Uninstall script - Part 4 == 
</translate>

<translate>
=== Requirements === 
</translate>
<translate> You need Joomla! 4.x for this tutorial (as of writing currently Joomla! 4.0.0-alpha6-dev)</translate>

<translate>
=== Scripts === 
</translate>
<translate> Installing, updating and uninstalling a module may require additional operations that cannot be achieved by the basic operations described in the main XML file. Joomla offers a new approach to solve this problem. It consists in using a PHP script file containing a class using five methods:</translate>
<translate>
* preflight which is executed before install and update
* install
* update
* uninstall
* postflight which is executed after install and update</translate>

<translate> Let's take a look how to use them in Joomla 4. We use the helper file for this.</translate>

<translate>
=== File Structure === 
</translate>
<translate> We will create/change the following files:</translate>
<translate>
* <tt>script.php</tt> - This is the file we use here as an example. We have to create it.
* <tt>language/en-GB/en-GB.mod_foo.sys.ini</tt> - In this file we will add text.
* <tt>mod_foo.xml</tt> - We create a new file. This must be installed during the installation. For this we have to specify it in this file.</translate>

<translate>
=== Creating script.php === 
</translate>
<translate> Writing an extension script consists in declaring a class whose name is <tt>mod_ModuleNameInstallerScript</tt> with these 5 methods. See the comments in the file for more information. In this comments I explain when a method is called.</translate>

<translate> In this example, I only use text to show when which method will be executed. In addition, I show you how to check the minimum requirements. Of course you can do much more. For example, you can delete files that are no longer needed in a new version of your module. This can be seen in the file. Another idea for this file is to create sample content, to show a success message with the current installed version number or you can redirect after a successful installation to the page with the module settings.</translate>

<translate>
==== Completed script.php ==== 
</translate>
<translate> The complete <tt>script.php</tt> file is as follows:</translate>

<source lang="php">

<?php
/**
* @package [PACKAGE_NAME]
*
* @author [AUTHOR] <[AUTHOR_EMAIL]>
* @copyright [COPYRIGHT]
* @license GNU General Public License version 2 or later; see LICENSE.txt
* @link [AUTHOR_URL]
*/

// No direct access to this file
defined('_JEXEC') or die;

use Joomla\CMS\Language\Text;
use Joomla\CMS\Log\Log;

/**
* Script file of Foo module
*/
class mod_fooInstallerScript {

/**
* Extension script constructor.
*
* @return void
*/
public function __construct() {
$this->minimumJoomla = '4.0';
$this->minimumPhp = JOOMLA_MINIMUM_PHP;
}

/**
* Method to install the extension
*
* @param InstallerAdapter $parent The class calling this method
*
* @return boolean True on success
*/
function install($parent) {
echo Text::_('MOD_FOO_INSTALLERSCRIPT_INSTALL');

return true;
}

/**
* Method to uninstall the extension
*
* @param InstallerAdapter $parent The class calling this method
*
* @return boolean True on success
*/
function uninstall($parent) {
echo Text::_('MOD_FOO_INSTALLERSCRIPT_UNINSTALL');

return true;
}

/**
* Method to update the extension
*
* @param InstallerAdapter $parent The class calling this method
*
* @return boolean True on success
*/
function update($parent) {
echo Text::_('MOD_FOO_INSTALLERSCRIPT_UPDATE');

return true;
}

/**
* Function called before extension installation/update/removal procedure commences
*
* @param string $type The type of change (install, update or discover_install, not uninstall)
* @param InstallerAdapter $parent The class calling this method
*
* @return boolean True on success
*/
function preflight($type, $parent) {
// Check for the minimum PHP version before continuing
if (!empty($this->minimumPhp) && version_compare(PHP_VERSION, $this->minimumPhp, '<')) {
Log::add(Text::sprintf('JLIB_INSTALLER_MINIMUM_PHP', $this->minimumPhp), Log::WARNING, 'jerror');

return false;
}

// Check for the minimum Joomla version before continuing
if (!empty($this->minimumJoomla) && version_compare(JVERSION, $this->minimumJoomla, '<')) {
Log::add(Text::sprintf('JLIB_INSTALLER_MINIMUM_JOOMLA', $this->minimumJoomla), Log::WARNING, 'jerror');

return false;
}

echo Text::_('MOD_FOO_INSTALLERSCRIPT_PREFLIGHT');
echo $this->minimumJoomla . ' ' . $this->minimumPhp;

return true;
}

/**
* Function called after extension installation/update/removal procedure commences
*
* @param string $type The type of change (install, update or discover_install, not uninstall)
* @param InstallerAdapter $parent The class calling this method
*
* @return boolean True on success
*/
function postflight($type, $parent) {
echo Text::_('MOD_FOO_INSTALLERSCRIPT_POSTFLIGHT');

return true;
}
}

</source>

<translate>
=== Editing language/en-GB/en-GB.mod_foo.sys.ini === 
</translate>
<translate> There is not much to explain here. Write the text for the translation into this file.</translate>

<translate>
==== Completed language/en-GB/en-GB.mod_foo.sys.ini file ==== 
</translate>
<translate> The complete <tt>language/en-GB/en-GB.mod_foo.sys.ini</tt> file is as follows:</translate>

<source lang="php">

MOD_FOO="[PROJECT_NAME]"
MOD_FOO_XML_DESCRIPTION="Foo Module"
MOD_FOO_INSTALLERSCRIPT_PREFLIGHT="Anything here happens before the installation/update/uninstallation of the module"
MOD_FOO_INSTALLERSCRIPT_UPDATE="The module has been updated"
MOD_FOO_INSTALLERSCRIPT_UNINSTALL="The module has been uninstalled"
MOD_FOO_INSTALLERSCRIPT_INSTALL="The module has been installed"
MOD_FOO_INSTALLERSCRIPT_POSTFLIGHT="Anything here happens after the installation/update/uninstallation of the module"

</source>

<translate>
=== Editing mod_foo.xml === 
</translate>
<translate> You have to add a line, so that the script is called automatically in Joomla.</translate>

<source lang="xml"><scriptfile>script.php</scriptfile></source>

<translate>
==== Completed mod_foo.xml ==== 
</translate>
<translate> The complete <tt>mod_foo.xml</tt> file is as follows:</translate>

<source lang="xml">

<?xml version="1.0" encoding="utf-8"?>
<extension type="module" version="4.0" client="site" method="upgrade">
<name>MOD_FOO</name>
<creationDate>[DATE]</creationDate>
<author>[AUTHOR]</author>
<authorEmail>[AUTHOR_EMAIL]</authorEmail>
<authorUrl>[AUTHOR_URL]</authorUrl>
<copyright>[COPYRIGHT]</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<version>1.0</version>
<description>MOD_FOO_XML_DESCRIPTION</description>
<namespace>Joomla\Module\Foo</namespace>
<scriptfile>script.php</scriptfile>
<files>
<filename module="mod_foo">mod_foo.php</filename>
<folder>tmpl</folder>
<folder>Helper</folder>
<folder>language</folder>
<filename>mod_foo.xml</filename>
</files>
<config>
<fields name="params">
<fieldset name="basic">
<field
name="domain"
type="url"
label="MOD_FOO_FIELD_URL_LABEL"
filter="url"
/>
</fieldset>
<fieldset name="advanced">
<field
name="layout"
type="modulelayout"
label="JFIELD_ALT_LAYOUT_LABEL"
class="custom-select"
/>
<field
name="moduleclass_sfx"
type="textarea"
label="COM_MODULES_FIELD_MODULECLASS_SFX_LABEL"
rows="3"
/>
<field
name="cache"
type="list"
label="COM_MODULES_FIELD_CACHING_LABEL"
default="0"
>
<option value="1">JGLOBAL_USE_GLOBAL</option>
<option value="0">COM_MODULES_FIELD_VALUE_NOCACHING</option>
</field>
<field
name="cache_time"
type="number"
label="COM_MODULES_FIELD_CACHE_TIME_LABEL"
default="0"
/>
<field
name="cachemode"
type="hidden"
default="itemid"
>
<option value="itemid"></option>
</field>
</fieldset>
</fields>
</config>
</extension>
</source>

<translate>
== Test your module == 
</translate>
<translate> Now you can zip all files and install them via the Joomla Extension Manager.</translate>
<translate> Immediately after the installation, you will see the following information. This you had entered in the script so.</translate>
{{-}}
[[File:moduletutorial14-<translate> en</translate>.png|700px|center]]

<translate>
== Conclusion == 
</translate>
<translate> As you can see, Joomla offers you a lot to make your extension easy to use - right from the start.</translate>

<translate> You can find boilerplates hereː</translate>
* https://github.com/joomla-extensions/boilerplate/tree/master/module
<translate> The sample files for this Tutorial can be found hereː</translate>
* https://github.com/astridx/boilerplate/tree/tutorial/tutorial/modules

<translate>

== Use Joomla Updaterː Adding Auto Update - Part 5 == 
</translate>

<translate>
=== Requirements === 
</translate>
<translate> You need Joomla! 4.x for this tutorial (as of writing currently Joomla! 4.0.0-alpha6-dev)</translate>

<translate>
=== Joomla Updater === 
</translate>
<translate> The first thing to do is to read the [[S:MyLanguage/J2.5:Managing_Component_Updates|Managing Component Upgrades with Joomla 2.5 - Part 1]] tutorial to give an idea of how the upgrade process works in Joomlaǃ. Whilst written for 2.5 the process hasn't changed. Also read [[S:MyLanguage/Deploying_an_Update_Server|Deploying an update server]] - this is what we'll be implementing in this tutorial.</translate>

<translate>
=== File Structure === 
</translate>
<translate> We will create/change the following files:</translate>
<translate> * <tt>mod_foo.xml</tt> - The only way to update our existing module is to add in a update server - for example <tt><nowiki>http://www.example.com/foo_update.xml</nowiki></tt> - into the xml file.</translate>
<translate> * <tt>foo_update.xml</tt> - Then we have to create the XML file for the update server at <tt><nowiki>http://www.example.com/foo_update.xml</nowiki></tt> to let Joomla know an update is available.</translate>

<translate>
==== Editing mod_foo.xml ==== 
</translate>
<translate> To add our update server, we need to insert the following lines in your XML-Fileː</translate>

<source lang="php">

<updateservers>
<server type="extension" priority="1" name="[PROJECT_NAME]">https://www.example.com/mod_foo.xml</server>
</updateservers>

</source>

<translate>
==== Completed mod_foo.xml ==== 
</translate>
<translate> The complete <tt>mod_foo.xml</tt> file is as follows:</translate>

<source lang="xml">

<?xml version="1.0" encoding="utf-8"?>
<extension type="module" version="4.0" client="site" method="upgrade">
<name>MOD_FOO</name>
<creationDate>[DATE]</creationDate>
<author>[AUTHOR]</author>
<authorEmail>[AUTHOR_EMAIL]</authorEmail>
<authorUrl>[AUTHOR_URL]</authorUrl>
<copyright>[COPYRIGHT]</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<version>1.0</version>
<description>MOD_FOO_XML_DESCRIPTION</description>
<namespace>Joomla\Module\Foo</namespace>
<files>
<filename module="mod_foo">mod_foo.php</filename>
<folder>tmpl</folder>
<folder>Helper</folder>
<folder>language</folder>
<filename>mod_foo.xml</filename>
</files>
<updateservers>
<server type="extension" priority="1" name="[PROJECT_NAME]">https://www.example.com/mod_foo.xml</server>
</updateservers>
<config>
<fields name="params">
<fieldset name="basic">
<field
name="domain"
type="url"
label="MOD_FOO_FIELD_URL_LABEL"
filter="url"
/>
</fieldset>
<fieldset name="advanced">
<field
name="layout"
type="modulelayout"
label="JFIELD_ALT_LAYOUT_LABEL"
class="custom-select"
/>
<field
name="moduleclass_sfx"
type="textarea"
label="COM_MODULES_FIELD_MODULECLASS_SFX_LABEL"
rows="3"
/>
<field
name="cache"
type="list"
label="COM_MODULES_FIELD_CACHING_LABEL"
default="0"
>
<option value="1">JGLOBAL_USE_GLOBAL</option>
<option value="0">COM_MODULES_FIELD_VALUE_NOCACHING</option>
</field>
<field
name="cache_time"
type="number"
label="COM_MODULES_FIELD_CACHE_TIME_LABEL"
default="0"
/>
<field
name="cachemode"
type="hidden"
default="itemid"
>
<option value="itemid"></option>
</field>
</fieldset>
</fields>
</config>
</extension>

</source>

<translate> So now that Joomlaǃ is searching for updates to our extension - let's create one to test out our process. But first we need to create the file <tt>foo_update.xml</tt>. So far we have only described the update server. We do not know yet if there is an update. In the file <tt>foo_update.xml</tt> we indicate when a new version is published and where it can be downloaded.</translate>

<translate>
=== Creating foo_update.xml === 
</translate>
<translate> Now we have to create the XML file at <tt><nowiki>http://www.example.com/foo_update.xml</nowiki></tt> to let Joomla know an update is available.</translate>

<translate>
==== Completed foo_update.xml ==== 
</translate>
<translate> The complete <tt>foo_update.xml</tt> file is as follows:</translate>

<source lang="xml">

<?xml version="1.0" ?>
<updates>
<update>
<name>Foo</name>
<description>This is mod_foo 1.0.1</description>
<element>mod_foo</element>
<type>module</type>
<version>1.0.1</version>
<downloads>
<downloadurl type="full" format="zip">http://www.example.com/mod_foo_101.zip</downloadurl>
</downloads>
<maintainer>Joomla</maintainer>
<maintainerurl>http://www.example.com</maintainerurl>
<targetplatform name="joomla" version="4.0"/>
<client>site</client>
</update>
</updates>

</source>

<translate> After uploading this file to the address <tt><nowiki>https://www.example.com/mod_foo.xml</nowiki></tt> the update will be displayed in the Joomla backend.</translate>

<translate>
=== Test your module update === 
</translate>
<translate> Create a copy of the module as it is now. Then let's update the version number to 1.0.1. Now you can zip all files. After that you should load your zip to the URL <tt><nowiki>http://www.example.com/mod_foo_101.zip</nowiki></tt>. Now you can update your module via the Joomla Updater.</translate>

<translate>
=== Commercial Modules === 
</translate>
<translate> Note that in our files we have linked to the extensions updates xml file. And from that xml file we have a location for the zip of the module. This means that if someone was to track this backwards they could find the physical source of your modules zip file. If you don't do like this, you can find a solution in this PRː https://github.com/joomla/joomla-cms/pull/15185 .</translate>

<translate>
=== Conclusion === 
</translate>
<translate> With the Joomlaǃ updater, you can easily reach all users and tell them that there is a new version. Even the update itself is easy.</translate>

<translate> Each extension should use an update server. Especially for security reasons.</translate>

<translate> You can find boilerplates hereː</translate>
* https://github.com/joomla-extensions/boilerplate/tree/master/module
<translate> The sample files for this Tutorial can be found hereː</translate>
* https://github.com/astridx/boilerplate/tree/tutorial/tutorial/modules

<noinclude>
[[Category:Beginner Development{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]
[[Category:Tutorials in a Series{{#translation:}}]]
[[Category:Development{{#translation:}}]]
[[Category:Module Development{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Joomla! 4.0{{#translation:}}]]
</noinclude>