[BUG]: Not all files in downloaded zip file #1185
Labels
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: joomla/Component-Builder#1185
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 Install Component-Builder-v5.0.3 (Last stable one, but try the current one too) without any warnings.
Then I go to Compiler, select "Demo (public)" and start "Compile Component"
The I get the message
Total folders created: 126
Total files created: 466
Total fields created: 133
Total lines written: 60533
A4 Book of: 1081 pages
But if I download the package only 2 admin and 2 site language files are in the zip file.
All the settings from https://git.vdm.dev/joomla/Component-Builder/wiki/PHP-Settings are correct.
Steps to reproduce the Bug
Install Joomla, install Component-Builder, press compile of the included demo project
Which Joomla version are you compiling in?
5.1.4
Which PHP version are you compiling in?
8.2.23
Which Joomla versions are you targeting?
5.1.4
Which PHP version are you targeting?
8.2.23
Which Web server is JCB running on?
Apache
Which Relational Database is JCB running on?
8.0.34-cll-lve
Which OS is JCB running on?
Linux
Which JCB version are you using?
Component-Builder-v5.0.3 (Last stable one, but try the current one too)
Where in JCB did this issue occur?
Compilation of a component
On which browsers did you encounter the issue?
Chrome
Additional Comments
No response
I experience this a lot as well working on my own custom component.
Very often when I compile, I get errors like this after compile and I try to install: JInstaller: :Install: Can't find Joomla XML setup file.
Sometimes I have to compile 10 - 20 times before it works. I can't figure out why. JCB is running on my own server that has plenty of muscle and little load. All required setting have been met.
Other times I get the error: Failed deleting ItemInterface.php
0 You must specify a non-empty path to clean
Or this: RecursiveDirectoryIterator::__construct(/home/DOMAIN/public_html/administrator/components/com_componentbuilder/compiler/com_XXXXXXX_v1_0_5__J5/admin/src/Table): Failed to open directory: No such file or directory
Or this: Failed deleting NoUserIdFoundException.php
0 You must specify a non-empty path to clean
And them, with no apparent logic, it compiles.
I experience this a lot as well working on my own custom component.
Very often when I compile, I get errors like this after compile and I try to install: JInstaller: :Install: Can't find Joomla XML setup file.
Sometimes I have to compile 10 - 20 times before it works. I can't figure out why. JCB is running on my own server that has plenty of muscle and little load. All required setting have been met.
Other times I get the error: Failed deleting ItemInterface.php
0 You must specify a non-empty path to clean
Or this: RecursiveDirectoryIterator::__construct(/home/DOMAIN/public_html/administrator/components/com_componentbuilder/compiler/com_XXXXXXX_v1_0_5__J5/admin/src/Table): Failed to open directory: No such file or directory
Or this: Failed deleting NoUserIdFoundException.php
0 You must specify a non-empty path to clean
And them, with no apparent logic, it compiles.
Hi @dyvel apologies for the slow reply here, I have been tied up with person responsibilities the last few weeks.
Please do not use Chrome, but Firefox instead during your development phase... since it seems like Chrome being an app engine aswell as a browsers is caching things it shouldn't.
While Firefox seems not to do the same thing, it works more reliably stable with JCB.
Let me know if this helped?
@Llewellyn Using Firefox over Safari seems to fix my issue. At least I've had no issue since switching. Thanks!
Solves my problem too. It should be mentioned somewhere that you shouldn't use Chrome. Many people will just try it, have no success and then just look for another solution. I'm closing the issue.