[BUG]: Installation failure on J5 using Component Builder (v.5.0.1-alpha6) #1141
Labels
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: joomla/Component-Builder#1141
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What Happened?
Installation aborted with this message:
Unknown column 'add_backup_folder_path' in 'field list'
Error installing component
Steps to reproduce the Bug
Install Component-Builder-v5.0.1-alpha6 on Joomla 5.1
Which Joomla version are you compiling in?
Joomla! 5.1.0 Stable [ Kudumisha ] 16-April-2024 16:00 GMT
Which PHP version are you compiling in?
8.1.2-1ubuntu2.18
Which Joomla versions are you targeting?
Joomla! 5.1.0
Which PHP version are you targeting?
8.1
Which Web server is JCB running on?
Apache version 2.4.52
Which Relational Database is JCB running on?
10.6.18-MariaDB-0ubuntu0.22.04.1
Which OS is JCB running on?
Ubuntu Linux 22.04.4
Which JCB version are you using?
Component-Builder-v5.0.1-alpha6
Where in JCB did this issue occur?
Installation JCB pkg
On which browsers did you encounter the issue?
Firefox
Additional Comments
I did report this previously on Alpha5, but it was deleted. This is Alpha6.
Closed by mistake, sorry. Please reopen
My Joomla 5 debug sysinfo attached.
Check your PHP installation environment, the missing field is one of the component table fields... which should have been created by Joomla during the installation of JCB. But since JCB is a very large component it needs special care...
We can only assume it is related to your environment setup where Joomla is installed, because all our tests and larger team of developers are not able to duplicate this issue.
We are using OctoJoom to manage all our Joomla docker dev containers.
Just installing JCB again, once your PHP is setup correctly should resolve the issue.
Also check the official docker container setup of PHP to confirm that your Joomla setup is optimal, or use the official container directly.
After careful rechecking, they are, and were, exactly as per your PHP-Settings document. Using Virtualmin v 7.10.0. Docker not used. I found 2 lists of installation items in the docker file and installed them, without error. Some were not in my system or your 'module list'. Installing the JCB component still errors. There are no errors in the Journalctl, Apache, PHP or Joomla Logs.
A bug's existence doesn't depend on developer team size. I'll use the other component instead, but thank you for your quick replies.
Addressing the Issue with JCB Installation
Bug Existence and Developer Team Size
A bug's existence isn't dependent on the size of the developer team. We've never suggested otherwise. We simply pointed out that multiple developers who regularly test JCB (both with fresh and existing installs) have not been able to replicate your issue. Therefore, we believe it's not a bug but likely related to your specific environment setup.
Installation Errors
Many developers using the official Docker image (which is the documentation by the way) are able to set up JCB without encountering the issues you're facing. If everyone else is getting it right, it's unlikely that they're all wrong and your setup is the only correct one.
Using Virtualmin v7.10.0
We extensively use Virtualmin and have never needed to do more than run their own PHP setup commands. We have over 10+ JCB systems running on Virtualmin for large projects without issues. Here’s how we set up PHP 8.1 on a virtual system:
Install PHP 8.1 and all needed extensions for Joomla:
Exploring Other Components
If you prefer to use another component, that's perfectly fine. Here’s a list of our fellow extension developers:
We welcome and support these developers and their solutions. If JCB can assist them in any way, we're more than willing to help.
Our market focuses on corporate industrial applications developed by experts in PHP and Joomla. We understand that JCB might not be the right fit for everyone. There have been discussions about using JCB in a Software as a Service (SaaS) model to make it more accessible for users without coding knowledge. However, we’ve always questioned the safety of this approach—just as having an inexperienced person perform open-heart surgery would be dangerous, JCB lacks the necessary safeguards to prevent users from making critical errors. Perhaps AI can assist in this regard, and we are actively researching its potential.
I have been coding and hosting LAMP projects since Joomla was Mambo and explicitly followed the instructions, several times. I think some 'pre-flight' checking phase might be a useful addition, especially as nothing was reported in the logs.
Good luck with all your projects, they look very useful.
In the Docker setup, we only need to check a few PHP values, which are already being verified during installation line 590 and update line 582, triggering the phpConfigurationCheck method.
We are always looking for more help. If you're willing to improve JCB's installation script, please update the file here. Submit a pull request (PR), and we will make time to evaluate your solution.
We are even performing a table validation check.