Editor type field requires a data lenght and doesn't save (only on first attempt) #546

New Issue

Closed

opened 2020-04-30 18:37:53 +00:00 by jcodewalker · 5 comments

jcodewalker commented

2020-04-30 18:37:53 +00:00

(Migrated from github.com)

Steps to reproduce the issue

Set a new editor field. First attempt to save fails with a warning message: Field required: Data Length (bat the data lenght was set, obviously) and all field setting are lost. On second attempt the field is saved succesfully.

Expected result

Actual result

System information (as much as possible)

OS Name & Version:
MySql Version:
Apache Version:
PHP Version:
Joomla Version: 3.9.18
JCB Version: 2.9.13
Browser:

Additional comments

### Steps to reproduce the issue Set a new editor field. First attempt to save fails with a warning message: Field required: Data Length (bat the data lenght was set, obviously) and all field setting are lost. On second attempt the field is saved succesfully. ### Expected result ### Actual result ### System information (as much as possible) - OS Name & Version: - MySql Version: - Apache Version: - PHP Version: - Joomla Version: 3.9.18 - JCB Version: 2.9.13 - Browser: ### Additional comments

Llewellyn commented

2020-05-02 12:37:22 +00:00

I know about this issue, been trying to fix it a number of times. There is just to many JavaScript conflict on this page, and as you may know JavaScript is not my favorite of languages. So any help with this would be great!

jcodewalker commented

2020-05-02 13:05:23 +00:00

(Migrated from github.com)

Humm, I'm not so expert myself, but please give me an hint on where it is being processed (which files I have to look in at least)

jcodewalker commented

2020-05-03 16:35:49 +00:00

(Migrated from github.com)

Hello,
I think the solution is to set default value to 0 (zero) for datalenght in field.xml file, row #287 .

field.js works fine and actually the form is posted when all data are correct, so the issue comes from legacy model which compare the data with the form.
Since all the rules are managed by field.js file this solution shouldn't affect (I did some test but obviously can't test all the combinations) other field setting.

Hello, I think the solution is to set default value to 0 (zero) for datalenght in field.xml file, row #287 . field.js works fine and actually the form is posted when all data are correct, so the issue comes from legacy model which compare the data with the form. Since all the rules are managed by field.js file this solution shouldn't affect (I did some test but obviously can't test all the combinations) other field setting.

jcodewalker commented

2020-07-09 07:31:19 +00:00

(Migrated from github.com)

This bug is still there in version 2.11.2.
This bug affects both Editor and Calendar (as far as I know) fields type.

On every update I have to re-set this change. Is it possible to have it fixed? I work with this change since May and everything is fine.
file: administrator/components/component_builder/models/forms/field.xml
row: 287
change: default="">
to: default="0">

Thank you.

This bug is still there in version 2.11.2. This bug affects both Editor and Calendar (as far as I know) fields type. On every update I have to re-set this change. Is it possible to have it fixed? I work with this change since May and everything is fine. file: administrator/components/component_builder/models/forms/field.xml row: 287 change: default=""> to: default="0"> Thank you. ![Schermata 2020-07-09 alle 09 28 48](https://user-images.githubusercontent.com/49115855/87010478-e7828f00-c1c6-11ea-88b6-0db1f3b4c787.png)

Llewellyn commented

2020-12-08 23:11:36 +00:00

I have encountered this issue a few times, and as yet have not been able to fix it, it is indeed a Javascript issue.