This repository has been archived by the owner on Mar 1, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
145 changed files
with
688 additions
and
1,018 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,355 +1,3 @@ | ||
| #  FormZ - Changelog | ||
|
|
||
| 1.1.1 - 2017-06-12 | ||
| ------------------ | ||
|
|
||
| Contains two bug-fixes: | ||
|
|
||
| - **[[e225096](https://github.com/romm/formz/commit/e2250962f9ae92b5fa00876217e59d7f6a649f7a)] [BUGFIX] Fix nested field layouts not properly rendered** | ||
|
|
||
| This commit allows several field layouts level: a field rendered with the field view helper can now render another field within its slots. | ||
|
|
||
| Example: | ||
|
|
||
| ``` | ||
| <fz:field name="foo"> | ||
| <fz:slot name="Field"> | ||
| Bacon ipsum dolor... | ||
| <fz:field name="bar"> | ||
| ... | ||
| </fz:field> | ||
| </fz:slot> | ||
| </fz:field> | ||
| ``` | ||
|
|
||
| - **[[7da753a](https://github.com/romm/formz/commit/7da753ac0e7115dc84a5a964884051ca5c91ca84)] [BUGFIX] Fix layout/partial root paths not merged in field layouts** | ||
|
|
||
| This commit fixes the situation where a slot in a field layout tries to use a partial from the actual rendering context: until now only the partials configured in the FormZ view TypoScript configuration were supported, resulting in a fatal error. | ||
|
|
||
| The paths are now merged together, giving access to both of them. | ||
|
|
||
| The same behaviour is done for layouts. | ||
|
|
||
| - **[[9be619c](https://github.com/romm/formz/commit/9be619cf5ebdf567404203aaa748a066d413cc05)] [TASK] Mark form validation data functions as deprecated** | ||
|
|
||
| 1.1.0 - 2017-04-08 | ||
| ------------------ | ||
|
|
||
| TYPO3 8.7 LTS is now officially supported! 馃帀 | ||
|
|
||
| Some bug fixes have been committed as well: | ||
|
|
||
| - **[[915ec9a](https://github.com/romm/formz/commit/915ec9aa8aa5b14c53819b80f1cf0c9e270a53fa)] [BUGFIX] Use slot rendering context instance to inject variables** | ||
|
|
||
| In some cases, injecting variables in the template variable container that was fetched from the controller context would not work. | ||
|
|
||
| This commit changes the way a slot controller context is stored, to solve this issue. | ||
|
|
||
| - **[[30b987f](https://github.com/romm/formz/commit/30b987faeeb7e3d2ec20d843a48a3a8afb1a3b27)] [BUGFIX] Use one view instance per layout** | ||
|
|
||
| When using fields with different templates, the source of the template file was not reloaded, causing issues. | ||
|
|
||
| Instead of using the same view instance everytime, they are stored in local cache based on their template file. | ||
|
|
||
| - **[[2141fc8](https://github.com/romm/formz/commit/2141fc87763745764d296976cffcd61797c32289)] [BUGFIX] Fix cHash issue in Ajax request URI** | ||
|
|
||
| Adding an argument forces the URI to calculate a cHash (it was not the case previously). Unfortunately, in TYPO3 8 the cHash is required in the request, and would cause a fatal error when it's missing. | ||
|
|
||
| This may be a temporary fix, as this is probably not the best way to do it. | ||
|
|
||
| 1.0.0 - 2017-03-23 | ||
| ------------------ | ||
|
|
||
| First stable version! 馃嵒 | ||
|
|
||
| After months of work on making the extension as reliable as possible (core refactoring, better architecture, hundreds of unit tests), the first stable version is finally out! | ||
|
|
||
| **Please note that major changes have been made since last beta version, you should check the breaking changes below (commits that begin with `[!!!]`).** | ||
|
|
||
| - **[[#48](https://github.com/romm/formz/pull/48)] [FEATURE] Handle `warning` and `notice` types in validation messages** | ||
|
|
||
| This commit adds a more reliable handling of the warning and notice message types in validation rules. | ||
|
|
||
| These messages wont block a validation (an error will), but can be used to deliver more information to the final user about actions done during the validation. | ||
|
|
||
| Ajax requests are supported. | ||
|
|
||
| - **[[#49](https://github.com/romm/formz/pull/49)] [!!!][TASK] Change fields TypoScript configuration `activation` keys** | ||
|
|
||
| For the fields activation configuration, the keys `items` and `condition` have been changed to `conditions` and `expression`. | ||
|
|
||
| This makes more sense for what these configuration actually do. | ||
|
|
||
| A depreciation message has been added to help converting old configuration to the new one. | ||
|
|
||
| - **[[#52](https://github.com/romm/formz/pull/52)] [!!!][TASK] Rename `section` to `slot`** | ||
|
|
||
| The decision has been taken to rename the two view helpers `formz:section` and `formz:renderSection` to `formz:slot` and `formz:slot.render`. | ||
|
|
||
| This helps to reduce the confusion with Extbase `f:section` and `f:render` view helpers. | ||
|
|
||
| The argument `section` of the view helper `renderSlot` has also been renamed to `slot`. | ||
|
|
||
| See examples below: | ||
|
|
||
| Old: | ||
| ``` | ||
| Template : | ||
| ---------- | ||
| <formz:field name="myField" ...> | ||
| <formz:section name="Field"> | ||
| <f:form.textField /> | ||
| </formz:section> | ||
| </formz:field> | ||
| Layout : | ||
| -------- | ||
| <fieldset> | ||
| <formz:renderSection section="Field" /> | ||
| </fieldset> | ||
| ``` | ||
|
|
||
| New: | ||
| ``` | ||
| Template : | ||
| ---------- | ||
| <formz:field name="myField" ...> | ||
| <formz:slot name="Field"> | ||
| <f:form.textField /> | ||
| </formz:slot> | ||
| </formz:field> | ||
| Layout : | ||
| -------- | ||
| <fieldset> | ||
| <formz:slot.render slot="Field" /> | ||
| </fieldset> | ||
| ``` | ||
|
|
||
| - **[[#53](https://github.com/romm/formz/pull/53)] [FEATURE] Introduce `slot.has` view helper** | ||
|
|
||
| This is a conditional view helper, used to check if a slot has been defined in a field template. It allows changing the HTML rendering depending on the presence of the slot. | ||
|
|
||
| **Example:** | ||
|
|
||
| ``` | ||
| <div class="container"> | ||
| <formz:slot.has slot="Image"> | ||
| <div class="image"> | ||
| <formz:slot.render slot="Image" /> | ||
| </div> | ||
| </formz:slot.has> | ||
| </div> | ||
| ``` | ||
|
|
||
| `<f:then>` and `<f:else>` work too! | ||
|
|
||
| ``` | ||
| <div class="container"> | ||
| <formz:slot.has slot="Image"> | ||
| <f:then> | ||
| <formz:slot.render slot="Image" /> | ||
| </f:then> | ||
| <f:else> | ||
| <img src="default-image.jpg" /> | ||
| </f:else> | ||
| </formz:slot.has> | ||
| </div> | ||
| ``` | ||
|
|
||
| - **[[#58](https://github.com/romm/formz/pull/58)] [!!!][TASK] Rename `formz` namespace to `fz`** | ||
|
|
||
| The decision has been taken to rename the namespace `formz` to `fz` in the contexts below. | ||
|
|
||
| The main reason is to improve readability: `fz` is far more ignorable by the eye than `formz` is. It also reduces the weight of the generated code. | ||
|
|
||
| - **JavaScript**: the global namespace `Formz` is now accessible with `Fz`. | ||
|
|
||
| Note that `Formz` is still accessible, but should be avoided. | ||
|
|
||
| **Example:** | ||
|
|
||
| ```javascript | ||
| Fz.Form.get(...) | ||
| ``` | ||
|
|
||
| - **CSS**: the entire list of data attributes that looked like `formz-*` are transformed to `fz-*`. This does affect generated CSS files. | ||
|
|
||
| **Example:** | ||
|
|
||
| ```css | ||
| form[fz-value-gender="male"] { | ||
| ... | ||
| } | ||
| ``` | ||
|
|
||
| - **Fluid**: the namespace `formz`, which was used in every template of the extension has been renamed to `fz`. | ||
|
|
||
| **Example:** | ||
|
|
||
| ```html | ||
| {namespace fz=Romm\Formz\ViewHelpers} | ||
|
|
||
| <fz:field name="Email"> | ||
| ... | ||
| </fz:field> | ||
| ``` | ||
|
|
||
| - **[[58b0fe0](https://github.com/romm/formz/commit/58b0fe09793a84eb7784fc2f401ccb11b281e45e)] [!!!][TASK] Remove method `onRequiredArgumentIsMissing`** | ||
|
|
||
| This method has nothing to do with the form API, and is entirely and only bound to controller behaviours. | ||
|
|
||
| If you need it, please paste the code in your own controller. | ||
|
|
||
| - **[[0f73599](https://github.com/romm/formz/commit/0f73599dad09d536568d767b3626ef47e660e048)] [!!!][TASK] Change form TypoScript configuration `activationCondition`** | ||
|
|
||
| The TypoScript configuration `activationCondition` has been renamed to `conditionList`. | ||
|
|
||
| This makes more sense for what this configuration actually do. | ||
|
|
||
| A depreciation message has been added to help converting old configuration to the new one. | ||
|
|
||
| - **[[e32f00c](https://github.com/romm/formz/commit/e32f00c5a0768070a084be17156f814d51ad342c)] [!!!][TASK] Rename `feedback` to `message`** | ||
|
|
||
| The old decision to use the word "feedback" for actual validation messages was a mistake that could lead to misunderstanding. Indeed, TYPO3 core uses the word "messages" everywhere for errors, warnings and notices, and never "feedback". | ||
|
|
||
| It has been decided to rename it before the stable version is out. | ||
|
|
||
| 0.4.1 - 2017-02-15 | ||
| ------------------ | ||
|
|
||
| TYPO3 version requirement changed from 8.5 to 8.6 (mistake from last version). | ||
|
|
||
| 0.4.0 - 2017-02-15 | ||
| ------------------ | ||
|
|
||
| Support for TYPO3 8.6 has been added. It means you should now be able to use FormZ with TYPO3 6.2/7.6/8.6! | ||
|
|
||
| ---- | ||
|
|
||
| - **[[#44](https://github.com/romm/formz/pull/44)] [FEATURE] Introduce TYPO3 8.6 support (#44)** | ||
|
|
||
| 0.3.3 - 2017-01-25 | ||
| ------------------ | ||
|
|
||
| This release fixes a PHP warning (which could be thrown as an exception) when working on TYPO3 >= 7.6.13. | ||
|
|
||
| ---- | ||
|
|
||
| - **[[5f119e1](https://github.com/romm/formz/commit/5f119e1be9b7510bd79378539ad02d7831cb0b15)] [TASK] Introduce legacy version of `FormViewHelper`** | ||
|
|
||
| 0.3.2 - 2017-01-24 | ||
| ------------------ | ||
|
|
||
| This release introduces partial backend support for FormZ, meaning you can use FormZ in any backend module. | ||
|
|
||
| The last remaining known issue is ajax calls, which wont work for now. | ||
|
|
||
| ---- | ||
|
|
||
| - **[[f2ca2b1](https://github.com/romm/formz/commit/f2ca2b19177ee2eae94e3daf6eef688191392b1d)] [TASK] Add new layout for TYPO3 backend (#40)** | ||
|
|
||
| **[[98f3a0f](https://github.com/romm/formz/commit/98f3a0fc4d2fdce36717994a783db398a94633a5)] [TASK] Improve assets inclusion to make it work in backend context (#38)** | ||
|
|
||
| **[[3cc9886](https://github.com/romm/formz/commit/3cc9886b05a26d524704f91b4f97d45d3501e01a)] [TASK] Add backend support for `TypoScriptUtility` (#36)** | ||
|
|
||
| 0.3.1 - 2017-01-05 | ||
| ------------------ | ||
|
|
||
| This release fixes two issues, updating is recommended. | ||
|
|
||
| ---- | ||
|
|
||
| - **[[a71a039](https://github.com/romm/formz/commit/a71a039ae4b56cf4f86cc428fc66e6312b1ddd52)] [BUGFIX] Delete required property for activation configuration** | ||
|
|
||
| The property `items` for activations (fields and conditions) was flagged as required, that is not true and has been removed. | ||
|
|
||
| - **[[55769f9](https://github.com/romm/formz/commit/55769f93eb6ce16d8a7544250181eea51b02874d)] [BUGFIX] Fix page renderer singleton issue** | ||
|
|
||
| The page renderer must be instantiated with `GeneralUtility::makeInstance()` instead of Extbase object manager (or with an inject function). | ||
|
|
||
| This is due to some TYPO3 low level behaviour which overrides the page renderer singleton instance, whenever a new request is used. The problem is that the instance is not updated on Extbase side. | ||
|
|
||
| Using Extbase injection can lead to old page renderer instance being used, resulting in a leak of assets inclusion, and maybe more issues. | ||
|
|
||
| 0.3.0 - 2016-12-10 | ||
| ------------------ | ||
|
|
||
| This release fixes two minor issues, and one major issue. Please update to this new version! | ||
|
|
||
| The road to full unit tests coverage continues. | ||
|
|
||
| ---- | ||
|
|
||
| - **[[45020d6](https://github.com/romm/formz/commit/45020d6e62ae2e30024188020b57d6dea8206d11)] [TASK] Introduce asset handler connectors** | ||
|
|
||
| Big refactoring of the asset handlers usage: connectors have been introduced, in order to split the several asset handlers usage. A whole tests suite has been written for these connectors. | ||
|
|
||
| A refactoring of the condition API has also been made, to help testing out some functionnality of the asset handler connectors, but also to resolve an issue that has been discovered during development (#28). | ||
|
|
||
| - **[[35528cf](https://github.com/romm/formz/commit/35528cf7a64501fccf091a86ffd3394e8d2a32dc)] [BUGFIX] Fix the js email validator regex (@Mopolo)** | ||
|
|
||
| - **[[e8c9a4b](https://github.com/romm/formz/commit/e8c9a4bd91261777587f6c16358a381e76b6daf4)] [BUGFIX] Fix double event issue for text inputs** | ||
|
|
||
| 0.2.0 - 2016-11-10 | ||
| ------------------ | ||
|
|
||
| This release fixes two severe issues (see below), it is **strongly recommended** to upgrade to this version. | ||
|
|
||
| A new condition type has also been introduced: `fieldIsEmpty`, which can be used to check whether a field has no value set. | ||
|
|
||
| A bunch of unit tests are also embedded in this version, making a step forward the first stable version, which will be released when the tests coverage reaches a correct rate. | ||
|
|
||
| ---- | ||
|
|
||
| **Major commits list:** | ||
|
|
||
| - **[[5849c42](https://github.com/romm/formz/commit/5849c4241946e673cf0895a1d2c2440eb697a0a3)] [FEATURE] Add new condition `fieldIsEmpty`** | ||
|
|
||
| Adding a new condition, with its own JavaScript connector. It is verified when a field has no value, but also when a multiple checkbox has no value checked. | ||
|
|
||
| - **[[3e70d83](https://github.com/romm/formz/commit/3e70d8364320a050c59699f66be6c0e8b2f9ce6f)] [BUGFIX] Fix wrong JavaScript call** | ||
|
|
||
| A JavaScript debug statement was using the `Debug` library directly, instead of the low-level `debug` function. | ||
|
|
||
| It could cause an error when the `Debug` library was not loaded (when the debug mode is not enabled in FormZ configuration). | ||
|
|
||
| - **[[#26](https://github.com/romm/formz/pull/26)] [BUGFIX] Fix persistent option in field ViewHelper** | ||
|
|
||
| When using the ViewHelper `<fz:option>` inside `<fz:field>`, the option would not be deleted after the whole field is processed, resulting in unwanted options in later fields, which could cause pretty ugly behaviours. | ||
|
|
||
| For instance, a field could be flagged as required even if it is not. | ||
|
|
||
| In the following example, the option `required` would have been present for the field `bar` (it is now fixed by this commit). | ||
|
|
||
| ``` | ||
| <fz:field name="foo"> | ||
| <fz:option name="required" value="1" /> | ||
| [...] | ||
| </fz:field> | ||
| <fz:field name="bar"> | ||
| [...] | ||
| </fz:field> | ||
| ``` | ||
|
|
||
| 0.1.1 - 2016-10-10 | ||
| ------------------ | ||
|
|
||
| - **[[#1](https://github.com/romm/formz/pull/1)] [TASK] Implement Travis & Coveralls integration** | ||
|
|
||
| A continuous integration is now up and running on the Git repository. | ||
|
|
||
| Unit tests are being written. | ||
|
|
||
| ----- | ||
|
|
||
| - **[[#5](https://github.com/romm/formz/pull/5)] [DOC] Fix typos in the chapter 5** | ||
| - **[[#7](https://github.com/romm/formz/pull/7)] [DOC] Fix typos in the chapter 6** | ||
| - **[[#10](https://github.com/romm/formz/pull/10)] [DOC] Fix typos in the chapter 7** | ||
| - **[[#11](https://github.com/romm/formz/pull/11)] [DOC] Fix typos in the chapter 8** | ||
| - **[[#12](https://github.com/romm/formz/pull/12)] [DOC] fix typos in the readme file** | ||
|
|
||
| Many english mistakes were corrected in the documentation. Thanks to [@Mopolo](https://github.com/Mopolo) for his help! | ||
| You can find a detailed changelog at the [official FormZ documentation](https://docs.typo3.org/typo3cms/extensions/formz/11-Changelog/Index.html). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.