Releases: enonic/app-metafields
v1.12.1
v1.12.0
v1.11.1
v1.11.0
v1.10.0
Changelog
There have been no changes to the project after v1.9.0.
v1.9.0
Changelog
There have been no changes to the project after v1.9.0.
Title fixes
Handle nested userDefinedPaths and non strings when overriding title.
Usability improvements
With the introduction and support for help texts inside Content Studio in Enonic XP we now have the ability to assist web editors customising the app for their needs. All fields used in the app now comes with helpful texts explaining what is needed to fill it in properly. We've also updated the settings with some default values (most commonly used settings activated out-of-the-box) and some simple validation of fields that requires specific formats.
At the same time we took the chance to restructure and reorganise most settings into more logical groups. And the labels for all fields have all been improved. Any change affecting the documentation is also updated in the main readme-file, making it easier to understand.
All-in-all this update greatly improves the usability of the app.
Full change log:
- Greatly improved usability of app by adding help texts to all the fields.
- Changed the overall structure of settings for the app. Now with more logical groups (field sets).
- Gave multiple labels improved names, making it more obvious what they do.
- Improved documentation.
- Regex force Twitter username to always begin with the @ symbol.
- Added default settings for frontpage behaviour, it now starts as checked.
- Setting for "Append site name to title" now starts out as checked.
- Added "-" as the default page-site title separator.
1.3 released - Twitter Cards, Canonical
With this version we introduce generation of Twitter Cards meta data, and Canonical meta data. Both are controlled with two new settings on the app, added in the "Other" section at the bottom of app config. Use the checkbox to activate canonical meta generation, default is off. Add a Twitter username (starting with the @ symbol) to activate Twitter Cards meta.
Two more powerful features to improve your SEO.
Recommended update
This update fixes multiple unknown bugs with the app settings for defining your own content data to search for. A user can add a string of extra fields with JSON-paths to prioritize when generating meta fields. However, multiple issues where found:
- Adding just one field would not work.
- Adding multiple fields worked, but not if there where any space characters inside the field.
- User-definitions for meta description never worked (the code was checking the wrong JSON-path).
We also made some minor updates to the readme and discovered some errors in how the waterfall logic was explained. This is fixed, and we now also mention specifically what happens to the waterfall logic if it finds no title or description (since this is handled differently).
We also noticed that content displayName took precedence over user-defined paths for titles meta. This is not optimal, so it is now reversed. Any user-defined content fields will be used first, if none of them are defined (or found) we will try to use content displayName.
Please don't use any older versions if you are dependent on defining your own JSON-paths for description or titles.