When I compile my component there are inconsistent errors related to directory creation or deletion. It eventually works after repeated attempts.
Steps to reproduce the Bug
Compile my component (includes a module) for Joomla version 6.
Sometimes there is a message "An error has occurred. Joomla\Filesystem\Folder::create: Could not create directory. Path: [ROOT]/administrator/components/com_componentbuilder/compiler/com_threedbug_v1_1_0beta__J6/libraries/jcb_powers/Confidant.Joomla/src.
Returning to the compiler afterward sometimes shows that "The Extensions were Successfully Compiled!". Sometimes not.
Clicking "Install all of the above extensions" sometimes works, sometimes will install only the module.
Sometimes there was complete success in compiling, often after an initial failure.
Sometimes the zipped component is installable elsewhere, sometimes it is missing a manifest.
### What Happened?
When I compile my component there are inconsistent errors related to directory creation or deletion. It eventually works after repeated attempts.
### Steps to reproduce the Bug
Compile my component (includes a module) for Joomla version 6.
1. Sometimes there is a message "An error has occurred. Joomla\Filesystem\Folder::create: Could not create directory. Path: [ROOT]/administrator/components/com_componentbuilder/compiler/com_threedbug_v1_1_0beta__J6/libraries/jcb_powers/Confidant.Joomla/src.
2. Returning to the compiler afterward sometimes shows that "The Extensions were Successfully Compiled!". Sometimes not.
3. Clicking "Install all of the above extensions" sometimes works, sometimes will install only the module.
4. Sometimes there was complete success in compiling, often after an initial failure.
5. Sometimes the zipped component is installable elsewhere, sometimes it is missing a manifest.
### Which Joomla version are you compiling in?
6.0.3
### Which PHP version are you compiling in?
8.3.27
### Which Joomla versions are you targeting?
6.0.0
### Which PHP version are you targeting?
8.3.27
### Which Web server is JCB running on?
Joomla Docker image "joomla:5.4.0-php8.3". Apache 2
### Which Relational Database is JCB running on?
mysqlnd 8.3.27
### Which OS is JCB running on?
Alpine linux inside Docker on a Mac ARM64
### Which JCB version are you using?
6.1.5
### Where in JCB did this issue occur?
Compilation of a component
### On which browsers did you encounter the issue?
Chrome
### Additional Comments
_No response_
Hi @ConfidantCommunications,
I noticed that you are currently using JCB in Chrome. While it may function in that environment, it is not the recommended browser for development and compilation tasks.
For optimal performance and compatibility, we strongly suggest using Firefox or Librewolf. JCB is actively tested and developed with Firefox-based browsers, which ensures a more stable and consistent experience - particularly during the compilation process.
As a next step, please try compiling the same components using either Firefox or Librewolf. If the issue persists, we would appreciate it if you could provide additional details to help us investigate further. Specifically, screenshots of the error and any available debug logs would be very helpful.
Hi @ConfidantCommunications,
I noticed that you are currently using JCB in Chrome. While it may function in that environment, it is not the recommended browser for development and compilation tasks.
For optimal performance and compatibility, we strongly suggest using Firefox or Librewolf. JCB is actively tested and developed with Firefox-based browsers, which ensures a more stable and consistent experience - particularly during the compilation process.
As a next step, please try compiling the same components using either Firefox or Librewolf. If the issue persists, we would appreciate it if you could provide additional details to help us investigate further. Specifically, screenshots of the error and any available debug logs would be very helpful.
Hm, well Firefox is actually my preferred browser but Chrome's debug tools seem to work better for me. So that's not necessarily bad news for me but a little strange since it's usually people using Chrome and ignoring Firefox ;)
Here's a shot from just a minute ago, in Chrome.
A while back I was having permission troubles using Docker on Mac and I would have to periodically do a chmod to fix it. This isn't behaving exactly the same way but I wonder if it's related to that.
Hm, well Firefox is actually my preferred browser but Chrome's debug tools seem to work better for me. So that's not necessarily bad news for me but a little strange since it's usually people using Chrome and ignoring Firefox ;)
Here's a shot from just a minute ago, in Chrome.
A while back I was having permission troubles using Docker on Mac and I would have to periodically do a chmod to fix it. This isn't behaving exactly the same way but I wonder if it's related to that.
@ConfidantCommunications I'm going to close this issue, as I understand from your last comment that compiling with Firefox, as recommended, resolves the problem.
That said, I do agree that it would be valuable for JCB to compile reliably across different browsers, including Chrome. However, I want to be transparent that we currently have several active projects and priorities, so this is not high on the immediate development list at this time.
For now, our recommendation remains to use Firefox when compiling with JCB, as it has consistently provided the most reliable results. We also know that some users have had good results using Safari on macOS, so that may be another viable option depending on your environment.
For the moment, Firefox or a Firefox-based browser remains the recommended and best-supported option for compiling with JCB.
Thanks again for reporting this and for helping us clarify the current browser compatibility expectations.
@ConfidantCommunications I'm going to close this issue, as I understand from your last comment that compiling with Firefox, as recommended, resolves the problem.
That said, I do agree that it would be valuable for JCB to compile reliably across different browsers, including Chrome. However, I want to be transparent that we currently have several active projects and priorities, so this is not high on the immediate development list at this time.
For now, our recommendation remains to use Firefox when compiling with JCB, as it has consistently provided the most reliable results. We also know that some users have had good results using Safari on macOS, so that may be another viable option depending on your environment.
For the moment, Firefox or a Firefox-based browser remains the recommended and best-supported option for compiling with JCB.
Thanks again for reporting this and for helping us clarify the current browser compatibility expectations.
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.
What Happened?
When I compile my component there are inconsistent errors related to directory creation or deletion. It eventually works after repeated attempts.
Steps to reproduce the Bug
Compile my component (includes a module) for Joomla version 6.
Which Joomla version are you compiling in?
6.0.3
Which PHP version are you compiling in?
8.3.27
Which Joomla versions are you targeting?
6.0.0
Which PHP version are you targeting?
8.3.27
Which Web server is JCB running on?
Joomla Docker image "joomla:5.4.0-php8.3". Apache 2
Which Relational Database is JCB running on?
mysqlnd 8.3.27
Which OS is JCB running on?
Alpine linux inside Docker on a Mac ARM64
Which JCB version are you using?
6.1.5
Where in JCB did this issue occur?
Compilation of a component
On which browsers did you encounter the issue?
Chrome
Additional Comments
No response
Hi @ConfidantCommunications,
I noticed that you are currently using JCB in Chrome. While it may function in that environment, it is not the recommended browser for development and compilation tasks.
For optimal performance and compatibility, we strongly suggest using Firefox or Librewolf. JCB is actively tested and developed with Firefox-based browsers, which ensures a more stable and consistent experience - particularly during the compilation process.
As a next step, please try compiling the same components using either Firefox or Librewolf. If the issue persists, we would appreciate it if you could provide additional details to help us investigate further. Specifically, screenshots of the error and any available debug logs would be very helpful.
Hm, well Firefox is actually my preferred browser but Chrome's debug tools seem to work better for me. So that's not necessarily bad news for me but a little strange since it's usually people using Chrome and ignoring Firefox ;)
Here's a shot from just a minute ago, in Chrome.
A while back I was having permission troubles using Docker on Mac and I would have to periodically do a chmod to fix it. This isn't behaving exactly the same way but I wonder if it's related to that.
I have been using Firefox to compile since my last message and can confirm it has none of the same errors.
@ConfidantCommunications I'm going to close this issue, as I understand from your last comment that compiling with Firefox, as recommended, resolves the problem.
That said, I do agree that it would be valuable for JCB to compile reliably across different browsers, including Chrome. However, I want to be transparent that we currently have several active projects and priorities, so this is not high on the immediate development list at this time.
For now, our recommendation remains to use Firefox when compiling with JCB, as it has consistently provided the most reliable results. We also know that some users have had good results using Safari on macOS, so that may be another viable option depending on your environment.
For the moment, Firefox or a Firefox-based browser remains the recommended and best-supported option for compiling with JCB.
Thanks again for reporting this and for helping us clarify the current browser compatibility expectations.
All good!
i can confirm safari is no longer a valid option for compiling.