Joomla! Documentation - User contributions [en]

J5.x:J5.1.3:Pagination broken for Smart Search

2024-08-20T18:04:08Z

Bembelimen: Bembelimen moved page J5.x:J5.1.3:Pagination broken for Smart Search to J5.x:Pagination broken for Smart Search

#REDIRECT [[J5.x:Pagination broken for Smart Search]]

J5.x:Pagination broken for Smart Search

2024-08-20T18:04:08Z

Bembelimen: Bembelimen moved page J5.x:J5.1.3:Pagination broken for Smart Search to J5.x:Pagination broken for Smart Search

==Errors reported==
Smart search loses search and filter parameters when going to page 2 or up.

==Versions affected== 
{{tip|This pertains only to Joomla! version(s): '''5.1.3''', '''4.4.7'''|title=General Information}} 

==What is the cause== 
[[J5.x:Pagination_class_removes_query_parameters]] filters away this parameters.

==How to fix==
Update to 4.4.8 and 5.1.4 or apply the following changes from https://github.com/joomla/joomla-cms/pull/43953/files

<noinclude>
__NOTOC__
</noinclude>

<noinclude>
[[Category:Version 4.4.7 FAQ{{#translation:}}]]
[[Category:Version 5.1.3 FAQ{{#translation:}}]]
</noinclude>

J5.x:Pagination broken for Smart Search

2024-08-20T18:01:02Z

Bembelimen: Add breaking change

Category:Version 5.1.2 FAQ

2024-07-10T10:01:17Z

Bembelimen: Created page with "<noinclude><languages /></noinclude> {{Joomla version|version=5.1.2|}} <translate>  These FAQs are specific to the Joomla! 5.1.2 release. Only issues that are speci..."

<noinclude><languages /></noinclude>
{{Joomla version|version=5.1.2|}}
<translate>


These FAQs are specific to the Joomla! 5.1.2 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:832|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.</translate>

{{Note|To appear in this category, this text is required at the foot of the page:<br />
<nowiki>[[Category:Version 5.1.2 FAQ{{#translation:}}]]</nowiki>|reminder}}

{{TT|CreateFAQ|J5.x}}
<noinclude>
[[Category:Version 5.1 FAQ{{#translation:}}]]
[[Category:Joomla! 5.1{{#translation:}}]]
</noinclude>

Pizza Bugs and Fun 2024/Contributors List

2024-02-24T15:25:54Z

Bembelimen: /* Germany */

<noinclude><languages /></noinclude>

[[Image:Banner_pbf24_1100px.png|center]]

Back to [[https://www.pizza-bugs-fun.com/en/ Pizza, Bugs & Fun]]

<translate>
''Edit the page and add your name to have your contribution to PBF2024 recorded.''

== These awesome Joomlers contributed to Pizza, Bugs & Fun 2024 ==

====Austria====
* Harald Leithner
* Sigrid Gramlinger
* Christine Walk
* Florian Bauer
* Kurt W.

====France====
* Catherine Mollet
* Emmanuel Lemor
* Cyrille Poussin
* Serge Billon
* Jean-Charles Antoine
* Sebastien Lhuillier
* Yann Gomiero

====Germany====
* Martina Scholz
* Christiane Maier-Stadtherr
` Nadja Lamisch
* Benjamin Trenkle (JUG Munich)
* Dieter Ziller (max123kl)

====Greece====
* Dimitris Trikkas
* Bill Kotsias

====Italy====
* Pierantonio Borga
* Gioacchino Cipriano
* Walter Consoli
* Nicola Galgano
* Roberto Longo
* Alessandro Lumaca
* Davide Messia
* Luigi Morgantini
* Fausto Nenci
* Luca Racchetti
* Luca Sacchi Ricciardi

====Kenyia====
* James Gichuru
* Dominic Maina
* Charles Kiruru
* Esther Nyambura

====Netherlands====
* Peter Martin
* Anja de Crom
* Tom van der Laan
* Nico van de Kamp
* Steven Trooster

====Spain====

====Switzerland====
* Martin Kopp
* Christof Rimle
* Heinz Riedener
* Rahel Schierbaum
* Lea Kemper
* Doris Dreher
* Manuel Häusler
* Roger Abt
* Peter Guntern
* Vreni Angst
* Ruedi Knutti

====Uganda====

====UK====
* Mark Fleeson

====USA====
* Laura Gordon
* Olivier Buisard
* Eddie Konczel
* Sarah Berryman
* SD Williams

====Vietnam====
* Tuan Pham Ngoc

</translate>

[[Category:Volunteer Engagement{{#translation:}}]]
[[Category:Pizza_Bugs_and_Fun{{#translation:}}]]

GSoC 2024 Project Ideas

2024-01-30T12:26:49Z

Bembelimen: Fix name

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

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

If you are interested in participating as a student please review the materials on applying that are available at [https://developers.google.com/open-source/gsoc/faq Google]. We strongly encourage you to ask questions about process and projects on our
[https://joomlacommunity.cloud.mattermost.com/main/channels/gsoc2024 Mattermost chat tool].

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

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

==Project I: API Improvements ==

===Project Description===
Improve the API to cover more/all general functions in Joomla!
Go through the components to add missing calls
Implement proper authentication (oAuth2, ...)
Improve error handling

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

===Difficulty===
*Hard

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

===Mentors===
*George Wilson
*Carlos Rodriguez
*Shivam Rajput

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

==Project II: Health page ==

===Project Description===
A page to check the integrity of your Joomla! files and database structure (also for 3rd party extensions).
Built as a series of plugin checks that feed into a dashboard

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

===Difficulty===
*Medium

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

===Mentors===
*Rishabh Ranjan Jha
*Shazma Siddiqui
*Shubham Verma

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

==Project III: Increase test coverage ==

===Project Description===
System or unit tests are an essential part of the development process to ensure stability of any application.
https://magazine.joomla.org/all-issues/october-2022/off-to-cyprus-ehm-cypress-how-joomla-does-its-end-to-end-testing

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript
*Besides that, a must have: VueJS
*Nice to have: Joomla! 4 template creation
*Cypress

===Difficulty===
*Medium

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

===Mentors===
*Franciska Perisa
*Allon Moritz
*Anurag Kumar

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

==Project IV: Command Palette for Joomla 5.3 ==

===Project Description===
An interface within Joomla CMS for Command Palette, to type in actions like creating new artiles; Execute the command. The project should be integrated with the shortcuts; a good example is VS code command palette.

===Expected Outcome ===
*Command Palette Integrated with adequate number of commands.
*Integration of short keys

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript
*Besides that, a must have: VueJS
*Nice to have: Joomla! 4 template creation
*Cypress

===Difficulty===
*Medium

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

===Mentors===
*Benjamin
*Christiane
*Martina

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

==Project V: Enhancing Database Driver for JSON Field Management 5.3 ==

===Project Description===

The current database driver lacks comprehensive features for handling JSON fields, resulting in limitations when it comes to querying, indexing, and updating JSON data. As JSON becomes increasingly prevalent in application development, it is essential to optimize the database driver to meet the evolving needs of developers and ensure better compatibility with modern data storage requirements.
Proposed Enhancements:

Improved Querying:
Enhance the database driver to support advanced querying capabilities for JSON fields. This includes the ability to search for specific key-value pairs within JSON objects, perform range queries on numeric values in JSON, and execute complex queries involving nested JSON structures.

Indexing Support:
Introduce indexing options specifically tailored for JSON fields. This will significantly improve query performance by allowing the database engine to efficiently locate and retrieve data from JSON fields. Indexing should support both simple and nested structures within JSON.

Validation and Schema Enforcement:
Implement mechanisms for validating JSON data against predefined schemas. This will ensure data integrity by enforcing a consistent structure for JSON fields, preventing the insertion of invalid or inconsistent data.

Atomic Updates:
Enable atomic updates for JSON fields to ensure that changes to JSON data are applied consistently and without the risk of data corruption. This includes supporting operations like adding, updating, or removing elements within JSON arrays or objects within a single atomic transaction.

Compatibility and Standardization:
Ensure compatibility with widely adopted JSON standards and specifications. This will enhance interoperability between different applications and systems, providing a standardized way of handling JSON data within the database.

===Expected Outcome ===
*Improved query performance and efficiency when working with JSON fields.
*Enhanced data integrity through validation and schema enforcement.
*Better support for modern application development practices relying on JSON data.
*Increased flexibility for developers to build complex and efficient queries involving JSON content.By implementing these enhancements, we aim to elevate the database driver's capabilities in managing JSON fields, providing developers with a more robust and flexible solution for handling JSON data within the database.

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript
*Besides that, a must have: VueJS
*Nice to have: Joomla! 4 template creation
*Cypress

===Difficulty===
*Hard

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

===Mentors===
*Richard Faith
*Nicholas

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

==Project V: Model Driven approach for CMS integration ==

===Project Description===
To exchange information between different Content Management Systems, for integration or migration purposes, many ad hoc solutions have been created. A more universally applicable approach would be establishing a common, shared model for content. This would enable the creation of specific models tailored to individual CMSs, facilitating model-to-model transformations. A standardized content model would provide a more versatile and efficient solution for handling information exchange across diverse CMS platforms.

There was a standard for content integration, CMIS [http://docs.oasis-open.org/cmis/CMIS/v1.1/cs01/CMIS-v1.1-cs01.html], but it is hardly used nowadays, mainly because it is not up to date with modern web content management.
A recent project [https://modeling-languages.com/content-management-system-modeling-generation] has used the API of WordPress and Drupal to gather information in a more general content model.

===Expected Outcome ===
*Work towards a gradually more general (formal) content model, usable in multiple CMSs.
*Gradually adding more CMSs. Adjusting the general model and defining the specificities per CMS. Start with Joomla and 1 other.
*Write code to export content from those CMSs to the general model using the API.
*Write code to import content from the general model using the API.

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript
*Besides that, a must have: VueJS
*Nice to have: Joomla! 4 template creation
*Cypress

===Difficulty===
*Hard

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

===Mentors===
*Herman

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

==Project VI: Using AI for automated testing ==

===Project Description===
With the help of AI to provide an environment to increase the test coverage when new features do land in the CMS.

===Expected Outcome ===
*AI offers new possibilities to define system tests which can be used in our CI process. With the knowledge of end users together with artificial intelligence, it will reduce the amount of bugs. Community members without developer experience will be able to help increase the testing coverage.

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript
*Besides that, a must have: VueJS
*Nice to have: Joomla! 4 template creation
*Cypress

===Difficulty===
*Mediun

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

===Mentors===
*Allon
*Astrid

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

==Project VII: AI for improving accessibility of WEB sites ==

===Project Description===
Until now, our accessibility plugin helps writing accessible content but does not check the whole website for accessibility.
AI could help to make websites accessible
*generating accessible color scheme helps the web designer,
*improve navigation logic
*verify optimal keyboard access to the site
*generate alt-text via image recognition from AI
*and others

===Expected Outcome ===
*Better Accessibility of the Web
*Support for Template developers (agencies)
*Advantage for marketing

===Knowledge Prerequisite===
*Language Requisitions: PHP, HTML, CSS and JavaScript
*Besides that, a must have: VueJS
*Nice to have: Joomla! 4 template creation
*Cypress

===Difficulty===
*Mediun

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

===Mentors===
*Christiane
*Carlos Camara Mora
*Viviana Menzel

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

Category:Version 5.0.1 FAQ

2023-11-29T09:08:16Z

Bembelimen: Fix version

<noinclude><languages /></noinclude>
{{Joomla version|version=5.0.1|}}
<translate>

These FAQs are specific to the Joomla! 5.0.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:832|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.</translate>

{{Note|To appear in this category, this text is required at the foot of the page:<br />
<nowiki>[[Category:Version 5.0.1 FAQ{{#translation:}}]]</nowiki>|reminder}}

{{TT|CreateFAQ|J5.x}}
<noinclude>
[[Category:Version 5.0 FAQ{{#translation:}}]]
[[Category:Joomla! 5.0{{#translation:}}]]
</noinclude>

Category:Version 5.0.0 FAQ

2023-11-29T09:07:55Z

Bembelimen: Revert wrong version

<noinclude><languages /></noinclude>
{{Joomla version|version=5.0.0|}}
<translate>

These FAQs are specific to the Joomla! 5.0.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:832|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.</translate>

{{Note|To appear in this category, this text is required at the foot of the page:<br />
<nowiki>[[Category:Version 5.0.0 FAQ{{#translation:}}]]</nowiki>|reminder}}

{{TT|CreateFAQ|J5.x}}
<noinclude>
[[Category:Version 5.0 FAQ{{#translation:}}]]
[[Category:Joomla! 5.0{{#translation:}}]]
</noinclude>

Category:Version 5.0.0 FAQ

2023-11-29T09:07:25Z

Bembelimen: Fix category

<noinclude><languages /></noinclude>
{{Joomla version|version=5.0.0|}}
<translate>

These FAQs are specific to the Joomla! 5.0.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:832|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.</translate>

{{Note|To appear in this category, this text is required at the foot of the page:<br />
<nowiki>[[Category:Version 5.0.0 FAQ{{#translation:}}]]</nowiki>|reminder}}

{{TT|CreateFAQ|J5.x}}
<noinclude>
[[Category:Version 5.0.0 FAQ{{#translation:}}]]
[[Category:Joomla! 5.0{{#translation:}}]]
</noinclude>

Category:Version 5.0.1 FAQ

2023-11-29T09:06:37Z

Bembelimen: Create 5.0.1 FAQ page

<noinclude><languages /></noinclude>
{{Joomla version|version=5.0.1|}}
<translate>

These FAQs are specific to the Joomla! 5.0.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:832|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.</translate>

{{Note|To appear in this category, this text is required at the foot of the page:<br />
<nowiki>[[Category:Version 5.0.1 FAQ{{#translation:}}]]</nowiki>|reminder}}

{{TT|CreateFAQ|J5.x}}
<noinclude>
[[Category:Version 5.0.1 FAQ{{#translation:}}]]
[[Category:Joomla! 5.0{{#translation:}}]]
</noinclude>

J4.x:Fix "Reinstall Joomla! core files" in 4.4.0 broke Installation and backend login

2023-10-18T10:38:10Z

Bembelimen: Added some details

==Errors reported==
For a short amount of time when having an up-to-date Joomla 4.4.0 installation reinstalling the core files via the updater leads to a broken Joomla 4.0 page with Joomla 5.0 files copied over. This lead to a broken installation without the chance to login.

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

==What is the cause==
Due to a mis-configurated of the update server Joomla! 5.0 files were shipped instead of Joomla! 4.4 packages. As the database was not updated in the process and new classes were introduced, the page breaks.

==How to fix==
* Download the latest [https://downloads.joomla.org/cms/joomla4/4-4-0/Joomla_4-4-0-Stable-Update_Package.zip Joomla! 4.4.0 Upgrade Package (.zip)] ('''not''' Full Package) from [https://downloads.joomla.org/cms/joomla4/4-4-0 The official download page]
* Unzip the ZIP file locally
* Connect via FTP client to your server and copy the full content over your broken website
* Delete the file ''administrator/cache/autoload_psr4.php''
* (optional) Clean your cache
* Try to login into your website again

If you have access via SSH to your server you can alternatively execute the following steps:

* Connect to your server via SSH
* Download the Upgrade Package: <source lang="php">
wget https://downloads.joomla.org/cms/joomla4/4-4-0/Joomla_4-4-0-Stable-Update_Package.zip
</source>
* Unzip the ZIP file: <source lang="php">unzip Joomla_4-4-0-Stable-Update_Package.zip</source>
* Confirm, that you want to overwrite the existing files
* Delete the autoload PSR4 file <source lang="php">rm -f administrator/cache/autoload_psr4.php</source>
* (optional) Clean your cache
* Try to login into your website again

__NOTOC__


<noinclude>
[[Category:Version 4.4.0 FAQ{{#translation:}}]]
</noinclude>

J4.x:Fix "Reinstall Joomla! core files" in 4.4.0 broke Installation and backend login

2023-10-18T10:19:05Z

Bembelimen: Typo

==Errors reported==
For a short amount of time when having an up-to-date Joomla 4.4.0 installation reinstalling the core files via the updater leads to a broken Joomla 5.0 page. This lead to a broken installation without the chance to login.

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

==What is the cause==
Due to a mis-configurated of the update server Joomla! 5.0 files were shipped instead of Joomla! 4.4 packages. As the database was not updated in the process and new classes were introduced, the page breaks.

==How to fix==
* Download the latest [https://downloads.joomla.org/cms/joomla4/4-4-0/Joomla_4-4-0-Stable-Update_Package.zip Joomla! 4.4.0 Upgrade Package (.zip)] ('''not''' Full Package) from [https://downloads.joomla.org/cms/joomla4/4-4-0 The official download page]
* Unzip the ZIP file locally
* Connect via FTP client to your server and copy the full content over your broken website
* Delete the file ''administrator/cache/autoload_psr4.php''
* (optional) Clean your cache
* Try to login into your website again

If you have access via SSH to your server you can alternatively execute the following steps:

* Connect to your server via SSH
* Download the Upgrade Package: <source lang="php">
wget https://downloads.joomla.org/cms/joomla4/4-4-0/Joomla_4-4-0-Stable-Update_Package.zip
</source>
* Unzip the ZIP file: <source lang="php">unzip Joomla_4-4-0-Stable-Update_Package.zip</source>
* Confirm, that you want to overwrite the existing files
* Delete the autoload PSR4 file <source lang="php">rm -f administrator/cache/autoload_psr4.php</source>
* (optional) Clean your cache
* Try to login into your website again

__NOTOC__


<noinclude>
[[Category:Version 4.4.0 FAQ{{#translation:}}]]
</noinclude>

J4.x:Fix "Reinstall Joomla! core files" copied Joomla 5 over a Joomla 4 installation without migration

2023-10-18T10:09:38Z

Bembelimen: Bembelimen moved page J4.x:Fix "Reinstall Joomla! core files" copied Joomla 5 over a Joomla 4 installation without migration to J4.x:Fix "Reinstall Joomla! core files" in 4.4.0 broke Installation and backend login

#REDIRECT [[J4.x:Fix "Reinstall Joomla! core files" in 4.4.0 broke Installation and backend login]]

J4.x:Fix "Reinstall Joomla! core files" in 4.4.0 broke Installation and backend login

2023-10-18T10:09:37Z

==Errors reported==
For a short amount of time when having an up-to-date Joomla 4.4.0 installation reinstalling the core files via the updater leads to a broken Joomla 5.0 page. This lead to a broken installation without the chance to login.

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

==What is the cause==
Due to a miss-configuration of the update server Joomla! 5.0 files were shipped instead of Joomla! 4.4 packages. As the database was not updated in the process and new classes were introduced, the page breaks.

==How to fix==
* Download the latest [https://downloads.joomla.org/cms/joomla4/4-4-0/Joomla_4-4-0-Stable-Update_Package.zip Joomla! 4.4.0 Upgrade Package (.zip)] ('''not''' Full Package) from [https://downloads.joomla.org/cms/joomla4/4-4-0 The official download page]
* Unzip the ZIP file locally
* Connect via FTP client to your server and copy the full content over your broken website
* Delete the file ''administrator/cache/autoload_psr4.php''
* (optional) Clean your cache
* Try to login into your website again

If you have access via SSH to your server you can alternatively execute the following steps:

* Connect to your server via SSH
* Download the Upgrade Package: <source lang="php">
wget https://downloads.joomla.org/cms/joomla4/4-4-0/Joomla_4-4-0-Stable-Update_Package.zip
</source>
* Unzip the ZIP file: <source lang="php">unzip Joomla_4-4-0-Stable-Update_Package.zip</source>
* Confirm, that you want to overwrite the existing files
* Delete the autoload PSR4 file <source lang="php">rm -f administrator/cache/autoload_psr4.php</source>
* (optional) Clean your cache
* Try to login into your website again

__NOTOC__


<noinclude>
[[Category:Version 4.4.0 FAQ{{#translation:}}]]
</noinclude>

J4.x:Fix "Reinstall Joomla! core files" in 4.4.0 broke Installation and backend login

2023-10-18T10:06:53Z

Bembelimen: Bembelimen moved page J4.x:Fix "Reinstall Joomla! core files" copied Joomla 5 over a Joomla 4 installation witout migration to J4.x:Fix "Reinstall Joomla! core files" copied Joomla 5 over a Joomla 4 installation without migration without leaving a redirect

==Errors reported==
For a short amount of time when having an up-to-date Joomla 4.4.0 installation reinstalling the core files via the updater leads to a broken Joomla 5.0 page. This lead to a broken installation without the chance to login.

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

==What is the cause==
Due to a miss-configuration of the update server Joomla! 5.0 files were shipped instead of Joomla! 4.4 packages. As the database was not updated in the process and new classes were introduced, the page breaks.

==How to fix==
* Download the latest [https://downloads.joomla.org/cms/joomla4/4-4-0/Joomla_4-4-0-Stable-Update_Package.zip Joomla! 4.4.0 Upgrade Package (.zip)] ('''not''' Full Package) from [https://downloads.joomla.org/cms/joomla4/4-4-0 The official download page]
* Unzip the ZIP file locally
* Connect via FTP client to your server and copy the full content over your broken website
* Delete the file ''administrator/cache/autoload_psr4.php''
* (optional) Clean your cache
* Try to login into your website again

If you have access via SSH to your server you can alternatively execute the following steps:

* Connect to your server via SSH
* Download the Upgrade Package: <source lang="php">
wget https://downloads.joomla.org/cms/joomla4/4-4-0/Joomla_4-4-0-Stable-Update_Package.zip
</source>
* Unzip the ZIP file: <source lang="php">unzip Joomla_4-4-0-Stable-Update_Package.zip</source>
* Confirm, that you want to overwrite the existing files
* Delete the autoload PSR4 file <source lang="php">rm -f administrator/cache/autoload_psr4.php</source>
* (optional) Clean your cache
* Try to login into your website again

__NOTOC__


<noinclude>
[[Category:Version 4.4.0 FAQ{{#translation:}}]]
</noinclude>

Category:Version 4.4.0 FAQ

2023-10-18T09:59:46Z

Bembelimen: Add 4.4 info text

<noinclude><languages /></noinclude>
{{Joomla version|version=4.4.0|}}
<translate>

These FAQs are specific to the Joomla! 4.4.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:807|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.</translate>

{{Note|To appear in this category, this text is required at the foot of the page:<br />
<nowiki>[[Category:Version 4.4.0 FAQ{{#translation:}}]]</nowiki>|reminder}}

{{TT|CreateFAQ|J4.x}}
<noinclude>
[[Category:Version 4.4 FAQ{{#translation:}}]]
[[Category:Joomla! 4.4{{#translation:}}]]
</noinclude>

J4.x:Fix "Reinstall Joomla! core files" in 4.4.0 broke Installation and backend login

2023-10-18T09:58:15Z

Bembelimen: Bembelimen moved page J5.x:Fix "Reinstall Joomla! core files" copied Joomla 5 over a Joomla 4 installation witout migration to J4.x:Fix "Reinstall Joomla! core files" copied Joomla 5 over a Joomla 4 installation witout migration without leaving a redirect

==Errors reported==
For a short amount of time when having an up-to-date Joomla 4.4.0 installation reinstalling the core files via the updater leads to a broken Joomla 5.0 page. This lead to a broken installation without the chance to login.

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

==What is the cause==
Due to a miss-configuration of the update server Joomla! 5.0 files were shipped instead of Joomla! 4.4 packages. As the database was not updated in the process and new classes were introduced, the page breaks.

==How to fix==
* Download the latest [https://downloads.joomla.org/cms/joomla4/4-4-0/Joomla_4-4-0-Stable-Update_Package.zip Joomla! 4.4.0 Upgrade Package (.zip)] ('''not''' Full Package) from [https://downloads.joomla.org/cms/joomla4/4-4-0 The official download page]
* Unzip the ZIP file locally
* Connect via FTP client to your server and copy the full content over your broken website
* Delete the file ''administrator/cache/autoload_psr4.php''
* (optional) Clean your cache
* Try to login into your website again

If you have access via SSH to your server you can alternatively execute the following steps:

* Connect to your server via SSH
* Download the Upgrade Package: <source lang="php">
wget https://downloads.joomla.org/cms/joomla4/4-4-0/Joomla_4-4-0-Stable-Update_Package.zip
</source>
* Unzip the ZIP file: <source lang="php">unzip Joomla_4-4-0-Stable-Update_Package.zip</source>
* Confirm, that you want to overwrite the existing files
* Delete the autoload PSR4 file <source lang="php">rm -f administrator/cache/autoload_psr4.php</source>
* (optional) Clean your cache
* Try to login into your website again

__NOTOC__


<noinclude>
[[Category:Version 4.4.0 FAQ{{#translation:}}]]
</noinclude>

J4.x:Fix "Reinstall Joomla! core files" in 4.4.0 broke Installation and backend login

2023-10-18T09:57:49Z

Bembelimen: Add category

==Errors reported==
For a short amount of time when having an up-to-date Joomla 4.4.0 installation reinstalling the core files via the updater leads to a broken Joomla 5.0 page. This lead to a broken installation without the chance to login.

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

==What is the cause==
Due to a miss-configuration of the update server Joomla! 5.0 files were shipped instead of Joomla! 4.4 packages. As the database was not updated in the process and new classes were introduced, the page breaks.

==How to fix==
* Download the latest [https://downloads.joomla.org/cms/joomla4/4-4-0/Joomla_4-4-0-Stable-Update_Package.zip Joomla! 4.4.0 Upgrade Package (.zip)] ('''not''' Full Package) from [https://downloads.joomla.org/cms/joomla4/4-4-0 The official download page]
* Unzip the ZIP file locally
* Connect via FTP client to your server and copy the full content over your broken website
* Delete the file ''administrator/cache/autoload_psr4.php''
* (optional) Clean your cache
* Try to login into your website again

If you have access via SSH to your server you can alternatively execute the following steps:

* Connect to your server via SSH
* Download the Upgrade Package: <source lang="php">
wget https://downloads.joomla.org/cms/joomla4/4-4-0/Joomla_4-4-0-Stable-Update_Package.zip
</source>
* Unzip the ZIP file: <source lang="php">unzip Joomla_4-4-0-Stable-Update_Package.zip</source>
* Confirm, that you want to overwrite the existing files
* Delete the autoload PSR4 file <source lang="php">rm -f administrator/cache/autoload_psr4.php</source>
* (optional) Clean your cache
* Try to login into your website again

__NOTOC__


<noinclude>
[[Category:Version 4.4.0 FAQ{{#translation:}}]]
</noinclude>

J4.x:Fix "Reinstall Joomla! core files" in 4.4.0 broke Installation and backend login

2023-10-18T09:56:34Z

Bembelimen: Add fix for broken reinstall installations

==Errors reported==
For a short amount of time when having an up-to-date Joomla 4.4.0 installation reinstalling the core files via the updater leads to a broken Joomla 5.0 page. This lead to a broken installation without the chance to login.

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

==What is the cause==
Due to a miss-configuration of the update server Joomla! 5.0 files were shipped instead of Joomla! 4.4 packages. As the database was not updated in the process and new classes were introduced, the page breaks.

==How to fix==
* Download the latest [https://downloads.joomla.org/cms/joomla4/4-4-0/Joomla_4-4-0-Stable-Update_Package.zip Joomla! 4.4.0 Upgrade Package (.zip)] ('''not''' Full Package) from [https://downloads.joomla.org/cms/joomla4/4-4-0 The official download page]
* Unzip the ZIP file locally
* Connect via FTP client to your server and copy the full content over your broken website
* Delete the file ''administrator/cache/autoload_psr4.php''
* (optional) Clean your cache
* Try to login into your website again

If you have access via SSH to your server you can alternatively execute the following steps:

* Connect to your server via SSH
* Download the Upgrade Package: <source lang="php">
wget https://downloads.joomla.org/cms/joomla4/4-4-0/Joomla_4-4-0-Stable-Update_Package.zip
</source>
* Unzip the ZIP file: <source lang="php">unzip Joomla_4-4-0-Stable-Update_Package.zip</source>
* Confirm, that you want to overwrite the existing files
* Delete the autoload PSR4 file <source lang="php">rm -f administrator/cache/autoload_psr4.php</source>
* (optional) Clean your cache
* Try to login into your website again

__NOTOC__

Category:Version 5.0.0 FAQ

2023-10-18T09:41:13Z

Bembelimen: Set FAQ creation to 5.x

Category:Version 5.0.0 FAQ

2023-10-18T09:35:50Z

Bembelimen: Create page

<noinclude><languages /></noinclude>
{{Joomla version|version=5.0.0|}}
<translate>

These FAQs are specific to the Joomla! 5.0.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:832|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.</translate>

{{Note|To appear in this category, this text is required at the foot of the page:<br />
<nowiki>[[Category:Version 5.0.0 FAQ{{#translation:}}]]</nowiki>|reminder}}

{{TT|CreateFAQ}}
<noinclude>
[[Category:Version 5.0 FAQ{{#translation:}}]]
[[Category:Joomla! 5.0{{#translation:}}]]
</noinclude>

J4.x:Fix "Cannot reorder menu entries"

2022-05-12T06:44:10Z

Bembelimen:

==Errors reported== 
When reordering submenu items, the new ordering is not saved. See [https://github.com/joomla/joomla-cms/issues/37778 the following issue for a detailed description].

==Versions affected== 
{{tip|This affects only the following Joomla! version(s): '''4.1.3'''|title=General Information}} 

==What is the cause== 
Conflicting parameters are send to the server which prevent Joomla! from saving the new ordering.

==How to fix== 
See this [https://github.com/joomla/joomla-cms/pull/37781 Pull Request] for the fix, especially [https://github.com/joomla/joomla-cms/pull/37781#issuecomment-1124536569 this comment] for the files.

__NOTOC__


<noinclude>
[[Category:Version 4.1.3 FAQ]]
</noinclude>

J4.x:Fix "Cannot reorder menu entries"

2022-05-12T06:40:10Z

Bembelimen: Created page with " ==Errors reported==  When reordering submenu items, the new ordering is not saved. ==Versions affected..."

==Errors reported== 
When reordering submenu items, the new ordering is not saved.

==Versions affected== 
{{tip|This affects only the following Joomla! version(s): '''4.1.3'''|title=General Information}} 

==What is the cause== 
Conflicting parameters are send to the server which prevent Joomla! from saving the new ordering.

==How to fix== 
See this [https://github.com/joomla/joomla-cms/pull/37781 Pull Request] for the fix, especially [https://github.com/joomla/joomla-cms/pull/37781#issuecomment-1124536569 this comment] for the files.

__NOTOC__


<noinclude>
[[Category:Version 4.1.3 FAQ]]
</noinclude>

GSoC 2022 Project Ideas

2022-04-28T08:35:28Z

Bembelimen: Update mentors list

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

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

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

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

==Project I: Workflow/scheduler ==

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

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

===Difficulty===
*Medium

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

===Mentors===
*Yatharth Vyas
*Tushar Malik
*Christiane Maier-Stadtherr
*Benjamin Trenkle

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

==Project II: Guided Tour==

===Project Description===

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

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

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

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

===Difficulty===
*Easy

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

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

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

==Project III: SEO ==

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

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

===Difficulty===

*Medium

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

===Mentors===
*Elisa Foltyn
*Jacob Wijaya
*Philip Walton

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

==Project IV: Accessibility Plugin ==

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

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

===Difficulty===

*Medium

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

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

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

==Project V: Schema.org==

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

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

===Difficulty===

*Hard

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

===Mentors===
*Rishabh Ranjan Jha
*Anurag Kumar
*Niels Braczek

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

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

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

GSoC 2022

2022-04-08T09:42:40Z

Bembelimen: Add headline for becoming a contributor

{{Top portal heading|color=white-bkgd|text-color=#333|title=Welcome to Joomla Google Summer of Code 2022 }}
[[Image:Gsoc2016.png|200px|center]]
<noinclude><languages /></noinclude>
<translate>

This page will aim to be a general informational page for students, mentors and others interested in Joomla's Google Summer of Code Program.</translate>

<translate>

{{tip|title=Make sure to check out the [[GSoC 2022 Project Ideas|2022 project list]]}} </translate>

<translate>
== What is Joomla? == </translate>
<translate>
Joomla is a very popular and well known FOSS content management system powering currently around 3-4% of the internet.</translate>
<translate>

Joomla developers are currently working on multiple projects.
* Joomla 4.x was released in August 2021, and this year's GSoC projects are aimed at developing new features or significantly enhancing existing features for the next major release of Joomla 4.x. Joomla 4.x is maintained for bugs, security and feature enhancements.
* Joomla 3.x Version is still being supported, but the focus for this version is bug and security patches only. No new features are being introduced going forward in Joomla 3.x.

Additionally, when you look through [https://github.com/joomla Joomla's Github Repositories] there are many side projects related to testing, performance, and other things.

It's important to note that [https://github.com/joomla/joomla-cms joomla-cms is the primary repository] for the development of the CMS.</translate>

<translate>
== What is GSoC? == </translate>
<translate>

Google Summer of Code is a program run by Google for college students interested in getting a stipend to contribute to Open Source Software. They will spend their summer with improving and writing new features for the project. [https://summerofcode.withgoogle.com/ Visit the Google Summer of Code website to learn more.]</translate>

<translate>

*[https://volunteers.joomla.org/teams/google-summer-of-code-joomla-team Joomla GSoC Team on Joomla Volunteers Portal]</translate>

<translate>
=== GSoC Project Timeline === </translate>
<translate>
Before getting onboard for this year's program, please familiarise yourself with:
* [https://summerofcode.withgoogle.com/how-it-works How Google Summer of Code works]
* [https://developers.google.com/open-source/gsoc/timeline Review the GSoC 2022 Timeline]</translate>

<translate>
=== Become a contributor === </translate>

<translate>
If you still think GSoC is for you, express your interest in participating in GSoC 2022 as a Contributor by filling in the [https://forms.gle/eiHgWehmWQKE9jBJ7 Joomla GSoC 2022 registration form].</translate>

Once we receive your form, you will receive:
* Some more information on participating in GSoC with Joomla
* An invitation to join Joomla's organisation chat (using RingCentral)
* Be added to a general chanel on RingCentral where we'll interact with all interested students during the application phase.
* Be added to a personal channel on RingCentral where you'll be able to interact with mentors for the project you're interested in.

<translate>
=== Project Proposal === </translate>
<translate>

Please check the [[GSoC Student Application Template]] to understand what we are expecting from your proposal.</translate>

<translate>
===Last years projects:=== </translate>
<translate>

*[https://summerofcode.withgoogle.com/archive/2019/organizations/6743345328553984/ Google Summer of Code for Joomla! 2019]
*[https://summerofcode.withgoogle.com/archive/2018/organizations/6484151049912320/ Google Summer of Code for Joomla! 2018]</translate>

<translate>
== Information For Students == 
</translate>
<translate>

* [[GSoC 2022 Project Ideas|Joomla's project list]]
* [[GSoC Student Selection Criteria]]
* [[GSoC Student Application Template]]
* [https://groups.google.com/forum/?hl=en#!forum/jgsoc Joomla GSoC Mailing List]
* [https://groups.google.com/forum/#!forum/joomla-dev-cms General Joomla CMS Developer Mailing List]</translate>

<translate>
==Information for Mentors== 
</translate>
<translate>

*Want to be a mentor? Please check the [[GSoC Mentor Guidelines]].
*[[GSoC Mentors Selection Criteria]]</translate>

<translate>
==Any questions please do contact the Joomla GSoC Core Team 2022:== 
</translate>
<translate>

*[mailto:shivam.rajput@community.joomla.org Shivam Rajput (Lead and Admin)]
*[mailto:christiane.maier-stadtherr@community.joomla.org Christiane Maier-Stadtherr (Assistant)]
*Benjamin Trenkle
*Philip Walton</translate>

<translate>
==Related Articles== 
</translate>
<translate>
===Google Summer of Code Articles on the Community Blog=== 
</translate>
<translate>

*[https://community.joomla.org/gsoc-2021.html Joomla GSoC 2021 blog articles]</translate>
<translate>

*[https://community.joomla.org/gsoc-2020.html Joomla GSoC 2020 blog articles]</translate>
<translate>

*[https://community.joomla.org/gsoc-2019.html Joomla GSoC 2019 blog articles]</translate>
<translate>

*[https://community.joomla.org/gsoc-2018.html Joomla GSoC 2018 blog articles]</translate>
<translate>

*[https://community.joomla.org/gsoc-2017.html Joomla GSoC 2017 blog articles]</translate>
<translate>

*[https://community.joomla.org/gsoc-2016.html Joomla GSoC 2016 blog articles]</translate>

<translate>
===Google Summer of Code Articles on Joomla Community Magazine=== 
</translate>
<translate>

*[https://magazine.joomla.org/all-issues/tags/google-summer-of-code Joomla Community Magazine GSoC articles]</translate>

<translate>== Getting familiar with Joomla==
Not familiar with Joomla, Github and new to Open Source?
You may be best upskilling, getting set up and getting familiar with Joomla before you apply for GSoC.
Visit the [https://www.joomla.org/contribute-to-joomla.html Contribute to Joomla page] to find out all the different ways you can help. You can get familiar with using Joomla by helping with many other aspects apart from coding. Whether it's contributing documentation, adding translations in your language, participating in marketing activities or writing a magazine article, there's many ways to still make a contribution if you're not experienced with coding, bug testing or developing in PHP.
</translate>

<translate>==Setting up your Joomla Development Environment==
Here are some resources for getting familiar with Joomla and installing a Joomla Development environment:</translate>

<translate>'''Beginners:'''

[https://magazine.joomla.org/all-issues/june-2020/github-installing-git Read this Joomla Magazine Article] that walks through the entire process of installing XAMPP on Windows, installing Joomla 4, and adding the Joomla Patch Tester</translate>

<translate>'''Intermediate:'''

[https://docs.joomla.org/Special:MyLanguage/J4.x:Setting_Up_Your_Local_Environment Setting Up Your Local Environment guide on Joomla Docs] assumes you are familiar with the base concepts needed, but has links through to various concepts of setting up your local environment to help.</translate>

<translate>'''Advanced:'''

[https://gist.github.com/ditsuke/4c100e54b24b667406e145d838c08fac Check out Tushar's Github Guide] - This guide assumes you have a local dev environment set up and are already familiar with using Git for development version control.</translate>

<translate>'''Development Tools'''

Joomla developers also have a number of tools that they use, and on RingCentral you will find channels for some of these tools where you can get further assistance with using them to develop in Joomla:
* [https://visualstudio.microsoft.com/ Microsoft Visual Studio]
* [https://www.jetbrains.com/phpstorm/ JetBrains PHPStorm]
</translate>

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

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

2022-03-30T15:56:14Z

Bembelimen: Add additional note

==Errors reported== 

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

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

==What is the cause== 

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

==How to fix== 

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

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

Now make an update to 3.10.8 or 4.1.2 or higher to apply the fix on all affected users and protect against the issue in the first place.

__NOTOC__


<noinclude>
[[Category:Version 4.1.1 FAQ{{#translation:}}]]
[[Category:Joomla! 4.1{{#translation:}}]]
[[Category:Version 3.10.7 FAQ{{#translation:}}]]
[[Category:Joomla! 3.10{{#translation:}}]]
</noinclude>

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

2022-03-30T15:52:51Z

Bembelimen: Added category

<span style="color:#FF0000"> '''According to users in the forum this method does not fix the problem''' </span> https://forum.joomla.org/viewtopic.php?p=3656713#p3656713

<span style="color:#00af89"> '''The fix is''' </span> https://www.akeeba.com/news/1750-do-not-install-the-joomla-4-1-1-and-3-10-7-updates.html

==Errors reported== 

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

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

==What is the cause== 

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

==How to fix== 

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

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

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

__NOTOC__


<noinclude>
[[Category:Version 4.1.1 FAQ{{#translation:}}]]
[[Category:Joomla! 4.1{{#translation:}}]]
[[Category:Version 3.10.7 FAQ{{#translation:}}]]
[[Category:Joomla! 3.10{{#translation:}}]]
</noinclude>

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

2022-03-29T22:06:14Z

Bembelimen:

==Errors reported== 

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

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

==What is the cause== 

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

==How to fix== 

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

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

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

__NOTOC__

GSoC 2022 Project Ideas

2022-03-27T20:05:51Z

Bembelimen: Remove unnessesary requirements

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

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

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

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

==Project I: Workflow/scheduler ==

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

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

===Difficulty===
*Medium

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

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

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

==Project II: Guided Tour==

===Project Description===

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

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

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

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

===Difficulty===
*Easy

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

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

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

==Project III: SEO ==

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

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

===Difficulty===

*Medium

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

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

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

==Project IV: Accessibility Plugin ==

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

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

===Difficulty===

*Medium

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

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

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

==Project V: Schema.org==

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

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

===Difficulty===

*Hard

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

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

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

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

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

J4.x:Fix"Database Table Structure NOT Up to Date" before Upate

2022-02-24T00:11:53Z

Bembelimen: Bembelimen moved page J4.x:Fix"Database Table Structure NOT Up to Date" before Upate to J4.x:Fix "Database Table Structure NOT Up to Date" before Upate: Missing space

#REDIRECT [[J4.x:Fix "Database Table Structure NOT Up to Date" before Upate]]

J4.x:Fix "Database Table Structure NOT Up to Date" before Update

2022-02-24T00:11:53Z

Bembelimen: Bembelimen moved page J4.x:Fix"Database Table Structure NOT Up to Date" before Upate to J4.x:Fix "Database Table Structure NOT Up to Date" before Upate: Missing space

==Errors reported==

When updating Joomla! the database table structure has to be up to date before the process can start.

The "Pre-Update Check for Joomla" complains if this is not the case.

[[File:J4-database-table-structure-up-to-date-no.jpg|Joomla! 4 - Pre-Update Check - database table structure not up to date]]

But when you go to 'System - Maintenance - Database' there is no entry available.

==Versions affected== 
{{tip|This was reported in any Joomla! 4.x versions.|title=General Information}} 

==What is the cause== 
This is caused by an empty #__schemas table in the database. Most likely this occurs when the Joomla! instance is not installed by the official Joomla! installer but e.g. though an customized script which did not fill in all required data.

==How to fix== 
We fix it by adding the missing value to the table. First we need the ID from Joomla!. Go to the #__extensions table via e.g. phpMyAdmin (or another database client). Search for name="files_joomla" and write down the ID (in our case 211).

Second we need to know the latest SQL script which is installed. Go to "administrator/components/com_admin/sql/updates/mysql" and get the file name with the highest version. In this example we assume "4.0.3-2021-09-05.sql" is the filename with the highest version. Now we have to add this in our insert query as second value:

<source lang="sql">
INSERT INTO `#__schemas` (`extension_id`, `version_id`) VALUES
(211, '4.0.3-2021-09-05');
</source>

or for PostgreSQL:
<source lang="sql">
INSERT INTO "#__schemas" ("extension_id", "version_id") VALUES
(211, '4.0.3-2021-09-05');
</source>

Replace "#__" by your database prefix (see Global Configuration) before running the statements.

Then go to "System - Maintenance - Database" and fix the tables.

Now the update should work as expected.

__NOTOC__

<noinclude>
[[Category:Version 4.1.0 FAQ{{#translation:}}]]
</noinclude>

J4.x:Fix "Database Table Structure NOT Up to Date" before Update

2022-02-24T00:08:42Z

Bembelimen: Update information regarding ID

J4.x:Fix "Database Table Structure NOT Up to Date" before Update

2022-02-24T00:05:27Z

Bembelimen: Explain how to fix empty schemas

==Errors reported==

When updating Joomla! the database table structure has to be up to date before the process can start.

The "Pre-Update Check for Joomla" complains if this is not the case.

[[File:J4-database-table-structure-up-to-date-no.jpg|Joomla! 4 - Pre-Update Check - database table structure not up to date]]

But when you go to 'System - Maintenance - Database' there is no entry available.

==Versions affected== 
{{tip|This was reported in any Joomla! 4.x versions.|title=General Information}} 

==What is the cause== 
This is caused by an empty #__schemas table in the database. Most likely this occurs when the Joomla! instance is not installed by the official Joomla! installer but e.g. though an customized script which did not fill in all required data.

==How to fix== 
We fix it by adding the missing value to the table. First we need to know the latest SQL script which is installed. Go to "administrator/components/com_admin/sql/updates/mysql" and get the file name with the highest version. In this example we assume "4.0.3-2021-09-05.sql" is the filename with the highest version. Now we have to add this in our insert query as second value:

<source lang="sql">
INSERT INTO `#__schemas` (`extension_id`, `version_id`) VALUES
(211, '4.0.3-2021-09-05');
</source>

or for PostgreSQL:
<source lang="sql">
INSERT INTO "#__schemas" ("extension_id", "version_id") VALUES
(211, '4.0.3-2021-09-05');
</source>

Replace "#__" by your database prefix (see Global Configuration) before running the statements.

Then go to "System - Maintenance - Database" and fix the tables.

Now the update should work as expected.

__NOTOC__

<noinclude>
[[Category:Version 4.1.0 FAQ{{#translation:}}]]
</noinclude>

File:J4-database-table-structure-up-to-date-no.jpg

2022-02-23T23:49:18Z

Bembelimen:

== Licensing ==
{{PD}}

J4.x:Task Scheduler

2022-01-02T18:26:42Z

Bembelimen: Add categories

== Limit Task to CLI only ==
To implement a task, which is executed via CLI only add the following code to the task XML:
<source lang="xml">
<fieldset name="aside">
<field name="cli_exclusive" type="hidden" default="1" />
</fieldset>
</source>

<noinclude>
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]
</noinclude>

J4.x:Task Scheduler

2022-01-02T18:22:59Z

Bembelimen: First start with task scheduler page

Updating from an existing version

2021-07-13T18:12:59Z

Bembelimen: Add a redirect to cover the help link in Joomla!

#Redirect [[Portal:Upgrading_Versions]]

J4.x:Workflow

2021-04-25T15:27:12Z

Bembelimen: Add information regarding versions + workflow

<noinclude><languages /></noinclude>
<noinclude>{{Joomla version|version=4.x}}</noinclude>
{{-}}
<translate>
==Introduction== 
</translate>
<translate> The Publishing Workflow component is used to replace static states (unpublished, published, trashed and archived) with a more generic approach. This way you can easily create a customized workflow to manage your articles within a component.</translate>

*<translate> The article backend view in Joomla 3.x:</translate>
[[File:Article view 3-<translate> en</translate>.png|800px]]
*<translate> The article backend view in Joomla 4.x:</translate>
[[File:J4 Articles Backend-<translate> en</translate>.png|800px]]

<translate> The article tool range is now smaller and the view generally tidier. You can create customized states for the articles and group them in categories.</translate>

<translate> There is a tutorial page containing steps for the creation of your first workflow: [[S:MyLanguage/J4.x:Workflow/Scenarios|Scenarios]].</translate><br />
<translate>

You can find more information about the implementation of the component in other areas on the page of the Google Summer of Code project DOC: [[S:MyLanguage/Publishing_Workflow_Implementation|Publishing Workflow Implementation]]</translate>

<translate> You can disable workflows at any time by visiting "articles" or "workflows" and clicking "options" in the top right. Switch to the tab "Integration" and scroll down to "Enable Workflow".</translate>

<translate>

==Terms & Definitions== 
</translate>
* <translate> ''Workflows:'' You can create several workflows. Each workflow contains states, possible transitions and item conditions.</translate>
* <translate> ''Stages:'' Stages are the start points and end points within a workflow.</translate>
* <translate> ''State:'' The state of an item can be unpublished, published, trashed or archived. A state can be changed by executing a transition</translate>
* <translate> ''Transitions:'' Transitions occur between stages. They are where the actions happen.</translate>
* <translate> ''Categories:'' Articles can be assigned to categories.</translate>

<translate>

==Workflows== 
</translate>
<translate> The workflow resembles a sequence of steps. It can be accessed via the main top menu under "Content". You will be directed to the "Workflows List", an overview of all your existing workflows. A workflow contains several states of different conditions. Items (e.g. articles) can transit through those states.</translate>

[[File:Workflows-<translate> en</translate>.png|800px|Workflows List]]

* <translate> You see the status of the workflow (published / unpublished)</translate>
* <translate> Next to the status is the title. By clicking on the title you can ''edit the workflow''</translate>
** <translate> ''Editable'': Title | Description | Status | Default Option | Permissions (Rights Management)</translate>
* <translate> Next to the title you find the option to ''Manage'' the workflow stages (for more info see [[S:MyLanguage/Publishing_Workflow#Stages|Stages]])</translate>
* <translate> Next to the "Stages" is the default option</translate>
* <translate> You find a yellow icon, next to "default", representing the number of existing stages in this workflow</translate>
* <translate> Next to the yellow circle is a blue icon that represents the number of existing transitions in this workflow (for more info see[[S:MyLanguage/Publishing_Workflow#Transitions| Transitions]])</translate>
* <translate> You can also see the workflow ID.</translate>

<translate>

==Stages== 
</translate>
<translate> The stages are accessed via the "Workflows List" container via clicking on the yellow icon showing the number of stages. You can edit the name of a stage by clicking on it.</translate>

[[File:Stages-<translate> en</translate>.png|800px|Stages View]]

[[File:Stages--edit-<translate> en</translate>.png|800px|The Edit Stage view]]

* <translate> In the second picture you can edit the stage. You can enable or disable it and write a note. It also has a "default" toggle. If there is only one item you will not be able to toggle this.</translate>

<translate>

==Transitions== 
</translate>
<translate> Articles can transit from one stage to another. The transitions can be managed through the "Workflows List" container via clicking on the blue icon. You can set several transitions that items can go through. The possible stages are based on the ones you have created for this specific workflow.</translate>

<translate> The ''current stage'' will define where this transition is applied. You can choose all stages, or a specific stage.</translate>

<translate> The ''target stage'' is the stage the workflow will end up at after the transition has taken place.</translate>

[[File:Transitions--edit--description-<translate> en</translate>.png|800px|Edit Transitions View]]

<translate> The ''transition actions'' stage allows you to define what state the item will be in after the transition is complete. For example if the item is an article it could become unpublished, which is exactly what happens in the ''unpublish'' transition. You can also define whether the item is featured or not by the end of the state.</translate>

[[File:Transitions--edit--transition-actions-<translate> en</translate>.png|800px|Edit Transition Actions]]

<translate> The ''transition notifications'' tab allows you to define whether a notification is sent during that state. For example if an article has been written but needs to be proofread, you could send an email notification to the editor.</translate>

<translate> You can also add additional message text. This will also allow you to use a [[J3.x:Language_Overrides_in_Joomla|language string]] which would make the message text translatable.</translate>

<translate> The Usergroups option will allow you to define who will receive the notification. In the example we have chosen we would choose ''editor'' as the usergroup. In that example all users within that usergroup would get a notification.</translate>

<translate> Finally there is the "more receivers" option. This allows you to choose individual users to receive this notification.</translate>

[[File:Transitions--edit--notification-<translate> en</translate>.png|800px|Edit Transition Notification]]

<translate> The final tab is the permissions tab. This allows you to set who can use this transition.</translate>

* <translate> ''Example:'' In the transition "Next Step: Publishing" items are originally of the state "unpublished". They are, for example, in need of a review. After they have been reviewed, they can transit to the state "published".</translate>

* <translate> All the workflow transition actions are Joomla! workflow plugins. If you go to System{{rarr}}Plugins. Then change the "type" dropdown to "workflow" you will see the plugins. These can be disabled like any other plugin.</translate>

[[File:Workflows--plugins--workflows-<translate> en</translate>.png|800px|Workflows Plugins]]

<translate>
==Categories== 
</translate>
<translate> Articles can be assigned to categories. They correspond to a certain workflow and can be customized in various ways. You can set a status, parent category and also restrict the access as well as the permissions. This option is not within the workflows screen. For this option you need to go to Content{{rarr}}Categories. Once there open any category and you will see a "workflows" tab.</translate>
* <translate>  ''Example:'' You have certain articles that you want to be available only for administrators or users of a higher rank. You can call your category "Restricted" and set all permissions on "Allowed" for administrators or higher. This way you do not have to set those permissions for every article concerned but can move them into this special category and save time instead.</translate>

[[File:Workflow-categories-<translate> en</translate>.png|800px]]

== Versioning ==
When the workflow is enabled fields managed by the workflow are excluded from the versioning (like "state" and "featured") to avoid permission conflicts.

<translate>
==Related Information== 
</translate>
<translate>

See also:</translate>
<translate>

* [[S:MyLanguage/Publishing_Workflow_Implementation|Publishing Workflow Implementation]]
* [[S:MyLanguage/J4.x:Workflow/Scenarios|Scenarios]]</translate>

<noinclude>
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]
[[Category:Article Management{{#translation:}}]]
</noinclude>

GSoC 2021 Project Ideas

2021-03-20T15:58:50Z

Bembelimen: Update the media manager description.

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

{{tip|title=The application for students is going to open soon!}}

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

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

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

==Project I: Frontend inline editing ==

===Project Description===
Implement a inline editing feature in the frontend for modules, articles, (and all other extensions, where it makes sense) (see: https://www.tiny.cloud/docs/demo/inline/ + https://www.tiny.cloud/blog/inline-editor/)

See https://github.com/joomla/joomla-cms/pull/30476

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===

*Medium

===Mentors===

*[mailto:roland.dalmulder@community.joomla.org Roland Dalmulder]
*[mailto:harald.leithner@community.joomla.org Harald Leithner]
*[mailto:peter.martin@community.joomla.org Peter Martin]
*[mailto:ciar4n@gmail.com Ciaran Walsh]

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

==Project II: Accessibility==

===Project Description===

Implement and improve several accessibility functions in Joomla!
Keyboard navigation

===Knowledge Prerequisite===
*Must have: PHP, mySQL, JS, CSS

===Difficulty===

*Easy

===Mentors===
*[mailto:anuragvns1999@gmail.com Anurag Kumar]
*[mailto:shivam.rajput@community.joomla.org Shivam Rajput]
*[mailto:patrick.jackson@community.joomla.org Patrick Jackson]
*[mailto:sdw@danicoenterprises.com Shirielle "SD" Williams]

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

==Project III: Feature enhancement ==

===Project Description===
====Cookies management====
*Create a cookie management system (component / plugin) in Joomla 4 to manage cookies as required by GDPR and other privacy regulations.
====Improve Menu List view (Menu Items)====
*Add information of the selected menu item (like article title and id, category title and id) to the menu overview list and link it directly to the items. Categories receive a link to the category item as well as to the list of child items.
It should be taken care for performance, so e.g. information should be visible on request.
====Improve Menu-Module Assignment====
*Placing modules on a page (in the menu item form) is currently tedious. Ability to change the module menu assignment in the menu item.
====Improve Content====
*Remove the view featured and integrate it in the current article list. Take care of the featured ordering.
====Improve the incorporation of modules in the Articles-Edit-View====
*The function to insert modules in an article will be supplemented with the function to create and edit Modules in the Article-Edit-View.

===Knowledge Prerequisite===
*Must have: PHP, XML, CSS, JS
*Nice to have: Joomla MVC, Bootstrap 4

===Difficulty===

*Easy

===Mentors===
*[mailto:christiane.maier-stadtherr@community.joomla.org Christiane Maier-Stadtherr]
*[mailto:niels.braczek@community.joomla.org Niels Braczek]
*[mailto:j.weigel@karo3.de Jules Weigel]
*[mailto:luca.marzo@community.joomla.org Luca Marzo]
*[mailto:george.wilson@community.joomla.org George Wilson]

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

==Project IV: Media Manager==

===Project Description===
With Joomla 4, the Media Manager got a complete rewrite. The Media Manager team finished milestone 1 from the planned list.
In this project milestone 2 should be implemented.

As a student, here is the list of things expected from you as deliverable for the project:

*Allow the creation of different image sizes
*Extend the “add image” editor button to support srcset (with different sizes)
*Implement different filters for other media types than images (like PDF, video, audio, ...), so a user can edit, extract, cut etc.

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, VueJS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===

*Medium

===Mentors===
*[mailto:vivianamenzel@gmail.com Dr. Viviana Menzel]
*[mailto:mail.senns@gmail.com Sebastian Enns]
*[mailto:chris.keen@community.joomla.org Chris Keen]
*[mailto:glip@copyn.plus.com Geraint Edwards]
*[mailto:franci_perisa@hotmail.de Franciska Perisa]

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

{{tip|title=More Coming Soon!}}

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

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

GSoC 2021 Project Ideas

2021-01-21T12:44:55Z

Bembelimen: Update tinyMCE link

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

{{tip|title=The application for students is going to open soon!}}

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

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

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

==Project I: Frontend inline editing ==

===Project Description===
Implement a inline editing feature in the frontend for modules, articles, (and all other extensions, where it makes sense) (see: https://www.tiny.cloud/docs/demo/inline/ + https://www.tiny.cloud/blog/inline-editor/)

See https://github.com/joomla/joomla-cms/pull/30476

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===

*Medium

===Mentors===

*[mailto:roland.dalmulder@community.joomla.org Roland Dalmulder]
*[mailto:harald.leithner@community.joomla.org Harald Leithner]
*[mailto:peter.martin@community.joomla.org Peter Martin]
*[mailto:ciar4n@gmail.com Ciaran Walsh]

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

==Project II: Accessibility==

===Project Description===

Implement and improve several accessibility functions in Joomla!
Keyboard navigation

===Knowledge Prerequisite===
*Must have: PHP, mySQL, JS, CSS

===Difficulty===

*Easy

===Mentors===
*[mailto:anuragvns1999@gmail.com Anurag Kumar]
*[mailto:shivam.rajput@community.joomla.org Shivam Rajput]
*[mailto:patrick.jackson@community.joomla.org Patrick Jackson]
*[mailto:sdw@danicoenterprises.com Shirielle "SD" Williams]

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

==Project III: Feature enhancement ==

===Project Description===
====Cookies management====
*Create a cookie management system (component / plugin) in Joomla 4 to manage cookies as required by GDPR and other privacy regulations.
====Improve Menu List view (Menu Items)====
*Add information of the selected menu item (like article title and id, category title and id) to the menu overview list and link it directly to the items. Categories receive a link to the category item as well as to the list of child items.
It should be taken care for performance, so e.g. information should be visible on request.
====Improve Menu-Module Assignment====
*Placing modules on a page (in the menu item form) is currently tedious. Ability to change the module menu assignment in the menu item.
====Improve Content====
*Remove the view featured and integrate it in the current article list. Take care of the featured ordering.
====Improve the incorporation of modules in the Articles-Edit-View====
*The function to insert modules in an article will be supplemented with the function to create and edit Modules in the Article-Edit-View.

===Knowledge Prerequisite===
*Must have: PHP, XML, CSS, JS
*Nice to have: Joomla MVC, Bootstrap 4

===Difficulty===

*Easy

===Mentors===
*[mailto:christiane.maier-stadtherr@community.joomla.org Christiane Maier-Stadtherr]
*[mailto:niels.braczek@community.joomla.org Niels Braczek]
*[mailto:j.weigel@karo3.de Jules Weigel]
*[mailto:luca.marzo@community.joomla.org Luca ]
*[mailto:george.wilson@community.joomla.org George Wilson]

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

==Project IV: Media Manager==

===Project Description===
With Joomla 4, the Media Manager got a complete rewrite. The Media Manager team finished milestone 1 from the planned list.
In this project milestone 2 should be implemented.

As a student, here is the list of things expected from you as deliverable for the project:
*Implement a “database abstraction” for the files, so all files will be entries into the database and folders will be categories. A virtual layer above the (cloud) file system. This function should be opt-in (needs probably a htaccess) and still support the old way of handling files.
*Implement permissions for files and folders, based on the “database abstraction” layer
*Allow the creation of different image sizes
*Extend the “add image” editor button to support srcset (with different sizes)

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, VueJS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===

*Medium

===Mentors===
*[mailto:vivianamenzel@gmail.com Dr. Viviana Menzel]
*[mailto:mail.senns@gmail.com Sebastian Enns]
*[mailto:chris.keen@community.joomla.org Chris Keen]
*[mailto:glip@copyn.plus.com Geraint Edwards]
*[mailto:franci_perisa@hotmail.de Franciska Perisa]

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

{{tip|title=More Coming Soon!}}

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

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

GSoC 2021

2021-01-20T18:27:50Z

Bembelimen: Update admins

{{Top portal heading|color=white-bkgd|text-color=#333|title=Welcome to Joomla Google Summer of Code 2021 }}
[[Image:Gsoc2016.png|200px|center]]
<noinclude><languages /></noinclude>
<translate>

This page will aim to be a general informational page for students, mentors and others interested in Joomla's Google Summer of Code Program.


{{tip|title=Make sure to check out the [[GSoC 2021 Project Ideas|2021 project list]]}}

== CMS == 
Joomla developers are currently working on multiple projects: the Joomla CMS main 3.x Version and the upcoming new major version 4.0 (2021). Additionally there are many side projects related to testing, performance, and other things.


The Joomla CMS is the very popular and well known FOSS content management system powering currently around 3-4 % of the internet.

== What is GSoC? == 
Google Summer of Code is a program run by Google for college students interested in getting a stipend to contribute to Open Source Software. They will spend their summer with improving and writing new features for the project. [https://summerofcode.withgoogle.com/ Visit the Google Summer of Code website to learn more.]


*[https://volunteers.joomla.org/teams/google-summer-of-code-joomla-team Joomla GSoC Team on Joomla Volunteers Portal]

=== Project Timeline === 
The GSoC 2021 time line is available on the GSoC Site, we suggest you to go through it: [https://summerofcode.withgoogle.com/how-it-works]

=== Project Proposal === 
Please check the [[GSoC Student Application Template]] to understand what we are expecting from your proposal.


===Last years projects:===
*[https://summerofcode.withgoogle.com/archive/2019/organizations/6743345328553984/ Google Summer of Code for Joomla! 2019]
*[https://summerofcode.withgoogle.com/archive/2018/organizations/6484151049912320/ Google Summer of Code for Joomla! 2018]

== Information For Students == 
* [[GSoC 2021 Project Ideas|Joomla's project list]]
* [[GSoC Student Selection Criteria]]
* [[GSoC Student Application Template]]
* [https://groups.google.com/forum/?hl=en#!forum/jgsoc Joomla GSoC Mailing List]
* [https://groups.google.com/forum/#!forum/joomla-dev-cms General Joomla CMS Developer Mailing List]

==Information for Mentors== 
*Want to be a mentor? Please check the [[GSoC Mentor Guidelines]].
*[[GSoC Mentors Selection Criteria]]


==Any questions please do contact the Joomla GSoC Core Team 2021:==
*[mailto:philip.walton@community.joomla.org Philip Walton (Lead and Admin)]
*[mailto:shivam.rajput@community.joomla.org Shivam Rajput (Assistant)]
*[mailto:benjamin.trenkle@community.joomla.org Benjamin Trenkle]
*[mailto:llewellyn.van-der-merwe@community.joomla.org Llewellyn van der Merwe]

==Related Articles== 

===Google Summer of Code 2019=== 
*[https://community.joomla.org/gsoc-2019.html Joomla GSoC 2019 blog articles.]

===Google Summer of Code 2018=== 
*[https://community.joomla.org/gsoc-2018.html Joomla GSoC 2018 blog articles.]

===Google Summer of Code 2017=== 
*[https://community.joomla.org/gsoc-2017.html Joomla GSoC 2017 blog articles.]

===Google Summer of Code 2016=== 
*[https://magazine.joomla.org/issues/issue-sep-2016/item/3129-gsoc-every-story-has-an-ending-every-ending-is-a-new-beginning GSoC: Every Story Has An Ending. Every Ending Is A New Beginning.]
*[https://magazine.joomla.org/issues/issue-oct-2016/item/3143-the-brains-behind-joomla-gsoc The brains behind the Joomla! GSoC projects]
*[https://magazine.joomla.org/issues/issue-oct-2016/item/3152-gsoc-student-ruchiranga-wickramasinghe Interview with one of the 2016 students Ruchiranga Wickramasinghe]
*[http://magazine.joomla.org/issues/issue-feb-2016/item/2964-joomla-s-google-summer-of-code-gsoc-is-proud-to-announce-team-lead-puneet-kala Joomla's Google Summer of Code (GSoC) is Proud to Announce Team Lead: Puneet Kala]
*[http://community.joomla.org/blogs/community/1894-joomla-has-been-selected-as-a-google-summer-of-code-2016-mentor-organization.html Joomla! has been selected as a Google Summer of Code 2016 mentor organization]
*[https://community.joomla.org/gsoc-2016/3070-joomla-google-mentor-summit-gsoc16.html Joomla! is going to the 2016 Google Summer of Code Mentor Summit]
*[https://magazine.joomla.org/all-issues/tags/google-summer-of-code Articles on Joomla Community Magazine]
</translate>

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

Joomla CodeSniffer

2020-08-26T00:08:23Z

Bembelimen: Update to the latest tag of Joomla! code sniffer

<noinclude><languages /></noinclude>

<translate>
== A Nose For Joomla == 
</translate>
<translate> This is a custom coding standard for the PHP CodeSniffer that attempts to codify and enforce the Joomla coding standards. This article covers how to set the automatic code style checker. It consists of three steps:</translate>
<translate>
# Install PHP CodeSniffer (phpcs).
# Clone the Joomla Code Style (for use with for phpcs).
# Configure your IDE to work with PHP CodeSniffer and Joomla Code Style.</translate>

[[File:CodeSnifferInAction.jpg|center|thumb|300px|PHP Code Sniffer in action]]

<translate>
==Why?== 
</translate>
<translate> *Coherent and consistent coding practice makes the files look more professional. Conflicting styles in the same project (or worse, the same file) not only look sloppy, they encourage further sloppiness.</translate>
<translate> *When all code complies with the same standard, bad code is easier for everyone to spot.</translate>
<translate> *It makes it easier for someone new to a particular file in the project to find and fix errors or extend functionality.</translate>
<translate> *If there is no consistent standard maintained, sometimes developers will reformat the code to suit themselves. This causes a wide range of changes in the code repository. If there is a later problem, a significant change could be lost in the chaff produced by a diff.</translate>

<translate>
==1. Installation of PHP Code Sniffer (phpcs)== 
</translate>
<translate>
===Composer=== 
</translate>
<translate> PHP Code Sniffer is available via Composer. It can be installed system-wide with the following command:</translate><br />
<tt>composer global require squizlabs/php_codesniffer "^3.5"</tt>
<translate>

On '''Linux''' PHP Code Sniffer (phpcs) will be installed under your user folder:</translate>
* <translate> Symbolic Link:</translate> <tt>~/.composer/vendor/bin/phpcs</tt>
* <translate> The file:</translate> <tt>~/.composer/vendor/squizlabs/php_codesniffer/scripts/phpcs</tt>
<translate> To create that symbolic link, use on the command line: <code></translate>
$ sudo ln -s ~/.config/composer/vendor/squizlabs/php_codesniffer/scripts /usr/bin/phpcs
</code>

<translate> or (for example OpenSuse)</translate>
* <translate> Symbolic Link:</translate> <tt>~/.config/composer/vendor/bin/phpcs</tt>
* <translate> The file:</translate> <tt>~/.config/composer/vendor/squizlabs/php_codesniffer/scripts/phpcs</tt>

<translate> On '''Windows''' PHP Code Sniffer (phpcs) will be installed under your user folder:</translate>
* <translate> Symbolic Link:</translate> <tt>c:\Users\Username\AppData\Roaming\Composer\vendor\bin\phpcs</tt>
* <translate> The file:</translate> <tt>c:\Users\Username\AppData\Roaming\Composer\vendor\squizlabs\php_codesniffer\scripts\phpcs</tt>

<translate>

=== Add composer bin directory to your $PATH === 
</translate>
<translate>

In order to execute PHP Code sniffer from anywhere on Linux or Mac command line you have to add <tt>.composer/vendor/bin</tt> to your $PATH variable.</translate>
<translate>

To do this persistent edit your shells start file, like your .profile or .bash_profile file depending which shell you are using (echo $SHELL shows you which one you are using).</translate>

<translate> Add the following line to the file:</translate>
<tt>export PATH=$PATH:~/.composer/vendor/bin</tt>

<translate> Alternatively you can also create a symbolic link in the bin folder:</translate>
<tt>ln -s ~/.composer/vendor/bin/phpcs /usr/local/bin/phpcs</tt>

<translate>

==2. Install Joomla Coding Standards== 
</translate>
<translate> In order to have PHP Code Sniffer (phpcs) sniffing your Joomla projects for the right code style, you have to install the Joomla Coding Standards.</translate>

<translate> Using composer we can execute:</translate>
<tt>composer global require joomla/coding-standards "~3.0@alpha"</tt>

<translate> Notice that it says <tt>@alpha</tt>, that is because the coding standard is still in alpha state and we need to allow the installation of alpha status code. If we do not include the @alpha the coding standards will not install and throw this error.</translate>

<pre>
Your requirements could not be resolved to an installable set of packages.

Problem 1
- The requested package joomla/coding-standards ~3.0 is satisfiable by joomla/coding-standards[3.0.0-alpha, 3.0.0-alpha2, 3.x-dev] but these conflict with your requirements or minimum-stability.
</pre>

<translate> Once the installation is done the coding standard will be installed in the global composer folder. The location of this folder depends on your operating system. Some popular locations are:</translate>

'''Mac / Linux'''
~/.composer/vendor/joomla/coding-standards/

~/.config/composer/vendor/joomla/coding-standards/
'''Windows'''
c:\Users\Username\AppData\Roaming\Composer\vendor\joomla\coding-standards\
<translate> This is using Composer on Windows.</translate>

<translate> If you can't find it in any of the above folders, note that the folder you are looking for ends with '''\joomla\coding-standards\'''</translate>
<translate>

Finally we need to tell Code Sniffer that the Joomla coding standards exist.</translate>

<translate>
'''Install Joomla Coding Standards'''
# Check if certain paths are already set by running <tt>phpcs --config-show</tt>
# You can get an answer that looks like this: <tt>installed_paths: /path/to/installation</tt>
# In step 2, if you see the '''installed_paths''' you need to copy that
# Set the Joomla Coding Standards path in phpcs by executing <tt>phpcs --config-set installed_paths /Users/user/.composer/vendor/joomla/coding-standards</tt>. If you copied any paths in step 2, include them here as well by separating them with a comma. The command looks like <tt>phpcs --config-set installed_paths [/to/path1],[/to/path2],[/Users/user/.composer/vendor/joomla/coding-standards]</tt>
# Verify the path is set correctly by running <tt>phpcs --config-show</tt>
# Verify that phpcs can see the Joomla codestyle by running <tt>phpcs -i</tt>
# The output should look like this: <tt>The installed coding standards are MySource, PEAR, PHPCS, PSR1, PSR2, Squiz, Zend and Joomla</tt></translate>
<translate>

== Usage == 
</translate>
<translate> You invoke the custom standard by</translate>
<tt>phpcs --standard=Joomla file/to/sniff</tt>

<translate> To test a platform file using the provided platform coding standards, use</translate>
<tt>phpcs --standard=build/phpcs/Joomla path/to/file/or/folder</tt>

<translate> Further documentation on the use of phpcs can be found at: [http://pear.php.net/package/PHP_CodeSniffer/docs]</translate>

<translate>
==3. IDE Integration== 
</translate>
<translate> Everybody loves the console. It is, with no doubt, the most effective way to do whatever you need to do. Sometimes even Linux gurus need a little bit of comfort.</translate>

<translate> Fortunately there is a plug-in available for PhpStorm, Eclipse and Netbeans that integrates the CodeSniffer into your favourite IDE, so any coding standard violations are shown like "normal" errors.</translate>

<translate>
=== PhpStorm === 
</translate>
<translate> Code Sniffer is supported out of the box in PhpStorm. Go to Settings and under Editor {{rarr}} Inspections you will see the list of sniffers you have installed.</translate>
<translate>
==== Set Path to Code Sniffer ==== 
</translate>
<translate>
# Open Settings (CTRL-ALT-S / CMD-,)
# Go to Languages & Frameworks
# Click on PHP
# Click on Quality Tools
# Click on PHP cs fixer dropdown arrow
# The configuration is set to Local by default
# Click on the 3 dots behind it to open the configuration screen
# The first option is the PHP Code Sniffer (phpcs) path
# Click on the 3 dots behind the path to select the location of the phpcs file. See above on where phpcs may be installed on your site
# Click on Validate to make sure the path is correct and phpcs is working
# Click OK</translate>

<translate>
===== Activating the Joomla Code Style ===== 
</translate>
<translate>
# Open Settings (CTRL-ALT-S / CMD-,)
# Go to Editor
# Click on Inspections
# In the list, go to PHP
# Click on PHP Code Sniffer Validation
# Click on the check box behind it to activate it
# Click the Reload button (2 arrows) to force a reload of rules from disk
# Joomla should now be available in the list. See following image:{{-}}[[File:PhpStorm8CodeSniffer.png|PHPStorm CodeSniffer|500px]]
# Click OK</translate>

<translate>

==== PHP PSR-0, PSR-1 and PSR-2 ==== 
</translate>
* https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md
* https://github.com/pmjones/fig-standards/blob/psr-1-style-guide/proposed/PSR-1-basic.md
* https://github.com/pmjones/fig-standards/blob/psr-1-style-guide/proposed/PSR-2-advanced.md

<translate>
===== Using PHP PSR-1 and PSR-2 Sniff ===== 
</translate>
<translate> A CodeSniffer sniff to check against the PSR-x Coding Standard can be used as well. In that case you can select a different standard than Joomla.</translate>
<translate>
===== Using Joomla Code style ===== 
</translate>
<translate> It's nice to be able to check that the standards are respected. It's even nicer if PhpStorm helps you format properly too as you are coding.</translate>
<translate>
To use the Joomla code style in PhpStorm
# Open Settings (CTRL-ALT-S / CMD-,)
# Go to Editor
# Click on Code Style
# Select Joomla from the Scheme select box</translate>

<translate>
==== PhpStorm / Alternative Method ==== 
</translate>
<translate> '''NOTE''': This method is '''outdated''', but it might be useful if you are looking for a different integration. It also demonstrates the use of external tools in PhpStorm - so it ''shouldn't be deleted''.</translate>

<translate> The Code Sniffer can also be integrated easily as an external tool. PhpStorm will display the output in the console, including click-able links containing line and column numbers to the files that contain errors.</translate>

<translate>
* Click on "Settings" and search for "External tools"
* Click "Add..."
* Choose a "Name", "Group" and "Description".
* Click "Output Filters"
** Click "Add...", Choose a name and enter under "Regular expression to match output" the value: <tt>$FILE_PATH$:$LINE$:$COLUMN$</tt>
* "Program": Search for the phpcs executable on your system. You have to set the path to the ''phpcs.bat'' from the installed PHP_CodeSniffer PEAR package
** For Unix based systems, the path is something like /usr/bin/phpcs
** In XAMPP (windows), you can find the file in the PHP root folder (e.g. C:\xampp\php\phpcs.bat)
* "Parameters":
** <tt>--standard=<path/to/joomla-platform>/build/phpcs/Joomla</tt> The path to the Joomla! coding standards.
** <tt>--report=emacs</tt> The will generate a simple list containing links to the error files
** Optionally you may want to specify <tt>-p</tt> for "progress" or <tt>-n</tt> for "errors only".
** The last parameter has to be <tt>$FilePath$</tt> specifying the file or folder you want to sniff.</translate>

<translate> A typical "Parameters" line on a Linux system might look like this:</translate>
<pre>-np --standard=/home/elkuku/libs/joomla/build/phpcs/Joomla --report=emacs $FilePath$</pre>

<translate> You may now right click any file or folder and choose the sniffer from the context menu or add a new tool bar button with a nice Joomla! logo</translate> [[File:icon-16-joomla.png]].

<translate>
=== Netbeans === 
</translate>
<translate> Netbeans has the sniffer functionality integrated into the core system.</translate>

<translate>
# Start your Netbeans IDE
# Open Tools => Options => PHP => Code Analysis => Code Sniffer
# You have to set the path to ''phpcs.bat'' from the installed PHP_CodeSniffer PEAR package
#* For Unix based systems the path is something like /usr/bin/phpcs
#* In XAMPP (windows) you can find the file in the PHP root folder (e.g. C:\xampp\php\phpcs.bat)
# As "Default Standard," choose "Joomla" to use the Joomla! standard
# Now you can click ''OK'' to start sniffing
# Open from the top menu Source => Inspect...
# Enjoy</translate>

<translate>
=== Eclipse === 
</translate>
[[Image:eclipse_pti.png|left|thumb|200px|1) Eclipse PTI]]
{{-}}
<translate>
Installation is a breeze and follows the usual pattern:
# <tt>Help => Install New Software...</tt>
# <tt>Work with:</tt> Fill in one of the update site URLs found here: http://www.phpsrc.org/eclipse/pti/
# Select the desired tools
# Restart Eclipse.</translate>

[[Image:eclipse_pti_settings.png|right|thumb|150px|2) <translate> Eclipse PTI settings</translate>]]
<translate> You are now able to sniff for code violations against common standards like PEAR or Zend etc.</translate>

<translate> To sniff against your own standards, specify their location and activate them (see screen shot 2)</translate>
<translate>
# <tt>Window => Preferences</tt>
# <tt>PHP Tools => PHP CodeSniffer</tt></translate>

<translate> Happy sniffing.</translate>

<translate>

=== Geany === 
</translate>
<translate>
* Open a PHP file. (Otherwise the build menu is not accessible.) See this [http://static.xscreenshot.com/2016/07/13/08/screen_6bc0692cf995702a1e379b39643d0c2d Screenshot]
* On the top menu, select Build->Set Build Commands.
* Select the second field and name it as you wish. Enter this code in the Command: <code>phpcs --standard=Joomla "%f" | sed -e 's/^/%f |/' | egrep 'WARNING|ERROR'</code>
* Enter this code in the Error Regular Expression field: <code>(.+) [|]\s+([0-9]+)</code> See this [http://view.xscreenshot.com/ef00820cf7c017ce659c8e9f0b02d3ae Screenshot]
* Select OK.
* If the Message Window is not open, display it by selecting it in the top View menu.
* When viewing any PHP file, press F9 to see the errors found. [http://view.xscreenshot.com/8704b9fd1bda3f841364a0ffa28a54ae Screenshot]</translate>

<translate>

=== Atom === 
</translate>
<translate>

* Install phpcs and the Joomla standards as described above.
* In '''Atom > Preferences > Install''' install '''linter-phpcs''' and all its requirements.
* In '''Atom > Preferences > Packages > linter-phpcs > Settings''' adjust
** '''Executable Path''' to the path of your phpcs
** '''Code Standard Or Config File''': Joomla
** '''Tab Width''': 4
</translate>

<translate>
=== References === 
</translate>
* https://github.com/joomla/coding-standards - <translate> Joomla! Coding Standards</translate>
* http://www.phpsrc.org/ <translate> PTI - PHP tools integration for Eclipse</translate>
* http://sourceforge.net/projects/phpmdnb/ <translate> Netbeans plugin</translate>
* http://hakre.wordpress.com/2010/03/06/php-code-sniffer-eclipse-and-wordpress/ - <translate> Excellent article. Just change "Wordpress" for "Joomla!" ;)</translate>

<noinclude>
[[Category:Development{{#translation:}}]]
[[Category:Bug Squad{{#translation:}}]]
[[Category:IDE (Integrated development environment){{#translation:}}]]
</noinclude>

Joomla CodeSniffer

2020-08-26T00:07:00Z

Bembelimen: Update to the latest tag of Joomla! code sniffer

<noinclude><languages /></noinclude>

<translate>
== A Nose For Joomla == 
</translate>
<translate> This is a custom coding standard for the PHP CodeSniffer that attempts to codify and enforce the Joomla coding standards. This article covers how to set the automatic code style checker. It consists of three steps:</translate>
<translate>
# Install PHP CodeSniffer (phpcs).
# Clone the Joomla Code Style (for use with for phpcs).
# Configure your IDE to work with PHP CodeSniffer and Joomla Code Style.</translate>

[[File:CodeSnifferInAction.jpg|center|thumb|300px|PHP Code Sniffer in action]]

<translate>
==Why?== 
</translate>
<translate> *Coherent and consistent coding practice makes the files look more professional. Conflicting styles in the same project (or worse, the same file) not only look sloppy, they encourage further sloppiness.</translate>
<translate> *When all code complies with the same standard, bad code is easier for everyone to spot.</translate>
<translate> *It makes it easier for someone new to a particular file in the project to find and fix errors or extend functionality.</translate>
<translate> *If there is no consistent standard maintained, sometimes developers will reformat the code to suit themselves. This causes a wide range of changes in the code repository. If there is a later problem, a significant change could be lost in the chaff produced by a diff.</translate>

<translate>
==1. Installation of PHP Code Sniffer (phpcs)== 
</translate>
<translate>
===Composer=== 
</translate>
<translate> PHP Code Sniffer is available via Composer. It can be installed system-wide with the following command:</translate><br />
<tt>composer global require squizlabs/php_codesniffer "^3.5"</tt>
<translate>

On '''Linux''' PHP Code Sniffer (phpcs) will be installed under your user folder:</translate>
* <translate> Symbolic Link:</translate> <tt>~/.composer/vendor/bin/phpcs</tt>
* <translate> The file:</translate> <tt>~/.composer/vendor/squizlabs/php_codesniffer/scripts/phpcs</tt>
<translate> To create that symbolic link, use on the command line: <code></translate>
$ sudo ln -s ~/.config/composer/vendor/squizlabs/php_codesniffer/scripts /usr/bin/phpcs
</code>

<translate> or (for example OpenSuse)</translate>
* <translate> Symbolic Link:</translate> <tt>~/.config/composer/vendor/bin/phpcs</tt>
* <translate> The file:</translate> <tt>~/.config/composer/vendor/squizlabs/php_codesniffer/scripts/phpcs</tt>

<translate> On '''Windows''' PHP Code Sniffer (phpcs) will be installed under your user folder:</translate>
* <translate> Symbolic Link:</translate> <tt>c:\Users\Username\AppData\Roaming\Composer\vendor\bin\phpcs</tt>
* <translate> The file:</translate> <tt>c:\Users\Username\AppData\Roaming\Composer\vendor\squizlabs\php_codesniffer\scripts\phpcs</tt>

<translate>

=== Add composer bin directory to your $PATH === 
</translate>
<translate>

In order to execute PHP Code sniffer from anywhere on Linux or Mac command line you have to add <tt>.composer/vendor/bin</tt> to your $PATH variable.</translate>
<translate>

To do this persistent edit your shells start file, like your .profile or .bash_profile file depending which shell you are using (echo $SHELL shows you which one you are using).</translate>

<translate> Add the following line to the file:</translate>
<tt>export PATH=$PATH:~/.composer/vendor/bin</tt>

<translate> Alternatively you can also create a symbolic link in the bin folder:</translate>
<tt>ln -s ~/.composer/vendor/bin/phpcs /usr/local/bin/phpcs</tt>

<translate>

==2. Install Joomla Coding Standards== 
</translate>
<translate> In order to have PHP Code Sniffer (phpcs) sniffing your Joomla projects for the right code style, you have to install the Joomla Coding Standards.</translate>

<translate> Using composer we can execute:</translate>
<tt>composer global require joomla/coding-standards "~2.0@alpha"</tt>

<translate> Notice that it says <tt>@alpha</tt>, that is because the coding standard is still in alpha state and we need to allow the installation of alpha status code. If we do not include the @alpha the coding standards will not install and throw this error.</translate>

<pre>
Your requirements could not be resolved to an installable set of packages.

Problem 1
- The requested package joomla/coding-standards ~2.0 is satisfiable by joomla/coding-standards[2.0.0-alpha, 2.0.0-alpha2, 2.x-dev] but these conflict with your requirements or minimum-stability.
</pre>

<translate> Once the installation is done the coding standard will be installed in the global composer folder. The location of this folder depends on your operating system. Some popular locations are:</translate>

'''Mac / Linux'''
~/.composer/vendor/joomla/coding-standards/

~/.config/composer/vendor/joomla/coding-standards/
'''Windows'''
c:\Users\Username\AppData\Roaming\Composer\vendor\joomla\coding-standards\
<translate> This is using Composer on Windows.</translate>

<translate> If you can't find it in any of the above folders, note that the folder you are looking for ends with '''\joomla\coding-standards\'''</translate>
<translate>

Finally we need to tell Code Sniffer that the Joomla coding standards exist.</translate>

<translate>
'''Install Joomla Coding Standards'''
# Check if certain paths are already set by running <tt>phpcs --config-show</tt>
# You can get an answer that looks like this: <tt>installed_paths: /path/to/installation</tt>
# In step 2, if you see the '''installed_paths''' you need to copy that
# Set the Joomla Coding Standards path in phpcs by executing <tt>phpcs --config-set installed_paths /Users/user/.composer/vendor/joomla/coding-standards</tt>. If you copied any paths in step 2, include them here as well by separating them with a comma. The command looks like <tt>phpcs --config-set installed_paths [/to/path1],[/to/path2],[/Users/user/.composer/vendor/joomla/coding-standards]</tt>
# Verify the path is set correctly by running <tt>phpcs --config-show</tt>
# Verify that phpcs can see the Joomla codestyle by running <tt>phpcs -i</tt>
# The output should look like this: <tt>The installed coding standards are MySource, PEAR, PHPCS, PSR1, PSR2, Squiz, Zend and Joomla</tt></translate>
<translate>

== Usage == 
</translate>
<translate> You invoke the custom standard by</translate>
<tt>phpcs --standard=Joomla file/to/sniff</tt>

<translate> To test a platform file using the provided platform coding standards, use</translate>
<tt>phpcs --standard=build/phpcs/Joomla path/to/file/or/folder</tt>

<translate> Further documentation on the use of phpcs can be found at: [http://pear.php.net/package/PHP_CodeSniffer/docs]</translate>

<translate>
==3. IDE Integration== 
</translate>
<translate> Everybody loves the console. It is, with no doubt, the most effective way to do whatever you need to do. Sometimes even Linux gurus need a little bit of comfort.</translate>

<translate> Fortunately there is a plug-in available for PhpStorm, Eclipse and Netbeans that integrates the CodeSniffer into your favourite IDE, so any coding standard violations are shown like "normal" errors.</translate>

<translate>
=== PhpStorm === 
</translate>
<translate> Code Sniffer is supported out of the box in PhpStorm. Go to Settings and under Editor {{rarr}} Inspections you will see the list of sniffers you have installed.</translate>
<translate>
==== Set Path to Code Sniffer ==== 
</translate>
<translate>
# Open Settings (CTRL-ALT-S / CMD-,)
# Go to Languages & Frameworks
# Click on PHP
# Click on Quality Tools
# Click on PHP cs fixer dropdown arrow
# The configuration is set to Local by default
# Click on the 3 dots behind it to open the configuration screen
# The first option is the PHP Code Sniffer (phpcs) path
# Click on the 3 dots behind the path to select the location of the phpcs file. See above on where phpcs may be installed on your site
# Click on Validate to make sure the path is correct and phpcs is working
# Click OK</translate>

<translate>
===== Activating the Joomla Code Style ===== 
</translate>
<translate>
# Open Settings (CTRL-ALT-S / CMD-,)
# Go to Editor
# Click on Inspections
# In the list, go to PHP
# Click on PHP Code Sniffer Validation
# Click on the check box behind it to activate it
# Click the Reload button (2 arrows) to force a reload of rules from disk
# Joomla should now be available in the list. See following image:{{-}}[[File:PhpStorm8CodeSniffer.png|PHPStorm CodeSniffer|500px]]
# Click OK</translate>

<translate>

==== PHP PSR-0, PSR-1 and PSR-2 ==== 
</translate>
* https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md
* https://github.com/pmjones/fig-standards/blob/psr-1-style-guide/proposed/PSR-1-basic.md
* https://github.com/pmjones/fig-standards/blob/psr-1-style-guide/proposed/PSR-2-advanced.md

<translate>
===== Using PHP PSR-1 and PSR-2 Sniff ===== 
</translate>
<translate> A CodeSniffer sniff to check against the PSR-x Coding Standard can be used as well. In that case you can select a different standard than Joomla.</translate>
<translate>
===== Using Joomla Code style ===== 
</translate>
<translate> It's nice to be able to check that the standards are respected. It's even nicer if PhpStorm helps you format properly too as you are coding.</translate>
<translate>
To use the Joomla code style in PhpStorm
# Open Settings (CTRL-ALT-S / CMD-,)
# Go to Editor
# Click on Code Style
# Select Joomla from the Scheme select box</translate>

<translate>
==== PhpStorm / Alternative Method ==== 
</translate>
<translate> '''NOTE''': This method is '''outdated''', but it might be useful if you are looking for a different integration. It also demonstrates the use of external tools in PhpStorm - so it ''shouldn't be deleted''.</translate>

<translate> The Code Sniffer can also be integrated easily as an external tool. PhpStorm will display the output in the console, including click-able links containing line and column numbers to the files that contain errors.</translate>

<translate>
* Click on "Settings" and search for "External tools"
* Click "Add..."
* Choose a "Name", "Group" and "Description".
* Click "Output Filters"
** Click "Add...", Choose a name and enter under "Regular expression to match output" the value: <tt>$FILE_PATH$:$LINE$:$COLUMN$</tt>
* "Program": Search for the phpcs executable on your system. You have to set the path to the ''phpcs.bat'' from the installed PHP_CodeSniffer PEAR package
** For Unix based systems, the path is something like /usr/bin/phpcs
** In XAMPP (windows), you can find the file in the PHP root folder (e.g. C:\xampp\php\phpcs.bat)
* "Parameters":
** <tt>--standard=<path/to/joomla-platform>/build/phpcs/Joomla</tt> The path to the Joomla! coding standards.
** <tt>--report=emacs</tt> The will generate a simple list containing links to the error files
** Optionally you may want to specify <tt>-p</tt> for "progress" or <tt>-n</tt> for "errors only".
** The last parameter has to be <tt>$FilePath$</tt> specifying the file or folder you want to sniff.</translate>

<translate> A typical "Parameters" line on a Linux system might look like this:</translate>
<pre>-np --standard=/home/elkuku/libs/joomla/build/phpcs/Joomla --report=emacs $FilePath$</pre>

<translate> You may now right click any file or folder and choose the sniffer from the context menu or add a new tool bar button with a nice Joomla! logo</translate> [[File:icon-16-joomla.png]].

<translate>
=== Netbeans === 
</translate>
<translate> Netbeans has the sniffer functionality integrated into the core system.</translate>

<translate>
# Start your Netbeans IDE
# Open Tools => Options => PHP => Code Analysis => Code Sniffer
# You have to set the path to ''phpcs.bat'' from the installed PHP_CodeSniffer PEAR package
#* For Unix based systems the path is something like /usr/bin/phpcs
#* In XAMPP (windows) you can find the file in the PHP root folder (e.g. C:\xampp\php\phpcs.bat)
# As "Default Standard," choose "Joomla" to use the Joomla! standard
# Now you can click ''OK'' to start sniffing
# Open from the top menu Source => Inspect...
# Enjoy</translate>

<translate>
=== Eclipse === 
</translate>
[[Image:eclipse_pti.png|left|thumb|200px|1) Eclipse PTI]]
{{-}}
<translate>
Installation is a breeze and follows the usual pattern:
# <tt>Help => Install New Software...</tt>
# <tt>Work with:</tt> Fill in one of the update site URLs found here: http://www.phpsrc.org/eclipse/pti/
# Select the desired tools
# Restart Eclipse.</translate>

[[Image:eclipse_pti_settings.png|right|thumb|150px|2) <translate> Eclipse PTI settings</translate>]]
<translate> You are now able to sniff for code violations against common standards like PEAR or Zend etc.</translate>

<translate> To sniff against your own standards, specify their location and activate them (see screen shot 2)</translate>
<translate>
# <tt>Window => Preferences</tt>
# <tt>PHP Tools => PHP CodeSniffer</tt></translate>

<translate> Happy sniffing.</translate>

<translate>

=== Geany === 
</translate>
<translate>
* Open a PHP file. (Otherwise the build menu is not accessible.) See this [http://static.xscreenshot.com/2016/07/13/08/screen_6bc0692cf995702a1e379b39643d0c2d Screenshot]
* On the top menu, select Build->Set Build Commands.
* Select the second field and name it as you wish. Enter this code in the Command: <code>phpcs --standard=Joomla "%f" | sed -e 's/^/%f |/' | egrep 'WARNING|ERROR'</code>
* Enter this code in the Error Regular Expression field: <code>(.+) [|]\s+([0-9]+)</code> See this [http://view.xscreenshot.com/ef00820cf7c017ce659c8e9f0b02d3ae Screenshot]
* Select OK.
* If the Message Window is not open, display it by selecting it in the top View menu.
* When viewing any PHP file, press F9 to see the errors found. [http://view.xscreenshot.com/8704b9fd1bda3f841364a0ffa28a54ae Screenshot]</translate>

<translate>

=== Atom === 
</translate>
<translate>

* Install phpcs and the Joomla standards as described above.
* In '''Atom > Preferences > Install''' install '''linter-phpcs''' and all its requirements.
* In '''Atom > Preferences > Packages > linter-phpcs > Settings''' adjust
** '''Executable Path''' to the path of your phpcs
** '''Code Standard Or Config File''': Joomla
** '''Tab Width''': 4
</translate>

<translate>
=== References === 
</translate>
* https://github.com/joomla/coding-standards - <translate> Joomla! Coding Standards</translate>
* http://www.phpsrc.org/ <translate> PTI - PHP tools integration for Eclipse</translate>
* http://sourceforge.net/projects/phpmdnb/ <translate> Netbeans plugin</translate>
* http://hakre.wordpress.com/2010/03/06/php-code-sniffer-eclipse-and-wordpress/ - <translate> Excellent article. Just change "Wordpress" for "Joomla!" ;)</translate>

<noinclude>
[[Category:Development{{#translation:}}]]
[[Category:Bug Squad{{#translation:}}]]
[[Category:IDE (Integrated development environment){{#translation:}}]]
</noinclude>

Publishing Workflow

2020-06-11T07:23:45Z

Bembelimen: Add redirect so links are not broken

#REDIRECT [[J4.x:Workflow]]

GSoC 2020 Project Ideas

2020-02-15T14:35:00Z

Bembelimen: Update email address

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

{{tip|title=The application for students is going to open soon!}}

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

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

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

==Project I: Layout Builder ==

===Project Description===
The main focus of the Layout Builder lies on a Drag & Drop editor, which makes it possible to create a full Joomla! frontend template with custom defined positions without writing any HTML code. Users can use predefined elements - container, grid, column, module position as well as custom elements. 3rd party developers are able to add their own elements via plugins. https://docs.joomla.org/J4.x:Page_Builder

This project is a continuation of the GSoC Page Builder project 2019 (https://github.com/joomla-projects/gsoc19_page-builder ). The idea is to extend the basic implementation to a level where it’s possible to reproduce the Cassiopeia template (current frontend template) using the Layout Builder. The project is now called 'Layout Builder' because that is what it does: users can build a template layout with it.

As a student, here is the list of things expected from you as a deliverable for the project:

*Improve the function of the Layout Builder and add missing features like parameters, elements, … so at the end of the project it should be possible to create a structure which looks and acts like the current Cassiopeia template (if another template is the current default one, then this should be the reference)
*Iron out any existing issues to make the Layout Builder release ready.

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, VueJS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===
*Hard

===Mentors===
*[mailto:vivianamenzel@gmail.com Dr. Viviana Menzel] - Main Mentor
*[mailto:anuragvns1999@gmail.com Anurag Kumar]
*[mailto:nitishbahl24@gmail.com Nitish Bahl]
*[mailto:roland.dalmulder@community.joomla.org Roland Dalmulder]
*[mailto:r.kreijveld@dsd.nu René Kreijveld]
[[Image:Gsoc2016.png|30px|center]]

==Project II: Auto Updater==

===Project Description===

An Auto-Updater would decrease the number of hacked pages significantly. With this project Joomla! 4 should be extended by an auto updater. In order to prevent that such an auto-update feature can be weaponized, strong cryptographic signatures have to be used for signing and verifying available updates. A centrally hosted service should trigger site updates on all connected Joomla sites.

As a student, here is the list of things expected from you as a deliverable for the project:

*Extend the current Joomla! Updater with a secure auto-update function; Available updates need to be downloaded and their integrity has to be verified using cryptographic signatures
*Implement a CLI tool to sign Joomla updates
*Implement a centralized service triggering sites that require updates

===Knowledge Prerequisite===
*Must have: Knowledge of PHP

===Difficulty===
*Medium

===Mentors===
*[mailto:david.jardin@community.joomla.org David Jardin] - Main Mentor
*[mailto:niels.braczek@community.joomla.org Niels Braczek]
*[mailto:tobias.zulauf@community.joomla.org Tobias Zulauf]
*[mailto:harald.leithner@community.joomla.org Harald Leithner]

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

==Project III: Feature enhancement ==

===Project Description===
====Cookies management====
Create a cookie management system (component / plugin) in Joomla 4 to manage cookies as required by GDPR and other privacy regulations.
====Improve Menu List view (Menu Items)====
Add information of the selected menu item (like article title and id, category title and id) to the menu overview list and link it directly to the items. Categories receive a link to the category item as well as to the list of child items.
It should be taken care for performance, so e.g. information should be visible on request.
====Improve Menu-Module Assignment====
Placing modules on a page (in the menu item form) is currently tedious. Ability to change the module menu assignment in the menu item.
====Improve Content====
Remove the view featured and integrate it in the current article list. Take care of the featured ordering.
====Improve the incorporation of modules in the Articles-Edit-View====
The function to insert modules in an article will be supplemented with the function to create and edit Modules in the Article-Edit-View.

===Knowledge Prerequisite===
*Must have: PHP, XML, CSS, JS
*Nice to have: Joomla MVC, Bootstrap 4

===Difficulty===
*Medium

===Mentors===
*[mailto:christiane.maier-stadtherr@community.joomla.org Christiane Maier-Stadtherr] - Main Mentor
*[mailto:j.weigel@karo3.de Jules Weigel]
*[mailto:luca.marzo@community.joomla.org Luca Marzo]
*[mailto:achilleas.papageorgiou@community.joomla.org Achilleas Papageorgiou]

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

==Project IV: Performance Improvements==

===Project Description===
Joomla! has several testing procedures until it gets released, but currently it lacks in terms of high performance tests with thousands of contents.

This project should close this gap by creating tools which support this kind of tests.

As a student, here is the list of things expected from you as deliverable for the project:
*Create a generic component which allows (via adapters?) to generate content for all extensions (core and 3rd party) in Joomla!
*Create different “adapter” to support com_content, com_menu, com_categories, com_tags
*Integrate the Joomla! 4 CLI function into the component to execute the functionality via the CLI.
*Check the performance of each component where an adapter exists and improve the database queries (as PR against the core)

===Knowledge Prerequisite===
*Must have: PHP, SQL
*Nice to have: Joomla MVC, Bootstrap 4

===Difficulty===
*Easy

===Mentors===
*[mailto:nicolagalgano@yahoo.it Nicola Galgano] - Main Mentor
*[mailto:peter.martin@community.joomla.org Peter Martin]
*[mailto:astrid.guenther@community.joomla.org Astrid Günther]
*[mailto:shivamdiehard@gmail.com Shivam Rajput]

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

==Project V: Media Manager==

===Project Description===
With Joomla 4, the Media Manager got a complete rewrite. The Media Manager team finished milestone 1 from the planned list.
In this project milestone 2 should be implemented.

As a student, here is the list of things expected from you as deliverable for the project:
*Implement a “database abstraction” for the files, so all files will be entries into the database and folders will be categories. A virtual layer above the (cloud) file system. This function should be opt-in (needs probably a htaccess) and still support the old way of handling files.
*Implement permissions for files and folders, based on the “database abstraction” layer
*Allow the creation of different image sizes
*Extend the “add image” editor button to support srcset (with different sizes)

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, VueJS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===
*Moderate

===Mentors===
*[mailto:benjamin.trenkle@community.joomla.org Benjamin Trenkle]
*[mailto:mail.senns@gmail.com Sebastian Enns]
*[mailto:mathur.geetanshu887@gmail.com Geetanshu Mathur]

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

{{tip|title=More Coming Soon!}}

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

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

GSoC 2020 Project Ideas

2020-01-30T14:52:15Z

Bembelimen: Update mentor list for enhancement project

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

{{tip|title=The application for students is going to open soon!}}

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

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

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

==Project I: Page Builder ==

===Project Description===
The main focus of the PageBuilder lies on a Drag & Drop editor, which makes it possible to create a full Joomla! frontend template with custom defined positions without writing any HTML code. Users can use predefined elements - container, grid, column, module position as well as custom elements. 3rd party developers are able to add their own elements via plugins. https://docs.joomla.org/J4.x:Page_Builder

This project is a continuation of the GSoC Page Builder project 2019 (https://github.com/joomla-projects/gsoc19_page-builder ). The idea is to extend the basic implementation to a level where it’s possible to reproduce the Cassiopeia template (current frontend template) using the PageBuilder.

As a student, here is the list of things expected from you as a deliverable for the project:

*Improve the function of the PageBuilder and add missing features like parameters, elements, … so at the end of the project it should be possible to create a structure which looks and acts like the current Cassiopeia template (if another template is the current default one, then this should be the reference)
*Iron out any existing issues to make the page builder release ready.

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, VueJS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===
*Hard

===Mentors===
*[mailto:vivianamenzel@gmail.com Dr. Viviana Menzel] - Main Mentor
*[mailto:anuragvns1999@gmail.com Anurag Kumar]
*[mailto:nitishbahl24@gmail.com Nitish Bahl]
[[Image:Gsoc2016.png|30px|center]]

==Project II: Auto Updater==

===Project Description===

An Auto-Updater would decrease the number of hacked pages significantly. With this project Joomla! 4 should be extended by an auto updater. In order to prevent that such an auto-update feature can be weaponized, strong cryptographic signatures have to be used for signing and verifying available updates. A centrally hosted service should trigger site updates on all connected Joomla sites.

As a student, here is the list of things expected from you as a deliverable for the project:

*Extend the current Joomla! Updater with a secure auto-update function; Available updates need to be downloaded and their integrity has to be verified using cryptographic signatures
*Implement a CLI tool to sign Joomla updates
*Implement a centralized service triggering sites that require updates

===Knowledge Prerequisite===
*Must have: Knowledge of PHP

===Difficulty===
*Medium

===Mentors===
*[mailto:david.jardin@community.joomla.org David Jardin] - Main Mentor
*[mailto:niels.braczek@community.joomla.org Niels Braczek]
*[mailto:tobias.zulauf@community.joomla.org Tobias Zulauf]
*[mailto:harald.leithner@community.joomla.org Harald Leithner]

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

==Project III: Feature enhancement ==

===Project Description===
====Cookies management====
Create a cookie management system (component / plugin) in Joomla 4 to manage cookies as required by GDPR and other privacy regulations.
====Improve Menu List view (Menu Items)====
Add information of the selected menu item (like article title and id, category title and id) to the menu overview list and link it directly to the items. Categories receive a link to the category item as well as to the list of child items.
It should be taken care for performance, so e.g. information should be visible on request.
====Improve Menu-Module Assignment====
Placing modules on a page (in the menu item form) is currently tedious. Ability to change the module menu assignment in the menu item.
====Improve Content====
Remove the view featured and integrate it in the current article list. Take care of the featured ordering.
====Improve the incorporation of modules in the Articles-Edit-View====
The function to insert modules in an article will be supplemented with the function to create and edit Modules in the Article-Edit-View.

===Knowledge Prerequisite===
*Must have: PHP, XML, CSS, JS
*Nice to have: Joomla MVC, Bootstrap 4

===Difficulty===
*Medium

===Mentors===
*[mailto:christiane.maier-stadtherr@community.joomla.org Christiane Maier-Stadtherr] - Main Mentor
*[mailto:j.weigel@karo3.de Jules Weigel]
*[mailto:luca.marzo@community.joomla.org Luca Marzo]
*[mailto:achilleas.papageorgiou@community.joomla.org Achilleas Papageorgiou]

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

==Project IV: Performance Improvements==

===Project Description===
Joomla! has several testing procedures until it gets released, but currently it lacks in terms of high performance tests with thousands of contents.

This project should close this gap by creating tools which support this kind of tests.

As a student, here is the list of things expected from you as deliverable for the project:
*Create a generic component which allows (via adapters?) to generate content for all extensions (core and 3rd party) in Joomla!
*Create different “adapter” to support com_content, com_menu, com_categories, com_tags
*Integrate the Joomla! 4 CLI function into the component to execute the functionality via the CLI.
*Check the performance of each component where an adapter exists and improve the database queries (as PR against the core)

===Knowledge Prerequisite===
*Must have: PHP, SQL
*Nice to have: Joomla MVC, Bootstrap 4

===Difficulty===
*Easy

===Mentors===
*[mailto:nicolagalgano@yahoo.it Nicola Galgano] - Main Mentor
*[mailto:peter.martin@community.joomla.org Peter Martin]
*[mailto:astrid.guenther@community.joomla.org Astrid Günther]
*[mailto:shivamdiehard@gmail.com Shivam Rajput]

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

==Project V: Media Manager==

===Project Description===
With Joomla 4, the Media Manager got a complete rewrite. The Media Manager team finished milestone 1 from the planned list.
In this project milestone 2 should be implemented.

As a student, here is the list of things expected from you as deliverable for the project:
*Implement a “database abstraction” for the files, so all files will be entries into the database and folders will be categories. A virtual layer above the (cloud) file system. This function should be opt-in (needs probably a htaccess) and still support the old way of handling files.
*Implement permissions for files and folders, based on the “database abstraction” layer
*Allow the creation of different image sizes
*Extend the “add image” editor button to support srcset (with different sizes)

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, VueJS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===
*Moderate

===Mentors===
*[mailto:benjamin.trenkle@community.joomla.org Benjamin Trenkle]
*Sebastian Enns
*[mailto:mathur.geetanshu887@gmail.com Geetanshu Mathur]

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

{{tip|title=More Coming Soon!}}

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

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

GSoC 2020 Project Ideas

2019-12-21T23:50:45Z

Bembelimen: Updated email addresses

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

{{tip|title=The application for students is going to open soon!}}

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

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

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

==Project I: Page Builder ==

===Project Description===
The main focus of the PageBuilder lies on a Drag & Drop editor, which makes it possible to create a full Joomla! frontend template with custom defined positions without writing any HTML code. Users can use predefined elements - container, grid, column, module position as well as custom elements. 3rd party developers are able to add their own elements via plugins. https://docs.joomla.org/J4.x:Page_Builder

This project is a continuation of the GSoC Page Builder project 2019 (https://github.com/joomla-projects/gsoc19_page-builder ). The idea is to extend the basic implementation to a level where it’s possible to reproduce the Cassiopeia template (current frontend template) using the PageBuilder.

As a student, here is the list of things expected from you as a deliverable for the project:

*Improve the function of the PageBuilder and add missing features like parameters, elements, … so at the end of the project it should be possible to create a structure which looks and acts like the current Cassiopeia template (if another template is the current default one, then this should be the reference)
*Iron out any existing issues to make the page builder release ready.

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, VueJS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===
*Hard

===Mentors===
*[mailto:vivianamenzel@gmail.com Dr. Viviana Menzel] - Main Mentor
*[mailto:anuragvns1999@gmail.com Anurag Kumar]
*[mailto:nitishbahl24@gmail.com Nitish Bahl]
[[Image:Gsoc2016.png|30px|center]]

==Project II: Auto Updater==

===Project Description===

An Auto-Updater would decrease the number of hacked pages significantly. With this project Joomla! 4 should be extended by an auto updater. In order to prevent that such an auto-update feature can be weaponized, strong cryptographic signatures have to be used for signing and verifying available updates. A centrally hosted service should trigger site updates on all connected Joomla sites.

As a student, here is the list of things expected from you as a deliverable for the project:

*Extend the current Joomla! Updater with a secure auto-update function; Available updates need to be downloaded and their integrity has to be verified using cryptographic signatures
*Implement a CLI tool to sign Joomla updates
*Implement a centralized service triggering sites that require updates

===Knowledge Prerequisite===
*Must have: Knowledge of PHP

===Difficulty===
*Medium

===Mentors===
*[mailto:david.jardin@community.joomla.org David Jardin] - Main Mentor
[[Image:Gsoc2016.png|30px|center]]

==Project III: Feature enhancement ==

===Project Description===
====Cookies management====
Create a cookie management system (component / plugin) in Joomla 4 to manage cookies as required by GDPR and other privacy regulations.
====Improve Menu List view (Menu Items)====
Add information of the selected menu item (like article title and id, category title and id) to the menu overview list and link it directly to the items. Categories receive a link to the category item as well as to the list of child items.
It should be taken care for performance, so e.g. information should be visible on request.
====Improve Menu-Module Assignment====
Placing modules on a page (in the menu item form) is currently tedious. Ability to change the module menu assignment in the menu item.
====Improve Content====
Remove the view featured and integrate it in the current article list. Take care of the featured ordering.
====Improve the incorporation of modules in the Articles-Edit-View====
The function to insert modules in an article will be supplemented with the function to create and edit Modules in the Article-Edit-View.

===Knowledge Prerequisite===
*Must have: PHP, XML, CSS, JS
*Nice to have: Joomla MVC, Bootstrap 4

===Difficulty===
*Medium

===Mentors===
*[mailto:christiane.maier-stadtherr@community.joomla.org Christiane Maier-Stadtherr] - Main Mentor
*[mailto:j.weigel@karo3.de Jules Weigel]
*[mailto:luca.marzo@community.joomla.org Luca Marzo]
*[mailto:achilleas.papageorgiou@community.joomla.org Achilleas Papageorgiou]
*[mailto:benjamin.trenkle@community.joomla.org Benjamin Trenkle]

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

==Project IV: Performance Improvements==

===Project Description===
Joomla! has several testing procedures until it gets released, but currently it lacks in terms of high performance tests with thousands of contents.

This project should close this gap by creating tools which supports this kind of tests.

As a student, here is the list of things expected from you as deliverable for the project:
*Create a generic component which allows (via adapters?) to generate content for all extensions (core and 3rd party) in Joomla!
*Create different “adapter” to support com_content, com_menu, com_categories, com_tags
*Integrate the Joomla! 4 CLI function into the component to execute the functionality via the CLI.
*Check the performance of each component where an adapter exists and improve the database queries (as PR against the core)

===Knowledge Prerequisite===
*Must have: PHP, SQL
*Nice to have: Joomla MVC, Bootstrap 4

===Difficulty===
*Easy

===Mentors===
*[mailto:nicolagalgano@yahoo.it Nicola Galgano] - Main Mentor

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

==Project V: Media Manager==

===Project Description===
With Joomla 4, the Media Manager got a complete rewrite. The Media Manager team finished milestone 1 from the planned list.
In this project milestone 2 should be implemented.

As a student, here is the list of things expected from you as deliverable for the project:
*Implement a “database abstraction” for the files, so all files will be entries into the database and folders will be categories. A virtual layer above the (cloud) file system. This function should be opt-in (needs probably a htaccess) and still support the old way of handling files.
*Implement permissions for files and folders, based on the “database abstraction” layer
*Allow the creation of different image sizes
*Extend the “add image” editor button to support srcset (with different sizes)

===Knowledge Prerequisite===
*Must have: Knowledge of PHP, HTML, CSS, VueJS, JavaScript
*Nice to have: Joomla! 4 template creation

===Difficulty===
*Moderate

===Mentors===
*[mailto:benjamin.trenkle@community.joomla.org Benjamin Trenkle]
*Sebastian Enns

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

{{tip|title=More Coming Soon!}}

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

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

Pizza Bugs and Fun 2018 Germany

2018-09-07T11:54:53Z

Bembelimen: Fix broken email address

<noinclude><languages /></noinclude>
{{RightTOC}}
[[Image:pbf-2018.png|700px]]

<translate>

A Joomla! Pizza Bug and Fun event '''8th of September 2018''' - originally planned for Germany, but now takes place in many countries across europe.
This wiki will be used as the central resource for coordinating efforts and accumulating results from this event.
</translate>

<translate>
== Goals == 
</translate>

<translate>

Whether you are a newbie, beginner or professional, graphic designer or programmer, whether you have an agency or a club site, whether female or male, whether young or old. We are happy about everyone who already works with Joomla! or wants to get to know Joomla! first. Only the interest in Joomla! counts. Everyone is welcome here.
On '''8th of September 2018''' we would like to invite all Joomla-enthusiastic users, regardless of their previous knowledge, to make Joomla! even better. We are grateful for any support! Participation is free, non-alcoholic drinks and a pizza included.


* '''Joomla 4''': Joomla 4.0 is on the horizon, but over 200 bugs and feature requests are untested, which means, they cannot go into the Joomla core.
* '''Documentation''': There are lots of untranslated Documents, Tutorials and Help Screens. At the PBF Event we hope to translate a lot of it to give Joomla! users as much information as possible in their language.
* '''Patch testing''': As a main rule, new functions for Joomla have to be tested before they can be merged into an official release. Usually it takes only a few minutes and Joomla becomes better and better.
</translate>

<translate>

== FAQ == 
</translate>
<translate>

You'll find as much information as possible on how this event is organized. If you don't find what you are looking for, here are a few FAQs:
</translate>

<translate>

#'''Q:''' Where can I register if I want to join? '''A:''' Contact a [[S:MyLanguage/Portal:Joomla_User_Groups|Joomla! User Groups (JUGs)]] near you or write a mail to Benjamin Trenkle [mailto:pbf@benjamintrenkle.de].
</translate>
<translate>

#'''Q:''' I can't come to a location - can I join online? '''A:''' Yes! You only need a computer and internet, but unfortunately you have to order a pizza by yourself.
</translate>

<translate>
== Organization, logistics and communications == 
</translate>
<translate>

This PBF is organized by local [[S:MyLanguage/Portal:Joomla_User_Groups|Joomla! User Groups (JUGs)]] in Germany. You can find more information on the special event page: [https://www.pizza-bugs-fun.de pizza-bugs-fun.de] (german).


You would like to participate but you don't have a user group nearby? Or you are Joomla User Group and want to join? Just do it!
There are very small requirements:


*You need a room with WiFi access
*You need some Joomlers equipped with a laptop and motivation.
*Do no thesitate to send an email to Benjamin Trenkle [mailto:pbf@benjamintrenkle.de] or search him in Glip.


Of course, you can also join from home, but where is the fun without the community and the pizza?
</translate>

<translate>
===Social Media=== 
</translate>
<translate>

For sharing information in the social media please use this hashtag: #pbf18de.
</translate>

<translate>
== Locations == 
</translate>

<translate>

If you want to get people together and have a venue to share, please add it below. Share as many details as possible, like exact location, URL for more information about the venue, ways to register, date and time when the venue is available etc. If you have any questions regarding this, feel free to contact Benjamin Trenkle ([mailto:pbf@benjamin.trenkle.de]).
</translate>

<translate>
=== Europe === 
</translate>
<translate>

This year we organize Pizza, Bugs & Fun in Germany, Austria and Switzerland at various local user groups, called [[S:MyLanguage/Portal:Joomla_User_Groups|Joomla! User Group (JUG)]].
So far the following cities are registered:
*Munich (DE Initiator)
*Augsburg (DE)
*Dresden (DE)
*Frankfurt/Gießen (DE)
*Fribourg (DE)
*Hamburg (DE)
*Coblenz (DE)
*Cologne (DE)
*Nuremberg (DE)
*Vienna (AUT)
*Zurich (CH)
*Bussum (NL)
</translate>

<translate>
== Registration == 
</translate>
<translate>
=== For write access to this wiki === 
</translate>
<translate>

To get write access to this wiki you will need to [[Special:Userlogin|register here first]]. Please be aware that the registration process requires a valid email address. If you are traveling to one of the physical locations you are advised to ensure that you have registered on this wiki and have a valid login before you travel. You don't need access to your email account after registration.</translate>

<translate>
=== At a physical location === 
</translate>
<translate>

If you wish to be present at one of the physical locations listed above then you must register in advance because space most likely is limited. Registrations are the responsibility of the individual location organizers and you should click on the appropriate link above for more information.
</translate>

<translate>
=== Taking bugs, tasks and pizza === 
</translate>
<translate>

Pizza can be ordered at a shop near by :-)
</translate>

<translate>
==Requirements== 
</translate>
<translate>

* All code must be made available under the [http://www.gnu.org/licenses/gpl-2.0.html General Public Licence version 2].
</translate>
<translate>

* All documentation contributions must be made available under the [[S:MyLanguage/JEDL|Joomla! Electronic Documentation License]]. Further information on the JEDL is available in the [[S:MyLanguage/JEDL/FAQ|JEDL Frequently Asked Questions]]
</translate>
<translate>

* No advertising or self-promotion will be allowed. This includes backlinks to your website or anyone else's. The one exception is that if you have made a contribution then feel free to add your name and an optional link to your website to the [[S:MyLanguage/Pizza Bugs and Fun 2/Contributors List|Contributors List]]
</translate>
<translate>

* All contributions must be in English. Note that the official language of the Joomla Project is British/Australian English.</translate>

<translate>

== Preparations and installations ==
</translate>
<translate>

=== 1.Communication tools ===
That's how teamwork works today :-)

In the Glip Chatroom you can ask questions and exchange ideas. [https://glip.com Glip] and [https://github.com GitHub] you need for example if you want to test patches.

</translate>
<translate>

===2.Setting up a Joomla! installation===

Required if you want to test patches. There are two ways to get a Joomla! installation at PBF:
*Option 1: The online PBF environment is available shortly before the PBF event and is also suitable for participants with little system knowledge.

*Option 2 allows you to set up a local installation on your device. Instruction you can find [https://pizza-bugs-fun.de/anleitung.html here] (german).
</translate>
<translate>

===3.JDocs Translations===
If you don't want to test patches but still want to give back a lot of support to the community, help translating the JDocs.

Here you will find all informations you need to get started. Please read '''[[S:MyLanguage/JDOC:How_to_Contribute_to_Joomla!_Documentation|How to Contribute to Joomla! Documentation]]'''.
</translate>
<translate>
==JDocs Contributors== 
List will be completed during the event:
</translate>
{{:Pizza Bugs and Fun 2018 Germany/Contributors List}}
<translate>
==Related Information== 
</translate>
<translate>
*Organizers website [https://www.pizza-bugs-fun.de pizza-bugs-fun.de] (german)
*Community blog entry [https://community.joomla.org/blogs/community/pizza-suppliers-love-joomla.html Pizza suppliers love Joomla!]
*French community announcement [https://www.joomla.fr/actualites/les-fournisseurs-de-pizza-aiment-joomla Les fournisseurs de pizza-aiment Joomla!] (french)
*Dutch community announcement [https://www.joomlacommunity.nl/agenda/pizza-bugs-fun/event/358-joomla-pizza-bugs-en-fun-bussum Joomla! Pizza Bugs en Fun Bussum] (dutch)
</translate>

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Development{{#translation:}}]]
[[Category:Events{{#translation:}}]]
</noinclude>

Pizza Bugs and Fun 2018 Germany

2018-07-18T11:56:34Z

Bembelimen: Added my contact email

<noinclude><languages /></noinclude>
{{underconstruction}}
{{RightTOC}}
[[Image:pbf-2018.png|700px]]

<translate>
A Joomla! Pizza Bug and Fun event will be held in Germany on the '''8th of September 2018'''.
This wiki will be used as the central resource for coordinating efforts and accumulating results from this event.
</translate>

<translate>
== Goals ==
</translate>

<translate>
* '''Joomla 4''' : ''Placeholder''
* '''Documentation''' : ''Placeholder''
* '''Patch testing''' : ''Placeholder''
</translate>

<translate>
== FAQ ==
</translate>
<translate>
You'll find as much information as possible on how this event is organized. If you don't find what you are looking for, here are a few FAQs:
</translate>

<translate>
Q: ''Placeholder''

A: ''Placeholder''
</translate>

<translate>
== Organization, logistics and communications ==
</translate>
<translate>''Placeholder''</translate>

<translate>
===Social Media===
</translate>
<translate>
For sharing information in the social media please use this hashtag: #pbf18de.
</translate>

<translate>
== Locations ==
</translate>

<translate>
If you want to get people together and have a venue to share, please add it below. Share as many details as possible, like exact location, URL for more information about the venue, ways to register, date and time when the venue is available etc. If you have any questions regarding this, feel free to contact Benjamin Trenkle (benjamin.trenkle@community.joomla.org).
</translate>

<translate>
=== Europe ===
</translate>
<translate>
This Pizza, Bugs and Fun event will only take place in german speaking countries: Germany, Austria and Switzerland.
</translate>

<translate>
== Registration ==
</translate>
<translate>
=== For write access to this wiki ===
</translate>
<translate>
To get write access to this wiki you will need to [[Special:Userlogin|register here first]]. Please be aware that the registration process requires a valid email address. If you are traveling to one of the physical locations you are advised to ensure that you have registered on this wiki and have a valid login before you travel. You don't need access to your email account after registration.</translate>

<translate>
=== At a physical location ===
</translate>
<translate>
If you wish to be present at one of the physical locations listed above then you must register in advance because space most likely is limited. Registrations are the responsibility of the individual location organizers and you should click on the appropriate link above for more information.
</translate>

<translate>
=== Taking bugs, tasks and pizza ===
</translate>
<translate>
Pizza can be ordered at a shop near by :-)
</translate>

<translate>
Please check the [[S:MyLanguage/Pizza_Bugs_and_Fun_2#Organization.2C_logistics_and_communications|Organization, logistics and communications section]] for details on how to get involved in working on tasks.
</translate>

<translate>
==Requirements==
</translate>
<translate>
* All code must be made available under the [http://www.gnu.org/licenses/gpl-2.0.html General Public Licence version 2].
</translate>
<translate>
* All documentation contributions must be made available under the [[S:MyLanguage/JEDL|Joomla! Electronic Documentation License]]. Further information on the JEDL is available in the [[S:MyLanguage/JEDL/FAQ|JEDL Frequently Asked Questions]]
</translate>
<translate>
* No advertising or self-promotion will be allowed. This includes backlinks to your website or anyone else's. The one exception is that if you have made a contribution then feel free to add your name and an optional link to your website to the [[S:MyLanguage/Pizza Bugs and Fun 2/Contributors List|Contributors List]]
</translate>
<translate>
* All contributions must be in English. Note that the official language of the Joomla Project is British/Australian English.</translate>

<translate>
==JDocs Contributors==
</translate>
{{:Pizza Bugs and Fun 2018 Germany/Contributors List}}

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Development{{#translation:}}]]
[[Category:Events{{#translation:}}]]
</noinclude>

Joomla CodeSniffer

2016-05-19T13:43:09Z

Bembelimen: Update Netbeans information

== A Nose For Joomla ==

This is a custom coding standard for the PHP CodeSniffer that attempts to codify and enforce the Joomla coding standards. This article covers how to set the automatic code style checker. It consist's of three parts:
# Install PHP CodeSniffer (phpcs)
# Clone Joomla Code Style (for use with for phpcs)
# Configure your IDE to work with PHP CodeSniffer + Joomla Code Style

[[File:CodeSnifferInAction.jpg|center|thumb|300px|PHP Code Sniffer in action]]

==Why?==

- Coherent and consisting coding practice makes the files look more professional. Conflicting styles in the same project (or worse, the same file) not only look sloppy, they encourage further sloppiness.

- When all code complies with the same standard, bad code is easier for everyone to spot.

- It makes it easier for someone new to a particular file in the project to find and fix errors, or extend functionality.

- If there is no consistent standard maintained, the sometimes developers will reformat the code to suit themselves. This causes a wide range of changes in the code repository, and if there is a later problem, a significant change could be lost in the chaff produced by a diff.

==1. Installation of PHP Code Sniffer (phpcs)==

===PEAR===
First of all you have to install the [http://pear.php.net/package/PHP_CodeSniffer/ PHP CodeSniffer]. This set of files is intended to work with phpcs version 1.4, so behavior with any other version is undefined. One way to do this is to start the console (cmd.exe in windows environments) and type:

<code>pear install PHP_CodeSniffer</code>

To specify a specific version of the PHP CodeSniffer, type:

<code>pear install PHP_CodeSniffer-1.5.x</code> (specify a number for x, in August 2015 was 1.5.6)

'''Important note:''' currently the latest PHPcs is the 2.x series. But they are under development so '''Joomla Sniffers are not yet compatible with this 2.x version'''. PEAR gives you the option to install it by default but since Joomla sniffers will not work remind to always install PHPCS 1.5. version not 2.0.

Pear will handle the whole installation by itself.

Then download and unzip the [https://github.com/joomla/coding-standards Joomla! CodeSniffer] and copy the contents of it into /path/to/PHP_CodeSniffer/Standards/Joomla.

In Unix systems this path is usually /usr/lib/php/PHP/PHP_CodeSniffer/Standards/Joomla but this varies from system to system. In Xubuntu 12.04, the path is /usr/share/php/PHP/CodeSniffer/Standards/Joomla.
Windows based system with XAMPP have the following path: PATH_TO_XAMMP\php\PEAR\PHP\CodeSniffer\Standards (for example: C:\xampp\php\PEAR\PHP\CodeSniffer\Standards)

Use

<code>pear config-get php_dir</code>

to find out where the PEAR directory is on your system, then add "/PHP/PHP_CodeSniffer/Standards" to it.

===Composer===
PHP Code Sniffer is available via Composer. It can be installed system-wide with the following command:

<code>composer global require 'squizlabs/php_codesniffer=1.*'</code>

On Linux PHP Code Sniffer (phpcs) will be installed under your user folder:
* Symbolic Link: ~/.composer/vendor/bin/phpcs
* The file: ~/.composer/vendor/squizlabs/php_codesniffer/scripts/phpcs

==2. Clone Joomla Codestyle==
In order to have PHP Code Sniffer (phpcs) sniffing your Joomla projects for the right code style, you've to clone the Joomla Codestyle '''into the /Standards/''' folder of Code Sniffer. That folder already has other folders for styles like PSR1, PSR2, Squiz & Zend.

On Linux, goto the Standards folder of CodeSniffer & git clone from https://github.com/joomla/coding-standards :
$ cd ~/.composer/vendor/squizlabs/php_codesniffer/CodeSniffer/Standards/
$ git clone https://github.com/joomla/coding-standards.git Joomla

You'll end up with a folder like ~/.composer/vendor/squizlabs/php_codesniffer/CodeSniffer/Standards/Joomla/

== Usage ==

You invoke the custom standard by

<code>phpcs --standard=Joomla file/to/sniff</code>

To test a platform file using the provided platform coding standards use

<code>phpcs --standard=build/phpcs/Joomla path/to/file/or/folder</code>

Further documentation on the use of phpcs can be found at: [http://pear.php.net/package/PHP_CodeSniffer/docs]

==3. IDE integration==

While everybody loves the console as it is with no doubt the most effective way to do whatever you need to do.. sometimes even Linux gurus need a little bit of comfort.

Fortunately there is a plugin available for Eclipse, Netbeans and PHPStorm that integrates the CodeSniffer into your favourite IDE, so any coding standard violations are shown like "normal" errors.

=== Netbeans ===

Netbeans has the sniffer functionality integrated into the core system

# Start your netbeans IDE
# Open Tools => Options => PHP => Code Analysis => Code Sniffer
# You have to set the path to the ''phpcs.bat'' from the installed PHP_CodeSniffer PEAR package
#* for Unix based systems the path is something like /usr/bin/phpcs
#* in XAMPP (windows) you can find the file in the php root folder (e.g. C:\xampp\php\phpcs.bat)
# As "Default Standard" choose "Joomla" to use the Joomla! standard
# now you can click ''Ok'' to start sniffing
# Open from the top menu Source => Inspect...
# Enjoy

=== Eclipse ===
[[Image:eclipse_pti.png|left|thumb|200px|1) Eclipse PTI]]

<div style="clear: both"></div>
Installation is a breeze and follows the usual pattern:
# <tt>Help => Install new Software...</tt>
# <tt>Work with:</tt> Fill in one of the update site URLs found here: http://www.phpsrc.org/eclipse/pti/
# Select the desired tools
# Restart Eclipse.

[[Image:eclipse_pti_settings.png|right|thumb|150px|2) Eclipse PTI settings]]
You are now able to sniff for code violations against common standards like PEAR or Zend etc.

To sniff against your own standards, all you have to do is specify their location and activate them (see screen shot 2)

# <tt>Window => Preferences</tt>
# <tt>PHP Tools => PHP CodeSniffer</tt>

Happy sniffing

==== PHP Tools compatibility issue ====

PHP Tools does not directly support PHP_CodeSniffer-1.5.x. It reports this error:

<tt>PHP Fatal error: Uncaught exception 'PHP_CodeSniffer_Exception' with message 'Class PHP_CodeSniffer_CommentParser_ClassCommentParser not found' in /usr/share/php5/PEAR/PHP/CodeSniffer/Standards/Joomla/Sniffs/Commenting/FileCommentSniff.php:18</tt>

It comes with a pre-packaged CodeSniffer version located in eclipse/plugins/org.phpsrc.eclipse.pti.library.pear_.../php/library/PEAR/PHP. To fix the issue, you can just remove the pre-packaged CodeSniffer version and link the local version. For example, /usr/share/php/PHP.

<tt>ln -s /usr/share/php/PHP /home/.../eclipse/plugins/org.phpsrc.eclipse.pti.library.pear_.../php/library/PEAR/PHP</tt>

In any case, you can also debug a PHP Tools issue, enabling the debug mode to show the internal commands in Eclipse console:

# <tt>Window => Preferences</tt>
# <tt>PHP Tools => PHP CodeSniffer</tt>
# <tt>Debug: print PHP output to console</tt>

Command example:

<tt>/usr/bin/php -c /tmp/zend_debug/session8314597725413224814.tmp -d asp_tags=off -d short_open_tag=on /home/.../eclipse/plugins/org.phpsrc.eclipse.pti.tools.codesniffer_1.3.0.R20111119000000/php/tools/phpcs.php --report=xml --standard=/home/.../Joomla /home/..../myphpfile.php</tt>

=== PHPStorm ===

==== PHPStorm ====
CodeSniffer is supported out of the box in PHPStorm, just go to settings, and under "Inspections" you will see the list of Sniff you have installed.

See: the [http://www.jetbrains.com/phpstorm/webhelp/using-php-code-sniffer-tool.html JetBrains documentation page for setting the Code Sniffer] and also [http://blog.jetbrains.com/webide/2012/03/checking-your-code-with-php-code-sniffer-in-phpstorm-4-0/ phpStorm Blog])

For users on ubuntu using phpStorm. Don't listen instructions at http://www.jetbrains.com/phpstorm/webhelp/using-php-code-sniffer-tool.html#d59626e1126 because there is no working bat (windows file) on linux system. To validate your CodeSniffer choose /usr/bin/phpcs launcher.

Under Settings->Inspections when you choose joomla profile, in the tree below, search for PHP and open it and than make sure that PHP Code Sniffer validation checkbox is checked. Otherwise PHP Code Sniffer won't sniff your code.

On ubuntu you install code standards with:
cd /usr/share/php/PHP/CodeSniffer/Standards
sudo git clone http://github.com/joomla/coding-standards.git Joomla
===== Installing Joomla Sniff =====

# get the sniffers from the [https://github.com/joomla/coding-standards coding standards repo]
# unpack Joomla CodeSniffer rules under:
## If you are using XAMPP ''\xampp\php\PEAR\PHP\CodeSniffer\Standards\Joomla''
## If not maybe you should check here: ''/usr/share/php/PHP/CodeSniffer/Standards''
# Go to Settings (CTRL-ALT-S) and search for "PHP Code Sniffer Validation", click the button Validate to force reload of rules from disk
# Joomla should be now available in the list. See following image:
<gallery>
File:PhpStorm4CodeSniffer.png|PHPStorm 4.x CodeSniffer
File:PhpStorm6CodeSniffer.png|PHPStorm 6.x CodeSniffer
File:PhpStorm8CodeSniffer.png|PHPStorm 8.x CodeSniffer
</gallery>
<div style="clear: both"></div>

===== Installing Joomla Code style =====

It's nice to be able to check that the standards are respected, but it's even nicer if phpstorm helps you formatting properly too as you are coding.
To add joomla code style to phpstorm
# first get the xml scheme file from here: https://github.com/betweenbrain/phpstorm-joomla-code-style
# Then save the file in phpstorm [http://www.jetbrains.com/phpstorm/webhelp/project-and-ide-settings.html#d231397e460 home directory]: <phpstorm home directory>/config/codestyles/Joomla.xml
# restart phpstorm, and you should be able to select Joomla from the Code Style > Scheme select box

==== PHP PSR-0, PSR-1 and PSR-2 ====
* https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md
* https://github.com/pmjones/fig-standards/blob/psr-1-style-guide/proposed/PSR-1-basic.md
* https://github.com/pmjones/fig-standards/blob/psr-1-style-guide/proposed/PSR-2-advanced.md

===== Installing PHP PSR-0, PSR-1 and PSR-2 Sniff =====

A CodeSniffer sniff to check against the PSR-x Coding Standard

Download files at
* https://github.com/squizlabs/PHP_CodeSniffer/tree/master/CodeSniffer/Standards

if you are using Xampp,
# unpack PSR-1 CodeSniffer rules under \xampp\php\PEAR\PHP\CodeSniffer\Standards\PSR (SPR or any directory will work)
# Go to Settings (CTRL-ALT-S) and search for "PHP Code Sniffer Validation", click the button Validate to force reload of rules from disk
# PSR is available in the list

==== PHPStorm / Alternative method ====
'''NOTE''': This method is '''outdated''', but it might be useful if you are looking for a different integration. It also demonstrates the use of external tools in PHPStorm - so it ''shouldn't be deleted''.

The CodeSniffer can also be integrated easily as an external tool. PHPStorm will display the output in the console, including clickable links containing line and column numbers to the files that contain errors.

* Click on "Settings" and search for "External tools"
* Click "Add..."
* Choose a "name", "Group" and "Description".
* Click "Output Filters"
** Click "Add...", Choose a name and enter under "Regular expression to match output" the value: <tt>$FILE_PATH$:$LINE$:$COLUMN$</tt>
* "Program": Search for the phpcs executable on your system. You have to set the path to the ''phpcs.bat'' from the installed PHP_CodeSniffer PEAR package
** for Unix based systems the path is something like /usr/bin/phpcs
** in XAMPP (windows) you can find the file in the php root folder (e.g. C:\xampp\php\phpcs.bat)
* "Parameters":
** <tt>--standard=<path/to/joomla-platform>/build/phpcs/Joomla</tt> The path to the Joomla! coding standards.
** <tt>--report=emacs</tt> The will generate a simple list containing links to the error files
** Optional you may want to specify <tt>-p</tt> for "progress" or <tt>-n</tt> for "errors only".
** The last parameter has to be <tt>$FilePath$</tt> specifying the file or folder you want to sniff.

A typical "Parameters" line on a Linux system might look like this:
<pre>-np --standard=/home/elkuku/libs/joomla/build/phpcs/Joomla --report=emacs $FilePath$</pre>

You may now right click any file or folder and choose the sniffer from the context menu or add a new toolbar button with a nice Joomla! logo [[File:icon-16-joomla.png]].

=== References ===
* http://www.phpsrc.org/ PTI - PHP tools integration for Eclipse
* http://sourceforge.net/projects/phpmdnb/ Netbeans plugin
* http://hakre.wordpress.com/2010/03/06/php-code-sniffer-eclipse-and-wordpress/ - Excellent article. Just change "Wordpress" for "Joomla!" ;)

[[Category:Development]][[Category:Bug Squad]]
[[Category:IDE (Integrated development environment)]]