When i create an admin field relation and i set it to use custom code and i have two join fields, only one join field is added to the "set" field.
From my example image attached you can see it is missing House number suffix. Altho it is specified in the join fields.
Steps to reproduce the Bug
Create admin field relation, custom code, add more than one join field. see only one join field added to set field.
Which Joomla version are you compiling in?
6.0.3
Which PHP version are you compiling in?
8.3
Which Joomla versions are you targeting?
6
Which PHP version are you targeting?
8.3
Which Web server is JCB running on?
apache 2.4
Which Relational Database is JCB running on?
mariadb 10.x
Which OS is JCB running on?
centos 7
Which JCB version are you using?
6.1.5-beta1
Where in JCB did this issue occur?
Admin View(admin_view)
On which browsers did you encounter the issue?
Firefox
Additional Comments
No response
### What Happened?
When i create an admin field relation and i set it to use custom code and i have two join fields, only one join field is added to the "set" field.
From my example image attached you can see it is missing House number suffix. Altho it is specified in the join fields.
### Steps to reproduce the Bug
Create admin field relation, custom code, add more than one join field. see only one join field added to set field.
### Which Joomla version are you compiling in?
6.0.3
### Which PHP version are you compiling in?
8.3
### Which Joomla versions are you targeting?
6
### Which PHP version are you targeting?
8.3
### Which Web server is JCB running on?
apache 2.4
### Which Relational Database is JCB running on?
mariadb 10.x
### Which OS is JCB running on?
centos 7
### Which JCB version are you using?
6.1.5-beta1
### Where in JCB did this issue occur?
Admin View(admin_view)
### On which browsers did you encounter the issue?
Firefox
### Additional Comments
_No response_
Hi @TLWebdesign, Thank you for reporting this issue.
After reviewing and discussing it, we've now implemented a fix. Please try the latest release v6.1.5-beta2, which includes the changes addressing this bug.
Thanks again for taking the time to report and investigate this with us. We'd really appreciate it if you could test the update and let us know whether it resolves the problem on your side. If the fix works as expected, we'll go ahead and close the issue.
Looking forward to your feedback.
Hi @TLWebdesign, Thank you for reporting this issue.
After reviewing and discussing it, we've now implemented a fix. Please try the latest release [v6.1.5-beta2](https://github.com/joomengine/pkg-component-builder/archive/refs/heads/6.x.zip), which includes the changes addressing this bug.
Thanks again for taking the time to report and investigate this with us. We'd really appreciate it if you could test the update and let us know whether it resolves the problem on your side. If the fix works as expected, we'll go ahead and close the issue.
Looking forward to your feedback.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What Happened?
When i create an admin field relation and i set it to use custom code and i have two join fields, only one join field is added to the "set" field.
From my example image attached you can see it is missing House number suffix. Altho it is specified in the join fields.
Steps to reproduce the Bug
Create admin field relation, custom code, add more than one join field. see only one join field added to set field.
Which Joomla version are you compiling in?
6.0.3
Which PHP version are you compiling in?
8.3
Which Joomla versions are you targeting?
6
Which PHP version are you targeting?
8.3
Which Web server is JCB running on?
apache 2.4
Which Relational Database is JCB running on?
mariadb 10.x
Which OS is JCB running on?
centos 7
Which JCB version are you using?
6.1.5-beta1
Where in JCB did this issue occur?
Admin View(admin_view)
On which browsers did you encounter the issue?
Firefox
Additional Comments
No response
Hi @TLWebdesign, Thank you for reporting this issue.
After reviewing and discussing it, we've now implemented a fix. Please try the latest release v6.1.5-beta2, which includes the changes addressing this bug.
Thanks again for taking the time to report and investigate this with us. We'd really appreciate it if you could test the update and let us know whether it resolves the problem on your side. If the fix works as expected, we'll go ahead and close the issue.
Looking forward to your feedback.
Confirmed fixed thanks!