[BUG]: Error when deleting item within JCB #1227

New Issue

Closed

opened 2025-06-22 15:07:36 +00:00 by mwweb · 1 comment

mwweb commented

2025-06-22 15:07:36 +00:00

What Happened?

Deleted Admin View, then went to trash to permanently delete, and received error: A query must be a string or a Joomla\Database\QueryInterface instance, a NULL was given.

Steps to reproduce the Bug

Delete and item from within JCB, then in filters change to Trashed, and attempt to delete.

Which Joomla version are you compiling in?

5.3.1

Which PHP version are you compiling in?

8.2.24

Which Joomla versions are you targeting?

5.x

Which PHP version are you targeting?

8.2+

Which Web server is JCB running on?

Apache 2.4.62

Which Relational Database is JCB running on?

11.7.2-MariaDB-ubu2404

Which OS is JCB running on?

Ubuntu 24.04.2

Which JCB version are you using?

5.1.0

Where in JCB did this issue occur?

Other

On which browsers did you encounter the issue?

Firefox

Additional Comments

I'm using OctoJoom

### What Happened? Deleted Admin View, then went to trash to permanently delete, and received error: A query must be a string or a Joomla\Database\QueryInterface instance, a NULL was given. ### Steps to reproduce the Bug Delete and item from within JCB, then in filters change to Trashed, and attempt to delete. ### Which Joomla version are you compiling in? 5.3.1 ### Which PHP version are you compiling in? 8.2.24 ### Which Joomla versions are you targeting? 5.x ### Which PHP version are you targeting? 8.2+ ### Which Web server is JCB running on? Apache 2.4.62 ### Which Relational Database is JCB running on? 11.7.2-MariaDB-ubu2404 ### Which OS is JCB running on? Ubuntu 24.04.2 ### Which JCB version are you using? 5.1.0 ### Where in JCB did this issue occur? Other ### On which browsers did you encounter the issue? Firefox ### Additional Comments I'm using OctoJoom

mwweb added the

Bug

label 2025-06-22 15:07:36 +00:00

mwweb changed title from ~~[BUG]:~~ to [BUG]: Error when deleting item within JCB

2025-06-22 15:08:01 +00:00

Lemuel commented

2025-06-23 11:10:33 +00:00

Member

Hello @mwweb,
Thank you for raising this issue.

I’ve completed a round of testing to investigate the problem. Here’s what I did:

I set up a test JCB system on Joomla 5.3.0 and installed the JCB 5.1.0 package.
I was able to reproduce the issue related to deleting and emptying the trash.
I then updated to JCB 5.1.1 Beta 2, and the issue no longer occurred.

After updating:

The Demo Component compiled successfully.
The Empty Trash function worked as expected.

Note: I had deleted some admin views during my testing of the Empty Trash function. After re-initializing those views using the new packaging engine, the component still compiled without any issues.

We recommend updating to Beta 2 as it includes fixes for this issue. That said, please keep in mind that while it is a beta release, we actively use it for internal and testing, and it has proven to be quite stable. However, as with any beta version, it may still require broader testing, and individual experiences may vary.

Let us know if the update resolves the issue on your end. Once again, thank you for taking the time to test JCB - community feedback like yours plays a vital role in helping us identify and address edge cases as we prepare for stable releases.

Hello @mwweb, Thank you for raising this issue. I’ve completed a round of testing to investigate the problem. Here’s what I did: - I set up a test JCB system on Joomla 5.3.0 and installed the JCB 5.1.0 package. - I was able to reproduce the issue related to deleting and emptying the trash. - I then updated to JCB 5.1.1 Beta 2, and the issue no longer occurred. After updating: - The **Demo Component** compiled successfully. - The **Empty Trash** function worked as expected. Note: I had deleted some admin views during my testing of the Empty Trash function. After re-initializing those views using the new packaging engine, the component still compiled without any issues. We recommend updating to **Beta 2** as it includes fixes for this issue. That said, please keep in mind that while it is a beta release, we actively use it for internal and testing, and it has proven to be quite stable. However, as with any beta version, it may still require broader testing, and individual experiences may vary. Let us know if the update resolves the issue on your end. Once again, thank you for taking the time to test JCB - community feedback like yours plays a vital role in helping us identify and address edge cases as we prepare for stable releases.