The accessiblemedia form field type provides modal access to the media manager for the choice of an image like the media field. Users with appropriate permissions will be able to upload files.

Like the media field you can use parameters

* type (mandatory) must be media.
* name (mandatory) is the unique name of the field.
* label (mandatory) (translatable) is the descriptive title of the field.
* description (optional) (translatable) is text that will be shown as a tooltip when the user moves the mouse over the drop-down box.
* directory (optional) is the directory from which the user will be able to choose a file. This attribute should be relative to the top level /images/ folder. The default is that the user will be confined to the top level /images/ folder.
* preview (optional) shows or hides the preview of the currently chosen image. ("true": Show always, "tooltip": Show as tooltip, "false": Show never). Default is "tooltip". (since Joomla! 2.5.5)
* preview_width (optional) sets the max-width of preview image (default: "200").
* preview_height (optional) sets the max-height of preview image (default: "200").

Example XML field definition:

<field name="myimage" type="accessiblemedia" directory="stories" />

[[File:Datei.png|200px|thumb|left|The right one is a Accessible Media Field]]
This will open the media manager with the directory /images/stories/ already selected an provide an text field like the media field. In addition it offers a text field for add an alternative text.

Note that if you are using this field on the frontend then permissions restrictions are likely to be in force. If the user is not authorized to view or add media they will see an error page in the modal popup ("403 You are not authorized to view this resource.").
See also

PR where the field is addedː [https://github.com/joomla/joomla-cms/pull/27712 PR]

2020-03-29T23:26:57Z

Astridx:

Testing Joomla! patches

2020-03-29T23:26:25Z

Astridx:

<noinclude><languages /></noinclude>
<translate>
In all software there are mistakes that need to be fixed, this is also the case in Open Source software like Joomla!. The source code of Joomla! is centrally located on the internet, making it accessible to everyone. Anyone who spots a bug or issue with Joomla! can report it. A guide to Filing bugs and issues can be found here: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]]
Reported bugs will be solved and eventually need testing. This page explains how you can contribute to the Joomla project by testing proposed solutions. You do not need to have any coding knowledge, you do need a Joomla installation to test on.
A Quick Reference Guide for testing is available at: [[S:MyLanguage/Testing Joomla! patches QuickReferenceGuide|Testing Joomla! patches QuickReferenceGuide]]</translate>

<translate>
=== The Joomla staging code === 
</translate>
<translate>
The Joomla staging code is the most recent code that is being worked on. All bugfixes and new features are applied to this code.


The Joomla staging code is located at https://github.com/joomla/joomla-cms, this is the code that needs to be installed. How that is done is explained a little further under [[#Preparing to test|Preparing to test]].</translate>

<translate>
=== The issue-tracker === 
</translate>
<translate>
The issue-tracker for Joomla is located here: https://issues.joomla.org</translate>

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

<translate>
The list shows the tracker items from new to old but the order can be changed by using the filters under Search tools. All items in the tracker, that have a patch, have a version number beside the title.
* PR-staging: This is Joomla 3.9.x
* PR-4.0-dev: This is Joomla 4.0</translate>

<translate>
These labels will change in the future as new versions come and old versions go.


The status is important and this is an explanation:</translate>

<translate>
'''New''' - Immediately after an issue is reported it receives this status. When you find a bug, create a description how to reproduce the bug. People who are testing the issue then know how to test the patch.</translate>

<translate>
'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.</translate>

<translate>
'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.</translate>

<translate>
'''Ready to commit''' - The patch has been successfully tested and the code can be committed.</translate>

<translate>
'''Closed''' - This status is for all issues that need no further action.</translate>

<translate>
Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.</translate>

<translate>
Basically you start testing issues that have the status "Pending".</translate>

<translate>

=== Preparing to test === 
</translate>
<translate>
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.</translate>

<translate>
==== Create folder ==== 
</translate>
<translate>
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.</translate>

<translate>
==== Download Joomla! ==== 
</translate>
<translate>
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''</translate>

[[File:joomla_github-<translate>
en</translate>.png]]

<translate>
This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.</translate>

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

<translate>
Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data


This is important so everybody uses the same data to test!


The installation folder does not have to be removed, this way you can easily reinstall everything if needed.</translate>

<translate>

=== Download Patch Tester === 
</translate>
<translate>
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page] and after that can be installed via the Extension manager in Joomla.</translate>

<translate>
To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].</translate>

<translate>
=== Setup Patch Tester === 
</translate>
<translate>
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.</translate>

[[File:patchtester_repo-<translate>
en</translate>.png]]

<translate>

On the second tab called GitHub Authentication you can enter your GitHub username and password or token if you use a token.
</translate>

[[File:patchtester_details-<translate>
en</translate>.png]]

<translate>

Note: If you have enabled Two-Factor Authentication for your GitHub account, you will need to create a personal access token at https://github.com/settings/applications and enter that in the GitHub token field.
</translate>

<translate>
After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.</translate>

<translate>
You are now ready to start testing.


Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.</translate>

<translate>

=== Installing Patch === 
</translate>
<translate>
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:


[#4308] - Fixed event dispatching inconsistencies leading to incomplete API


Beside the # is the ID and behind the - sign comes the title.</translate>

<translate>
After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced</translate>

<translate>
=== Recording test results === 
</translate>
<translate>

After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.


It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.
</translate>

[[File:New_testthis_button-<translate>
en</translate>.png|The new Test This button and how to use it]]

<translate>
=== Revert patch === 
</translate>
<translate>
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git == 
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.


To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.


The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed

=== Getting the diff === 
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is <source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>


To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes <source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff === 
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>

=== Applying the diff === 
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>


With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff === 
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>


To verify that everything is clean you can run
<source lang="bash">
git status
</source>


You should get the notice: 
'''nothing to commit, working directory clean'''


In case the system is not clean you can get a notice like this: 
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]


In case you see changed files but you have not made any changes you can cleanup the system with <source lang="bash">
git reset --hard HEAD
</source>


Now all should be clean


If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.</translate>

<translate>

== Prebuild packages == 
For all people who test Pull Requests for J4: There is a new feature for every J4 pull request which has been received any commit since that [https://github.com/joomla/joomla-cms/pull/28409 new Feature] was merged into J4, i.e. for all new PR's, too: You can find in the test details. At the bottom of such PR's is a link to Downloads.

Maybe you have to expand the details for the tests first.

[[File:PrebuildPackages1.png||Maybe you have to expand the details for the tests first.]]

Then you see the link to download.

[[File:PrebuildPackages2.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and upload packages.

[[File:PrebuildPackages3.png||Then you see the link to download.]]

This will get you a copy of the Joomla 4.-dev code inclusive the patch in a ZIP file.

Unzip the file in a temporary location, a folder named Joomla_[Version]+[Number of Path]-Development-Full_Package will appear.

For Version 4.0.0-beta1-dev and PR-number 28462 this will be for example Joomla_4.0.0-beta1-dev+pr.28462-Development-Full_Package.

Now we need to create a folder on either the local web server or the hosting account that can be accessed via the browser. Create the folder bugtesting and go to this folder via Explorer or Finder.

Go into the Joomla_[Version]+[Number of Path]-Development-Full_Package folder and copy the complete contents to the folder bugtesting that you created in the previous step.

Now you can install Joomla by navigating to http://localhost/bugtesting if you are using a local web server, if you use one on a hosting account, navigate to the appropriate URL for the hosting account.

[[File:PrebuildPackages4.png||Set up your sytem.]]

For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos== 
</translate>
<translate> Learn How to test patch with this video series ''How to "Patch Test" Joomla! code'':</translate>
<translate> *Part 1: Introduction</translate>
{{#widget:YouTube|id=zmnWkMisdJk}}

<translate> *Part 2: Neard Web Server setup</translate>
{{#widget:YouTube|id=Tqj-BAmPGLA}}

<translate> *Part 3: Sample issue testing.</translate>
{{#widget:YouTube|id=s881RLaFO8U}}

<translate>
== Link== 
</translate>
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

File:PrebuildPackages3-en.png

2020-03-29T23:11:20Z

Astridx:

File:PrebuildPackages2-en.png

2020-03-29T23:10:44Z

Astridx:

Testing Joomla! patches

2020-03-29T23:09:13Z

Astridx:

<noinclude><languages /></noinclude>
<translate>
In all software there are mistakes that need to be fixed, this is also the case in Open Source software like Joomla!. The source code of Joomla! is centrally located on the internet, making it accessible to everyone. Anyone who spots a bug or issue with Joomla! can report it. A guide to Filing bugs and issues can be found here: [[S:MyLanguage/Filing_bugs_and_issues|Filing bugs and issues]]
Reported bugs will be solved and eventually need testing. This page explains how you can contribute to the Joomla project by testing proposed solutions. You do not need to have any coding knowledge, you do need a Joomla installation to test on.
A Quick Reference Guide for testing is available at: [[S:MyLanguage/Testing Joomla! patches QuickReferenceGuide|Testing Joomla! patches QuickReferenceGuide]]</translate>

<translate>
=== The Joomla staging code === 
</translate>
<translate>
The Joomla staging code is the most recent code that is being worked on. All bugfixes and new features are applied to this code.


The Joomla staging code is located at https://github.com/joomla/joomla-cms, this is the code that needs to be installed. How that is done is explained a little further under [[#Preparing to test|Preparing to test]].</translate>

<translate>
=== The issue-tracker === 
</translate>
<translate>
The issue-tracker for Joomla is located here: https://issues.joomla.org</translate>

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

<translate>
The list shows the tracker items from new to old but the order can be changed by using the filters under Search tools. All items in the tracker, that have a patch, have a version number beside the title.
* PR-staging: This is Joomla 3.9.x
* PR-4.0-dev: This is Joomla 4.0</translate>

<translate>
These labels will change in the future as new versions come and old versions go.


The status is important and this is an explanation:</translate>

<translate>
'''New''' - Immediately after an issue is reported it receives this status. When you find a bug, create a description how to reproduce the bug. People who are testing the issue then know how to test the patch.</translate>

<translate>
'''Confirmed''' - The tracker team has been able to reproduce the issue. The coding team is going to look for a solution.</translate>

<translate>
'''Pending''' - A solution has been found for the issue. A patch has been attached that can be tested. The issue needs to be tested. Pay attention to the label beside the title, this indicates for which Joomla version the patch is applicable.</translate>

<translate>
'''Ready to commit''' - The patch has been successfully tested and the code can be committed.</translate>

<translate>
'''Closed''' - This status is for all issues that need no further action.</translate>

<translate>
Filtering is useful in the issue tracker. Monitoring can be useful to receive notifications of an issue that has been updated.</translate>

<translate>
Basically you start testing issues that have the status "Pending".</translate>

<translate>

=== Preparing to test === 
</translate>
<translate>
First the master code has to be retrieved from the Joomla GitHub repository.
There are several different ways to download the Joomla master code but here we only discuss the download option.</translate>

<translate>
==== Create folder ==== 
</translate>
<translate>
First we need to create a folder on either the local webserver or the hosting account that can be accessed via the browser. Create the folder '''bugtesting''' and go to this folder via Explorer or Finder.</translate>

<translate>
==== Download Joomla! ==== 
</translate>
<translate>
Go to the [https://github.com/joomla/joomla-cms Joomla GitHub location] and click on '''Download ZIP'''</translate>

[[File:joomla_github-<translate>
en</translate>.png]]

<translate>
This will get you a copy of the Joomla master code in a ZIP file. Unzip the file in a temporary location, a folder named joomla-cms-staging will appear. Inside this folder is the Joomla master code. Go into the joomla-cms-staging folder and copy the complete contents to the folder '''bugtesting''' that you created in the previous step.</translate>

After that you have to set up your system. For more information see https://docs.joomla.org/J4.x:Setting_Up_Your_Local_Environment/en.

<translate>
Now you can install Joomla by navigating to <code><nowiki>http://localhost/bugtesting</nowiki></code> if you are using a local webserver, if you use one on a hosting account, navigate to the appropriate URL for the hosting account. You will see the regular installation process of Joomla.
For sample data choose: Test English (GB) sample data


This is important so everybody uses the same data to test!


The installation folder does not have to be removed, this way you can easily reinstall everything if needed.</translate>

<translate>

=== Download Patch Tester === 
</translate>
<translate>
To help you with the process of testing patches, a Joomla extension called Patch Tester has been developed. The Patch Tester can be downloaded from the [https://github.com/joomla-extensions/patchtester/releases Patch Tester page] and after that can be installed via the Extension manager in Joomla.</translate>

<translate>
To use the Patch Tester a GitHub account is required, the reason for this that there is a strict limit on the number of anonymous requests that can be made via the Patch Tester. You can sign up for a GitHub account on [https://github.com/join this page].</translate>

<translate>
=== Setup Patch Tester === 
</translate>
<translate>
The GitHub account details can be entered into the settings of the Patch Tester. After the Patch Tester has been installed go to Components -> Joomla! Patch Tester and click on Options in the top right corner. The Options page shows up and there are three tabs. On the first tab called GitHub Repository you can choose which repository you want to use. By default this is Joomla! CMS.</translate>

[[File:patchtester_repo-<translate>
en</translate>.png]]

<translate>

On the second tab called GitHub Authentication you can enter your GitHub username and password or token if you use a token.
</translate>

[[File:patchtester_details-<translate>
en</translate>.png]]

<translate>

Note: If you have enabled Two-Factor Authentication for your GitHub account, you will need to create a personal access token at https://github.com/settings/applications and enter that in the GitHub token field.
</translate>

<translate>
After entering your account details click on Save & Close. Once back in the Patch Tester click on Fetch Data in the top left corner.</translate>

<translate>
You are now ready to start testing.


Find an issue in the issue tracker you want to test or use the "Feeling lucky" button. First check if you can reproduce the issue. If you can reproduce the issue, then you can install the patch.</translate>

<translate>

=== Installing Patch === 
</translate>
<translate>
In the Patch Tester find the issue you are working on by (partial) title or ID. The title of a tracker always looks like this:


[#4308] - Fixed event dispatching inconsistencies leading to incomplete API


Beside the # is the ID and behind the - sign comes the title.</translate>

<translate>
After the patch has been found click on the blue button Apply Patch. Check if the bug has been fixed and also check if no new bugs have been introduced</translate>

<translate>
=== Recording test results === 
</translate>
<translate>

After testing, please add your test result in the test overview (''use the button "Test this"''). Now you only need to add a comment if you have extra information or if you test unsuccessful. As the Tracker now automatically add a comment that you test it.


It must also be noted that it is much better if you can test patches in a multilingual environment (''with at least 3 content languages published'') as there can be issues triggered only in such environment.
</translate>

[[File:New_testthis_button-<translate>
en</translate>.png|The new Test This button and how to use it]]

<translate>
=== Revert patch === 
</translate>
<translate>
After a patch has been tested it is no longer needed and can be removed from your test installation, this way you are always testing with a clean system (You can test patches in conjunction to each other to make sure they don't conflict). Go back to the Patch Tester and click on the green button Revert Patch. This will remove the patch and you can start testing the next issue.

== Testing patches using Git == 
Since the Patch Tester cannot be used for all patches to test, sometimes we must use another way. The Patch Tester replaces the complete file and does not only apply the changes of the pull request, so you may not be testing an issue in an isolated state.


To truly test a patch with only the changes made in the patch, we must use Git. The reason is that Git can apply a patch with only the changes in that patch. Git does this using a diff file.


The prerequisites to be able to use the below method are:
* Joomla is installed using Git
* cURL is installed

=== Getting the diff === 
To get a diff from a pull request is rather easy. Let's say the URL to the pull request is <source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452
</source>


To get the diff, all you need to do is add ''.diff'' after the URL, so it becomes <source lang="bash">
https://github.com/joomla/joomla-cms/pull/1452.diff
</source>

=== Testing the diff === 
Before you apply the diff, you can first check if the diff can be applied, a sanity check. Go to the root of your Joomla installation and run the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply --check
</source>

=== Applying the diff === 
After the diff has been tested and there are no errors, the diff can be applied by running the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply
</source>


With the diff applied you can run your tests and record your test results as explained above. If needed, you can apply multiple diffs at once as long as they do not overlap each other. In some cases this is needed when there are multiple pull requests that need to be combined to be tested.

=== Reverting the diff === 
Once you are done with testing you can cleanup the system by revering the diff with the following command:
<source lang="bash">
curl -L https://github.com/joomla/joomla-cms/pull/1452.diff | git apply -R
</source>


To verify that everything is clean you can run
<source lang="bash">
git status
</source>


You should get the notice: 
'''nothing to commit, working directory clean'''


In case the system is not clean you can get a notice like this: 
[[File:Gitwithchanges.png|center|thumb|There are changed files in the working directory]]


In case you see changed files but you have not made any changes you can cleanup the system with <source lang="bash">
git reset --hard HEAD
</source>


Now all should be clean


If you have become enthusiastic to test, give it a try. It takes a bit of effort to set everything up but once that is done, it is fun and easy! In addition you are also contributing to Joomla!.</translate>

<translate>

== Prebuild packages == 
For all people who test Pull Requests for J4: There is a new feature for every J4 pull request which has been received any commit since that [https://github.com/joomla/joomla-cms/pull/28409 new Feature] was merged into J4, i.e. for all new PR's, too: You can find in the test details. At the bottom of such PR's is a link to Downloads.

Maybe you have to expand the details for the tests first.

[[File:PrebuildPackages1.png||Maybe you have to expand the details for the tests first.]]

Then you see the link to download.

[[File:PrebuildPackages2.png||Then you see the link to download.]]

The link leads to a download page for that PR where you can download full install packages and upload packages.

[[File:PrebuildPackages3.png||Then you see the link to download.]]

For testing a PR, people who don't have a git clone and do not have Composer or Node.js can download and install the full install package. If a PR modifies update SQL scripts or other things related to updating, testers can install a 3.10-dev nightly or 3.10 beta and use the update package of that J4 PR to test updating to J4.

== Videos== 
</translate>
<translate> Learn How to test patch with this video series ''How to "Patch Test" Joomla! code'':</translate>
<translate> *Part 1: Introduction</translate>
{{#widget:YouTube|id=zmnWkMisdJk}}

<translate> *Part 2: Neard Web Server setup</translate>
{{#widget:YouTube|id=Tqj-BAmPGLA}}

<translate> *Part 3: Sample issue testing.</translate>
{{#widget:YouTube|id=s881RLaFO8U}}

<translate>
== Link== 
</translate>
[https://brian.teeman.net/joomla/873-a-dummies-guide-to-joomla-bug-testing Brian Teeman: A Dummies Guide to Joomla Bug Testing]

<noinclude>
[[Category:Bug Squad{{#translation:}}]]
[[Category:Bug Tracker{{#translation:}}]]
[[Category:Core Contributions{{#translation:}}]]
[[Category: Tutorials{{#translation:}}]]
</noinclude>

2019-08-19T16:56:00Z

Astridx: