The repeatable custom field is the most loved and used in Joomla 3.X, in the alpha versions of Joomla 4 it seemed that they were going to keep it, but in the beta version it is no longer there and it was replaced by subfield.
Do you plan to reintegrate the repeatble custom field? Is there a way to migrate these fields to the new subfield?
Currently doing a migration this gives an error.
The repeating field should work.
It is not possible to create articles, and it shows errors in the section of custom fields
Warning: Declaration of PlgFieldsRepeatable::onCustomFieldsPrepareDom($field, DOMElement $parent, JForm $form) should be compatible with Joomla\Component\Fields\Administrator\Plugin\FieldsPlugin::onCustomFieldsPrepareDom($field, DOMElement $parent, Joomla\CMS\Form\Form $form)
When the repeatable field was checked in Joomla 3.10 alpha, it was working fine. The problem is in Joomla 4.0 beta3. so it is necessary to know what will happen with this. Thank you
Labels |
Added:
?
|
Hello i didnt find any Doc about migration to subfield some link ?
Well the intention is that this migration is done on upgrade as mention in the PR linked above. I did not had time to check what goes wrong on upgrade that this does not happen.
Labels |
Added:
?
|
Title |
|
@Hackwar @wilsonge to me it looks like a migration fail higher in the execution, that affects/prevents the repeatable fields update to complete. I will run a few more passes on this to check until where we have the execution stack of the migration working as expected. Here is the path I have been going about five times now already...
Fixed the fatal on upgrade. Now the field migrates to a subform field - and other articles can correctly create data. However the existing 3.x data doesn't get upgraded - which requires fixing still (hence this remains open)
Thanks for this update, was waiting for this fix on the upgrade path, will now take a closer look at this.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-03-08 11:01:53 |
Closed_By | ⇒ | chmst |
Closing as we have a PR.
Labels |
Removed:
?
|
hmm on upgrade that field should be uninstalled and convert to the subform field: #28319
So it seems that migration did not happen for some reason to be investigated.