Problem with Help_Documents #1300
Closed
opened 2026-03-30 18:24:11 +00:00 by pctechnikch
·
2 comments
No Branch/Tag Specified
6.x
5.x
4.x
3.x
v6.2.0
v5.2.0
v4.2.0
v6.1.6
v5.1.6
v4.1.5
v6.1.5
v5.1.5
v4.1.4
v6.1.4
v5.1.4
v4.1.3
v6.1.3
v5.1.3
v6.1.2
v5.1.2
v4.1.2
v5.1.1
v4.1.1
v4.1.0
v3.2.5
v5.1.0
v5.0.3
v4.0.3
v3.2.4
v5.0.2
v4.0.2
v3.2.3
v5.0.1
v4.0.1
v3.2.2
v5.0.0
v4.0.0
v3.2.1
v3.2.0
v3.1.28
v3.1.27
v3.1.26
v3.1.24
v3.1.19
v3.1.17
v3.1.15
v3.1.12
v3.1.11
v3.1.10
v3.1.9
v3.1.8
v3.1.7
v3.1.6
v3.1.5
v3.1.4
v3.1.3
v3.1.2
v2.13.1
v2.13.0
v2.12.16
v2.12.15
v2.12.14
v2.12.10
v2.12.9
v2.12.8
v2.12.7
v2.12.6
v2.12.4
v2.12.3
v2.12.2
v2.11.7
v2.11.4
v2.11.3
v2.11.2
v2.11.0
v2.10.13
v2.10.11
v2.10.9
v2.10.5
v2.10.1
v2.10.0
v2.9.21
v2.9.18
v2.9.14
v2.9.11
v2.9.10
v2.9.8
v2.9.7
v2.9.1
v2.9.0
v2.8.5
v2.8.4
v2.8.2
v2.8.0
v2.7.10
v2.7.7
v2.7.6
v2.7.5
v2.7.4
v2.7.1
v2.7.0
v2.6.17
v2.6.16
v2.6.15
v2.6.14
v2.6.13
v2.6.12
v2.6.11
v2.6.10
v2.6.9
v2.6.8
v2.6.7
v2.6.6
v2.6.5
v2.6.3
v2.6.2
v2.6.1
v2.6.0
v2.5.8
v2.5.6
v2.5.5
v2.5.4
v2.5.1
v2.5.0
v2.4.10
v2.4.9
v2.4.8
v2.4.7
v2.4.6
v2.4.5
v2.4.4
v2.4.3
v2.4.2
v2.4.1
v2.4.0
v2.3.10
v2.3.9
v2.3.8
v2.3.7
v2.3.6
v2.3.5
v2.3.4
v2.3.2
v2.3.1
v2.3.0
v2.2.10
v2.2.9
v2.2.6
v2.2.5
v2.2.4
v2.2.3
v2.2.2
v2.2.0
v2.1.21
v2.1.20
v2.1.19
v2.1.18
v2.1.17
v2.1.16
v2.1.14
v2.1.13
v2.1.12
v2.1.11
v2.1.10
v2.1.9
v2.1.8
v2.1.7
v2.1.6
v2.1.5
v2.1.4
v2.1.3
v2.1.2
v2.1.1
v2.1.0
v2.0.9
v2.0.8
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: joomla/Component-Builder#1300
Reference in new issue
Block a user
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.
Steps to reproduce the issue
Hello
I'm really excited about the new version of JCB. I've been tasked with migrating a client's project from JCB V3 to V6. Version 3 had the Help_Document function. I've seen that this code is also included in JCB V6, so I have everything I need. The single view displays correctly. Unfortunately, saving causes an error "Incorrect integer value! What's wrong? Is it my MySQL or the new MariaDB version, or am I missing something? I also need to know where I can insert the
use Joomla\Filesystem\Folder;statement in the header for custom fields.Expected result
Actual result
Error
[],site_view,url' for column 'not_required' at row 1System information (as much as possible)
Additional comments
It would be fantastic if we could find a solution. I would be happy with inline help, but as they say, this is how it's requested.
Thanks René
Hi, thanks for reaching out and for the detailed description of the issue.
From what you've described, this looks very likely to be related to a legacy database structure carried over from Joomla 3, rather than something directly caused by JCB itself.
In Joomla 3, there were cases where a
not_requiredcolumn existed in certain tables. During migration to newer Joomla versions (like Joomla 6), this column is no longer expected, and its presence can lead to errors such as:I encountered a very similar issue on a migrated system. In that case, simply removing the
not_requiredcolumn from the relevant help document table resolved the problem completely. The column didn't appear to be used anywhere in the current system, and once removed, saving worked as expected again.What I recommend:
not_requiredcolumn exists.Important note:
The Help Documents in JCB are not the same as help documents inside your own custom components, so this is most likely specific to your migrated environment rather than a general JCB issue.
That said, if you are seeing this error directly within JCB (not just your own component), it would be good for us to verify further. In that case, please share:
In our clean test environments (including standard JCB test setups), this issue does not occur. However, we did observe it on a long-lived dev system that was originally migrated from Joomla 3, which further supports the database migration angle.
So the immediate fix is to clean up that legacy column, and if anything still persists after that, we can dig deeper together.
Thank you, unbelievable! I won't even mention how long I searched, anyway. Thank you so much, the problem is solved.
I've seen that the Inline Help is quite good. The only issue is that you have to re-enter it first.
JCB is brilliant, thanks again!
René