[BUG]: Folder Path Error #1150
Labels
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: joomla/Component-Builder#1150
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?
I have, as suggested, setup VirtualBox and installed OctoJoom. I installed a base Joomla 5.1.2, and have Component Builder 5.0.2 Alpha 2 installed. When attempting to compile the Demo component, all work except upon completion I get a
Folder Path Error The folder path: /var/www/html/libraries/phpspreadsheet/vendor does not exist, and was not added!
The component installs fine, but upon going into the Demo component, there are no icons on the menu options on the cPanel.
Steps to reproduce the Bug
Install and compile/create Octojoom, create a joomla site using 5.1.2, install Component Builder 5.0.1 Alpha 2 and compile the Demo component.
Which Joomla version are you compiling in?
5.1.2
Which PHP version are you compiling in?
8.2.21
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.61 (Debian)
Which Relational Database is JCB running on?
11.4.2-MariaDB-ubu2404
Which OS is JCB running on?
Ubuntu 22.04.4 LTS
Which JCB version are you using?
v5.0.2-alpha2
Where in JCB did this issue occur?
Compilation of a component
On which browsers did you encounter the issue?
Firefox
Additional Comments
No response
We remove the import and export feature from Joomla 4+ but not from Joomla 3
This causes some error/warring/notices... and while it is not effecting JCB on Joomla 3, it effect all other versions. We are planning to add a far more superior import export feature to Joomla 4+ in the next few weeks.
The
/var/www/html/libraries/phpspreadsheet
was used in export and import in Joomla 3.You should actually be able to ignore this specific error when targeting Joomla 4+
Should you still like to target Joomla 3, then please run JCB 3 in Joomla 3, this remains the best choice for Joomla 3.
What I did in the latest alpha3 is remove the error message when targeting Joomla 4+ in Joomla 4+
Side note
I have been working on the front-end of Joomla 4 & 5 and we found many bugs that we fixed in the latest alpha3 releases of JCB. It is currently more stable than the last stable releases... ironically.
This means I am trying to push out the next stable releases as quick as possible...