Joomla! Documentation - User contributions [en]

Joomla! Extension Directory FAQs

2013-05-07T09:12:45Z

Nonumber: /* The JED Team */

{{RightTOC}}
==Extensions' submission, approval and rejection==
* FAQ for developers: [[Publishing_to_JED|Publishing to JED]]

==Reviews==

===Why was my review of an extension is rejected, removed and/or edited?===
The following are some reasons why your review may have been rejected, removed or edited:
*Too short.
*Spam and/or self-promotion.
*Contains links.
*Feature requests. Send feature requests to the developer.
*Support requests. Send support requests to the developer.
*Bug reports. Send bug reports to the developer.
*Your review does not show that you used the extension.
*Not a review of the product.
*Contains code. The review section doesn't like code languages.
*Commercial disputes. Instead, report the extension.
*Complaints about licenses, download policies, and version compatibility.
*Violation of the Terms of Service.
*Duplicate accounts.

===I submitted a review yesterday but it is not shown yet, why?===
All reviews are being manually approved by the Editorial Team, and some submissions will be considered borderline and therefore gets a comment and awaits a second opinion from another editor. In some cases reviews can take up to 21 days to be processed.

===How can I change or delete a review that I submitted earlier?===
Please use the ‘Report this review’ button next to the review, and explain what changes you would like added or if you wish to have the review removed in order to be able to submit a new and updated review. By using the ‘Report this review’ we will be able to see that the request is made by the same user who originally created the review.

==Categorization==

===Can I suggest some changes to categorization?===
Categories in JED is constantly evolving to cope with the increasing amount of extensions. We strive to provide a good categorization to fit all extensions listed in JED. If you feel that an extension deserved to be in another existing or new category, please use the "Report This" button and let us know about your suggestion. You can also post your feedback to our forum.

==Directory==

===When is an extension considered ‘Popular’?===
Extension will be shown as ‘Hot’ when it has an average of 150 views or more per day.

===For how long is the tag ‘Just Added’ used?===
An extension will be tagged as ‘Just Added’ for 14 days from the days it is approved and published.

===What is the calculation for an extension to be ‘Top Rated’?===
An extension has to have at least 15 votes to be eligible to be listed as Top Rated Extension. Top Rated extensions are ordered by the average rating given by users.

===How is ‘Most Reviewed’ list calculated?===
Extensions with the highest number of reviews are listed in [http://extensions.joomla.org/extensions/most-reviewed Most Reviewed].

===When is an extension listed in ‘Recently Updated’ page?===
Extensions will be listed in [http://extensions.joomla.org/extensions/updated Recently Update] here when they are updated with new version.

===How are extensions selected to be shown in JED's front page?===
There are 4 main modules in JED's front page.

* '''''Random New Extensions''''' module randomly shows 12 extensions added in the past 4 weeks. All extensions added in this period have equal chance of appearing in the module.
* '''''New and Noteworthy''''' module shows 4 most viewed extensions added in the past 2 weeks. In another words, these are popular new extensions added in the past 2 weeks. Additionally, only listings that have uploaded image are considered in this module.
* '''''Recently Updated''''' module shows 12 most recently updated extensions in JED. Extensions are considered 'updated' when their version information is changed.
* '''''Random Extensions''''' module randomly shows 2 extensions with image.

===What component is used to manage Joomla! Extensions Directory?===
The directory component used at Joomla! Extensions Directory is (a customized version of) [http://extensions.joomla.org/extensions/233/details Mosets Tree] by a company called [http://www.mosets.com Mosets].

==The JED Team==
See here for a full list of the [http://extensions.joomla.org/component/content/article/30 JED team members]

===Contacting the team===
The editors can be reached by submitting a support ticket on the [http://extensions.joomla.org/component/maqmahelpdesk/ JED Help Desk]. Support is no longer provided via email.

<noinclude>[[Category:FAQ]][[Category:JED]]</noinclude>

Joomla! Extension Directory FAQs

2013-05-07T09:10:41Z

Nonumber: /* What component is used to manage Joomla! Extensions Directory? */

{{RightTOC}}
==Extensions' submission, approval and rejection==
* FAQ for developers: [[Publishing_to_JED|Publishing to JED]]

==Reviews==

===Why was my review of an extension is rejected, removed and/or edited?===
The following are some reasons why your review may have been rejected, removed or edited:
*Too short.
*Spam and/or self-promotion.
*Contains links.
*Feature requests. Send feature requests to the developer.
*Support requests. Send support requests to the developer.
*Bug reports. Send bug reports to the developer.
*Your review does not show that you used the extension.
*Not a review of the product.
*Contains code. The review section doesn't like code languages.
*Commercial disputes. Instead, report the extension.
*Complaints about licenses, download policies, and version compatibility.
*Violation of the Terms of Service.
*Duplicate accounts.

===I submitted a review yesterday but it is not shown yet, why?===
All reviews are being manually approved by the Editorial Team, and some submissions will be considered borderline and therefore gets a comment and awaits a second opinion from another editor. In some cases reviews can take up to 21 days to be processed.

===How can I change or delete a review that I submitted earlier?===
Please use the ‘Report this review’ button next to the review, and explain what changes you would like added or if you wish to have the review removed in order to be able to submit a new and updated review. By using the ‘Report this review’ we will be able to see that the request is made by the same user who originally created the review.

==Categorization==

===Can I suggest some changes to categorization?===
Categories in JED is constantly evolving to cope with the increasing amount of extensions. We strive to provide a good categorization to fit all extensions listed in JED. If you feel that an extension deserved to be in another existing or new category, please use the "Report This" button and let us know about your suggestion. You can also post your feedback to our forum.

==Directory==

===When is an extension considered ‘Popular’?===
Extension will be shown as ‘Hot’ when it has an average of 150 views or more per day.

===For how long is the tag ‘Just Added’ used?===
An extension will be tagged as ‘Just Added’ for 14 days from the days it is approved and published.

===What is the calculation for an extension to be ‘Top Rated’?===
An extension has to have at least 15 votes to be eligible to be listed as Top Rated Extension. Top Rated extensions are ordered by the average rating given by users.

===How is ‘Most Reviewed’ list calculated?===
Extensions with the highest number of reviews are listed in [http://extensions.joomla.org/extensions/most-reviewed Most Reviewed].

===When is an extension listed in ‘Recently Updated’ page?===
Extensions will be listed in [http://extensions.joomla.org/extensions/updated Recently Update] here when they are updated with new version.

===How are extensions selected to be shown in JED's front page?===
There are 4 main modules in JED's front page.

* '''''Random New Extensions''''' module randomly shows 12 extensions added in the past 4 weeks. All extensions added in this period have equal chance of appearing in the module.
* '''''New and Noteworthy''''' module shows 4 most viewed extensions added in the past 2 weeks. In another words, these are popular new extensions added in the past 2 weeks. Additionally, only listings that have uploaded image are considered in this module.
* '''''Recently Updated''''' module shows 12 most recently updated extensions in JED. Extensions are considered 'updated' when their version information is changed.
* '''''Random Extensions''''' module randomly shows 2 extensions with image.

===What component is used to manage Joomla! Extensions Directory?===
The directory component used at Joomla! Extensions Directory is (a customized version of) [http://extensions.joomla.org/extensions/233/details Mosets Tree] by a company called [http://www.mosets.com Mosets].

==The JED Team==
===Community Leadership Team Liaison===
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=106184 Sander Potjer]

===JED Team Manager===
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=456393 Matthew Baylor]

===JED Editors===
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=87230 Pierre Gazzola]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6515 P.Izidoro]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=29306 Nathan Gifford]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=246372 Andy Sharman]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=115421 Mustaq Sheikh]

===VEL/JSST/J!People Liaison===
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=28000 Claire Mandville]

===Technical Advisory===
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=79 Lee Cher Yeong]

===Contacting the team===
The editors can be reached by submitting a support ticket on the [http://extensions.joomla.org/component/maqmahelpdesk/ JED Help Desk]. Support is no longer provided via email.

<noinclude>[[Category:FAQ]][[Category:JED]]</noinclude>

Joomla! Extension Directory FAQs

2013-05-07T09:09:22Z

Nonumber:

{{RightTOC}}
==Extensions' submission, approval and rejection==
* FAQ for developers: [[Publishing_to_JED|Publishing to JED]]

==Reviews==

===Why was my review of an extension is rejected, removed and/or edited?===
The following are some reasons why your review may have been rejected, removed or edited:
*Too short.
*Spam and/or self-promotion.
*Contains links.
*Feature requests. Send feature requests to the developer.
*Support requests. Send support requests to the developer.
*Bug reports. Send bug reports to the developer.
*Your review does not show that you used the extension.
*Not a review of the product.
*Contains code. The review section doesn't like code languages.
*Commercial disputes. Instead, report the extension.
*Complaints about licenses, download policies, and version compatibility.
*Violation of the Terms of Service.
*Duplicate accounts.

===I submitted a review yesterday but it is not shown yet, why?===
All reviews are being manually approved by the Editorial Team, and some submissions will be considered borderline and therefore gets a comment and awaits a second opinion from another editor. In some cases reviews can take up to 21 days to be processed.

===How can I change or delete a review that I submitted earlier?===
Please use the ‘Report this review’ button next to the review, and explain what changes you would like added or if you wish to have the review removed in order to be able to submit a new and updated review. By using the ‘Report this review’ we will be able to see that the request is made by the same user who originally created the review.

==Categorization==

===Can I suggest some changes to categorization?===
Categories in JED is constantly evolving to cope with the increasing amount of extensions. We strive to provide a good categorization to fit all extensions listed in JED. If you feel that an extension deserved to be in another existing or new category, please use the "Report This" button and let us know about your suggestion. You can also post your feedback to our forum.

==Directory==

===When is an extension considered ‘Popular’?===
Extension will be shown as ‘Hot’ when it has an average of 150 views or more per day.

===For how long is the tag ‘Just Added’ used?===
An extension will be tagged as ‘Just Added’ for 14 days from the days it is approved and published.

===What is the calculation for an extension to be ‘Top Rated’?===
An extension has to have at least 15 votes to be eligible to be listed as Top Rated Extension. Top Rated extensions are ordered by the average rating given by users.

===How is ‘Most Reviewed’ list calculated?===
Extensions with the highest number of reviews are listed in [http://extensions.joomla.org/extensions/most-reviewed Most Reviewed].

===When is an extension listed in ‘Recently Updated’ page?===
Extensions will be listed in [http://extensions.joomla.org/extensions/updated Recently Update] here when they are updated with new version.

===How are extensions selected to be shown in JED's front page?===
There are 4 main modules in JED's front page.

* '''''Random New Extensions''''' module randomly shows 12 extensions added in the past 4 weeks. All extensions added in this period have equal chance of appearing in the module.
* '''''New and Noteworthy''''' module shows 4 most viewed extensions added in the past 2 weeks. In another words, these are popular new extensions added in the past 2 weeks. Additionally, only listings that have uploaded image are considered in this module.
* '''''Recently Updated''''' module shows 12 most recently updated extensions in JED. Extensions are considered 'updated' when their version information is changed.
* '''''Random Extensions''''' module randomly shows 2 extensions with image.

===What component is used to manage Joomla! Extensions Directory?===
The directory component used at Joomla! Extensions Directory is [http://extensions.joomla.org/extensions/233/details Mosets Tree] by a company called [http://www.mosets.com Mosets].

==The JED Team==
===Community Leadership Team Liaison===
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=106184 Sander Potjer]

===JED Team Manager===
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=456393 Matthew Baylor]

===JED Editors===
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=87230 Pierre Gazzola]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=6515 P.Izidoro]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=29306 Nathan Gifford]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=246372 Andy Sharman]
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=115421 Mustaq Sheikh]

===VEL/JSST/J!People Liaison===
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=28000 Claire Mandville]

===Technical Advisory===
* [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=79 Lee Cher Yeong]

===Contacting the team===
The editors can be reached by submitting a support ticket on the [http://extensions.joomla.org/component/maqmahelpdesk/ JED Help Desk]. Support is no longer provided via email.

<noinclude>[[Category:FAQ]][[Category:JED]]</noinclude>

Note form field type

2013-04-22T14:16:44Z

Nonumber: /* Title and or Description */

{{version|3.1}}
This form field makes it possible to create titles, texts, descriptions and even alert boxes. It also allows you to bring order in the settings for extensions, by separating them with useful titles. Or adding descriptions for certain settings (without having to rely on the tooltips). Or adding any other text you want.

The syntax is pretty straight-forward:
<source lang="php">
<field name="..." type="note" label="..." description="..." class="..." close="..." />
</source>

==Attributes==
*''Name:'' contains the name of the field (like with any other field tag)
*''Type:'' the type of the field, which is: note
*''Label:'' the title of the note (uses JText) (optional if using description)
*''Description:'' the description/text of the note (uses JText) (optional if using label)
*''Heading:'' the type of heading element to use for the label (optional) (default: h4)
*''Class:'' a class name (or class names), like alert (see further for examples) (optional)
*''Close:'' a value of 'true' (for alerts) or the value for the data-dismiss of the bootstrap close icon (optional)

==Title and or Description==
In the following code examples we will use these example language strings:
<source>
LOREMIPSUM="Lorem ipsum dolor sit amet"
LOREMIPSUM_DESC="Consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat."
</source>

So with this note field you can either use the title or the description or both.

<source lang="php">
<field name="opt10" type="text" label="Some Other Option" />
<field name="note11" type="note" label="LOREMIPSUM" />
<field name="opt11" type="text" label="Some Other Option" />
<field name="note12" type="note" description="LOREMIPSUM_DESC" />
<field name="opt12" type="text" label="Some Other Option" />
<field name="note13" type="note" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt13" type="text" label="Some Other Option" />
</source>

[[Image:Help25-note-form-field-title-screenshot.png]]

==Classes (Alerts)==
You can add classes to the note. This way you can make (bootstrap) alerts very easily. But also any other styling via class names you want (like a 'well').

<source lang="php">
<field name="opt20" type="text" label="Some Other Option" />
<field name="note21" type="note" class="alert" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt21" type="text" label="Some Other Option" />
<field name="note22" type="note" class="alert alert-info" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt22" type="text" label="Some Other Option" />
<field name="note23" type="note" class="alert alert-success" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt23" type="text" label="Some Other Option" />
<field name="note24" type="note" class="alert alert-error" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt24" type="text" label="Some Other Option" />
</source>

[[Image:Help25-note-form-field-classes-screenshot.png]]

==Close button==
A close button can be added to the alerts by adding the close="true" attribute to the tag. If you use a different class than the alert, use the required value for the data-dismiss of the bootstrap close icon instead of the value "true". But here is the code to test the close icon on an alert.

<source lang="php">
<field name="opt30" type="text" label="Some Other Option" />
<field name="note31" type="note" class="alert" close="true" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt31" type="text" label="Some Other Option" />
</source>

[[Image:Help25-note-form-field-close-screenshot.png]]

<noinclude>

== See also ==
* [[Standard form field types|List of standard form field types]]
[[Category:Standard form field types]]</noinclude>

Note form field type

2013-04-22T14:16:00Z

Nonumber: /* Close button */

{{version|3.1}}
This form field makes it possible to create titles, texts, descriptions and even alert boxes. It also allows you to bring order in the settings for extensions, by separating them with useful titles. Or adding descriptions for certain settings (without having to rely on the tooltips). Or adding any other text you want.

The syntax is pretty straight-forward:
<source lang="php">
<field name="..." type="note" label="..." description="..." class="..." close="..." />
</source>

==Attributes==
*''Name:'' contains the name of the field (like with any other field tag)
*''Type:'' the type of the field, which is: note
*''Label:'' the title of the note (uses JText) (optional if using description)
*''Description:'' the description/text of the note (uses JText) (optional if using label)
*''Heading:'' the type of heading element to use for the label (optional) (default: h4)
*''Class:'' a class name (or class names), like alert (see further for examples) (optional)
*''Close:'' a value of 'true' (for alerts) or the value for the data-dismiss of the bootstrap close icon (optional)

==Title and or Description==
In the following code examples we will use these example language strings:
<source>
LOREMIPSUM="Lorem ipsum dolor sit amet"
LOREMIPSUM_DESC="Consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt."
</source>

So with this note field you can either use the title or the description or both.

<source lang="php">
<field name="opt10" type="text" label="Some Other Option" />
<field name="note11" type="note" label="LOREMIPSUM" />
<field name="opt11" type="text" label="Some Other Option" />
<field name="note12" type="note" description="LOREMIPSUM_DESC" />
<field name="opt12" type="text" label="Some Other Option" />
<field name="note13" type="note" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt13" type="text" label="Some Other Option" />
</source>

[[Image:Help25-note-form-field-title-screenshot.png]]

==Classes (Alerts)==
You can add classes to the note. This way you can make (bootstrap) alerts very easily. But also any other styling via class names you want (like a 'well').

<source lang="php">
<field name="opt20" type="text" label="Some Other Option" />
<field name="note21" type="note" class="alert" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt21" type="text" label="Some Other Option" />
<field name="note22" type="note" class="alert alert-info" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt22" type="text" label="Some Other Option" />
<field name="note23" type="note" class="alert alert-success" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt23" type="text" label="Some Other Option" />
<field name="note24" type="note" class="alert alert-error" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt24" type="text" label="Some Other Option" />
</source>

[[Image:Help25-note-form-field-classes-screenshot.png]]

==Close button==
A close button can be added to the alerts by adding the close="true" attribute to the tag. If you use a different class than the alert, use the required value for the data-dismiss of the bootstrap close icon instead of the value "true". But here is the code to test the close icon on an alert.

<source lang="php">
<field name="opt30" type="text" label="Some Other Option" />
<field name="note31" type="note" class="alert" close="true" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt31" type="text" label="Some Other Option" />
</source>

[[Image:Help25-note-form-field-close-screenshot.png]]

<noinclude>

== See also ==
* [[Standard form field types|List of standard form field types]]
[[Category:Standard form field types]]</noinclude>

Note form field type

2013-04-22T14:15:39Z

Nonumber: /* Classes (Alerts) */

{{version|3.1}}
This form field makes it possible to create titles, texts, descriptions and even alert boxes. It also allows you to bring order in the settings for extensions, by separating them with useful titles. Or adding descriptions for certain settings (without having to rely on the tooltips). Or adding any other text you want.

The syntax is pretty straight-forward:
<source lang="php">
<field name="..." type="note" label="..." description="..." class="..." close="..." />
</source>

==Attributes==
*''Name:'' contains the name of the field (like with any other field tag)
*''Type:'' the type of the field, which is: note
*''Label:'' the title of the note (uses JText) (optional if using description)
*''Description:'' the description/text of the note (uses JText) (optional if using label)
*''Heading:'' the type of heading element to use for the label (optional) (default: h4)
*''Class:'' a class name (or class names), like alert (see further for examples) (optional)
*''Close:'' a value of 'true' (for alerts) or the value for the data-dismiss of the bootstrap close icon (optional)

==Title and or Description==
In the following code examples we will use these example language strings:
<source>
LOREMIPSUM="Lorem ipsum dolor sit amet"
LOREMIPSUM_DESC="Consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt."
</source>

So with this note field you can either use the title or the description or both.

<source lang="php">
<field name="opt10" type="text" label="Some Other Option" />
<field name="note11" type="note" label="LOREMIPSUM" />
<field name="opt11" type="text" label="Some Other Option" />
<field name="note12" type="note" description="LOREMIPSUM_DESC" />
<field name="opt12" type="text" label="Some Other Option" />
<field name="note13" type="note" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt13" type="text" label="Some Other Option" />
</source>

[[Image:Help25-note-form-field-title-screenshot.png]]

==Classes (Alerts)==
You can add classes to the note. This way you can make (bootstrap) alerts very easily. But also any other styling via class names you want (like a 'well').

<source lang="php">
<field name="opt20" type="text" label="Some Other Option" />
<field name="note21" type="note" class="alert" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt21" type="text" label="Some Other Option" />
<field name="note22" type="note" class="alert alert-info" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt22" type="text" label="Some Other Option" />
<field name="note23" type="note" class="alert alert-success" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt23" type="text" label="Some Other Option" />
<field name="note24" type="note" class="alert alert-error" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt24" type="text" label="Some Other Option" />
</source>

[[Image:Help25-note-form-field-classes-screenshot.png]]

==Close button==
A close button can be added to the alerts by adding the close="true" attribute to the tag. If you use a different class than the alert, use the required value for the data-dismiss of the bootstrap close icon instead of the value "true". But here is the code to test the close icon on an alert.

<source lang="php">
<field name="opt30" type="text" label="Some Other Option" />
<field name="note31" type="note" class="alert" close="true" label="Lorem ipsum dolor sit amet" description="Consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat." />
<field name="opt31" type="text" label="Some Other Option" />
</source>

[[Image:Help25-note-form-field-close-screenshot.png]]

<noinclude>
== See also ==
* [[Standard form field types|List of standard form field types]]
[[Category:Standard form field types]]</noinclude>

Note form field type

2013-04-22T14:14:30Z

Nonumber: /* Title and or Description */

{{version|3.1}}
This form field makes it possible to create titles, texts, descriptions and even alert boxes. It also allows you to bring order in the settings for extensions, by separating them with useful titles. Or adding descriptions for certain settings (without having to rely on the tooltips). Or adding any other text you want.

The syntax is pretty straight-forward:
<source lang="php">
<field name="..." type="note" label="..." description="..." class="..." close="..." />
</source>

==Attributes==
*''Name:'' contains the name of the field (like with any other field tag)
*''Type:'' the type of the field, which is: note
*''Label:'' the title of the note (uses JText) (optional if using description)
*''Description:'' the description/text of the note (uses JText) (optional if using label)
*''Heading:'' the type of heading element to use for the label (optional) (default: h4)
*''Class:'' a class name (or class names), like alert (see further for examples) (optional)
*''Close:'' a value of 'true' (for alerts) or the value for the data-dismiss of the bootstrap close icon (optional)

==Title and or Description==
In the following code examples we will use these example language strings:
<source>
LOREMIPSUM="Lorem ipsum dolor sit amet"
LOREMIPSUM_DESC="Consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt."
</source>

So with this note field you can either use the title or the description or both.

<source lang="php">
<field name="opt10" type="text" label="Some Other Option" />
<field name="note11" type="note" label="LOREMIPSUM" />
<field name="opt11" type="text" label="Some Other Option" />
<field name="note12" type="note" description="LOREMIPSUM_DESC" />
<field name="opt12" type="text" label="Some Other Option" />
<field name="note13" type="note" label="LOREMIPSUM" description="LOREMIPSUM_DESC" />
<field name="opt13" type="text" label="Some Other Option" />
</source>

[[Image:Help25-note-form-field-title-screenshot.png]]

==Classes (Alerts)==
You can add classes to the note. This way you can make (bootstrap) alerts very easily. But also any other styling via class names you want (like a 'well').

<source lang="php">
<field name="opt20" type="text" label="Some Other Option" />
<field name="note21" type="note" class="alert" label="Lorem ipsum dolor sit amet" description="Consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat." />
<field name="opt21" type="text" label="Some Other Option" />
<field name="note22" type="note" class="alert alert-info" label="Lorem ipsum dolor sit amet" description="Consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat." />
<field name="opt22" type="text" label="Some Other Option" />
<field name="note23" type="note" class="alert alert-success" label="Lorem ipsum dolor sit amet" description="Consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat." />
<field name="opt23" type="text" label="Some Other Option" />
<field name="note24" type="note" class="alert alert-error" label="Lorem ipsum dolor sit amet" description="Consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat." />
<field name="opt24" type="text" label="Some Other Option" />
</source>

[[Image:Help25-note-form-field-classes-screenshot.png]]

==Close button==
A close button can be added to the alerts by adding the close="true" attribute to the tag. If you use a different class than the alert, use the required value for the data-dismiss of the bootstrap close icon instead of the value "true". But here is the code to test the close icon on an alert.

<source lang="php">
<field name="opt30" type="text" label="Some Other Option" />
<field name="note31" type="note" class="alert" close="true" label="Lorem ipsum dolor sit amet" description="Consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat." />
<field name="opt31" type="text" label="Some Other Option" />
</source>

[[Image:Help25-note-form-field-close-screenshot.png]]

<noinclude>
== See also ==
* [[Standard form field types|List of standard form field types]]
[[Category:Standard form field types]]</noinclude>

Why is my site broken after upgrading

2010-05-08T10:03:01Z

Nonumber:

In Joomla 1.5.16 & 1.5.17 there is a feature that checks plugins for errors.
http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=19859

If a plugin causes some error, it gets unpublished. But a certain plugin might give an error during the actual upgrade (because the file hasn't been copied fully via ftp yet) or during a server hickup.
This can cause the unpublishing of vital plugins (like the SEF plugin).

So the solution is to go into your Plugin Manager and republish the plugins that need to be published.
If some plugins are unpublish that cause you to not be able to login to your administrator, you can republish the necessary plugins via your database manager (like phpMyAdmin). Only do that if you know what you are doing...

PS: Of course it is advised to always make a backup of your site (files and database) before upgrading. And to set your site to Offline Mode (via Global Configuration) during the actual upgrade.
[[Category:Version 1.5.17 FAQ]]

Why is my site broken after upgrading

2010-05-08T10:01:45Z

Nonumber:

In Joomla 1.5.16 & 1.5.17 there is a feature that checks plugins for errors.
http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=19859

If a plugin causes some error, it gets unpublished. But a certain plugin might give an error during the actual upgrade (because the file hasn't been copied fully via ftp yet) or during a server hickup.
This can cause the unpublishing of vital plugins (like the SEF plugin).

So the solution is to go into your Plugin Manager and republish the plugins that need to be published.
If some plugins are unpublish that cause you to not be able to login to your administrator, you can republish the necessary plugins via your database manager (like phpMyAdmin). Only do that if you know what you are doing...

PS: Of course it is advised to always make a backup of your site (files and database) before upgrading. And to set your site in Offline Mode (via Global Configuration) during the actual upgrade.
[[Category:Version 1.5.17 FAQ]]

Why is my site broken after upgrading

2010-05-08T08:58:08Z

Nonumber: 16