https://docs.sandbox.joomla.org/api.php?action=feedcontributions&feedformat=atom&user=Wilsonge 2026-08-07T11:52:50Z User contributions MediaWiki 1.43.0 https://docs.sandbox.joomla.org/index.php?title=How_to_add_breadcrumbs&diff=1034201 2025-01-26T16:33:16Z

<p>Wilsonge: Hardcode language?</p> <hr /> <div>{{version/tutor|2.5,3.1}}<br /> {{disambig}}<br /> ===What is a breadcrumb?===<br /> Breadcrumbs are nice way to display the connection from the root. It gives you a hierarchical representation with click able links so that user can visit upper links easily. Breadcrumbs can be added in templates by using the object returned by &lt;source lang=&quot;php&quot;&gt;JFactory::getApplication()-&gt;getPathWay()&lt;/source&gt;. The member function addItem() allows to add a breadcrumb with the title of choice.<br /> <br /> ===Developer Tutorials===<br /> {{other versions/navbox/en|The '''{{PAGENAME}}''' Tutorial is available in these versions:-| version}}<br /> <br /> [[Category:Component Development]]<br /> [[Category:Tutorials]]</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Template:Basic_button&diff=1034200 2025-01-26T16:17:51Z

<p>Wilsonge: </p> <hr /> <div>{{#widget:Basic button external<br /> |url={{ localurl:{{{1|Main Page}}} }}<br /> |class={{{class|}}}<br /> |text={{{2|{{{1|Click}}} }}}}}<br /> &lt;noinclude&gt;<br /> {{documentation}}&lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Template:Basic_button_external&diff=1034199 2025-01-26T16:16:56Z

<p>Wilsonge: </p> <hr /> <div>{{#widget:Basic button external<br /> |url={{{1|https://docs.joomla.org}}}<br /> |class={{{class|}}}<br /> |text={{{2|{{{1|Click}}} }}}}}<br /> &lt;noinclude&gt;<br /> {{documentation}}&lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Widget:Basic_button_external&diff=1034198 2025-01-26T16:08:47Z

<p>Wilsonge: Fix extra html</p> <hr /> <div>&lt;noinclude&gt;<br /> This widget allows you to add '''[http://www.google.com/calendar/embedhelper Google Calendar]''' widget to a page.<br /> <br /> To insert this widget, use the following code:<br /> <br /> &lt;pre style=&quot;width:100%;&quot;&gt;<br /> &lt;nowiki&gt;{{#widget:&lt;/nowiki&gt;Basic button external&lt;nowiki&gt;<br /> |url=https://tm.joomla.org<br /> |id=content-button<br /> |class=foo<br /> |text=Click me<br /> }}&lt;/nowiki&gt;<br /> &lt;/pre&gt;<br /> <br /> == Available Parameters ==<br /> TODO!<br /> &lt;/noinclude&gt;&lt;includeonly&gt;&lt;a href=&quot;&lt;!--{$url|escape:'url'}--&gt;&quot; id=&quot;content-button&quot; class=&quot;button&lt;!--{if isset($class)}--&gt; &lt;!--{$class|escape:'html'}--&gt; &lt;!--{/if}--&gt;&quot; target=&quot;_blank&quot;&gt;&lt;!--{$text|escape:'html'}--&gt;&lt;/a&gt;&lt;/includeonly&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Template:Basic_button_external&diff=1034197 2025-01-26T16:07:45Z

<p>Wilsonge: Migrate to widget</p> <hr /> <div>{{#widget:Basic button external<br /> |url={{{1|https://docs.joomla.org}}}<br /> |class={{{class|}}}<br /> |text={{{2|{{{1|Click}}} }}}}}<br /> &lt;noinclude&gt;<br /> This template is deprecated and available for migration purposes please use the widget directly<br /> {{documentation}}&lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Widget:Basic_button_external&diff=1034196 2025-01-26T16:06:15Z

<p>Wilsonge: Basic button external moved to widget</p> <hr /> <div>&lt;noinclude&gt;<br /> This widget allows you to add '''[http://www.google.com/calendar/embedhelper Google Calendar]''' widget to a page.<br /> <br /> To insert this widget, use the following code:<br /> <br /> &lt;pre style=&quot;width:100%;&quot;&gt;<br /> &lt;nowiki&gt;{{#widget:&lt;/nowiki&gt;Basic button external&lt;nowiki&gt;<br /> |url=https://tm.joomla.org<br /> |id=content-button<br /> |class=foo<br /> |text=Click me<br /> }}&lt;/nowiki&gt;<br /> &lt;/pre&gt;<br /> <br /> == Available Parameters ==<br /> TODO!<br /> &lt;/noinclude&gt;&lt;includeonly&gt;&lt;a href=&quot;&lt;!--{$url|escape:'url'}--&gt;&quot; id=&quot;content-button&quot; class=&quot;button &lt;!--{if isset($class)}--&gt; style=&quot;&lt;!--{$class|escape:'html'}--&gt;&quot;&lt;!--{/if}--&gt;&quot; target=&quot;_blank&quot;&gt;&lt;!--{$text|escape:'html'}--&gt;&lt;/a&gt;&lt;/includeonly&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Template:Basic_button_external&diff=1034195 2025-01-26T15:59:50Z

<p>Wilsonge: Revert back to original</p> <hr /> <div>{{#tag:html|&lt;a href=&quot;{{{1|https://docs.joomla.org}}}&quot; id=&quot;content-button&quot; class=&quot;button {{{class|}}}&quot; target=&quot;_blank&quot;&gt;{{{2|{{{1|Click}}} }}}&lt;/a&gt;}}&lt;noinclude&gt;{{documentation}}</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Template:Basic_button_external&diff=1034194 2025-01-26T15:50:32Z

<p>Wilsonge: And again</p> <hr /> <div>&lt;a href=&quot;{{{1|https://docs.joomla.org}}} id=&quot;content-button&quot; class=&quot;button {{{#if:{{{2}}}|{{{2}}}|}}}&quot; target=&quot;_blank&quot;&gt;{{{3|Click}}}&lt;/a&gt;&lt;noinclude&gt;{{documentation}}<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Template:Basic_button_external&diff=1034193 2025-01-26T15:33:17Z

<p>Wilsonge: Another try</p> <hr /> <div>&lt;a href=&quot;{{{1|https://docs.joomla.org}}} id=&quot;content-button&quot; class=&quot;button {{#if:{{{2}}}|{{{2}}}|}}&quot; target=&quot;_blank&quot;&gt;{{{3|{{{4|Click}}} }}}&lt;/span&gt;&lt;noinclude&gt;{{documentation}}<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Template:Basic_button_external&diff=1034192 2025-01-26T15:30:36Z

<p>Wilsonge: Second pass</p> <hr /> <div>&lt;a href=&quot;{{1|https://docs.joomla.org}}&quot; id=&quot;content-button&quot; class=&quot;button {{class|}}&quot; target=&quot;_blank&quot;&gt;{{2|{{1|Click}} }}&lt;/a&gt;&lt;noinclude&gt;{{documentation}}<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Template:Basic_button_external&diff=1034191 2025-01-26T15:29:42Z

<p>Wilsonge: Remove html wrapper</p> <hr /> <div>&lt;a href=&quot;{{{1|https://docs.joomla.org}}}&quot; id=&quot;content-button&quot; class=&quot;button {{{class|}}}&quot; target=&quot;_blank&quot;&gt;{{{2|{{{1|Click}}} }}}&lt;/a&gt;&lt;noinclude&gt;{{documentation}}<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Template:Icon&diff=1034190 2025-01-26T15:25:31Z

<p>Wilsonge: Update to avoid html tag?</p> <hr /> <div>&lt;span class=&quot;fa fa-{{{1|info-circle}}} {{#if:{{{2}}}|fa-{{{2}}}|}}&quot; style=&quot;color:{{{3|#000}}};&quot;&gt;&lt;/span&gt;&lt;noinclude&gt;{{documentation}}<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Main_Page&diff=1015191 2023-10-06T13:49:53Z

<p>Wilsonge: Remove J3 links</p> <hr /> <div>&lt;div class=&quot;row&quot;&gt;<br /> &lt;div class=&quot;large-12 small-12 columns text-center hide-for-small&quot;&gt;<br /> &lt;span style=&quot;font-size:2.5em;&quot;&gt;'''Joomla!'''&lt;span style=&quot;font-size:.4em; vertical-align:super;&quot;&gt;&lt;sup&gt;&amp;reg;&lt;sup&gt;&lt;/span&gt;&lt;/span&gt;{{-}}<br /> [[File:Joomla_logo.png‎|80px|center]]{{-}}<br /> &lt;/div&gt;<br /> &lt;div class=&quot;large-12 small-12 columns text-center hide-for-small&quot;&gt;<br /> &lt;span style=&quot;font-size:2.5em;font-weight:bold;&quot;&gt;&lt;translate&gt;&lt;!--T:1--&gt;<br /> Documentation&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;div class=&quot;large-11 large-centered column small-12&quot;&gt;<br /> &lt;translate&gt;<br /> &lt;!--T:2--&gt;<br /> An online [[S:MyLanguage/JDOC:About|collaborative community manual]] for Joomla! users, developers or anyone interested in learning more about Joomla! Currently, we have [[Special:Statistics|{{NUMBEROFARTICLES}}]] articles written, maintained, and translated by our Joomla! community members.<br /> &lt;/translate&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> {{-}}<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot; style=&quot;margin:0;&quot;&gt;<br /> &lt;div style=&quot;min-width:60px; display:inline-block; margin:0 auto;&quot;&gt;&lt;div class=&quot;fa fa-language fa-3x&quot;&gt;&lt;/div&gt;&lt;/div&gt;<br /> &lt;div id=&quot;lang-control&quot; style=&quot;max-width:80%; margin:0 auto;&quot;&gt;<br /> &lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;!--- First 3 Icons ---&gt;<br /> &lt;div class=&quot;large-6 small-12 column&quot;&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div class=&quot;main-page-icon blue-bkgd&quot;&gt;&lt;div class=&quot;fa fa-university fa-3x&quot;&gt;&lt;/div&gt;<br /> &lt;span class=&quot;icon-text&quot;&gt;<br /> &lt;translate&gt;<br /> &lt;!--T:3--&gt;<br /> '''Learn'''<br /> &lt;/translate&gt;<br /> &lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div id=&quot;main-page-list&quot; class=&quot;text-left&quot;&gt;<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-info-circle fa-lg icon&quot; style=&quot;color:#5290C8;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:4--&gt;<br /> [[S:MyLanguage/Portal:Learn More|More About Joomla!]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-joomla fa-lg icon&quot; style=&quot;color:#000;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:56--&gt;<br /> [[S:MyLanguage/Joomla:The_Joomla_Websites|The Joomla! Websites]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-bug fa-lg icon&quot; style=&quot;color:#E6462B;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:9--&gt;<br /> [[S:MyLanguage/Filing_bugs_and_issues|Report a Bug or Issue]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-users fa-lg icon&quot; style=&quot;color:#7DB847;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:5--&gt;<br /> [[S:MyLanguage/Portal:Beginners|Beginners]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-users fa-lg icon&quot; style=&quot;color:#E6462B;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:6--&gt;<br /> [[S:MyLanguage/Portal:Administrators|Administrators]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-code fa-lg icon&quot; style=&quot;color:#F5A443;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:8--&gt;<br /> [[S:MyLanguage/Portal:Developers|Developers]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-joomla fa-lg icon&quot; style=&quot;color:#000;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:10--&gt;<br /> [[S:MyLanguage/Portal:Joomla!_Code_Contributors|Core Developers]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;large-6 small-12 column&quot;&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div class=&quot;main-page-icon red-bkgd&quot;&gt;&lt;div class=&quot;fa fa-exclamation fa-3x&quot;&gt;&lt;/div&gt;<br /> &lt;span class=&quot;icon-text&quot;&gt;<br /> &lt;translate&gt;<br /> &lt;!--T:11--&gt;<br /> '''Links'''<br /> &lt;/translate&gt;&lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div id=&quot;main-page-list&quot; class=&quot;text-left&quot;&gt;<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-wrench fa-lg icon&quot; style=&quot;color:#5290C8;&quot;&gt;&lt;/div&gt; &lt;translate&gt;&lt;!--T:44--&gt;<br /> [[S:MyLanguage/J3.x:Installing_Joomla|Installing Joomla!]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-arrow-circle-o-up fa-lg icon&quot; style=&quot;color:#aaa;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:7--&gt;<br /> [[S:MyLanguage/Portal:Upgrading Versions|Upgrading and Migrations]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-question-circle fa-lg icon&quot; style=&quot;color:#7DB847;&quot;&gt;&lt;/div&gt; &lt;translate&gt;&lt;!--T:51--&gt;<br /> [[S:MyLanguage/Tutorials:Beginners|Beginner Tutorials]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-life-saver fa-lg icon&quot; style=&quot;color:#E6462B;&quot;&gt;&lt;/div&gt; &lt;translate&gt;&lt;!--T:45--&gt;<br /> [[S:MyLanguage/Help screens|Admin Help Screens]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-unlock fa-lg icon&quot; style=&quot;color:#F5A443;&quot;&gt;&lt;/div&gt; &lt;translate&gt;&lt;!--T:46--&gt;<br /> [[S:MyLanguage/How do you recover or reset your admin password?|Password Recovery]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-book fa-lg icon&quot; style=&quot;color:#555;&quot;&gt;&lt;/div&gt; &lt;translate&gt;&lt;!--T:47--&gt;<br /> [[S:MyLanguage/Glossary|Our Glossary]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-magic fa-lg icon&quot; style=&quot;color:#333;&quot;&gt;&lt;/div&gt; &lt;translate&gt;&lt;!--T:48--&gt;<br /> [[S:MyLanguage/:Category:Tips and tricks|Tips and Tricks]] or [[S:MyLanguage/:Category:FAQ|FAQs]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div class=&quot;main-page-icon dark-grey-bkgd&quot;&gt;&lt;div class=&quot;fa fa-code-fork fa-3x&quot;&gt;&lt;/div&gt;<br /> &lt;span class=&quot;icon-text&quot;&gt;<br /> &lt;translate&gt;<br /> &lt;!--T:12--&gt;<br /> '''Versions'''<br /> &lt;/translate&gt;&lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;span class=&quot;main-page-text&quot;&gt;'''Joomla! {{CurrentSTSVer4|maintenance}} &lt;translate&gt;<br /> &lt;!--T:60--&gt;<br /> is the latest stable version of Joomla 4, we recommend for new installations.&lt;/translate&gt;'''&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;'''Joomla! 3.10.12 &lt;translate&gt;&lt;!--T:13--&gt;<br /> was the last stable version of Joomla 3. Support ended on the 17th of August 2023&lt;/translate&gt;.'''&lt;/span&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:15--&gt;<br /> Info on all [[S:MyLanguage/What_version_of_Joomla!_should_you_use?|Joomla! CMS Versions]]&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:55--&gt;<br /> [[S:MyLanguage/Technical_requirements|Technical requirements]] for Joomla! {{CurrentSTSVer4|maintenance}} and {{CurrentSTSVer|maintenance}}&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:16--&gt;<br /> [[S:MyLanguage/J4.x:What%27s_new_in_Joomla!|Find out what's new in Joomla! CMS {{CurrentSTSVer4|minor}}]]&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;&lt;!--T:54--&gt;<br /> Take an extended test drive and build your own [[S:MyLanguage/How_to_build_your_free_Joomla_Website|free Joomla! website]]&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:50--&gt;<br /> Always use a supported version, read our [[S:MyLanguage/Release and support cycle|release and support cycle]] page.&lt;/translate&gt;{{-}}<br /> &lt;div class=&quot;no-external-icon&quot;&gt;&lt;span style=&quot;line-height:2.2em;font-size:1.3em;&quot;&gt;&lt;translate&gt;<br /> &lt;!--T:18--&gt;<br /> [https://downloads.joomla.org Download Joomla!]&lt;/translate&gt;{{-}}&lt;div class=&quot;fa fa-download fa-2x&quot; style=&quot;color:#142849;&quot;&gt;&lt;/div&gt;&lt;/span&gt;&lt;/div&gt;{{-}}<br /> &lt;/div&gt;<br /> <br /> &lt;!--- Last 3 Icons ---&gt;<br /> &lt;div class=&quot;large-6 small-12 column&quot;&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div class=&quot;main-page-icon green-bkgd&quot;&gt;&lt;div class=&quot;fa fa-tasks fa-3x&quot;&gt;&lt;/div&gt;<br /> &lt;span class=&quot;icon-text&quot;&gt;<br /> &lt;translate&gt;<br /> &lt;!--T:19--&gt;<br /> '''Tasks'''&lt;/translate&gt;&lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div id=&quot;main-page-list&quot; class=&quot;text-left&quot;&gt;<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-cogs fa-lg icon&quot; style=&quot;color:#5290C8;&quot;&gt;&lt;/div&gt; &lt;translate&gt;&lt;!--T:52--&gt;<br /> [[S:MyLanguage/J3.x:Global_configuration|Configuring Your Installation]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-lock fa-lg icon&quot; style=&quot;color:#E6462B;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:20--&gt;<br /> [[S:MyLanguage/Security_Checklist|Secure Your Website]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-search-plus fa-lg icon&quot; style=&quot;color:#7DB847;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:21--&gt;<br /> [[S:MyLanguage/Portal:Search Engine Optimisation|Search Engine Optimisation]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-users fa-lg icon&quot; style=&quot;color:#aaa;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:22--&gt;<br /> [[S:MyLanguage/User Management|Managing Your Users]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-info-circle fa-lg icon&quot; style=&quot;color:#F5A443;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:23--&gt;<br /> [[S:MyLanguage/Portal:Template_Management|Managing Templates]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-newspaper-o fa-lg icon&quot; style=&quot;color:#555;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:24--&gt;<br /> [[S:MyLanguage/Article_Management|Content Management]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-bars fa-lg icon&quot; style=&quot;color:#333;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:25--&gt;<br /> [[S:MyLanguage/Menu_Management|Menu Management]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;large-6 small-12 column text-center&quot;&gt;<br /> &lt;div class=&quot;large-12 small-12 column&quot;&gt;<br /> &lt;div class=&quot;main-page-icon orange-bkgd&quot;&gt;&lt;div class=&quot;fa fa-users fa-3x&quot;&gt;&lt;/div&gt;<br /> &lt;span class=&quot;icon-text&quot;&gt;&lt;translate&gt;<br /> &lt;!--T:26--&gt;<br /> '''Contribute'''&lt;/translate&gt;&lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div id=&quot;main-page-list&quot; class=&quot;text-left&quot;&gt;<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-pencil-square-o fa-lg icon&quot; style=&quot;color:#7DB847;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:28--&gt;<br /> [[S:MyLanguage/JDOC:How_to_Contribute_to_Joomla!_Documentation|Help with Documentation]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span style=&quot;color:#7DB847;line-height:2.2em;font-size:1.1em;&quot;&gt;&lt;div class=&quot;fa fa-language fa-lg icon&quot; style=&quot;color:#333;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:29--&gt;<br /> [[S:MyLanguage/JDOC:Documentation_Translators|Translate Documentation]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-bug fa-lg icon&quot; style=&quot;color:#E6462B;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:30--&gt;<br /> Join the [[S:MyLanguage/Portal:Bug Squad|Bug Squad]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-file-code-o fa-lg icon&quot; style=&quot;color:#F5A443;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:31--&gt;<br /> Be a [[S:MyLanguage/Portal:Joomla!_Code_Contributors|Core Code Contributor]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-user-plus fa-lg icon&quot; style=&quot;color:#555;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:32--&gt;<br /> Join a [[S:MyLanguage/Portal:Joomla_User_Groups|Joomla User Group]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text no-external-icon&quot;&gt;&lt;div class=&quot;fa fa-life-ring fa-lg icon&quot; style=&quot;color:#E6462B;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:33--&gt;<br /> Help on a [http://volunteers.joomla.org Joomla! Team]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-joomla fa-lg icon&quot; style=&quot;color:#5091CD;&quot;&gt;&lt;/div&gt; <br /> [[S:MyLanguage/Joomla:Brand Identity Elements|&lt;translate&gt;&lt;!--T:57--&gt;<br /> Brand Identity Elements&lt;/translate&gt;]]&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-users fa-lg icon&quot; style=&quot;color:#F9A541;&quot;&gt;&lt;/div&gt; <br /> [[S:MyLanguage/Category:Marketing materials|&lt;translate&gt;&lt;!--T:58--&gt;<br /> Marketing Resources&lt;/translate&gt;]]&lt;/span&gt;{{-}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> {{-}}<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div class=&quot;main-page-icon dark-grey-bkgd&quot;&gt;&lt;div class=&quot;fa fa-list-alt fa-3x&quot;&gt;&lt;/div&gt;<br /> &lt;span class=&quot;icon-text&quot;&gt;&lt;translate&gt;<br /> &lt;!--T:34--&gt;<br /> '''Projects'''&lt;/translate&gt;&lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;span class=&quot;icon-text&quot;&gt;&lt;translate&gt;<br /> &lt;!--T:35--&gt;<br /> '''[[S:MyLanguage/JDOC:Projects|Find a JDOC Project]]'''&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:36--&gt;<br /> Here are a few in need of contributors.&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:41--&gt;<br /> '''[[S:MyLanguage/Help screens|Help Screens Project]]'''&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:37--&gt;<br /> '''[[S:MyLanguage/JDOC:Beginners Tutorial Project|Beginners Tutorial Project]]'''&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:39--&gt;<br /> '''[[S:MyLanguage/JDOC:Developer Tutorials Project|Developer Tutorials Project]]'''&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;&lt;!--T:59--&gt; '''[[S:MyLanguage/JDOC:Joomla 4 Tutorials Project|Joomla 4 Tutorials Project]]'''&lt;/translate&gt;{{-}}<br /> &lt;/div&gt;<br /> {{-}}<br /> {{license/&lt;translate&gt;&lt;!--T:53--&gt;<br /> en&lt;/translate&gt;}}<br /> __NOTOC__ __NOEDITSECTION__</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Main_Page&diff=1015190 2023-10-06T13:46:49Z

<p>Wilsonge: Language</p> <hr /> <div>&lt;div class=&quot;row&quot;&gt;<br /> &lt;div class=&quot;large-12 small-12 columns text-center hide-for-small&quot;&gt;<br /> &lt;span style=&quot;font-size:2.5em;&quot;&gt;'''Joomla!'''&lt;span style=&quot;font-size:.4em; vertical-align:super;&quot;&gt;&lt;sup&gt;&amp;reg;&lt;sup&gt;&lt;/span&gt;&lt;/span&gt;{{-}}<br /> [[File:Joomla_logo.png‎|80px|center]]{{-}}<br /> &lt;/div&gt;<br /> &lt;div class=&quot;large-12 small-12 columns text-center hide-for-small&quot;&gt;<br /> &lt;span style=&quot;font-size:2.5em;font-weight:bold;&quot;&gt;&lt;translate&gt;&lt;!--T:1--&gt;<br /> Documentation&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;div class=&quot;large-11 large-centered column small-12&quot;&gt;<br /> &lt;translate&gt;<br /> &lt;!--T:2--&gt;<br /> An online [[S:MyLanguage/JDOC:About|collaborative community manual]] for Joomla! users, developers or anyone interested in learning more about Joomla! Currently, we have [[Special:Statistics|{{NUMBEROFARTICLES}}]] articles written, maintained, and translated by our Joomla! community members.<br /> &lt;/translate&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> {{-}}<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot; style=&quot;margin:0;&quot;&gt;<br /> &lt;div style=&quot;min-width:60px; display:inline-block; margin:0 auto;&quot;&gt;&lt;div class=&quot;fa fa-language fa-3x&quot;&gt;&lt;/div&gt;&lt;/div&gt;<br /> &lt;div id=&quot;lang-control&quot; style=&quot;max-width:80%; margin:0 auto;&quot;&gt;<br /> &lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;!--- First 3 Icons ---&gt;<br /> &lt;div class=&quot;large-6 small-12 column&quot;&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div class=&quot;main-page-icon blue-bkgd&quot;&gt;&lt;div class=&quot;fa fa-university fa-3x&quot;&gt;&lt;/div&gt;<br /> &lt;span class=&quot;icon-text&quot;&gt;<br /> &lt;translate&gt;<br /> &lt;!--T:3--&gt;<br /> '''Learn'''<br /> &lt;/translate&gt;<br /> &lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div id=&quot;main-page-list&quot; class=&quot;text-left&quot;&gt;<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-info-circle fa-lg icon&quot; style=&quot;color:#5290C8;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:4--&gt;<br /> [[S:MyLanguage/Portal:Learn More|More About Joomla!]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-joomla fa-lg icon&quot; style=&quot;color:#000;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:56--&gt;<br /> [[S:MyLanguage/Joomla:The_Joomla_Websites|The Joomla! Websites]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-bug fa-lg icon&quot; style=&quot;color:#E6462B;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:9--&gt;<br /> [[S:MyLanguage/Filing_bugs_and_issues|Report a Bug or Issue]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-users fa-lg icon&quot; style=&quot;color:#7DB847;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:5--&gt;<br /> [[S:MyLanguage/Portal:Beginners|Beginners]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-users fa-lg icon&quot; style=&quot;color:#E6462B;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:6--&gt;<br /> [[S:MyLanguage/Portal:Administrators|Administrators]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-code fa-lg icon&quot; style=&quot;color:#F5A443;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:8--&gt;<br /> [[S:MyLanguage/Portal:Developers|Developers]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-joomla fa-lg icon&quot; style=&quot;color:#000;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:10--&gt;<br /> [[S:MyLanguage/Portal:Joomla!_Code_Contributors|Core Developers]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;large-6 small-12 column&quot;&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div class=&quot;main-page-icon red-bkgd&quot;&gt;&lt;div class=&quot;fa fa-exclamation fa-3x&quot;&gt;&lt;/div&gt;<br /> &lt;span class=&quot;icon-text&quot;&gt;<br /> &lt;translate&gt;<br /> &lt;!--T:11--&gt;<br /> '''Links'''<br /> &lt;/translate&gt;&lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div id=&quot;main-page-list&quot; class=&quot;text-left&quot;&gt;<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-wrench fa-lg icon&quot; style=&quot;color:#5290C8;&quot;&gt;&lt;/div&gt; &lt;translate&gt;&lt;!--T:44--&gt;<br /> [[S:MyLanguage/J3.x:Installing_Joomla|Installing Joomla!]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-arrow-circle-o-up fa-lg icon&quot; style=&quot;color:#aaa;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:7--&gt;<br /> [[S:MyLanguage/Portal:Upgrading Versions|Upgrading and Migrations]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-question-circle fa-lg icon&quot; style=&quot;color:#7DB847;&quot;&gt;&lt;/div&gt; &lt;translate&gt;&lt;!--T:51--&gt;<br /> [[S:MyLanguage/Tutorials:Beginners|Beginner Tutorials]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-life-saver fa-lg icon&quot; style=&quot;color:#E6462B;&quot;&gt;&lt;/div&gt; &lt;translate&gt;&lt;!--T:45--&gt;<br /> [[S:MyLanguage/Help screens|Admin Help Screens]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-unlock fa-lg icon&quot; style=&quot;color:#F5A443;&quot;&gt;&lt;/div&gt; &lt;translate&gt;&lt;!--T:46--&gt;<br /> [[S:MyLanguage/How do you recover or reset your admin password?|Password Recovery]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-book fa-lg icon&quot; style=&quot;color:#555;&quot;&gt;&lt;/div&gt; &lt;translate&gt;&lt;!--T:47--&gt;<br /> [[S:MyLanguage/Glossary|Our Glossary]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-magic fa-lg icon&quot; style=&quot;color:#333;&quot;&gt;&lt;/div&gt; &lt;translate&gt;&lt;!--T:48--&gt;<br /> [[S:MyLanguage/:Category:Tips and tricks|Tips and Tricks]] or [[S:MyLanguage/:Category:FAQ|FAQs]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div class=&quot;main-page-icon dark-grey-bkgd&quot;&gt;&lt;div class=&quot;fa fa-code-fork fa-3x&quot;&gt;&lt;/div&gt;<br /> &lt;span class=&quot;icon-text&quot;&gt;<br /> &lt;translate&gt;<br /> &lt;!--T:12--&gt;<br /> '''Versions'''<br /> &lt;/translate&gt;&lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;span class=&quot;main-page-text&quot;&gt;'''Joomla! {{CurrentSTSVer4|maintenance}} &lt;translate&gt;<br /> &lt;!--T:60--&gt;<br /> is the latest stable version of Joomla 4, we recommend for new installations.&lt;/translate&gt;'''&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;'''Joomla! 3.10.12 &lt;translate&gt;&lt;!--T:13--&gt;<br /> was the last stable version of Joomla 3. Support ended on the 17th of August 2023&lt;/translate&gt;.'''&lt;/span&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:15--&gt;<br /> Info on all [[S:MyLanguage/What_version_of_Joomla!_should_you_use?|Joomla! CMS Versions]]&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:55--&gt;<br /> [[S:MyLanguage/Technical_requirements|Technical requirements]] for Joomla! {{CurrentSTSVer4|maintenance}} and {{CurrentSTSVer|maintenance}}&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:16--&gt;<br /> [[S:MyLanguage/J3.x:What%27s_new_in_Joomla!|Find out what's new in Joomla! CMS {{CurrentSTSVer|minor}}]]&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:17--&gt;<br /> [[S:MyLanguage/Joomla_3_FAQ|Answers to common questions about Joomla! CMS 3]]&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;&lt;!--T:54--&gt;<br /> Take an extended test drive and build your own [[S:MyLanguage/How_to_build_your_free_Joomla_Website|free Joomla! website]]&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:50--&gt;<br /> Always use a supported version, read our [[S:MyLanguage/Release and support cycle|release and support cycle]] page.&lt;/translate&gt;{{-}}<br /> &lt;div class=&quot;no-external-icon&quot;&gt;&lt;span style=&quot;line-height:2.2em;font-size:1.3em;&quot;&gt;&lt;translate&gt;<br /> &lt;!--T:18--&gt;<br /> [https://downloads.joomla.org Download Joomla!]&lt;/translate&gt;{{-}}&lt;div class=&quot;fa fa-download fa-2x&quot; style=&quot;color:#142849;&quot;&gt;&lt;/div&gt;&lt;/span&gt;&lt;/div&gt;{{-}}<br /> &lt;/div&gt;<br /> <br /> &lt;!--- Last 3 Icons ---&gt;<br /> &lt;div class=&quot;large-6 small-12 column&quot;&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div class=&quot;main-page-icon green-bkgd&quot;&gt;&lt;div class=&quot;fa fa-tasks fa-3x&quot;&gt;&lt;/div&gt;<br /> &lt;span class=&quot;icon-text&quot;&gt;<br /> &lt;translate&gt;<br /> &lt;!--T:19--&gt;<br /> '''Tasks'''&lt;/translate&gt;&lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div id=&quot;main-page-list&quot; class=&quot;text-left&quot;&gt;<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-cogs fa-lg icon&quot; style=&quot;color:#5290C8;&quot;&gt;&lt;/div&gt; &lt;translate&gt;&lt;!--T:52--&gt;<br /> [[S:MyLanguage/J3.x:Global_configuration|Configuring Your Installation]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-lock fa-lg icon&quot; style=&quot;color:#E6462B;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:20--&gt;<br /> [[S:MyLanguage/Security_Checklist|Secure Your Website]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-search-plus fa-lg icon&quot; style=&quot;color:#7DB847;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:21--&gt;<br /> [[S:MyLanguage/Portal:Search Engine Optimisation|Search Engine Optimisation]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-users fa-lg icon&quot; style=&quot;color:#aaa;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:22--&gt;<br /> [[S:MyLanguage/User Management|Managing Your Users]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-info-circle fa-lg icon&quot; style=&quot;color:#F5A443;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:23--&gt;<br /> [[S:MyLanguage/Portal:Template_Management|Managing Templates]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-newspaper-o fa-lg icon&quot; style=&quot;color:#555;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:24--&gt;<br /> [[S:MyLanguage/Article_Management|Content Management]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-bars fa-lg icon&quot; style=&quot;color:#333;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:25--&gt;<br /> [[S:MyLanguage/Menu_Management|Menu Management]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> <br /> &lt;div class=&quot;large-6 small-12 column text-center&quot;&gt;<br /> &lt;div class=&quot;large-12 small-12 column&quot;&gt;<br /> &lt;div class=&quot;main-page-icon orange-bkgd&quot;&gt;&lt;div class=&quot;fa fa-users fa-3x&quot;&gt;&lt;/div&gt;<br /> &lt;span class=&quot;icon-text&quot;&gt;&lt;translate&gt;<br /> &lt;!--T:26--&gt;<br /> '''Contribute'''&lt;/translate&gt;&lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div id=&quot;main-page-list&quot; class=&quot;text-left&quot;&gt;<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-pencil-square-o fa-lg icon&quot; style=&quot;color:#7DB847;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:28--&gt;<br /> [[S:MyLanguage/JDOC:How_to_Contribute_to_Joomla!_Documentation|Help with Documentation]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span style=&quot;color:#7DB847;line-height:2.2em;font-size:1.1em;&quot;&gt;&lt;div class=&quot;fa fa-language fa-lg icon&quot; style=&quot;color:#333;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:29--&gt;<br /> [[S:MyLanguage/JDOC:Documentation_Translators|Translate Documentation]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-bug fa-lg icon&quot; style=&quot;color:#E6462B;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:30--&gt;<br /> Join the [[S:MyLanguage/Portal:Bug Squad|Bug Squad]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-file-code-o fa-lg icon&quot; style=&quot;color:#F5A443;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:31--&gt;<br /> Be a [[S:MyLanguage/Portal:Joomla!_Code_Contributors|Core Code Contributor]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-user-plus fa-lg icon&quot; style=&quot;color:#555;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:32--&gt;<br /> Join a [[S:MyLanguage/Portal:Joomla_User_Groups|Joomla User Group]]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text no-external-icon&quot;&gt;&lt;div class=&quot;fa fa-life-ring fa-lg icon&quot; style=&quot;color:#E6462B;&quot;&gt;&lt;/div&gt; &lt;translate&gt;<br /> &lt;!--T:33--&gt;<br /> Help on a [http://volunteers.joomla.org Joomla! Team]&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-joomla fa-lg icon&quot; style=&quot;color:#5091CD;&quot;&gt;&lt;/div&gt; <br /> [[S:MyLanguage/Joomla:Brand Identity Elements|&lt;translate&gt;&lt;!--T:57--&gt;<br /> Brand Identity Elements&lt;/translate&gt;]]&lt;/span&gt;{{-}}<br /> &lt;span class=&quot;main-page-text&quot;&gt;&lt;div class=&quot;fa fa-users fa-lg icon&quot; style=&quot;color:#F9A541;&quot;&gt;&lt;/div&gt; <br /> [[S:MyLanguage/Category:Marketing materials|&lt;translate&gt;&lt;!--T:58--&gt;<br /> Marketing Resources&lt;/translate&gt;]]&lt;/span&gt;{{-}}<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> {{-}}<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;div class=&quot;main-page-icon dark-grey-bkgd&quot;&gt;&lt;div class=&quot;fa fa-list-alt fa-3x&quot;&gt;&lt;/div&gt;<br /> &lt;span class=&quot;icon-text&quot;&gt;&lt;translate&gt;<br /> &lt;!--T:34--&gt;<br /> '''Projects'''&lt;/translate&gt;&lt;/span&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;large-12 small-12 column text-center&quot;&gt;<br /> &lt;span class=&quot;icon-text&quot;&gt;&lt;translate&gt;<br /> &lt;!--T:35--&gt;<br /> '''[[S:MyLanguage/JDOC:Projects|Find a JDOC Project]]'''&lt;/translate&gt;&lt;/span&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:36--&gt;<br /> Here are a few in need of contributors.&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:41--&gt;<br /> '''[[S:MyLanguage/Help screens|Help Screens Project]]'''&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:37--&gt;<br /> '''[[S:MyLanguage/JDOC:Beginners Tutorial Project|Beginners Tutorial Project]]'''&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;<br /> &lt;!--T:39--&gt;<br /> '''[[S:MyLanguage/JDOC:Developer Tutorials Project|Developer Tutorials Project]]'''&lt;/translate&gt;{{-}}<br /> &lt;translate&gt;&lt;!--T:59--&gt; '''[[S:MyLanguage/JDOC:Joomla 4 Tutorials Project|Joomla 4 Tutorials Project]]'''&lt;/translate&gt;{{-}}<br /> &lt;/div&gt;<br /> {{-}}<br /> {{license/&lt;translate&gt;&lt;!--T:53--&gt;<br /> en&lt;/translate&gt;}}<br /> __NOTOC__ __NOEDITSECTION__</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Template:CurrentSTSVer4&diff=1010683 2023-08-16T12:16:20Z

<p>Wilsonge: Update version</p> <hr /> <div>{{#switch:{{{1}}}|<br /> 1|<br /> major=4|<br /> 2|<br /> minor=4.3|<br /> 4|<br /> #default|<br /> maintenance=4.3.3<br /> }}&lt;noinclude&gt;&lt;!--The editor of this page is responsible for ensuring the three versions are consistent!--&gt;&lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Template:CurrentSTSVer4&diff=1001130 2023-04-27T20:23:54Z

<p>Wilsonge: </p> <hr /> <div>{{#switch:{{{1}}}|<br /> 1|<br /> major=4|<br /> 2|<br /> minor=4.3|<br /> 4|<br /> #default|<br /> maintenance=4.3.1<br /> }}&lt;noinclude&gt;&lt;!--The editor of this page is responsible for ensuring the three versions are consistent!--&gt;&lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Template:CurrentSTSVer4&diff=999339 2023-02-16T16:29:28Z

<p>Wilsonge: </p> <hr /> <div>{{#switch:{{{1}}}|<br /> 1|<br /> major=4|<br /> 2|<br /> minor=4.2|<br /> 4|<br /> #default|<br /> maintenance=4.2.8<br /> }}&lt;noinclude&gt;&lt;!--The editor of this page is responsible for ensuring the three versions are consistent!--&gt;&lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Template:CurrentSTSVer4&diff=999336 2023-02-16T10:42:23Z

<p>Wilsonge: Fix version</p> <hr /> <div>{{#switch:{{{1}}}|<br /> 1|<br /> major=4|<br /> 2|<br /> minor=4.2|<br /> 4|<br /> #default|<br /> maintenance=4.2.7<br /> }}&lt;noinclude&gt;&lt;!--The editor of this page is responsible for ensuring the three versions are consistent!--&gt;&lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Joomla!_CMS_versions&diff=999321 2023-02-16T10:38:52Z

<p>Wilsonge: No bugs or security for 4.1</p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> {{Joomla version|version={{CurrentSTSVer4|maintenance}}|comment='''&lt;translate&gt;&lt;!--T:97--&gt; Stable Version&lt;/translate&gt;'''}}<br /> {{Joomla version|version={{CurrentSTSVer|maintenance}}|comment='''&lt;translate&gt; &lt;!--T:96--&gt; Stable Version&lt;/translate&gt;'''}}&lt;translate&gt;&lt;!--T:1--&gt;<br /> 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.&lt;/translate&gt;<br /> <br /> &lt;translate&gt;&lt;!--T:2--&gt;<br /> *Normally, you should use the latest version of Joomla! for a new site unless you have a specific reason not to.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:3--&gt;<br /> *The latest version can be downloaded from [https://downloads.joomla.org Joomla! Downloads site].&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:4--&gt;<br /> * 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.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:5--&gt;<br /> * 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.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> &lt;!--T:104--&gt;<br /> * See the [https://developer.joomla.org/roadmap.html Joomla! Project Roadmap] for the time frames of all future releases.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Joomla! CMS Versions== &lt;!--T:6--&gt;<br /> &lt;/translate&gt;<br /> {| border=1 cellpadding=2 cellspacing=0 style=&quot;text-align:center; border-collapse:collapse; border-color:#000;&quot;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:7--&gt;<br /> CMS Version&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:8--&gt;<br /> Available&lt;/translate&gt;<br /> | colspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:9--&gt;<br /> Support&lt;/translate&gt;<br /> | style='display:none;' |<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:10--&gt;<br /> End of Life&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:11--&gt;<br /> Upgrade Type&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:12--&gt;<br /> Notes&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:13--&gt;<br /> Latest Release&lt;/translate&gt;<br /> |-<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:14--&gt;<br /> Bugs&lt;/translate&gt;<br /> | style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:15--&gt;<br /> Security&lt;/translate&gt;<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> |-<br /> | style=&quot;background-color:#d9ead3; font-weight:bold;&quot; | 4.2<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | 4.3 release (currently planned for April 2023)<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:105--&gt; One-click from Joomla! 4.0&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:106--&gt; Recommended for all new installations&lt;br/&gt;[[S:MyLanguage/Joomla 4.2 version history|Joomla! 4.2 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | {{CurrentSTSVer4|maintenance}}<br /> |-|-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 4.1<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.2 release<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:102--&gt; One-click from Joomla! 4.0&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:103--&gt; Upgrade to {{CurrentSTSVer4|maintenance}} now&lt;br /&gt;[[S:MyLanguage/Joomla 4.1 version history|Joomla! 4.1 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.1.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 4.0<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.1 release<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:99--&gt; Migration from Joomla! 3.10&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:100--&gt; Upgrade to {{CurrentSTSVer4|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 4.0 version history|Joomla! 4.0 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.0.6<br /> |-<br /> | style=&quot;background-color:#d9ead3; font-weight:bold;&quot; | 3.10<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | 17.08.2023<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:101--&gt; One-click from Joomla! 3.9&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:98--&gt; Recommended for migration to Joomla! 4&lt;br/&gt;[[S:MyLanguage/Joomla 3.10 version history|Joomla! 3.10 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | {{CurrentSTSVer|maintenance}}<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.9<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:92--&gt; 3.10 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:93--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:94--&gt; Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.9 version history|Joomla! 3.9 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.9.28<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.8<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:85--&gt; 3.9 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:86--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:95--&gt; Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.8 version history|Joomla! 3.8 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.8.13<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.7<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:82--&gt; 3.8 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:83--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;<br /> &lt;!--T:84--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.7 version history|Joomla! 3.7 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.7.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.6<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:61--&gt;<br /> 3.7 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:62--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:68--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.6 version history|Joomla! 3.6 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.6.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:46--&gt;<br /> 3.6 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:47--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:41--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.5 version history|Joomla 3.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.5.1<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.4<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:43--&gt;<br /> 3.5 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:44--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;<br /> &lt;!--T:67--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.4 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.4.8<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.3<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:39--&gt;<br /> 3.4 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:40--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:57--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;<br /> &lt;!--T:58--&gt;<br /> [[Joomla 3.3 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.3.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.2<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:36--&gt;<br /> Oct 2014&lt;ref&gt;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]. &lt;blockquote&gt;&quot;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.&quot;&lt;/blockquote&gt;&lt;/ref&gt;&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:37--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:38--&gt;<br /> Upgrade server's PHP to 5.3.10 or greater and upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.2 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.2.7<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.1<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:33--&gt;<br /> Dec 2013&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:34--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:35--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;&lt;!--T:54--&gt;<br /> [[Joomla 3.1 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.1.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; width:100px; font-weight:bold;&quot; | 3.0<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | &lt;translate&gt;&lt;!--T:30--&gt;<br /> May 2013&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | &lt;translate&gt;&lt;!--T:31--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc; width:306px;&quot; | &lt;translate&gt;&lt;!--T:32--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.0 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.0.4<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 2.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:26--&gt;<br /> December 31st, 2014&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:27--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:28--&gt;<br /> Upgrade to&lt;/translate&gt; {{CurrentSTSVer}} &lt;translate&gt;&lt;!--T:56--&gt;<br /> now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;&lt;!--T:29--&gt;<br /> [[Joomla 2.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | {{CurrentLTSVer|maintanence}}<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.7<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:23--&gt;<br /> Feb 2012&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:24--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:25--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.7 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 1.7.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.6<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:20--&gt;<br /> Aug 2011&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:21--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:22--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.6 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 1.6.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:16--&gt;<br /> Sept 2012&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:17--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:18--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:19--&gt;<br /> EOL at 1.5.26&lt;/translate&gt;<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.0<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:69--&gt;<br /> 22 July 2009&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:70--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:71--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:72--&gt;<br /> EOL at 1.0.15&lt;/translate&gt;<br /> |}<br /> &lt;noinclude&gt;<br /> &lt;references /&gt;<br /> &lt;translate&gt;&lt;!--T:53--&gt;<br /> [[Category:Joomla! versions]]&lt;/translate&gt;<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Joomla!_CMS_versions&diff=999297 2023-02-16T10:36:38Z

<p>Wilsonge: Marked this version for translation</p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> {{Joomla version|version={{CurrentSTSVer4|maintenance}}|comment='''&lt;translate&gt;&lt;!--T:97--&gt; Stable Version&lt;/translate&gt;'''}}<br /> {{Joomla version|version={{CurrentSTSVer|maintenance}}|comment='''&lt;translate&gt; &lt;!--T:96--&gt; Stable Version&lt;/translate&gt;'''}}&lt;translate&gt;&lt;!--T:1--&gt;<br /> 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.&lt;/translate&gt;<br /> <br /> &lt;translate&gt;&lt;!--T:2--&gt;<br /> *Normally, you should use the latest version of Joomla! for a new site unless you have a specific reason not to.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:3--&gt;<br /> *The latest version can be downloaded from [https://downloads.joomla.org Joomla! Downloads site].&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:4--&gt;<br /> * 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.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:5--&gt;<br /> * 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.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> &lt;!--T:104--&gt;<br /> * See the [https://developer.joomla.org/roadmap.html Joomla! Project Roadmap] for the time frames of all future releases.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Joomla! CMS Versions== &lt;!--T:6--&gt;<br /> &lt;/translate&gt;<br /> {| border=1 cellpadding=2 cellspacing=0 style=&quot;text-align:center; border-collapse:collapse; border-color:#000;&quot;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:7--&gt;<br /> CMS Version&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:8--&gt;<br /> Available&lt;/translate&gt;<br /> | colspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:9--&gt;<br /> Support&lt;/translate&gt;<br /> | style='display:none;' |<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:10--&gt;<br /> End of Life&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:11--&gt;<br /> Upgrade Type&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:12--&gt;<br /> Notes&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:13--&gt;<br /> Latest Release&lt;/translate&gt;<br /> |-<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:14--&gt;<br /> Bugs&lt;/translate&gt;<br /> | style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:15--&gt;<br /> Security&lt;/translate&gt;<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> |-<br /> | style=&quot;background-color:#d9ead3; font-weight:bold;&quot; | 4.2<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | 4.3 release (currently planned for April 2023)<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:105--&gt; One-click from Joomla! 4.0&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:106--&gt; Recommended for all new installations&lt;br/&gt;[[S:MyLanguage/Joomla 4.2 version history|Joomla! 4.2 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | {{CurrentSTSVer4|maintenance}}<br /> |-|-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 4.1<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.2 release<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:102--&gt; One-click from Joomla! 4.0&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:103--&gt; Upgrade to {{CurrentSTSVer4|maintenance}} now&lt;br /&gt;[[S:MyLanguage/Joomla 4.1 version history|Joomla! 4.1 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.1.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 4.0<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.1 release<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:99--&gt; Migration from Joomla! 3.10&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:100--&gt; Upgrade to {{CurrentSTSVer4|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 4.0 version history|Joomla! 4.0 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.0.6<br /> |-<br /> | style=&quot;background-color:#d9ead3; font-weight:bold;&quot; | 3.10<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | 17.08.2023<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:101--&gt; One-click from Joomla! 3.9&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:98--&gt; Recommended for migration to Joomla! 4&lt;br/&gt;[[S:MyLanguage/Joomla 3.10 version history|Joomla! 3.10 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | {{CurrentSTSVer|maintenance}}<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.9<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:92--&gt; 3.10 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:93--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:94--&gt; Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.9 version history|Joomla! 3.9 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.9.28<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.8<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:85--&gt; 3.9 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:86--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:95--&gt; Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.8 version history|Joomla! 3.8 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.8.13<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.7<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:82--&gt; 3.8 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:83--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;<br /> &lt;!--T:84--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.7 version history|Joomla! 3.7 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.7.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.6<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:61--&gt;<br /> 3.7 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:62--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:68--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.6 version history|Joomla! 3.6 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.6.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:46--&gt;<br /> 3.6 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:47--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:41--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.5 version history|Joomla 3.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.5.1<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.4<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:43--&gt;<br /> 3.5 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:44--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;<br /> &lt;!--T:67--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.4 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.4.8<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.3<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:39--&gt;<br /> 3.4 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:40--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:57--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;<br /> &lt;!--T:58--&gt;<br /> [[Joomla 3.3 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.3.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.2<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:36--&gt;<br /> Oct 2014&lt;ref&gt;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]. &lt;blockquote&gt;&quot;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.&quot;&lt;/blockquote&gt;&lt;/ref&gt;&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:37--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:38--&gt;<br /> Upgrade server's PHP to 5.3.10 or greater and upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.2 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.2.7<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.1<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:33--&gt;<br /> Dec 2013&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:34--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:35--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;&lt;!--T:54--&gt;<br /> [[Joomla 3.1 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.1.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; width:100px; font-weight:bold;&quot; | 3.0<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | &lt;translate&gt;&lt;!--T:30--&gt;<br /> May 2013&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | &lt;translate&gt;&lt;!--T:31--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc; width:306px;&quot; | &lt;translate&gt;&lt;!--T:32--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.0 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.0.4<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 2.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:26--&gt;<br /> December 31st, 2014&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:27--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:28--&gt;<br /> Upgrade to&lt;/translate&gt; {{CurrentSTSVer}} &lt;translate&gt;&lt;!--T:56--&gt;<br /> now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;&lt;!--T:29--&gt;<br /> [[Joomla 2.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | {{CurrentLTSVer|maintanence}}<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.7<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:23--&gt;<br /> Feb 2012&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:24--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:25--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.7 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 1.7.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.6<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:20--&gt;<br /> Aug 2011&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:21--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:22--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.6 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 1.6.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:16--&gt;<br /> Sept 2012&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:17--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:18--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:19--&gt;<br /> EOL at 1.5.26&lt;/translate&gt;<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.0<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:69--&gt;<br /> 22 July 2009&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:70--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:71--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:72--&gt;<br /> EOL at 1.0.15&lt;/translate&gt;<br /> |}<br /> &lt;noinclude&gt;<br /> &lt;references /&gt;<br /> &lt;translate&gt;&lt;!--T:53--&gt;<br /> [[Category:Joomla! versions]]&lt;/translate&gt;<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Joomla!_CMS_versions&diff=999296 2023-02-16T10:36:10Z

<p>Wilsonge: Remove duplicates</p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> {{Joomla version|version={{CurrentSTSVer4|maintenance}}|comment='''&lt;translate&gt;&lt;!--T:97--&gt; Stable Version&lt;/translate&gt;'''}}<br /> {{Joomla version|version={{CurrentSTSVer|maintenance}}|comment='''&lt;translate&gt; &lt;!--T:96--&gt; Stable Version&lt;/translate&gt;'''}}&lt;translate&gt;&lt;!--T:1--&gt;<br /> 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.&lt;/translate&gt;<br /> <br /> &lt;translate&gt;&lt;!--T:2--&gt;<br /> *Normally, you should use the latest version of Joomla! for a new site unless you have a specific reason not to.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:3--&gt;<br /> *The latest version can be downloaded from [https://downloads.joomla.org Joomla! Downloads site].&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:4--&gt;<br /> * 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.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:5--&gt;<br /> * 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.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> * See the [https://developer.joomla.org/roadmap.html Joomla! Project Roadmap] for the time frames of all future releases.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Joomla! CMS Versions== &lt;!--T:6--&gt;<br /> &lt;/translate&gt;<br /> {| border=1 cellpadding=2 cellspacing=0 style=&quot;text-align:center; border-collapse:collapse; border-color:#000;&quot;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:7--&gt;<br /> CMS Version&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:8--&gt;<br /> Available&lt;/translate&gt;<br /> | colspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:9--&gt;<br /> Support&lt;/translate&gt;<br /> | style='display:none;' |<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:10--&gt;<br /> End of Life&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:11--&gt;<br /> Upgrade Type&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:12--&gt;<br /> Notes&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:13--&gt;<br /> Latest Release&lt;/translate&gt;<br /> |-<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:14--&gt;<br /> Bugs&lt;/translate&gt;<br /> | style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:15--&gt;<br /> Security&lt;/translate&gt;<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> |-<br /> | style=&quot;background-color:#d9ead3; font-weight:bold;&quot; | 4.2<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | 4.3 release (currently planned for April 2023)<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;One-click from Joomla! 4.0&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;Recommended for all new installations&lt;br/&gt;[[S:MyLanguage/Joomla 4.2 version history|Joomla! 4.2 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | {{CurrentSTSVer4|maintenance}}<br /> |-|-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 4.1<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.2 release<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:102--&gt; One-click from Joomla! 4.0&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:103--&gt; Upgrade to {{CurrentSTSVer4|maintenance}} now&lt;br /&gt;[[S:MyLanguage/Joomla 4.1 version history|Joomla! 4.1 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.1.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 4.0<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.1 release<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:99--&gt; Migration from Joomla! 3.10&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:100--&gt; Upgrade to {{CurrentSTSVer4|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 4.0 version history|Joomla! 4.0 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.0.6<br /> |-<br /> | style=&quot;background-color:#d9ead3; font-weight:bold;&quot; | 3.10<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | 17.08.2023<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:101--&gt; One-click from Joomla! 3.9&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:98--&gt; Recommended for migration to Joomla! 4&lt;br/&gt;[[S:MyLanguage/Joomla 3.10 version history|Joomla! 3.10 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | {{CurrentSTSVer|maintenance}}<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.9<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:92--&gt; 3.10 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:93--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:94--&gt; Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.9 version history|Joomla! 3.9 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.9.28<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.8<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:85--&gt; 3.9 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:86--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:95--&gt; Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.8 version history|Joomla! 3.8 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.8.13<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.7<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:82--&gt; 3.8 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:83--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;<br /> &lt;!--T:84--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.7 version history|Joomla! 3.7 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.7.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.6<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:61--&gt;<br /> 3.7 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:62--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:68--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.6 version history|Joomla! 3.6 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.6.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:46--&gt;<br /> 3.6 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:47--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:41--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.5 version history|Joomla 3.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.5.1<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.4<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:43--&gt;<br /> 3.5 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:44--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;<br /> &lt;!--T:67--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.4 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.4.8<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.3<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:39--&gt;<br /> 3.4 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:40--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:57--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;<br /> &lt;!--T:58--&gt;<br /> [[Joomla 3.3 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.3.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.2<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:36--&gt;<br /> Oct 2014&lt;ref&gt;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]. &lt;blockquote&gt;&quot;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.&quot;&lt;/blockquote&gt;&lt;/ref&gt;&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:37--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:38--&gt;<br /> Upgrade server's PHP to 5.3.10 or greater and upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.2 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.2.7<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.1<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:33--&gt;<br /> Dec 2013&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:34--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:35--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;&lt;!--T:54--&gt;<br /> [[Joomla 3.1 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.1.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; width:100px; font-weight:bold;&quot; | 3.0<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | &lt;translate&gt;&lt;!--T:30--&gt;<br /> May 2013&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | &lt;translate&gt;&lt;!--T:31--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc; width:306px;&quot; | &lt;translate&gt;&lt;!--T:32--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.0 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.0.4<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 2.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:26--&gt;<br /> December 31st, 2014&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:27--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:28--&gt;<br /> Upgrade to&lt;/translate&gt; {{CurrentSTSVer}} &lt;translate&gt;&lt;!--T:56--&gt;<br /> now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;&lt;!--T:29--&gt;<br /> [[Joomla 2.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | {{CurrentLTSVer|maintanence}}<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.7<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:23--&gt;<br /> Feb 2012&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:24--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:25--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.7 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 1.7.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.6<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:20--&gt;<br /> Aug 2011&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:21--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:22--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.6 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 1.6.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:16--&gt;<br /> Sept 2012&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:17--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:18--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:19--&gt;<br /> EOL at 1.5.26&lt;/translate&gt;<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.0<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:69--&gt;<br /> 22 July 2009&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:70--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:71--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:72--&gt;<br /> EOL at 1.0.15&lt;/translate&gt;<br /> |}<br /> &lt;noinclude&gt;<br /> &lt;references /&gt;<br /> &lt;translate&gt;&lt;!--T:53--&gt;<br /> [[Category:Joomla! versions]]&lt;/translate&gt;<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Joomla!_CMS_versions&diff=995768 2022-11-29T23:32:19Z

<p>Wilsonge: </p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> {{Joomla version|version={{CurrentSTSVer4|maintenance}}|comment='''&lt;translate&gt;&lt;!--T:97--&gt; Stable Version&lt;/translate&gt;'''}}<br /> {{Joomla version|version={{CurrentSTSVer|maintenance}}|comment='''&lt;translate&gt; &lt;!--T:96--&gt; Stable Version&lt;/translate&gt;'''}}&lt;translate&gt;&lt;!--T:1--&gt;<br /> 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.&lt;/translate&gt;<br /> <br /> &lt;translate&gt;&lt;!--T:2--&gt;<br /> *Normally, you should use the latest version of Joomla! for a new site unless you have a specific reason not to.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:3--&gt;<br /> *The latest version can be downloaded from [https://downloads.joomla.org Joomla! Downloads site].&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:4--&gt;<br /> * 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.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:5--&gt;<br /> * 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.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Joomla! CMS Versions== &lt;!--T:6--&gt;<br /> &lt;/translate&gt;<br /> {| border=1 cellpadding=2 cellspacing=0 style=&quot;text-align:center; border-collapse:collapse; border-color:#000;&quot;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:7--&gt;<br /> CMS Version&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:8--&gt;<br /> Available&lt;/translate&gt;<br /> | colspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:9--&gt;<br /> Support&lt;/translate&gt;<br /> | style='display:none;' |<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:10--&gt;<br /> End of Life&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:11--&gt;<br /> Upgrade Type&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:12--&gt;<br /> Notes&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:13--&gt;<br /> Latest Release&lt;/translate&gt;<br /> |-<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:14--&gt;<br /> Bugs&lt;/translate&gt;<br /> | style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:15--&gt;<br /> Security&lt;/translate&gt;<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> |-<br /> | style=&quot;background-color:#d9ead3; font-weight:bold;&quot; | 4.2<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | 4.3 release (currently planned for April 2023)<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:102--&gt; One-click from Joomla! 4.0&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:103--&gt; Recommended for all new installations&lt;br/&gt;[[S:MyLanguage/Joomla 4.2 version history|Joomla! 4.2 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | {{CurrentSTSVer4|maintenance}}<br /> |-|-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 4.1<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.2 release<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:102--&gt; One-click from Joomla! 4.0&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:103--&gt; Upgrade to {{CurrentSTSVer4|maintenance}} now&lt;br /&gt;[[S:MyLanguage/Joomla 4.1 version history|Joomla! 4.1 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.1.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 4.0<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.1 release<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:99--&gt; Migration from Joomla! 3.10&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:100--&gt; Upgrade to {{CurrentSTSVer4|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 4.0 version history|Joomla! 4.0 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.0.6<br /> |-<br /> | style=&quot;background-color:#d9ead3; font-weight:bold;&quot; | 3.10<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | 17.08.2023<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:101--&gt; One-click from Joomla! 3.9&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:98--&gt; Recommended for migration to Joomla! 4&lt;br/&gt;[[S:MyLanguage/Joomla 3.10 version history|Joomla! 3.10 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | {{CurrentSTSVer|maintenance}}<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.9&lt;ref name=&quot;roadmap&quot;&gt;&lt;translate&gt;<br /> &lt;!--T:88--&gt;<br /> See J3's [http://developer.joomla.org/cms/roadmap.html roadmap] for time frames of all future releases of all Joomla! 3 versions.&lt;/translate&gt;&lt;/ref&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:92--&gt; 3.10 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:93--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:94--&gt; Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.9 version history|Joomla! 3.9 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.9.28<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.8<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:85--&gt; 3.9 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:86--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:95--&gt; Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.8 version history|Joomla! 3.8 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.8.13<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.7<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:82--&gt; 3.8 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:83--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;<br /> &lt;!--T:84--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.7 version history|Joomla! 3.7 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.7.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.6<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:61--&gt;<br /> 3.7 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:62--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:68--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.6 version history|Joomla! 3.6 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.6.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:46--&gt;<br /> 3.6 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:47--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:41--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.5 version history|Joomla 3.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.5.1<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.4<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:43--&gt;<br /> 3.5 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:44--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;<br /> &lt;!--T:67--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.4 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.4.8<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.3<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:39--&gt;<br /> 3.4 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:40--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:57--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;<br /> &lt;!--T:58--&gt;<br /> [[Joomla 3.3 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.3.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.2<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:36--&gt;<br /> Oct 2014&lt;ref&gt;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]. &lt;blockquote&gt;&quot;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.&quot;&lt;/blockquote&gt;&lt;/ref&gt;&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:37--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:38--&gt;<br /> Upgrade server's PHP to 5.3.10 or greater and upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.2 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.2.7<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.1<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:33--&gt;<br /> Dec 2013&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:34--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:35--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;&lt;!--T:54--&gt;<br /> [[Joomla 3.1 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.1.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; width:100px; font-weight:bold;&quot; | 3.0<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | &lt;translate&gt;&lt;!--T:30--&gt;<br /> May 2013&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | &lt;translate&gt;&lt;!--T:31--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc; width:306px;&quot; | &lt;translate&gt;&lt;!--T:32--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.0 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.0.4<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 2.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:26--&gt;<br /> December 31st, 2014&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:27--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:28--&gt;<br /> Upgrade to&lt;/translate&gt; {{CurrentSTSVer}} &lt;translate&gt;&lt;!--T:56--&gt;<br /> now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;&lt;!--T:29--&gt;<br /> [[Joomla 2.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | {{CurrentLTSVer|maintanence}}<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.7<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:23--&gt;<br /> Feb 2012&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:24--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:25--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.7 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 1.7.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.6<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:20--&gt;<br /> Aug 2011&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:21--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:22--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.6 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 1.6.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:16--&gt;<br /> Sept 2012&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:17--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:18--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:19--&gt;<br /> EOL at 1.5.26&lt;/translate&gt;<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.0<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:69--&gt;<br /> 22 July 2009&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:70--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:71--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:72--&gt;<br /> EOL at 1.0.15&lt;/translate&gt;<br /> |}<br /> &lt;noinclude&gt;<br /> &lt;references /&gt;<br /> &lt;translate&gt;&lt;!--T:53--&gt;<br /> [[Category:Joomla! versions]]&lt;/translate&gt;<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Joomla!_CMS_versions&diff=995767 2022-11-29T23:31:26Z

<p>Wilsonge: </p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> {{Joomla version|version={{CurrentSTSVer4|maintenance}}|comment='''&lt;translate&gt;&lt;!--T:97--&gt; Stable Version&lt;/translate&gt;'''}}<br /> {{Joomla version|version={{CurrentSTSVer|maintenance}}|comment='''&lt;translate&gt; &lt;!--T:96--&gt; Stable Version&lt;/translate&gt;'''}}&lt;translate&gt;&lt;!--T:1--&gt;<br /> 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.&lt;/translate&gt;<br /> <br /> &lt;translate&gt;&lt;!--T:2--&gt;<br /> *Normally, you should use the latest version of Joomla! for a new site unless you have a specific reason not to.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:3--&gt;<br /> *The latest version can be downloaded from [https://downloads.joomla.org Joomla! Downloads site].&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:4--&gt;<br /> * 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.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:5--&gt;<br /> * 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.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Joomla! CMS Versions== &lt;!--T:6--&gt;<br /> &lt;/translate&gt;<br /> {| border=1 cellpadding=2 cellspacing=0 style=&quot;text-align:center; border-collapse:collapse; border-color:#000;&quot;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:7--&gt;<br /> CMS Version&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:8--&gt;<br /> Available&lt;/translate&gt;<br /> | colspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:9--&gt;<br /> Support&lt;/translate&gt;<br /> | style='display:none;' |<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:10--&gt;<br /> End of Life&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:11--&gt;<br /> Upgrade Type&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:12--&gt;<br /> Notes&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:13--&gt;<br /> Latest Release&lt;/translate&gt;<br /> |-<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:14--&gt;<br /> Bugs&lt;/translate&gt;<br /> | style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:15--&gt;<br /> Security&lt;/translate&gt;<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> |-<br /> | style=&quot;background-color:#d9ead3; font-weight:bold;&quot; | 4.2<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | N/A<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:102--&gt; One-click from Joomla! 4.0&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:103--&gt; Recommended for all new installations&lt;br/&gt;[[S:MyLanguage/Joomla 4.2 version history|Joomla! 4.2 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | {{CurrentSTSVer4|maintenance}}<br /> |-|-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 4.1<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | N/A<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:102--&gt; One-click from Joomla! 4.0&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:103--&gt; Upgrade to {{CurrentSTSVer4|maintenance}} now&lt;br /&gt;[[S:MyLanguage/Joomla 4.1 version history|Joomla! 4.1 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.1.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 4.0<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | N/A<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:99--&gt; Migration from Joomla! 3.10&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:100--&gt; Upgrade to {{CurrentSTSVer4|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 4.0 version history|Joomla! 4.0 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.0.6<br /> |-<br /> | style=&quot;background-color:#d9ead3; font-weight:bold;&quot; | 3.10<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | 17.08.2023<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:101--&gt; One-click from Joomla! 3.9&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:98--&gt; Recommended for migration to Joomla! 4&lt;br/&gt;[[S:MyLanguage/Joomla 3.10 version history|Joomla! 3.10 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | {{CurrentSTSVer|maintenance}}<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.9&lt;ref name=&quot;roadmap&quot;&gt;&lt;translate&gt;<br /> &lt;!--T:88--&gt;<br /> See J3's [http://developer.joomla.org/cms/roadmap.html roadmap] for time frames of all future releases of all Joomla! 3 versions.&lt;/translate&gt;&lt;/ref&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:92--&gt; 3.10 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:93--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:94--&gt; Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.9 version history|Joomla! 3.9 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.9.28<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.8<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:85--&gt; 3.9 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:86--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:95--&gt; Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.8 version history|Joomla! 3.8 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.8.13<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.7<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:82--&gt; 3.8 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:83--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;<br /> &lt;!--T:84--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.7 version history|Joomla! 3.7 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.7.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.6<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:61--&gt;<br /> 3.7 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:62--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:68--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.6 version history|Joomla! 3.6 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.6.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:46--&gt;<br /> 3.6 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:47--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:41--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.5 version history|Joomla 3.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.5.1<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.4<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:43--&gt;<br /> 3.5 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:44--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;<br /> &lt;!--T:67--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.4 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.4.8<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.3<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:39--&gt;<br /> 3.4 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:40--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:57--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;<br /> &lt;!--T:58--&gt;<br /> [[Joomla 3.3 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.3.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.2<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:36--&gt;<br /> Oct 2014&lt;ref&gt;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]. &lt;blockquote&gt;&quot;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.&quot;&lt;/blockquote&gt;&lt;/ref&gt;&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:37--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:38--&gt;<br /> Upgrade server's PHP to 5.3.10 or greater and upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.2 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.2.7<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.1<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:33--&gt;<br /> Dec 2013&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:34--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:35--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;&lt;!--T:54--&gt;<br /> [[Joomla 3.1 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.1.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; width:100px; font-weight:bold;&quot; | 3.0<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | &lt;translate&gt;&lt;!--T:30--&gt;<br /> May 2013&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | &lt;translate&gt;&lt;!--T:31--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc; width:306px;&quot; | &lt;translate&gt;&lt;!--T:32--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.0 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.0.4<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 2.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:26--&gt;<br /> December 31st, 2014&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:27--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:28--&gt;<br /> Upgrade to&lt;/translate&gt; {{CurrentSTSVer}} &lt;translate&gt;&lt;!--T:56--&gt;<br /> now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;&lt;!--T:29--&gt;<br /> [[Joomla 2.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | {{CurrentLTSVer|maintanence}}<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.7<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:23--&gt;<br /> Feb 2012&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:24--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:25--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.7 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 1.7.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.6<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:20--&gt;<br /> Aug 2011&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:21--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:22--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.6 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 1.6.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:16--&gt;<br /> Sept 2012&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:17--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:18--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:19--&gt;<br /> EOL at 1.5.26&lt;/translate&gt;<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.0<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:69--&gt;<br /> 22 July 2009&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:70--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:71--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:72--&gt;<br /> EOL at 1.0.15&lt;/translate&gt;<br /> |}<br /> &lt;noinclude&gt;<br /> &lt;references /&gt;<br /> &lt;translate&gt;&lt;!--T:53--&gt;<br /> [[Category:Joomla! versions]]&lt;/translate&gt;<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Joomla!_CMS_versions&diff=995766 2022-11-29T23:29:59Z

<p>Wilsonge: Fix extra line</p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> {{Joomla version|version={{CurrentSTSVer4|maintenance}}|comment='''&lt;translate&gt;&lt;!--T:97--&gt; Stable Version&lt;/translate&gt;'''}}<br /> {{Joomla version|version={{CurrentSTSVer|maintenance}}|comment='''&lt;translate&gt; &lt;!--T:96--&gt; Stable Version&lt;/translate&gt;'''}}&lt;translate&gt;&lt;!--T:1--&gt;<br /> 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.&lt;/translate&gt;<br /> <br /> &lt;translate&gt;&lt;!--T:2--&gt;<br /> *Normally, you should use the latest version of Joomla! for a new site unless you have a specific reason not to.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:3--&gt;<br /> *The latest version can be downloaded from [https://downloads.joomla.org Joomla! Downloads site].&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:4--&gt;<br /> * 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.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:5--&gt;<br /> * 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.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Joomla! CMS Versions== &lt;!--T:6--&gt;<br /> &lt;/translate&gt;<br /> {| border=1 cellpadding=2 cellspacing=0 style=&quot;text-align:center; border-collapse:collapse; border-color:#000;&quot;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:7--&gt;<br /> CMS Version&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:8--&gt;<br /> Available&lt;/translate&gt;<br /> | colspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:9--&gt;<br /> Support&lt;/translate&gt;<br /> | style='display:none;' |<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:10--&gt;<br /> End of Life&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:11--&gt;<br /> Upgrade Type&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:12--&gt;<br /> Notes&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:13--&gt;<br /> Latest Release&lt;/translate&gt;<br /> |-<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:14--&gt;<br /> Bugs&lt;/translate&gt;<br /> | style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:15--&gt;<br /> Security&lt;/translate&gt;<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> |-<br /> | style=&quot;background-color:#d9ead3; font-weight:bold;&quot; | 4.2<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | N/A<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:102--&gt; One-click from Joomla! 4.0&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:103--&gt; Recommended for all new installations&lt;br/&gt;[[S:MyLanguage/Joomla 4.2 version history|Joomla! 4.2 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | {{CurrentSTSVer4|maintenance}}<br /> |-|-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 4.1<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | N/A<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:102--&gt; One-click from Joomla! 4.0&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:103--&gt; Upgrade to {{CurrentSTSVer4|maintenance}} now&lt;br /&gt;[[S:MyLanguage/Joomla 4.1 version history|Joomla! 4.1 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.1.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 4.0<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | 15.02.2024<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:99--&gt; Migration from Joomla! 3.10&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:100--&gt; Upgrade to {{CurrentSTSVer4|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 4.0 version history|Joomla! 4.0 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.0.6<br /> |-<br /> | style=&quot;background-color:#d9ead3; font-weight:bold;&quot; | 3.10<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | 17.08.2023<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:101--&gt; One-click from Joomla! 3.9&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:98--&gt; Recommended for migration to Joomla! 4&lt;br/&gt;[[S:MyLanguage/Joomla 3.10 version history|Joomla! 3.10 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | {{CurrentSTSVer|maintenance}}<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.9&lt;ref name=&quot;roadmap&quot;&gt;&lt;translate&gt;<br /> &lt;!--T:88--&gt;<br /> See J3's [http://developer.joomla.org/cms/roadmap.html roadmap] for time frames of all future releases of all Joomla! 3 versions.&lt;/translate&gt;&lt;/ref&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:92--&gt; 3.10 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:93--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:94--&gt; Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.9 version history|Joomla! 3.9 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.9.28<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.8<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:85--&gt; 3.9 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:86--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:95--&gt; Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.8 version history|Joomla! 3.8 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.8.13<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.7<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:82--&gt; 3.8 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:83--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;<br /> &lt;!--T:84--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.7 version history|Joomla! 3.7 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.7.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.6<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:61--&gt;<br /> 3.7 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:62--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:68--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.6 version history|Joomla! 3.6 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.6.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:46--&gt;<br /> 3.6 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:47--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:41--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.5 version history|Joomla 3.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.5.1<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.4<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:43--&gt;<br /> 3.5 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:44--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;<br /> &lt;!--T:67--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.4 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.4.8<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.3<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:39--&gt;<br /> 3.4 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:40--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:57--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;<br /> &lt;!--T:58--&gt;<br /> [[Joomla 3.3 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.3.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.2<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:36--&gt;<br /> Oct 2014&lt;ref&gt;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]. &lt;blockquote&gt;&quot;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.&quot;&lt;/blockquote&gt;&lt;/ref&gt;&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:37--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:38--&gt;<br /> Upgrade server's PHP to 5.3.10 or greater and upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.2 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.2.7<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.1<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:33--&gt;<br /> Dec 2013&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:34--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:35--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;&lt;!--T:54--&gt;<br /> [[Joomla 3.1 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.1.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; width:100px; font-weight:bold;&quot; | 3.0<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | &lt;translate&gt;&lt;!--T:30--&gt;<br /> May 2013&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | &lt;translate&gt;&lt;!--T:31--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc; width:306px;&quot; | &lt;translate&gt;&lt;!--T:32--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.0 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.0.4<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 2.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:26--&gt;<br /> December 31st, 2014&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:27--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:28--&gt;<br /> Upgrade to&lt;/translate&gt; {{CurrentSTSVer}} &lt;translate&gt;&lt;!--T:56--&gt;<br /> now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;&lt;!--T:29--&gt;<br /> [[Joomla 2.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | {{CurrentLTSVer|maintanence}}<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.7<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:23--&gt;<br /> Feb 2012&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:24--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:25--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.7 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 1.7.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.6<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:20--&gt;<br /> Aug 2011&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:21--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:22--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.6 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 1.6.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:16--&gt;<br /> Sept 2012&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:17--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:18--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:19--&gt;<br /> EOL at 1.5.26&lt;/translate&gt;<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.0<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:69--&gt;<br /> 22 July 2009&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:70--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:71--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:72--&gt;<br /> EOL at 1.0.15&lt;/translate&gt;<br /> |}<br /> &lt;noinclude&gt;<br /> &lt;references /&gt;<br /> &lt;translate&gt;&lt;!--T:53--&gt;<br /> [[Category:Joomla! versions]]&lt;/translate&gt;<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Joomla!_CMS_versions&diff=995765 2022-11-29T23:27:51Z

<p>Wilsonge: Various version updates</p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> {{Joomla version|version={{CurrentSTSVer4|maintenance}}|comment='''&lt;translate&gt;&lt;!--T:97--&gt; Stable Version&lt;/translate&gt;'''}}<br /> {{Joomla version|version={{CurrentSTSVer|maintenance}}|comment='''&lt;translate&gt; &lt;!--T:96--&gt; Stable Version&lt;/translate&gt;'''}}&lt;translate&gt;&lt;!--T:1--&gt;<br /> 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.&lt;/translate&gt;<br /> <br /> &lt;translate&gt;&lt;!--T:2--&gt;<br /> *Normally, you should use the latest version of Joomla! for a new site unless you have a specific reason not to.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:3--&gt;<br /> *The latest version can be downloaded from [https://downloads.joomla.org Joomla! Downloads site].&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:4--&gt;<br /> * 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.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:5--&gt;<br /> * 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.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Joomla! CMS Versions== &lt;!--T:6--&gt;<br /> &lt;/translate&gt;<br /> {| border=1 cellpadding=2 cellspacing=0 style=&quot;text-align:center; border-collapse:collapse; border-color:#000;&quot;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:7--&gt;<br /> CMS Version&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:8--&gt;<br /> Available&lt;/translate&gt;<br /> | colspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:9--&gt;<br /> Support&lt;/translate&gt;<br /> | style='display:none;' |<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:10--&gt;<br /> End of Life&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:11--&gt;<br /> Upgrade Type&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:12--&gt;<br /> Notes&lt;/translate&gt;<br /> | rowspan=2 style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:13--&gt;<br /> Latest Release&lt;/translate&gt;<br /> |-<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:14--&gt;<br /> Bugs&lt;/translate&gt;<br /> | style=&quot;text-align:center; background-color:#4a86e8; font-weight:bold;&quot; | &lt;translate&gt;&lt;!--T:15--&gt;<br /> Security&lt;/translate&gt;<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> | style='display:none;' |<br /> |-<br /> | style=&quot;background-color:#d9ead3; font-weight:bold;&quot; | 4.2<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | N/A<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:102--&gt; One-click from Joomla! 4.0&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:103--&gt; Recommeded for all new installations&lt;br/&gt;[[S:MyLanguage/Joomla 4.2 version history|Joomla! 4.2 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | {{CurrentSTSVer4|maintenance}}<br /> |-|-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 4.1<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | N/A<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:102--&gt; One-click from Joomla! 4.0&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:103--&gt; Recommeded for all new installations&lt;br/&gt;[[S:MyLanguage/Joomla 4.1 version history|Joomla! 4.1 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.1.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 4.0<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | 15.02.2024<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:99--&gt; Migration from Joomla! 3.10&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:100--&gt; Upgrade to {{CurrentSTSVer4|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 4.0 version history|Joomla! 4.0 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 4.0.6<br /> |-<br /> | style=&quot;background-color:#d9ead3; font-weight:bold;&quot; | 3.10<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | [[File:Checkmark.png|center]]<br /> | style=&quot;background-color:#d9ead3;&quot; | 17.08.2023<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:101--&gt; One-click from Joomla! 3.9&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | &lt;translate&gt;&lt;!--T:98--&gt; Recommended for migration to Joomla! 4&lt;br/&gt;[[S:MyLanguage/Joomla 3.10 version history|Joomla! 3.10 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#d9ead3;&quot; | {{CurrentSTSVer|maintenance}}<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.9&lt;ref name=&quot;roadmap&quot;&gt;&lt;translate&gt;<br /> &lt;!--T:88--&gt;<br /> See J3's [http://developer.joomla.org/cms/roadmap.html roadmap] for time frames of all future releases of all Joomla! 3 versions.&lt;/translate&gt;&lt;/ref&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:92--&gt; 3.10 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:93--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:94--&gt; Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.9 version history|Joomla! 3.9 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.9.28<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.8<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:85--&gt; 3.9 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:86--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:95--&gt; Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.8 version history|Joomla! 3.8 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.8.13<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.7<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:82--&gt; 3.8 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:83--&gt; One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;<br /> &lt;!--T:84--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.7 version history|Joomla! 3.7 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.7.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.6<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:61--&gt;<br /> 3.7 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:62--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:68--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.6 version history|Joomla! 3.6 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.6.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:46--&gt;<br /> 3.6 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:47--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:41--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[S:MyLanguage/Joomla 3.5 version history|Joomla 3.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.5.1<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.4<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:43--&gt;<br /> 3.5 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:44--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;<br /> &lt;!--T:67--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.4 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.4.8<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.3<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:39--&gt;<br /> 3.4 release&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:40--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:57--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;<br /> &lt;!--T:58--&gt;<br /> [[Joomla 3.3 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.3.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.2<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:36--&gt;<br /> Oct 2014&lt;ref&gt;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]. &lt;blockquote&gt;&quot;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.&quot;&lt;/blockquote&gt;&lt;/ref&gt;&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:37--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:38--&gt;<br /> Upgrade server's PHP to 5.3.10 or greater and upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.2 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.2.7<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 3.1<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:33--&gt;<br /> Dec 2013&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:34--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:35--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;&lt;!--T:54--&gt;<br /> [[Joomla 3.1 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.1.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; width:100px; font-weight:bold;&quot; | 3.0<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | &lt;translate&gt;&lt;!--T:30--&gt;<br /> May 2013&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc; width:100px;&quot; | &lt;translate&gt;&lt;!--T:31--&gt;<br /> One-click&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc; width:306px;&quot; | &lt;translate&gt;&lt;!--T:32--&gt;<br /> Upgrade to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 3.0 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 3.0.4<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 2.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:26--&gt;<br /> December 31st, 2014&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:27--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:28--&gt;<br /> Upgrade to&lt;/translate&gt; {{CurrentSTSVer}} &lt;translate&gt;&lt;!--T:56--&gt;<br /> now&lt;/translate&gt;&lt;br/&gt;&lt;translate&gt;&lt;!--T:29--&gt;<br /> [[Joomla 2.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | {{CurrentLTSVer|maintanence}}<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.7<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:23--&gt;<br /> Feb 2012&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:24--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:25--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.7 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 1.7.5<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.6<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:20--&gt;<br /> Aug 2011&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:21--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:22--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.6 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | 1.6.6<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.5<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:16--&gt;<br /> Sept 2012&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:17--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:18--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;br/&gt;[[Joomla 1.5 version history]]&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:19--&gt;<br /> EOL at 1.5.26&lt;/translate&gt;<br /> |-<br /> | style=&quot;background-color:#f4cccc; font-weight:bold;&quot; | 1.0<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | [[File:X-mark.png|center]]<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:69--&gt;<br /> 22 July 2009&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:70--&gt;<br /> Migration to 3.x&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:71--&gt;<br /> Plan to migrate to {{CurrentSTSVer|maintenance}} now&lt;/translate&gt;<br /> | style=&quot;background-color:#f4cccc;&quot; | &lt;translate&gt;&lt;!--T:72--&gt;<br /> EOL at 1.0.15&lt;/translate&gt;<br /> |}<br /> &lt;noinclude&gt;<br /> &lt;references /&gt;<br /> &lt;translate&gt;&lt;!--T:53--&gt;<br /> [[Category:Joomla! versions]]&lt;/translate&gt;<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Category:Version_4.2.0_FAQ&diff=956666 2022-08-22T21:44:22Z

<p>Wilsonge: Default namespace is J4</p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> {{Joomla version|version=4.2.0|}}<br /> <br /> &lt;translate&gt;&lt;!--T:1--&gt; These FAQs are specific to the Joomla! 4.2.0 release. Only issues that are specific to this release will be listed here, together with suggested resolutions. Please add information to this resource. The Joomla! Bug Squad will watch over this page to ensure any new bugs are added to the tracker and resolved. Continue to use the '''[[jforum:705|Joomla! Forums for support requests]]''' as this is not a substitute for posting there, but rather a common location for the community to gather common release issues.&lt;/translate&gt;<br /> <br /> {{&lt;translate&gt;&lt;!--T:2--&gt; Note|To appear in this category, this text is required at the foot of the page&lt;/translate&gt;:&lt;br /&gt;<br /> &lt;nowiki&gt;[[Category:Version 4.2.0 FAQ{{#translation:}}]]&lt;/nowiki&gt;|reminder}}<br /> <br /> {{TT|CreateFAQ|J4.x}}<br /> &lt;noinclude&gt; <br /> [[Category:Version 4.2 FAQ{{#translation:}}]]<br /> [[Category:Joomla! 4.2{{#translation:}}]]<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Template:TT&diff=956665 2022-08-22T21:37:20Z

<p>Wilsonge: More defaults</p> <hr /> <div>{{#ifeq:{{#titleparts:{{FULLPAGENAME}}|1|-1}}|{{#language:{{#titleparts:{{FULLPAGENAME}}|1|-1}}}}|{{ {{{1}}} | {{{2|J3.x}}} }}<br /> |{{#ifexist:Template:{{{1}}}/{{#titleparts:{{FULLPAGENAME}}|1|-1}}<br /> |{{ {{{1}}}/{{#titleparts:{{FULLPAGENAME}}|1|-1}} | {{{2|J3.x}}} }}<br /> |{{ {{{1}}}/en | {{{2|J3.x}}} }}<br /> }}<br /> }}&lt;noinclude&gt;<br /> {{documentation}}&lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Category:Version_4.2.1_FAQ&diff=956660 2022-08-22T19:58:49Z

<p>Wilsonge: </p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> {{Joomla version|version=4.2.1|}}<br /> <br /> &lt;translate&gt;&lt;!--T:1--&gt; These FAQs are specific to the Joomla! 4.2.1 release. Only issues that are specific to this release will be listed here, together with suggested resolutions. Please add information to this resource. The Joomla! Bug Squad will watch over this page to ensure any new bugs are added to the tracker and resolved. Continue to use the '''[[jforum:705|Joomla! Forums for support requests]]''' as this is not a substitute for posting there, but rather a common location for the community to gather common release issues.&lt;/translate&gt;<br /> <br /> {{&lt;translate&gt;&lt;!--T:2--&gt; Note|To appear in this category, this text is required at the foot of the page&lt;/translate&gt;:&lt;br /&gt;<br /> &lt;nowiki&gt;[[Category:Version 4.2.1 FAQ{{#translation:}}]]&lt;/nowiki&gt;|reminder}}<br /> <br /> {{TT|CreateFAQ|J4.x}}<br /> &lt;noinclude&gt; <br /> [[Category:Version 4.2 FAQ{{#translation:}}]]<br /> [[Category:Joomla! 4.2{{#translation:}}]]<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Category:Version_4.2.1_FAQ&diff=956659 2022-08-22T19:58:38Z

<p>Wilsonge: </p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> {{Joomla version|version=4.2.1|}}<br /> <br /> &lt;translate&gt;&lt;!--T:1--&gt; These FAQs are specific to the Joomla! 4.2.1 release. Only issues that are specific to this release will be listed here, together with suggested resolutions. Please add information to this resource. The Joomla! Bug Squad will watch over this page to ensure any new bugs are added to the tracker and resolved. Continue to use the '''[[jforum:705|Joomla! Forums for support requests]]''' as this is not a substitute for posting there, but rather a common location for the community to gather common release issues.&lt;/translate&gt;<br /> <br /> {{&lt;translate&gt;&lt;!--T:2--&gt; Note|To appear in this category, this text is required at the foot of the page&lt;/translate&gt;:&lt;br /&gt;<br /> &lt;nowiki&gt;[[Category:Version 4.2.1 FAQ{{#translation:}}]]&lt;/nowiki&gt;|reminder}}<br /> <br /> {{TT|(CreateFAQ|J4.x)}}<br /> &lt;noinclude&gt; <br /> [[Category:Version 4.2 FAQ{{#translation:}}]]<br /> [[Category:Joomla! 4.2{{#translation:}}]]<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Template:TT&diff=956658 2022-08-22T19:58:31Z

<p>Wilsonge: Add default for template</p> <hr /> <div>{{#ifeq:{{#titleparts:{{FULLPAGENAME}}|1|-1}}|{{#language:{{#titleparts:{{FULLPAGENAME}}|1|-1}}}}|{{ {{{1}}} | {{{2|J3.x}}} }}<br /> |{{#ifexist:Template:{{{1}}}/{{#titleparts:{{FULLPAGENAME}}|1|-1}}<br /> |{{ {{{1}}}/{{#titleparts:{{FULLPAGENAME}}|1|-1}} }}<br /> |{{ {{{1}}}/en }}<br /> }}<br /> }}&lt;noinclude&gt;<br /> {{documentation}}&lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Category:Version_4.2.1_FAQ&diff=956654 2022-08-22T19:52:07Z

<p>Wilsonge: </p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> {{Joomla version|version=4.2.1|}}<br /> <br /> &lt;translate&gt;&lt;!--T:1--&gt; These FAQs are specific to the Joomla! 4.2.1 release. Only issues that are specific to this release will be listed here, together with suggested resolutions. Please add information to this resource. The Joomla! Bug Squad will watch over this page to ensure any new bugs are added to the tracker and resolved. Continue to use the '''[[jforum:705|Joomla! Forums for support requests]]''' as this is not a substitute for posting there, but rather a common location for the community to gather common release issues.&lt;/translate&gt;<br /> <br /> {{&lt;translate&gt;&lt;!--T:2--&gt; Note|To appear in this category, this text is required at the foot of the page&lt;/translate&gt;:&lt;br /&gt;<br /> &lt;nowiki&gt;[[Category:Version 4.2.1 FAQ{{#translation:}}]]&lt;/nowiki&gt;|reminder}}<br /> <br /> {{TT|CreateFAQ|J4.x}}<br /> &lt;noinclude&gt; <br /> [[Category:Version 4.2 FAQ{{#translation:}}]]<br /> [[Category:Joomla! 4.2{{#translation:}}]]<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Category:Version_4.2.1_FAQ&diff=956653 2022-08-22T19:49:11Z

<p>Wilsonge: </p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> {{Joomla version|version=4.2.1|}}<br /> <br /> &lt;translate&gt;&lt;!--T:1--&gt; These FAQs are specific to the Joomla! 4.2.1 release. Only issues that are specific to this release will be listed here, together with suggested resolutions. Please add information to this resource. The Joomla! Bug Squad will watch over this page to ensure any new bugs are added to the tracker and resolved. Continue to use the '''[[jforum:705|Joomla! Forums for support requests]]''' as this is not a substitute for posting there, but rather a common location for the community to gather common release issues.&lt;/translate&gt;<br /> <br /> {{&lt;translate&gt;&lt;!--T:2--&gt; Note|To appear in this category, this text is required at the foot of the page&lt;/translate&gt;:&lt;br /&gt;<br /> &lt;nowiki&gt;[[Category:Version 4.2.1 FAQ{{#translation:}}]]&lt;/nowiki&gt;|reminder}}<br /> <br /> {{TT|CreateFAQ|1=J4.x}}<br /> &lt;noinclude&gt; <br /> [[Category:Version 4.2 FAQ{{#translation:}}]]<br /> [[Category:Joomla! 4.2{{#translation:}}]]<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Category:Version_4.2.1_FAQ&diff=956652 2022-08-22T19:45:29Z

<p>Wilsonge: Try passing in param</p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> {{Joomla version|version=4.2.1|}}<br /> <br /> &lt;translate&gt;&lt;!--T:1--&gt; These FAQs are specific to the Joomla! 4.2.1 release. Only issues that are specific to this release will be listed here, together with suggested resolutions. Please add information to this resource. The Joomla! Bug Squad will watch over this page to ensure any new bugs are added to the tracker and resolved. Continue to use the '''[[jforum:705|Joomla! Forums for support requests]]''' as this is not a substitute for posting there, but rather a common location for the community to gather common release issues.&lt;/translate&gt;<br /> <br /> {{&lt;translate&gt;&lt;!--T:2--&gt; Note|To appear in this category, this text is required at the foot of the page&lt;/translate&gt;:&lt;br /&gt;<br /> &lt;nowiki&gt;[[Category:Version 4.2.1 FAQ{{#translation:}}]]&lt;/nowiki&gt;|reminder}}<br /> <br /> {{TT|CreateFAQ|J4.x}}<br /> &lt;noinclude&gt; <br /> [[Category:Version 4.2 FAQ{{#translation:}}]]<br /> [[Category:Joomla! 4.2{{#translation:}}]]<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Help4.x:Admin_Modules:_Action_Logs_-_Latest&diff=927619 2022-06-30T18:26:42Z

<p>Wilsonge: removed Category:Help screen 4.2 using HotCat</p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> &lt;translate&gt;<br /> <br /> ==Description== &lt;!--T:1--&gt;<br /> &lt;/translate&gt; <br /> &lt;translate&gt;<br /> &lt;!--T:2--&gt;<br /> The '''Action Logs - Latest''' module type shows a list of the most recent actions on the Administrator '''Home Dashboard'''.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> <br /> ==How to Access== &lt;!--T:3--&gt;<br /> &lt;/translate&gt;<br /> {{safesubst:Chunk4x:ModuleManager How to Access Administrator Module/&lt;translate&gt;<br /> &lt;!--T:4--&gt;<br /> en&lt;/translate&gt;|Action Logs - Latest}}<br /> &lt;translate&gt;<br /> <br /> ==Screenshot== &lt;!--T:5--&gt;<br /> &lt;/translate&gt; <br /> [[Image:help-4x-modules-manager-admin-module-latestactions-&lt;translate&gt;<br /> &lt;!--T:6--&gt;<br /> en&lt;/translate&gt;.png|800px|none]]<br /> &lt;translate&gt;<br /> <br /> ==Form Fields== &lt;!--T:7--&gt;<br /> &lt;/translate&gt; <br /> &lt;translate&gt;<br /> &lt;!--T:8--&gt;<br /> *'''Title.''' Sets the name to give to this instance of the module. &lt;/translate&gt;<br /> &lt;translate&gt;<br /> <br /> ===Module Tab=== &lt;!--T:9--&gt; <br /> &lt;/translate&gt;<br /> *&lt;translate&gt;<br /> &lt;!--T:10--&gt;<br /> '''Count.''' Sets the number of recent actions to display on the Home Dasboard of your site.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> <br /> ===Advanced Tab=== &lt;!--T:11--&gt;<br /> &lt;/translate&gt;<br /> [[Image:Help-4x-modules-manager-admin-module-latestactions-advanced-options-&lt;translate&gt;<br /> &lt;!--T:12--&gt;<br /> en&lt;/translate&gt;.png|600px]]<br /> {{Chunk4x:ModuleManager Advanced Tab/&lt;translate&gt;<br /> &lt;!--T:13--&gt;<br /> en&lt;/translate&gt;}}<br /> &lt;translate&gt;<br /> <br /> ===Permissions Tab=== &lt;!--T:14--&gt;<br /> &lt;/translate&gt;<br /> [[Image:Help-4x-modules-manager-admin-module-latestactions-permissions-&lt;translate&gt;<br /> &lt;!--T:15--&gt;<br /> en&lt;/translate&gt;.png|600px]]<br /> {{Chunk4x:ExtensionsModuleManager-tab-Permissions/&lt;translate&gt;<br /> &lt;!--T:16--&gt;<br /> en&lt;/translate&gt;}}<br /> &lt;translate&gt;<br /> <br /> ==Toolbar== &lt;!--T:17--&gt;<br /> &lt;/translate&gt; <br /> {{safesubst:Chunk4x:Help_screen_toolbar_top_descriptor/&lt;translate&gt;<br /> &lt;!--T:18--&gt;<br /> en&lt;/translate&gt;}}<br /> {{safesubst:Chunk4x:Help_screen_toolbar_icon_Save/&lt;translate&gt;<br /> &lt;!--T:19--&gt;<br /> en&lt;/translate&gt;}}<br /> {{safesubst:Chunk4x:Help_screen_toolbar_icon_SaveAndClose/&lt;translate&gt;<br /> &lt;!--T:20--&gt;<br /> en&lt;/translate&gt;}}<br /> {{safesubst:Chunk4x:Help_screen_toolbar_icon_SaveAndNew/&lt;translate&gt;<br /> &lt;!--T:21--&gt;<br /> en&lt;/translate&gt;}}<br /> {{safesubst:Chunk4x:Help_screen_toolbar_icon_SaveAsCopy/&lt;translate&gt;<br /> &lt;!--T:22--&gt;<br /> en&lt;/translate&gt;}}<br /> {{safesubst:Chunk4x:Help_screen_toolbar_icon_Help/&lt;translate&gt;<br /> &lt;!--T:23--&gt;<br /> en&lt;/translate&gt;}}<br /> &lt;translate&gt;<br /> <br /> == Related Information== &lt;!--T:24--&gt;<br /> &lt;/translate&gt;<br /> * [[J3.x:User_Action_Logs/&lt;translate&gt;&lt;!--T:25--&gt; en|Joomla 3 Tutorial: User Action Logs&lt;/translate&gt;]]<br /> <br /> &lt;noinclude&gt;{{Cathelp|4.0|Module Manager Help Screens}}&lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Category:Help_screen_4.2&diff=927615 2022-06-30T18:25:58Z

<p>Wilsonge: Created page with &quot;&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt; &lt;translate&gt;&lt;!--T:1--&gt; Joomla 4.2 Help Screens&lt;/translate&gt;&quot;</p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt; <br /> &lt;translate&gt;&lt;!--T:1--&gt; Joomla 4.2 Help Screens&lt;/translate&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Help4.x:Admin_Modules:_Action_Logs_-_Latest&diff=927614 2022-06-30T18:25:15Z

<p>Wilsonge: added Category:Help screen 4.2 using HotCat</p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> &lt;translate&gt;<br /> <br /> ==Description== &lt;!--T:1--&gt;<br /> &lt;/translate&gt; <br /> &lt;translate&gt;<br /> &lt;!--T:2--&gt;<br /> The '''Action Logs - Latest''' module type shows a list of the most recent actions on the Administrator '''Home Dashboard'''.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> <br /> ==How to Access== &lt;!--T:3--&gt;<br /> &lt;/translate&gt;<br /> {{safesubst:Chunk4x:ModuleManager How to Access Administrator Module/&lt;translate&gt;<br /> &lt;!--T:4--&gt;<br /> en&lt;/translate&gt;|Action Logs - Latest}}<br /> &lt;translate&gt;<br /> <br /> ==Screenshot== &lt;!--T:5--&gt;<br /> &lt;/translate&gt; <br /> [[Image:help-4x-modules-manager-admin-module-latestactions-&lt;translate&gt;<br /> &lt;!--T:6--&gt;<br /> en&lt;/translate&gt;.png|800px|none]]<br /> &lt;translate&gt;<br /> <br /> ==Form Fields== &lt;!--T:7--&gt;<br /> &lt;/translate&gt; <br /> &lt;translate&gt;<br /> &lt;!--T:8--&gt;<br /> *'''Title.''' Sets the name to give to this instance of the module. &lt;/translate&gt;<br /> &lt;translate&gt;<br /> <br /> ===Module Tab=== &lt;!--T:9--&gt; <br /> &lt;/translate&gt;<br /> *&lt;translate&gt;<br /> &lt;!--T:10--&gt;<br /> '''Count.''' Sets the number of recent actions to display on the Home Dasboard of your site.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> <br /> ===Advanced Tab=== &lt;!--T:11--&gt;<br /> &lt;/translate&gt;<br /> [[Image:Help-4x-modules-manager-admin-module-latestactions-advanced-options-&lt;translate&gt;<br /> &lt;!--T:12--&gt;<br /> en&lt;/translate&gt;.png|600px]]<br /> {{Chunk4x:ModuleManager Advanced Tab/&lt;translate&gt;<br /> &lt;!--T:13--&gt;<br /> en&lt;/translate&gt;}}<br /> &lt;translate&gt;<br /> <br /> ===Permissions Tab=== &lt;!--T:14--&gt;<br /> &lt;/translate&gt;<br /> [[Image:Help-4x-modules-manager-admin-module-latestactions-permissions-&lt;translate&gt;<br /> &lt;!--T:15--&gt;<br /> en&lt;/translate&gt;.png|600px]]<br /> {{Chunk4x:ExtensionsModuleManager-tab-Permissions/&lt;translate&gt;<br /> &lt;!--T:16--&gt;<br /> en&lt;/translate&gt;}}<br /> &lt;translate&gt;<br /> <br /> ==Toolbar== &lt;!--T:17--&gt;<br /> &lt;/translate&gt; <br /> {{safesubst:Chunk4x:Help_screen_toolbar_top_descriptor/&lt;translate&gt;<br /> &lt;!--T:18--&gt;<br /> en&lt;/translate&gt;}}<br /> {{safesubst:Chunk4x:Help_screen_toolbar_icon_Save/&lt;translate&gt;<br /> &lt;!--T:19--&gt;<br /> en&lt;/translate&gt;}}<br /> {{safesubst:Chunk4x:Help_screen_toolbar_icon_SaveAndClose/&lt;translate&gt;<br /> &lt;!--T:20--&gt;<br /> en&lt;/translate&gt;}}<br /> {{safesubst:Chunk4x:Help_screen_toolbar_icon_SaveAndNew/&lt;translate&gt;<br /> &lt;!--T:21--&gt;<br /> en&lt;/translate&gt;}}<br /> {{safesubst:Chunk4x:Help_screen_toolbar_icon_SaveAsCopy/&lt;translate&gt;<br /> &lt;!--T:22--&gt;<br /> en&lt;/translate&gt;}}<br /> {{safesubst:Chunk4x:Help_screen_toolbar_icon_Help/&lt;translate&gt;<br /> &lt;!--T:23--&gt;<br /> en&lt;/translate&gt;}}<br /> &lt;translate&gt;<br /> <br /> == Related Information== &lt;!--T:24--&gt;<br /> &lt;/translate&gt;<br /> * [[J3.x:User_Action_Logs/&lt;translate&gt;&lt;!--T:25--&gt; en|Joomla 3 Tutorial: User Action Logs&lt;/translate&gt;]]<br /> <br /> &lt;noinclude&gt;{{Cathelp|4.0|Module Manager Help Screens}}&lt;/noinclude&gt;<br /> <br /> [[Category:Help screen 4.2]]</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=J3.x:Creating_a_submenu&diff=924784 2022-06-22T09:23:45Z

<p>Wilsonge: Syntax highlight to html rather than remove html4</p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> {{Top portal heading|color=white-bkgd|icon=magic|icon-color=#5091cd|size=3x|text-color=#333|title=Tutorial&lt;br /&gt;<br /> &lt;translate&gt;&lt;!--T:1--&gt;<br /> How to Create a Submenu in a Joomla! Site&lt;/translate&gt;}}<br /> &lt;noinclude&gt;{{Joomla version|version=3.x}}&lt;/noinclude&gt;<br /> &lt;translate&gt;&lt;!--T:2--&gt;<br /> In Joomla, submenus can be shown either as one menu with two or more levels or as completely separate menu modules. This is useful for constructing menus showing parent and child level navigation or for showing sublevel menu items in entirely separate positions on your template. To show how to do this, we will step through creating parent and child level menu items and then see how to show those items within one large menu and as a separate menu with only the child level items showing in a separate position on a template.&lt;/translate&gt; {{-}} <br /> __TOC__<br /> &lt;translate&gt;&lt;!--T:3--&gt;<br /> To begin, menus function with three basic constructs:&lt;/translate&gt; <br /> &lt;translate&gt;&lt;!--T:4--&gt;<br /> *Articles - you need content to link to. This can also be component pieces, other menu items or external links.&lt;/translate&gt; <br /> &lt;translate&gt;&lt;!--T:5--&gt;<br /> *Menu - describes the menu items, the type of navigation, their parent/child relationship to other menu items and the order they are displayed in.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:6--&gt;<br /> *Menu Module - controls the position and displaying of the menu.&lt;/translate&gt;<br /> <br /> &lt;translate&gt;&lt;!--T:7--&gt;<br /> For this tutorial, begin by logging into the Joomla Administrator. If you are unfamiliar with how to login see this article: [[S:MyLanguage/J3.x:Logging_in_or_out_of_the_Administrator_back-end|Logging in or out of the Administrator backend]].&lt;/translate&gt; {{-}} <br /> <br /> &lt;translate&gt;&lt;!--T:8--&gt;<br /> '''Note:''' For this tutorial you need Super Administrator permissions or permissions open enough to create and modify Articles, Menu Items, and Modules. For more information on User Access Control see: [[S:MyLanguage/J3.x:Access Control List Tutorial|ACL Tutorial]].&lt;/translate&gt;<br /> <br /> &lt;translate&gt;<br /> ==Step 1 - Create Your Articles== &lt;!--T:9--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:10--&gt;<br /> In our example, we will create top level menu items for ''Dogs'' and ''Cats''. Under Dogs, we will have ''Collies'' and ''Pomeranians''. Under Cats we will have ''Burmese'' and ''Russian Blues''. So the structure of our sample menu items will be as follows:&lt;/translate&gt;<br /> <br /> &lt;translate&gt;&lt;!--T:11--&gt;<br /> *Dogs&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:12--&gt;<br /> **Collies&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:13--&gt;<br /> **Pomeranians&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:14--&gt;<br /> *Cats&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:15--&gt;<br /> **Burmese&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:16--&gt;<br /> **Russian Blues&lt;/translate&gt;<br /> <br /> &lt;translate&gt;&lt;!--T:17--&gt;<br /> First, create 4 articles so our menu items will have something to link to: ''Collies'', ''Pomeranians'', ''Burmese'' and ''Russian Blue''. See this tutorial if you need help creating an Article: [[S:MyLanguage/Help34:Content Article Manager Edit|Adding a new Article]].&lt;/translate&gt;<br /> <br /> &lt;translate&gt;<br /> ==Step 2 - Create the Parent Level Menu Items== &lt;!--T:18--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:19--&gt;<br /> To create the structure, we need to navigate to the menu where we want our new menu items. If this is a new menu, you will need to create it. See this tutorial on how to create a menu: [[S:MyLanguage/J3.x:Adding a new menu|Adding a new menu]].&lt;/translate&gt; <br /> <br /> &lt;translate&gt;&lt;!--T:20--&gt;<br /> Once you have your menu located in the Menu Manager, you will add the parent menu items using the '''System Links'''{{rarr}}'''External URL''' for each navigation link: ''Dogs'' and ''Cats''.&lt;/translate&gt; <br /> <br /> &lt;translate&gt;&lt;!--T:21--&gt;<br /> Please note, there are other menu item types that can be used for the parent level navigation structure.&lt;/translate&gt; <br /> <br /> &lt;translate&gt;&lt;!--T:22--&gt;<br /> Here are the steps to create sample Menu Items using our example data. For more information on creating Menu Items see: [[S:MyLanguage/J3.x:Adding a new menu|Adding a new menu item]].&lt;/translate&gt; {{-}} <br /> &lt;translate&gt;&lt;!--T:23--&gt;<br /> # Navigate to the Menu Manager by clicking on '''Menus'''{{rarr}}'''Menu Manager'''&lt;/translate&gt;{{-}}[[Image:J3x-Edit-Main-Menu-&lt;translate&gt;&lt;!--T:24--&gt;<br /> en&lt;/translate&gt;.jpg|775px|border]]<br /> &lt;translate&gt;&lt;!--T:25--&gt;<br /> # In the toolbar, click on ''New''&lt;/translate&gt;{{-}}[[Image:J3x-Edit-Main-Menu-Toolbar-new-&lt;translate&gt;&lt;!--T:26--&gt;<br /> en&lt;/translate&gt;.png|775px|border]]<br /> &lt;translate&gt;&lt;!--T:27--&gt;<br /> # For the purposes of this exercise we are creating &quot;placeholder&quot; links using the '''System'''{{rarr}}'''External URL''' menu type for the ''Dogs'' and ''Cats'' parent level menu items. So, in the new Menu Item, click on the Menu Type select button:&lt;/translate&gt; {{-}}[[Image:J3x-Add-Main-Menu-Select-Type-&lt;translate&gt;&lt;!--T:28--&gt;<br /> en&lt;/translate&gt;.png|775px|border]]<br /> &lt;translate&gt;&lt;!--T:29--&gt;<br /> # Click on ''System Links'' then scroll down and select ''External URL''.&lt;/translate&gt;{{-}}[[Image:J3x-Create-Sublevel-Menu-System-External-Url-&lt;translate&gt;&lt;!--T:30--&gt;<br /> en&lt;/translate&gt;.png|775px|border]]<br /> &lt;translate&gt;&lt;!--T:31--&gt;<br /> # Add the '''Menu Item Title''' (&quot;Dogs&quot;) and type in a hashtag &quot;#&quot; in the '''Link''' box.&lt;/translate&gt;{{-}}[[Image:J3x-Create-Sublevel-Menu-Menu-Item-External-Url-&lt;translate&gt;&lt;!--T:32--&gt;<br /> en&lt;/translate&gt;.png|775px|border]]<br /> &lt;translate&gt;&lt;!--T:33--&gt;<br /> # Save your menu item.&lt;/translate&gt; {{-}}[[Image:Joomla-3-Menu-Add-Menu-Save-&lt;translate&gt;&lt;!--T:34--&gt;<br /> en&lt;/translate&gt;.png|775px|border]]<br /> &lt;translate&gt;&lt;!--T:35--&gt;<br /> # Repeat steps 2 - 6 for the ''Cats'' Parent Level menu item.&lt;/translate&gt;<br /> <br /> &lt;translate&gt;<br /> ==Step 3 - Create the Sublevel Menu Items== &lt;!--T:36--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:37--&gt;<br /> Now you will add the sublevel menu items using the '''Articles'''{{rarr}}'''Single Article''' to create menu links to the individual pages ''Collies'', ''Pomeranians'', ''Burmese'', and ''Russian Blues''. For each Menu Item created, we will set the '''Parentage''' to ''Dogs'' or ''Cats''.&lt;/translate&gt;<br /> <br /> &lt;translate&gt;&lt;!--T:38--&gt;<br /> For more detailed information on how to create a Single Article Menu Type, see: [[S:MyLanguage/Adding a menu item which points to an Article|Adding a menu item which points to an Article]].&lt;/translate&gt;<br /> <br /> &lt;translate&gt;&lt;!--T:39--&gt;<br /> '''Note:''' There are other menu item types that can be used for the sublevel navigation structure.&lt;/translate&gt; <br /> <br /> &lt;translate&gt;&lt;!--T:40--&gt;<br /> # In the toolbar, click on &quot;New&quot;.&lt;/translate&gt;{{-}}[[Image:J3x-Edit-Main-Menu-Toolbar-new-&lt;translate&gt;&lt;!--T:41--&gt;<br /> en&lt;/translate&gt;.png|775px|border]]<br /> &lt;translate&gt;&lt;!--T:42--&gt;<br /> # In the new Menu Item click on the Menu Type select button:&lt;/translate&gt;{{-}}[[Image:J3x-Add-Main-Menu-Select-Type-&lt;translate&gt;&lt;!--T:43--&gt;<br /> en&lt;/translate&gt;.png|775px|border]]<br /> &lt;translate&gt;&lt;!--T:44--&gt;<br /> # Select '''Articles'''{{rarr}}'''Single Article''' from the list displayed.&lt;/translate&gt;{{-}}[[Image:J3x-Add-Main-Menu-Article-Type-&lt;translate&gt;&lt;!--T:45--&gt;<br /> en&lt;/translate&gt;.png|border]]<br /> &lt;translate&gt;&lt;!--T:46--&gt;<br /> # Returning to the Menu Item Detail page, click on the '''Select Article''' List.&lt;/translate&gt;{{-}}[[Image:J3x-Add-Main-Menu-Article-Select-Article-&lt;translate&gt;&lt;!--T:47--&gt;<br /> en&lt;/translate&gt;.png|border]]<br /> &lt;translate&gt;&lt;!--T:48--&gt;<br /> # Select the ''Collies'' article for this example.&lt;/translate&gt;{{-}}[[Image:J3x-Create-Sublevel-Menu-Menu-Item-Single-Article-&lt;translate&gt;&lt;!--T:49--&gt;<br /> en&lt;/translate&gt;.png|border]]<br /> &lt;translate&gt;&lt;!--T:50--&gt;<br /> # On returning to the Article Detail page, fill in the ''Menu Item Title''.&lt;/translate&gt; &lt;translate&gt;&lt;!--T:51--&gt;<br /> Then click on the '''Parent Item''' select list located in the far right column. Find and select the ''Dogs'' parent item by scrolling through the Parent Item List. Note that menu levels are displayed with dashes: &quot;-&quot; (single dash) is the highest level, &quot;--&quot; (two dashes) is the second level, &quot;---&quot; third level and so on.&lt;/translate&gt; {{-}}[[Image:J3x-Create-Sublevel-Menu-Select-Parent-Item-&lt;translate&gt;&lt;!--T:52--&gt;<br /> en&lt;/translate&gt;.png|775px|border]]<br /> &lt;translate&gt;&lt;!--T:53--&gt;<br /> # Click on the button '''Save &amp; Close''' up in the top button.&lt;/translate&gt;{{-}}[[Image:Joomla-3-Menu-Add-Menu-Save-&lt;translate&gt;&lt;!--T:54--&gt;<br /> en&lt;/translate&gt;.png|775px|border]] <br /> &lt;translate&gt;&lt;!--T:55--&gt;<br /> # Repeat steps 1-7 for the remaining articles ''Pomeranians'' with the ''Dog'' parent and articles ''Burmese'' and ''Russian Blues'' for the ''Cat'' parent.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:56--&gt;<br /> # When you are finished with the &quot;Menu Items&quot; section, the Menu Item Manager should look very similar to the following:&lt;/translate&gt;{{-}}[[Image:J3x-Create-Sublevel-Menu-Items-&lt;translate&gt;&lt;!--T:57--&gt;<br /> en&lt;/translate&gt;.png|775px|border]]<br /> <br /> &lt;translate&gt;<br /> <br /> ==Step 4 - Setup the Menu Module== &lt;!--T:58--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:59--&gt;<br /> At this point, we have our Articles and Menu Items done. Now we need to update the '''Menu Module'''. In Joomla!, the Menu Module determines three main things:&lt;/translate&gt; <br /> &lt;translate&gt;&lt;!--T:60--&gt;<br /> # What the menu looks like;&lt;/translate&gt; <br /> &lt;translate&gt;&lt;!--T:61--&gt;<br /> # Where on the page it will show;&lt;/translate&gt; <br /> &lt;translate&gt;&lt;!--T:62--&gt;<br /> # Which pages it will show on.&lt;/translate&gt; <br /> <br /> &lt;translate&gt;&lt;!--T:63--&gt;<br /> We will do two examples:&lt;/translate&gt; <br /> &lt;translate&gt;&lt;!--T:64--&gt;<br /> * In the first example, we will set the parameters that show the parent level menu items with the lower level items beneath.&lt;/translate&gt; <br /> &lt;translate&gt;&lt;!--T:65--&gt;<br /> * In the second example, we will add an additional menu module that appears in the left column and shows only the second level menu items.&lt;/translate&gt; <br /> &lt;translate&gt;&lt;!--T:66--&gt;<br /> '''Note:''' We will do both examples using the Protostar Template included in the core Joomla! installation.&lt;/translate&gt;<br /> <br /> &lt;translate&gt;<br /> ===Example 1 - One Menu Module With Second Level Menu Items=== &lt;!--T:67--&gt;<br /> &lt;/translate&gt; <br /> &lt;translate&gt;&lt;!--T:68--&gt;<br /> To show this as one module, follow these steps:&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:69--&gt;<br /> # Navigate to '''Extensions'''{{rarr}}'''Module Manager''' and locate the Menu Module associated with your menu. If you need to create a new menu module, for instructions on creating a menu module, see:&lt;/translate&gt; [[S:MyLanguage/Help34:Extensions Module Manager Menu|Module Menu]] {{-}}[[Image:J3x-Create-Sublevel-Menu-Module-Control-Panel-&lt;translate&gt;&lt;!--T:70--&gt;<br /> en&lt;/translate&gt;.png|775px|border]]<br /> &lt;translate&gt;&lt;!--T:71--&gt;<br /> # Click on the module name associated with your menu. In this tutorial, we are selecting '''Main Menu'''. ''Note:'' this image has been filtered by selecting ''Menu'' in the Module type dropdown.&lt;/translate&gt;{{-}}[[Image:J3x-Create-Sublevel-Menu-Module-List-Menus-&lt;translate&gt;&lt;!--T:72--&gt;<br /> en&lt;/translate&gt;.png|775px|border]]<br /> &lt;translate&gt;&lt;!--T:73--&gt;<br /> # In the Module details, set the '''Start level''' to ''1'', the '''End Level''' to ''All'' and set '''Show Submenu Items''' to ''Yes''.&lt;/translate&gt;{{-}}[[Image:J3x-Create-Sublevel-Menu-Module-Details-&lt;translate&gt;&lt;!--T:74--&gt;<br /> en&lt;/translate&gt;.png|775px|border]] <br /> &lt;translate&gt;&lt;!--T:75--&gt;<br /> # For this tutorial, we have added some styling in the '''Advanced''' tab. In the '''Menu Class Suffix''' we have entered ''navbar-nav nav-pills''. You can also add ''navbar-nav nav-tabs'' for a slightly different look. Note: there is a space before ''navbar-nav''.&lt;/translate&gt;{{-}}[[Image:J3x-Create-Sublevel-Menu-Module-Advanced-Menu-Class-Suffix-&lt;translate&gt;&lt;!--T:76--&gt;<br /> en&lt;/translate&gt;.png|border]]<br /> &lt;translate&gt;&lt;!--T:77--&gt;<br /> # Click on '''Save &amp; Close'''.&lt;/translate&gt;{{-}}[[Image:J3x-Create-Sublevel-Menu-Module-Save-&lt;translate&gt;&lt;!--T:78--&gt;<br /> en&lt;/translate&gt;.png|border]] <br /> &lt;translate&gt;&lt;!--T:79--&gt;<br /> # Go to the frontend of your site and your menu should look similar to this. In the Protostar Template, the sublevel menu items are displayed as dropdown menu items.&lt;/translate&gt;{{-}}[[Image:J3x-Create-Sublevel-Menu-Frontend-Sample-Dropdown-&lt;translate&gt;&lt;!--T:80--&gt;<br /> en&lt;/translate&gt;.png|775px|border]]<br /> &lt;translate&gt;&lt;!--T:81--&gt;<br /> # The source code generated will look similar to this:&lt;/translate&gt;<br /> &lt;source lang=&quot;html&quot;&gt;<br /> &lt;ul class=&quot;nav menu navbar-nav nav-pills&quot;&gt;<br /> &lt;li class=&quot;item-101 current active&quot;&gt;&lt;a href=&quot;/&quot; &gt;Home&lt;/a&gt;&lt;/li&gt;<br /> &lt;li class=&quot;item-102&quot;&gt;&lt;a class=&quot;dropdown-toggle&quot; href=&quot;/about-us&quot; &gt;About Us&lt;/a&gt;&lt;/li&gt;<br /> &lt;li class=&quot;item-210 deeper parent&quot;&gt;&lt;a href=&quot;#&quot; &gt;Dogs&lt;/a&gt;<br /> &lt;ul class=&quot;nav-child unstyled small&quot;&gt;<br /> &lt;li class=&quot;item-212&quot;&gt;&lt;a href=&quot;/2015-11-24-14-19-31/collies&quot; &gt;Collies&lt;/a&gt;&lt;/li&gt;<br /> &lt;li class=&quot;item-213&quot;&gt;&lt;a href=&quot;/2015-11-24-14-19-31/pomeranians&quot; &gt;Pomeranians&lt;/a&gt;&lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/li&gt;<br /> &lt;li class=&quot;item-211 deeper parent&quot;&gt;&lt;a href=&quot;#&quot; &gt;Cats&lt;/a&gt;<br /> &lt;ul class=&quot;nav-child unstyled small&quot;&gt;<br /> &lt;li class=&quot;item-214&quot;&gt;&lt;a href=&quot;/2015-11-24-14-20-12/burmese&quot; &gt;Burmese &lt;/a&gt;&lt;/li&gt;<br /> &lt;li class=&quot;item-215&quot;&gt;&lt;a href=&quot;/2015-11-24-14-20-12/russian-blues&quot; &gt;Russian Blues&lt;/a&gt;&lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/source&gt;<br /> <br /> &lt;translate&gt;<br /> ===Example 2 - A Second Menu Module With Child Level Menu Items=== &lt;!--T:82--&gt;<br /> &lt;/translate&gt; <br /> <br /> &lt;translate&gt;&lt;!--T:83--&gt;<br /> To show in a separate module in a different position, follow these steps:&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:84--&gt;<br /> # Navigate to '''Extensions'''{{rarr}}'''Module Manager''' and locate or create a second Menu Module associated with your menu. If you are unfamiliar with how to create a new menu module, for instructions on creating a menu module, see:&lt;/translate&gt; &lt;translate&gt;&lt;!--T:85--&gt;<br /> [[S:MyLanguage/Help34:Extensions Module Manager Menu|Module Menu]]&lt;/translate&gt;{{-}}[[Image:J3x-Create-Sublevel-Menu-Module-Control-Panel-&lt;translate&gt;&lt;!--T:86--&gt;<br /> en&lt;/translate&gt;.png|775px|border]] <br /> &lt;translate&gt;&lt;!--T:87--&gt;<br /> # Click on the module name associated with your menu. In this tutorial, we are selecting ''Left Menu''. Note: this image has been filtered by selecting ''Menu'' in the Module type dropdown.&lt;/translate&gt;{{-}}[[Image:J3x-Create-Sublevel-Menu-Module-List-Menus-2-&lt;translate&gt;&lt;!--T:88--&gt;<br /> en&lt;/translate&gt;.png|775px|border]] <br /> &lt;translate&gt;&lt;!--T:89--&gt;<br /> # In the Module details, set the '''Start level''' to ''2'', the '''End Level''' to ''All'' and set '''Show Submenu Items''' to ''Yes''. Note the position has changed and the menu we are pointing to is the '''Main Menu'''.&lt;/translate&gt;{{-}}[[Image:J3x-Create-Sublevel-Menu-Module-Details-2-&lt;translate&gt;&lt;!--T:90--&gt;<br /> en&lt;/translate&gt;.png|775px|border]] <br /> &lt;translate&gt;&lt;!--T:91--&gt;<br /> # For this tutorial, we have used the '''Menu Assignment''' tab and assigned this Menu Module to appear on all pages except the home page.&lt;/translate&gt;{{-}}[[Image:J3x-Create-Sublevel-Menu-Module-Module-Assignment-Tab-&lt;translate&gt;&lt;!--T:92--&gt;<br /> en&lt;/translate&gt;.png]]<br /> &lt;translate&gt;&lt;!--T:93--&gt;<br /> # Click on '''Save &amp; Close'''.&lt;/translate&gt;{{-}}[[Image:J3x-Create-Sublevel-Menu-Module-Save-&lt;translate&gt;&lt;!--T:94--&gt;<br /> en&lt;/translate&gt;.png]] <br /> &lt;translate&gt;&lt;!--T:95--&gt;<br /> # Go to the frontend of your site and navigate to the ''Collies'' article. Your menu should look similar to this. Notice the child level subitems are the only items showing.&lt;/translate&gt;{{-}}[[Image:J3x-Create-Sublevel-Menu-Frontend-Sample-Child-Menu-&lt;translate&gt;&lt;!--T:96--&gt;<br /> en&lt;/translate&gt;.png|775px|border]]<br /> &lt;translate&gt;&lt;!--T:97--&gt;<br /> # The source code generated will look similar to this:&lt;/translate&gt;<br /> &lt;source lang=&quot;html&quot;&gt;<br /> &lt;ul class=&quot;nav menu&quot;&gt;<br /> &lt;li class=&quot;item-212 current active&quot;&gt;&lt;a href=&quot;/2015-11-24-14-19-31/collies&quot; &gt;Collies&lt;/a&gt;&lt;/li&gt;<br /> &lt;li class=&quot;item-213&quot;&gt;&lt;a href=&quot;/2015-11-24-14-19-31/pomeranians&quot; &gt;Pomeranians&lt;/a&gt;&lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/source&gt;<br /> <br /> &lt;translate&gt;<br /> <br /> ==Sub-Sub-Menus== &lt;!--T:98--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:99--&gt;<br /> Using this same technique, it is easy to create third-level sub-menus. You just make the Parent Menu Item a second-level sub-menu. Then you could use the same technique to create a separate Menu Module with Start Level of 2 and End Level of 3. This would show only the third-level Menu Items.&lt;/translate&gt;<br /> <br /> &lt;noinclude&gt;<br /> &lt;translate&gt;<br /> &lt;!--T:100--&gt;<br /> [[Category:Beginners]]<br /> [[Category:Tutorials]]<br /> [[Category:Joomla! 3.x]]<br /> [[Category:Menu Management]]<br /> &lt;/translate&gt;<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Absolute_Basics_of_How_a_Component_Functions&diff=924783 2022-06-22T09:18:05Z

<p>Wilsonge: Revert back</p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> &lt;translate&gt;&lt;!--T:1--&gt;<br /> This article is designed for Joomlaǃ beginners; it is designed to explain what a Joomlaǃ component is and how it functions. When a specific component example will benefit the tutorial, this article will refer to an example component named Hello Worldǃ.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==What is a Joomlaǃ Component== &lt;!--T:2--&gt;<br /> &lt;/translate&gt;<br /> {{Chunk:Component/&lt;translate&gt;&lt;!--T:58--&gt;<br /> en&lt;/translate&gt;}}<br /> &lt;translate&gt;&lt;!--T:5--&gt;<br /> In the Joomla! framework, components can be designed using a flat model (returns HTML code for the requested page) or Model-View-Controller (herein referred to as MVC) pattern.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Introduction to MVC== &lt;!--T:6--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:7--&gt;<br /> MVC is a software design pattern that can be used to organize code in such a way that the business logic and data presentation are separate. The premise behind this approach is that if the business logic is grouped into one section, then the interface and user interaction that surrounds the data can be revised and customized without having to reprogram the business logic. MVC was originally developed to map the traditional input, processing, output roles into a logical GUI architecture.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ===Model=== &lt;!--T:8--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:9--&gt;<br /> The model is the part of the component that encapsulates the application's data. It will often provide routines to manage and manipulate this data in a meaningful way in addition to routines that retrieve the data from the model. In general, the underlying data access technique should be encapsulated in the model. In this way, if an application is to be moved from a system that utilizes a flat file to store its information to a system that uses a database, the model is the only element that needs to be changed, not the view or the controller.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ===View=== &lt;!--T:10--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:11--&gt;<br /> The view is the part of the component that is used to render the data from the model in a manner that is suitable for interaction. For a web-based application, the view would generally be an HTML page that is returned to the user. The view pulls data from the model (which is passed to it from the controller) and feeds the data into a template which is populated and presented to the user. The view does not cause the data to be modified in any way, it only displays the data received from the model.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ===Controller=== &lt;!--T:12--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:13--&gt;<br /> The controller is responsible for responding to user actions. In the case of a web application, a user action is generally a page request. The controller will determine what request is being made by the user and respond appropriately by triggering the model to manipulate the data appropriately and passing the model into the view. The controller does not display the data in the model, it only triggers methods in the model which modify the data, and then pass the model into the view which displays the data.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> == Joomla! Component Framework Explained == &lt;!--T:14--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;<br /> === Model === &lt;!--T:15--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:16--&gt;<br /> In the Joomla framework, models are responsible for managing the data. The first function that has to be written for a model is a get function. It returns data to the caller. For this example, the caller will be the HelloWorldViewHelloWorld view. By default, the model named HelloWorldModelHelloWorld residing in site/models/helloworld.php is the main model associated to this view.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:17--&gt;<br /> So let's have a quick look at the naming conventions with an example, since the naming convention are the actual magic that make everything work:&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:18--&gt;<br /> The class ''HelloWorldView'''HelloWorld''''' resides in ''site/views/'''helloworld'''/view.html.php'' and will make use of the class ''HelloWorldModel'''HelloWorld''''' in the file ''site/models/'''helloworld'''.php''&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:19--&gt;<br /> Let's just assume we want to use an imaginary view ''fluffy'', you would have to have:&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:20--&gt;<br /> The class ''HelloWorldView'''Fluffy''''' which resides in ''site/views/'''fluffy'''/view.html.php''. The view will make use of ''HelloWorldModel'''Fluffy''''' in the file ''site/models/'''fluffy'''.php''. Note: the actual screen of the view: ''site/views/'''fluffy'''/tmpl/default.php'' is required as well to make this example work.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:21--&gt;<br /> Breaking any of these bold conventions will lead to errors or a blank page.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Accessing a Joomlaǃ Component== &lt;!--T:22--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:23--&gt;<br /> First we need to access the Joomla! platform, which is always accessed through a single point of entry. Using your preferred web browser, navigate to the following URL:&lt;/translate&gt;<br /> {| border=1<br /> | 1<br /> | &lt;translate&gt;&lt;!--T:24--&gt;<br /> user access&lt;/translate&gt;<br /> | &lt;translate&gt;&lt;!--T:25--&gt;<br /> &lt;tt&gt;&lt;yoursite&gt;/joomla/index.php&lt;/tt&gt;&lt;/translate&gt;<br /> |-<br /> | 2<br /> | &lt;translate&gt;&lt;!--T:26--&gt;<br /> administrator access&lt;/translate&gt; <br /> | &lt;translate&gt;&lt;!--T:27--&gt;<br /> &lt;tt&gt;&lt;yoursite&gt;/joomla/administrator/index.php&lt;/tt&gt;&lt;/translate&gt;<br /> |}<br /> &lt;translate&gt;&lt;!--T:28--&gt;<br /> Hello World! example:&lt;/translate&gt; &lt;tt&gt;localhost/joomla/index.php&lt;/tt&gt;<br /> &lt;translate&gt;&lt;!--T:29--&gt;<br /> You can use the URL of the component, or a [[#Menu| Menu]] in order to navigate to the component. In this article we will discuss using the URL.&lt;/translate&gt;<br /> {| border=1<br /> | 1<br /> | &lt;translate&gt;&lt;!--T:30--&gt;<br /> user access&lt;/translate&gt;<br /> | &lt;translate&gt;&lt;!--T:31--&gt;<br /> &lt;tt&gt;&lt;yoursite&gt;/joomla/index.php?option=com_&lt;component_name&gt;&lt;/tt&gt;&lt;/translate&gt;<br /> |-<br /> | 2<br /> | &lt;translate&gt;&lt;!--T:32--&gt;<br /> administrator access&lt;/translate&gt; <br /> | &lt;translate&gt;&lt;!--T:33--&gt;<br /> &lt;tt&gt;&lt;yoursite&gt;/joomla/administrator/index.php?option=com_&lt;component_name&gt;&lt;/tt&gt;&lt;/translate&gt;<br /> |}<br /> &lt;translate&gt;&lt;!--T:34--&gt;<br /> Hello World! example:&lt;/translate&gt; &lt;tt&gt;localhost/joomla/index.php?option=com_helloworld&lt;/tt&gt;<br /> &lt;translate&gt;<br /> ==MVC Basic Directory Structure== &lt;!--T:35--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:36--&gt;<br /> Components are stored in a directory within your Joomla! installation, specifically at:<br /> *&lt;tt&gt;htdocs/&lt;path_to_joomla&gt;/components/com_&lt;component_name&gt;/&lt;/tt&gt; .&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:37--&gt;<br /> The Hello World! component would be stored in &lt;tt&gt; htdocs/&lt;path_to_joomla&gt;/components/com_helloworld/&lt;/tt&gt;.&lt;/translate&gt; <br /> &lt;translate&gt;&lt;!--T:38--&gt;<br /> A basic component will contain the following files within its directoryː&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:39--&gt;<br /> *An HTML file that is just a security file with a background colorː &lt;tt&gt;index.html&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:40--&gt;<br /> *A PHP file that represents the controller itselfː &lt;tt&gt;controller.php&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:41--&gt;<br /> *A PHP file that loads the controller classː &lt;tt&gt;&lt;component_name&gt;.php&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:42--&gt;<br /> *A PHP file that represents the model itselfː &lt;tt&gt;models/&lt;component_name&gt;.php&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:43--&gt;<br /> *Another HTML file for background controlː &lt;tt&gt;models/index.html&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:44--&gt;<br /> *A PHP file containing the default viewː &lt;tt&gt;views/&lt;component_name&gt;/tmpl/default.php&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:45--&gt;<br /> *An XML file for adding a menu item typeː &lt;tt&gt;views/&lt;component_name&gt;/tmpl/default.xml&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:46--&gt;<br /> *Another HTML file for background controlː &lt;tt&gt;views/&lt;component_name&gt;/tmpl/index.html&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:47--&gt;<br /> *Another HTML file for background controlː &lt;tt&gt;views/&lt;component_name&gt;/index.html&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:48--&gt;<br /> *A PHP file for displaying the viewː &lt;tt&gt;views/&lt;component_name&gt;/view.html.php&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==JEXEC== &lt;!--T:49--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:50--&gt;<br /> The following line is commonly found at the start of Joomla! PHP files:&lt;/translate&gt;<br /> &lt;source lang=&quot;php&quot;&gt;<br /> &lt;?php<br /> defined('_JEXEC') or die('Restricted Access');<br /> &lt;/source&gt;<br /> &lt;translate&gt;&lt;!--T:51--&gt;<br /> This enables a secure entry point into the Joomla! platform. [[S:MyLanguage/JEXEC| JEXEC]] contains a detailed explanation.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Tutorials on Designing a MVC Component== &lt;!--T:52--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:53--&gt;<br /> To learn how to design your own MVC Component, please complete the tutorial for your Joomla! version.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:54--&gt;<br /> * [[S:MyLanguage/J1.5:Developing_a_MVC_Component/Introduction| Joomla! 1.5]]&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:55--&gt;<br /> * [[S:MyLanguage/J2.5:Developing_a_MVC_Component| Joomla! 2.5]]&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:56--&gt;<br /> * [[S:MyLanguage/J3.x:Developing_an_MVC_Component/Introduction| Joomla! 3.x]]<br /> * [[S:MyLanguage/J4.x:Developing_an_MVC_Component| Joomla! 4.x]]&lt;/translate&gt;<br /> <br /> &lt;noinclude&gt;<br /> [[Category:Tutorials{{#translation:}}]]<br /> [[Category:Explanations{{#translation:}}]]<br /> [[Category:Component Development{{#translation:}}]]<br /> [[Category:Beginner Development{{#translation:}}]]<br /> [[Category:Development Recommended Reading{{#translation:}}]]<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Absolute_Basics_of_How_a_Component_Functions&diff=924782 2022-06-22T09:16:11Z

<p>Wilsonge: Oops</p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> &lt;translate&gt;&lt;!--T:1--&gt;<br /> This article is designed for Joomlaǃ beginners; it is designed to explain what a Joomlaǃ component is and how it functions. When a specific component example will benefit the tutorial, this article will refer to an example component named Hello Worldǃ.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==What is a Joomlaǃ Component== &lt;!--T:2--&gt;<br /> &lt;/translate&gt;<br /> {{Chunk:Component/&lt;translate&gt;&lt;!--T:58--&gt;<br /> en&lt;/translate&gt;}}<br /> &lt;translate&gt;&lt;!--T:5--&gt;<br /> In the Joomla! framework, components can be designed using a flat model (returns HTML code for the requested page) or Model-View-Controller (herein referred to as MVC) pattern.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Introduction to MVC== &lt;!--T:6--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:7--&gt;<br /> MVC is a software design pattern that can be used to organize code in such a way that the business logic and data presentation are separate. The premise behind this approach is that if the business logic is grouped into one section, then the interface and user interaction that surrounds the data can be revised and customized without having to reprogram the business logic. MVC was originally developed to map the traditional input, processing, output roles into a logical GUI architecture.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ===Model=== &lt;!--T:8--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:9--&gt;<br /> The model is the part of the component that encapsulates the application's data. It will often provide routines to manage and manipulate this data in a meaningful way in addition to routines that retrieve the data from the model. In general, the underlying data access technique should be encapsulated in the model. In this way, if an application is to be moved from a system that utilizes a flat file to store its information to a system that uses a database, the model is the only element that needs to be changed, not the view or the controller.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ===View=== &lt;!--T:10--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:11--&gt;<br /> The view is the part of the component that is used to render the data from the model in a manner that is suitable for interaction. For a web-based application, the view would generally be an HTML page that is returned to the user. The view pulls data from the model (which is passed to it from the controller) and feeds the data into a template which is populated and presented to the user. The view does not cause the data to be modified in any way, it only displays the data received from the model.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ===Controller=== &lt;!--T:12--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:13--&gt;<br /> The controller is responsible for responding to user actions. In the case of a web application, a user action is generally a page request. The controller will determine what request is being made by the user and respond appropriately by triggering the model to manipulate the data appropriately and passing the model into the view. The controller does not display the data in the model, it only triggers methods in the model which modify the data, and then pass the model into the view which displays the data.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> == Joomla! Component Framework Explained == &lt;!--T:14--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;<br /> === Model === &lt;!--T:15--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:16--&gt;<br /> In the Joomla framework, models are responsible for managing the data. The first function that has to be written for a model is a get function. It returns data to the caller. For this example, the caller will be the HelloWorldViewHelloWorld view. By default, the model named HelloWorldModelHelloWorld residing in site/models/helloworld.php is the main model associated to this view.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:17--&gt;<br /> So let's have a quick look at the naming conventions with an example, since the naming convention are the actual magic that make everything work:&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:18--&gt;<br /> The class ''HelloWorldView'''HelloWorld''''' resides in ''site/views/'''helloworld'''/view.html.php'' and will make use of the class ''HelloWorldModel'''HelloWorld''''' in the file ''site/models/'''helloworld'''.php''&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:19--&gt;<br /> Let's just assume we want to use an imaginary view ''fluffy'', you would have to have:&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:20--&gt;<br /> The class ''HelloWorldView'''Fluffy''''' which resides in ''site/views/'''fluffy'''/view.html.php''. The view will make use of ''HelloWorldModel'''Fluffy''''' in the file ''site/models/'''fluffy'''.php''. Note: the actual screen of the view: ''site/views/'''fluffy'''/tmpl/default.php'' is required as well to make this example work.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:21--&gt;<br /> Breaking any of these bold conventions will lead to errors or a blank page.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Accessing a Joomlaǃ Component== &lt;!--T:22--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:23--&gt;<br /> First we need to access the Joomla! platform, which is always accessed through a single point of entry. Using your preferred web browser, navigate to the following URL:&lt;/translate&gt;<br /> {| border=1<br /> | 1<br /> | &lt;translate&gt;&lt;!--T:24--&gt;<br /> user access&lt;/translate&gt;<br /> | &lt;translate&gt;&lt;!--T:25--&gt;<br /> &lt;tt&gt;&lt;yoursite&gt;/joomla/index.php&lt;/tt&gt;&lt;/translate&gt;<br /> |-<br /> | 2<br /> | &lt;translate&gt;&lt;!--T:26--&gt;<br /> administrator access&lt;/translate&gt; <br /> | &lt;translate&gt;&lt;!--T:27--&gt;<br /> &lt;tt&gt;&lt;yoursite&gt;/joomla/administrator/index.php&lt;/tt&gt;&lt;/translate&gt;<br /> |}<br /> &lt;translate&gt;&lt;!--T:28--&gt;<br /> Hello World! example:&lt;/translate&gt; &lt;tt&gt;localhost/joomla/index.php&lt;/tt&gt;<br /> &lt;translate&gt;&lt;!--T:29--&gt;<br /> You can use the URL of the component, or a [[#Menu| Menu]] in order to navigate to the component. In this article we will discuss using the URL.&lt;/translate&gt;<br /> {| border=1<br /> | 1<br /> | &lt;translate&gt;&lt;!--T:30--&gt;<br /> user access&lt;/translate&gt;<br /> | &lt;translate&gt;&lt;!--T:31--&gt;<br /> &lt;tt&gt;&lt;yoursite&gt;/joomla/index.php?option=com_&lt;component_name&gt;&lt;/tt&gt;&lt;/translate&gt;<br /> |-<br /> | 2<br /> | &lt;translate&gt;&lt;!--T:32--&gt;<br /> administrator access&lt;/translate&gt; <br /> | &lt;translate&gt;&lt;!--T:33--&gt;<br /> &lt;tt&gt;&lt;yoursite&gt;/joomla/administrator/index.php?option=com_&lt;component_name&gt;&lt;/tt&gt;&lt;/translate&gt;<br /> |}<br /> &lt;translate&gt;&lt;!--T:34--&gt;<br /> Hello World! example:&lt;/translate&gt; &lt;tt&gt;localhost/joomla/index.php?option=com_helloworld&lt;/tt&gt;<br /> &lt;translate&gt;<br /> ==MVC Basic Directory Structure== &lt;!--T:35--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:36--&gt;<br /> Components are stored in a directory within your Joomla! installation, specifically at:<br /> *&lt;tt&gt;htdocs/&lt;path_to_joomla&gt;/components/com_&lt;component_name&gt;/&lt;/tt&gt; .&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:37--&gt;<br /> The Hello World! component would be stored in &lt;tt&gt; htdocs/&lt;path_to_joomla&gt;/components/com_helloworld/&lt;/tt&gt;.&lt;/translate&gt; <br /> &lt;translate&gt;&lt;!--T:38--&gt;<br /> A basic component will contain the following files within its directoryː&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:39--&gt;<br /> *An HTML file that is just a security file with a background colorː &lt;tt&gt;index.html&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:40--&gt;<br /> *A PHP file that represents the controller itselfː &lt;tt&gt;controller.php&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:41--&gt;<br /> *A PHP file that loads the controller classː &lt;tt&gt;&lt;component_name&gt;.php&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:42--&gt;<br /> *A PHP file that represents the model itselfː &lt;tt&gt;models/&lt;component_name&gt;.php&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:43--&gt;<br /> *Another HTML file for background controlː &lt;tt&gt;models/index.html&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:44--&gt;<br /> *A PHP file containing the default viewː &lt;tt&gt;views/&lt;component_name&gt;/tmpl/default.php&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:45--&gt;<br /> *An XML file for adding a menu item typeː &lt;tt&gt;views/&lt;component_name&gt;/tmpl/default.xml&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:46--&gt;<br /> *Another HTML file for background controlː &lt;tt&gt;views/&lt;component_name&gt;/tmpl/index.html&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:47--&gt;<br /> *Another HTML file for background controlː &lt;tt&gt;views/&lt;component_name&gt;/index.html&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:48--&gt;<br /> *A PHP file for displaying the viewː &lt;tt&gt;views/&lt;component_name&gt;/view.html.php&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==JEXEC== &lt;!--T:49--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:50--&gt;<br /> The following line is commonly found at the start of Joomla! PHP files:&lt;/translate&gt;<br /> &lt;syntaxhighlight lang=&quot;php&quot;&gt;<br /> &lt;?php<br /> defined('_JEXEC') or die('Restricted Access');<br /> &lt;/syntaxhighlight&gt;<br /> &lt;translate&gt;&lt;!--T:51--&gt;<br /> This enables a secure entry point into the Joomla! platform. [[S:MyLanguage/JEXEC| JEXEC]] contains a detailed explanation.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Tutorials on Designing a MVC Component== &lt;!--T:52--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:53--&gt;<br /> To learn how to design your own MVC Component, please complete the tutorial for your Joomla! version.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:54--&gt;<br /> * [[S:MyLanguage/J1.5:Developing_a_MVC_Component/Introduction| Joomla! 1.5]]&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:55--&gt;<br /> * [[S:MyLanguage/J2.5:Developing_a_MVC_Component| Joomla! 2.5]]&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:56--&gt;<br /> * [[S:MyLanguage/J3.x:Developing_an_MVC_Component/Introduction| Joomla! 3.x]]<br /> * [[S:MyLanguage/J4.x:Developing_an_MVC_Component| Joomla! 4.x]]&lt;/translate&gt;<br /> <br /> &lt;noinclude&gt;<br /> [[Category:Tutorials{{#translation:}}]]<br /> [[Category:Explanations{{#translation:}}]]<br /> [[Category:Component Development{{#translation:}}]]<br /> [[Category:Beginner Development{{#translation:}}]]<br /> [[Category:Development Recommended Reading{{#translation:}}]]<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Absolute_Basics_of_How_a_Component_Functions&diff=924781 2022-06-22T09:15:32Z

<p>Wilsonge: Try fixing</p> <hr /> <div>&lt;noinclude&gt;&lt;languages /&gt;&lt;/noinclude&gt;<br /> &lt;translate&gt;&lt;!--T:1--&gt;<br /> This article is designed for Joomlaǃ beginners; it is designed to explain what a Joomlaǃ component is and how it functions. When a specific component example will benefit the tutorial, this article will refer to an example component named Hello Worldǃ.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==What is a Joomlaǃ Component== &lt;!--T:2--&gt;<br /> &lt;/translate&gt;<br /> {{Chunk:Component/&lt;translate&gt;&lt;!--T:58--&gt;<br /> en&lt;/translate&gt;}}<br /> &lt;translate&gt;&lt;!--T:5--&gt;<br /> In the Joomla! framework, components can be designed using a flat model (returns HTML code for the requested page) or Model-View-Controller (herein referred to as MVC) pattern.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Introduction to MVC== &lt;!--T:6--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:7--&gt;<br /> MVC is a software design pattern that can be used to organize code in such a way that the business logic and data presentation are separate. The premise behind this approach is that if the business logic is grouped into one section, then the interface and user interaction that surrounds the data can be revised and customized without having to reprogram the business logic. MVC was originally developed to map the traditional input, processing, output roles into a logical GUI architecture.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ===Model=== &lt;!--T:8--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:9--&gt;<br /> The model is the part of the component that encapsulates the application's data. It will often provide routines to manage and manipulate this data in a meaningful way in addition to routines that retrieve the data from the model. In general, the underlying data access technique should be encapsulated in the model. In this way, if an application is to be moved from a system that utilizes a flat file to store its information to a system that uses a database, the model is the only element that needs to be changed, not the view or the controller.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ===View=== &lt;!--T:10--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:11--&gt;<br /> The view is the part of the component that is used to render the data from the model in a manner that is suitable for interaction. For a web-based application, the view would generally be an HTML page that is returned to the user. The view pulls data from the model (which is passed to it from the controller) and feeds the data into a template which is populated and presented to the user. The view does not cause the data to be modified in any way, it only displays the data received from the model.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ===Controller=== &lt;!--T:12--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:13--&gt;<br /> The controller is responsible for responding to user actions. In the case of a web application, a user action is generally a page request. The controller will determine what request is being made by the user and respond appropriately by triggering the model to manipulate the data appropriately and passing the model into the view. The controller does not display the data in the model, it only triggers methods in the model which modify the data, and then pass the model into the view which displays the data.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> == Joomla! Component Framework Explained == &lt;!--T:14--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;<br /> === Model === &lt;!--T:15--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:16--&gt;<br /> In the Joomla framework, models are responsible for managing the data. The first function that has to be written for a model is a get function. It returns data to the caller. For this example, the caller will be the HelloWorldViewHelloWorld view. By default, the model named HelloWorldModelHelloWorld residing in site/models/helloworld.php is the main model associated to this view.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:17--&gt;<br /> So let's have a quick look at the naming conventions with an example, since the naming convention are the actual magic that make everything work:&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:18--&gt;<br /> The class ''HelloWorldView'''HelloWorld''''' resides in ''site/views/'''helloworld'''/view.html.php'' and will make use of the class ''HelloWorldModel'''HelloWorld''''' in the file ''site/models/'''helloworld'''.php''&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:19--&gt;<br /> Let's just assume we want to use an imaginary view ''fluffy'', you would have to have:&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:20--&gt;<br /> The class ''HelloWorldView'''Fluffy''''' which resides in ''site/views/'''fluffy'''/view.html.php''. The view will make use of ''HelloWorldModel'''Fluffy''''' in the file ''site/models/'''fluffy'''.php''. Note: the actual screen of the view: ''site/views/'''fluffy'''/tmpl/default.php'' is required as well to make this example work.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:21--&gt;<br /> Breaking any of these bold conventions will lead to errors or a blank page.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Accessing a Joomlaǃ Component== &lt;!--T:22--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:23--&gt;<br /> First we need to access the Joomla! platform, which is always accessed through a single point of entry. Using your preferred web browser, navigate to the following URL:&lt;/translate&gt;<br /> {| border=1<br /> | 1<br /> | &lt;translate&gt;&lt;!--T:24--&gt;<br /> user access&lt;/translate&gt;<br /> | &lt;translate&gt;&lt;!--T:25--&gt;<br /> &lt;tt&gt;&lt;yoursite&gt;/joomla/index.php&lt;/tt&gt;&lt;/translate&gt;<br /> |-<br /> | 2<br /> | &lt;translate&gt;&lt;!--T:26--&gt;<br /> administrator access&lt;/translate&gt; <br /> | &lt;translate&gt;&lt;!--T:27--&gt;<br /> &lt;tt&gt;&lt;yoursite&gt;/joomla/administrator/index.php&lt;/tt&gt;&lt;/translate&gt;<br /> |}<br /> &lt;translate&gt;&lt;!--T:28--&gt;<br /> Hello World! example:&lt;/translate&gt; &lt;tt&gt;localhost/joomla/index.php&lt;/tt&gt;<br /> &lt;translate&gt;&lt;!--T:29--&gt;<br /> You can use the URL of the component, or a [[#Menu| Menu]] in order to navigate to the component. In this article we will discuss using the URL.&lt;/translate&gt;<br /> {| border=1<br /> | 1<br /> | &lt;translate&gt;&lt;!--T:30--&gt;<br /> user access&lt;/translate&gt;<br /> | &lt;translate&gt;&lt;!--T:31--&gt;<br /> &lt;tt&gt;&lt;yoursite&gt;/joomla/index.php?option=com_&lt;component_name&gt;&lt;/tt&gt;&lt;/translate&gt;<br /> |-<br /> | 2<br /> | &lt;translate&gt;&lt;!--T:32--&gt;<br /> administrator access&lt;/translate&gt; <br /> | &lt;translate&gt;&lt;!--T:33--&gt;<br /> &lt;tt&gt;&lt;yoursite&gt;/joomla/administrator/index.php?option=com_&lt;component_name&gt;&lt;/tt&gt;&lt;/translate&gt;<br /> |}<br /> &lt;translate&gt;&lt;!--T:34--&gt;<br /> Hello World! example:&lt;/translate&gt; &lt;tt&gt;localhost/joomla/index.php?option=com_helloworld&lt;/tt&gt;<br /> &lt;translate&gt;<br /> ==MVC Basic Directory Structure== &lt;!--T:35--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:36--&gt;<br /> Components are stored in a directory within your Joomla! installation, specifically at:<br /> *&lt;tt&gt;htdocs/&lt;path_to_joomla&gt;/components/com_&lt;component_name&gt;/&lt;/tt&gt; .&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:37--&gt;<br /> The Hello World! component would be stored in &lt;tt&gt; htdocs/&lt;path_to_joomla&gt;/components/com_helloworld/&lt;/tt&gt;.&lt;/translate&gt; <br /> &lt;translate&gt;&lt;!--T:38--&gt;<br /> A basic component will contain the following files within its directoryː&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:39--&gt;<br /> *An HTML file that is just a security file with a background colorː &lt;tt&gt;index.html&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:40--&gt;<br /> *A PHP file that represents the controller itselfː &lt;tt&gt;controller.php&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:41--&gt;<br /> *A PHP file that loads the controller classː &lt;tt&gt;&lt;component_name&gt;.php&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:42--&gt;<br /> *A PHP file that represents the model itselfː &lt;tt&gt;models/&lt;component_name&gt;.php&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:43--&gt;<br /> *Another HTML file for background controlː &lt;tt&gt;models/index.html&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:44--&gt;<br /> *A PHP file containing the default viewː &lt;tt&gt;views/&lt;component_name&gt;/tmpl/default.php&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:45--&gt;<br /> *An XML file for adding a menu item typeː &lt;tt&gt;views/&lt;component_name&gt;/tmpl/default.xml&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:46--&gt;<br /> *Another HTML file for background controlː &lt;tt&gt;views/&lt;component_name&gt;/tmpl/index.html&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:47--&gt;<br /> *Another HTML file for background controlː &lt;tt&gt;views/&lt;component_name&gt;/index.html&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:48--&gt;<br /> *A PHP file for displaying the viewː &lt;tt&gt;views/&lt;component_name&gt;/view.html.php&lt;/tt&gt;&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==JEXEC== &lt;!--T:49--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:50--&gt;<br /> The following line is commonly found at the start of Joomla! PHP files:&lt;/translate&gt;<br /> &lt; syntaxhighlight lang=&quot;php&quot;&gt;<br /> &lt;?php<br /> defined('_JEXEC') or die('Restricted Access');<br /> &lt;/syntaxhighlight&gt;<br /> &lt;translate&gt;&lt;!--T:51--&gt;<br /> This enables a secure entry point into the Joomla! platform. [[S:MyLanguage/JEXEC| JEXEC]] contains a detailed explanation.&lt;/translate&gt;<br /> &lt;translate&gt;<br /> ==Tutorials on Designing a MVC Component== &lt;!--T:52--&gt;<br /> &lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:53--&gt;<br /> To learn how to design your own MVC Component, please complete the tutorial for your Joomla! version.&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:54--&gt;<br /> * [[S:MyLanguage/J1.5:Developing_a_MVC_Component/Introduction| Joomla! 1.5]]&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:55--&gt;<br /> * [[S:MyLanguage/J2.5:Developing_a_MVC_Component| Joomla! 2.5]]&lt;/translate&gt;<br /> &lt;translate&gt;&lt;!--T:56--&gt;<br /> * [[S:MyLanguage/J3.x:Developing_an_MVC_Component/Introduction| Joomla! 3.x]]<br /> * [[S:MyLanguage/J4.x:Developing_an_MVC_Component| Joomla! 4.x]]&lt;/translate&gt;<br /> <br /> &lt;noinclude&gt;<br /> [[Category:Tutorials{{#translation:}}]]<br /> [[Category:Explanations{{#translation:}}]]<br /> [[Category:Component Development{{#translation:}}]]<br /> [[Category:Beginner Development{{#translation:}}]]<br /> [[Category:Development Recommended Reading{{#translation:}}]]<br /> &lt;/noinclude&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=MediaWiki:Gadget-HotCat.js&diff=888298 2022-03-06T01:10:07Z

<p>Wilsonge: New version for new wiki version</p> <hr /> <div>/**<br /> HotCat V2.43<br /> <br /> Ajax-based simple Category manager. Allows adding/removing/changing categories on a page view.<br /> Supports multiple category changes, as well as redirect and disambiguation resolution. Also<br /> plugs into the upload form. Search engines to use for the suggestion list are configurable, and<br /> can be selected interactively.<br /> <br /> Documentation: https://commons.wikimedia.org/wiki/Help:Gadget-HotCat<br /> List of main authors: https://commons.wikimedia.org/wiki/Help:Gadget-HotCat/Version_history<br /> <br /> License: Quadruple licensed GFDL, GPL, LGPL and Creative Commons Attribution 3.0 (CC-BY-3.0)<br /> <br /> Choose whichever license of these you like best :-)<br /> <br /> This code should run on any MediaWiki installation &gt;= MW 1.27.<br /> <br /> For use with older versions of MediaWiki, use the archived versions below:<br /> <br /> &lt;=1.26: https://commons.wikimedia.org/w/index.php?title=MediaWiki:Gadget-HotCat.js&amp;oldid=211134664<br /> */<br /> // &lt;nowiki&gt;<br /> /* eslint-disable vars-on-top, one-var, camelcase, no-alert, curly */<br /> /* global jQuery, mediaWiki, UFUI, JSconfig, UploadForm */<br /> /* jslint strict:false, nonew:false, bitwise:true */<br /> ( function ( $, mw ) {<br /> // Don't use mw.config.get() as that takes a copy of the config, and so doesn't<br /> // account for values changing, e.g. wgCurRevisionId after a VE edit<br /> var<br /> conf = $.extend( {}, mw.config.values, {<br /> // when running on mobile domain - do not use wgServer.<br /> wgServer: window.location.host.indexOf('.m.') &gt; -1 ?<br /> '//' + window.location.host : mw.config.get( 'wgServer' )<br /> } );<br /> <br /> // Guard against double inclusions (in old IE/Opera element ids become window properties)<br /> if ( ( window.HotCat &amp;&amp; !window.HotCat.nodeName ) ||<br /> conf.wgAction === 'edit' ) // Not on edit mode<br /> return;<br /> <br /> // Configuration stuff.<br /> var HC = window.HotCat = {<br /> // Localize these messages to the main language of your wiki.<br /> messages: {<br /> cat_removed: 'removed [[Category:$1]]',<br /> template_removed: 'removed {{[[Category:$1]]}}',<br /> cat_added: 'added [[Category:$1]]',<br /> cat_keychange: 'new key for [[Category:$1]]: &quot;$2&quot;', // $2 is the new key<br /> cat_notFound: 'Category &quot;$1&quot; not found',<br /> cat_exists: 'Category &quot;$1&quot; already exists; not added.',<br /> cat_resolved: ' (redirect [[Category:$1]] resolved)',<br /> uncat_removed: 'removed {{uncategorized}}',<br /> separator: '; ',<br /> // Some text to prefix to the edit summary.<br /> prefix: '',<br /> // Some text to append to the edit summary. Named 'using' for historical reasons. If you prefer<br /> // to have a marker at the front, use prefix and set this to the empty string.<br /> using: ' using [[Help:Gadget-HotCat|HotCat]]',<br /> // $1 is replaced by a number. If your language has several plural forms (c.f. [[:en:Dual (grammatical form)]]),<br /> // you can set this to an array of strings suitable for passing to mw.language.configPlural().<br /> // If that function doesn't exist, HotCat will simply fall back to using the last<br /> // entry in the array.<br /> multi_change: '$1 categories',<br /> // Button text. Localize to wgContentLanguage here; localize to wgUserLanguage in a subpage,<br /> // see localization hook below.<br /> commit: 'Save',<br /> // Button text. Localize to wgContentLanguage here; localize to wgUserLanguage in a subpage,<br /> // see localization hook below.<br /> ok: 'OK',<br /> // Button text. Localize to wgContentLanguage here; localize to wgUserLanguage in a subpage,<br /> // see localization hook below.<br /> cancel: 'Cancel',<br /> // Localize to wgContentLanguage here; localize to wgUserLanguage in a subpage,<br /> // see localization hook below.<br /> multi_error: 'Could not retrieve the page text from the server. Therefore, your category changes ' +<br /> 'cannot be saved. We apologize for the inconvenience.',<br /> // Defaults to '[[' + category_canonical + ':$1]]'. Can be overridden if in the short edit summaries<br /> // not the standard category name should be used but, say, a shorter namespace alias. $1 is replaced<br /> // by a category name.<br /> short_catchange: null<br /> },<br /> // Plural of category_canonical.<br /> categories: 'Categories',<br /> // Any category in this category is deemed a disambiguation category; i.e., a category that should not contain<br /> // any items, but that contains links to other categories where stuff should be categorized. If you don't have<br /> // that concept on your wiki, set it to null. Use blanks, not underscores.<br /> disambig_category: 'Disambiguation',<br /> // Any category in this category is deemed a (soft) redirect to some other category defined by a link<br /> // to another non-blacklisted category. If your wiki doesn't have soft category redirects, set this to null.<br /> // If a soft-redirected category contains more than one link to another non-blacklisted category, it's considered<br /> // a disambiguation category instead.<br /> redir_category: 'Category redirects',<br /> // The little modification links displayed after category names. U+2212 is a minus sign; U+2193 and U+2191 are<br /> // downward and upward pointing arrows. Do not use ↓ and ↑ in the code!<br /> links: {<br /> change: '(±)',<br /> remove: '(\u2212)',<br /> add: '(+)',<br /> restore: '(×)',<br /> undo: '(×)',<br /> down: '(\u2193)',<br /> up: '(\u2191)'<br /> },<br /> changeTag: conf.wgUserName ? 'HotCat' : '', // if tag is missing, edit is rejected<br /> // The tooltips for the above links<br /> tooltips: {<br /> change: 'Modify',<br /> remove: 'Remove',<br /> add: 'Add a new category',<br /> restore: 'Undo changes',<br /> undo: 'Undo changes',<br /> down: 'Open for modifying and display subcategories',<br /> up: 'Open for modifying and display parent categories'<br /> },<br /> // The HTML content of the &quot;enter multi-mode&quot; link at the front.<br /> addmulti: '&lt;span&gt;+&lt;sup&gt;+&lt;/sup&gt;&lt;/span&gt;',<br /> // Tooltip for the &quot;enter multi-mode&quot; link<br /> multi_tooltip: 'Modify several categories',<br /> // Return true to disable HotCat.<br /> disable: function () {<br /> var ns = conf.wgNamespaceNumber;<br /> var nsIds = conf.wgNamespaceIds;<br /> return (<br /> ns &lt; 0 || // Special pages; Special:Upload is handled differently<br /> ns === 10 || // Templates<br /> ns === 828 || // Module (Lua)<br /> ns === 8 || // MediaWiki<br /> ns === 6 &amp;&amp; !conf.wgArticleId || // Non-existing file pages<br /> ns === 2 &amp;&amp; /\.(js|css)$/.test( conf.wgTitle ) || // User scripts<br /> nsIds &amp;&amp;<br /> ( ns === nsIds.creator ||<br /> ns === nsIds.timedtext ||<br /> ns === nsIds.institution ) );<br /> },<br /> // A regexp matching a templates used to mark uncategorized pages, if your wiki does have that.<br /> // If not, set it to null.<br /> uncat_regexp: /\{\{\s*[Uu]ncategorized\s*[^}]*\}\}\s*(&lt;!--.*?--&gt;\s*)?/g,<br /> // The images used for the little indication icon. Should not need changing.<br /> existsYes: '//upload.wikimedia.org/wikipedia/commons/thumb/b/be/P_yes.svg/20px-P_yes.svg.png',<br /> existsNo: '//upload.wikimedia.org/wikipedia/commons/thumb/4/42/P_no.svg/20px-P_no.svg.png',<br /> // a list of categories which can be removed by removing a template<br /> // key: the category without namespace<br /> // value: A regexp matching the template name, again without namespace<br /> // If you don't have this at your wiki, or don't want this, set it to an empty object {}.<br /> template_categories: {},<br /> // Names for the search engines<br /> engine_names: {<br /> searchindex: 'Search index',<br /> pagelist: 'Page list',<br /> combined: 'Combined search',<br /> subcat: 'Subcategories',<br /> parentcat: 'Parent categories'<br /> },<br /> <br /> // Override the decision of whether HotCat should help users by automatically<br /> // capitalising the title in the user input text if the wiki has case-sensitive page names.<br /> // Basically, this will make an API query to check the MediaWiki configuration and HotCat then sets<br /> // this to true for most wikis, and to false on Wiktionary.<br /> // <br /> // You can set this directly if there is a problem with it. For example, Georgian Wikipedia (kawiki),<br /> // is known to have different capitalisation logic between MediaWiki PHP and JavaScript. As such, automatic<br /> // case changes in JavaScript by HotCat would be wrong.<br /> capitalizePageNames: null,<br /> // If upload_disabled is true, HotCat will not be used on the Upload form.<br /> upload_disabled: false,<br /> // Single regular expression matching blacklisted categories that cannot be changed or<br /> // added using HotCat. For instance /\bstubs?$/ (any category ending with the word &quot;stub&quot;<br /> // or &quot;stubs&quot;), or /(\bstubs?$)|\bmaintenance\b/ (stub categories and any category with the<br /> // word &quot;maintenance&quot; in its title.<br /> blacklist: null,<br /> <br /> // Stuff changeable by users:<br /> // Background for changed categories in multi-edit mode. Default is a very light salmon pink.<br /> bg_changed: '#FCA',<br /> // If true, HotCat will never automatically submit changes. HotCat will only open an edit page with<br /> // the changes; users must always save explicitly.<br /> no_autocommit: false,<br /> // If true, the &quot;category deletion&quot; link &quot;(-)&quot; will never save automatically but always show an<br /> // edit page where the user has to save the edit manually. Is false by default because that's the<br /> // traditional behavior. This setting overrides no_autocommit for &quot;(-)&quot; links.<br /> del_needs_diff: false,<br /> // Time, in milliseconds, that HotCat waits after a keystroke before making a request to the<br /> // server to get suggestions.<br /> suggest_delay: 100,<br /> // Default width, in characters, of the text input field.<br /> editbox_width: 40,<br /> // One of the engine_names above, to be used as the default suggestion engine.<br /> suggestions: 'combined',<br /> // If true, always use the default engine, and never display a selector.<br /> fixed_search: false,<br /> // If false, do not display the &quot;up&quot; and &quot;down&quot; links<br /> use_up_down: true,<br /> // Default list size<br /> listSize: 10,<br /> // If true, single category changes are marked as minor edits. If false, they're not.<br /> single_minor: true,<br /> // If true, never add a page to the user's watchlist. If false, pages get added to the watchlist if<br /> // the user has the &quot;Add pages I edit to my watchlist&quot; or the &quot;Add pages I create to my watchlist&quot;<br /> // options in his or her preferences set.<br /> dont_add_to_watchlist: false,<br /> shortcuts: null,<br /> addShortcuts: function ( map ) {<br /> if ( !map ) return;<br /> window.HotCat.shortcuts = window.HotCat.shortcuts || {};<br /> for ( var k in map ) {<br /> if ( !map.hasOwnProperty( k ) || typeof k !== 'string' ) continue;<br /> <br /> var v = map[ k ];<br /> if ( typeof v !== 'string' ) continue;<br /> <br /> k = k.replace( /^\s+|\s+$/g, '' );<br /> v = v.replace( /^\s+|\s+$/g, '' );<br /> if ( !k.length || !v.length ) continue;<br /> <br /> window.HotCat.shortcuts[ k ] = v;<br /> }<br /> }<br /> };<br /> <br /> // More backwards compatibility. We have a few places where we test for the browser: once for<br /> // Safari &lt; 3.0, and twice for WebKit (Chrome or Safari, any versions)<br /> var ua = navigator.userAgent.toLowerCase();<br /> var is_webkit = /applewebkit\/\d+/.test( ua ) &amp;&amp; ua.indexOf( 'spoofer' ) &lt; 0;<br /> var cat_prefix = null;<br /> var noSuggestions = false;<br /> <br /> function LoadTrigger( needed ) {<br /> // Define methods in a closure so that self reference is available,<br /> // also allows method calls to be detached.<br /> var self = this;<br /> self.queue = [];<br /> self.needed = needed;<br /> self.register = function ( callback ) {<br /> if ( self.needed &lt;= 0 ) callback(); // Execute directly<br /> else self.queue.push( callback );<br /> };<br /> self.loaded = function () {<br /> self.needed--;<br /> if ( self.needed === 0 ) {<br /> // Run queued callbacks once<br /> for ( var i = 0; i &lt; self.queue.length; i++ ) self.queue[ i ]();<br /> self.queue = [];<br /> }<br /> };<br /> }<br /> <br /> // Used to delay running the HotCat setup until /local_defaults and localizations have been loaded.<br /> var loadTrigger = new LoadTrigger( 2 );<br /> <br /> function load( uri, callback ) {<br /> var s = document.createElement( 'script' );<br /> s.src = uri;<br /> var called = false;<br /> <br /> s.onload = s.onerror = function () {<br /> if ( !called &amp;&amp; callback ) {<br /> called = true;<br /> callback();<br /> }<br /> if ( s.parentNode ) {<br /> s.parentNode.removeChild( s );<br /> }<br /> };<br /> document.head.appendChild( s );<br /> }<br /> <br /> function loadJS( page, callback ) {<br /> load( conf.wgServer + conf.wgScript + '?title=' + encodeURIComponent( page ) + '&amp;action=raw&amp;ctype=text/javascript', callback );<br /> }<br /> <br /> function loadURI( href, callback ) {<br /> var url = href;<br /> if ( url.substring( 0, 2 ) === '//' ) url = window.location.protocol + url; else if ( url.substring( 0, 1 ) === '/' ) url = conf.wgServer + url;<br /> <br /> load( url, callback );<br /> }<br /> <br /> // Load local configurations, overriding the pre-set default values in the HotCat object above. This is always loaded<br /> // from the wiki where this script is executing, even if this script itself is hotlinked from Commons. This can<br /> // be used to change the default settings, or to provide localized interface texts for edit summaries and so on.<br /> loadJS( 'MediaWiki:Gadget-HotCat.js/local_defaults', loadTrigger.loaded );<br /> <br /> // Load localized UI texts. These are the texts that HotCat displays on the page itself. Texts shown in edit summaries<br /> // should be localized in /local_defaults above.<br /> if ( conf.wgUserLanguage !== 'en' ) {<br /> // Lupo: somebody thought it would be a good idea to add this. So the default is true, and you have to set it to false<br /> // explicitly if you're not on Commons and don't want that.<br /> if ( window.hotcat_translations_from_commons === undefined ) window.hotcat_translations_from_commons = true;<br /> <br /> // Localization hook to localize HotCat messages, tooltips, and engine names for wgUserLanguage.<br /> if ( window.hotcat_translations_from_commons &amp;&amp; conf.wgServer.indexOf( '//commons' ) &lt; 0 ) {<br /> loadURI( '//commons.wikimedia.org/w/index.php?title=' +<br /> 'MediaWiki:Gadget-HotCat.js/' + conf.wgUserLanguage +<br /> '&amp;action=raw&amp;ctype=text/javascript', loadTrigger.loaded );<br /> } else {<br /> // Load translations locally<br /> loadJS( 'MediaWiki:Gadget-HotCat.js/' + conf.wgUserLanguage, loadTrigger.loaded );<br /> }<br /> } else {<br /> loadTrigger.loaded();<br /> }<br /> <br /> // No further changes should be necessary here.<br /> <br /> // The following regular expression strings are used when searching for categories in wikitext.<br /> var wikiTextBlank = '[\\t _\\xA0\\u1680\\u180E\\u2000-\\u200A\\u2028\\u2029\\u202F\\u205F\\u3000]+';<br /> var wikiTextBlankRE = new RegExp( wikiTextBlank, 'g' );<br /> // Regexp for handling blanks inside a category title or namespace name.<br /> // See http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/includes/Title.php?revision=104051&amp;view=markup#l2722<br /> // See also http://www.fileformat.info/info/unicode/category/Zs/list.htm<br /> // MediaWiki collapses several contiguous blanks inside a page title to one single blank. It also replace a<br /> // number of special whitespace characters by simple blanks. And finally, blanks are treated as underscores.<br /> // Therefore, when looking for page titles in wikitext, we must handle all these cases.<br /> // Note: we _do_ include the horizontal tab in the above list, even though the MediaWiki software for some reason<br /> // appears to not handle it. The zero-width space \u200B is _not_ handled as a space inside titles by MW.<br /> var wikiTextBlankOrBidi = '[\\t _\\xA0\\u1680\\u180E\\u2000-\\u200B\\u200E\\u200F\\u2028-\\u202F\\u205F\\u3000]*';<br /> // Whitespace regexp for handling whitespace between link components. Including the horizontal tab, but not \n\r\f\v:<br /> // a link must be on one single line.<br /> // MediaWiki also removes Unicode bidi override characters in page titles (and namespace names) completely.<br /> // This is *not* handled, as it would require us to allow any of [\u200E\u200F\u202A-\u202E] between any two<br /> // characters inside a category link. It _could_ be done though... We _do_ handle strange spaces, including the<br /> // zero-width space \u200B, and bidi overrides between the components of a category link (adjacent to the colon,<br /> // or adjacent to and inside of &quot;[[&quot; and &quot;]]&quot;).<br /> <br /> // First auto-localize the regexps for the category and the template namespaces.<br /> var formattedNamespaces = conf.wgFormattedNamespaces;<br /> var namespaceIds = conf.wgNamespaceIds;<br /> function autoLocalize( namespaceNumber, fallback ) {<br /> function createRegexpStr( name ) {<br /> if ( !name || !name.length ) return '';<br /> <br /> var regex_name = '';<br /> for ( var i = 0; i &lt; name.length; i++ ) {<br /> var initial = name.charAt( i ),<br /> ll = initial.toLowerCase(),<br /> ul = initial.toUpperCase();<br /> if ( ll === ul ) regex_name += initial; else regex_name += '[' + ll + ul + ']';<br /> }<br /> return regex_name<br /> .replace( /([\\^$.?*+()])/g, '\\$1' )<br /> .replace( wikiTextBlankRE, wikiTextBlank );<br /> }<br /> <br /> fallback = fallback.toLowerCase();<br /> var canonical = formattedNamespaces[ String( namespaceNumber ) ].toLowerCase();<br /> var regexp = createRegexpStr( canonical );<br /> if ( fallback &amp;&amp; canonical !== fallback ) regexp += '|' + createRegexpStr( fallback );<br /> <br /> if ( namespaceIds ) {<br /> for ( var cat_name in namespaceIds ) {<br /> if (<br /> typeof cat_name === 'string' &amp;&amp;<br /> cat_name.toLowerCase() !== canonical &amp;&amp;<br /> cat_name.toLowerCase() !== fallback &amp;&amp;<br /> namespaceIds[ cat_name ] === namespaceNumber<br /> ) {<br /> regexp += '|' + createRegexpStr( cat_name );<br /> }<br /> }<br /> }<br /> return regexp;<br /> }<br /> <br /> HC.category_canonical = formattedNamespaces[ '14' ];<br /> HC.category_regexp = autoLocalize( 14, 'category' );<br /> if ( formattedNamespaces[ '10' ] ) HC.template_regexp = autoLocalize( 10, 'template' );<br /> <br /> // Utility functions. Yes, this duplicates some functionality that also exists in other places, but<br /> // to keep this whole stuff in a single file not depending on any other on-wiki JavaScripts, we re-do<br /> // these few operations here.<br /> function make( arg, literal ) {<br /> if ( !arg ) return null;<br /> <br /> return literal ? document.createTextNode( arg ) : document.createElement( arg );<br /> }<br /> function param( name, uri ) {<br /> uri = uri || document.location.href;<br /> var re = new RegExp( '[&amp;?]' + name + '=([^&amp;#]*)' );<br /> var m = re.exec( uri );<br /> if ( m &amp;&amp; m.length &gt; 1 ) return decodeURIComponent( m[ 1 ] );<br /> return null;<br /> }<br /> function title( href ) {<br /> if ( !href ) return null;<br /> <br /> var script = conf.wgScript + '?';<br /> if ( href.indexOf( script ) === 0 || href.indexOf( conf.wgServer + script ) === 0 || conf.wgServer.substring( 0, 2 ) === '//' &amp;&amp; href.indexOf( document.location.protocol + conf.wgServer + script ) === 0 ) {<br /> // href=&quot;/w/index.php?title=...&quot;<br /> return param( 'title', href );<br /> } else {<br /> // href=&quot;/wiki/...&quot;<br /> var prefix = conf.wgArticlePath.replace( '$1', '' );<br /> if ( href.indexOf( prefix ) ) prefix = conf.wgServer + prefix; // Fully expanded URL?<br /> <br /> if ( href.indexOf( prefix ) &amp;&amp; prefix.substring( 0, 2 ) === '//' ) prefix = document.location.protocol + prefix; // Protocol-relative wgServer?<br /> <br /> if ( href.indexOf( prefix ) === 0 ) return decodeURIComponent( href.substring( prefix.length ) );<br /> }<br /> return null;<br /> }<br /> function hasClass( elem, name ) {<br /> return ( ' ' + elem.className + ' ' ).indexOf( ' ' + name + ' ' ) &gt;= 0;<br /> }<br /> function capitalize( str ) {<br /> if ( !str || !str.length ) return str;<br /> <br /> return str.substr( 0, 1 ).toUpperCase() + str.substr( 1 );<br /> }<br /> function wikiPagePath( pageName ) {<br /> // Note: do not simply use encodeURI, it doesn't encode '&amp;', which might break if wgArticlePath actually has the $1 in<br /> // a query parameter.<br /> return conf.wgArticlePath.replace( '$1', encodeURIComponent( pageName ).replace( /%3A/g, ':' ).replace( /%2F/g, '/' ) );<br /> }<br /> function escapeRE( str ) {<br /> return str.replace( /([\\^$.?*+()[\]])/g, '\\$1' );<br /> }<br /> <br /> function substituteFactory( options ) {<br /> options = options || {};<br /> var lead = options.indicator || '$';<br /> var indicator = escapeRE( lead );<br /> var lbrace = escapeRE( options.lbrace || '{' );<br /> var rbrace = escapeRE( options.rbrace || '}' );<br /> var re;<br /> <br /> re = new RegExp(<br /> // $$<br /> '(?:' + indicator + '(' + indicator + '))|' +<br /> // $0, $1<br /> '(?:' + indicator + '(\\d+))|' +<br /> // ${key}<br /> '(?:' + indicator + '(?:' + lbrace + '([^' + lbrace + rbrace + ']+)' + rbrace + '))|' +<br /> // $key (only if first char after $ is not $, digit, or { )<br /> '(?:' + indicator + '(?!(?:[' + indicator + lbrace + ']|\\d))(\\S+?)\\b)',<br /> 'g'<br /> );<br /> // Replace $1, $2, or ${key1}, ${key2}, or $key1, $key2 by values from map. $$ is replaced by a single $.<br /> return function ( str, map ) {<br /> if ( !map ) return str;<br /> <br /> return str.replace( re, function ( match, prefix, idx, key, alpha ) {<br /> if ( prefix === lead ) return lead;<br /> <br /> var k = alpha || key || idx;<br /> var replacement = typeof map[ k ] === 'function' ? map[ k ]( match, k ) : map[ k ];<br /> return typeof replacement === 'string' ? replacement : ( replacement || match );<br /> } );<br /> };<br /> }<br /> <br /> var substitute = substituteFactory();<br /> var replaceShortcuts = ( function () {<br /> var replaceHash = substituteFactory( {<br /> indicator: '#',<br /> lbrace: '[',<br /> rbrace: ']'<br /> } );<br /> return function ( str, map ) {<br /> var s = replaceHash( str, map );<br /> return HC.capitalizePageNames ? capitalize( s ) : s;<br /> };<br /> }() );<br /> <br /> // Text modification<br /> <br /> var findCatsRE =<br /> new RegExp( '\\[\\[' + wikiTextBlankOrBidi + '(?:' + HC.category_regexp + ')' + wikiTextBlankOrBidi + ':[^\\]]+\\]\\]', 'g' );<br /> <br /> function replaceByBlanks( match ) {<br /> return match.replace( /(\s|\S)/g, ' ' ); // /./ doesn't match linebreaks. /(\s|\S)/ does.<br /> }<br /> <br /> function find_category( wikitext, category, once ) {<br /> var cat_regex = null;<br /> if ( HC.template_categories[ category ] ) {<br /> cat_regex = new RegExp(<br /> '\\{\\{' + wikiTextBlankOrBidi + '(' + HC.template_regexp + '(?=' + wikiTextBlankOrBidi + ':))?' + wikiTextBlankOrBidi +<br /> '(?:' + HC.template_categories[ category ] + ')' +<br /> wikiTextBlankOrBidi + '(\\|.*?)?\\}\\}',<br /> 'g'<br /> );<br /> } else {<br /> var cat_name = escapeRE( category );<br /> var initial = cat_name.substr( 0, 1 );<br /> cat_regex = new RegExp(<br /> '\\[\\[' + wikiTextBlankOrBidi + '(' + HC.category_regexp + ')' + wikiTextBlankOrBidi + ':' + wikiTextBlankOrBidi +<br /> ( initial === '\\' || !HC.capitalizePageNames ?<br /> initial :<br /> '[' + initial.toUpperCase() + initial.toLowerCase() + ']' ) +<br /> cat_name.substring( 1 ).replace( wikiTextBlankRE, wikiTextBlank ) +<br /> wikiTextBlankOrBidi + '(\\|.*?)?\\]\\]',<br /> 'g'<br /> );<br /> }<br /> if ( once ) return cat_regex.exec( wikitext );<br /> <br /> var copiedtext = wikitext<br /> .replace( /&lt;!--(\s|\S)*?--&gt;/g, replaceByBlanks )<br /> .replace( /&lt;nowiki&gt;(\s|\S)*?&lt;\/nowiki&gt;/g, replaceByBlanks );<br /> var result = [];<br /> var curr_match = null;<br /> while ( ( curr_match = cat_regex.exec( copiedtext ) ) !== null ) {<br /> result.push( {<br /> match: curr_match<br /> } );<br /> }<br /> result.re = cat_regex;<br /> return result; // An array containing all matches, with positions, in result[ i ].match<br /> }<br /> <br /> var interlanguageRE = null;<br /> <br /> function change_category( wikitext, toRemove, toAdd, key, is_hidden ) {<br /> <br /> function find_insertionpoint( wikitext ) {<br /> var copiedtext = wikitext<br /> .replace( /&lt;!--(\s|\S)*?--&gt;/g, replaceByBlanks )<br /> .replace( /&lt;nowiki&gt;(\s|\S)*?&lt;\/nowiki&gt;/g, replaceByBlanks );<br /> // Search in copiedtext to avoid that we insert inside an HTML comment or a nowiki &quot;element&quot;.<br /> var index = -1;<br /> findCatsRE.lastIndex = 0;<br /> while ( findCatsRE.exec( copiedtext ) !== null ) index = findCatsRE.lastIndex;<br /> <br /> if ( index &lt; 0 ) {<br /> // Find the index of the first interlanguage link...<br /> var match = null;<br /> if ( !interlanguageRE ) {<br /> // Approximation without API: interlanguage links start with 2 to 3 lower case letters, optionally followed by<br /> // a sequence of groups consisting of a dash followed by one or more lower case letters. Exceptions are &quot;simple&quot;<br /> // and &quot;tokipona&quot;.<br /> match = /((^|\n\r?)(\[\[\s*(([a-z]{2,3}(-[a-z]+)*)|simple|tokipona)\s*:[^\]]+\]\]\s*))+$/.exec( copiedtext );<br /> } else {<br /> match = interlanguageRE.exec( copiedtext );<br /> }<br /> if ( match ) index = match.index;<br /> <br /> return {<br /> idx: index,<br /> onCat: false<br /> };<br /> }<br /> return {<br /> idx: index,<br /> onCat: index &gt;= 0<br /> };<br /> }<br /> <br /> var summary = [],<br /> nameSpace = HC.category_canonical,<br /> cat_point = -1, // Position of removed category;<br /> keyChange = ( toRemove &amp;&amp; toAdd &amp;&amp; toRemove === toAdd &amp;&amp; toAdd.length ),<br /> matches;<br /> if ( key ) key = '|' + key;<br /> // Remove<br /> if ( toRemove &amp;&amp; toRemove.length ) {<br /> matches = find_category( wikitext, toRemove );<br /> if ( !matches || !matches.length ) {<br /> return {<br /> text: wikitext,<br /> summary: summary,<br /> error: HC.messages.cat_notFound.replace( /\$1/g, toRemove )<br /> };<br /> } else {<br /> var before = wikitext.substring( 0, matches[ 0 ].match.index ),<br /> after = wikitext.substring( matches[ 0 ].match.index + matches[ 0 ].match[ 0 ].length );<br /> if ( matches.length &gt; 1 ) {<br /> // Remove all occurrences in after<br /> matches.re.lastIndex = 0;<br /> after = after.replace( matches.re, '' );<br /> }<br /> if ( toAdd ) {<br /> // nameSpace = matches[ 0 ].match[ 1 ] || nameSpace; Canonical namespace should be always preferred<br /> if ( key === null ) key = matches[ 0 ].match[ 2 ];<br /> // Remember the category key, if any.<br /> }<br /> // Remove whitespace (properly): strip whitespace, but only up to the next line feed.<br /> // If we then have two linefeeds in a row, remove one. Otherwise, if we have two non-<br /> // whitespace characters, insert a blank.<br /> var i = before.length - 1;<br /> while ( i &gt;= 0 &amp;&amp; before.charAt( i ) !== '\n' &amp;&amp; before.substr( i, 1 ).search( /\s/ ) &gt;= 0 ) i--;<br /> <br /> var j = 0;<br /> while ( j &lt; after.length &amp;&amp; after.charAt( j ) !== '\n' &amp;&amp; after.substr( j, 1 ).search( /\s/ ) &gt;= 0 ) j++;<br /> <br /> if ( i &gt;= 0 &amp;&amp; before.charAt( i ) === '\n' &amp;&amp; ( !after.length || j &lt; after.length &amp;&amp; after.charAt( j ) === '\n' ) ) i--;<br /> <br /> if ( i &gt;= 0 ) before = before.substring( 0, i + 1 ); else before = '';<br /> <br /> if ( j &lt; after.length ) after = after.substring( j ); else after = '';<br /> <br /> if (<br /> before.length &amp;&amp; before.substring( before.length - 1 ).search( /\S/ ) &gt;= 0 &amp;&amp;<br /> after.length &amp;&amp; after.substr( 0, 1 ).search( /\S/ ) &gt;= 0<br /> ) {<br /> before += ' ';<br /> }<br /> <br /> cat_point = before.length;<br /> if ( cat_point === 0 &amp;&amp; after.length &amp;&amp; after.substr( 0, 1 ) === '\n' ) after = after.substr( 1 );<br /> <br /> wikitext = before + after;<br /> if ( !keyChange ) {<br /> if ( HC.template_categories[ toRemove ] ) { summary.push( HC.messages.template_removed.replace( /\$1/g, toRemove ) ); } else { summary.push( HC.messages.cat_removed.replace( /\$1/g, toRemove ) ); }<br /> }<br /> <br /> }<br /> }<br /> // Add<br /> if ( toAdd &amp;&amp; toAdd.length ) {<br /> matches = find_category( wikitext, toAdd );<br /> if ( matches &amp;&amp; matches.length ) {<br /> // Already exists<br /> return {<br /> text: wikitext,<br /> summary: summary,<br /> error: HC.messages.cat_exists.replace( /\$1/g, toAdd )<br /> };<br /> } else {<br /> var onCat = false;<br /> if ( cat_point &lt; 0 ) {<br /> var point = find_insertionpoint( wikitext );<br /> cat_point = point.idx;<br /> onCat = point.onCat;<br /> } else {<br /> onCat = true;<br /> }<br /> var newcatstring = '[[' + nameSpace + ':' + toAdd + ( key || '' ) + ']]';<br /> if ( cat_point &gt;= 0 ) {<br /> var suffix = wikitext.substring( cat_point );<br /> wikitext = wikitext.substring( 0, cat_point ) + ( cat_point &gt; 0 ? '\n' : '' ) + newcatstring + ( !onCat ? '\n' : '' );<br /> if ( suffix.length &amp;&amp; suffix.substr( 0, 1 ) !== '\n' ) wikitext += '\n' + suffix; else wikitext += suffix;<br /> } else {<br /> if ( wikitext.length &amp;&amp; wikitext.substr( wikitext.length - 1, 1 ) !== '\n' ) wikitext += '\n';<br /> <br /> wikitext += ( wikitext.length ? '\n' : '' ) + newcatstring;<br /> }<br /> if ( keyChange ) {<br /> var k = key || '';<br /> if ( k.length ) k = k.substr( 1 );<br /> <br /> summary.push( substitute( HC.messages.cat_keychange, [ null, toAdd, k ] ) );<br /> } else {<br /> summary.push( HC.messages.cat_added.replace( /\$1/g, toAdd ) );<br /> }<br /> if ( HC.uncat_regexp &amp;&amp; !is_hidden ) {<br /> var txt = wikitext.replace( HC.uncat_regexp, '' ); // Remove &quot;uncat&quot; templates<br /> if ( txt.length !== wikitext.length ) {<br /> wikitext = txt;<br /> summary.push( HC.messages.uncat_removed );<br /> }<br /> }<br /> }<br /> }<br /> return {<br /> text: wikitext,<br /> summary: summary,<br /> error: null<br /> };<br /> }<br /> <br /> // The real HotCat UI<br /> <br /> function evtKeys( e ) {<br /> /* eslint-disable no-bitwise */<br /> var code = 0;<br /> if ( e.ctrlKey ) { // All modern browsers<br /> // Ctrl-click seems to be overloaded in FF/Mac (it opens a pop-up menu), so treat cmd-click<br /> // as a ctrl-click, too.<br /> if ( e.ctrlKey || e.metaKey ) code |= 1;<br /> <br /> if ( e.shiftKey ) code |= 2;<br /> }<br /> return code;<br /> }<br /> function evtKill( e ) {<br /> if ( e.preventDefault ) {<br /> e.preventDefault();<br /> e.stopPropagation();<br /> } else {<br /> e.cancelBubble = true;<br /> }<br /> return false;<br /> }<br /> <br /> var catLine = null,<br /> onUpload = false,<br /> editors = [],<br /> <br /> commitButton = null,<br /> commitForm = null,<br /> multiSpan = null,<br /> <br /> pageText = null,<br /> pageTime = null,<br /> pageWatched = false,<br /> watchCreate = false,<br /> watchEdit = false,<br /> minorEdits = false,<br /> editToken = null,<br /> <br /> is_rtl = false,<br /> serverTime = null,<br /> lastRevId = null,<br /> pageTextRevId = null,<br /> conflictingUser = null,<br /> <br /> newDOM = false; // true if MediaWiki serves the new UL-LI DOM for categories<br /> <br /> function CategoryEditor() {<br /> this.initialize.apply( this, arguments );<br /> }<br /> <br /> function setPage( json ) {<br /> var startTime = null;<br /> if ( json &amp;&amp; json.query ) {<br /> if ( json.query.pages ) {<br /> var page = json.query.pages[ !conf.wgArticleId ? '-1' : String( conf.wgArticleId ) ];<br /> if ( page ) {<br /> if ( page.revisions &amp;&amp; page.revisions.length ) {<br /> // Revisions are sorted by revision ID, hence [ 0 ] is the one we asked for, and possibly there's a [ 1 ] if we're<br /> // not on the latest revision (edit conflicts and such).<br /> pageText = page.revisions[ 0 ][ '*' ];<br /> if ( page.revisions[ 0 ].timestamp ) pageTime = page.revisions[ 0 ].timestamp.replace( /\D/g, '' );<br /> if ( page.revisions[ 0 ].revid ) pageTextRevId = page.revisions[ 0 ].revid;<br /> if ( page.revisions.length &gt; 1 ) conflictingUser = page.revisions[ 1 ].user;<br /> }<br /> if ( page.lastrevid ) lastRevId = page.lastrevid;<br /> if ( page.starttimestamp ) startTime = page.starttimestamp.replace( /\D/g, '' );<br /> pageWatched = typeof page.watched === 'string';<br /> if ( json.query.tokens ) editToken = json.query.tokens.csrftoken;<br /> if ( page.langlinks &amp;&amp; ( !json[ 'query-continue' ] || !json[ 'query-continue' ].langlinks ) ) {<br /> // We have interlanguage links, and we got them all.<br /> var re = '';<br /> for ( var i = 0; i &lt; page.langlinks.length; i++ ) re += ( i &gt; 0 ? '|' : '' ) + page.langlinks[ i ].lang.replace( /([\\^$.?*+()])/g, '\\$1' );<br /> if ( re.length ) interlanguageRE = new RegExp( '((^|\\n\\r?)(\\[\\[\\s*(' + re + ')\\s*:[^\\]]+\\]\\]\\s*))+$' );<br /> }<br /> }<br /> }<br /> // Siteinfo<br /> if ( json.query.general ) {<br /> if ( json.query.general.time &amp;&amp; !startTime ) startTime = json.query.general.time.replace( /\D/g, '' );<br /> <br /> if ( HC.capitalizePageNames === null ) {<br /> // ResourceLoader's JSParser doesn't like .case, so override eslint.<br /> // eslint-disable-next-line dot-notation<br /> HC.capitalizePageNames = ( json.query.general[ 'case' ] === 'first-letter' );<br /> }<br /> }<br /> serverTime = startTime;<br /> // Userinfo<br /> if ( json.query.userinfo &amp;&amp; json.query.userinfo.options ) {<br /> watchCreate = !HC.dont_add_to_watchlist &amp;&amp; json.query.userinfo.options.watchcreations === '1';<br /> watchEdit = !HC.dont_add_to_watchlist &amp;&amp; json.query.userinfo.options.watchdefault === '1';<br /> minorEdits = json.query.userinfo.options.minordefault === 1;<br /> // If the user has the &quot;All edits are minor&quot; preference enabled, we should honor that<br /> // for single category changes, no matter what the site configuration is.<br /> if ( minorEdits ) HC.single_minor = true;<br /> }<br /> }<br /> }<br /> <br /> var saveInProgress = false;<br /> function initiateEdit( doEdit, failure ) {<br /> if ( saveInProgress ) return;<br /> saveInProgress = true;<br /> var oldButtonState;<br /> if ( commitButton ) {<br /> oldButtonState = commitButton.disabled;<br /> commitButton.disabled = true;<br /> }<br /> <br /> function fail() {<br /> saveInProgress = false;<br /> if ( commitButton ) commitButton.disabled = oldButtonState;<br /> failure.apply( this, arguments );<br /> }<br /> <br /> // Must use Ajax here to get the user options and the edit token.<br /> $.getJSON(<br /> conf.wgServer + conf.wgScriptPath + '/api.php?' +<br /> 'format=json&amp;action=query&amp;rawcontinue=&amp;titles=' + encodeURIComponent( conf.wgPageName ) +<br /> '&amp;prop=info%7Crevisions%7Clanglinks&amp;inprop=watched&amp;rvprop=content%7Ctimestamp%7Cids%7Cuser&amp;lllimit=500' +<br /> '&amp;rvlimit=2&amp;rvdir=newer&amp;rvstartid=' + conf.wgCurRevisionId + '&amp;meta=siteinfo%7Cuserinfo%7Ctokens&amp;type=csrf&amp;uiprop=options',<br /> function ( json ) {<br /> setPage( json );<br /> doEdit( fail );<br /> }<br /> ).fail( function ( req ) {<br /> fail( req.status + ' ' + req.statusText );<br /> } );<br /> }<br /> <br /> function multiChangeMsg( count ) {<br /> var msg = HC.messages.multi_change;<br /> if ( typeof msg !== 'string' &amp;&amp; msg.length )<br /> if ( mw.language &amp;&amp; mw.language.convertPlural ) { msg = mw.language.convertPlural( count, msg ); } else { msg = msg[ msg.length - 1 ]; }<br /> <br /> return substitute( msg, [ null, String( count ) ] );<br /> }<br /> <br /> function currentTimestamp() {<br /> var now = new Date();<br /> var ts = String( now.getUTCFullYear() );<br /> function two( s ) {<br /> return s.substr( s.length - 2 );<br /> }<br /> ts +=<br /> two( '0' + ( now.getUTCMonth() + 1 ) ) +<br /> two( '0' + now.getUTCDate() ) +<br /> two( '00' + now.getUTCHours() ) +<br /> two( '00' + now.getUTCMinutes() ) +<br /> two( '00' + now.getUTCSeconds() );<br /> return ts;<br /> }<br /> <br /> function performChanges( failure, singleEditor ) {<br /> if ( pageText === null ) {<br /> failure( HC.messages.multi_error );<br /> return;<br /> }<br /> // Backwards compatibility after message change (added $2 to cat_keychange)<br /> if ( HC.messages.cat_keychange.indexOf( '$2' ) &lt; 0 ) HC.messages.cat_keychange += '&quot;$2&quot;';<br /> <br /> // More backwards-compatibility with earlier HotCat versions:<br /> if ( !HC.messages.short_catchange ) HC.messages.short_catchange = '[[' + HC.category_canonical + ':$1]]';<br /> <br /> // Create a form and submit it. We don't use the edit API (api.php?action=edit) because<br /> // (a) sensibly reporting back errors like edit conflicts is always a hassle, and<br /> // (b) we want to show a diff for multi-edits anyway, and<br /> // (c) we want to trigger onsubmit events, allowing user code to intercept the edit.<br /> // Using the form, we can do (b) and (c), and we get (a) for free. And, of course, using the form<br /> // automatically reloads the page with the updated categories on a successful submit, which<br /> // we would have to do explicitly if we used the edit API.<br /> var action;<br /> // Normally, we don't have to care about edit conflicts. If some other user edited the page in the meantime, the<br /> // server will take care of it and merge the edit automatically or present an edit conflict screen. However, the<br /> // server suppresses edit conflicts with oneself. Hence, if we have a conflict, and the conflicting user is the<br /> // current user, then we set the &quot;oldid&quot; value and switch to diff, which gives the &quot;you are editing an old version;<br /> // if you save, any more recent changes will be lost&quot; screen.<br /> var selfEditConflict = ( lastRevId !== null &amp;&amp; lastRevId !== conf.wgCurRevisionId || pageTextRevId !== null &amp;&amp;<br /> pageTextRevId !== conf.wgCurRevisionId ) &amp;&amp; conflictingUser &amp;&amp; conflictingUser === conf.wgUserName;<br /> if ( singleEditor &amp;&amp; !singleEditor.noCommit &amp;&amp; !HC.no_autocommit &amp;&amp; editToken &amp;&amp; !selfEditConflict ) {<br /> // If we do have an edit conflict, but not with ourself, that's no reason not to attempt to save: the server side may actually be able to<br /> // merge the changes. We just need to make sure that we do present a diff view if it's a self edit conflict.<br /> commitForm.wpEditToken.value = editToken;<br /> action = commitForm.wpDiff;<br /> if ( action ) action.name = action.value = 'wpSave';<br /> } else {<br /> action = commitForm.wpSave;<br /> if ( action ) action.name = action.value = 'wpDiff';<br /> }<br /> var result = {<br /> text: pageText<br /> },<br /> changed = [],<br /> added = [],<br /> deleted = [],<br /> changes = 0,<br /> toEdit = singleEditor ? [ singleEditor ] : editors,<br /> error = null,<br /> edit,<br /> i;<br /> for ( i = 0; i &lt; toEdit.length; i++ ) {<br /> edit = toEdit[ i ];<br /> if ( edit.state === CategoryEditor.CHANGED ) {<br /> result = change_category(<br /> result.text,<br /> edit.originalCategory,<br /> edit.currentCategory,<br /> edit.currentKey,<br /> edit.currentHidden );<br /> if ( !result.error ) {<br /> changes++;<br /> if ( !edit.originalCategory || !edit.originalCategory.length ) {<br /> added.push( edit.currentCategory );<br /> } else {<br /> changed.push( {<br /> from: edit.originalCategory,<br /> to: edit.currentCategory<br /> } );<br /> }<br /> } else if ( error === null ) {<br /> error = result.error;<br /> }<br /> } else if (<br /> edit.state === CategoryEditor.DELETED &amp;&amp; edit.originalCategory &amp;&amp; edit.originalCategory.length ) {<br /> result = change_category(<br /> result.text,<br /> edit.originalCategory,<br /> null, null, false );<br /> if ( !result.error ) {<br /> changes++;<br /> deleted.push( edit.originalCategory );<br /> } else if ( error === null ) {<br /> error = result.error;<br /> }<br /> }<br /> }<br /> if ( error !== null ) { // Do not commit if there were errors<br /> action = commitForm.wpSave;<br /> if ( action ) action.name = action.value = 'wpDiff';<br /> }<br /> // Fill in the form and submit it<br /> commitForm.wpMinoredit.checked = minorEdits;<br /> commitForm.wpWatchthis.checked = !conf.wgArticleId &amp;&amp; watchCreate || watchEdit || pageWatched;<br /> if ( conf.wgArticleId || !!singleEditor ) {<br /> // Prepare change-tag save<br /> if ( action &amp;&amp; action.value === 'wpSave' ) {<br /> if ( HC.changeTag ) {<br /> commitForm.wpChangeTags.value = HC.changeTag;<br /> HC.messages.using = '';<br /> HC.messages.prefix = '';<br /> }<br /> } else {<br /> commitForm.wpAutoSummary.value = HC.changeTag;<br /> }<br /> if ( changes === 1 ) {<br /> if ( result.summary &amp;&amp; result.summary.length ) commitForm.wpSummary.value = HC.messages.prefix + result.summary.join( HC.messages.separator ) + HC.messages.using;<br /> commitForm.wpMinoredit.checked = HC.single_minor || minorEdits;<br /> } else if ( changes ) {<br /> var summary = [];<br /> var shortSummary = [];<br /> // Deleted<br /> for ( i = 0; i &lt; deleted.length; i++ ) summary.push( '−' + substitute( HC.messages.short_catchange, [ null, deleted[ i ] ] ) );<br /> <br /> if ( deleted.length === 1 ) shortSummary.push( '−' + substitute( HC.messages.short_catchange, [ null, deleted[ 0 ] ] ) ); else if ( deleted.length ) shortSummary.push( '− ' + multiChangeMsg( deleted.length ) );<br /> <br /> // Added<br /> for ( i = 0; i &lt; added.length; i++ ) summary.push( '+' + substitute( HC.messages.short_catchange, [ null, added[ i ] ] ) );<br /> <br /> if ( added.length === 1 ) shortSummary.push( '+' + substitute( HC.messages.short_catchange, [ null, added[ 0 ] ] ) ); else if ( added.length ) shortSummary.push( '+ ' + multiChangeMsg( added.length ) );<br /> <br /> // Changed<br /> var arrow = is_rtl ? '\u2190' : '\u2192'; // left and right arrows. Don't use ← and → in the code.<br /> for ( i = 0; i &lt; changed.length; i++ ) {<br /> if ( changed[ i ].from !== changed[ i ].to ) {<br /> summary.push(<br /> '±' + substitute( HC.messages.short_catchange, [ null, changed[ i ].from ] ) + arrow +<br /> substitute( HC.messages.short_catchange, [ null, changed[ i ].to ] )<br /> );<br /> } else {<br /> summary.push( '±' + substitute( HC.messages.short_catchange, [ null, changed[ i ].from ] ) );<br /> }<br /> }<br /> if ( changed.length === 1 ) {<br /> if ( changed[ 0 ].from !== changed[ 0 ].to ) {<br /> shortSummary.push(<br /> '±' + substitute( HC.messages.short_catchange, [ null, changed[ 0 ].from ] ) + arrow +<br /> substitute( HC.messages.short_catchange, [ null, changed[ 0 ].to ] )<br /> );<br /> } else {<br /> shortSummary.push( '±' + substitute( HC.messages.short_catchange, [ null, changed[ 0 ].from ] ) );<br /> }<br /> } else if ( changed.length ) {<br /> shortSummary.push( '± ' + multiChangeMsg( changed.length ) );<br /> }<br /> if ( summary.length ) {<br /> summary = summary.join( HC.messages.separator );<br /> if ( summary.length &gt; 200 - HC.messages.prefix.length - HC.messages.using.length ) summary = shortSummary.join( HC.messages.separator );<br /> <br /> commitForm.wpSummary.value = HC.messages.prefix + summary + HC.messages.using;<br /> }<br /> }<br /> }<br /> <br /> commitForm.wpTextbox1.value = result.text;<br /> commitForm.wpStarttime.value = serverTime || currentTimestamp();<br /> commitForm.wpEdittime.value = pageTime || commitForm.wpStarttime.value;<br /> if ( selfEditConflict ) commitForm.oldid.value = String( pageTextRevId || conf.wgCurRevisionId );<br /> <br /> // Submit the form in a way that triggers onsubmit events: commitForm.submit() doesn't.<br /> commitForm.hcCommit.click();<br /> }<br /> <br /> function resolveOne( page, toResolve ) {<br /> var cats = page.categories,<br /> lks = page.links,<br /> is_dab = false,<br /> is_redir = typeof page.redirect === 'string', // Hard redirect?<br /> is_hidden = page.categoryinfo &amp;&amp; typeof page.categoryinfo.hidden === 'string',<br /> is_missing = typeof page.missing === 'string',<br /> i;<br /> for ( i = 0; i &lt; toResolve.length; i++ ) {<br /> if ( i &amp;&amp; toResolve[ i ].dabInputCleaned !== page.title.substring( page.title.indexOf( ':' ) + 1 ) ) continue;<br /> // Note: the server returns in page an NFC normalized Unicode title. If our input was not NFC normalized, we may not find<br /> // any entry here. If we have only one editor to resolve (the most common case, I presume), we may simply skip the check.<br /> toResolve[ i ].currentHidden = is_hidden;<br /> toResolve[ i ].inputExists = !is_missing;<br /> toResolve[ i ].icon.src = ( is_missing ? HC.existsNo : HC.existsYes );<br /> }<br /> if ( is_missing ) return;<br /> if ( !is_redir &amp;&amp; cats &amp;&amp; ( HC.disambig_category || HC.redir_category ) ) {<br /> for ( var c = 0; c &lt; cats.length; c++ ) {<br /> var cat = cats[ c ].title;<br /> // Strip namespace prefix<br /> if ( cat ) {<br /> cat = cat.substring( cat.indexOf( ':' ) + 1 ).replace( /_/g, ' ' );<br /> if ( cat === HC.disambig_category ) {<br /> is_dab = true;<br /> break;<br /> } else if ( cat === HC.redir_category ) {<br /> is_redir = true;<br /> break;<br /> }<br /> }<br /> }<br /> }<br /> if ( !is_redir &amp;&amp; !is_dab ) return;<br /> if ( !lks || !lks.length ) return;<br /> var titles = [];<br /> for ( i = 0; i &lt; lks.length; i++ ) {<br /> if (<br /> // Category namespace -- always true since we ask only for the category links<br /> lks[ i ].ns === 14 &amp;&amp;<br /> // Name not empty<br /> lks[ i ].title &amp;&amp; lks[ i ].title.length<br /> ) {<br /> // Internal link to existing thingy. Extract the page name and remove the namespace.<br /> var match = lks[ i ].title;<br /> match = match.substring( match.indexOf( ':' ) + 1 );<br /> // Exclude blacklisted categories.<br /> if ( !HC.blacklist || !HC.blacklist.test( match ) ) titles.push( match );<br /> }<br /> }<br /> if ( !titles.length ) return;<br /> for ( i = 0; i &lt; toResolve.length; i++ ) {<br /> if ( i &amp;&amp; toResolve[ i ].dabInputCleaned !== page.title.substring( page.title.indexOf( ':' ) + 1 ) ) continue;<br /> toResolve[ i ].inputExists = true; // Might actually be wrong if it's a redirect pointing to a non-existing category<br /> toResolve[ i ].icon.src = HC.existsYes;<br /> if ( titles.length &gt; 1 ) {<br /> toResolve[ i ].dab = titles;<br /> } else {<br /> toResolve[ i ].text.value =<br /> titles[ 0 ] + ( toResolve[ i ].currentKey !== null ? '|' + toResolve[ i ].currentKey : '' );<br /> }<br /> }<br /> }<br /> <br /> function resolveRedirects( toResolve, params ) {<br /> if ( !params || !params.query || !params.query.pages ) return;<br /> for ( var p in params.query.pages ) resolveOne( params.query.pages[ p ], toResolve );<br /> }<br /> <br /> function resolveMulti( toResolve, callback ) {<br /> var i;<br /> for ( i = 0; i &lt; toResolve.length; i++ ) {<br /> toResolve[ i ].dab = null;<br /> toResolve[ i ].dabInput = toResolve[ i ].lastInput;<br /> }<br /> if ( noSuggestions ) {<br /> callback( toResolve );<br /> return;<br /> }<br /> // Use %7C instead of |, otherwise Konqueror insists on re-encoding the arguments, resulting in doubly encoded<br /> // category names. (That is a bug in Konqueror. Other browsers don't have this problem.)<br /> var args = 'action=query&amp;prop=info%7Clinks%7Ccategories%7Ccategoryinfo&amp;plnamespace=14' +<br /> '&amp;pllimit=' + ( toResolve.length * 10 ) +<br /> '&amp;cllimit=' + ( toResolve.length * 10 ) +<br /> '&amp;format=json&amp;titles=';<br /> for ( i = 0; i &lt; toResolve.length; i++ ) {<br /> var v = toResolve[ i ].dabInput;<br /> v = replaceShortcuts( v, HC.shortcuts );<br /> toResolve[ i ].dabInputCleaned = v;<br /> args += encodeURIComponent( 'Category:' + v );<br /> if ( i + 1 &lt; toResolve.length ) args += '%7C';<br /> }<br /> $.getJSON( conf.wgServer + conf.wgScriptPath + '/api.php?' + args,<br /> function ( json ) {<br /> resolveRedirects( toResolve, json );<br /> callback( toResolve );<br /> } ).fail( function ( req ) {<br /> if ( !req ) noSuggestions = true;<br /> callback( toResolve );<br /> } );<br /> }<br /> <br /> function makeActive( which ) {<br /> if ( which.is_active ) return;<br /> for ( var i = 0; i &lt; editors.length; i++ )<br /> if ( editors[ i ] !== which ) editors[ i ].inactivate();<br /> <br /> which.is_active = true;<br /> if ( which.dab ) {<br /> // eslint-disable-next-line no-use-before-define<br /> showDab( which );<br /> } else {<br /> // Check for programmatic value changes.<br /> var expectedInput = which.lastRealInput || which.lastInput || '';<br /> var actualValue = which.text.value || '';<br /> if ( !expectedInput.length &amp;&amp; actualValue.length || expectedInput.length &amp;&amp; actualValue.indexOf( expectedInput ) ) {<br /> // Somehow the field's value appears to have changed, and which.lastSelection therefore is no longer valid. Try to set the<br /> // cursor at the end of the category, and do not display the old suggestion list.<br /> which.showsList = false;<br /> var v = actualValue.split( '|' );<br /> which.lastRealInput = which.lastInput = v[ 0 ];<br /> if ( v.length &gt; 1 ) which.currentKey = v[ 1 ];<br /> <br /> if ( which.lastSelection ) {<br /> which.lastSelection = {<br /> start: v[ 0 ].length,<br /> end: v[ 0 ].length<br /> };<br /> }<br /> }<br /> if ( which.showsList ) which.displayList();<br /> <br /> if ( which.lastSelection ) {<br /> if ( is_webkit ) {<br /> // WebKit (Safari, Chrome) has problems selecting inside focus()<br /> // See http://code.google.com/p/chromium/issues/detail?id=32865#c6<br /> window.setTimeout(<br /> function () {<br /> which.setSelection( which.lastSelection.start, which.lastSelection.end );<br /> },<br /> 1 );<br /> } else {<br /> which.setSelection( which.lastSelection.start, which.lastSelection.end );<br /> }<br /> }<br /> }<br /> }<br /> <br /> function showDab( which ) {<br /> if ( !which.is_active ) {<br /> makeActive( which );<br /> } else {<br /> which.showSuggestions( which.dab, false, null, null ); // do autocompletion, no key, no engine selector<br /> which.dab = null;<br /> }<br /> }<br /> <br /> function multiSubmit() {<br /> var toResolve = [];<br /> for ( var i = 0; i &lt; editors.length; i++ )<br /> if ( editors[ i ].state === CategoryEditor.CHANGE_PENDING || editors[ i ].state === CategoryEditor.OPEN ) toResolve.push( editors[ i ] );<br /> <br /> if ( !toResolve.length ) {<br /> initiateEdit( function ( failure ) {<br /> performChanges( failure );<br /> }, function ( msg ) {<br /> alert( msg );<br /> } );<br /> return;<br /> }<br /> resolveMulti( toResolve, function ( resolved ) {<br /> var firstDab = null;<br /> var dontChange = false;<br /> for ( var i = 0; i &lt; resolved.length; i++ ) {<br /> if ( resolved[ i ].lastInput !== resolved[ i ].dabInput ) {<br /> // We didn't disable all the open editors, but we did asynchronous calls. It is<br /> // theoretically possible that the user changed something...<br /> dontChange = true;<br /> } else {<br /> if ( resolved[ i ].dab ) {<br /> if ( !firstDab ) firstDab = resolved[ i ];<br /> } else {<br /> if ( resolved[ i ].acceptCheck( true ) ) resolved[ i ].commit();<br /> }<br /> }<br /> }<br /> if ( firstDab ) {<br /> showDab( firstDab );<br /> } else if ( !dontChange ) {<br /> initiateEdit( function ( failure ) {<br /> performChanges( failure );<br /> }, function ( msg ) {<br /> alert( msg );<br /> } );<br /> }<br /> } );<br /> }<br /> <br /> function setMultiInput() {<br /> if ( commitButton || onUpload ) return;<br /> commitButton = make( 'input' );<br /> commitButton.type = 'button';<br /> commitButton.value = HC.messages.commit;<br /> commitButton.onclick = multiSubmit;<br /> if ( multiSpan ) multiSpan.parentNode.replaceChild( commitButton, multiSpan ); else catLine.appendChild( commitButton );<br /> }<br /> <br /> function checkMultiInput() {<br /> if ( !commitButton ) return;<br /> var hasChanges = false;<br /> for ( var i = 0; i &lt; editors.length; i++ ) {<br /> if ( editors[ i ].state !== CategoryEditor.UNCHANGED ) {<br /> hasChanges = true;<br /> break;<br /> }<br /> }<br /> commitButton.disabled = !hasChanges;<br /> }<br /> <br /> var suggestionEngines = {<br /> opensearch: {<br /> uri: '/api.php?format=json&amp;action=opensearch&amp;namespace=14&amp;limit=30&amp;search=Category:$1', // $1 = search term<br /> // Function to convert result of uri into an array of category names<br /> handler: function ( queryResult, queryKey ) {<br /> if ( queryResult &amp;&amp; queryResult.length &gt;= 2 ) {<br /> var key = queryResult[ 0 ].substring( queryResult[ 0 ].indexOf( ':' ) + 1 );<br /> var titles = queryResult[ 1 ];<br /> var exists = false;<br /> if ( !cat_prefix ) cat_prefix = new RegExp( '^(' + HC.category_regexp + '):' );<br /> <br /> for ( var i = 0; i &lt; titles.length; i++ ) {<br /> cat_prefix.lastIndex = 0;<br /> var m = cat_prefix.exec( titles[ i ] );<br /> if ( m &amp;&amp; m.length &gt; 1 ) {<br /> titles[ i ] = titles[ i ].substring( titles[ i ].indexOf( ':' ) + 1 ); // rm namespace<br /> if ( key === titles[ i ] ) exists = true;<br /> } else {<br /> titles.splice( i, 1 ); // Nope, it's not a category after all.<br /> i--;<br /> }<br /> }<br /> titles.exists = exists;<br /> if ( queryKey !== key ) titles.normalized = key;<br /> // Remember the NFC normalized key we got back from the server<br /> return titles;<br /> }<br /> return null;<br /> }<br /> },<br /> internalsearch: {<br /> uri: '/api.php?format=json&amp;action=query&amp;list=allpages&amp;apnamespace=14&amp;aplimit=30&amp;apfrom=$1&amp;apprefix=$1',<br /> handler: function ( queryResult ) {<br /> if ( queryResult &amp;&amp; queryResult.query &amp;&amp; queryResult.query.allpages ) {<br /> var titles = queryResult.query.allpages;<br /> for ( var i = 0; i &lt; titles.length; i++ ) titles[ i ] = titles[ i ].title.substring( titles[ i ].title.indexOf( ':' ) + 1 ); // rm namespace<br /> <br /> return titles;<br /> }<br /> return null;<br /> }<br /> },<br /> exists: {<br /> uri: '/api.php?format=json&amp;action=query&amp;prop=info&amp;titles=Category:$1',<br /> handler: function ( queryResult, queryKey ) {<br /> if ( queryResult &amp;&amp; queryResult.query &amp;&amp; queryResult.query.pages &amp;&amp; !queryResult.query.pages[ -1 ] ) {<br /> // Should have exactly 1<br /> for ( var p in queryResult.query.pages ) {<br /> var title = queryResult.query.pages[ p ].title;<br /> title = title.substring( title.indexOf( ':' ) + 1 );<br /> var titles = [ title ];<br /> titles.exists = true;<br /> if ( queryKey !== title ) titles.normalized = title;<br /> // NFC<br /> return titles;<br /> }<br /> }<br /> return null;<br /> }<br /> },<br /> subcategories: {<br /> uri: '/api.php?format=json&amp;action=query&amp;list=categorymembers&amp;cmtype=subcat&amp;cmlimit=max&amp;cmtitle=Category:$1',<br /> handler: function ( queryResult ) {<br /> if ( queryResult &amp;&amp; queryResult.query &amp;&amp; queryResult.query.categorymembers ) {<br /> var titles = queryResult.query.categorymembers;<br /> for ( var i = 0; i &lt; titles.length; i++ ) titles[ i ] = titles[ i ].title.substring( titles[ i ].title.indexOf( ':' ) + 1 ); // rm namespace<br /> <br /> return titles;<br /> }<br /> return null;<br /> }<br /> },<br /> parentcategories: {<br /> uri: '/api.php?format=json&amp;action=query&amp;prop=categories&amp;titles=Category:$1&amp;cllimit=max',<br /> handler: function ( queryResult ) {<br /> if ( queryResult &amp;&amp; queryResult.query &amp;&amp; queryResult.query.pages ) {<br /> for ( var p in queryResult.query.pages ) {<br /> if ( queryResult.query.pages[ p ].categories ) {<br /> var titles = queryResult.query.pages[ p ].categories;<br /> for ( var i = 0; i &lt; titles.length; i++ ) titles[ i ] = titles[ i ].title.substring( titles[ i ].title.indexOf( ':' ) + 1 ); // rm namespace<br /> <br /> return titles;<br /> }<br /> }<br /> }<br /> return null;<br /> }<br /> }<br /> };<br /> <br /> var suggestionConfigs = {<br /> searchindex: {<br /> name: 'Search index',<br /> engines: [ 'opensearch' ],<br /> cache: {},<br /> show: true,<br /> temp: false,<br /> noCompletion: false<br /> },<br /> pagelist: {<br /> name: 'Page list',<br /> engines: [ 'internalsearch', 'exists' ],<br /> cache: {},<br /> show: true,<br /> temp: false,<br /> noCompletion: false<br /> },<br /> combined: {<br /> name: 'Combined search',<br /> engines: [ 'opensearch', 'internalsearch' ],<br /> cache: {},<br /> show: true,<br /> temp: false,<br /> noCompletion: false<br /> },<br /> subcat: {<br /> name: 'Subcategories',<br /> engines: [ 'subcategories' ],<br /> cache: {},<br /> show: true,<br /> temp: true,<br /> noCompletion: true<br /> },<br /> parentcat: {<br /> name: 'Parent categories',<br /> engines: [ 'parentcategories' ],<br /> cache: {},<br /> show: true,<br /> temp: true,<br /> noCompletion: true<br /> }<br /> };<br /> <br /> CategoryEditor.UNCHANGED = 0;<br /> CategoryEditor.OPEN = 1; // Open, but no input yet<br /> CategoryEditor.CHANGE_PENDING = 2; // Open, some input made<br /> CategoryEditor.CHANGED = 3;<br /> CategoryEditor.DELETED = 4;<br /> <br /> // Support: IE6<br /> // IE6 sometimes forgets to redraw the list when editors are opened or closed.<br /> // Adding/removing a dummy element helps, at least when opening editors.<br /> var dummyElement = make( '\xa0', true );<br /> <br /> function forceRedraw() {<br /> if ( dummyElement.parentNode ) document.body.removeChild( dummyElement ); else document.body.appendChild( dummyElement );<br /> }<br /> <br /> // Event keyCodes that we handle in the text input field/suggestion list.<br /> var BS = 8,<br /> TAB = 9,<br /> RET = 13,<br /> ESC = 27,<br /> SPACE = 32,<br /> PGUP = 33,<br /> PGDOWN = 34,<br /> UP = 38,<br /> DOWN = 40,<br /> DEL = 46,<br /> IME = 229;<br /> <br /> CategoryEditor.prototype = {<br /> <br /> initialize: function ( line, span, after, key, is_hidden ) {<br /> // If a span is given, 'after' is the category title, otherwise it may be an element after which to<br /> // insert the new span. 'key' is likewise overloaded; if a span is given, it is the category key (if<br /> // known), otherwise it is a boolean indicating whether a bar shall be prepended.<br /> if ( !span ) {<br /> this.isAddCategory = true;<br /> // Create add span and append to catLinks<br /> this.originalCategory = '';<br /> this.originalKey = null;<br /> this.originalExists = false;<br /> if ( !newDOM ) {<br /> span = make( 'span' );<br /> span.className = 'noprint';<br /> if ( key ) {<br /> span.appendChild( make( ' | ', true ) );<br /> if ( after ) {<br /> after.parentNode.insertBefore( span, after.nextSibling );<br /> after = after.nextSibling;<br /> } else if (line) {<br /> line.appendChild( span );<br /> }<br /> } else if ( line &amp;&amp; line.firstChild ) {<br /> span.appendChild( make( ' ', true ) );<br /> line.appendChild( span );<br /> }<br /> }<br /> this.linkSpan = make( 'span' );<br /> this.linkSpan.className = 'noprint nopopups hotcatlink';<br /> var lk = make( 'a' );<br /> lk.href = '#catlinks';<br /> lk.onclick = this.open.bind( this );<br /> lk.appendChild( make( HC.links.add, true ) );<br /> lk.title = HC.tooltips.add;<br /> this.linkSpan.appendChild( lk );<br /> span = make( newDOM ? 'li' : 'span' );<br /> span.className = 'noprint';<br /> if ( is_rtl ) span.dir = 'rtl';<br /> <br /> span.appendChild( this.linkSpan );<br /> if ( after ) {<br /> after.parentNode.insertBefore( span, after.nextSibling );<br /> } else if ( line ) {<br /> line.appendChild( span );<br /> }<br /> <br /> this.normalLinks = null;<br /> this.undelLink = null;<br /> this.catLink = null;<br /> } else {<br /> if ( is_rtl ) span.dir = 'rtl';<br /> <br /> this.isAddCategory = false;<br /> this.catLink = span.firstChild;<br /> this.originalCategory = after;<br /> this.originalKey = ( key &amp;&amp; key.length &gt; 1 ) ? key.substr( 1 ) : null; // &gt; 1 because it includes the leading bar<br /> this.originalExists = !hasClass( this.catLink, 'new' );<br /> // Create change and del links<br /> this.makeLinkSpan();<br /> if ( !this.originalExists &amp;&amp; this.upDownLinks ) this.upDownLinks.style.display = 'none';<br /> <br /> span.appendChild( this.linkSpan );<br /> }<br /> this.originalHidden = is_hidden;<br /> this.line = line;<br /> this.engine = HC.suggestions;<br /> this.span = span;<br /> this.currentCategory = this.originalCategory;<br /> this.currentExists = this.originalExists;<br /> this.currentHidden = this.originalHidden;<br /> this.currentKey = this.originalKey;<br /> this.state = CategoryEditor.UNCHANGED;<br /> this.lastSavedState = CategoryEditor.UNCHANGED;<br /> this.lastSavedCategory = this.originalCategory;<br /> this.lastSavedKey = this.originalKey;<br /> this.lastSavedExists = this.originalExists;<br /> this.lastSavedHidden = this.originalHidden;<br /> if ( this.catLink &amp;&amp; this.currentKey ) this.catLink.title = this.currentKey;<br /> <br /> editors[ editors.length ] = this;<br /> },<br /> <br /> makeLinkSpan: function () {<br /> this.normalLinks = make( 'span' );<br /> var lk = null;<br /> if ( this.originalCategory &amp;&amp; this.originalCategory.length ) {<br /> lk = make( 'a' );<br /> lk.href = '#catlinks';<br /> lk.onclick = this.remove.bind( this );<br /> lk.appendChild( make( HC.links.remove, true ) );<br /> lk.title = HC.tooltips.remove;<br /> this.normalLinks.appendChild( make( ' ', true ) );<br /> this.normalLinks.appendChild( lk );<br /> }<br /> if ( !HC.template_categories[ this.originalCategory ] ) {<br /> lk = make( 'a' );<br /> lk.href = '#catlinks';<br /> lk.onclick = this.open.bind( this );<br /> lk.appendChild( make( HC.links.change, true ) );<br /> lk.title = HC.tooltips.change;<br /> this.normalLinks.appendChild( make( ' ', true ) );<br /> this.normalLinks.appendChild( lk );<br /> if ( !noSuggestions &amp;&amp; HC.use_up_down ) {<br /> this.upDownLinks = make( 'span' );<br /> lk = make( 'a' );<br /> lk.href = '#catlinks';<br /> lk.onclick = this.down.bind( this );<br /> lk.appendChild( make( HC.links.down, true ) );<br /> lk.title = HC.tooltips.down;<br /> this.upDownLinks.appendChild( make( ' ', true ) );<br /> this.upDownLinks.appendChild( lk );<br /> lk = make( 'a' );<br /> lk.href = '#catlinks';<br /> lk.onclick = this.up.bind( this );<br /> lk.appendChild( make( HC.links.up, true ) );<br /> lk.title = HC.tooltips.up;<br /> this.upDownLinks.appendChild( make( ' ', true ) );<br /> this.upDownLinks.appendChild( lk );<br /> this.normalLinks.appendChild( this.upDownLinks );<br /> }<br /> }<br /> this.linkSpan = make( 'span' );<br /> this.linkSpan.className = 'noprint nopopups hotcatlink';<br /> this.linkSpan.appendChild( this.normalLinks );<br /> this.undelLink = make( 'span' );<br /> this.undelLink.className = 'nopopups hotcatlink';<br /> this.undelLink.style.display = 'none';<br /> lk = make( 'a' );<br /> lk.href = '#catlinks';<br /> lk.onclick = this.restore.bind( this );<br /> lk.appendChild( make( HC.links.restore, true ) );<br /> lk.title = HC.tooltips.restore;<br /> this.undelLink.appendChild( make( ' ', true ) );<br /> this.undelLink.appendChild( lk );<br /> this.linkSpan.appendChild( this.undelLink );<br /> },<br /> <br /> invokeSuggestions: function ( dont_autocomplete ) {<br /> if ( this.engine &amp;&amp; suggestionConfigs[ this.engine ] &amp;&amp; suggestionConfigs[ this.engine ].temp &amp;&amp; !dont_autocomplete ) this.engine = HC.suggestions; // Reset to a search upon input<br /> <br /> this.state = CategoryEditor.CHANGE_PENDING;<br /> var self = this;<br /> window.setTimeout( function () {<br /> self.textchange( dont_autocomplete );<br /> }, HC.suggest_delay );<br /> },<br /> <br /> makeForm: function () {<br /> var form = make( 'form' );<br /> form.method = 'POST';<br /> form.onsubmit = this.accept.bind( this );<br /> this.form = form;<br /> var self = this;<br /> var text = make( 'input' );<br /> text.type = 'text';<br /> text.size = HC.editbox_width;<br /> if ( !noSuggestions ) {<br /> // Be careful here to handle IME input. This is browser/OS/IME dependent, but basically there are two mechanisms:<br /> // - Modern (DOM Level 3) browsers use compositionstart/compositionend events to signal composition; if the<br /> // composition is not canceled, there'll be a textInput event following. During a composition key events are<br /> // either all suppressed (FF/Gecko), or otherwise have keyDown === IME for all keys (Webkit).<br /> // - Webkit sends a textInput followed by keyDown === IME and a keyUp with the key that ended composition.<br /> // - Gecko doesn't send textInput but just a keyUp with the key that ended composition, without sending keyDown<br /> // first. Gecko doesn't send any keydown while IME is active.<br /> // - Older browsers signal composition by keyDown === IME for the first and subsequent keys for a composition. The<br /> // first keyDown !== IME is certainly after the end of the composition. Typically, composition end can also be<br /> // detected by a keyDown IME with a keyUp of space, tab, escape, or return.<br /> text.onkeyup = function ( evt ) {<br /> var key = evt.keyCode || 0;<br /> if ( self.ime &amp;&amp; self.lastKey === IME &amp;&amp; !self.usesComposition &amp;&amp; ( key === TAB || key === RET || key === ESC || key === SPACE ) ) self.ime = false;<br /> <br /> if ( self.ime ) return true;<br /> <br /> if ( key === UP || key === DOWN || key === PGUP || key === PGDOWN ) {<br /> // In case a browser doesn't generate keypress events for arrow keys...<br /> if ( self.keyCount === 0 ) return self.processKey( evt );<br /> } else {<br /> if ( key === ESC &amp;&amp; self.lastKey !== IME ) {<br /> if ( !self.resetKeySelection() ) {<br /> // No undo of key selection: treat ESC as &quot;cancel&quot;.<br /> self.cancel();<br /> return;<br /> }<br /> }<br /> // Also do this for ESC as a workaround for Firefox bug 524360<br /> // https://bugzilla.mozilla.org/show_bug.cgi?id=524360<br /> self.invokeSuggestions( key === BS || key === DEL || key === ESC );<br /> }<br /> return true;<br /> };<br /> text.onkeydown = function ( evt ) {<br /> var key = evt.keyCode || 0;<br /> self.lastKey = key;<br /> self.keyCount = 0;<br /> // DOM Level &lt; 3 IME input<br /> if ( !self.ime &amp;&amp; key === IME &amp;&amp; !self.usesComposition ) {<br /> // self.usesComposition catches browsers that may emit spurious keydown IME after a composition has ended<br /> self.ime = true;<br /> } else if ( self.ime &amp;&amp; key !== IME &amp;&amp; !( key &gt;= 16 &amp;&amp; key &lt;= 20 || key &gt;= 91 &amp;&amp; key &lt;= 93 || key === 144 ) ) {<br /> // Ignore control keys: ctrl, shift, alt, alt gr, caps lock, windows/apple cmd keys, num lock. Only the windows keys<br /> // terminate IME (apple cmd doesn't), but they also cause a blur, so it's OK to ignore them here.<br /> // Note: Safari 4 (530.17) propagates ESC out of an IME composition (observed at least on Win XP).<br /> self.ime = false;<br /> }<br /> if ( self.ime ) return true;<br /> <br /> // Handle return explicitly, to override the default form submission to be able to check for ctrl<br /> if ( key === RET ) return self.accept( evt );<br /> <br /> // Inhibit default behavior of ESC (revert to last real input in FF: we do that ourselves)<br /> return ( key === ESC ) ? evtKill( evt ) : true;<br /> };<br /> // And handle continued pressing of arrow keys<br /> text.onkeypress = function ( evt ) {<br /> self.keyCount++;<br /> return self.processKey( evt );<br /> };<br /> $( text ).on( 'focus', function () {<br /> makeActive( self );<br /> } );<br /> // On IE, blur events are asynchronous, and may thus arrive after the element has lost the focus. Since IE<br /> // can get the selection only while the element is active (has the focus), we may not always get the selection.<br /> // Therefore, use an IE-specific synchronous event on IE...<br /> // Don't test for text.selectionStart being defined;<br /> $( text ).on(<br /> ( text.onbeforedeactivate !== undefined &amp;&amp; text.createTextRange ) ? 'beforedeactivate' : 'blur',<br /> this.saveView.bind( this ) );<br /> // DOM Level 3 IME handling<br /> try {<br /> // Setting lastKey = IME provides a fake keyDown for Gecko's single keyUp after a cmposition. If we didn't do this,<br /> // cancelling a composition via ESC would also cancel and close the whole category input editor.<br /> $( text ).on( 'compositionstart', function () {<br /> self.lastKey = IME;<br /> self.usesComposition = true;<br /> self.ime = true;<br /> } );<br /> $( text ).on( 'compositionend', function () {<br /> self.lastKey = IME;<br /> self.usesComposition = true;<br /> self.ime = false;<br /> } );<br /> $( text ).on( 'textInput', function () {<br /> self.ime = false;<br /> self.invokeSuggestions( false );<br /> } );<br /> } catch ( any ) {<br /> // Just in case some browsers might produce exceptions with these DOM Level 3 events<br /> }<br /> $( text ).on( 'blur', function () {<br /> self.usesComposition = false;<br /> self.ime = false;<br /> } );<br /> }<br /> this.text = text;<br /> <br /> this.icon = make( 'img' );<br /> <br /> var list = null;<br /> if ( !noSuggestions ) {<br /> list = make( 'select' );<br /> list.onclick = function () {<br /> if ( self.highlightSuggestion( 0 ) ) self.textchange( false, true );<br /> };<br /> list.ondblclick = function ( e ) {<br /> if ( self.highlightSuggestion( 0 ) ) self.accept( e );<br /> };<br /> list.onchange = function () {<br /> self.highlightSuggestion( 0 );<br /> self.text.focus();<br /> };<br /> list.onkeyup = function ( evt ) {<br /> if ( evt.keyCode === ESC ) {<br /> self.resetKeySelection();<br /> self.text.focus();<br /> window.setTimeout( function () {<br /> self.textchange( true );<br /> }, HC.suggest_delay );<br /> } else if ( evt.keyCode === RET ) {<br /> self.accept( evt );<br /> }<br /> };<br /> if ( !HC.fixed_search ) {<br /> var engineSelector = make( 'select' );<br /> for ( var key in suggestionConfigs ) {<br /> if ( suggestionConfigs[ key ].show ) {<br /> var opt = make( 'option' );<br /> opt.value = key;<br /> if ( key === this.engine ) opt.selected = true;<br /> <br /> opt.appendChild( make( suggestionConfigs[ key ].name, true ) );<br /> engineSelector.appendChild( opt );<br /> }<br /> }<br /> engineSelector.onchange = function () {<br /> self.engine = self.engineSelector.options[ self.engineSelector.selectedIndex ].value;<br /> self.text.focus();<br /> self.textchange( true, true ); // Don't autocomplete, force re-display of list<br /> };<br /> this.engineSelector = engineSelector;<br /> }<br /> }<br /> this.list = list;<br /> <br /> function button_label( id, defaultText ) {<br /> var label = null;<br /> if (<br /> onUpload &amp;&amp;<br /> window.UFUI !== undefined &amp;&amp;<br /> window.UIElements !== undefined &amp;&amp;<br /> UFUI.getLabel instanceof Function<br /> ) {<br /> try {<br /> label = UFUI.getLabel( id, true );<br /> // Extract the plain text. IE doesn't know that Node.TEXT_NODE === 3<br /> while ( label &amp;&amp; label.nodeType !== 3 ) label = label.firstChild;<br /> } catch ( ex ) {<br /> label = null;<br /> }<br /> }<br /> if ( !label || !label.data ) return defaultText;<br /> <br /> return label.data;<br /> }<br /> <br /> // Do not use type 'submit'; we cannot detect modifier keys if we do<br /> var OK = make( 'input' );<br /> OK.type = 'button';<br /> OK.value = button_label( 'wpOkUploadLbl', HC.messages.ok );<br /> OK.onclick = this.accept.bind( this );<br /> this.ok = OK;<br /> <br /> var cancel = make( 'input' );<br /> cancel.type = 'button';<br /> cancel.value = button_label( 'wpCancelUploadLbl', HC.messages.cancel );<br /> cancel.onclick = this.cancel.bind( this );<br /> this.cancelButton = cancel;<br /> <br /> var span = make( 'span' );<br /> span.className = 'hotcatinput';<br /> span.style.position = 'relative';<br /> span.appendChild( text );<br /> <br /> // Support: IE8, IE9<br /> // Put some text into this span (a0 is nbsp) and make sure it always stays on the same<br /> // line as the input field, otherwise, IE8/9 miscalculates the height of the span and<br /> // then the engine selector may overlap the input field.<br /> span.appendChild( make( '\xa0', true ) );<br /> span.style.whiteSpace = 'nowrap';<br /> <br /> if ( list ) span.appendChild( list );<br /> <br /> if ( this.engineSelector ) span.appendChild( this.engineSelector );<br /> <br /> if ( !noSuggestions ) span.appendChild( this.icon );<br /> <br /> span.appendChild( OK );<br /> span.appendChild( cancel );<br /> form.appendChild( span );<br /> form.style.display = 'none';<br /> this.span.appendChild( form );<br /> },<br /> <br /> display: function ( evt ) {<br /> if ( this.isAddCategory &amp;&amp; !onUpload &amp;&amp; this.line ) {<br /> // eslint-disable-next-line no-new<br /> new CategoryEditor( this.line, null, this.span, true ); // Create a new one<br /> }<br /> if ( !commitButton &amp;&amp; !onUpload ) {<br /> for ( var i = 0; i &lt; editors.length; i++ ) {<br /> if ( editors[ i ].state !== CategoryEditor.UNCHANGED ) {<br /> setMultiInput();<br /> break;<br /> }<br /> }<br /> }<br /> if ( !this.form ) this.makeForm();<br /> <br /> if ( this.list ) this.list.style.display = 'none';<br /> <br /> if ( this.engineSelector ) this.engineSelector.style.display = 'none';<br /> <br /> this.currentCategory = this.lastSavedCategory;<br /> this.currentExists = this.lastSavedExists;<br /> this.currentHidden = this.lastSavedHidden;<br /> this.currentKey = this.lastSavedKey;<br /> this.icon.src = ( this.currentExists ? HC.existsYes : HC.existsNo );<br /> this.text.value = this.currentCategory + ( this.currentKey !== null ? '|' + this.currentKey : '' );<br /> this.originalState = this.state;<br /> this.lastInput = this.currentCategory;<br /> this.inputExists = this.currentExists;<br /> this.state = this.state === CategoryEditor.UNCHANGED ? CategoryEditor.OPEN : CategoryEditor.CHANGE_PENDING;<br /> this.lastSelection = {<br /> start: this.currentCategory.length,<br /> end: this.currentCategory.length<br /> };<br /> this.showsList = false;<br /> // Display the form<br /> if ( this.catLink ) this.catLink.style.display = 'none';<br /> <br /> this.linkSpan.style.display = 'none';<br /> this.form.style.display = 'inline';<br /> this.ok.disabled = false;<br /> // Kill the event before focussing, otherwise IE will kill the onfocus event!<br /> var result = evtKill( evt );<br /> this.text.focus();<br /> this.text.readOnly = false;<br /> checkMultiInput();<br /> return result;<br /> },<br /> <br /> show: function ( evt, engine, readOnly ) {<br /> var result = this.display( evt );<br /> var v = this.lastSavedCategory;<br /> if ( !v.length ) return result;<br /> <br /> this.text.readOnly = !!readOnly;<br /> this.engine = engine;<br /> this.textchange( false, true ); // do autocompletion, force display of suggestions<br /> forceRedraw();<br /> return result;<br /> },<br /> <br /> open: function ( evt ) {<br /> return this.show( evt, ( this.engine &amp;&amp; suggestionConfigs[ this.engine ].temp ) ? HC.suggestions : this.engine );<br /> },<br /> <br /> down: function ( evt ) {<br /> return this.show( evt, 'subcat', true );<br /> },<br /> <br /> up: function ( evt ) {<br /> return this.show( evt, 'parentcat' );<br /> },<br /> <br /> cancel: function () {<br /> if ( this.isAddCategory &amp;&amp; !onUpload ) {<br /> this.removeEditor(); // We added a new adder when opening<br /> return;<br /> }<br /> // Close, re-display link<br /> this.inactivate();<br /> this.form.style.display = 'none';<br /> if ( this.catLink ) this.catLink.style.display = '';<br /> <br /> this.linkSpan.style.display = '';<br /> this.state = this.originalState;<br /> this.currentCategory = this.lastSavedCategory;<br /> this.currentKey = this.lastSavedKey;<br /> this.currentExists = this.lastSavedExists;<br /> this.currentHidden = this.lastSavedHidden;<br /> if ( this.catLink )<br /> if ( this.currentKey &amp;&amp; this.currentKey.length ) { this.catLink.title = this.currentKey; } else { this.catLink.title = ''; }<br /> <br /> if ( this.state === CategoryEditor.UNCHANGED ) {<br /> if ( this.catLink ) this.catLink.style.backgroundColor = 'transparent';<br /> } else {<br /> if ( !onUpload ) {<br /> try {<br /> this.catLink.style.backgroundColor = HC.bg_changed;<br /> } catch ( ex ) {}<br /> }<br /> }<br /> checkMultiInput();<br /> forceRedraw();<br /> },<br /> <br /> removeEditor: function () {<br /> if ( !newDOM ) {<br /> var next = this.span.nextSibling;<br /> if ( next ) next.parentNode.removeChild( next );<br /> }<br /> if (this.span &amp;&amp; this.span.parentNode) {<br /> this.span.parentNode.removeChild( this.span );<br /> }<br /> for ( var i = 0; i &lt; editors.length; i++ ) {<br /> if ( editors[ i ] === this ) {<br /> editors.splice( i, 1 );<br /> break;<br /> }<br /> }<br /> checkMultiInput();<br /> },<br /> <br /> rollback: function ( evt ) {<br /> this.undoLink.parentNode.removeChild( this.undoLink );<br /> this.undoLink = null;<br /> this.currentCategory = this.originalCategory;<br /> this.currentKey = this.originalKey;<br /> this.currentExists = this.originalExists;<br /> this.currentHidden = this.originalHidden;<br /> this.lastSavedCategory = this.originalCategory;<br /> this.lastSavedKey = this.originalKey;<br /> this.lastSavedExists = this.originalExists;<br /> this.lastSavedHidden = this.originalHidden;<br /> this.state = CategoryEditor.UNCHANGED;<br /> if ( !this.currentCategory || !this.currentCategory.length ) {<br /> // It was a newly added category. Remove the whole editor.<br /> this.removeEditor();<br /> } else {<br /> // Redisplay the link...<br /> this.catLink.removeChild( this.catLink.firstChild );<br /> this.catLink.appendChild( make( this.currentCategory, true ) );<br /> this.catLink.href = wikiPagePath( HC.category_canonical + ':' + this.currentCategory );<br /> this.catLink.title = this.currentKey || '';<br /> this.catLink.className = this.currentExists ? '' : 'new';<br /> this.catLink.style.backgroundColor = 'transparent';<br /> if ( this.upDownLinks ) this.upDownLinks.style.display = this.currentExists ? '' : 'none';<br /> <br /> checkMultiInput();<br /> }<br /> return evtKill( evt );<br /> },<br /> <br /> inactivate: function () {<br /> if ( this.list ) this.list.style.display = 'none';<br /> <br /> if ( this.engineSelector ) this.engineSelector.style.display = 'none';<br /> <br /> this.is_active = false;<br /> },<br /> <br /> acceptCheck: function ( dontCheck ) {<br /> this.sanitizeInput();<br /> var value = this.text.value.split( '|' );<br /> var key = null;<br /> if ( value.length &gt; 1 ) key = value[ 1 ];<br /> <br /> var v = value[ 0 ].replace( /_/g, ' ' ).replace( /^\s+|\s+$/g, '' );<br /> if ( HC.capitalizePageNames ) v = capitalize( v );<br /> <br /> this.lastInput = v;<br /> v = replaceShortcuts( v, HC.shortcuts );<br /> if ( !v.length ) {<br /> this.cancel();<br /> return false;<br /> }<br /> if ( !dontCheck &amp;&amp; (<br /> conf.wgNamespaceNumber === 14 &amp;&amp; v === conf.wgTitle || HC.blacklist &amp;&amp; HC.blacklist.test( v ) ) ) {<br /> this.cancel();<br /> return false;<br /> }<br /> this.currentCategory = v;<br /> this.currentKey = key;<br /> this.currentExists = this.inputExists;<br /> return true;<br /> },<br /> <br /> accept: function ( evt ) {<br /> // eslint-disable-next-line no-bitwise<br /> this.noCommit = ( evtKeys( evt ) &amp; 1 ) !== 0;<br /> var result = evtKill( evt );<br /> if ( this.acceptCheck() ) {<br /> var toResolve = [ this ];<br /> var original = this.currentCategory;<br /> resolveMulti( toResolve, function ( resolved ) {<br /> if ( resolved[ 0 ].dab ) {<br /> showDab( resolved[ 0 ] );<br /> } else {<br /> if ( resolved[ 0 ].acceptCheck( true ) ) {<br /> resolved[ 0 ].commit(<br /> ( resolved[ 0 ].currentCategory !== original ) ?<br /> HC.messages.cat_resolved.replace( /\$1/g, original ) :<br /> null );<br /> }<br /> }<br /> } );<br /> }<br /> return result;<br /> },<br /> <br /> close: function () {<br /> if ( !this.catLink ) {<br /> // Create a catLink<br /> this.catLink = make( 'a' );<br /> this.catLink.appendChild( make( 'foo', true ) );<br /> this.catLink.style.display = 'none';<br /> this.span.insertBefore( this.catLink, this.span.firstChild.nextSibling );<br /> }<br /> this.catLink.removeChild( this.catLink.firstChild );<br /> this.catLink.appendChild( make( this.currentCategory, true ) );<br /> this.catLink.href = wikiPagePath( HC.category_canonical + ':' + this.currentCategory );<br /> this.catLink.className = this.currentExists ? '' : 'new';<br /> this.lastSavedCategory = this.currentCategory;<br /> this.lastSavedKey = this.currentKey;<br /> this.lastSavedExists = this.currentExists;<br /> this.lastSavedHidden = this.currentHidden;<br /> // Close form and redisplay category<br /> this.inactivate();<br /> this.form.style.display = 'none';<br /> this.catLink.title = this.currentKey || '';<br /> this.catLink.style.display = '';<br /> if ( this.isAddCategory ) {<br /> if ( onUpload &amp;&amp; this.line ) {<br /> // eslint-disable-next-line no-new<br /> new CategoryEditor( this.line, null, this.span, true ); // Create a new one<br /> }<br /> this.isAddCategory = false;<br /> this.linkSpan.parentNode.removeChild( this.linkSpan );<br /> this.makeLinkSpan();<br /> this.span.appendChild( this.linkSpan );<br /> }<br /> if ( !this.undoLink ) {<br /> // Append an undo link.<br /> var span = make( 'span' );<br /> var lk = make( 'a' );<br /> lk.href = '#catlinks';<br /> lk.onclick = this.rollback.bind( this );<br /> lk.appendChild( make( HC.links.undo, true ) );<br /> lk.title = HC.tooltips.undo;<br /> span.appendChild( make( ' ', true ) );<br /> span.appendChild( lk );<br /> this.normalLinks.appendChild( span );<br /> this.undoLink = span;<br /> if ( !onUpload ) {<br /> try {<br /> this.catLink.style.backgroundColor = HC.bg_changed;<br /> } catch ( ex ) {}<br /> }<br /> }<br /> if ( this.upDownLinks ) this.upDownLinks.style.display = this.lastSavedExists ? '' : 'none';<br /> <br /> this.linkSpan.style.display = '';<br /> this.state = CategoryEditor.CHANGED;<br /> checkMultiInput();<br /> forceRedraw();<br /> },<br /> <br /> commit: function () {<br /> // Check again to catch problem cases after redirect resolution<br /> if (<br /> (<br /> this.currentCategory === this.originalCategory &amp;&amp;<br /> (<br /> this.currentKey === this.originalKey ||<br /> this.currentKey === null &amp;&amp; !this.originalKey.length<br /> )<br /> ) ||<br /> conf.wgNamespaceNumber === 14 &amp;&amp; this.currentCategory === conf.wgTitle ||<br /> HC.blacklist &amp;&amp; HC.blacklist.test( this.currentCategory )<br /> ) {<br /> this.cancel();<br /> return;<br /> }<br /> this.close();<br /> if ( !commitButton &amp;&amp; !onUpload ) {<br /> var self = this;<br /> initiateEdit( function ( failure ) {<br /> performChanges( failure, self );<br /> }, function ( msg ) {<br /> alert( msg );<br /> } );<br /> }<br /> },<br /> <br /> remove: function ( evt ) {<br /> // eslint-disable-next-line no-bitwise<br /> this.doRemove( evtKeys( evt ) &amp; 1 );<br /> return evtKill( evt );<br /> },<br /> <br /> doRemove: function ( noCommit ) {<br /> if ( this.isAddCategory ) { // Empty input on adding a new category<br /> this.cancel();<br /> return;<br /> }<br /> if ( !commitButton &amp;&amp; !onUpload ) {<br /> for ( var i = 0; i &lt; editors.length; i++ ) {<br /> if ( editors[ i ].state !== CategoryEditor.UNCHANGED ) {<br /> setMultiInput();<br /> break;<br /> }<br /> }<br /> }<br /> if ( commitButton ) {<br /> this.catLink.title = '';<br /> this.catLink.style.cssText += '; text-decoration : line-through !important;';<br /> try {<br /> this.catLink.style.backgroundColor = HC.bg_changed;<br /> } catch ( ex ) {}<br /> this.originalState = this.state;<br /> this.state = CategoryEditor.DELETED;<br /> this.normalLinks.style.display = 'none';<br /> this.undelLink.style.display = '';<br /> checkMultiInput();<br /> } else {<br /> if ( onUpload ) {<br /> // Remove this editor completely<br /> this.removeEditor();<br /> } else {<br /> this.originalState = this.state;<br /> this.state = CategoryEditor.DELETED;<br /> this.noCommit = noCommit || HC.del_needs_diff;<br /> var self = this;<br /> initiateEdit(<br /> function ( failure ) {<br /> performChanges( failure, self );<br /> },<br /> function ( msg ) {<br /> self.state = self.originalState;<br /> alert( msg );<br /> } );<br /> }<br /> }<br /> },<br /> <br /> restore: function ( evt ) {<br /> // Can occur only if we do have a commit button and are not on the upload form<br /> this.catLink.title = this.currentKey || '';<br /> this.catLink.style.textDecoration = '';<br /> this.state = this.originalState;<br /> if ( this.state === CategoryEditor.UNCHANGED ) {<br /> this.catLink.style.backgroundColor = 'transparent';<br /> } else {<br /> try {<br /> this.catLink.style.backgroundColor = HC.bg_changed;<br /> } catch ( ex ) {}<br /> }<br /> this.normalLinks.style.display = '';<br /> this.undelLink.style.display = 'none';<br /> checkMultiInput();<br /> return evtKill( evt );<br /> },<br /> <br /> // Internal operations<br /> <br /> selectEngine: function ( engineName ) {<br /> if ( !this.engineSelector ) return;<br /> for ( var i = 0; i &lt; this.engineSelector.options.length; i++ ) this.engineSelector.options[ i ].selected = this.engineSelector.options[ i ].value === engineName;<br /> },<br /> <br /> sanitizeInput: function () {<br /> var v = this.text.value || '';<br /> v = v.replace( /^(\s|_)+/, '' ); // Trim leading blanks and underscores<br /> var re = new RegExp( '^(' + HC.category_regexp + '):' );<br /> if ( re.test( v ) ) v = v.substring( v.indexOf( ':' ) + 1 ).replace( /^(\s|_)+/, '' );<br /> v = v.replace(/\u200E$/, ''); // Trim ending left-to-right mark<br /> if ( HC.capitalizePageNames ) v = capitalize( v );<br /> <br /> // Only update the input field if there is a difference. Various browsers otherwise<br /> // reset the selection and cursor position after each value re-assignment.<br /> if ( this.text.value !== null &amp;&amp; this.text.value !== v ) this.text.value = v;<br /> },<br /> <br /> makeCall: function ( url, callbackObj, engine, queryKey, cleanKey ) {<br /> var cb = callbackObj,<br /> e = engine,<br /> v = queryKey,<br /> z = cleanKey,<br /> thisObj = this;<br /> <br /> function done() {<br /> cb.callsMade++;<br /> if ( cb.callsMade === cb.nofCalls ) {<br /> if ( cb.exists ) cb.allTitles.exists = true;<br /> <br /> if ( cb.normalized ) cb.allTitles.normalized = cb.normalized;<br /> <br /> if ( !cb.dontCache &amp;&amp; !suggestionConfigs[ cb.engineName ].cache[ z ] ) suggestionConfigs[ cb.engineName ].cache[ z ] = cb.allTitles;<br /> <br /> thisObj.text.readOnly = false;<br /> if ( !cb.cancelled ) thisObj.showSuggestions( cb.allTitles, cb.noCompletion, v, cb.engineName );<br /> <br /> if ( cb === thisObj.callbackObj ) thisObj.callbackObj = null;<br /> <br /> cb = undefined;<br /> }<br /> }<br /> <br /> $.getJSON( url, function ( json ) {<br /> var titles = e.handler( json, z );<br /> if ( titles &amp;&amp; titles.length ) {<br /> if ( cb.allTitles === null ) cb.allTitles = titles; else cb.allTitles = cb.allTitles.concat( titles );<br /> if ( titles.exists ) cb.exists = true;<br /> if ( titles.normalized ) cb.normalized = titles.normalized;<br /> }<br /> done();<br /> } ).fail( function ( req ) {<br /> if ( !req ) noSuggestions = true;<br /> cb.dontCache = true;<br /> done();<br /> } );<br /> },<br /> <br /> callbackObj: null,<br /> <br /> textchange: function ( dont_autocomplete, force ) {<br /> // Hide all other lists<br /> makeActive( this );<br /> // Get input value, omit sort key, if any<br /> this.sanitizeInput();<br /> var v = this.text.value;<br /> // Disregard anything after a pipe.<br /> var pipe = v.indexOf( '|' );<br /> if ( pipe &gt;= 0 ) {<br /> this.currentKey = v.substring( pipe + 1 );<br /> v = v.substring( 0, pipe );<br /> } else {<br /> this.currentKey = null;<br /> }<br /> if ( this.lastInput === v &amp;&amp; !force ) return; // No change<br /> if ( this.lastInput !== v ) checkMultiInput();<br /> <br /> this.lastInput = v;<br /> this.lastRealInput = v;<br /> <br /> // Mark blacklisted inputs.<br /> this.ok.disabled = v.length &amp;&amp; HC.blacklist &amp;&amp; HC.blacklist.test( v );<br /> <br /> if ( noSuggestions ) {<br /> // No Ajax: just make sure the list is hidden<br /> if ( this.list ) this.list.style.display = 'none';<br /> if ( this.engineSelector ) this.engineSelector.style.display = 'none';<br /> if ( this.icon ) this.icon.style.display = 'none';<br /> return;<br /> }<br /> <br /> if ( !v.length ) {<br /> this.showSuggestions( [] );<br /> return;<br /> }<br /> var cleanKey = v.replace( /[\u200E\u200F\u202A-\u202E]/g, '' ).replace( wikiTextBlankRE, ' ' );<br /> cleanKey = replaceShortcuts( cleanKey, HC.shortcuts );<br /> cleanKey = cleanKey.replace( /^\s+|\s+$/g, '' );<br /> if ( !cleanKey.length ) {<br /> this.showSuggestions( [] );<br /> return;<br /> }<br /> <br /> if ( this.callbackObj ) this.callbackObj.cancelled = true;<br /> <br /> var engineName = suggestionConfigs[ this.engine ] ? this.engine : 'combined';<br /> <br /> dont_autocomplete = dont_autocomplete || suggestionConfigs[ engineName ].noCompletion;<br /> if ( suggestionConfigs[ engineName ].cache[ cleanKey ] ) {<br /> this.showSuggestions( suggestionConfigs[ engineName ].cache[ cleanKey ], dont_autocomplete, v, engineName );<br /> return;<br /> }<br /> <br /> var engines = suggestionConfigs[ engineName ].engines;<br /> this.callbackObj = {<br /> allTitles: null,<br /> callsMade: 0,<br /> nofCalls: engines.length,<br /> noCompletion: dont_autocomplete,<br /> engineName: engineName<br /> };<br /> this.makeCalls( engines, this.callbackObj, v, cleanKey );<br /> },<br /> <br /> makeCalls: function ( engines, cb, v, cleanKey ) {<br /> for ( var j = 0; j &lt; engines.length; j++ ) {<br /> var engine = suggestionEngines[ engines[ j ] ];<br /> var url = conf.wgServer + conf.wgScriptPath + engine.uri.replace( /\$1/g, encodeURIComponent( cleanKey ) );<br /> this.makeCall( url, cb, engine, v, cleanKey );<br /> }<br /> },<br /> <br /> showSuggestions: function ( titles, dontAutocomplete, queryKey, engineName ) {<br /> this.text.readOnly = false;<br /> this.dab = null;<br /> this.showsList = false;<br /> if ( !this.list ) return;<br /> if ( noSuggestions ) {<br /> if ( this.list ) this.list.style.display = 'none';<br /> <br /> if ( this.engineSelector ) this.engineSelector.style.display = 'none';<br /> <br /> if ( this.icon ) this.icon.style.display = 'none';<br /> <br /> this.inputExists = true; // Default...<br /> return;<br /> }<br /> this.engineName = engineName;<br /> if ( engineName ) {<br /> if ( !this.engineSelector ) this.engineName = null;<br /> } else {<br /> if ( this.engineSelector ) this.engineSelector.style.display = 'none';<br /> }<br /> if ( queryKey ) {<br /> if ( this.lastInput.indexOf( queryKey ) ) return;<br /> if ( this.lastQuery &amp;&amp; this.lastInput.indexOf( this.lastQuery ) === 0 &amp;&amp; this.lastQuery.length &gt; queryKey.length ) return;<br /> }<br /> this.lastQuery = queryKey;<br /> <br /> // Get current input text<br /> var v = this.text.value.split( '|' );<br /> var key = v.length &gt; 1 ? '|' + v[ 1 ] : '';<br /> v = ( HC.capitalizePageNames ? capitalize( v[ 0 ] ) : v[ 0 ] );<br /> var vNormalized = v;<br /> var knownToExist = titles &amp;&amp; titles.exists;<br /> var i;<br /> if ( titles ) {<br /> if ( titles.normalized &amp;&amp; v.indexOf( queryKey ) === 0 ) {<br /> // We got back a different normalization than what is in the input field<br /> vNormalized = titles.normalized + v.substring( queryKey.length );<br /> }<br /> var vLow = vNormalized.toLowerCase();<br /> // Strip blacklisted categories<br /> if ( HC.blacklist ) {<br /> for ( i = 0; i &lt; titles.length; i++ ) {<br /> if ( HC.blacklist.test( titles[ i ] ) ) {<br /> titles.splice( i, 1 );<br /> i--;<br /> }<br /> }<br /> }<br /> titles.sort(<br /> function ( a, b ) {<br /> if ( a === b ) return 0;<br /> <br /> if ( a.indexOf( b ) === 0 ) return 1;<br /> // a begins with b: a &gt; b<br /> if ( b.indexOf( a ) === 0 ) return -1;<br /> // b begins with a: a &lt; b<br /> // Opensearch may return stuff not beginning with the search prefix!<br /> var prefixMatchA = ( a.indexOf( vNormalized ) === 0 ? 1 : 0 );<br /> var prefixMatchB = ( b.indexOf( vNormalized ) === 0 ? 1 : 0 );<br /> if ( prefixMatchA !== prefixMatchB ) return prefixMatchB - prefixMatchA;<br /> <br /> // Case-insensitive prefix match!<br /> var aLow = a.toLowerCase(),<br /> bLow = b.toLowerCase();<br /> prefixMatchA = ( aLow.indexOf( vLow ) === 0 ? 1 : 0 );<br /> prefixMatchB = ( bLow.indexOf( vLow ) === 0 ? 1 : 0 );<br /> if ( prefixMatchA !== prefixMatchB ) return prefixMatchB - prefixMatchA;<br /> <br /> if ( a &lt; b ) return -1;<br /> <br /> if ( b &lt; a ) return 1;<br /> <br /> return 0;<br /> } );<br /> // Remove duplicates and self-references<br /> for ( i = 0; i &lt; titles.length; i++ ) {<br /> if (<br /> i + 1 &lt; titles.length &amp;&amp; titles[ i ] === titles[ i + 1 ] ||<br /> conf.wgNamespaceNumber === 14 &amp;&amp; titles[ i ] === conf.wgTitle<br /> ) {<br /> titles.splice( i, 1 );<br /> i--;<br /> }<br /> }<br /> }<br /> if ( !titles || !titles.length ) {<br /> if ( this.list ) this.list.style.display = 'none';<br /> <br /> if ( this.engineSelector ) this.engineSelector.style.display = 'none';<br /> <br /> if ( engineName &amp;&amp; suggestionConfigs[ engineName ] &amp;&amp; !suggestionConfigs[ engineName ].temp ) {<br /> if ( this.icon ) this.icon.src = HC.existsNo;<br /> <br /> this.inputExists = false;<br /> }<br /> return;<br /> }<br /> <br /> var firstTitle = titles[ 0 ];<br /> var completed = this.autoComplete( firstTitle, v, vNormalized, key, dontAutocomplete );<br /> var existing = completed || knownToExist || firstTitle === replaceShortcuts( v, HC.shortcuts );<br /> if ( engineName &amp;&amp; suggestionConfigs[ engineName ] &amp;&amp; !suggestionConfigs[ engineName ].temp ) {<br /> this.icon.src = ( existing ? HC.existsYes : HC.existsNo );<br /> this.inputExists = existing;<br /> }<br /> if ( completed ) {<br /> this.lastInput = firstTitle;<br /> if ( titles.length === 1 ) {<br /> this.list.style.display = 'none';<br /> if ( this.engineSelector ) this.engineSelector.style.display = 'none';<br /> <br /> return;<br /> }<br /> }<br /> // (Re-)fill the list<br /> while ( this.list.firstChild ) this.list.removeChild( this.list.firstChild );<br /> <br /> for ( i = 0; i &lt; titles.length; i++ ) {<br /> var opt = make( 'option' );<br /> opt.appendChild( make( titles[ i ], true ) );<br /> opt.selected = completed &amp;&amp; ( i === 0 );<br /> this.list.appendChild( opt );<br /> }<br /> this.displayList();<br /> },<br /> <br /> displayList: function () {<br /> this.showsList = true;<br /> if ( !this.is_active ) {<br /> this.list.style.display = 'none';<br /> if ( this.engineSelector ) this.engineSelector.style.display = 'none';<br /> <br /> return;<br /> }<br /> var nofItems = ( this.list.options.length &gt; HC.listSize ? HC.listSize : this.list.options.length );<br /> if ( nofItems &lt;= 1 ) nofItems = 2;<br /> <br /> this.list.size = nofItems;<br /> this.list.style.align = is_rtl ? 'right' : 'left';<br /> this.list.style.zIndex = 5;<br /> this.list.style.position = 'absolute';<br /> // Compute initial list position. First the height.<br /> var anchor = is_rtl ? 'right' : 'left';<br /> var listh = 0;<br /> if ( this.list.style.display === 'none' ) {<br /> // Off-screen display to get the height<br /> this.list.style.top = this.text.offsetTop + 'px';<br /> this.list.style[ anchor ] = '-10000px';<br /> this.list.style.display = '';<br /> listh = this.list.offsetHeight;<br /> this.list.style.display = 'none';<br /> } else {<br /> listh = this.list.offsetHeight;<br /> }<br /> // Approximate calculation of maximum list size<br /> var maxListHeight = listh;<br /> if ( nofItems &lt; HC.listSize ) maxListHeight = ( listh / nofItems ) * HC.listSize;<br /> <br /> function viewport( what ) {<br /> if ( is_webkit &amp;&amp; !document.evaluate ) {<br /> // Safari &lt; 3.0<br /> return window[ 'inner' + what ];<br /> }<br /> var s = 'client' + what;<br /> if ( window.opera ) return document.body[ s ];<br /> <br /> return ( document.documentElement ? document.documentElement[ s ] : 0 ) || document.body[ s ] || 0;<br /> }<br /> function scroll_offset( what ) {<br /> var s = 'scroll' + what;<br /> var result = ( document.documentElement ? document.documentElement[ s ] : 0 ) || document.body[ s ] || 0;<br /> if ( is_rtl &amp;&amp; what === 'Left' ) {<br /> // RTL inconsistencies.<br /> // FF: 0 at the far right, then increasingly negative values.<br /> // IE &gt;= 8: 0 at the far right, then increasingly positive values.<br /> // Webkit: scrollWidth - clientWidth at the far right, then down to zero.<br /> // Opera: don't know...<br /> if ( result &lt; 0 ) result = -result;<br /> <br /> if ( !is_webkit ) result = scroll_offset( 'Width' ) - viewport( 'Width' ) - result;<br /> <br /> // Now all have webkit behavior, i.e. zero if at the leftmost edge.<br /> }<br /> return result;<br /> }<br /> function position( node ) {<br /> // Stripped-down simplified position function. It's good enough for our purposes.<br /> if ( node.getBoundingClientRect ) {<br /> var box = node.getBoundingClientRect();<br /> return {<br /> x: Math.round( box.left + scroll_offset( 'Left' ) ),<br /> y: Math.round( box.top + scroll_offset( 'Top' ) )<br /> };<br /> }<br /> var t = 0,<br /> l = 0;<br /> do {<br /> t += ( node.offsetTop || 0 );<br /> l += ( node.offsetLeft || 0 );<br /> node = node.offsetParent;<br /> } while ( node );<br /> return {<br /> x: l,<br /> y: t<br /> };<br /> }<br /> <br /> var textPos = position( this.text ),<br /> nl = 0,<br /> nt = 0,<br /> offset = 0,<br /> // Opera 9.5 somehow has offsetWidth = 0 here?? Use the next best value...<br /> textBoxWidth = this.text.offsetWidth || this.text.clientWidth;<br /> if ( this.engineName ) {<br /> this.engineSelector.style.zIndex = 5;<br /> this.engineSelector.style.position = 'absolute';<br /> this.engineSelector.style.width = textBoxWidth + 'px';<br /> // Figure out the height of this selector: display it off-screen, then hide it again.<br /> if ( this.engineSelector.style.display === 'none' ) {<br /> this.engineSelector.style[ anchor ] = '-10000px';<br /> this.engineSelector.style.top = '0';<br /> this.engineSelector.style.display = '';<br /> offset = this.engineSelector.offsetHeight;<br /> this.engineSelector.style.display = 'none';<br /> } else {<br /> offset = this.engineSelector.offsetHeight;<br /> }<br /> this.engineSelector.style[ anchor ] = nl + 'px';<br /> }<br /> if ( textPos.y &lt; maxListHeight + offset + 1 ) {<br /> // The list might extend beyond the upper border of the page. Let's avoid that by placing it<br /> // below the input text field.<br /> nt = this.text.offsetHeight + offset + 1;<br /> if ( this.engineName ) this.engineSelector.style.top = this.text.offsetHeight + 'px';<br /> } else {<br /> nt = -listh - offset - 1;<br /> if ( this.engineName ) this.engineSelector.style.top = -( offset + 1 ) + 'px';<br /> }<br /> this.list.style.top = nt + 'px';<br /> this.list.style.width = ''; // No fixed width (yet)<br /> this.list.style[ anchor ] = nl + 'px';<br /> if ( this.engineName ) {<br /> this.selectEngine( this.engineName );<br /> this.engineSelector.style.display = '';<br /> }<br /> this.list.style.display = 'block';<br /> // Set the width of the list<br /> if ( this.list.offsetWidth &lt; textBoxWidth ) {<br /> this.list.style.width = textBoxWidth + 'px';<br /> return;<br /> }<br /> // If the list is wider than the textbox: make sure it fits horizontally into the browser window<br /> var scroll = scroll_offset( 'Left' );<br /> var view_w = viewport( 'Width' );<br /> var w = this.list.offsetWidth;<br /> var l_pos = position( this.list );<br /> var left = l_pos.x;<br /> var right = left + w;<br /> if ( left &lt; scroll || right &gt; scroll + view_w ) {<br /> if ( w &gt; view_w ) {<br /> w = view_w;<br /> this.list.style.width = w + 'px';<br /> if ( is_rtl ) left = right - w; else right = left + w;<br /> }<br /> var relative_offset = 0;<br /> if ( left &lt; scroll ) relative_offset = scroll - left; else if ( right &gt; scroll + view_w ) relative_offset = -( right - scroll - view_w );<br /> <br /> if ( is_rtl ) relative_offset = -relative_offset;<br /> <br /> if ( relative_offset ) this.list.style[ anchor ] = ( nl + relative_offset ) + 'px';<br /> }<br /> },<br /> <br /> autoComplete: function ( newVal, actVal, normalizedActVal, key, dontModify ) {<br /> if ( newVal === actVal ) return true;<br /> <br /> if ( dontModify || this.ime || !this.canSelect() ) return false;<br /> <br /> // If we can't select properly or an IME composition is ongoing, autocompletion would be a major annoyance to the user.<br /> if ( newVal.indexOf( actVal ) ) {<br /> // Maybe it'll work with the normalized value (NFC)?<br /> if ( normalizedActVal &amp;&amp; newVal.indexOf( normalizedActVal ) === 0 ) {<br /> if ( this.lastRealInput === actVal ) this.lastRealInput = normalizedActVal;<br /> <br /> actVal = normalizedActVal;<br /> } else {<br /> return false;<br /> }<br /> }<br /> // Actual input is a prefix of the new text. Fill in new text, selecting the newly added suffix<br /> // such that it can be easily removed by typing backspace if the suggestion is unwanted.<br /> this.text.focus();<br /> this.text.value = newVal + key;<br /> this.setSelection( actVal.length, newVal.length );<br /> return true;<br /> },<br /> <br /> canSelect: function () {<br /> return this.text.setSelectionRange ||<br /> this.text.createTextRange ||<br /> this.text.selectionStart !== undefined &amp;&amp;<br /> this.text.selectionEnd !== undefined;<br /> },<br /> <br /> setSelection: function ( from, to ) {<br /> // this.text must be focused (at least on IE)<br /> if ( !this.text.value ) return;<br /> if ( this.text.setSelectionRange ) { // e.g. khtml<br /> this.text.setSelectionRange( from, to );<br /> } else if ( this.text.selectionStart !== undefined ) {<br /> if ( from &gt; this.text.selectionStart ) {<br /> this.text.selectionEnd = to;<br /> this.text.selectionStart = from;<br /> } else {<br /> this.text.selectionStart = from;<br /> this.text.selectionEnd = to;<br /> }<br /> } else if ( this.text.createTextRange ) { // IE<br /> var new_selection = this.text.createTextRange();<br /> new_selection.move( 'character', from );<br /> new_selection.moveEnd( 'character', to - from );<br /> new_selection.select();<br /> }<br /> },<br /> <br /> getSelection: function () {<br /> var from = 0,<br /> to = 0;<br /> // this.text must be focused (at least on IE)<br /> if ( !this.text.value ) {<br /> // No text.<br /> } else if ( this.text.selectionStart !== undefined ) {<br /> from = this.text.selectionStart;<br /> to = this.text.selectionEnd;<br /> } else if ( document.selection &amp;&amp; document.selection.createRange ) { // IE<br /> var rng = document.selection.createRange().duplicate();<br /> if ( rng.parentElement() === this.text ) {<br /> try {<br /> var textRng = this.text.createTextRange();<br /> textRng.move( 'character', 0 );<br /> textRng.setEndPoint( 'EndToEnd', rng );<br /> // We're in a single-line input box: no need to care about IE's strange<br /> // handling of line ends<br /> to = textRng.text.length;<br /> textRng.setEndPoint( 'EndToStart', rng );<br /> from = textRng.text.length;<br /> } catch ( notFocused ) {<br /> from = this.text.value.length;<br /> to = from; // At end of text<br /> }<br /> }<br /> }<br /> return {<br /> start: from,<br /> end: to<br /> };<br /> },<br /> <br /> saveView: function () {<br /> this.lastSelection = this.getSelection();<br /> },<br /> <br /> processKey: function ( evt ) {<br /> var dir = 0;<br /> switch ( this.lastKey ) {<br /> case UP:<br /> dir = -1;<br /> break;<br /> case DOWN:<br /> dir = 1;<br /> break;<br /> case PGUP:<br /> dir = -HC.listSize;<br /> break;<br /> case PGDOWN:<br /> dir = HC.listSize;<br /> break;<br /> case ESC: // Inhibit default behavior (revert to last real input in FF: we do that ourselves)<br /> return evtKill( evt );<br /> }<br /> if ( dir ) {<br /> if ( this.list.style.display !== 'none' ) {<br /> // List is visible, so there are suggestions<br /> this.highlightSuggestion( dir );<br /> // Kill the event, otherwise some browsers (e.g., Firefox) may additionally treat an up-arrow<br /> // as &quot;place the text cursor at the front&quot;, which we don't want here.<br /> return evtKill( evt );<br /> } else if (<br /> this.keyCount &lt;= 1 &amp;&amp;<br /> ( !this.callbackObj || this.callbackObj.callsMade === this.callbackObj.nofCalls )<br /> ) {<br /> // If no suggestions displayed, get them, unless we're already getting them.<br /> this.textchange();<br /> }<br /> }<br /> return true;<br /> },<br /> <br /> highlightSuggestion: function ( dir ) {<br /> if ( noSuggestions || !this.list || this.list.style.display === 'none' ) return false;<br /> <br /> var curr = this.list.selectedIndex;<br /> var tgt = -1;<br /> if ( dir === 0 ) {<br /> if ( curr &lt; 0 || curr &gt;= this.list.options.length ) return false;<br /> <br /> tgt = curr;<br /> } else {<br /> tgt = curr &lt; 0 ? 0 : curr + dir;<br /> tgt = tgt &lt; 0 ? 0 : tgt;<br /> if ( tgt &gt;= this.list.options.length ) tgt = this.list.options.length - 1;<br /> }<br /> if ( tgt !== curr || dir === 0 ) {<br /> if ( curr &gt;= 0 &amp;&amp; curr &lt; this.list.options.length &amp;&amp; dir !== 0 ) this.list.options[ curr ].selected = false;<br /> <br /> this.list.options[ tgt ].selected = true;<br /> // Get current input text<br /> var v = this.text.value.split( '|' );<br /> var key = v.length &gt; 1 ? '|' + v[ 1 ] : '';<br /> var completed = this.autoComplete( this.list.options[ tgt ].text, this.lastRealInput, null, key, false );<br /> if ( !completed || this.list.options[ tgt ].text === this.lastRealInput ) {<br /> this.text.value = this.list.options[ tgt ].text + key;<br /> if ( this.canSelect() ) this.setSelection( this.list.options[ tgt ].text.length, this.list.options[ tgt ].text.length );<br /> }<br /> this.lastInput = this.list.options[ tgt ].text;<br /> this.inputExists = true; // Might be wrong if from a dab list...<br /> if ( this.icon ) this.icon.src = HC.existsYes;<br /> <br /> this.state = CategoryEditor.CHANGE_PENDING;<br /> }<br /> return true;<br /> },<br /> <br /> resetKeySelection: function () {<br /> if ( noSuggestions || !this.list || this.list.style.display === 'none' ) return false;<br /> <br /> var curr = this.list.selectedIndex;<br /> if ( curr &gt;= 0 &amp;&amp; curr &lt; this.list.options.length ) {<br /> this.list.options[ curr ].selected = false;<br /> // Get current input text<br /> var v = this.text.value.split( '|' );<br /> var key = v.length &gt; 1 ? '|' + v[ 1 ] : '';<br /> // ESC is handled strangely by some browsers (e.g., FF); somehow it resets the input value before<br /> // our event handlers ever get a chance to run.<br /> var result = v[ 0 ] !== this.lastInput;<br /> if ( v[ 0 ] !== this.lastRealInput ) {<br /> this.text.value = this.lastRealInput + key;<br /> result = true;<br /> }<br /> this.lastInput = this.lastRealInput;<br /> return result;<br /> }<br /> return false;<br /> }<br /> }; // end CategoryEditor.prototype<br /> <br /> function initialize() {<br /> // User configurations: Do this here, called from the onload handler, so that users can<br /> // override it easily in their own user script files by just declaring variables. JSconfig<br /> // is some feature used at Wikimedia Commons.<br /> var config = ( window.JSconfig !== undefined &amp;&amp; JSconfig.keys ) ? JSconfig.keys : {};<br /> HC.dont_add_to_watchlist = ( window.hotcat_dont_add_to_watchlist !== undefined ?<br /> !!window.hotcat_dont_add_to_watchlist :<br /> ( config.HotCatDontAddToWatchlist !== undefined ? config.HotCatDontAddToWatchlist :<br /> HC.dont_add_to_watchlist ) );<br /> HC.no_autocommit = ( window.hotcat_no_autocommit !== undefined ?<br /> !!window.hotcat_no_autocommit : ( config.HotCatNoAutoCommit !== undefined ?<br /> config.HotCatNoAutoCommit :<br /> // On talk namespace default autocommit off<br /> ( conf.wgNamespaceNumber % 2 ?<br /> true : HC.no_autocommit ) ) );<br /> HC.del_needs_diff = ( window.hotcat_del_needs_diff !== undefined ?<br /> !!window.hotcat_del_needs_diff :<br /> ( config.HotCatDelNeedsDiff !== undefined ?<br /> config.HotCatDelNeedsDiff :<br /> HC.del_needs_diff ) );<br /> HC.suggest_delay = window.hotcat_suggestion_delay || config.HotCatSuggestionDelay || HC.suggest_delay;<br /> HC.editbox_width = window.hotcat_editbox_width || config.HotCatEditBoxWidth || HC.editbox_width;<br /> HC.suggestions = window.hotcat_suggestions || config.HotCatSuggestions || HC.suggestions;<br /> if ( typeof HC.suggestions !== 'string' || !suggestionConfigs[ HC.suggestions ] ) HC.suggestions = 'combined';<br /> <br /> HC.fixed_search = ( window.hotcat_suggestions_fixed !== undefined ?<br /> !!window.hotcat_suggestions_fixed : ( config.HotCatFixedSuggestions !== undefined ?<br /> config.HotCatFixedSuggestions : HC.fixed_search ) );<br /> HC.single_minor = ( window.hotcat_single_changes_are_minor !== undefined ?<br /> !!window.hotcat_single_changes_are_minor :<br /> ( config.HotCatMinorSingleChanges !== undefined ?<br /> config.HotCatMinorSingleChanges :<br /> HC.single_minor ) );<br /> HC.bg_changed = window.hotcat_changed_background || config.HotCatChangedBackground || HC.bg_changed;<br /> HC.use_up_down = ( window.hotcat_use_category_links !== undefined ?<br /> !!window.hotcat_use_category_links :<br /> ( config.HotCatUseCategoryLinks !== undefined ?<br /> config.HotCatUseCategoryLinks :<br /> HC.use_up_down ) );<br /> HC.listSize = window.hotcat_list_size || config.HotCatListSize || HC.listSize;<br /> if ( conf.wgDBname !== 'commonswiki' ) HC.changeTag = config.HotCatChangeTag || '';<br /> <br /> // The next whole shebang is needed, because manual tags get not submitted except of save<br /> if ( HC.changeTag ) {<br /> var eForm = document.editform,<br /> catRegExp = new RegExp( '^\\[\\[(' + HC.category_regexp + '):' ),<br /> oldTxt;<br /> // Returns true if minor change<br /> var isMinorChange = function () {<br /> var newTxt = eForm.wpTextbox1;<br /> if ( !newTxt ) return;<br /> newTxt = newTxt.value;<br /> var oldLines = oldTxt.match( /^.*$/gm ),<br /> newLines = newTxt.match( /^.*$/gm ),<br /> cArr; // changes<br /> var except = function ( aArr, bArr ) {<br /> var result = [],<br /> lArr, // larger<br /> sArr; // smaller<br /> if ( aArr.length &lt; bArr.length ) {<br /> lArr = bArr;<br /> sArr = aArr;<br /> } else {<br /> lArr = aArr;<br /> sArr = bArr;<br /> }<br /> for ( var i = 0; i &lt; lArr.length; i++ ) {<br /> var item = lArr[ i ];<br /> var ind = $.inArray( item, sArr );<br /> if ( ind === -1 ) result.push( item );<br /> else sArr.splice( ind, 1 ); // don't check this item again<br /> }<br /> return result.concat( sArr );<br /> };<br /> cArr = except( oldLines, newLines );<br /> if ( cArr.length ) {<br /> cArr = $.grep( cArr, function ( c ) {<br /> c = $.trim( c );<br /> return ( c &amp;&amp; !catRegExp.test( c ) );<br /> } );<br /> }<br /> if ( !cArr.length ) {<br /> oldTxt = newTxt;<br /> return true;<br /> }<br /> };<br /> <br /> if ( conf.wgAction === 'submit' &amp;&amp; conf.wgArticleId &amp;&amp; eForm &amp;&amp; eForm.wpSummary &amp;&amp; document.getElementById( 'wikiDiff' ) ) {<br /> var sum = eForm.wpSummary,<br /> sumA = eForm.wpAutoSummary;<br /> if ( sum.value &amp;&amp; sumA.value === HC.changeTag ) { // HotCat diff<br /> // MD5 hash of the empty string, as HotCat edit is based on empty sum<br /> sumA.value = sumA.value.replace( HC.changeTag, 'd41d8cd98f00b204e9800998ecf8427e' );<br /> // Attr creation and event handling is not same in all (old) browsers so use $<br /> var $ct = $( '&lt;input type=&quot;hidden&quot; name=&quot;wpChangeTags&quot;&gt;' ).val( HC.changeTag );<br /> $( eForm ).append( $ct );<br /> oldTxt = eForm.wpTextbox1.value;<br /> $( '#wpSave' ).one( 'click', function () {<br /> if ( $ct.val() )<br /> sum.value = sum.value.replace( ( HC.messages.using || HC.messages.prefix ), '' );<br /> <br /> } );<br /> var removeChangeTag = function () {<br /> $( eForm.wpTextbox1 ).add( sum ).one( 'input', function () {<br /> window.setTimeout( function () {<br /> if ( !isMinorChange() ) $ct.val( '' );<br /> else removeChangeTag();<br /> }, 500 );<br /> } );<br /> };<br /> removeChangeTag();<br /> }<br /> }<br /> }<br /> // Numeric input, make sure we have a numeric value<br /> HC.listSize = parseInt( HC.listSize, 10 );<br /> if ( isNaN( HC.listSize ) || HC.listSize &lt; 5 ) HC.listSize = 5;<br /> <br /> HC.listSize = Math.min( HC.listSize, 30 ); // Max size<br /> <br /> // Localize search engine names<br /> if ( HC.engine_names ) {<br /> for ( var key in HC.engine_names )<br /> if ( suggestionConfigs[ key ] &amp;&amp; HC.engine_names[ key ] ) suggestionConfigs[ key ].name = HC.engine_names[ key ];<br /> <br /> }<br /> // Catch both native RTL and &quot;faked&quot; RTL through [[MediaWiki:Rtl.js]]<br /> is_rtl = hasClass( document.body, 'rtl' );<br /> if ( !is_rtl ) {<br /> if ( document.defaultView &amp;&amp; document.defaultView.getComputedStyle ) { // Gecko etc.<br /> is_rtl = document.defaultView.getComputedStyle( document.body, null ).getPropertyValue( 'direction' );<br /> } else if ( document.body.currentStyle ) { // IE, has subtle differences to getComputedStyle<br /> is_rtl = document.body.currentStyle.direction;<br /> } else { // Not exactly right, but best effort<br /> is_rtl = document.body.style.direction;<br /> }<br /> is_rtl = ( is_rtl === 'rtl' );<br /> }<br /> }<br /> <br /> function can_edit() {<br /> var container = null;<br /> switch ( mw.config.get( 'skin' ) ) {<br /> case 'cologneblue':<br /> container = document.getElementById( 'quickbar' );<br /> /* fall through */<br /> case 'standard':<br /> case 'nostalgia':<br /> if ( !container ) container = document.getElementById( 'topbar' );<br /> var lks = container.getElementsByTagName( 'a' );<br /> for ( var i = 0; i &lt; lks.length; i++ ) {<br /> if (<br /> param( 'title', lks[ i ].href ) === conf.wgPageName &amp;&amp;<br /> param( 'action', lks[ i ].href ) === 'edit'<br /> ) {<br /> return true;<br /> }<br /> }<br /> return false;<br /> default:<br /> // all modern skins:<br /> return document.getElementById( 'ca-edit' ) !== null;<br /> }<br /> }<br /> <br /> // Legacy stuff<br /> function closeForm() {<br /> // Close all open editors without redirect resolution and other asynchronous stuff.<br /> for ( var i = 0; i &lt; editors.length; i++ ) {<br /> var edit = editors[ i ];<br /> if ( edit.state === CategoryEditor.OPEN ) {<br /> edit.cancel();<br /> } else if ( edit.state === CategoryEditor.CHANGE_PENDING ) {<br /> edit.sanitizeInput();<br /> var value = edit.text.value.split( '|' );<br /> var key = null;<br /> if ( value.length &gt; 1 ) key = value[ 1 ];<br /> var v = value[ 0 ].replace( /_/g, ' ' ).replace( /^\s+|\s+$/g, '' );<br /> if ( !v.length ) {<br /> edit.cancel();<br /> } else {<br /> edit.currentCategory = v;<br /> edit.currentKey = key;<br /> edit.currentExists = this.inputExists;<br /> edit.close();<br /> }<br /> }<br /> }<br /> }<br /> <br /> function setup_upload() {<br /> onUpload = true;<br /> // Add an empty category bar at the end of the table containing the description, and change the onsubmit handler.<br /> var ip = document.getElementById( 'mw-htmlform-description' ) || document.getElementById( 'wpDestFile' );<br /> if ( !ip ) {<br /> ip = document.getElementById( 'wpDestFile' );<br /> while ( ip &amp;&amp; ip.nodeName.toLowerCase() !== 'table' ) ip = ip.parentNode;<br /> }<br /> if ( !ip ) return;<br /> var reupload = document.getElementById( 'wpForReUpload' );<br /> var destFile = document.getElementById( 'wpDestFile' );<br /> if (<br /> ( reupload &amp;&amp; !!reupload.value ) ||<br /> ( destFile &amp;&amp; ( destFile.disabled || destFile.readOnly ) )<br /> ) {<br /> return; // re-upload form...<br /> }<br /> // Insert a table row with two fields (label and empty category bar)<br /> var labelCell = make( 'td' );<br /> var lineCell = make( 'td' );<br /> // Create the category line<br /> catLine = make( 'div' );<br /> catLine.className = 'catlinks';<br /> catLine.id = 'catlinks';<br /> catLine.style.textAlign = is_rtl ? 'right' : 'left';<br /> // We'll be inside a table row. Make sure that we don't have margins or strange borders.<br /> catLine.style.margin = '0';<br /> catLine.style.border = 'none';<br /> lineCell.appendChild( catLine );<br /> // Create the label<br /> var label = null;<br /> if ( window.UFUI &amp;&amp; window.UIElements &amp;&amp; UFUI.getLabel instanceof Function ) {<br /> try {<br /> label = UFUI.getLabel( 'wpCategoriesUploadLbl' );<br /> } catch ( ex ) {<br /> label = null;<br /> }<br /> }<br /> if ( !label ) {<br /> labelCell.id = 'hotcatLabel';<br /> labelCell.appendChild( make( HC.categories, true ) );<br /> } else {<br /> labelCell.id = 'hotcatLabelTranslated';<br /> labelCell.appendChild( label );<br /> }<br /> labelCell.className = 'mw-label';<br /> labelCell.style.textAlign = 'right';<br /> labelCell.style.verticalAlign = 'middle';<br /> // Change the onsubmit handler<br /> var form = document.getElementById( 'upload' ) || document.getElementById( 'mw-upload-form' );<br /> if ( form ) {<br /> var newRow = ip.insertRow( -1 );<br /> newRow.appendChild( labelCell );<br /> newRow.appendChild( lineCell );<br /> form.onsubmit = ( function ( oldSubmit ) {<br /> return function () {<br /> var do_submit = true;<br /> if ( oldSubmit ) {<br /> if ( typeof oldSubmit === 'string' ) {<br /> // eslint-disable-next-line no-eval<br /> do_submit = eval( oldSubmit );<br /> } else if ( oldSubmit instanceof Function ) {<br /> do_submit = oldSubmit.apply( form, arguments );<br /> }<br /> }<br /> if ( !do_submit ) return false;<br /> closeForm();<br /> // Copy the categories<br /> var eb = document.getElementById( 'wpUploadDescription' ) || document.getElementById( 'wpDesc' );<br /> var addedOne = false;<br /> for ( var i = 0; i &lt; editors.length; i++ ) {<br /> var t = editors[ i ].currentCategory;<br /> if ( !t ) continue;<br /> var key = editors[ i ].currentKey;<br /> var new_cat = '[[' + HC.category_canonical + ':' + t + ( key ? '|' + key : '' ) + ']]';<br /> // Only add if not already present<br /> var cleanedText = eb.value<br /> .replace( /&lt;!--(\s|\S)*?--&gt;/g, '' )<br /> .replace( /&lt;nowiki&gt;(\s|\S)*?&lt;\/nowiki&gt;/g, '' );<br /> if ( !find_category( cleanedText, t, true ) ) {<br /> eb.value += '\n' + new_cat;<br /> addedOne = true;<br /> }<br /> }<br /> if ( addedOne ) {<br /> // Remove &quot;subst:unc&quot; added by Flinfo if it didn't find categories<br /> eb.value = eb.value.replace( /\{\{subst:unc\}\}/g, '' );<br /> }<br /> return true;<br /> };<br /> }( form.onsubmit ) );<br /> }<br /> }<br /> <br /> var cleanedText = null;<br /> <br /> function isOnPage( span ) {<br /> if ( span.firstChild.nodeType !== Node.ELEMENT_NODE ) return null;<br /> <br /> var catTitle = title( span.firstChild.getAttribute( 'href' ) );<br /> if ( !catTitle ) return null;<br /> <br /> catTitle = catTitle.substr( catTitle.indexOf( ':' ) + 1 ).replace( /_/g, ' ' );<br /> if ( HC.blacklist &amp;&amp; HC.blacklist.test( catTitle ) ) return null;<br /> <br /> var result = {<br /> title: catTitle,<br /> match: [ '', '', '' ]<br /> };<br /> if ( pageText === null ) return result;<br /> <br /> if ( cleanedText === null ) {<br /> cleanedText = pageText<br /> .replace( /&lt;!--(\s|\S)*?--&gt;/g, '' )<br /> .replace( /&lt;nowiki&gt;(\s|\S)*?&lt;\/nowiki&gt;/g, '' );<br /> }<br /> result.match = find_category( cleanedText, catTitle, true );<br /> return result;<br /> }<br /> <br /> var initialized = false;<br /> var setupTimeout = null;<br /> <br /> function findByClass( scope, tag, className ) {<br /> var result = $( scope ).find( tag + '.' + className );<br /> return ( result &amp;&amp; result.length ) ? result[ 0 ] : null;<br /> }<br /> <br /> function setup( additionalWork ) {<br /> if ( initialized ) return;<br /> initialized = true;<br /> if ( setupTimeout ) {<br /> window.clearTimeout( setupTimeout );<br /> setupTimeout = null;<br /> }<br /> // Find the category bar, or create an empty one if there isn't one. Then add -/+- links after<br /> // each category, and add the + link.<br /> catLine =<br /> // Special:Upload<br /> catLine ||<br /> document.getElementById( 'mw-normal-catlinks' );<br /> var hiddenCats = document.getElementById( 'mw-hidden-catlinks' );<br /> if ( !catLine ) {<br /> var footer = null;<br /> if ( !hiddenCats ) {<br /> footer = findByClass( document, 'div', 'printfooter' );<br /> if ( !footer ) return; // Don't know where to insert the category line<br /> }<br /> catLine = make( 'div' );<br /> catLine.id = 'mw-normal-catlinks';<br /> catLine.style.textAlign = is_rtl ? 'right' : 'left';<br /> // Add a label<br /> var label = make( 'a' );<br /> label.href = conf.wgArticlePath.replace( '$1', 'Special:Categories' );<br /> label.title = HC.categories;<br /> label.appendChild( make( HC.categories, true ) );<br /> catLine.appendChild( label );<br /> catLine.appendChild( make( ':', true ) );<br /> // Insert the new category line<br /> var container = ( hiddenCats ? hiddenCats.parentNode : document.getElementById( 'catlinks' ) );<br /> if ( !container ) {<br /> container = make( 'div' );<br /> container.id = 'catlinks';<br /> footer.parentNode.insertBefore( container, footer.nextSibling );<br /> }<br /> container.className = 'catlinks noprint';<br /> container.style.display = '';<br /> if ( !hiddenCats ) container.appendChild( catLine ); else container.insertBefore( catLine, hiddenCats );<br /> } // end if catLine exists<br /> if ( is_rtl ) catLine.dir = 'rtl';<br /> <br /> // Create editors for all existing categories<br /> <br /> function createEditors( line, is_hidden ) {<br /> var i;<br /> var cats = line.getElementsByTagName( 'li' );<br /> if ( cats.length ) {<br /> newDOM = true;<br /> line = cats[ 0 ].parentNode;<br /> } else {<br /> cats = line.getElementsByTagName( 'span' );<br /> }<br /> // Copy cats, otherwise it'll also magically contain our added spans as it is a live collection!<br /> var copyCats = new Array( cats.length );<br /> for ( i = 0; i &lt; cats.length; i++ ) copyCats[ i ] = cats[ i ];<br /> for ( i = 0; i &lt; copyCats.length; i++ ) {<br /> var test = isOnPage( copyCats[ i ] );<br /> if ( test !== null &amp;&amp; test.match !== null &amp;&amp; line ) {<br /> // eslint-disable-next-line no-new<br /> new CategoryEditor( line, copyCats[ i ], test.title, test.match[ 2 ], is_hidden );<br /> }<br /> }<br /> return copyCats.length ? copyCats[ copyCats.length - 1 ] : null;<br /> }<br /> <br /> var lastSpan = createEditors( catLine, false );<br /> // Create one to add a new category<br /> // eslint-disable-next-line no-new<br /> new CategoryEditor( newDOM ? catLine.getElementsByTagName( 'ul' )[ 0 ] : catLine, null, null, lastSpan !== null, false );<br /> if ( !onUpload ) {<br /> if ( pageText !== null &amp;&amp; hiddenCats ) {<br /> if ( is_rtl ) hiddenCats.dir = 'rtl';<br /> createEditors( hiddenCats, true );<br /> }<br /> // And finally add the &quot;multi-mode&quot; span. (Do this at the end, otherwise it ends up in the list above.)<br /> var enableMulti = make( 'span' );<br /> enableMulti.className = 'noprint';<br /> if ( is_rtl ) enableMulti.dir = 'rtl';<br /> catLine.insertBefore( enableMulti, catLine.firstChild.nextSibling );<br /> enableMulti.appendChild( make( '\xa0', true ) ); // nbsp<br /> multiSpan = make( 'span' );<br /> enableMulti.appendChild( multiSpan );<br /> multiSpan.innerHTML = '(&lt;a&gt;' + HC.addmulti + '&lt;/a&gt;)';<br /> var lk = multiSpan.getElementsByTagName( 'a' )[ 0 ];<br /> lk.onclick = function ( evt ) {<br /> setMultiInput();<br /> checkMultiInput();<br /> return evtKill( evt );<br /> };<br /> lk.title = HC.multi_tooltip;<br /> lk.style.cursor = 'pointer';<br /> }<br /> cleanedText = null;<br /> if ( additionalWork instanceof Function ) additionalWork();<br /> mw.hook( 'hotcat.ready' ).fire(); // Execute registered callback functions<br /> $( 'body' ).trigger( 'hotcatSetupCompleted' );<br /> }<br /> <br /> function createCommitForm() {<br /> if ( commitForm ) return;<br /> var formContainer = make( 'div' );<br /> formContainer.style.display = 'none';<br /> document.body.appendChild( formContainer );<br /> formContainer.innerHTML =<br /> '&lt;form id=&quot;hotcatCommitForm&quot; method=&quot;post&quot; enctype=&quot;multipart/form-data&quot; action=&quot;' +<br /> conf.wgScript + '?title=' + encodeURIComponent( conf.wgPageName ) + '&amp;action=submit&quot;&gt;' +<br /> '&lt;input type=&quot;hidden&quot; name=&quot;wpTextbox1&quot;&gt;' +<br /> '&lt;input type=&quot;hidden&quot; name=&quot;model&quot; value=&quot;' + conf.wgPageContentModel + '&quot;&gt;' +<br /> '&lt;input type=&quot;hidden&quot; name=&quot;format&quot; value=&quot;text/x-wiki&quot;&gt;' +<br /> '&lt;input type=&quot;hidden&quot; name=&quot;wpSummary&quot; value=&quot;&quot;&gt;' +<br /> '&lt;input type=&quot;checkbox&quot; name=&quot;wpMinoredit&quot; value=&quot;1&quot;&gt;' +<br /> '&lt;input type=&quot;checkbox&quot; name=&quot;wpWatchthis&quot; value=&quot;1&quot;&gt;' +<br /> '&lt;input type=&quot;hidden&quot; name=&quot;wpAutoSummary&quot; value=&quot;d41d8cd98f00b204e9800998ecf8427e&quot;&gt;' +<br /> '&lt;input type=&quot;hidden&quot; name=&quot;wpEdittime&quot;&gt;' +<br /> '&lt;input type=&quot;hidden&quot; name=&quot;wpStarttime&quot;&gt;' +<br /> '&lt;input type=&quot;hidden&quot; name=&quot;wpDiff&quot; value=&quot;wpDiff&quot;&gt;' +<br /> '&lt;input type=&quot;hidden&quot; name=&quot;oldid&quot; value=&quot;0&quot;&gt;' +<br /> '&lt;input type=&quot;submit&quot; name=&quot;hcCommit&quot; value=&quot;hcCommit&quot;&gt;' +<br /> '&lt;input type=&quot;hidden&quot; name=&quot;wpEditToken&quot;&gt;' +<br /> '&lt;input type=&quot;hidden&quot; name=&quot;wpUltimateParam&quot; value=&quot;1&quot;&gt;' +<br /> '&lt;input type=&quot;hidden&quot; name=&quot;wpChangeTags&quot;&gt;' +<br /> '&lt;input type=&quot;hidden&quot; value=&quot;ℳ𝒲♥𝓊𝓃𝒾𝒸ℴ𝒹ℯ&quot; name=&quot;wpUnicodeCheck&quot;&gt;' +<br /> '&lt;/form&gt;';<br /> commitForm = document.getElementById( 'hotcatCommitForm' );<br /> }<br /> <br /> function getPage() {<br /> // We know we have an article here.<br /> if ( !conf.wgArticleId ) {<br /> // Doesn't exist yet. Disable on non-existing User pages -- might be a global user page.<br /> if ( conf.wgNamespaceNumber === 2 ) return;<br /> pageText = '';<br /> pageTime = null;<br /> setup( createCommitForm );<br /> } else {<br /> var url = conf.wgServer + conf.wgScriptPath + '/api.php?format=json&amp;callback=HotCat.start&amp;action=query&amp;rawcontinue=&amp;titles=' +<br /> encodeURIComponent( conf.wgPageName ) +<br /> '&amp;prop=info%7Crevisions&amp;rvprop=content%7Ctimestamp%7Cids&amp;meta=siteinfo&amp;rvlimit=1&amp;rvstartid=' +<br /> conf.wgCurRevisionId;<br /> var s = make( 'script' );<br /> s.src = url;<br /> HC.start = function ( json ) {<br /> setPage( json );<br /> setup( createCommitForm );<br /> };<br /> document.getElementsByTagName( 'head' )[ 0 ].appendChild( s );<br /> setupTimeout = window.setTimeout( function () {<br /> setup( createCommitForm );<br /> }, 4000 ); // 4 sec, just in case getting the wikitext takes longer.<br /> }<br /> }<br /> <br /> function setState( state ) {<br /> var cats = state.split( '\n' );<br /> if ( !cats.length ) return null;<br /> <br /> if ( initialized &amp;&amp; editors.length === 1 &amp;&amp; editors[ 0 ].isAddCategory ) {<br /> // Insert new spans and create new editors for them.<br /> var newSpans = [];<br /> var before = editors.length === 1 ? editors[ 0 ].span : null;<br /> var i;<br /> for ( i = 0; i &lt; cats.length; i++ ) {<br /> if ( !cats[ i ].length ) continue;<br /> var cat = cats[ i ].split( '|' );<br /> var key = cat.length &gt; 1 ? cat[ 1 ] : null;<br /> cat = cat[ 0 ];<br /> var lk = make( 'a' );<br /> lk.href = wikiPagePath( HC.category_canonical + ':' + cat );<br /> lk.appendChild( make( cat, true ) );<br /> lk.title = cat;<br /> var span = make( 'span' );<br /> span.appendChild( lk );<br /> if ( !i ) catLine.insertBefore( make( ' ', true ), before );<br /> <br /> catLine.insertBefore( span, before );<br /> if ( before &amp;&amp; i + 1 &lt; cats.length ) parent.insertBefore( make( ' | ', true ), before );<br /> <br /> newSpans.push( {<br /> element: span,<br /> title: cat,<br /> key: key<br /> } );<br /> }<br /> // And change the last one...<br /> if ( before ) before.parentNode.insertBefore( make( ' | ', true ), before );<br /> <br /> for ( i = 0; i &lt; newSpans.length; i++ ) {<br /> // eslint-disable-next-line no-new<br /> new CategoryEditor( catLine, newSpans[ i ].element, newSpans[ i ].title, newSpans[ i ].key );<br /> }<br /> }<br /> return null;<br /> }<br /> <br /> function getState() {<br /> var result = null;<br /> for ( var i = 0; i &lt; editors.length; i++ ) {<br /> var text = editors[ i ].currentCategory;<br /> var key = editors[ i ].currentKey;<br /> if ( text &amp;&amp; text.length ) {<br /> if ( key !== null ) text += '|' + key;<br /> if ( result === null ) result = text; else result += '\n' + text;<br /> }<br /> }<br /> return result;<br /> }<br /> <br /> function really_run() {<br /> initialize();<br /> <br /> if ( !HC.upload_disabled &amp;&amp; conf.wgNamespaceNumber === -1 &amp;&amp; conf.wgCanonicalSpecialPageName === 'Upload' &amp;&amp; conf.wgUserName ) {<br /> setup_upload();<br /> setup( function () {<br /> // Check for state restoration once the setup is done otherwise, but before signalling setup completion<br /> if ( window.UploadForm &amp;&amp; UploadForm.previous_hotcat_state ) UploadForm.previous_hotcat_state = setState( UploadForm.previous_hotcat_state );<br /> } );<br /> } else {<br /> if ( !conf.wgIsArticle || conf.wgAction !== 'view' || param( 'diff' ) !== null || param( 'oldid' ) !== null || !can_edit() || HC.disable() ) return;<br /> getPage();<br /> }<br /> }<br /> <br /> function run() {<br /> if ( HC.started ) return;<br /> HC.started = true;<br /> loadTrigger.register( really_run );<br /> }<br /> <br /> // Export legacy functions<br /> window.hotcat_get_state = function () {<br /> return getState();<br /> };<br /> window.hotcat_set_state = function ( state ) {<br /> return setState( state );<br /> };<br /> window.hotcat_close_form = function () {<br /> closeForm();<br /> };<br /> HC.runWhenReady = function ( callback ) {<br /> // run user-registered code once HotCat is fully set up and ready.<br /> mw.hook( 'hotcat.ready' ).add( callback );<br /> };<br /> <br /> // Make sure we don't get conflicts with AjaxCategories (core development that should one day<br /> // replace HotCat).<br /> mw.config.set( 'disableAJAXCategories', true );<br /> <br /> // Run as soon as possible. This varies depending on MediaWiki version;<br /> // window's 'load' event is always safe, but usually we can do better than that.<br /> <br /> if ( conf.wgCanonicalSpecialPageName !== 'Upload' ) {<br /> // Reload HotCat after (VE) edits (bug T103285)<br /> mw.hook( 'postEdit' ).add( function () {<br /> // Reset HotCat in case this is a soft reload (e.g. VisualEditor edit), unless the categories<br /> // were not re-rendered and our interface is still there (e.g. DiscussionTools edit)<br /> if ( document.querySelector( '#catlinks .hotcatlink' ) ) {<br /> return;<br /> }<br /> catLine = null;<br /> editors = [];<br /> initialized = false;<br /> HC.started = false;<br /> run();<br /> } );<br /> }<br /> <br /> // We can safely trigger just after user configuration is loaded.<br /> // Use always() instead of then() to also start HotCat if the user module has problems.<br /> $.when( mw.loader.using( 'user' ), $.ready ).always( run );<br /> }( jQuery, mediaWiki ) );<br /> // &lt;/nowiki&gt;</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=MediaWiki:Gadget-InsertTranslate.js&diff=888297 2022-03-06T01:08:04Z

<p>Wilsonge: Updates for new version</p> <hr /> <div>/* wikiEditor extra group and icons for developers allowing for easy tags of code insertion into articles*/<br /> <br /> var customizeToolbar = function() {<br /> $( '#wpTextbox1' ).wikiEditor( 'addToToolbar', {<br /> 'section': 'advanced',<br /> 'groups': {<br /> 'lang': {<br /> 'label': 'Tags' // or use labelMsg for a localized label, see above<br /> }<br /> }<br /> } );<br /> <br /> $('#wpTextbox1').wikiEditor('addToToolbar', {<br /> section: 'advanced',<br /> group: 'lang',<br /> tools: {<br /> &quot;atrans&quot;: {<br /> label: 'Insert translate tags',<br /> type: 'button',<br /> icon: '/images/2/29/Translate_button.png',<br /> action: {<br /> type: 'encapsulate',<br /> options: {<br /> pre: '\u003ctranslate&gt;',<br /> peri: &quot;Text to translate&quot;,<br /> post: '\u003c\u002ftranslate&gt;'<br /> }<br /> }<br /> }<br /> }<br /> } );<br /> <br /> $('#wpTextbox1').wikiEditor('addToToolbar', {<br /> section: 'advanced',<br /> group: 'lang',<br /> tools: {<br /> &quot;alangs&quot;: {<br /> label: 'Insert language tags',<br /> type: 'button',<br /> icon: '/images/1/1e/Language_button.png',<br /> action: {<br /> type: 'encapsulate',<br /> options: {<br /> pre: '\u003cnoinclude&gt;',<br /> peri: &quot;\u003clanguages \u002f&gt;&quot;,<br /> post: '\u003c\u002fnoinclude&gt;'<br /> }<br /> }<br /> }<br /> }<br /> } );<br /> <br /> $( '#wpTextbox1' ).wikiEditor( 'addToToolbar', {<br /> section: 'advanced',<br /> group: 'lang',<br /> tools: {<br /> &quot;comment&quot;: {<br /> label: 'Comment',<br /> type: 'button',<br /> icon: '//upload.wikimedia.org/wikipedia/commons/3/37/Btn_toolbar_commentaire.png',<br /> action: {<br /> type: 'encapsulate',<br /> options: {<br /> pre: &quot;&lt;!-- &quot;,<br /> post: &quot; --&gt;&quot;<br /> }<br /> }<br /> }<br /> }<br /> } );<br /> <br /> $( '#wpTextbox1' ).wikiEditor( 'addToToolbar', {<br /> section: 'advanced',<br /> group: 'lang',<br /> tools: {<br /> &quot;comment&quot;: {<br /> label: 'Insert Category {{#translation:}}',<br /> type: 'button',<br /> icon: '/images/7/7a/Language_Icon.png',<br /> action: {<br /> type: 'encapsulate',<br /> options: {<br /> pre: &quot;{{#translation:}}&quot;,<br /> post: &quot;&quot;<br /> }<br /> }<br /> }<br /> }<br /> } );<br /> <br /> };<br /> <br /> /* Check if view is in edit mode and that the required modules are available. Then, customize the toolbar . . . */<br /> if ( [ 'edit', 'submit' ].indexOf( mw.config.get( 'wgAction' ) ) !== -1 ) {<br /> mw.loader.using( 'user.options' ).then( function () {<br /> // This can be the string &quot;0&quot; if the user disabled the preference ([[phab:T54542#555387]])<br /> if ( mw.user.options.get( 'usebetatoolbar' ) == 1 ) {<br /> $.when(<br /> mw.loader.using( 'ext.wikiEditor' ), $.ready<br /> ).then( customizeToolbar );<br /> }<br /> } );<br /> }</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=MediaWiki:Gadget-InsertCode.js&diff=888296 2022-03-06T01:07:14Z

<p>Wilsonge: Fixes for new version</p> <hr /> <div>/* wikiEditor extra group and icons for developers allowing for easy tags of code insertion into articles*/<br /> <br /> var customizeToolbar = function() {<br /> $( '#wpTextbox1' ).wikiEditor( 'addToToolbar', {<br /> 'section': 'advanced',<br /> 'groups': {<br /> 'code': {<br /> 'label': 'Insert Code' // or use labelMsg for a localized label, see above<br /> }<br /> }<br /> } );<br /> jQuery(document).ready(function ($) {<br /> $('#wpTextbox1').wikiEditor('addToToolbar', {<br /> section: 'advanced',<br /> group: 'code',<br /> tools: {<br /> buttonId: {<br /> label: 'Insert PHP code tags',<br /> type: 'button',<br /> icon: '/images/5/5d/PHP_Icon.png',<br /> action: {<br /> type: 'encapsulate',<br /> options: {<br /> pre: '&lt;source lang=&quot;php&quot;&gt;\r',<br /> peri: &quot;Insert php code here\r&quot;,<br /> post: &quot;&lt;/source&gt;&quot;<br /> }<br /> }<br /> }<br /> }<br /> });<br /> });<br /> jQuery(document).ready(function ($) {<br /> $('#wpTextbox1').wikiEditor('addToToolbar', {<br /> section: 'advanced',<br /> group: 'code',<br /> tools: {<br /> buttonId: {<br /> label: 'Insert JavaScript code tags',<br /> type: 'button',<br /> icon: '/images/f/f0/JS_editor_toolbar_icon.png',<br /> action: {<br /> type: 'encapsulate',<br /> options: {<br /> pre: '&lt;source lang=&quot;javascript&quot;&gt;\r',<br /> peri: &quot;Insert javascript code here\r&quot;,<br /> post: &quot;&lt;/source&gt;&quot;<br /> }<br /> }<br /> }<br /> }<br /> });<br /> });<br /> jQuery(document).ready(function ($) {<br /> $('#wpTextbox1').wikiEditor('addToToolbar', {<br /> section: 'advanced',<br /> group: 'code',<br /> tools: {<br /> buttonId: {<br /> label: 'Insert XML code tags',<br /> type: 'button',<br /> icon: '/images/1/10/XML_toolbar_icon.png',<br /> action: {<br /> type: 'encapsulate',<br /> options: {<br /> pre: '&lt;source lang=&quot;xml&quot;&gt;\r',<br /> peri: &quot;Insert XML code here\r&quot;,<br /> post: &quot;&lt;/source&gt;&quot;<br /> }<br /> }<br /> }<br /> }<br /> });<br /> });<br /> <br /> };<br /> <br /> /* Check if view is in edit mode and that the required modules are available. Then, customize the toolbar . . . */<br /> if ( [ 'edit', 'submit' ].indexOf( mw.config.get( 'wgAction' ) ) !== -1 ) {<br /> mw.loader.using( 'user.options' ).then( function () {<br /> // This can be the string &quot;0&quot; if the user disabled the preference ([[phab:T54542#555387]])<br /> if ( mw.user.options.get( 'usebetatoolbar' ) == 1 ) {<br /> $.when(<br /> mw.loader.using( 'ext.wikiEditor' ), $.ready<br /> ).then( customizeToolbar );<br /> }<br /> } );<br /> }</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Joomla:Release_procedure_and_checklist&diff=881080 2022-02-12T22:41:00Z

<p>Wilsonge: /* Onboarding Release Leads */</p> <hr /> <div>{{RightTOC}}<br /> <br /> This is a general procedure explanation for managing releases of Joomla! and the Joomla! Framework. This list is best suited for a [[Minor Release]] or [[Maintenance Release]], however the steps will generally apply to a [[Major Release]] as well but will require some judgement calls from the release manager and/or leadership team.<br /> <br /> There is a more formal checklist available [https://github.com/joomla/joomla-cms/blob/4.1-dev/build/release-checklist.md on GitHub] for release leads to use that is intended to complement the steps described in this page.<br /> <br /> == Issue Triage, Patch Review, Merging Patches ==<br /> The release cycle for a new software version begins immediately after the previous one is completed. In the immediate hours and days after a release, the [https://github.com/joomla/joomla-cms issue tracker] and [https://forum.joomla.org/ support forums], in close coordination with the [https://volunteers.joomla.org/teams/bug-squad Bug Squad] and [https://volunteers.joomla.org/teams/cms-release-team CMS Release Team], should be monitored for reports of potential regressions or critical bugs that would warrant a quick follow-on release to address the issue. It is generally suggested to wait 48-72 hours before resuming merging of reviewed and ready for commit pull requests to keep the release branch &quot;clean&quot; and ready for a release (note this is only a suggestion, if need be a release manager could create a branch from the release tag however this involves a bit more effort therefore this suggestion is for simplicity's sake).<br /> <br /> Throughout the release cycle, the release manager should be involved with reviewing patches and merging reviewed patches to the appropriate release branch. As of this writing (where 4.0.6 is the present release), the following branches are generally active:<br /> <br /> * &lt;tt&gt;3.10-dev&lt;/tt&gt;: This is the 3.x branch, generally only bug fixes and &quot;general&quot; maintenance work should merge to this branch.<br /> * &lt;tt&gt;4.0-dev&lt;/tt&gt;: This is the 4.0.x branch - there are no more intended releases to this branch unless required by security fixes.<br /> * &lt;tt&gt;4.1-dev&lt;/tt&gt;: This is the main release branch and is where most activity occurs, generally only bug fixes and &quot;general&quot; maintenance work should merge to this branch although minor features may be merged at the discretion of the release manager and/or leadership team. All code from 3.10-dev is merged into this branch.<br /> * &lt;tt&gt;4.2-dev&lt;/tt&gt;: This is the release branch for the next minor release (the branch's name will always be the version it represents), new features should be merged to this branch<br /> <br /> === Branch Merging ===<br /> All branches should remain in-sync and all work should be regularly merged forward. Given the above example, the following is the recommended merging workflow (in general, the suggested workflow is that 3.10-dev is merged to the current 4.x-dev branch and then through to the next minor branch):<br /> <br /> * &lt;tt&gt;3.10-dev&lt;/tt&gt; should be merged into &lt;tt&gt;4.0-dev&lt;/tt&gt;<br /> * &lt;tt&gt;4.0-dev&lt;/tt&gt; should be merged to &lt;tt&gt;4.1-dev&lt;/tt&gt;<br /> * &lt;tt&gt;4.1-dev&lt;/tt&gt; should be merged to &lt;tt&gt;4.2-dev&lt;/tt&gt;<br /> <br /> It is suggested that at least once per week branch merging occurs.<br /> <br /> == Preparing To Release ==<br /> When scheduling and preparing a release, the timeline should be communicated with the Production and Marketing &amp; Communication Department leadership so that all teams are prepared to support the release. Note that when scheduling releases, consideration should be given to holidays around the world and the impact of issuing a release near those periods considered. Helpful resources include http://interfaith-calendar.org/ and https://www.timeanddate.com/holidays/<br /> <br /> === Review Release Milestone and Blockers ===<br /> On GitHub, check the [https://github.com/joomla/joomla-cms/milestones milestone] for the release you are preparing to create and for any open items with the [https://github.com/joomla/joomla-cms/labels/release-blocker release-blocker] label. If there are remaining open items, review them to determine if they are items that should be included in the release or if they can be rescheduled to a later release.<br /> <br /> === Release Schedule ===<br /> ==== Minor Release ====<br /> Given the nature of a minor release, the following is the suggested release timeline:<br /> <br /> * Six weeks prior to planned stable release: Tag the first Beta release<br /> ** At this point the release should be considered feature complete and new features should be deferred to the next minor release<br /> * Weekly Beta releases should follow this until the Release Candidate<br /> * Two weeks prior to planned stable release: Tag the Release Candidate<br /> ** At this point the release branch(es) should remain closed for committing except for high priority bug fixes and language updates<br /> ** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the &quot;no later than&quot; time<br /> ** Inform the CMS Release Team and call out anything that you would like extra testing on<br /> * One week prior to planned stable release: If necessary, create a second Release Candidate<br /> * 2-3 days before release: Build final packages - share with CMS Release Team and do release preparation activities.<br /> * Planned release date: Tag the stable release<br /> <br /> ==== Maintenance Release ====<br /> Maintenance releases operate on a 4-6 week cycle and the following is the suggested release timeline:<br /> <br /> * 9-10 days before planned release date: Tag a Release Candidate<br /> ** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the &quot;no later than&quot; time<br /> ** Inform the CMS Release Team and call out anything that you would like extra testing on<br /> * 2-3 days before release: Build final packages - share with CMS Release Team and do release preparation activities.<br /> * Planned release date: Tag the stable release<br /> <br /> === Reviewing Release Changes ===<br /> Before tagging a release, the list of changes in the release should be reviewed by the release manager and/or leadership team. The list of changes can be found using GitHub's compare function with the URL &lt;tt&gt;https://github.com/joomla/joomla-cms/compare/&lt;version&gt;...4.1-dev&lt;/tt&gt; which will compare the changes from &lt;tt&gt;&lt;version&gt;&lt;/tt&gt; to the current 4.1-dev branch (for example, https://github.com/joomla/joomla-cms/compare/3.9.0...3.9.1-rc is the comparison from the 3.9.0 release tag to the 3.9.1-rc tag). Key purposes of this review include:<br /> <br /> * Ensuring all patches are compliant with Semantic Versioning (SemVer) (i.e. no backward compatibility breaks in minor or maintenance releases and no features in maintenance releases); SemVer violations should be cleared with the Production Department leadership<br /> * Ensuring all code revisions are compatible with Joomla's minimum supported versions (i.e. no PHP 5.4 syntax in 3.x releases where PHP 5.3 is the minimum supported version, exceptions may be made if introducing a code path and files that will only be executed on newer PHP versions)<br /> ** Joomla's testing integrations should not be relied on in full for this as there are large portions of the Joomla code base which do not have automated test coverage, and as of this writing, there is not a code linting process in place checking for potential issues<br /> * Ensuring features and &quot;significant&quot; changes are documented<br /> <br /> === Security Fixes ===<br /> From time to time, security fixes must be included in a release. Prior to every release, the release manager should check with the [https://volunteers.joomla.org/teams/security-strike-team Security Strike Team] to determine if security fixes are required, and if so ensure this is communicated to all members involved with release work (i.e. the marketing team liaison who assists with the publication of release related material). When a security release is necessary, an internal Release Candidate should be built for testing by the Security Strike Team, CMS Release Team, and [https://volunteers.joomla.org/teams/cms-maintenance-team CMS Maintenance Team] with all security patches included. These teams should also receive information about the vulnerabilities being addressed to ensure there are no regressions in the impacted areas.<br /> <br /> Note, when a security fix involves a Joomla Framework package, the Framework package should be patched first and a release created of the affected package then the CMS updated with &lt;tt&gt;composer update&lt;/tt&gt;.<br /> <br /> Sometimes security fixes are required for composer dependencies that are out of support. In such cases we fork the 3rd party dependency into https://github.com/joomla-backports and then apply security fixes there in a &lt;tt&gt;joomla-backports&lt;/tt&gt; branch (and override the [https://github.com/joomla/joomla-cms/blob/3.10.5/composer.json#L28-L32 repository in composer.json] and as well as the branch reference [https://github.com/joomla/joomla-cms/blob/3.10.5/composer.json#L54 here]. Links are a sample for PHPMailer overrides in Joomla 3.10).<br /> <br /> === Release FAQ ===<br /> Create Release FAQ Category on the Joomla Documentation site. (i.e. Clone the contents of an existing page such as [https://docs.joomla.org/Category:Version_4.0.6_FAQ FAQ] and update the version number to your required version)<br /> <br /> == Building a Release ==<br /> Building a release starts with checking that any files and folders that have been deleted are included in the arrays in the installer script at &lt;tt&gt;administrator/components/com_admin/script.php&lt;/tt&gt;. There is a helper script in the repository to assist with this located at &lt;tt&gt;build/deleted_file_check.php&lt;/tt&gt;. Running &lt;tt&gt;php build/deleted_file_check.php&lt;/tt&gt; with its required &lt;tt&gt;--from&lt;/tt&gt; option will write a file to &lt;tt&gt;build/deleted_files.txt&lt;/tt&gt; with the list of files deleted since the from reference. Please see the PHP file for all documentation about this script.<br /> <br /> The following steps require the individual to create commits and tags. It is suggested that these commits and tags be GPG signed as an extra security step but this is not a mandatory requirement as of this writing.<br /> <br /> If creating a security release, at this point you should apply all patches provided by the security team.<br /> <br /> Once it is confirmed that the deleted files listing is correct, the &lt;tt&gt;build/bump.php&lt;/tt&gt; script should be executed to set the new version number. This script will also perform maintenance steps such as correcting the copyright year ranges for all files and replacing the &lt;tt&gt;__DEPLOY_VERSION__&lt;/tt&gt; placeholder. Please see the file for all documentation about this script.<br /> <br /> After running this script, review all changes with &lt;tt&gt;git diff&lt;/tt&gt; as a final check before creating your release commit. Once you are satisfied that all changes are correct, commit your changes locally. Once committed, create the release tag locally; all release tags should be the version number you are creating and should match the output of &lt;tt&gt;Joomla\CMS\Version::getShortVersion()&lt;/tt&gt; (so if you have created 3.9.0-beta2 then the tag should be named 3.9.0-beta2).<br /> <br /> Once the tag has been created, you will run the &lt;tt&gt;build/build.php&lt;/tt&gt; script to generate the release packages. To ensure a clean build is produced, the script makes an archive of the tag you are building using the &lt;tt&gt;git archive&lt;/tt&gt; command and extracts this to the &lt;tt&gt;build/tmp/&lt;timestamp&gt;&lt;/tt&gt; directory. Depending on the patch version number, the following packages will be created in the &lt;tt&gt;build/tmp/packages&lt;/tt&gt;:<br /> <br /> * 0: Full installation and upgrade packages<br /> * 1: Full installation, upgrade packages, and patch packages for x.y.0 to x.y.1<br /> * 2+: Full installation, upgrade packages, patch packages for x.y.0 to x.y.&lt;new&gt; and x.y.&lt;new-1&gt; to x.y.&lt;new&gt; (i.e. when creating 3.8.8 this will create a patch package suitable for all 3.8.x releases and an optimized patch package for 3.8.7 to 3.8.8)<br /> <br /> Additionally, the script will generate a &lt;tt&gt;build/tmp/checksums.txt&lt;/tt&gt; file with the checksums for all generated packages. &lt;tt&gt;build/tmp/github_release.txt&lt;/tt&gt; is also produced which is a text template used for the GitHub releases.<br /> <br /> After the packages are created, you should validate that you are able to install and update a site using the ZIP packages (as these are the most frequently used type and served by our update system).<br /> <br /> == Publishing a Release ==<br /> === Release Packages ===<br /> Depending on the type of release being created, you will publish the release packages in different locations.<br /> <br /> ==== Alpha, Beta, Release Candidate ====<br /> The packages for these releases are uploaded to GitHub. When ready to publish, you should push the release tag you created to GitHub and use their interface to create a release from the tag and upload the packages.<br /> <br /> ==== Stable ====<br /> The packages for stable releases are uploaded to multiple locations, this is in part driven by the fact that the Amazon Web Services (AWS) S3 region used by Joomla is blocked in some locations therefore download mirrors are available when necessary.<br /> <br /> Note that the Joomla! Downloads Portal release can be done in advance (as long as the release is kept unpublished until release day). The Update server and GitHub releases are public by default and therefore should only be done at the time of release.<br /> <br /> ===== Joomla! Downloads Portal =====<br /> The canonical source for all stable releases is the [https://downloads.joomla.org/ Joomla! Downloads Portal]. The packages served from the site use Joomla's AWS account. You will need to log into the AWS console to upload the packages to S3 under the &lt;tt&gt;joomla-official-downloads&lt;/tt&gt; bucket. The exact path inside the bucket is &lt;tt&gt;joomladownloads/joomla&lt;version&gt;&lt;/tt&gt; where &lt;tt&gt;&lt;version&gt;&lt;/tt&gt; is the major version number (i.e. &lt;tt&gt;joomla3&lt;/tt&gt;), note for compatibility with Akeeba Release System folders for each individual release are not used. You can use [https://aws.amazon.com/cli/ AWS CLI] to upload these files - but MFA is still required - follow the procedure documented [https://aws.amazon.com/premiumsupport/knowledge-center/authenticate-mfa-cli/ here] or use a tool to automate this such as [https://github.com/broamski/aws-mfa AWS-MFA]<br /> <br /> Once files have been uploaded to S3 then you need to generate the release in Akeeba Release System on the Downloads Portal. To generate all required items quickly it's recommended to use the &lt;tt&gt;cli/ars-create-cms-release.php&lt;/tt&gt; script - the source for this can be found on [https://github.com/joomla/downloads.joomla.org/blob/master/www/cli/ars-create-cms-release.php Github].<br /> <br /> Note that if you need to rebuild a package - for example because issues are found in the release candidate - you do not need to re-create the ARS resources but simply delete and reupload the S3 packages then use the &lt;tt&gt;cli/ars-get-hashes.php&lt;/tt&gt; script on the downloads site (which simply update the checksums for each item in the release) - source code for this is also located at [https://github.com/joomla/downloads.joomla.org/blob/master/www/cli/ars-get-hashes.php Github].<br /> <br /> ===== Joomla! Update Server =====<br /> The Joomla! Update Server is used as a mirror for the download packages. After connecting to the server, you should create a new folder at &lt;tt&gt;www/releases/&lt;version&gt;&lt;/tt&gt; (i.e. &lt;tt&gt;www/releases/3.9.1&lt;/tt&gt; for the 3.9.1 release) and upload the packages here.<br /> <br /> ===== GitHub =====<br /> The packages are also uploaded to GitHub. This is similar to the steps for alpha, beta, and release candidate releases above. Note that you only need to push the release tag at this point (i.e. &lt;tt&gt;git push --tags&lt;/tt&gt;), you can wait to push the updated release branch until after the release is available.<br /> <br /> === Announcements ===<br /> ==== joomla.org ====<br /> For all stable releases, the main release announcement is published to the &lt;tt&gt;Joomla! Official News &gt; Project Release News&lt;/tt&gt; category on the main &lt;tt&gt;joomla.org&lt;/tt&gt; website. This is primarily handled by the Marketing team - however release leads are expected to contribute to the ''Bug fixes and Improvements'' section as well as highlighting any other information that may need to be called out as part of release notes. After release the Social Media team need to be made aware to ensure the release is available on social media - use the ''Contact the Social Media Team'' Channel on Glip.<br /> <br /> For a minor release, an updated version of the landing page at &lt;tt&gt;joomla.org/4&lt;/tt&gt; (previously &lt;tt&gt;joomla.org/3&lt;/tt&gt;) is published. Generally, this site is backed up from the sandbox location and transferred to the live domain shortly before release, this transfer should be coordinated with the [https://volunteers.joomla.org/teams/webmasters-team Webmasters Team].<br /> <br /> ==== developer.joomla.org ====<br /> For security releases, all accompanying articles are published to the &lt;tt&gt;News &gt; Security Centre&lt;/tt&gt; category on the Joomla! Developer Network. As these articles are referenced from the main release announcement, these should be published at the same time.<br /> <br /> == Update Server ==<br /> The update server must be updated to alert websites that a core update is available, this subdomain is managed on GitHub at https://github.com/joomla/update.joomla.org. Prior to each release, a pull request should be prepared with necessary changes for the release (generally this updates the version number, announcement URL, package URLs, and package checksums for the stable release and updating the version number for the nightly builds), see https://github.com/joomla/update.joomla.org/pull/117 as an example of this update for the 3.9.1 release. Pushes to the &lt;tt&gt;master&lt;/tt&gt; branch of this repo are automatically deployed thanks to a Jenkins job, notifications for many of the Jenkins jobs are sent to the &lt;tt&gt;.org Build Notifications&lt;/tt&gt; channel on RingCentral Glip so you should ensure a success notification was sent here otherwise check if there was an issue with the job and/or manually deploy the updated files.<br /> <br /> Note that the &lt;tt&gt;update.joomla.org&lt;/tt&gt; subdomain is behind a CDN and it generally takes 5-10 minutes for all nodes to update, if need be you can access &lt;tt&gt;update1.joomla.org&lt;/tt&gt; to verify the right files are deployed without using the CDN. Note files cache times aren't consistent and often we've seen issues where the list update file is the new version and the extension.xml file is on the old version.<br /> <br /> == Post Release Actions ==<br /> Once the release is published, there are several additional tasks that should be completed shortly after.<br /> <br /> === Post-Release Version Bump ===<br /> The version should be bumped to the next version scheduled for release using the &lt;tt&gt;build/bump.php&lt;/tt&gt; script (i.e. after the 3.9.1 release this would be bumped to 3.9.2-dev).<br /> <br /> === Branch Merging ===<br /> After incrementing the version number, you should merge all the release changes forward to other active branches (especially in the case of a security release). Ensure you pay careful attention while resolving merge conflicts, when making a merge that includes a version bump generally all files which contain the version string and/or release date will be in conflict (as of this writing this is 8 files).<br /> <br /> === Push Updated Branches ===<br /> When ready, you should directly push your updates to the Git repo. If you elect to use pull requests, the pull requests should NEVER be squashed or rebased otherwise this will wipe out Git's awareness of the merged commits and will make your next branch merges even more complex. Likewise, as an example, if the commit preparing the 3.9.1 release and bumping the version string to 3.9.2-dev were squash merged as a pull request, then the commit that the 3.9.1 release was tagged from would not be in the repository.<br /> <br /> === Update Release Milestones ===<br /> On GitHub, all merged items are assigned to a milestone to help organize items. With each release, the [https://github.com/joomla/joomla-cms/milestones milestones] should be updated to ensure that the milestone for the release you created has been closed and a milestone for the next release is open.<br /> <br /> === Regenerate Nightly Builds ===<br /> The nightly builds for any branch updated during the release process should be regenerated to include the release's changes. These can be manually triggered within the &lt;tt&gt;CMS Packaging&lt;/tt&gt; folder on the Jenkins server.<br /> <br /> === Website Updates ===<br /> With all code updates pushed, there are several website updates that need to be triggered.<br /> <br /> ==== api.joomla.org ====<br /> With each release, an updated build of the API documentation should be deployed to the &lt;tt&gt;api.joomla.org&lt;/tt&gt; website. These updates are triggered with the &lt;tt&gt;Joomla! API &gt; Deploy Docs - CMS&lt;/tt&gt; job on Jenkins. As this job relies on the release tags from the CMS repo, this can only be done after the release tag has been pushed.<br /> <br /> ==== developer.joomla.org ====<br /> After a release, the &lt;tt&gt;Joomla! Project Roadmap&lt;/tt&gt; article in the &lt;tt&gt;Uncategorised&lt;/tt&gt; category should be updated to reflect the newly released version and updated links, as well as adding expected release dates for the next release.<br /> <br /> The version whitelist for the statistics server should also be updated to allow the next version to be submitted; if you have not already, you should have a clone of the https://github.com/joomla/statistics-server repository on your local system. Once cloned and set up, run the &lt;tt&gt;bin/stats tags:joomla&lt;/tt&gt; command to regenerate the Joomla version whitelist. As this command relies on the release tags from the CMS repo, this can only be done after the release tag has been pushed. The updated &lt;tt&gt;versions/joomla.json&lt;/tt&gt; should be committed and pushed, and a Jenkins job will deploy the updated site resources.<br /> <br /> == Additional Considerations ==<br /> The release manager or a delegate is suggested to be in communication with the Webmasters Team to ensure the &lt;tt&gt;joomla.org&lt;/tt&gt; websites are updated in a timely manner. When a security release is scheduled, it is encouraged to share the update release package with the team so that our sites may be updated before the fix is made public to mitigate the chance of the vulnerability being used to exploit one of our sites. It also provides additional testing for security fixes on real world sites in addition to the tests performed by the CMS Release Team.<br /> <br /> = Framework Release Cycle =<br /> The packages of the Joomla Framework are on an independent lifecycle meaning each package can be updated and released independently of all others. Generally the only restriction is with major releases, which should coincide with the CMS release cycle (i.e. CMS 3.x uses Framework 1.x, CMS 4.x will use Framework 2.x therefore Framework 2.0 stable releases should not be made until the CMS is in its beta phase at the earliest).<br /> <br /> == Tagging a Release ==<br /> Most packages can be tagged and released through the &lt;tt&gt;Joomla! Framework &gt; Package Release&lt;/tt&gt; job on Jenkins, however as of this writing this job only supports tagging releases from a repository's &lt;tt&gt;master&lt;/tt&gt; branch. To tag a release, select the package you wish to update and specify the version you are releasing in the job's parameters and run the job; all releases should follow Semantic Versioning to set the correct number.<br /> <br /> Once the job has completed, you should verify the new release is visible on [https://packagist.org/packages/joomla/ Packagist]. Within a day, the new update should be visible on the [https://framework.joomla.org/status Joomla Framework Status page] (the database is updated via cron job reading from Packagist's API), if the updated version isn't seen on the site in a relatively timely manner you should clone the website locally and debug the &lt;tt&gt;packagist:sync:releases&lt;/tt&gt; command.<br /> <br /> == Security Releases ==<br /> When a security release is created, a pull request should be sent to the [https://github.com/FriendsOfPHP/security-advisories FriendsOfPHP/security-advisories repository] with relevant details. This repository is used by many tools in the PHP and Composer ecosystem to alert users of security issues. https://github.com/FriendsOfPHP/security-advisories/pull/134 is an example of this pull request.<br /> <br /> == Onboarding Release Leads ==<br /> Release Leads will need access to a number of resources. The following are required:<br /> * Account on Github (added to [https://github.com/orgs/joomla/teams/cms-release-leads/members the CMS Release Leads team] for the Joomla Org (which also provides jenkins access) and [https://github.com/orgs/joomla-backports/teams/cms-release-leads the CMS Release Leads team] for the Joomla Backport org.<br /> * The Forum (Ensure users are aware of release threads)<br /> * Glip (CMS Maintainers, CMS Release Leads, WebMasters Team, Production, CMS Release Team)<br /> * Introduction with Translation, JSST and Webmaster Liasons<br /> * SSH keys added to Update and Downloads servers (including VPN Access)<br /> * Downloads Website (Release Leads -&gt; CMS ACL Group)<br /> * Developer Website (? ACL Group)<br /> * AWS Account in Release_Managers Group. User must reset password and setup MFA.<br /> * Drone Admins<br /> <br /> [[Category:Bug Squad]]<br /> [[Category:Coordinators]]<br /> [[Category:Development]]</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Joomla:Release_procedure_and_checklist&diff=876795 2022-01-30T19:54:02Z

<p>Wilsonge: /* Onboarding Release Leads */</p> <hr /> <div>{{RightTOC}}<br /> <br /> This is a general procedure explanation for managing releases of Joomla! and the Joomla! Framework. This list is best suited for a [[Minor Release]] or [[Maintenance Release]], however the steps will generally apply to a [[Major Release]] as well but will require some judgement calls from the release manager and/or leadership team.<br /> <br /> There is a more formal checklist available [https://github.com/joomla/joomla-cms/blob/4.1-dev/build/release-checklist.md on GitHub] for release leads to use that is intended to complement the steps described in this page.<br /> <br /> == Issue Triage, Patch Review, Merging Patches ==<br /> The release cycle for a new software version begins immediately after the previous one is completed. In the immediate hours and days after a release, the [https://github.com/joomla/joomla-cms issue tracker] and [https://forum.joomla.org/ support forums], in close coordination with the [https://volunteers.joomla.org/teams/bug-squad Bug Squad] and [https://volunteers.joomla.org/teams/cms-release-team CMS Release Team], should be monitored for reports of potential regressions or critical bugs that would warrant a quick follow-on release to address the issue. It is generally suggested to wait 48-72 hours before resuming merging of reviewed and ready for commit pull requests to keep the release branch &quot;clean&quot; and ready for a release (note this is only a suggestion, if need be a release manager could create a branch from the release tag however this involves a bit more effort therefore this suggestion is for simplicity's sake).<br /> <br /> Throughout the release cycle, the release manager should be involved with reviewing patches and merging reviewed patches to the appropriate release branch. As of this writing (where 4.0.6 is the present release), the following branches are generally active:<br /> <br /> * &lt;tt&gt;3.10-dev&lt;/tt&gt;: This is the 3.x branch, generally only bug fixes and &quot;general&quot; maintenance work should merge to this branch.<br /> * &lt;tt&gt;4.0-dev&lt;/tt&gt;: This is the 4.0.x branch - there are no more intended releases to this branch unless required by security fixes.<br /> * &lt;tt&gt;4.1-dev&lt;/tt&gt;: This is the main release branch and is where most activity occurs, generally only bug fixes and &quot;general&quot; maintenance work should merge to this branch although minor features may be merged at the discretion of the release manager and/or leadership team. All code from 3.10-dev is merged into this branch.<br /> * &lt;tt&gt;4.2-dev&lt;/tt&gt;: This is the release branch for the next minor release (the branch's name will always be the version it represents), new features should be merged to this branch<br /> <br /> === Branch Merging ===<br /> All branches should remain in-sync and all work should be regularly merged forward. Given the above example, the following is the recommended merging workflow (in general, the suggested workflow is that 3.10-dev is merged to the current 4.x-dev branch and then through to the next minor branch):<br /> <br /> * &lt;tt&gt;3.10-dev&lt;/tt&gt; should be merged into &lt;tt&gt;4.0-dev&lt;/tt&gt;<br /> * &lt;tt&gt;4.0-dev&lt;/tt&gt; should be merged to &lt;tt&gt;4.1-dev&lt;/tt&gt;<br /> * &lt;tt&gt;4.1-dev&lt;/tt&gt; should be merged to &lt;tt&gt;4.2-dev&lt;/tt&gt;<br /> <br /> It is suggested that at least once per week branch merging occurs.<br /> <br /> == Preparing To Release ==<br /> When scheduling and preparing a release, the timeline should be communicated with the Production and Marketing &amp; Communication Department leadership so that all teams are prepared to support the release. Note that when scheduling releases, consideration should be given to holidays around the world and the impact of issuing a release near those periods considered. Helpful resources include http://interfaith-calendar.org/ and https://www.timeanddate.com/holidays/<br /> <br /> === Review Release Milestone and Blockers ===<br /> On GitHub, check the [https://github.com/joomla/joomla-cms/milestones milestone] for the release you are preparing to create and for any open items with the [https://github.com/joomla/joomla-cms/labels/release-blocker release-blocker] label. If there are remaining open items, review them to determine if they are items that should be included in the release or if they can be rescheduled to a later release.<br /> <br /> === Release Schedule ===<br /> ==== Minor Release ====<br /> Given the nature of a minor release, the following is the suggested release timeline:<br /> <br /> * Six weeks prior to planned stable release: Tag the first Beta release<br /> ** At this point the release should be considered feature complete and new features should be deferred to the next minor release<br /> * Weekly Beta releases should follow this until the Release Candidate<br /> * Two weeks prior to planned stable release: Tag the Release Candidate<br /> ** At this point the release branch(es) should remain closed for committing except for high priority bug fixes and language updates<br /> ** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the &quot;no later than&quot; time<br /> ** Inform the CMS Release Team and call out anything that you would like extra testing on<br /> * One week prior to planned stable release: If necessary, create a second Release Candidate<br /> * 2-3 days before release: Build final packages - share with CMS Release Team and do release preparation activities.<br /> * Planned release date: Tag the stable release<br /> <br /> ==== Maintenance Release ====<br /> Maintenance releases operate on a 4-6 week cycle and the following is the suggested release timeline:<br /> <br /> * 9-10 days before planned release date: Tag a Release Candidate<br /> ** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the &quot;no later than&quot; time<br /> ** Inform the CMS Release Team and call out anything that you would like extra testing on<br /> * 2-3 days before release: Build final packages - share with CMS Release Team and do release preparation activities.<br /> * Planned release date: Tag the stable release<br /> <br /> === Reviewing Release Changes ===<br /> Before tagging a release, the list of changes in the release should be reviewed by the release manager and/or leadership team. The list of changes can be found using GitHub's compare function with the URL &lt;tt&gt;https://github.com/joomla/joomla-cms/compare/&lt;version&gt;...4.1-dev&lt;/tt&gt; which will compare the changes from &lt;tt&gt;&lt;version&gt;&lt;/tt&gt; to the current 4.1-dev branch (for example, https://github.com/joomla/joomla-cms/compare/3.9.0...3.9.1-rc is the comparison from the 3.9.0 release tag to the 3.9.1-rc tag). Key purposes of this review include:<br /> <br /> * Ensuring all patches are compliant with Semantic Versioning (SemVer) (i.e. no backward compatibility breaks in minor or maintenance releases and no features in maintenance releases); SemVer violations should be cleared with the Production Department leadership<br /> * Ensuring all code revisions are compatible with Joomla's minimum supported versions (i.e. no PHP 5.4 syntax in 3.x releases where PHP 5.3 is the minimum supported version, exceptions may be made if introducing a code path and files that will only be executed on newer PHP versions)<br /> ** Joomla's testing integrations should not be relied on in full for this as there are large portions of the Joomla code base which do not have automated test coverage, and as of this writing, there is not a code linting process in place checking for potential issues<br /> * Ensuring features and &quot;significant&quot; changes are documented<br /> <br /> === Security Fixes ===<br /> From time to time, security fixes must be included in a release. Prior to every release, the release manager should check with the [https://volunteers.joomla.org/teams/security-strike-team Security Strike Team] to determine if security fixes are required, and if so ensure this is communicated to all members involved with release work (i.e. the marketing team liaison who assists with the publication of release related material). When a security release is necessary, an internal Release Candidate should be built for testing by the Security Strike Team, CMS Release Team, and [https://volunteers.joomla.org/teams/cms-maintenance-team CMS Maintenance Team] with all security patches included. These teams should also receive information about the vulnerabilities being addressed to ensure there are no regressions in the impacted areas.<br /> <br /> Note, when a security fix involves a Joomla Framework package, the Framework package should be patched first and a release created of the affected package then the CMS updated with &lt;tt&gt;composer update&lt;/tt&gt;.<br /> <br /> Sometimes security fixes are required for composer dependencies that are out of support. In such cases we fork the 3rd party dependency into https://github.com/joomla-backports and then apply security fixes there in a &lt;tt&gt;joomla-backports&lt;/tt&gt; branch (and override the [https://github.com/joomla/joomla-cms/blob/3.10.5/composer.json#L28-L32 repository in composer.json] and as well as the branch reference [https://github.com/joomla/joomla-cms/blob/3.10.5/composer.json#L54 here]. Links are a sample for PHPMailer overrides in Joomla 3.10).<br /> <br /> === Release FAQ ===<br /> Create Release FAQ Category on the Joomla Documentation site. (i.e. Clone the contents of an existing page such as [https://docs.joomla.org/Category:Version_4.0.6_FAQ FAQ] and update the version number to your required version)<br /> <br /> == Building a Release ==<br /> Building a release starts with checking that any files and folders that have been deleted are included in the arrays in the installer script at &lt;tt&gt;administrator/components/com_admin/script.php&lt;/tt&gt;. There is a helper script in the repository to assist with this located at &lt;tt&gt;build/deleted_file_check.php&lt;/tt&gt;. Running &lt;tt&gt;php build/deleted_file_check.php&lt;/tt&gt; with its required &lt;tt&gt;--from&lt;/tt&gt; option will write a file to &lt;tt&gt;build/deleted_files.txt&lt;/tt&gt; with the list of files deleted since the from reference. Please see the PHP file for all documentation about this script.<br /> <br /> The following steps require the individual to create commits and tags. It is suggested that these commits and tags be GPG signed as an extra security step but this is not a mandatory requirement as of this writing.<br /> <br /> If creating a security release, at this point you should apply all patches provided by the security team.<br /> <br /> Once it is confirmed that the deleted files listing is correct, the &lt;tt&gt;build/bump.php&lt;/tt&gt; script should be executed to set the new version number. This script will also perform maintenance steps such as correcting the copyright year ranges for all files and replacing the &lt;tt&gt;__DEPLOY_VERSION__&lt;/tt&gt; placeholder. Please see the file for all documentation about this script.<br /> <br /> After running this script, review all changes with &lt;tt&gt;git diff&lt;/tt&gt; as a final check before creating your release commit. Once you are satisfied that all changes are correct, commit your changes locally. Once committed, create the release tag locally; all release tags should be the version number you are creating and should match the output of &lt;tt&gt;Joomla\CMS\Version::getShortVersion()&lt;/tt&gt; (so if you have created 3.9.0-beta2 then the tag should be named 3.9.0-beta2).<br /> <br /> Once the tag has been created, you will run the &lt;tt&gt;build/build.php&lt;/tt&gt; script to generate the release packages. To ensure a clean build is produced, the script makes an archive of the tag you are building using the &lt;tt&gt;git archive&lt;/tt&gt; command and extracts this to the &lt;tt&gt;build/tmp/&lt;timestamp&gt;&lt;/tt&gt; directory. Depending on the patch version number, the following packages will be created in the &lt;tt&gt;build/tmp/packages&lt;/tt&gt;:<br /> <br /> * 0: Full installation and upgrade packages<br /> * 1: Full installation, upgrade packages, and patch packages for x.y.0 to x.y.1<br /> * 2+: Full installation, upgrade packages, patch packages for x.y.0 to x.y.&lt;new&gt; and x.y.&lt;new-1&gt; to x.y.&lt;new&gt; (i.e. when creating 3.8.8 this will create a patch package suitable for all 3.8.x releases and an optimized patch package for 3.8.7 to 3.8.8)<br /> <br /> Additionally, the script will generate a &lt;tt&gt;build/tmp/checksums.txt&lt;/tt&gt; file with the checksums for all generated packages. &lt;tt&gt;build/tmp/github_release.txt&lt;/tt&gt; is also produced which is a text template used for the GitHub releases.<br /> <br /> After the packages are created, you should validate that you are able to install and update a site using the ZIP packages (as these are the most frequently used type and served by our update system).<br /> <br /> == Publishing a Release ==<br /> === Release Packages ===<br /> Depending on the type of release being created, you will publish the release packages in different locations.<br /> <br /> ==== Alpha, Beta, Release Candidate ====<br /> The packages for these releases are uploaded to GitHub. When ready to publish, you should push the release tag you created to GitHub and use their interface to create a release from the tag and upload the packages.<br /> <br /> ==== Stable ====<br /> The packages for stable releases are uploaded to multiple locations, this is in part driven by the fact that the Amazon Web Services (AWS) S3 region used by Joomla is blocked in some locations therefore download mirrors are available when necessary.<br /> <br /> Note that the Joomla! Downloads Portal release can be done in advance (as long as the release is kept unpublished until release day). The Update server and GitHub releases are public by default and therefore should only be done at the time of release.<br /> <br /> ===== Joomla! Downloads Portal =====<br /> The canonical source for all stable releases is the [https://downloads.joomla.org/ Joomla! Downloads Portal]. The packages served from the site use Joomla's AWS account. You will need to log into the AWS console to upload the packages to S3 under the &lt;tt&gt;joomla-official-downloads&lt;/tt&gt; bucket. The exact path inside the bucket is &lt;tt&gt;joomladownloads/joomla&lt;version&gt;&lt;/tt&gt; where &lt;tt&gt;&lt;version&gt;&lt;/tt&gt; is the major version number (i.e. &lt;tt&gt;joomla3&lt;/tt&gt;), note for compatibility with Akeeba Release System folders for each individual release are not used. You can use [https://aws.amazon.com/cli/ AWS CLI] to upload these files - but MFA is still required - follow the procedure documented [https://aws.amazon.com/premiumsupport/knowledge-center/authenticate-mfa-cli/ here] or use a tool to automate this such as [https://github.com/broamski/aws-mfa AWS-MFA]<br /> <br /> Once files have been uploaded to S3 then you need to generate the release in Akeeba Release System on the Downloads Portal. To generate all required items quickly it's recommended to use the &lt;tt&gt;cli/ars-create-cms-release.php&lt;/tt&gt; script - the source for this can be found on [https://github.com/joomla/downloads.joomla.org/blob/master/www/cli/ars-create-cms-release.php Github].<br /> <br /> Note that if you need to rebuild a package - for example because issues are found in the release candidate - you do not need to re-create the ARS resources but simply delete and reupload the S3 packages then use the &lt;tt&gt;cli/ars-get-hashes.php&lt;/tt&gt; script on the downloads site (which simply update the checksums for each item in the release) - source code for this is also located at [https://github.com/joomla/downloads.joomla.org/blob/master/www/cli/ars-get-hashes.php Github].<br /> <br /> ===== Joomla! Update Server =====<br /> The Joomla! Update Server is used as a mirror for the download packages. After connecting to the server, you should create a new folder at &lt;tt&gt;www/releases/&lt;version&gt;&lt;/tt&gt; (i.e. &lt;tt&gt;www/releases/3.9.1&lt;/tt&gt; for the 3.9.1 release) and upload the packages here.<br /> <br /> ===== GitHub =====<br /> The packages are also uploaded to GitHub. This is similar to the steps for alpha, beta, and release candidate releases above. Note that you only need to push the release tag at this point (i.e. &lt;tt&gt;git push --tags&lt;/tt&gt;), you can wait to push the updated release branch until after the release is available.<br /> <br /> === Announcements ===<br /> ==== joomla.org ====<br /> For all stable releases, the main release announcement is published to the &lt;tt&gt;Joomla! Official News &gt; Project Release News&lt;/tt&gt; category on the main &lt;tt&gt;joomla.org&lt;/tt&gt; website. This is primarily handled by the Marketing team - however release leads are expected to contribute to the ''Bug fixes and Improvements'' section as well as highlighting any other information that may need to be called out as part of release notes. After release the Social Media team need to be made aware to ensure the release is available on social media - use the ''Contact the Social Media Team'' Channel on Glip.<br /> <br /> For a minor release, an updated version of the landing page at &lt;tt&gt;joomla.org/4&lt;/tt&gt; (previously &lt;tt&gt;joomla.org/3&lt;/tt&gt;) is published. Generally, this site is backed up from the sandbox location and transferred to the live domain shortly before release, this transfer should be coordinated with the [https://volunteers.joomla.org/teams/webmasters-team Webmasters Team].<br /> <br /> ==== developer.joomla.org ====<br /> For security releases, all accompanying articles are published to the &lt;tt&gt;News &gt; Security Centre&lt;/tt&gt; category on the Joomla! Developer Network. As these articles are referenced from the main release announcement, these should be published at the same time.<br /> <br /> == Update Server ==<br /> The update server must be updated to alert websites that a core update is available, this subdomain is managed on GitHub at https://github.com/joomla/update.joomla.org. Prior to each release, a pull request should be prepared with necessary changes for the release (generally this updates the version number, announcement URL, package URLs, and package checksums for the stable release and updating the version number for the nightly builds), see https://github.com/joomla/update.joomla.org/pull/117 as an example of this update for the 3.9.1 release. Pushes to the &lt;tt&gt;master&lt;/tt&gt; branch of this repo are automatically deployed thanks to a Jenkins job, notifications for many of the Jenkins jobs are sent to the &lt;tt&gt;.org Build Notifications&lt;/tt&gt; channel on RingCentral Glip so you should ensure a success notification was sent here otherwise check if there was an issue with the job and/or manually deploy the updated files.<br /> <br /> Note that the &lt;tt&gt;update.joomla.org&lt;/tt&gt; subdomain is behind a CDN and it generally takes 5-10 minutes for all nodes to update, if need be you can access &lt;tt&gt;update1.joomla.org&lt;/tt&gt; to verify the right files are deployed without using the CDN. Note files cache times aren't consistent and often we've seen issues where the list update file is the new version and the extension.xml file is on the old version.<br /> <br /> == Post Release Actions ==<br /> Once the release is published, there are several additional tasks that should be completed shortly after.<br /> <br /> === Post-Release Version Bump ===<br /> The version should be bumped to the next version scheduled for release using the &lt;tt&gt;build/bump.php&lt;/tt&gt; script (i.e. after the 3.9.1 release this would be bumped to 3.9.2-dev).<br /> <br /> === Branch Merging ===<br /> After incrementing the version number, you should merge all the release changes forward to other active branches (especially in the case of a security release). Ensure you pay careful attention while resolving merge conflicts, when making a merge that includes a version bump generally all files which contain the version string and/or release date will be in conflict (as of this writing this is 8 files).<br /> <br /> === Push Updated Branches ===<br /> When ready, you should directly push your updates to the Git repo. If you elect to use pull requests, the pull requests should NEVER be squashed or rebased otherwise this will wipe out Git's awareness of the merged commits and will make your next branch merges even more complex. Likewise, as an example, if the commit preparing the 3.9.1 release and bumping the version string to 3.9.2-dev were squash merged as a pull request, then the commit that the 3.9.1 release was tagged from would not be in the repository.<br /> <br /> === Update Release Milestones ===<br /> On GitHub, all merged items are assigned to a milestone to help organize items. With each release, the [https://github.com/joomla/joomla-cms/milestones milestones] should be updated to ensure that the milestone for the release you created has been closed and a milestone for the next release is open.<br /> <br /> === Regenerate Nightly Builds ===<br /> The nightly builds for any branch updated during the release process should be regenerated to include the release's changes. These can be manually triggered within the &lt;tt&gt;CMS Packaging&lt;/tt&gt; folder on the Jenkins server.<br /> <br /> === Website Updates ===<br /> With all code updates pushed, there are several website updates that need to be triggered.<br /> <br /> ==== api.joomla.org ====<br /> With each release, an updated build of the API documentation should be deployed to the &lt;tt&gt;api.joomla.org&lt;/tt&gt; website. These updates are triggered with the &lt;tt&gt;Joomla! API &gt; Deploy Docs - CMS&lt;/tt&gt; job on Jenkins. As this job relies on the release tags from the CMS repo, this can only be done after the release tag has been pushed.<br /> <br /> ==== developer.joomla.org ====<br /> After a release, the &lt;tt&gt;Joomla! Project Roadmap&lt;/tt&gt; article in the &lt;tt&gt;Uncategorised&lt;/tt&gt; category should be updated to reflect the newly released version and updated links, as well as adding expected release dates for the next release.<br /> <br /> The version whitelist for the statistics server should also be updated to allow the next version to be submitted; if you have not already, you should have a clone of the https://github.com/joomla/statistics-server repository on your local system. Once cloned and set up, run the &lt;tt&gt;bin/stats tags:joomla&lt;/tt&gt; command to regenerate the Joomla version whitelist. As this command relies on the release tags from the CMS repo, this can only be done after the release tag has been pushed. The updated &lt;tt&gt;versions/joomla.json&lt;/tt&gt; should be committed and pushed, and a Jenkins job will deploy the updated site resources.<br /> <br /> == Additional Considerations ==<br /> The release manager or a delegate is suggested to be in communication with the Webmasters Team to ensure the &lt;tt&gt;joomla.org&lt;/tt&gt; websites are updated in a timely manner. When a security release is scheduled, it is encouraged to share the update release package with the team so that our sites may be updated before the fix is made public to mitigate the chance of the vulnerability being used to exploit one of our sites. It also provides additional testing for security fixes on real world sites in addition to the tests performed by the CMS Release Team.<br /> <br /> = Framework Release Cycle =<br /> The packages of the Joomla Framework are on an independent lifecycle meaning each package can be updated and released independently of all others. Generally the only restriction is with major releases, which should coincide with the CMS release cycle (i.e. CMS 3.x uses Framework 1.x, CMS 4.x will use Framework 2.x therefore Framework 2.0 stable releases should not be made until the CMS is in its beta phase at the earliest).<br /> <br /> == Tagging a Release ==<br /> Most packages can be tagged and released through the &lt;tt&gt;Joomla! Framework &gt; Package Release&lt;/tt&gt; job on Jenkins, however as of this writing this job only supports tagging releases from a repository's &lt;tt&gt;master&lt;/tt&gt; branch. To tag a release, select the package you wish to update and specify the version you are releasing in the job's parameters and run the job; all releases should follow Semantic Versioning to set the correct number.<br /> <br /> Once the job has completed, you should verify the new release is visible on [https://packagist.org/packages/joomla/ Packagist]. Within a day, the new update should be visible on the [https://framework.joomla.org/status Joomla Framework Status page] (the database is updated via cron job reading from Packagist's API), if the updated version isn't seen on the site in a relatively timely manner you should clone the website locally and debug the &lt;tt&gt;packagist:sync:releases&lt;/tt&gt; command.<br /> <br /> == Security Releases ==<br /> When a security release is created, a pull request should be sent to the [https://github.com/FriendsOfPHP/security-advisories FriendsOfPHP/security-advisories repository] with relevant details. This repository is used by many tools in the PHP and Composer ecosystem to alert users of security issues. https://github.com/FriendsOfPHP/security-advisories/pull/134 is an example of this pull request.<br /> <br /> == Onboarding Release Leads ==<br /> Release Leads will need access to a number of resources. The following are required:<br /> * Account on Github (added to [https://github.com/orgs/joomla/teams/cms-release-leads/members the CMS Release Leads team] for the Joomla Org (which also provides jenkins access) and [https://github.com/orgs/joomla-backports/teams/cms-release-leads the CMS Release Leads team] for the Joomla Backport org.<br /> * The Forum (Ensure users are aware of release threads)<br /> * Glip (CMS Maintainers, CMS Release Leads, WebMasters Team, Production, CMS Release Team)<br /> * Introduction with Translation, JSST and Webmaster Liasons<br /> * SSH keys added to Update and Downloads servers<br /> * Downloads Website (Release Leads -&gt; CMS ACL Group)<br /> * Developer Website (? ACL Group)<br /> * AWS Account in Release_Managers Group. User must reset password and setup MFA.<br /> * Drone Admins<br /> <br /> [[Category:Bug Squad]]<br /> [[Category:Coordinators]]<br /> [[Category:Development]]</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Joomla:Release_procedure_and_checklist&diff=876794 2022-01-30T17:54:22Z

<p>Wilsonge: /* Onboarding Release Leads */</p> <hr /> <div>{{RightTOC}}<br /> <br /> This is a general procedure explanation for managing releases of Joomla! and the Joomla! Framework. This list is best suited for a [[Minor Release]] or [[Maintenance Release]], however the steps will generally apply to a [[Major Release]] as well but will require some judgement calls from the release manager and/or leadership team.<br /> <br /> There is a more formal checklist available [https://github.com/joomla/joomla-cms/blob/4.1-dev/build/release-checklist.md on GitHub] for release leads to use that is intended to complement the steps described in this page.<br /> <br /> == Issue Triage, Patch Review, Merging Patches ==<br /> The release cycle for a new software version begins immediately after the previous one is completed. In the immediate hours and days after a release, the [https://github.com/joomla/joomla-cms issue tracker] and [https://forum.joomla.org/ support forums], in close coordination with the [https://volunteers.joomla.org/teams/bug-squad Bug Squad] and [https://volunteers.joomla.org/teams/cms-release-team CMS Release Team], should be monitored for reports of potential regressions or critical bugs that would warrant a quick follow-on release to address the issue. It is generally suggested to wait 48-72 hours before resuming merging of reviewed and ready for commit pull requests to keep the release branch &quot;clean&quot; and ready for a release (note this is only a suggestion, if need be a release manager could create a branch from the release tag however this involves a bit more effort therefore this suggestion is for simplicity's sake).<br /> <br /> Throughout the release cycle, the release manager should be involved with reviewing patches and merging reviewed patches to the appropriate release branch. As of this writing (where 4.0.6 is the present release), the following branches are generally active:<br /> <br /> * &lt;tt&gt;3.10-dev&lt;/tt&gt;: This is the 3.x branch, generally only bug fixes and &quot;general&quot; maintenance work should merge to this branch.<br /> * &lt;tt&gt;4.0-dev&lt;/tt&gt;: This is the 4.0.x branch - there are no more intended releases to this branch unless required by security fixes.<br /> * &lt;tt&gt;4.1-dev&lt;/tt&gt;: This is the main release branch and is where most activity occurs, generally only bug fixes and &quot;general&quot; maintenance work should merge to this branch although minor features may be merged at the discretion of the release manager and/or leadership team. All code from 3.10-dev is merged into this branch.<br /> * &lt;tt&gt;4.2-dev&lt;/tt&gt;: This is the release branch for the next minor release (the branch's name will always be the version it represents), new features should be merged to this branch<br /> <br /> === Branch Merging ===<br /> All branches should remain in-sync and all work should be regularly merged forward. Given the above example, the following is the recommended merging workflow (in general, the suggested workflow is that 3.10-dev is merged to the current 4.x-dev branch and then through to the next minor branch):<br /> <br /> * &lt;tt&gt;3.10-dev&lt;/tt&gt; should be merged into &lt;tt&gt;4.0-dev&lt;/tt&gt;<br /> * &lt;tt&gt;4.0-dev&lt;/tt&gt; should be merged to &lt;tt&gt;4.1-dev&lt;/tt&gt;<br /> * &lt;tt&gt;4.1-dev&lt;/tt&gt; should be merged to &lt;tt&gt;4.2-dev&lt;/tt&gt;<br /> <br /> It is suggested that at least once per week branch merging occurs.<br /> <br /> == Preparing To Release ==<br /> When scheduling and preparing a release, the timeline should be communicated with the Production and Marketing &amp; Communication Department leadership so that all teams are prepared to support the release. Note that when scheduling releases, consideration should be given to holidays around the world and the impact of issuing a release near those periods considered. Helpful resources include http://interfaith-calendar.org/ and https://www.timeanddate.com/holidays/<br /> <br /> === Review Release Milestone and Blockers ===<br /> On GitHub, check the [https://github.com/joomla/joomla-cms/milestones milestone] for the release you are preparing to create and for any open items with the [https://github.com/joomla/joomla-cms/labels/release-blocker release-blocker] label. If there are remaining open items, review them to determine if they are items that should be included in the release or if they can be rescheduled to a later release.<br /> <br /> === Release Schedule ===<br /> ==== Minor Release ====<br /> Given the nature of a minor release, the following is the suggested release timeline:<br /> <br /> * Six weeks prior to planned stable release: Tag the first Beta release<br /> ** At this point the release should be considered feature complete and new features should be deferred to the next minor release<br /> * Weekly Beta releases should follow this until the Release Candidate<br /> * Two weeks prior to planned stable release: Tag the Release Candidate<br /> ** At this point the release branch(es) should remain closed for committing except for high priority bug fixes and language updates<br /> ** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the &quot;no later than&quot; time<br /> ** Inform the CMS Release Team and call out anything that you would like extra testing on<br /> * One week prior to planned stable release: If necessary, create a second Release Candidate<br /> * 2-3 days before release: Build final packages - share with CMS Release Team and do release preparation activities.<br /> * Planned release date: Tag the stable release<br /> <br /> ==== Maintenance Release ====<br /> Maintenance releases operate on a 4-6 week cycle and the following is the suggested release timeline:<br /> <br /> * 9-10 days before planned release date: Tag a Release Candidate<br /> ** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the &quot;no later than&quot; time<br /> ** Inform the CMS Release Team and call out anything that you would like extra testing on<br /> * 2-3 days before release: Build final packages - share with CMS Release Team and do release preparation activities.<br /> * Planned release date: Tag the stable release<br /> <br /> === Reviewing Release Changes ===<br /> Before tagging a release, the list of changes in the release should be reviewed by the release manager and/or leadership team. The list of changes can be found using GitHub's compare function with the URL &lt;tt&gt;https://github.com/joomla/joomla-cms/compare/&lt;version&gt;...4.1-dev&lt;/tt&gt; which will compare the changes from &lt;tt&gt;&lt;version&gt;&lt;/tt&gt; to the current 4.1-dev branch (for example, https://github.com/joomla/joomla-cms/compare/3.9.0...3.9.1-rc is the comparison from the 3.9.0 release tag to the 3.9.1-rc tag). Key purposes of this review include:<br /> <br /> * Ensuring all patches are compliant with Semantic Versioning (SemVer) (i.e. no backward compatibility breaks in minor or maintenance releases and no features in maintenance releases); SemVer violations should be cleared with the Production Department leadership<br /> * Ensuring all code revisions are compatible with Joomla's minimum supported versions (i.e. no PHP 5.4 syntax in 3.x releases where PHP 5.3 is the minimum supported version, exceptions may be made if introducing a code path and files that will only be executed on newer PHP versions)<br /> ** Joomla's testing integrations should not be relied on in full for this as there are large portions of the Joomla code base which do not have automated test coverage, and as of this writing, there is not a code linting process in place checking for potential issues<br /> * Ensuring features and &quot;significant&quot; changes are documented<br /> <br /> === Security Fixes ===<br /> From time to time, security fixes must be included in a release. Prior to every release, the release manager should check with the [https://volunteers.joomla.org/teams/security-strike-team Security Strike Team] to determine if security fixes are required, and if so ensure this is communicated to all members involved with release work (i.e. the marketing team liaison who assists with the publication of release related material). When a security release is necessary, an internal Release Candidate should be built for testing by the Security Strike Team, CMS Release Team, and [https://volunteers.joomla.org/teams/cms-maintenance-team CMS Maintenance Team] with all security patches included. These teams should also receive information about the vulnerabilities being addressed to ensure there are no regressions in the impacted areas.<br /> <br /> Note, when a security fix involves a Joomla Framework package, the Framework package should be patched first and a release created of the affected package then the CMS updated with &lt;tt&gt;composer update&lt;/tt&gt;.<br /> <br /> Sometimes security fixes are required for composer dependencies that are out of support. In such cases we fork the 3rd party dependency into https://github.com/joomla-backports and then apply security fixes there in a &lt;tt&gt;joomla-backports&lt;/tt&gt; branch (and override the [https://github.com/joomla/joomla-cms/blob/3.10.5/composer.json#L28-L32 repository in composer.json] and as well as the branch reference [https://github.com/joomla/joomla-cms/blob/3.10.5/composer.json#L54 here]. Links are a sample for PHPMailer overrides in Joomla 3.10).<br /> <br /> === Release FAQ ===<br /> Create Release FAQ Category on the Joomla Documentation site. (i.e. Clone the contents of an existing page such as [https://docs.joomla.org/Category:Version_4.0.6_FAQ FAQ] and update the version number to your required version)<br /> <br /> == Building a Release ==<br /> Building a release starts with checking that any files and folders that have been deleted are included in the arrays in the installer script at &lt;tt&gt;administrator/components/com_admin/script.php&lt;/tt&gt;. There is a helper script in the repository to assist with this located at &lt;tt&gt;build/deleted_file_check.php&lt;/tt&gt;. Running &lt;tt&gt;php build/deleted_file_check.php&lt;/tt&gt; with its required &lt;tt&gt;--from&lt;/tt&gt; option will write a file to &lt;tt&gt;build/deleted_files.txt&lt;/tt&gt; with the list of files deleted since the from reference. Please see the PHP file for all documentation about this script.<br /> <br /> The following steps require the individual to create commits and tags. It is suggested that these commits and tags be GPG signed as an extra security step but this is not a mandatory requirement as of this writing.<br /> <br /> If creating a security release, at this point you should apply all patches provided by the security team.<br /> <br /> Once it is confirmed that the deleted files listing is correct, the &lt;tt&gt;build/bump.php&lt;/tt&gt; script should be executed to set the new version number. This script will also perform maintenance steps such as correcting the copyright year ranges for all files and replacing the &lt;tt&gt;__DEPLOY_VERSION__&lt;/tt&gt; placeholder. Please see the file for all documentation about this script.<br /> <br /> After running this script, review all changes with &lt;tt&gt;git diff&lt;/tt&gt; as a final check before creating your release commit. Once you are satisfied that all changes are correct, commit your changes locally. Once committed, create the release tag locally; all release tags should be the version number you are creating and should match the output of &lt;tt&gt;Joomla\CMS\Version::getShortVersion()&lt;/tt&gt; (so if you have created 3.9.0-beta2 then the tag should be named 3.9.0-beta2).<br /> <br /> Once the tag has been created, you will run the &lt;tt&gt;build/build.php&lt;/tt&gt; script to generate the release packages. To ensure a clean build is produced, the script makes an archive of the tag you are building using the &lt;tt&gt;git archive&lt;/tt&gt; command and extracts this to the &lt;tt&gt;build/tmp/&lt;timestamp&gt;&lt;/tt&gt; directory. Depending on the patch version number, the following packages will be created in the &lt;tt&gt;build/tmp/packages&lt;/tt&gt;:<br /> <br /> * 0: Full installation and upgrade packages<br /> * 1: Full installation, upgrade packages, and patch packages for x.y.0 to x.y.1<br /> * 2+: Full installation, upgrade packages, patch packages for x.y.0 to x.y.&lt;new&gt; and x.y.&lt;new-1&gt; to x.y.&lt;new&gt; (i.e. when creating 3.8.8 this will create a patch package suitable for all 3.8.x releases and an optimized patch package for 3.8.7 to 3.8.8)<br /> <br /> Additionally, the script will generate a &lt;tt&gt;build/tmp/checksums.txt&lt;/tt&gt; file with the checksums for all generated packages. &lt;tt&gt;build/tmp/github_release.txt&lt;/tt&gt; is also produced which is a text template used for the GitHub releases.<br /> <br /> After the packages are created, you should validate that you are able to install and update a site using the ZIP packages (as these are the most frequently used type and served by our update system).<br /> <br /> == Publishing a Release ==<br /> === Release Packages ===<br /> Depending on the type of release being created, you will publish the release packages in different locations.<br /> <br /> ==== Alpha, Beta, Release Candidate ====<br /> The packages for these releases are uploaded to GitHub. When ready to publish, you should push the release tag you created to GitHub and use their interface to create a release from the tag and upload the packages.<br /> <br /> ==== Stable ====<br /> The packages for stable releases are uploaded to multiple locations, this is in part driven by the fact that the Amazon Web Services (AWS) S3 region used by Joomla is blocked in some locations therefore download mirrors are available when necessary.<br /> <br /> Note that the Joomla! Downloads Portal release can be done in advance (as long as the release is kept unpublished until release day). The Update server and GitHub releases are public by default and therefore should only be done at the time of release.<br /> <br /> ===== Joomla! Downloads Portal =====<br /> The canonical source for all stable releases is the [https://downloads.joomla.org/ Joomla! Downloads Portal]. The packages served from the site use Joomla's AWS account. You will need to log into the AWS console to upload the packages to S3 under the &lt;tt&gt;joomla-official-downloads&lt;/tt&gt; bucket. The exact path inside the bucket is &lt;tt&gt;joomladownloads/joomla&lt;version&gt;&lt;/tt&gt; where &lt;tt&gt;&lt;version&gt;&lt;/tt&gt; is the major version number (i.e. &lt;tt&gt;joomla3&lt;/tt&gt;), note for compatibility with Akeeba Release System folders for each individual release are not used. You can use [https://aws.amazon.com/cli/ AWS CLI] to upload these files - but MFA is still required - follow the procedure documented [https://aws.amazon.com/premiumsupport/knowledge-center/authenticate-mfa-cli/ here] or use a tool to automate this such as [https://github.com/broamski/aws-mfa AWS-MFA]<br /> <br /> Once files have been uploaded to S3 then you need to generate the release in Akeeba Release System on the Downloads Portal. To generate all required items quickly it's recommended to use the &lt;tt&gt;cli/ars-create-cms-release.php&lt;/tt&gt; script - the source for this can be found on [https://github.com/joomla/downloads.joomla.org/blob/master/www/cli/ars-create-cms-release.php Github].<br /> <br /> Note that if you need to rebuild a package - for example because issues are found in the release candidate - you do not need to re-create the ARS resources but simply delete and reupload the S3 packages then use the &lt;tt&gt;cli/ars-get-hashes.php&lt;/tt&gt; script on the downloads site (which simply update the checksums for each item in the release) - source code for this is also located at [https://github.com/joomla/downloads.joomla.org/blob/master/www/cli/ars-get-hashes.php Github].<br /> <br /> ===== Joomla! Update Server =====<br /> The Joomla! Update Server is used as a mirror for the download packages. After connecting to the server, you should create a new folder at &lt;tt&gt;www/releases/&lt;version&gt;&lt;/tt&gt; (i.e. &lt;tt&gt;www/releases/3.9.1&lt;/tt&gt; for the 3.9.1 release) and upload the packages here.<br /> <br /> ===== GitHub =====<br /> The packages are also uploaded to GitHub. This is similar to the steps for alpha, beta, and release candidate releases above. Note that you only need to push the release tag at this point (i.e. &lt;tt&gt;git push --tags&lt;/tt&gt;), you can wait to push the updated release branch until after the release is available.<br /> <br /> === Announcements ===<br /> ==== joomla.org ====<br /> For all stable releases, the main release announcement is published to the &lt;tt&gt;Joomla! Official News &gt; Project Release News&lt;/tt&gt; category on the main &lt;tt&gt;joomla.org&lt;/tt&gt; website. This is primarily handled by the Marketing team - however release leads are expected to contribute to the ''Bug fixes and Improvements'' section as well as highlighting any other information that may need to be called out as part of release notes. After release the Social Media team need to be made aware to ensure the release is available on social media - use the ''Contact the Social Media Team'' Channel on Glip.<br /> <br /> For a minor release, an updated version of the landing page at &lt;tt&gt;joomla.org/4&lt;/tt&gt; (previously &lt;tt&gt;joomla.org/3&lt;/tt&gt;) is published. Generally, this site is backed up from the sandbox location and transferred to the live domain shortly before release, this transfer should be coordinated with the [https://volunteers.joomla.org/teams/webmasters-team Webmasters Team].<br /> <br /> ==== developer.joomla.org ====<br /> For security releases, all accompanying articles are published to the &lt;tt&gt;News &gt; Security Centre&lt;/tt&gt; category on the Joomla! Developer Network. As these articles are referenced from the main release announcement, these should be published at the same time.<br /> <br /> == Update Server ==<br /> The update server must be updated to alert websites that a core update is available, this subdomain is managed on GitHub at https://github.com/joomla/update.joomla.org. Prior to each release, a pull request should be prepared with necessary changes for the release (generally this updates the version number, announcement URL, package URLs, and package checksums for the stable release and updating the version number for the nightly builds), see https://github.com/joomla/update.joomla.org/pull/117 as an example of this update for the 3.9.1 release. Pushes to the &lt;tt&gt;master&lt;/tt&gt; branch of this repo are automatically deployed thanks to a Jenkins job, notifications for many of the Jenkins jobs are sent to the &lt;tt&gt;.org Build Notifications&lt;/tt&gt; channel on RingCentral Glip so you should ensure a success notification was sent here otherwise check if there was an issue with the job and/or manually deploy the updated files.<br /> <br /> Note that the &lt;tt&gt;update.joomla.org&lt;/tt&gt; subdomain is behind a CDN and it generally takes 5-10 minutes for all nodes to update, if need be you can access &lt;tt&gt;update1.joomla.org&lt;/tt&gt; to verify the right files are deployed without using the CDN. Note files cache times aren't consistent and often we've seen issues where the list update file is the new version and the extension.xml file is on the old version.<br /> <br /> == Post Release Actions ==<br /> Once the release is published, there are several additional tasks that should be completed shortly after.<br /> <br /> === Post-Release Version Bump ===<br /> The version should be bumped to the next version scheduled for release using the &lt;tt&gt;build/bump.php&lt;/tt&gt; script (i.e. after the 3.9.1 release this would be bumped to 3.9.2-dev).<br /> <br /> === Branch Merging ===<br /> After incrementing the version number, you should merge all the release changes forward to other active branches (especially in the case of a security release). Ensure you pay careful attention while resolving merge conflicts, when making a merge that includes a version bump generally all files which contain the version string and/or release date will be in conflict (as of this writing this is 8 files).<br /> <br /> === Push Updated Branches ===<br /> When ready, you should directly push your updates to the Git repo. If you elect to use pull requests, the pull requests should NEVER be squashed or rebased otherwise this will wipe out Git's awareness of the merged commits and will make your next branch merges even more complex. Likewise, as an example, if the commit preparing the 3.9.1 release and bumping the version string to 3.9.2-dev were squash merged as a pull request, then the commit that the 3.9.1 release was tagged from would not be in the repository.<br /> <br /> === Update Release Milestones ===<br /> On GitHub, all merged items are assigned to a milestone to help organize items. With each release, the [https://github.com/joomla/joomla-cms/milestones milestones] should be updated to ensure that the milestone for the release you created has been closed and a milestone for the next release is open.<br /> <br /> === Regenerate Nightly Builds ===<br /> The nightly builds for any branch updated during the release process should be regenerated to include the release's changes. These can be manually triggered within the &lt;tt&gt;CMS Packaging&lt;/tt&gt; folder on the Jenkins server.<br /> <br /> === Website Updates ===<br /> With all code updates pushed, there are several website updates that need to be triggered.<br /> <br /> ==== api.joomla.org ====<br /> With each release, an updated build of the API documentation should be deployed to the &lt;tt&gt;api.joomla.org&lt;/tt&gt; website. These updates are triggered with the &lt;tt&gt;Joomla! API &gt; Deploy Docs - CMS&lt;/tt&gt; job on Jenkins. As this job relies on the release tags from the CMS repo, this can only be done after the release tag has been pushed.<br /> <br /> ==== developer.joomla.org ====<br /> After a release, the &lt;tt&gt;Joomla! Project Roadmap&lt;/tt&gt; article in the &lt;tt&gt;Uncategorised&lt;/tt&gt; category should be updated to reflect the newly released version and updated links, as well as adding expected release dates for the next release.<br /> <br /> The version whitelist for the statistics server should also be updated to allow the next version to be submitted; if you have not already, you should have a clone of the https://github.com/joomla/statistics-server repository on your local system. Once cloned and set up, run the &lt;tt&gt;bin/stats tags:joomla&lt;/tt&gt; command to regenerate the Joomla version whitelist. As this command relies on the release tags from the CMS repo, this can only be done after the release tag has been pushed. The updated &lt;tt&gt;versions/joomla.json&lt;/tt&gt; should be committed and pushed, and a Jenkins job will deploy the updated site resources.<br /> <br /> == Additional Considerations ==<br /> The release manager or a delegate is suggested to be in communication with the Webmasters Team to ensure the &lt;tt&gt;joomla.org&lt;/tt&gt; websites are updated in a timely manner. When a security release is scheduled, it is encouraged to share the update release package with the team so that our sites may be updated before the fix is made public to mitigate the chance of the vulnerability being used to exploit one of our sites. It also provides additional testing for security fixes on real world sites in addition to the tests performed by the CMS Release Team.<br /> <br /> = Framework Release Cycle =<br /> The packages of the Joomla Framework are on an independent lifecycle meaning each package can be updated and released independently of all others. Generally the only restriction is with major releases, which should coincide with the CMS release cycle (i.e. CMS 3.x uses Framework 1.x, CMS 4.x will use Framework 2.x therefore Framework 2.0 stable releases should not be made until the CMS is in its beta phase at the earliest).<br /> <br /> == Tagging a Release ==<br /> Most packages can be tagged and released through the &lt;tt&gt;Joomla! Framework &gt; Package Release&lt;/tt&gt; job on Jenkins, however as of this writing this job only supports tagging releases from a repository's &lt;tt&gt;master&lt;/tt&gt; branch. To tag a release, select the package you wish to update and specify the version you are releasing in the job's parameters and run the job; all releases should follow Semantic Versioning to set the correct number.<br /> <br /> Once the job has completed, you should verify the new release is visible on [https://packagist.org/packages/joomla/ Packagist]. Within a day, the new update should be visible on the [https://framework.joomla.org/status Joomla Framework Status page] (the database is updated via cron job reading from Packagist's API), if the updated version isn't seen on the site in a relatively timely manner you should clone the website locally and debug the &lt;tt&gt;packagist:sync:releases&lt;/tt&gt; command.<br /> <br /> == Security Releases ==<br /> When a security release is created, a pull request should be sent to the [https://github.com/FriendsOfPHP/security-advisories FriendsOfPHP/security-advisories repository] with relevant details. This repository is used by many tools in the PHP and Composer ecosystem to alert users of security issues. https://github.com/FriendsOfPHP/security-advisories/pull/134 is an example of this pull request.<br /> <br /> == Onboarding Release Leads ==<br /> Release Leads will need access to a number of resources. The following are required:<br /> * Account on Github (added to [https://github.com/orgs/joomla/teams/cms-release-leads/members the CMS Release Leads team] for the Joomla Org (which also provides jenkins access) and [https://github.com/orgs/joomla-backports/teams/cms-release-leads the CMS Release Leads team] for the Joomla Backport org.<br /> * The Forum (Ensure users are aware of release groups)<br /> * Glip (CMS Maintainers, CMS Release Leads, WebMasters Team, JSST)<br /> * Introduction with Translation, JSST and Webmaster Liasons<br /> * SSH keys added to Update and Downloads servers<br /> * Downloads Website (Release Leads -&gt; CMS ACL Group)<br /> * AWS Account in Release_Managers Group. User must reset password and setup MFA.<br /> <br /> [[Category:Bug Squad]]<br /> [[Category:Coordinators]]<br /> [[Category:Development]]</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Joomla:Release_procedure_and_checklist&diff=876793 2022-01-30T17:53:33Z

<p>Wilsonge: /* Onboarding Release Leads */</p> <hr /> <div>{{RightTOC}}<br /> <br /> This is a general procedure explanation for managing releases of Joomla! and the Joomla! Framework. This list is best suited for a [[Minor Release]] or [[Maintenance Release]], however the steps will generally apply to a [[Major Release]] as well but will require some judgement calls from the release manager and/or leadership team.<br /> <br /> There is a more formal checklist available [https://github.com/joomla/joomla-cms/blob/4.1-dev/build/release-checklist.md on GitHub] for release leads to use that is intended to complement the steps described in this page.<br /> <br /> == Issue Triage, Patch Review, Merging Patches ==<br /> The release cycle for a new software version begins immediately after the previous one is completed. In the immediate hours and days after a release, the [https://github.com/joomla/joomla-cms issue tracker] and [https://forum.joomla.org/ support forums], in close coordination with the [https://volunteers.joomla.org/teams/bug-squad Bug Squad] and [https://volunteers.joomla.org/teams/cms-release-team CMS Release Team], should be monitored for reports of potential regressions or critical bugs that would warrant a quick follow-on release to address the issue. It is generally suggested to wait 48-72 hours before resuming merging of reviewed and ready for commit pull requests to keep the release branch &quot;clean&quot; and ready for a release (note this is only a suggestion, if need be a release manager could create a branch from the release tag however this involves a bit more effort therefore this suggestion is for simplicity's sake).<br /> <br /> Throughout the release cycle, the release manager should be involved with reviewing patches and merging reviewed patches to the appropriate release branch. As of this writing (where 4.0.6 is the present release), the following branches are generally active:<br /> <br /> * &lt;tt&gt;3.10-dev&lt;/tt&gt;: This is the 3.x branch, generally only bug fixes and &quot;general&quot; maintenance work should merge to this branch.<br /> * &lt;tt&gt;4.0-dev&lt;/tt&gt;: This is the 4.0.x branch - there are no more intended releases to this branch unless required by security fixes.<br /> * &lt;tt&gt;4.1-dev&lt;/tt&gt;: This is the main release branch and is where most activity occurs, generally only bug fixes and &quot;general&quot; maintenance work should merge to this branch although minor features may be merged at the discretion of the release manager and/or leadership team. All code from 3.10-dev is merged into this branch.<br /> * &lt;tt&gt;4.2-dev&lt;/tt&gt;: This is the release branch for the next minor release (the branch's name will always be the version it represents), new features should be merged to this branch<br /> <br /> === Branch Merging ===<br /> All branches should remain in-sync and all work should be regularly merged forward. Given the above example, the following is the recommended merging workflow (in general, the suggested workflow is that 3.10-dev is merged to the current 4.x-dev branch and then through to the next minor branch):<br /> <br /> * &lt;tt&gt;3.10-dev&lt;/tt&gt; should be merged into &lt;tt&gt;4.0-dev&lt;/tt&gt;<br /> * &lt;tt&gt;4.0-dev&lt;/tt&gt; should be merged to &lt;tt&gt;4.1-dev&lt;/tt&gt;<br /> * &lt;tt&gt;4.1-dev&lt;/tt&gt; should be merged to &lt;tt&gt;4.2-dev&lt;/tt&gt;<br /> <br /> It is suggested that at least once per week branch merging occurs.<br /> <br /> == Preparing To Release ==<br /> When scheduling and preparing a release, the timeline should be communicated with the Production and Marketing &amp; Communication Department leadership so that all teams are prepared to support the release. Note that when scheduling releases, consideration should be given to holidays around the world and the impact of issuing a release near those periods considered. Helpful resources include http://interfaith-calendar.org/ and https://www.timeanddate.com/holidays/<br /> <br /> === Review Release Milestone and Blockers ===<br /> On GitHub, check the [https://github.com/joomla/joomla-cms/milestones milestone] for the release you are preparing to create and for any open items with the [https://github.com/joomla/joomla-cms/labels/release-blocker release-blocker] label. If there are remaining open items, review them to determine if they are items that should be included in the release or if they can be rescheduled to a later release.<br /> <br /> === Release Schedule ===<br /> ==== Minor Release ====<br /> Given the nature of a minor release, the following is the suggested release timeline:<br /> <br /> * Six weeks prior to planned stable release: Tag the first Beta release<br /> ** At this point the release should be considered feature complete and new features should be deferred to the next minor release<br /> * Weekly Beta releases should follow this until the Release Candidate<br /> * Two weeks prior to planned stable release: Tag the Release Candidate<br /> ** At this point the release branch(es) should remain closed for committing except for high priority bug fixes and language updates<br /> ** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the &quot;no later than&quot; time<br /> ** Inform the CMS Release Team and call out anything that you would like extra testing on<br /> * One week prior to planned stable release: If necessary, create a second Release Candidate<br /> * 2-3 days before release: Build final packages - share with CMS Release Team and do release preparation activities.<br /> * Planned release date: Tag the stable release<br /> <br /> ==== Maintenance Release ====<br /> Maintenance releases operate on a 4-6 week cycle and the following is the suggested release timeline:<br /> <br /> * 9-10 days before planned release date: Tag a Release Candidate<br /> ** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the &quot;no later than&quot; time<br /> ** Inform the CMS Release Team and call out anything that you would like extra testing on<br /> * 2-3 days before release: Build final packages - share with CMS Release Team and do release preparation activities.<br /> * Planned release date: Tag the stable release<br /> <br /> === Reviewing Release Changes ===<br /> Before tagging a release, the list of changes in the release should be reviewed by the release manager and/or leadership team. The list of changes can be found using GitHub's compare function with the URL &lt;tt&gt;https://github.com/joomla/joomla-cms/compare/&lt;version&gt;...4.1-dev&lt;/tt&gt; which will compare the changes from &lt;tt&gt;&lt;version&gt;&lt;/tt&gt; to the current 4.1-dev branch (for example, https://github.com/joomla/joomla-cms/compare/3.9.0...3.9.1-rc is the comparison from the 3.9.0 release tag to the 3.9.1-rc tag). Key purposes of this review include:<br /> <br /> * Ensuring all patches are compliant with Semantic Versioning (SemVer) (i.e. no backward compatibility breaks in minor or maintenance releases and no features in maintenance releases); SemVer violations should be cleared with the Production Department leadership<br /> * Ensuring all code revisions are compatible with Joomla's minimum supported versions (i.e. no PHP 5.4 syntax in 3.x releases where PHP 5.3 is the minimum supported version, exceptions may be made if introducing a code path and files that will only be executed on newer PHP versions)<br /> ** Joomla's testing integrations should not be relied on in full for this as there are large portions of the Joomla code base which do not have automated test coverage, and as of this writing, there is not a code linting process in place checking for potential issues<br /> * Ensuring features and &quot;significant&quot; changes are documented<br /> <br /> === Security Fixes ===<br /> From time to time, security fixes must be included in a release. Prior to every release, the release manager should check with the [https://volunteers.joomla.org/teams/security-strike-team Security Strike Team] to determine if security fixes are required, and if so ensure this is communicated to all members involved with release work (i.e. the marketing team liaison who assists with the publication of release related material). When a security release is necessary, an internal Release Candidate should be built for testing by the Security Strike Team, CMS Release Team, and [https://volunteers.joomla.org/teams/cms-maintenance-team CMS Maintenance Team] with all security patches included. These teams should also receive information about the vulnerabilities being addressed to ensure there are no regressions in the impacted areas.<br /> <br /> Note, when a security fix involves a Joomla Framework package, the Framework package should be patched first and a release created of the affected package then the CMS updated with &lt;tt&gt;composer update&lt;/tt&gt;.<br /> <br /> Sometimes security fixes are required for composer dependencies that are out of support. In such cases we fork the 3rd party dependency into https://github.com/joomla-backports and then apply security fixes there in a &lt;tt&gt;joomla-backports&lt;/tt&gt; branch (and override the [https://github.com/joomla/joomla-cms/blob/3.10.5/composer.json#L28-L32 repository in composer.json] and as well as the branch reference [https://github.com/joomla/joomla-cms/blob/3.10.5/composer.json#L54 here]. Links are a sample for PHPMailer overrides in Joomla 3.10).<br /> <br /> === Release FAQ ===<br /> Create Release FAQ Category on the Joomla Documentation site. (i.e. Clone the contents of an existing page such as [https://docs.joomla.org/Category:Version_4.0.6_FAQ FAQ] and update the version number to your required version)<br /> <br /> == Building a Release ==<br /> Building a release starts with checking that any files and folders that have been deleted are included in the arrays in the installer script at &lt;tt&gt;administrator/components/com_admin/script.php&lt;/tt&gt;. There is a helper script in the repository to assist with this located at &lt;tt&gt;build/deleted_file_check.php&lt;/tt&gt;. Running &lt;tt&gt;php build/deleted_file_check.php&lt;/tt&gt; with its required &lt;tt&gt;--from&lt;/tt&gt; option will write a file to &lt;tt&gt;build/deleted_files.txt&lt;/tt&gt; with the list of files deleted since the from reference. Please see the PHP file for all documentation about this script.<br /> <br /> The following steps require the individual to create commits and tags. It is suggested that these commits and tags be GPG signed as an extra security step but this is not a mandatory requirement as of this writing.<br /> <br /> If creating a security release, at this point you should apply all patches provided by the security team.<br /> <br /> Once it is confirmed that the deleted files listing is correct, the &lt;tt&gt;build/bump.php&lt;/tt&gt; script should be executed to set the new version number. This script will also perform maintenance steps such as correcting the copyright year ranges for all files and replacing the &lt;tt&gt;__DEPLOY_VERSION__&lt;/tt&gt; placeholder. Please see the file for all documentation about this script.<br /> <br /> After running this script, review all changes with &lt;tt&gt;git diff&lt;/tt&gt; as a final check before creating your release commit. Once you are satisfied that all changes are correct, commit your changes locally. Once committed, create the release tag locally; all release tags should be the version number you are creating and should match the output of &lt;tt&gt;Joomla\CMS\Version::getShortVersion()&lt;/tt&gt; (so if you have created 3.9.0-beta2 then the tag should be named 3.9.0-beta2).<br /> <br /> Once the tag has been created, you will run the &lt;tt&gt;build/build.php&lt;/tt&gt; script to generate the release packages. To ensure a clean build is produced, the script makes an archive of the tag you are building using the &lt;tt&gt;git archive&lt;/tt&gt; command and extracts this to the &lt;tt&gt;build/tmp/&lt;timestamp&gt;&lt;/tt&gt; directory. Depending on the patch version number, the following packages will be created in the &lt;tt&gt;build/tmp/packages&lt;/tt&gt;:<br /> <br /> * 0: Full installation and upgrade packages<br /> * 1: Full installation, upgrade packages, and patch packages for x.y.0 to x.y.1<br /> * 2+: Full installation, upgrade packages, patch packages for x.y.0 to x.y.&lt;new&gt; and x.y.&lt;new-1&gt; to x.y.&lt;new&gt; (i.e. when creating 3.8.8 this will create a patch package suitable for all 3.8.x releases and an optimized patch package for 3.8.7 to 3.8.8)<br /> <br /> Additionally, the script will generate a &lt;tt&gt;build/tmp/checksums.txt&lt;/tt&gt; file with the checksums for all generated packages. &lt;tt&gt;build/tmp/github_release.txt&lt;/tt&gt; is also produced which is a text template used for the GitHub releases.<br /> <br /> After the packages are created, you should validate that you are able to install and update a site using the ZIP packages (as these are the most frequently used type and served by our update system).<br /> <br /> == Publishing a Release ==<br /> === Release Packages ===<br /> Depending on the type of release being created, you will publish the release packages in different locations.<br /> <br /> ==== Alpha, Beta, Release Candidate ====<br /> The packages for these releases are uploaded to GitHub. When ready to publish, you should push the release tag you created to GitHub and use their interface to create a release from the tag and upload the packages.<br /> <br /> ==== Stable ====<br /> The packages for stable releases are uploaded to multiple locations, this is in part driven by the fact that the Amazon Web Services (AWS) S3 region used by Joomla is blocked in some locations therefore download mirrors are available when necessary.<br /> <br /> Note that the Joomla! Downloads Portal release can be done in advance (as long as the release is kept unpublished until release day). The Update server and GitHub releases are public by default and therefore should only be done at the time of release.<br /> <br /> ===== Joomla! Downloads Portal =====<br /> The canonical source for all stable releases is the [https://downloads.joomla.org/ Joomla! Downloads Portal]. The packages served from the site use Joomla's AWS account. You will need to log into the AWS console to upload the packages to S3 under the &lt;tt&gt;joomla-official-downloads&lt;/tt&gt; bucket. The exact path inside the bucket is &lt;tt&gt;joomladownloads/joomla&lt;version&gt;&lt;/tt&gt; where &lt;tt&gt;&lt;version&gt;&lt;/tt&gt; is the major version number (i.e. &lt;tt&gt;joomla3&lt;/tt&gt;), note for compatibility with Akeeba Release System folders for each individual release are not used. You can use [https://aws.amazon.com/cli/ AWS CLI] to upload these files - but MFA is still required - follow the procedure documented [https://aws.amazon.com/premiumsupport/knowledge-center/authenticate-mfa-cli/ here] or use a tool to automate this such as [https://github.com/broamski/aws-mfa AWS-MFA]<br /> <br /> Once files have been uploaded to S3 then you need to generate the release in Akeeba Release System on the Downloads Portal. To generate all required items quickly it's recommended to use the &lt;tt&gt;cli/ars-create-cms-release.php&lt;/tt&gt; script - the source for this can be found on [https://github.com/joomla/downloads.joomla.org/blob/master/www/cli/ars-create-cms-release.php Github].<br /> <br /> Note that if you need to rebuild a package - for example because issues are found in the release candidate - you do not need to re-create the ARS resources but simply delete and reupload the S3 packages then use the &lt;tt&gt;cli/ars-get-hashes.php&lt;/tt&gt; script on the downloads site (which simply update the checksums for each item in the release) - source code for this is also located at [https://github.com/joomla/downloads.joomla.org/blob/master/www/cli/ars-get-hashes.php Github].<br /> <br /> ===== Joomla! Update Server =====<br /> The Joomla! Update Server is used as a mirror for the download packages. After connecting to the server, you should create a new folder at &lt;tt&gt;www/releases/&lt;version&gt;&lt;/tt&gt; (i.e. &lt;tt&gt;www/releases/3.9.1&lt;/tt&gt; for the 3.9.1 release) and upload the packages here.<br /> <br /> ===== GitHub =====<br /> The packages are also uploaded to GitHub. This is similar to the steps for alpha, beta, and release candidate releases above. Note that you only need to push the release tag at this point (i.e. &lt;tt&gt;git push --tags&lt;/tt&gt;), you can wait to push the updated release branch until after the release is available.<br /> <br /> === Announcements ===<br /> ==== joomla.org ====<br /> For all stable releases, the main release announcement is published to the &lt;tt&gt;Joomla! Official News &gt; Project Release News&lt;/tt&gt; category on the main &lt;tt&gt;joomla.org&lt;/tt&gt; website. This is primarily handled by the Marketing team - however release leads are expected to contribute to the ''Bug fixes and Improvements'' section as well as highlighting any other information that may need to be called out as part of release notes. After release the Social Media team need to be made aware to ensure the release is available on social media - use the ''Contact the Social Media Team'' Channel on Glip.<br /> <br /> For a minor release, an updated version of the landing page at &lt;tt&gt;joomla.org/4&lt;/tt&gt; (previously &lt;tt&gt;joomla.org/3&lt;/tt&gt;) is published. Generally, this site is backed up from the sandbox location and transferred to the live domain shortly before release, this transfer should be coordinated with the [https://volunteers.joomla.org/teams/webmasters-team Webmasters Team].<br /> <br /> ==== developer.joomla.org ====<br /> For security releases, all accompanying articles are published to the &lt;tt&gt;News &gt; Security Centre&lt;/tt&gt; category on the Joomla! Developer Network. As these articles are referenced from the main release announcement, these should be published at the same time.<br /> <br /> == Update Server ==<br /> The update server must be updated to alert websites that a core update is available, this subdomain is managed on GitHub at https://github.com/joomla/update.joomla.org. Prior to each release, a pull request should be prepared with necessary changes for the release (generally this updates the version number, announcement URL, package URLs, and package checksums for the stable release and updating the version number for the nightly builds), see https://github.com/joomla/update.joomla.org/pull/117 as an example of this update for the 3.9.1 release. Pushes to the &lt;tt&gt;master&lt;/tt&gt; branch of this repo are automatically deployed thanks to a Jenkins job, notifications for many of the Jenkins jobs are sent to the &lt;tt&gt;.org Build Notifications&lt;/tt&gt; channel on RingCentral Glip so you should ensure a success notification was sent here otherwise check if there was an issue with the job and/or manually deploy the updated files.<br /> <br /> Note that the &lt;tt&gt;update.joomla.org&lt;/tt&gt; subdomain is behind a CDN and it generally takes 5-10 minutes for all nodes to update, if need be you can access &lt;tt&gt;update1.joomla.org&lt;/tt&gt; to verify the right files are deployed without using the CDN. Note files cache times aren't consistent and often we've seen issues where the list update file is the new version and the extension.xml file is on the old version.<br /> <br /> == Post Release Actions ==<br /> Once the release is published, there are several additional tasks that should be completed shortly after.<br /> <br /> === Post-Release Version Bump ===<br /> The version should be bumped to the next version scheduled for release using the &lt;tt&gt;build/bump.php&lt;/tt&gt; script (i.e. after the 3.9.1 release this would be bumped to 3.9.2-dev).<br /> <br /> === Branch Merging ===<br /> After incrementing the version number, you should merge all the release changes forward to other active branches (especially in the case of a security release). Ensure you pay careful attention while resolving merge conflicts, when making a merge that includes a version bump generally all files which contain the version string and/or release date will be in conflict (as of this writing this is 8 files).<br /> <br /> === Push Updated Branches ===<br /> When ready, you should directly push your updates to the Git repo. If you elect to use pull requests, the pull requests should NEVER be squashed or rebased otherwise this will wipe out Git's awareness of the merged commits and will make your next branch merges even more complex. Likewise, as an example, if the commit preparing the 3.9.1 release and bumping the version string to 3.9.2-dev were squash merged as a pull request, then the commit that the 3.9.1 release was tagged from would not be in the repository.<br /> <br /> === Update Release Milestones ===<br /> On GitHub, all merged items are assigned to a milestone to help organize items. With each release, the [https://github.com/joomla/joomla-cms/milestones milestones] should be updated to ensure that the milestone for the release you created has been closed and a milestone for the next release is open.<br /> <br /> === Regenerate Nightly Builds ===<br /> The nightly builds for any branch updated during the release process should be regenerated to include the release's changes. These can be manually triggered within the &lt;tt&gt;CMS Packaging&lt;/tt&gt; folder on the Jenkins server.<br /> <br /> === Website Updates ===<br /> With all code updates pushed, there are several website updates that need to be triggered.<br /> <br /> ==== api.joomla.org ====<br /> With each release, an updated build of the API documentation should be deployed to the &lt;tt&gt;api.joomla.org&lt;/tt&gt; website. These updates are triggered with the &lt;tt&gt;Joomla! API &gt; Deploy Docs - CMS&lt;/tt&gt; job on Jenkins. As this job relies on the release tags from the CMS repo, this can only be done after the release tag has been pushed.<br /> <br /> ==== developer.joomla.org ====<br /> After a release, the &lt;tt&gt;Joomla! Project Roadmap&lt;/tt&gt; article in the &lt;tt&gt;Uncategorised&lt;/tt&gt; category should be updated to reflect the newly released version and updated links, as well as adding expected release dates for the next release.<br /> <br /> The version whitelist for the statistics server should also be updated to allow the next version to be submitted; if you have not already, you should have a clone of the https://github.com/joomla/statistics-server repository on your local system. Once cloned and set up, run the &lt;tt&gt;bin/stats tags:joomla&lt;/tt&gt; command to regenerate the Joomla version whitelist. As this command relies on the release tags from the CMS repo, this can only be done after the release tag has been pushed. The updated &lt;tt&gt;versions/joomla.json&lt;/tt&gt; should be committed and pushed, and a Jenkins job will deploy the updated site resources.<br /> <br /> == Additional Considerations ==<br /> The release manager or a delegate is suggested to be in communication with the Webmasters Team to ensure the &lt;tt&gt;joomla.org&lt;/tt&gt; websites are updated in a timely manner. When a security release is scheduled, it is encouraged to share the update release package with the team so that our sites may be updated before the fix is made public to mitigate the chance of the vulnerability being used to exploit one of our sites. It also provides additional testing for security fixes on real world sites in addition to the tests performed by the CMS Release Team.<br /> <br /> = Framework Release Cycle =<br /> The packages of the Joomla Framework are on an independent lifecycle meaning each package can be updated and released independently of all others. Generally the only restriction is with major releases, which should coincide with the CMS release cycle (i.e. CMS 3.x uses Framework 1.x, CMS 4.x will use Framework 2.x therefore Framework 2.0 stable releases should not be made until the CMS is in its beta phase at the earliest).<br /> <br /> == Tagging a Release ==<br /> Most packages can be tagged and released through the &lt;tt&gt;Joomla! Framework &gt; Package Release&lt;/tt&gt; job on Jenkins, however as of this writing this job only supports tagging releases from a repository's &lt;tt&gt;master&lt;/tt&gt; branch. To tag a release, select the package you wish to update and specify the version you are releasing in the job's parameters and run the job; all releases should follow Semantic Versioning to set the correct number.<br /> <br /> Once the job has completed, you should verify the new release is visible on [https://packagist.org/packages/joomla/ Packagist]. Within a day, the new update should be visible on the [https://framework.joomla.org/status Joomla Framework Status page] (the database is updated via cron job reading from Packagist's API), if the updated version isn't seen on the site in a relatively timely manner you should clone the website locally and debug the &lt;tt&gt;packagist:sync:releases&lt;/tt&gt; command.<br /> <br /> == Security Releases ==<br /> When a security release is created, a pull request should be sent to the [https://github.com/FriendsOfPHP/security-advisories FriendsOfPHP/security-advisories repository] with relevant details. This repository is used by many tools in the PHP and Composer ecosystem to alert users of security issues. https://github.com/FriendsOfPHP/security-advisories/pull/134 is an example of this pull request.<br /> <br /> == Onboarding Release Leads ==<br /> Release Leads will need access to a number of resources. The following are required:<br /> * Account on Github (added to [https://github.com/orgs/joomla/teams/cms-release-leads/members the CMS Release Leads team] for the Joomla Org (which also provides jenkins access) and [https://github.com/orgs/joomla-backports/teams/cms-release-leads the CMS Release Leads team] for the Joomla Backport org.<br /> * The Forum (Ensure users are aware of release groups)<br /> * Glip (CMS Maintainers, CMS Release Leads, WebMasters Team, JSST)<br /> * Introduction with Translation, JSST and Webmaster Liasons<br /> * SSH keys added to Update and Downloads servers<br /> * Downloads Website (Release Leads -&gt; CMS ACL Group)<br /> * AWS Account in Release_Managers Group<br /> <br /> [[Category:Bug Squad]]<br /> [[Category:Coordinators]]<br /> [[Category:Development]]</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Joomla:Release_procedure_and_checklist&diff=876792 2022-01-30T17:53:08Z

<p>Wilsonge: </p> <hr /> <div>{{RightTOC}}<br /> <br /> This is a general procedure explanation for managing releases of Joomla! and the Joomla! Framework. This list is best suited for a [[Minor Release]] or [[Maintenance Release]], however the steps will generally apply to a [[Major Release]] as well but will require some judgement calls from the release manager and/or leadership team.<br /> <br /> There is a more formal checklist available [https://github.com/joomla/joomla-cms/blob/4.1-dev/build/release-checklist.md on GitHub] for release leads to use that is intended to complement the steps described in this page.<br /> <br /> == Issue Triage, Patch Review, Merging Patches ==<br /> The release cycle for a new software version begins immediately after the previous one is completed. In the immediate hours and days after a release, the [https://github.com/joomla/joomla-cms issue tracker] and [https://forum.joomla.org/ support forums], in close coordination with the [https://volunteers.joomla.org/teams/bug-squad Bug Squad] and [https://volunteers.joomla.org/teams/cms-release-team CMS Release Team], should be monitored for reports of potential regressions or critical bugs that would warrant a quick follow-on release to address the issue. It is generally suggested to wait 48-72 hours before resuming merging of reviewed and ready for commit pull requests to keep the release branch &quot;clean&quot; and ready for a release (note this is only a suggestion, if need be a release manager could create a branch from the release tag however this involves a bit more effort therefore this suggestion is for simplicity's sake).<br /> <br /> Throughout the release cycle, the release manager should be involved with reviewing patches and merging reviewed patches to the appropriate release branch. As of this writing (where 4.0.6 is the present release), the following branches are generally active:<br /> <br /> * &lt;tt&gt;3.10-dev&lt;/tt&gt;: This is the 3.x branch, generally only bug fixes and &quot;general&quot; maintenance work should merge to this branch.<br /> * &lt;tt&gt;4.0-dev&lt;/tt&gt;: This is the 4.0.x branch - there are no more intended releases to this branch unless required by security fixes.<br /> * &lt;tt&gt;4.1-dev&lt;/tt&gt;: This is the main release branch and is where most activity occurs, generally only bug fixes and &quot;general&quot; maintenance work should merge to this branch although minor features may be merged at the discretion of the release manager and/or leadership team. All code from 3.10-dev is merged into this branch.<br /> * &lt;tt&gt;4.2-dev&lt;/tt&gt;: This is the release branch for the next minor release (the branch's name will always be the version it represents), new features should be merged to this branch<br /> <br /> === Branch Merging ===<br /> All branches should remain in-sync and all work should be regularly merged forward. Given the above example, the following is the recommended merging workflow (in general, the suggested workflow is that 3.10-dev is merged to the current 4.x-dev branch and then through to the next minor branch):<br /> <br /> * &lt;tt&gt;3.10-dev&lt;/tt&gt; should be merged into &lt;tt&gt;4.0-dev&lt;/tt&gt;<br /> * &lt;tt&gt;4.0-dev&lt;/tt&gt; should be merged to &lt;tt&gt;4.1-dev&lt;/tt&gt;<br /> * &lt;tt&gt;4.1-dev&lt;/tt&gt; should be merged to &lt;tt&gt;4.2-dev&lt;/tt&gt;<br /> <br /> It is suggested that at least once per week branch merging occurs.<br /> <br /> == Preparing To Release ==<br /> When scheduling and preparing a release, the timeline should be communicated with the Production and Marketing &amp; Communication Department leadership so that all teams are prepared to support the release. Note that when scheduling releases, consideration should be given to holidays around the world and the impact of issuing a release near those periods considered. Helpful resources include http://interfaith-calendar.org/ and https://www.timeanddate.com/holidays/<br /> <br /> === Review Release Milestone and Blockers ===<br /> On GitHub, check the [https://github.com/joomla/joomla-cms/milestones milestone] for the release you are preparing to create and for any open items with the [https://github.com/joomla/joomla-cms/labels/release-blocker release-blocker] label. If there are remaining open items, review them to determine if they are items that should be included in the release or if they can be rescheduled to a later release.<br /> <br /> === Release Schedule ===<br /> ==== Minor Release ====<br /> Given the nature of a minor release, the following is the suggested release timeline:<br /> <br /> * Six weeks prior to planned stable release: Tag the first Beta release<br /> ** At this point the release should be considered feature complete and new features should be deferred to the next minor release<br /> * Weekly Beta releases should follow this until the Release Candidate<br /> * Two weeks prior to planned stable release: Tag the Release Candidate<br /> ** At this point the release branch(es) should remain closed for committing except for high priority bug fixes and language updates<br /> ** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the &quot;no later than&quot; time<br /> ** Inform the CMS Release Team and call out anything that you would like extra testing on<br /> * One week prior to planned stable release: If necessary, create a second Release Candidate<br /> * 2-3 days before release: Build final packages - share with CMS Release Team and do release preparation activities.<br /> * Planned release date: Tag the stable release<br /> <br /> ==== Maintenance Release ====<br /> Maintenance releases operate on a 4-6 week cycle and the following is the suggested release timeline:<br /> <br /> * 9-10 days before planned release date: Tag a Release Candidate<br /> ** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the &quot;no later than&quot; time<br /> ** Inform the CMS Release Team and call out anything that you would like extra testing on<br /> * 2-3 days before release: Build final packages - share with CMS Release Team and do release preparation activities.<br /> * Planned release date: Tag the stable release<br /> <br /> === Reviewing Release Changes ===<br /> Before tagging a release, the list of changes in the release should be reviewed by the release manager and/or leadership team. The list of changes can be found using GitHub's compare function with the URL &lt;tt&gt;https://github.com/joomla/joomla-cms/compare/&lt;version&gt;...4.1-dev&lt;/tt&gt; which will compare the changes from &lt;tt&gt;&lt;version&gt;&lt;/tt&gt; to the current 4.1-dev branch (for example, https://github.com/joomla/joomla-cms/compare/3.9.0...3.9.1-rc is the comparison from the 3.9.0 release tag to the 3.9.1-rc tag). Key purposes of this review include:<br /> <br /> * Ensuring all patches are compliant with Semantic Versioning (SemVer) (i.e. no backward compatibility breaks in minor or maintenance releases and no features in maintenance releases); SemVer violations should be cleared with the Production Department leadership<br /> * Ensuring all code revisions are compatible with Joomla's minimum supported versions (i.e. no PHP 5.4 syntax in 3.x releases where PHP 5.3 is the minimum supported version, exceptions may be made if introducing a code path and files that will only be executed on newer PHP versions)<br /> ** Joomla's testing integrations should not be relied on in full for this as there are large portions of the Joomla code base which do not have automated test coverage, and as of this writing, there is not a code linting process in place checking for potential issues<br /> * Ensuring features and &quot;significant&quot; changes are documented<br /> <br /> === Security Fixes ===<br /> From time to time, security fixes must be included in a release. Prior to every release, the release manager should check with the [https://volunteers.joomla.org/teams/security-strike-team Security Strike Team] to determine if security fixes are required, and if so ensure this is communicated to all members involved with release work (i.e. the marketing team liaison who assists with the publication of release related material). When a security release is necessary, an internal Release Candidate should be built for testing by the Security Strike Team, CMS Release Team, and [https://volunteers.joomla.org/teams/cms-maintenance-team CMS Maintenance Team] with all security patches included. These teams should also receive information about the vulnerabilities being addressed to ensure there are no regressions in the impacted areas.<br /> <br /> Note, when a security fix involves a Joomla Framework package, the Framework package should be patched first and a release created of the affected package then the CMS updated with &lt;tt&gt;composer update&lt;/tt&gt;.<br /> <br /> Sometimes security fixes are required for composer dependencies that are out of support. In such cases we fork the 3rd party dependency into https://github.com/joomla-backports and then apply security fixes there in a &lt;tt&gt;joomla-backports&lt;/tt&gt; branch (and override the [https://github.com/joomla/joomla-cms/blob/3.10.5/composer.json#L28-L32 repository in composer.json] and as well as the branch reference [https://github.com/joomla/joomla-cms/blob/3.10.5/composer.json#L54 here]. Links are a sample for PHPMailer overrides in Joomla 3.10).<br /> <br /> === Release FAQ ===<br /> Create Release FAQ Category on the Joomla Documentation site. (i.e. Clone the contents of an existing page such as [https://docs.joomla.org/Category:Version_4.0.6_FAQ FAQ] and update the version number to your required version)<br /> <br /> == Building a Release ==<br /> Building a release starts with checking that any files and folders that have been deleted are included in the arrays in the installer script at &lt;tt&gt;administrator/components/com_admin/script.php&lt;/tt&gt;. There is a helper script in the repository to assist with this located at &lt;tt&gt;build/deleted_file_check.php&lt;/tt&gt;. Running &lt;tt&gt;php build/deleted_file_check.php&lt;/tt&gt; with its required &lt;tt&gt;--from&lt;/tt&gt; option will write a file to &lt;tt&gt;build/deleted_files.txt&lt;/tt&gt; with the list of files deleted since the from reference. Please see the PHP file for all documentation about this script.<br /> <br /> The following steps require the individual to create commits and tags. It is suggested that these commits and tags be GPG signed as an extra security step but this is not a mandatory requirement as of this writing.<br /> <br /> If creating a security release, at this point you should apply all patches provided by the security team.<br /> <br /> Once it is confirmed that the deleted files listing is correct, the &lt;tt&gt;build/bump.php&lt;/tt&gt; script should be executed to set the new version number. This script will also perform maintenance steps such as correcting the copyright year ranges for all files and replacing the &lt;tt&gt;__DEPLOY_VERSION__&lt;/tt&gt; placeholder. Please see the file for all documentation about this script.<br /> <br /> After running this script, review all changes with &lt;tt&gt;git diff&lt;/tt&gt; as a final check before creating your release commit. Once you are satisfied that all changes are correct, commit your changes locally. Once committed, create the release tag locally; all release tags should be the version number you are creating and should match the output of &lt;tt&gt;Joomla\CMS\Version::getShortVersion()&lt;/tt&gt; (so if you have created 3.9.0-beta2 then the tag should be named 3.9.0-beta2).<br /> <br /> Once the tag has been created, you will run the &lt;tt&gt;build/build.php&lt;/tt&gt; script to generate the release packages. To ensure a clean build is produced, the script makes an archive of the tag you are building using the &lt;tt&gt;git archive&lt;/tt&gt; command and extracts this to the &lt;tt&gt;build/tmp/&lt;timestamp&gt;&lt;/tt&gt; directory. Depending on the patch version number, the following packages will be created in the &lt;tt&gt;build/tmp/packages&lt;/tt&gt;:<br /> <br /> * 0: Full installation and upgrade packages<br /> * 1: Full installation, upgrade packages, and patch packages for x.y.0 to x.y.1<br /> * 2+: Full installation, upgrade packages, patch packages for x.y.0 to x.y.&lt;new&gt; and x.y.&lt;new-1&gt; to x.y.&lt;new&gt; (i.e. when creating 3.8.8 this will create a patch package suitable for all 3.8.x releases and an optimized patch package for 3.8.7 to 3.8.8)<br /> <br /> Additionally, the script will generate a &lt;tt&gt;build/tmp/checksums.txt&lt;/tt&gt; file with the checksums for all generated packages. &lt;tt&gt;build/tmp/github_release.txt&lt;/tt&gt; is also produced which is a text template used for the GitHub releases.<br /> <br /> After the packages are created, you should validate that you are able to install and update a site using the ZIP packages (as these are the most frequently used type and served by our update system).<br /> <br /> == Publishing a Release ==<br /> === Release Packages ===<br /> Depending on the type of release being created, you will publish the release packages in different locations.<br /> <br /> ==== Alpha, Beta, Release Candidate ====<br /> The packages for these releases are uploaded to GitHub. When ready to publish, you should push the release tag you created to GitHub and use their interface to create a release from the tag and upload the packages.<br /> <br /> ==== Stable ====<br /> The packages for stable releases are uploaded to multiple locations, this is in part driven by the fact that the Amazon Web Services (AWS) S3 region used by Joomla is blocked in some locations therefore download mirrors are available when necessary.<br /> <br /> Note that the Joomla! Downloads Portal release can be done in advance (as long as the release is kept unpublished until release day). The Update server and GitHub releases are public by default and therefore should only be done at the time of release.<br /> <br /> ===== Joomla! Downloads Portal =====<br /> The canonical source for all stable releases is the [https://downloads.joomla.org/ Joomla! Downloads Portal]. The packages served from the site use Joomla's AWS account. You will need to log into the AWS console to upload the packages to S3 under the &lt;tt&gt;joomla-official-downloads&lt;/tt&gt; bucket. The exact path inside the bucket is &lt;tt&gt;joomladownloads/joomla&lt;version&gt;&lt;/tt&gt; where &lt;tt&gt;&lt;version&gt;&lt;/tt&gt; is the major version number (i.e. &lt;tt&gt;joomla3&lt;/tt&gt;), note for compatibility with Akeeba Release System folders for each individual release are not used. You can use [https://aws.amazon.com/cli/ AWS CLI] to upload these files - but MFA is still required - follow the procedure documented [https://aws.amazon.com/premiumsupport/knowledge-center/authenticate-mfa-cli/ here] or use a tool to automate this such as [https://github.com/broamski/aws-mfa AWS-MFA]<br /> <br /> Once files have been uploaded to S3 then you need to generate the release in Akeeba Release System on the Downloads Portal. To generate all required items quickly it's recommended to use the &lt;tt&gt;cli/ars-create-cms-release.php&lt;/tt&gt; script - the source for this can be found on [https://github.com/joomla/downloads.joomla.org/blob/master/www/cli/ars-create-cms-release.php Github].<br /> <br /> Note that if you need to rebuild a package - for example because issues are found in the release candidate - you do not need to re-create the ARS resources but simply delete and reupload the S3 packages then use the &lt;tt&gt;cli/ars-get-hashes.php&lt;/tt&gt; script on the downloads site (which simply update the checksums for each item in the release) - source code for this is also located at [https://github.com/joomla/downloads.joomla.org/blob/master/www/cli/ars-get-hashes.php Github].<br /> <br /> ===== Joomla! Update Server =====<br /> The Joomla! Update Server is used as a mirror for the download packages. After connecting to the server, you should create a new folder at &lt;tt&gt;www/releases/&lt;version&gt;&lt;/tt&gt; (i.e. &lt;tt&gt;www/releases/3.9.1&lt;/tt&gt; for the 3.9.1 release) and upload the packages here.<br /> <br /> ===== GitHub =====<br /> The packages are also uploaded to GitHub. This is similar to the steps for alpha, beta, and release candidate releases above. Note that you only need to push the release tag at this point (i.e. &lt;tt&gt;git push --tags&lt;/tt&gt;), you can wait to push the updated release branch until after the release is available.<br /> <br /> === Announcements ===<br /> ==== joomla.org ====<br /> For all stable releases, the main release announcement is published to the &lt;tt&gt;Joomla! Official News &gt; Project Release News&lt;/tt&gt; category on the main &lt;tt&gt;joomla.org&lt;/tt&gt; website. This is primarily handled by the Marketing team - however release leads are expected to contribute to the ''Bug fixes and Improvements'' section as well as highlighting any other information that may need to be called out as part of release notes. After release the Social Media team need to be made aware to ensure the release is available on social media - use the ''Contact the Social Media Team'' Channel on Glip.<br /> <br /> For a minor release, an updated version of the landing page at &lt;tt&gt;joomla.org/4&lt;/tt&gt; (previously &lt;tt&gt;joomla.org/3&lt;/tt&gt;) is published. Generally, this site is backed up from the sandbox location and transferred to the live domain shortly before release, this transfer should be coordinated with the [https://volunteers.joomla.org/teams/webmasters-team Webmasters Team].<br /> <br /> ==== developer.joomla.org ====<br /> For security releases, all accompanying articles are published to the &lt;tt&gt;News &gt; Security Centre&lt;/tt&gt; category on the Joomla! Developer Network. As these articles are referenced from the main release announcement, these should be published at the same time.<br /> <br /> == Update Server ==<br /> The update server must be updated to alert websites that a core update is available, this subdomain is managed on GitHub at https://github.com/joomla/update.joomla.org. Prior to each release, a pull request should be prepared with necessary changes for the release (generally this updates the version number, announcement URL, package URLs, and package checksums for the stable release and updating the version number for the nightly builds), see https://github.com/joomla/update.joomla.org/pull/117 as an example of this update for the 3.9.1 release. Pushes to the &lt;tt&gt;master&lt;/tt&gt; branch of this repo are automatically deployed thanks to a Jenkins job, notifications for many of the Jenkins jobs are sent to the &lt;tt&gt;.org Build Notifications&lt;/tt&gt; channel on RingCentral Glip so you should ensure a success notification was sent here otherwise check if there was an issue with the job and/or manually deploy the updated files.<br /> <br /> Note that the &lt;tt&gt;update.joomla.org&lt;/tt&gt; subdomain is behind a CDN and it generally takes 5-10 minutes for all nodes to update, if need be you can access &lt;tt&gt;update1.joomla.org&lt;/tt&gt; to verify the right files are deployed without using the CDN. Note files cache times aren't consistent and often we've seen issues where the list update file is the new version and the extension.xml file is on the old version.<br /> <br /> == Post Release Actions ==<br /> Once the release is published, there are several additional tasks that should be completed shortly after.<br /> <br /> === Post-Release Version Bump ===<br /> The version should be bumped to the next version scheduled for release using the &lt;tt&gt;build/bump.php&lt;/tt&gt; script (i.e. after the 3.9.1 release this would be bumped to 3.9.2-dev).<br /> <br /> === Branch Merging ===<br /> After incrementing the version number, you should merge all the release changes forward to other active branches (especially in the case of a security release). Ensure you pay careful attention while resolving merge conflicts, when making a merge that includes a version bump generally all files which contain the version string and/or release date will be in conflict (as of this writing this is 8 files).<br /> <br /> === Push Updated Branches ===<br /> When ready, you should directly push your updates to the Git repo. If you elect to use pull requests, the pull requests should NEVER be squashed or rebased otherwise this will wipe out Git's awareness of the merged commits and will make your next branch merges even more complex. Likewise, as an example, if the commit preparing the 3.9.1 release and bumping the version string to 3.9.2-dev were squash merged as a pull request, then the commit that the 3.9.1 release was tagged from would not be in the repository.<br /> <br /> === Update Release Milestones ===<br /> On GitHub, all merged items are assigned to a milestone to help organize items. With each release, the [https://github.com/joomla/joomla-cms/milestones milestones] should be updated to ensure that the milestone for the release you created has been closed and a milestone for the next release is open.<br /> <br /> === Regenerate Nightly Builds ===<br /> The nightly builds for any branch updated during the release process should be regenerated to include the release's changes. These can be manually triggered within the &lt;tt&gt;CMS Packaging&lt;/tt&gt; folder on the Jenkins server.<br /> <br /> === Website Updates ===<br /> With all code updates pushed, there are several website updates that need to be triggered.<br /> <br /> ==== api.joomla.org ====<br /> With each release, an updated build of the API documentation should be deployed to the &lt;tt&gt;api.joomla.org&lt;/tt&gt; website. These updates are triggered with the &lt;tt&gt;Joomla! API &gt; Deploy Docs - CMS&lt;/tt&gt; job on Jenkins. As this job relies on the release tags from the CMS repo, this can only be done after the release tag has been pushed.<br /> <br /> ==== developer.joomla.org ====<br /> After a release, the &lt;tt&gt;Joomla! Project Roadmap&lt;/tt&gt; article in the &lt;tt&gt;Uncategorised&lt;/tt&gt; category should be updated to reflect the newly released version and updated links, as well as adding expected release dates for the next release.<br /> <br /> The version whitelist for the statistics server should also be updated to allow the next version to be submitted; if you have not already, you should have a clone of the https://github.com/joomla/statistics-server repository on your local system. Once cloned and set up, run the &lt;tt&gt;bin/stats tags:joomla&lt;/tt&gt; command to regenerate the Joomla version whitelist. As this command relies on the release tags from the CMS repo, this can only be done after the release tag has been pushed. The updated &lt;tt&gt;versions/joomla.json&lt;/tt&gt; should be committed and pushed, and a Jenkins job will deploy the updated site resources.<br /> <br /> == Additional Considerations ==<br /> The release manager or a delegate is suggested to be in communication with the Webmasters Team to ensure the &lt;tt&gt;joomla.org&lt;/tt&gt; websites are updated in a timely manner. When a security release is scheduled, it is encouraged to share the update release package with the team so that our sites may be updated before the fix is made public to mitigate the chance of the vulnerability being used to exploit one of our sites. It also provides additional testing for security fixes on real world sites in addition to the tests performed by the CMS Release Team.<br /> <br /> = Framework Release Cycle =<br /> The packages of the Joomla Framework are on an independent lifecycle meaning each package can be updated and released independently of all others. Generally the only restriction is with major releases, which should coincide with the CMS release cycle (i.e. CMS 3.x uses Framework 1.x, CMS 4.x will use Framework 2.x therefore Framework 2.0 stable releases should not be made until the CMS is in its beta phase at the earliest).<br /> <br /> == Tagging a Release ==<br /> Most packages can be tagged and released through the &lt;tt&gt;Joomla! Framework &gt; Package Release&lt;/tt&gt; job on Jenkins, however as of this writing this job only supports tagging releases from a repository's &lt;tt&gt;master&lt;/tt&gt; branch. To tag a release, select the package you wish to update and specify the version you are releasing in the job's parameters and run the job; all releases should follow Semantic Versioning to set the correct number.<br /> <br /> Once the job has completed, you should verify the new release is visible on [https://packagist.org/packages/joomla/ Packagist]. Within a day, the new update should be visible on the [https://framework.joomla.org/status Joomla Framework Status page] (the database is updated via cron job reading from Packagist's API), if the updated version isn't seen on the site in a relatively timely manner you should clone the website locally and debug the &lt;tt&gt;packagist:sync:releases&lt;/tt&gt; command.<br /> <br /> == Security Releases ==<br /> When a security release is created, a pull request should be sent to the [https://github.com/FriendsOfPHP/security-advisories FriendsOfPHP/security-advisories repository] with relevant details. This repository is used by many tools in the PHP and Composer ecosystem to alert users of security issues. https://github.com/FriendsOfPHP/security-advisories/pull/134 is an example of this pull request.<br /> <br /> == Onboarding Release Leads ==<br /> Release Leads will need access to a number of resources. The following are required:<br /> - Account on Github (added to [https://github.com/orgs/joomla/teams/cms-release-leads/members the CMS Release Leads team] for the Joomla Org (which also provides jenkins access) and [https://github.com/orgs/joomla-backports/teams/cms-release-leads the CMS Release Leads team] for the Joomla Backport org.<br /> - The Forum (Ensure users are aware of release groups)<br /> - Glip (CMS Maintainers, CMS Release Leads, WebMasters Team, JSST)<br /> - Introduction with Translation, JSST and Webmaster Liasons<br /> - SSH keys added to Update and Downloads servers<br /> - Downloads Website (Release Leads -&gt; CMS ACL Group)<br /> - AWS Account in Release_Managers Group<br /> <br /> [[Category:Bug Squad]]<br /> [[Category:Coordinators]]<br /> [[Category:Development]]</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Joomla:Release_procedure_and_checklist&diff=876769 2022-01-30T11:36:25Z

<p>Wilsonge: /* Maintenance Release */</p> <hr /> <div>{{RightTOC}}<br /> <br /> This is a general procedure explanation for managing releases of Joomla! and the Joomla! Framework. This list is best suited for a [[Minor Release]] or [[Maintenance Release]], however the steps will generally apply to a [[Major Release]] as well but will require some judgement calls from the release manager and/or leadership team.<br /> <br /> There is a more formal checklist available [https://github.com/joomla/joomla-cms/blob/4.1-dev/build/release-checklist.md on GitHub] for release leads to use that is intended to complement the steps described in this page.<br /> <br /> Release Leads will need access to a number of resources. But accounts on Github (and being added to [https://github.com/orgs/joomla/teams/cms-release-leads/members the CMS Release Leads team] - which also provides jenkins access), the Forum and Glip are effectively mandatory.<br /> <br /> = CMS Release Cycle =<br /> <br /> == Issue Triage, Patch Review, Merging Patches ==<br /> The release cycle for a new software version begins immediately after the previous one is completed. In the immediate hours and days after a release, the [https://github.com/joomla/joomla-cms issue tracker] and [https://forum.joomla.org/ support forums], in close coordination with the [https://volunteers.joomla.org/teams/bug-squad Bug Squad] and [https://volunteers.joomla.org/teams/cms-release-team CMS Release Team], should be monitored for reports of potential regressions or critical bugs that would warrant a quick follow-on release to address the issue. It is generally suggested to wait 48-72 hours before resuming merging of reviewed and ready for commit pull requests to keep the release branch &quot;clean&quot; and ready for a release (note this is only a suggestion, if need be a release manager could create a branch from the release tag however this involves a bit more effort therefore this suggestion is for simplicity's sake).<br /> <br /> Throughout the release cycle, the release manager should be involved with reviewing patches and merging reviewed patches to the appropriate release branch. As of this writing (where 4.0.6 is the present release), the following branches are generally active:<br /> <br /> * &lt;tt&gt;3.10-dev&lt;/tt&gt;: This is the 3.x branch, generally only bug fixes and &quot;general&quot; maintenance work should merge to this branch.<br /> * &lt;tt&gt;4.0-dev&lt;/tt&gt;: This is the 4.0.x branch - there are no more intended releases to this branch unless required by security fixes.<br /> * &lt;tt&gt;4.1-dev&lt;/tt&gt;: This is the main release branch and is where most activity occurs, generally only bug fixes and &quot;general&quot; maintenance work should merge to this branch although minor features may be merged at the discretion of the release manager and/or leadership team. All code from 3.10-dev is merged into this branch.<br /> * &lt;tt&gt;4.2-dev&lt;/tt&gt;: This is the release branch for the next minor release (the branch's name will always be the version it represents), new features should be merged to this branch<br /> <br /> === Branch Merging ===<br /> All branches should remain in-sync and all work should be regularly merged forward. Given the above example, the following is the recommended merging workflow (in general, the suggested workflow is that 3.10-dev is merged to the current 4.x-dev branch and then through to the next minor branch):<br /> <br /> * &lt;tt&gt;3.10-dev&lt;/tt&gt; should be merged into &lt;tt&gt;4.0-dev&lt;/tt&gt;<br /> * &lt;tt&gt;4.0-dev&lt;/tt&gt; should be merged to &lt;tt&gt;4.1-dev&lt;/tt&gt;<br /> * &lt;tt&gt;4.1-dev&lt;/tt&gt; should be merged to &lt;tt&gt;4.2-dev&lt;/tt&gt;<br /> <br /> It is suggested that at least once per week branch merging occurs.<br /> <br /> == Preparing To Release ==<br /> When scheduling and preparing a release, the timeline should be communicated with the Production and Marketing &amp; Communication Department leadership so that all teams are prepared to support the release. Note that when scheduling releases, consideration should be given to holidays around the world and the impact of issuing a release near those periods considered. Helpful resources include http://interfaith-calendar.org/ and https://www.timeanddate.com/holidays/<br /> <br /> === Review Release Milestone and Blockers ===<br /> On GitHub, check the [https://github.com/joomla/joomla-cms/milestones milestone] for the release you are preparing to create and for any open items with the [https://github.com/joomla/joomla-cms/labels/release-blocker release-blocker] label. If there are remaining open items, review them to determine if they are items that should be included in the release or if they can be rescheduled to a later release.<br /> <br /> === Release Schedule ===<br /> ==== Minor Release ====<br /> Given the nature of a minor release, the following is the suggested release timeline:<br /> <br /> * Six weeks prior to planned stable release: Tag the first Beta release<br /> ** At this point the release should be considered feature complete and new features should be deferred to the next minor release<br /> * Weekly Beta releases should follow this until the Release Candidate<br /> * Two weeks prior to planned stable release: Tag the Release Candidate<br /> ** At this point the release branch(es) should remain closed for committing except for high priority bug fixes and language updates<br /> ** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the &quot;no later than&quot; time<br /> ** Inform the CMS Release Team and call out anything that you would like extra testing on<br /> * One week prior to planned stable release: If necessary, create a second Release Candidate<br /> * 2-3 days before release: Build final packages - share with CMS Release Team and do release preparation activities.<br /> * Planned release date: Tag the stable release<br /> <br /> ==== Maintenance Release ====<br /> Maintenance releases operate on a 4-6 week cycle and the following is the suggested release timeline:<br /> <br /> * 9-10 days before planned release date: Tag a Release Candidate<br /> ** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the &quot;no later than&quot; time<br /> ** Inform the CMS Release Team and call out anything that you would like extra testing on<br /> * 2-3 days before release: Build final packages - share with CMS Release Team and do release preparation activities.<br /> * Planned release date: Tag the stable release<br /> <br /> === Reviewing Release Changes ===<br /> Before tagging a release, the list of changes in the release should be reviewed by the release manager and/or leadership team. The list of changes can be found using GitHub's compare function with the URL &lt;tt&gt;https://github.com/joomla/joomla-cms/compare/&lt;version&gt;...4.1-dev&lt;/tt&gt; which will compare the changes from &lt;tt&gt;&lt;version&gt;&lt;/tt&gt; to the current 4.1-dev branch (for example, https://github.com/joomla/joomla-cms/compare/3.9.0...3.9.1-rc is the comparison from the 3.9.0 release tag to the 3.9.1-rc tag). Key purposes of this review include:<br /> <br /> * Ensuring all patches are compliant with Semantic Versioning (SemVer) (i.e. no backward compatibility breaks in minor or maintenance releases and no features in maintenance releases); SemVer violations should be cleared with the Production Department leadership<br /> * Ensuring all code revisions are compatible with Joomla's minimum supported versions (i.e. no PHP 5.4 syntax in 3.x releases where PHP 5.3 is the minimum supported version, exceptions may be made if introducing a code path and files that will only be executed on newer PHP versions)<br /> ** Joomla's testing integrations should not be relied on in full for this as there are large portions of the Joomla code base which do not have automated test coverage, and as of this writing, there is not a code linting process in place checking for potential issues<br /> * Ensuring features and &quot;significant&quot; changes are documented<br /> <br /> === Security Fixes ===<br /> From time to time, security fixes must be included in a release. Prior to every release, the release manager should check with the [https://volunteers.joomla.org/teams/security-strike-team Security Strike Team] to determine if security fixes are required, and if so ensure this is communicated to all members involved with release work (i.e. the marketing team liaison who assists with the publication of release related material). When a security release is necessary, an internal Release Candidate should be built for testing by the Security Strike Team, CMS Release Team, and [https://volunteers.joomla.org/teams/cms-maintenance-team CMS Maintenance Team] with all security patches included. These teams should also receive information about the vulnerabilities being addressed to ensure there are no regressions in the impacted areas.<br /> <br /> Note, when a security fix involves a Joomla Framework package, the Framework package should be patched first and a release created of the affected package then the CMS updated with &lt;tt&gt;composer update&lt;/tt&gt;.<br /> <br /> Sometimes security fixes are required for composer dependencies that are out of support. In such cases we fork the 3rd party dependency into https://github.com/joomla-backports and then apply security fixes there in a &lt;tt&gt;joomla-backports&lt;/tt&gt; branch (and override the [https://github.com/joomla/joomla-cms/blob/3.10.5/composer.json#L28-L32 repository in composer.json] and as well as the branch reference [https://github.com/joomla/joomla-cms/blob/3.10.5/composer.json#L54 here]. Links are a sample for PHPMailer overrides in Joomla 3.10).<br /> <br /> === Release FAQ ===<br /> Create Release FAQ Category on the Joomla Documentation site. (i.e. Clone the contents of an existing page such as [https://docs.joomla.org/Category:Version_4.0.6_FAQ FAQ] and update the version number to your required version)<br /> <br /> == Building a Release ==<br /> Building a release starts with checking that any files and folders that have been deleted are included in the arrays in the installer script at &lt;tt&gt;administrator/components/com_admin/script.php&lt;/tt&gt;. There is a helper script in the repository to assist with this located at &lt;tt&gt;build/deleted_file_check.php&lt;/tt&gt;. Running &lt;tt&gt;php build/deleted_file_check.php&lt;/tt&gt; with its required &lt;tt&gt;--from&lt;/tt&gt; option will write a file to &lt;tt&gt;build/deleted_files.txt&lt;/tt&gt; with the list of files deleted since the from reference. Please see the PHP file for all documentation about this script.<br /> <br /> The following steps require the individual to create commits and tags. It is suggested that these commits and tags be GPG signed as an extra security step but this is not a mandatory requirement as of this writing.<br /> <br /> If creating a security release, at this point you should apply all patches provided by the security team.<br /> <br /> Once it is confirmed that the deleted files listing is correct, the &lt;tt&gt;build/bump.php&lt;/tt&gt; script should be executed to set the new version number. This script will also perform maintenance steps such as correcting the copyright year ranges for all files and replacing the &lt;tt&gt;__DEPLOY_VERSION__&lt;/tt&gt; placeholder. Please see the file for all documentation about this script.<br /> <br /> After running this script, review all changes with &lt;tt&gt;git diff&lt;/tt&gt; as a final check before creating your release commit. Once you are satisfied that all changes are correct, commit your changes locally. Once committed, create the release tag locally; all release tags should be the version number you are creating and should match the output of &lt;tt&gt;Joomla\CMS\Version::getShortVersion()&lt;/tt&gt; (so if you have created 3.9.0-beta2 then the tag should be named 3.9.0-beta2).<br /> <br /> Once the tag has been created, you will run the &lt;tt&gt;build/build.php&lt;/tt&gt; script to generate the release packages. To ensure a clean build is produced, the script makes an archive of the tag you are building using the &lt;tt&gt;git archive&lt;/tt&gt; command and extracts this to the &lt;tt&gt;build/tmp/&lt;timestamp&gt;&lt;/tt&gt; directory. Depending on the patch version number, the following packages will be created in the &lt;tt&gt;build/tmp/packages&lt;/tt&gt;:<br /> <br /> * 0: Full installation and upgrade packages<br /> * 1: Full installation, upgrade packages, and patch packages for x.y.0 to x.y.1<br /> * 2+: Full installation, upgrade packages, patch packages for x.y.0 to x.y.&lt;new&gt; and x.y.&lt;new-1&gt; to x.y.&lt;new&gt; (i.e. when creating 3.8.8 this will create a patch package suitable for all 3.8.x releases and an optimized patch package for 3.8.7 to 3.8.8)<br /> <br /> Additionally, the script will generate a &lt;tt&gt;build/tmp/checksums.txt&lt;/tt&gt; file with the checksums for all generated packages. &lt;tt&gt;build/tmp/github_release.txt&lt;/tt&gt; is also produced which is a text template used for the GitHub releases.<br /> <br /> After the packages are created, you should validate that you are able to install and update a site using the ZIP packages (as these are the most frequently used type and served by our update system).<br /> <br /> == Publishing a Release ==<br /> === Release Packages ===<br /> Depending on the type of release being created, you will publish the release packages in different locations.<br /> <br /> ==== Alpha, Beta, Release Candidate ====<br /> The packages for these releases are uploaded to GitHub. When ready to publish, you should push the release tag you created to GitHub and use their interface to create a release from the tag and upload the packages.<br /> <br /> ==== Stable ====<br /> The packages for stable releases are uploaded to multiple locations, this is in part driven by the fact that the Amazon Web Services (AWS) S3 region used by Joomla is blocked in some locations therefore download mirrors are available when necessary.<br /> <br /> Note that the Joomla! Downloads Portal release can be done in advance (as long as the release is kept unpublished until release day). The Update server and GitHub releases are public by default and therefore should only be done at the time of release.<br /> <br /> ===== Joomla! Downloads Portal =====<br /> The canonical source for all stable releases is the [https://downloads.joomla.org/ Joomla! Downloads Portal]. The packages served from the site use Joomla's AWS account. You will need to log into the AWS console to upload the packages to S3 under the &lt;tt&gt;joomla-official-downloads&lt;/tt&gt; bucket. The exact path inside the bucket is &lt;tt&gt;joomladownloads/joomla&lt;version&gt;&lt;/tt&gt; where &lt;tt&gt;&lt;version&gt;&lt;/tt&gt; is the major version number (i.e. &lt;tt&gt;joomla3&lt;/tt&gt;), note for compatibility with Akeeba Release System folders for each individual release are not used. You can use [https://aws.amazon.com/cli/ AWS CLI] to upload these files - but MFA is still required - follow the procedure documented [https://aws.amazon.com/premiumsupport/knowledge-center/authenticate-mfa-cli/ here] or use a tool to automate this such as [https://github.com/broamski/aws-mfa AWS-MFA]<br /> <br /> Once files have been uploaded to S3 then you need to generate the release in Akeeba Release System on the Downloads Portal. To generate all required items quickly it's recommended to use the &lt;tt&gt;cli/ars-create-cms-release.php&lt;/tt&gt; script - the source for this can be found on [https://github.com/joomla/downloads.joomla.org/blob/master/www/cli/ars-create-cms-release.php Github].<br /> <br /> Note that if you need to rebuild a package - for example because issues are found in the release candidate - you do not need to re-create the ARS resources but simply delete and reupload the S3 packages then use the &lt;tt&gt;cli/ars-get-hashes.php&lt;/tt&gt; script on the downloads site (which simply update the checksums for each item in the release) - source code for this is also located at [https://github.com/joomla/downloads.joomla.org/blob/master/www/cli/ars-get-hashes.php Github].<br /> <br /> ===== Joomla! Update Server =====<br /> The Joomla! Update Server is used as a mirror for the download packages. After connecting to the server, you should create a new folder at &lt;tt&gt;www/releases/&lt;version&gt;&lt;/tt&gt; (i.e. &lt;tt&gt;www/releases/3.9.1&lt;/tt&gt; for the 3.9.1 release) and upload the packages here.<br /> <br /> ===== GitHub =====<br /> The packages are also uploaded to GitHub. This is similar to the steps for alpha, beta, and release candidate releases above. Note that you only need to push the release tag at this point (i.e. &lt;tt&gt;git push --tags&lt;/tt&gt;), you can wait to push the updated release branch until after the release is available.<br /> <br /> === Announcements ===<br /> ==== joomla.org ====<br /> For all stable releases, the main release announcement is published to the &lt;tt&gt;Joomla! Official News &gt; Project Release News&lt;/tt&gt; category on the main &lt;tt&gt;joomla.org&lt;/tt&gt; website. This is primarily handled by the Marketing team - however release leads are expected to contribute to the ''Bug fixes and Improvements'' section as well as highlighting any other information that may need to be called out as part of release notes. After release the Social Media team need to be made aware to ensure the release is available on social media - use the ''Contact the Social Media Team'' Channel on Glip.<br /> <br /> For a minor release, an updated version of the landing page at &lt;tt&gt;joomla.org/4&lt;/tt&gt; (previously &lt;tt&gt;joomla.org/3&lt;/tt&gt;) is published. Generally, this site is backed up from the sandbox location and transferred to the live domain shortly before release, this transfer should be coordinated with the [https://volunteers.joomla.org/teams/webmasters-team Webmasters Team].<br /> <br /> ==== developer.joomla.org ====<br /> For security releases, all accompanying articles are published to the &lt;tt&gt;News &gt; Security Centre&lt;/tt&gt; category on the Joomla! Developer Network. As these articles are referenced from the main release announcement, these should be published at the same time.<br /> <br /> == Update Server ==<br /> The update server must be updated to alert websites that a core update is available, this subdomain is managed on GitHub at https://github.com/joomla/update.joomla.org. Prior to each release, a pull request should be prepared with necessary changes for the release (generally this updates the version number, announcement URL, package URLs, and package checksums for the stable release and updating the version number for the nightly builds), see https://github.com/joomla/update.joomla.org/pull/117 as an example of this update for the 3.9.1 release. Pushes to the &lt;tt&gt;master&lt;/tt&gt; branch of this repo are automatically deployed thanks to a Jenkins job, notifications for many of the Jenkins jobs are sent to the &lt;tt&gt;.org Build Notifications&lt;/tt&gt; channel on RingCentral Glip so you should ensure a success notification was sent here otherwise check if there was an issue with the job and/or manually deploy the updated files.<br /> <br /> Note that the &lt;tt&gt;update.joomla.org&lt;/tt&gt; subdomain is behind a CDN and it generally takes 5-10 minutes for all nodes to update, if need be you can access &lt;tt&gt;update1.joomla.org&lt;/tt&gt; to verify the right files are deployed without using the CDN. Note files cache times aren't consistent and often we've seen issues where the list update file is the new version and the extension.xml file is on the old version.<br /> <br /> == Post Release Actions ==<br /> Once the release is published, there are several additional tasks that should be completed shortly after.<br /> <br /> === Post-Release Version Bump ===<br /> The version should be bumped to the next version scheduled for release using the &lt;tt&gt;build/bump.php&lt;/tt&gt; script (i.e. after the 3.9.1 release this would be bumped to 3.9.2-dev).<br /> <br /> === Branch Merging ===<br /> After incrementing the version number, you should merge all the release changes forward to other active branches (especially in the case of a security release). Ensure you pay careful attention while resolving merge conflicts, when making a merge that includes a version bump generally all files which contain the version string and/or release date will be in conflict (as of this writing this is 8 files).<br /> <br /> === Push Updated Branches ===<br /> When ready, you should directly push your updates to the Git repo. If you elect to use pull requests, the pull requests should NEVER be squashed or rebased otherwise this will wipe out Git's awareness of the merged commits and will make your next branch merges even more complex. Likewise, as an example, if the commit preparing the 3.9.1 release and bumping the version string to 3.9.2-dev were squash merged as a pull request, then the commit that the 3.9.1 release was tagged from would not be in the repository.<br /> <br /> === Update Release Milestones ===<br /> On GitHub, all merged items are assigned to a milestone to help organize items. With each release, the [https://github.com/joomla/joomla-cms/milestones milestones] should be updated to ensure that the milestone for the release you created has been closed and a milestone for the next release is open.<br /> <br /> === Regenerate Nightly Builds ===<br /> The nightly builds for any branch updated during the release process should be regenerated to include the release's changes. These can be manually triggered within the &lt;tt&gt;CMS Packaging&lt;/tt&gt; folder on the Jenkins server.<br /> <br /> === Website Updates ===<br /> With all code updates pushed, there are several website updates that need to be triggered.<br /> <br /> ==== api.joomla.org ====<br /> With each release, an updated build of the API documentation should be deployed to the &lt;tt&gt;api.joomla.org&lt;/tt&gt; website. These updates are triggered with the &lt;tt&gt;Joomla! API &gt; Deploy Docs - CMS&lt;/tt&gt; job on Jenkins. As this job relies on the release tags from the CMS repo, this can only be done after the release tag has been pushed.<br /> <br /> ==== developer.joomla.org ====<br /> After a release, the &lt;tt&gt;Joomla! Project Roadmap&lt;/tt&gt; article in the &lt;tt&gt;Uncategorised&lt;/tt&gt; category should be updated to reflect the newly released version and updated links, as well as adding expected release dates for the next release.<br /> <br /> The version whitelist for the statistics server should also be updated to allow the next version to be submitted; if you have not already, you should have a clone of the https://github.com/joomla/statistics-server repository on your local system. Once cloned and set up, run the &lt;tt&gt;bin/stats tags:joomla&lt;/tt&gt; command to regenerate the Joomla version whitelist. As this command relies on the release tags from the CMS repo, this can only be done after the release tag has been pushed. The updated &lt;tt&gt;versions/joomla.json&lt;/tt&gt; should be committed and pushed, and a Jenkins job will deploy the updated site resources.<br /> <br /> == Additional Considerations ==<br /> The release manager or a delegate is suggested to be in communication with the Webmasters Team to ensure the &lt;tt&gt;joomla.org&lt;/tt&gt; websites are updated in a timely manner. When a security release is scheduled, it is encouraged to share the update release package with the team so that our sites may be updated before the fix is made public to mitigate the chance of the vulnerability being used to exploit one of our sites. It also provides additional testing for security fixes on real world sites in addition to the tests performed by the CMS Release Team.<br /> <br /> = Framework Release Cycle =<br /> The packages of the Joomla Framework are on an independent lifecycle meaning each package can be updated and released independently of all others. Generally the only restriction is with major releases, which should coincide with the CMS release cycle (i.e. CMS 3.x uses Framework 1.x, CMS 4.x will use Framework 2.x therefore Framework 2.0 stable releases should not be made until the CMS is in its beta phase at the earliest).<br /> <br /> == Tagging a Release ==<br /> Most packages can be tagged and released through the &lt;tt&gt;Joomla! Framework &gt; Package Release&lt;/tt&gt; job on Jenkins, however as of this writing this job only supports tagging releases from a repository's &lt;tt&gt;master&lt;/tt&gt; branch. To tag a release, select the package you wish to update and specify the version you are releasing in the job's parameters and run the job; all releases should follow Semantic Versioning to set the correct number.<br /> <br /> Once the job has completed, you should verify the new release is visible on [https://packagist.org/packages/joomla/ Packagist]. Within a day, the new update should be visible on the [https://framework.joomla.org/status Joomla Framework Status page] (the database is updated via cron job reading from Packagist's API), if the updated version isn't seen on the site in a relatively timely manner you should clone the website locally and debug the &lt;tt&gt;packagist:sync:releases&lt;/tt&gt; command.<br /> <br /> == Security Releases ==<br /> When a security release is created, a pull request should be sent to the [https://github.com/FriendsOfPHP/security-advisories FriendsOfPHP/security-advisories repository] with relevant details. This repository is used by many tools in the PHP and Composer ecosystem to alert users of security issues. https://github.com/FriendsOfPHP/security-advisories/pull/134 is an example of this pull request.<br /> <br /> [[Category:Bug Squad]]<br /> [[Category:Coordinators]]<br /> [[Category:Development]]</div>

Wilsonge https://docs.sandbox.joomla.org/index.php?title=Joomla:Release_procedure_and_checklist&diff=876403 2022-01-30T01:30:47Z

<p>Wilsonge: </p> <hr /> <div>{{RightTOC}}<br /> <br /> This is a general procedure explanation for managing releases of Joomla! and the Joomla! Framework. This list is best suited for a [[Minor Release]] or [[Maintenance Release]], however the steps will generally apply to a [[Major Release]] as well but will require some judgement calls from the release manager and/or leadership team.<br /> <br /> There is a more formal checklist available [https://github.com/joomla/joomla-cms/blob/4.1-dev/build/release-checklist.md on GitHub] for release leads to use that is intended to complement the steps described in this page.<br /> <br /> Release Leads will need access to a number of resources. But accounts on Github (and being added to [https://github.com/orgs/joomla/teams/cms-release-leads/members the CMS Release Leads team] - which also provides jenkins access), the Forum and Glip are effectively mandatory.<br /> <br /> = CMS Release Cycle =<br /> <br /> == Issue Triage, Patch Review, Merging Patches ==<br /> The release cycle for a new software version begins immediately after the previous one is completed. In the immediate hours and days after a release, the [https://github.com/joomla/joomla-cms issue tracker] and [https://forum.joomla.org/ support forums], in close coordination with the [https://volunteers.joomla.org/teams/bug-squad Bug Squad] and [https://volunteers.joomla.org/teams/cms-release-team CMS Release Team], should be monitored for reports of potential regressions or critical bugs that would warrant a quick follow-on release to address the issue. It is generally suggested to wait 48-72 hours before resuming merging of reviewed and ready for commit pull requests to keep the release branch &quot;clean&quot; and ready for a release (note this is only a suggestion, if need be a release manager could create a branch from the release tag however this involves a bit more effort therefore this suggestion is for simplicity's sake).<br /> <br /> Throughout the release cycle, the release manager should be involved with reviewing patches and merging reviewed patches to the appropriate release branch. As of this writing (where 4.0.6 is the present release), the following branches are generally active:<br /> <br /> * &lt;tt&gt;3.10-dev&lt;/tt&gt;: This is the 3.x branch, generally only bug fixes and &quot;general&quot; maintenance work should merge to this branch.<br /> * &lt;tt&gt;4.0-dev&lt;/tt&gt;: This is the 4.0.x branch - there are no more intended releases to this branch unless required by security fixes.<br /> * &lt;tt&gt;4.1-dev&lt;/tt&gt;: This is the main release branch and is where most activity occurs, generally only bug fixes and &quot;general&quot; maintenance work should merge to this branch although minor features may be merged at the discretion of the release manager and/or leadership team. All code from 3.10-dev is merged into this branch.<br /> * &lt;tt&gt;4.2-dev&lt;/tt&gt;: This is the release branch for the next minor release (the branch's name will always be the version it represents), new features should be merged to this branch<br /> <br /> === Branch Merging ===<br /> All branches should remain in-sync and all work should be regularly merged forward. Given the above example, the following is the recommended merging workflow (in general, the suggested workflow is that 3.10-dev is merged to the current 4.x-dev branch and then through to the next minor branch):<br /> <br /> * &lt;tt&gt;3.10-dev&lt;/tt&gt; should be merged into &lt;tt&gt;4.0-dev&lt;/tt&gt;<br /> * &lt;tt&gt;4.0-dev&lt;/tt&gt; should be merged to &lt;tt&gt;4.1-dev&lt;/tt&gt;<br /> * &lt;tt&gt;4.1-dev&lt;/tt&gt; should be merged to &lt;tt&gt;4.2-dev&lt;/tt&gt;<br /> <br /> It is suggested that at least once per week branch merging occurs.<br /> <br /> == Preparing To Release ==<br /> When scheduling and preparing a release, the timeline should be communicated with the Production and Marketing &amp; Communication Department leadership so that all teams are prepared to support the release. Note that when scheduling releases, consideration should be given to holidays around the world and the impact of issuing a release near those periods considered. Helpful resources include http://interfaith-calendar.org/ and https://www.timeanddate.com/holidays/<br /> <br /> === Review Release Milestone and Blockers ===<br /> On GitHub, check the [https://github.com/joomla/joomla-cms/milestones milestone] for the release you are preparing to create and for any open items with the [https://github.com/joomla/joomla-cms/labels/release-blocker release-blocker] label. If there are remaining open items, review them to determine if they are items that should be included in the release or if they can be rescheduled to a later release.<br /> <br /> === Release Schedule ===<br /> ==== Minor Release ====<br /> Given the nature of a minor release, the following is the suggested release timeline:<br /> <br /> * Six weeks prior to planned stable release: Tag the first Beta release<br /> ** At this point the release should be considered feature complete and new features should be deferred to the next minor release<br /> * Weekly Beta releases should follow this until the Release Candidate<br /> * Two weeks prior to planned stable release: Tag the Release Candidate<br /> ** At this point the release branch(es) should remain closed for committing except for high priority bug fixes and language updates<br /> ** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the &quot;no later than&quot; time<br /> ** Inform the CMS Release Team and call out anything that you would like extra testing on<br /> * One week prior to planned stable release: If necessary, create a second Release Candidate<br /> * 2-3 days before release: Build final packages - share with CMS Release Team and do release preparation activities.<br /> * Planned release date: Tag the stable release<br /> <br /> ==== Maintenance Release ====<br /> Maintenance releases operate on a 4-6 week cycle and the following is the suggested release timeline:<br /> <br /> * 7 days before planned release date: Tag a Release Candidate<br /> ** With the Release Candidate, language freeze is also in effect and no language changes are permitted unless there is an urgent need (which should be communicated with the translations coordinator); note that if necessary the language freeze may be declared earlier but the Release Candidate should be considered the &quot;no later than&quot; time<br /> ** Inform the CMS Release Team and call out anything that you would like extra testing on<br /> * 2-3 days before release: Build final packages - share with CMS Release Team and do release preparation activities.<br /> * Planned release date: Tag the stable release<br /> <br /> === Reviewing Release Changes ===<br /> Before tagging a release, the list of changes in the release should be reviewed by the release manager and/or leadership team. The list of changes can be found using GitHub's compare function with the URL &lt;tt&gt;https://github.com/joomla/joomla-cms/compare/&lt;version&gt;...4.1-dev&lt;/tt&gt; which will compare the changes from &lt;tt&gt;&lt;version&gt;&lt;/tt&gt; to the current 4.1-dev branch (for example, https://github.com/joomla/joomla-cms/compare/3.9.0...3.9.1-rc is the comparison from the 3.9.0 release tag to the 3.9.1-rc tag). Key purposes of this review include:<br /> <br /> * Ensuring all patches are compliant with Semantic Versioning (SemVer) (i.e. no backward compatibility breaks in minor or maintenance releases and no features in maintenance releases); SemVer violations should be cleared with the Production Department leadership<br /> * Ensuring all code revisions are compatible with Joomla's minimum supported versions (i.e. no PHP 5.4 syntax in 3.x releases where PHP 5.3 is the minimum supported version, exceptions may be made if introducing a code path and files that will only be executed on newer PHP versions)<br /> ** Joomla's testing integrations should not be relied on in full for this as there are large portions of the Joomla code base which do not have automated test coverage, and as of this writing, there is not a code linting process in place checking for potential issues<br /> * Ensuring features and &quot;significant&quot; changes are documented<br /> <br /> === Security Fixes ===<br /> From time to time, security fixes must be included in a release. Prior to every release, the release manager should check with the [https://volunteers.joomla.org/teams/security-strike-team Security Strike Team] to determine if security fixes are required, and if so ensure this is communicated to all members involved with release work (i.e. the marketing team liaison who assists with the publication of release related material). When a security release is necessary, an internal Release Candidate should be built for testing by the Security Strike Team, CMS Release Team, and [https://volunteers.joomla.org/teams/cms-maintenance-team CMS Maintenance Team] with all security patches included. These teams should also receive information about the vulnerabilities being addressed to ensure there are no regressions in the impacted areas.<br /> <br /> Note, when a security fix involves a Joomla Framework package, the Framework package should be patched first and a release created of the affected package then the CMS updated with &lt;tt&gt;composer update&lt;/tt&gt;.<br /> <br /> Sometimes security fixes are required for composer dependencies that are out of support. In such cases we fork the 3rd party dependency into https://github.com/joomla-backports and then apply security fixes there in a &lt;tt&gt;joomla-backports&lt;/tt&gt; branch (and override the [https://github.com/joomla/joomla-cms/blob/3.10.5/composer.json#L28-L32 repository in composer.json] and as well as the branch reference [https://github.com/joomla/joomla-cms/blob/3.10.5/composer.json#L54 here]. Links are a sample for PHPMailer overrides in Joomla 3.10).<br /> <br /> === Release FAQ ===<br /> Create Release FAQ Category on the Joomla Documentation site. (i.e. Clone the contents of an existing page such as [https://docs.joomla.org/Category:Version_4.0.6_FAQ FAQ] and update the version number to your required version)<br /> <br /> == Building a Release ==<br /> Building a release starts with checking that any files and folders that have been deleted are included in the arrays in the installer script at &lt;tt&gt;administrator/components/com_admin/script.php&lt;/tt&gt;. There is a helper script in the repository to assist with this located at &lt;tt&gt;build/deleted_file_check.php&lt;/tt&gt;. Running &lt;tt&gt;php build/deleted_file_check.php&lt;/tt&gt; with its required &lt;tt&gt;--from&lt;/tt&gt; option will write a file to &lt;tt&gt;build/deleted_files.txt&lt;/tt&gt; with the list of files deleted since the from reference. Please see the PHP file for all documentation about this script.<br /> <br /> The following steps require the individual to create commits and tags. It is suggested that these commits and tags be GPG signed as an extra security step but this is not a mandatory requirement as of this writing.<br /> <br /> If creating a security release, at this point you should apply all patches provided by the security team.<br /> <br /> Once it is confirmed that the deleted files listing is correct, the &lt;tt&gt;build/bump.php&lt;/tt&gt; script should be executed to set the new version number. This script will also perform maintenance steps such as correcting the copyright year ranges for all files and replacing the &lt;tt&gt;__DEPLOY_VERSION__&lt;/tt&gt; placeholder. Please see the file for all documentation about this script.<br /> <br /> After running this script, review all changes with &lt;tt&gt;git diff&lt;/tt&gt; as a final check before creating your release commit. Once you are satisfied that all changes are correct, commit your changes locally. Once committed, create the release tag locally; all release tags should be the version number you are creating and should match the output of &lt;tt&gt;Joomla\CMS\Version::getShortVersion()&lt;/tt&gt; (so if you have created 3.9.0-beta2 then the tag should be named 3.9.0-beta2).<br /> <br /> Once the tag has been created, you will run the &lt;tt&gt;build/build.php&lt;/tt&gt; script to generate the release packages. To ensure a clean build is produced, the script makes an archive of the tag you are building using the &lt;tt&gt;git archive&lt;/tt&gt; command and extracts this to the &lt;tt&gt;build/tmp/&lt;timestamp&gt;&lt;/tt&gt; directory. Depending on the patch version number, the following packages will be created in the &lt;tt&gt;build/tmp/packages&lt;/tt&gt;:<br /> <br /> * 0: Full installation and upgrade packages<br /> * 1: Full installation, upgrade packages, and patch packages for x.y.0 to x.y.1<br /> * 2+: Full installation, upgrade packages, patch packages for x.y.0 to x.y.&lt;new&gt; and x.y.&lt;new-1&gt; to x.y.&lt;new&gt; (i.e. when creating 3.8.8 this will create a patch package suitable for all 3.8.x releases and an optimized patch package for 3.8.7 to 3.8.8)<br /> <br /> Additionally, the script will generate a &lt;tt&gt;build/tmp/checksums.txt&lt;/tt&gt; file with the checksums for all generated packages. &lt;tt&gt;build/tmp/github_release.txt&lt;/tt&gt; is also produced which is a text template used for the GitHub releases.<br /> <br /> After the packages are created, you should validate that you are able to install and update a site using the ZIP packages (as these are the most frequently used type and served by our update system).<br /> <br /> == Publishing a Release ==<br /> === Release Packages ===<br /> Depending on the type of release being created, you will publish the release packages in different locations.<br /> <br /> ==== Alpha, Beta, Release Candidate ====<br /> The packages for these releases are uploaded to GitHub. When ready to publish, you should push the release tag you created to GitHub and use their interface to create a release from the tag and upload the packages.<br /> <br /> ==== Stable ====<br /> The packages for stable releases are uploaded to multiple locations, this is in part driven by the fact that the Amazon Web Services (AWS) S3 region used by Joomla is blocked in some locations therefore download mirrors are available when necessary.<br /> <br /> Note that the Joomla! Downloads Portal release can be done in advance (as long as the release is kept unpublished until release day). The Update server and GitHub releases are public by default and therefore should only be done at the time of release.<br /> <br /> ===== Joomla! Downloads Portal =====<br /> The canonical source for all stable releases is the [https://downloads.joomla.org/ Joomla! Downloads Portal]. The packages served from the site use Joomla's AWS account. You will need to log into the AWS console to upload the packages to S3 under the &lt;tt&gt;joomla-official-downloads&lt;/tt&gt; bucket. The exact path inside the bucket is &lt;tt&gt;joomladownloads/joomla&lt;version&gt;&lt;/tt&gt; where &lt;tt&gt;&lt;version&gt;&lt;/tt&gt; is the major version number (i.e. &lt;tt&gt;joomla3&lt;/tt&gt;), note for compatibility with Akeeba Release System folders for each individual release are not used. You can use [https://aws.amazon.com/cli/ AWS CLI] to upload these files - but MFA is still required - follow the procedure documented [https://aws.amazon.com/premiumsupport/knowledge-center/authenticate-mfa-cli/ here] or use a tool to automate this such as [https://github.com/broamski/aws-mfa AWS-MFA]<br /> <br /> Once files have been uploaded to S3 then you need to generate the release in Akeeba Release System on the Downloads Portal. To generate all required items quickly it's recommended to use the &lt;tt&gt;cli/ars-create-cms-release.php&lt;/tt&gt; script - the source for this can be found on [https://github.com/joomla/downloads.joomla.org/blob/master/www/cli/ars-create-cms-release.php Github].<br /> <br /> Note that if you need to rebuild a package - for example because issues are found in the release candidate - you do not need to re-create the ARS resources but simply delete and reupload the S3 packages then use the &lt;tt&gt;cli/ars-get-hashes.php&lt;/tt&gt; script on the downloads site (which simply update the checksums for each item in the release) - source code for this is also located at [https://github.com/joomla/downloads.joomla.org/blob/master/www/cli/ars-get-hashes.php Github].<br /> <br /> ===== Joomla! Update Server =====<br /> The Joomla! Update Server is used as a mirror for the download packages. After connecting to the server, you should create a new folder at &lt;tt&gt;www/releases/&lt;version&gt;&lt;/tt&gt; (i.e. &lt;tt&gt;www/releases/3.9.1&lt;/tt&gt; for the 3.9.1 release) and upload the packages here.<br /> <br /> ===== GitHub =====<br /> The packages are also uploaded to GitHub. This is similar to the steps for alpha, beta, and release candidate releases above. Note that you only need to push the release tag at this point (i.e. &lt;tt&gt;git push --tags&lt;/tt&gt;), you can wait to push the updated release branch until after the release is available.<br /> <br /> === Announcements ===<br /> ==== joomla.org ====<br /> For all stable releases, the main release announcement is published to the &lt;tt&gt;Joomla! Official News &gt; Project Release News&lt;/tt&gt; category on the main &lt;tt&gt;joomla.org&lt;/tt&gt; website. This is primarily handled by the Marketing team - however release leads are expected to contribute to the ''Bug fixes and Improvements'' section as well as highlighting any other information that may need to be called out as part of release notes. After release the Social Media team need to be made aware to ensure the release is available on social media - use the ''Contact the Social Media Team'' Channel on Glip.<br /> <br /> For a minor release, an updated version of the landing page at &lt;tt&gt;joomla.org/4&lt;/tt&gt; (previously &lt;tt&gt;joomla.org/3&lt;/tt&gt;) is published. Generally, this site is backed up from the sandbox location and transferred to the live domain shortly before release, this transfer should be coordinated with the [https://volunteers.joomla.org/teams/webmasters-team Webmasters Team].<br /> <br /> ==== developer.joomla.org ====<br /> For security releases, all accompanying articles are published to the &lt;tt&gt;News &gt; Security Centre&lt;/tt&gt; category on the Joomla! Developer Network. As these articles are referenced from the main release announcement, these should be published at the same time.<br /> <br /> == Update Server ==<br /> The update server must be updated to alert websites that a core update is available, this subdomain is managed on GitHub at https://github.com/joomla/update.joomla.org. Prior to each release, a pull request should be prepared with necessary changes for the release (generally this updates the version number, announcement URL, package URLs, and package checksums for the stable release and updating the version number for the nightly builds), see https://github.com/joomla/update.joomla.org/pull/117 as an example of this update for the 3.9.1 release. Pushes to the &lt;tt&gt;master&lt;/tt&gt; branch of this repo are automatically deployed thanks to a Jenkins job, notifications for many of the Jenkins jobs are sent to the &lt;tt&gt;.org Build Notifications&lt;/tt&gt; channel on RingCentral Glip so you should ensure a success notification was sent here otherwise check if there was an issue with the job and/or manually deploy the updated files.<br /> <br /> Note that the &lt;tt&gt;update.joomla.org&lt;/tt&gt; subdomain is behind a CDN and it generally takes 5-10 minutes for all nodes to update, if need be you can access &lt;tt&gt;update1.joomla.org&lt;/tt&gt; to verify the right files are deployed without using the CDN. Note files cache times aren't consistent and often we've seen issues where the list update file is the new version and the extension.xml file is on the old version.<br /> <br /> == Post Release Actions ==<br /> Once the release is published, there are several additional tasks that should be completed shortly after.<br /> <br /> === Post-Release Version Bump ===<br /> The version should be bumped to the next version scheduled for release using the &lt;tt&gt;build/bump.php&lt;/tt&gt; script (i.e. after the 3.9.1 release this would be bumped to 3.9.2-dev).<br /> <br /> === Branch Merging ===<br /> After incrementing the version number, you should merge all the release changes forward to other active branches (especially in the case of a security release). Ensure you pay careful attention while resolving merge conflicts, when making a merge that includes a version bump generally all files which contain the version string and/or release date will be in conflict (as of this writing this is 8 files).<br /> <br /> === Push Updated Branches ===<br /> When ready, you should directly push your updates to the Git repo. If you elect to use pull requests, the pull requests should NEVER be squashed or rebased otherwise this will wipe out Git's awareness of the merged commits and will make your next branch merges even more complex. Likewise, as an example, if the commit preparing the 3.9.1 release and bumping the version string to 3.9.2-dev were squash merged as a pull request, then the commit that the 3.9.1 release was tagged from would not be in the repository.<br /> <br /> === Update Release Milestones ===<br /> On GitHub, all merged items are assigned to a milestone to help organize items. With each release, the [https://github.com/joomla/joomla-cms/milestones milestones] should be updated to ensure that the milestone for the release you created has been closed and a milestone for the next release is open.<br /> <br /> === Regenerate Nightly Builds ===<br /> The nightly builds for any branch updated during the release process should be regenerated to include the release's changes. These can be manually triggered within the &lt;tt&gt;CMS Packaging&lt;/tt&gt; folder on the Jenkins server.<br /> <br /> === Website Updates ===<br /> With all code updates pushed, there are several website updates that need to be triggered.<br /> <br /> ==== api.joomla.org ====<br /> With each release, an updated build of the API documentation should be deployed to the &lt;tt&gt;api.joomla.org&lt;/tt&gt; website. These updates are triggered with the &lt;tt&gt;Joomla! API &gt; Deploy Docs - CMS&lt;/tt&gt; job on Jenkins. As this job relies on the release tags from the CMS repo, this can only be done after the release tag has been pushed.<br /> <br /> ==== developer.joomla.org ====<br /> After a release, the &lt;tt&gt;Joomla! Project Roadmap&lt;/tt&gt; article in the &lt;tt&gt;Uncategorised&lt;/tt&gt; category should be updated to reflect the newly released version and updated links, as well as adding expected release dates for the next release.<br /> <br /> The version whitelist for the statistics server should also be updated to allow the next version to be submitted; if you have not already, you should have a clone of the https://github.com/joomla/statistics-server repository on your local system. Once cloned and set up, run the &lt;tt&gt;bin/stats tags:joomla&lt;/tt&gt; command to regenerate the Joomla version whitelist. As this command relies on the release tags from the CMS repo, this can only be done after the release tag has been pushed. The updated &lt;tt&gt;versions/joomla.json&lt;/tt&gt; should be committed and pushed, and a Jenkins job will deploy the updated site resources.<br /> <br /> == Additional Considerations ==<br /> The release manager or a delegate is suggested to be in communication with the Webmasters Team to ensure the &lt;tt&gt;joomla.org&lt;/tt&gt; websites are updated in a timely manner. When a security release is scheduled, it is encouraged to share the update release package with the team so that our sites may be updated before the fix is made public to mitigate the chance of the vulnerability being used to exploit one of our sites. It also provides additional testing for security fixes on real world sites in addition to the tests performed by the CMS Release Team.<br /> <br /> = Framework Release Cycle =<br /> The packages of the Joomla Framework are on an independent lifecycle meaning each package can be updated and released independently of all others. Generally the only restriction is with major releases, which should coincide with the CMS release cycle (i.e. CMS 3.x uses Framework 1.x, CMS 4.x will use Framework 2.x therefore Framework 2.0 stable releases should not be made until the CMS is in its beta phase at the earliest).<br /> <br /> == Tagging a Release ==<br /> Most packages can be tagged and released through the &lt;tt&gt;Joomla! Framework &gt; Package Release&lt;/tt&gt; job on Jenkins, however as of this writing this job only supports tagging releases from a repository's &lt;tt&gt;master&lt;/tt&gt; branch. To tag a release, select the package you wish to update and specify the version you are releasing in the job's parameters and run the job; all releases should follow Semantic Versioning to set the correct number.<br /> <br /> Once the job has completed, you should verify the new release is visible on [https://packagist.org/packages/joomla/ Packagist]. Within a day, the new update should be visible on the [https://framework.joomla.org/status Joomla Framework Status page] (the database is updated via cron job reading from Packagist's API), if the updated version isn't seen on the site in a relatively timely manner you should clone the website locally and debug the &lt;tt&gt;packagist:sync:releases&lt;/tt&gt; command.<br /> <br /> == Security Releases ==<br /> When a security release is created, a pull request should be sent to the [https://github.com/FriendsOfPHP/security-advisories FriendsOfPHP/security-advisories repository] with relevant details. This repository is used by many tools in the PHP and Composer ecosystem to alert users of security issues. https://github.com/FriendsOfPHP/security-advisories/pull/134 is an example of this pull request.<br /> <br /> [[Category:Bug Squad]]<br /> [[Category:Coordinators]]<br /> [[Category:Development]]</div>

Wilsonge