* Added images decoding spanish translation
* Improved class assignment for form fields in the plugin's default template
* Fixed extra field.classes added
* Added Syslog tag
---------
Co-authored-by: pmoreno.rodriguez <pmoreno.rodriguez@outlook.com>
* Added descriptioin option and icon help to list field
* Changed description by sublabel in the list field. Added label classes
* Changed description by sublabel in the list field. Added label classes
* Options to add description, sublabel and help to the list field.
* Added description, sublabel and icon help to field. Field classes are also added
* Removed duplicate description
* Add item at the top if top button is clicked in list field
Pretty much title says it all. IMO it makes much more sense, that top button would add item at the top, because if list is long enough, you are not even seeing if something happens when item is added at the bottom. Created this PR because of [the question asked in forum](https://discourse.getgrav.org/t/blueprint-type-list-new-data-on-top-of-array/15254).
So the solution would be either like this PR suggests, or button actions should be configurable via Admin config somewhere.
* Change added item placement for List field
Add field `palecement` property check.
If `top` or `bottom`, both buttons add item to top or bottom.
If `position`, item is added depending on a clicked button position -
if top button is clicked, item added to top and if bottom button - item added to bottom.
Defaults to bottom
* Revert empty line at EOF
* Fix collapsed noncollapsible list fields
The value of `field.collapsed` seems to be true even in the case of collapsible fields, making noncollapsible fields collapsed by default, with no way to expand them. According to a quick test I've done, this should fix that.
* Actually fix noncollapsible list fields
* Added Classes support to range form field
Simple change to add support to classes in blueprints added to range field in admin forms
* Minor bugfix for range slider
Without adding the validate here the only way to make the range slider work with a step, say 0.1 is to have `step: 0.1` both inside and outside the validate:
Example:
```
width:
type: range
step: 0.1
validate:
min: 0
max: 1
step: 0.1
```
* Adding classes support to list form field
Adds a new notifications feature to the Admin plugin. It will now lookup notifications which are set up on getgrav.org and will inform users, and also alert for new updates and provide awareness on various topics.
Also fixes issue with Array field in `value_only` mode, improperly displaying the key when novalue was set, and fixes issue with drag handlers in Array not showing/hiding properly (#950)
Updated FontAwesome to 4.6.3
@w00fz I partially reverted b7caab8677, I
tested and it works with the markdown editor too. What was the reason
you changed it?
The problem introduced was the `data-collection-template` element was
changed from <script> to <ul> and then the template item is picked up
as a list item in the list, with '*' as key, instead of being ignored.
