You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are encountering an issue with the integration of BricksBuilder and JetEngine when using the Query Builder to display information related to a Custom Content Type (CCT) and associated users. Below is the scenario:
We have created a CCT called "Projects CCT", which includes, among other fields, the following:
custom_user_id: A field that stores the ID of an associated user.
responsible_user_id: Another field that stores the ID of another associated user.
In BricksBuilder (Query Loop):
We created a query using JetEngine's Query Builder to retrieve all records from the "Projects CCT". This query is displayed correctly as a set of cards.
Inside each card, we added additional queries (Query Loop):
A query of type Users that uses the custom_user_id field from the current CCT to retrieve data for the associated user. This query works correctly.
Another similar query of type Users that uses the responsible_user_id field from the current CCT to retrieve data for the associated user.
Issue Identified:
The second query (based on responsible_user_id) returns the user with the lowest ID in WordPress (in this case, user ID 1) instead of the correct user (which should be ID 20).
It seems that an error occurs in BricksBuilder, preventing the addition of more than one nested query inside an existing query when using the Query Builder with CCT and Users.
Test Performed:
When using a Listing Grid instead of BricksBuilder directly, the queries work correctly for both custom_user_id and responsible_user_id.
Steps to Reproduce the Issue:
Create a CCT with custom fields referencing user IDs (custom_user_id and responsible_user_id).
Configure a query in BricksBuilder using JetEngine's Query Builder to display all CCT records as a set of cards.
Within each card, configure additional Users queries:
One query using the custom_user_id field from the current CCT.
Another query using the responsible_user_id field from the current CCT.
Observe that the second query (based on responsible_user_id) returns incorrect data (the user with the lowest ID), while the first query works as expected.
Repeat the process using Listing Grid instead of BricksBuilder, and verify that both queries work correctly.
Impact:
It is not possible to nest more than one query in BricksBuilder, which limits the functionality of CCTs in scenarios requiring multiple user relationships.
This behavior suggests a limitation or bug in BricksBuilder when handling multiple nested queries within a CCT. We kindly request your assistance in identifying the cause and a possible solution.
Additional Note:
We have verified that when using a Listing Grid, nested queries work as expected, which confirms that the issue lies specifically with BricksBuilder.
If you need further details or access to the development environment, please let us know. @MjHead
The text was updated successfully, but these errors were encountered:
Problem Description:
We are encountering an issue with the integration of BricksBuilder and JetEngine when using the Query Builder to display information related to a Custom Content Type (CCT) and associated users. Below is the scenario:
We have created a CCT called "Projects CCT", which includes, among other fields, the following:
custom_user_id: A field that stores the ID of an associated user.
responsible_user_id: Another field that stores the ID of another associated user.
In BricksBuilder (Query Loop):
We created a query using JetEngine's Query Builder to retrieve all records from the "Projects CCT". This query is displayed correctly as a set of cards.
Inside each card, we added additional queries (Query Loop):
A query of type Users that uses the custom_user_id field from the current CCT to retrieve data for the associated user. This query works correctly.
Another similar query of type Users that uses the responsible_user_id field from the current CCT to retrieve data for the associated user.
Issue Identified:
The second query (based on responsible_user_id) returns the user with the lowest ID in WordPress (in this case, user ID 1) instead of the correct user (which should be ID 20).
It seems that an error occurs in BricksBuilder, preventing the addition of more than one nested query inside an existing query when using the Query Builder with CCT and Users.
Test Performed:
When using a Listing Grid instead of BricksBuilder directly, the queries work correctly for both custom_user_id and responsible_user_id.
Steps to Reproduce the Issue:
Create a CCT with custom fields referencing user IDs (custom_user_id and responsible_user_id).
Configure a query in BricksBuilder using JetEngine's Query Builder to display all CCT records as a set of cards.
Within each card, configure additional Users queries:
One query using the custom_user_id field from the current CCT.
Another query using the responsible_user_id field from the current CCT.
Observe that the second query (based on responsible_user_id) returns incorrect data (the user with the lowest ID), while the first query works as expected.
Repeat the process using Listing Grid instead of BricksBuilder, and verify that both queries work correctly.
Impact:
It is not possible to nest more than one query in BricksBuilder, which limits the functionality of CCTs in scenarios requiring multiple user relationships.
Software and Tools Versions Used:
JetEngine: Latest stable release (non-beta).
BricksBuilder: Latest stable release (non-beta).
WordPress: Latest stable release.
PHP: Latest stable release.
Conclusion:
This behavior suggests a limitation or bug in BricksBuilder when handling multiple nested queries within a CCT. We kindly request your assistance in identifying the cause and a possible solution.
Additional Note:
We have verified that when using a Listing Grid, nested queries work as expected, which confirms that the issue lies specifically with BricksBuilder.
If you need further details or access to the development environment, please let us know. @MjHead
The text was updated successfully, but these errors were encountered: