[BUG]: Uncaught TypeError: can't access property "length", property is null

remoover commented

2025-10-15 22:04:12 +00:00

What Happened?

Add new Property ... after selected eg getting error eg "type"

Steps to reproduce the Bug

Add new Property ... after selected eg getting error eg "type"

Uncaught TypeError: can't access property "length", property is null

Which Joomla version are you compiling in?

6

Which PHP version are you compiling in?

8.3

Which Joomla versions are you targeting?

6

Which PHP version are you targeting?

Which Web server is JCB running on?

apache

Which Relational Database is JCB running on?

mariadb 10x

Which OS is JCB running on?

ubuntu

Which JCB version are you using?

6.1.2

Where in JCB did this issue occur?

Dashboard(admin_view), Joomla Component(admin_view)

On which browsers did you encounter the issue?

Firefox, Chrome

Additional Comments

Editing the Field

administrator/index.php?option=com_componentbuilder&view=field&layout=edit&id=3738

### What Happened? Add new Property ... after selected eg getting error eg "type" ### Steps to reproduce the Bug Add new Property ... after selected eg getting error eg "type" Uncaught TypeError: can't access property "length", property is null ### Which Joomla version are you compiling in? 6 ### Which PHP version are you compiling in? 8.3 ### Which Joomla versions are you targeting? 6 ### Which PHP version are you targeting? 8. ### Which Web server is JCB running on? apache ### Which Relational Database is JCB running on? mariadb 10x ### Which OS is JCB running on? ubuntu ### Which JCB version are you using? 6.1.2 ### Where in JCB did this issue occur? Dashboard(admin_view), Joomla Component(admin_view) ### On which browsers did you encounter the issue? Firefox, Chrome ### Additional Comments Editing the Field administrator/index.php?option=com_componentbuilder&view=field&layout=edit&id=3738

remoover added the Bug label 2025-10-15 22:04:12 +00:00

Llewellyn commented

2025-10-15 22:06:04 +00:00

Owner

We do not see the same error, so we will need more information, like some screen shots and what exactly is the current field setup, since we don't see the same error, we need to try and reproduce it on our side. So give as as much as possible information.

remoover commented

2025-10-15 22:13:31 +00:00

Author

![obrázok.png](/attachments/f3c02531-92e6-452f-9b88-06bb3de0f3bb)

obrázok.png

142 KiB

remoover commented

2025-10-15 22:14:21 +00:00

Author

if u want i can provide you access to our website, you can try , test , that will be simplest

Llewellyn commented

2025-10-15 22:19:20 +00:00

Owner

Access to Our Website

We currently do not offer paid support at this time.

We'll investigate this issue further. Please note that JCB is not compatible with Chrome, so avoid using it during development.

Once we have more information, we'll update this thread.

In the meantime, please provide additional details about your field setup. Repeating the same error message alone doesn't give us enough context to diagnose the issue effectively.

> Access to Our Website We currently do not offer paid support at this time. We'll investigate this issue further. Please note that **JCB is not compatible with Chrome**, so avoid using it during development. Once we have more information, we'll update this thread. In the meantime, please provide additional details about your field setup. Repeating the same error message alone doesn't give us enough context to diagnose the issue effectively.

Lemuel commented

2025-10-15 22:24:49 +00:00

Owner

I can confirm that in J6 when adding a new property to a existing field it get the same issue. Additionally, creating a new field works but when I remove properties and then add them back the same issue occurs.

Llewellyn commented

2025-10-15 22:49:32 +00:00

Owner

@remoover It seems we missed this one — thank you for catching it! We really should have listened earlier. Now we’ve ended up with a stable release carrying a pretty big bug.

Not exactly the best outcome 😄

We'll get a bug fix out soon.

In the meantime, you can still edit the properties and add values manually. This issue only affects the automatic loading of the property descriptions; those are still available under the Type Info tab.

It won’t affect your component's functionality, so you can safely continue working by adding your values manually for now. Just make sure not to add the same property twice.

@remoover It seems we missed this one — thank you for catching it! We really should have listened earlier. Now we’ve ended up with a stable release carrying a pretty big bug. Not exactly the best outcome 😄 We'll get a bug fix out soon. In the meantime, you can still edit the properties and add values manually. This issue only affects the automatic loading of the property descriptions; those are still available under the **Type Info** tab. It won’t affect your component's functionality, so you can safely continue working by adding your values manually for now. Just make sure not to add the same property twice.