mwweb commented

Steps to reproduce the issue

Attempted install of v5.0.0-Alpha1

Expected result

JCB would install with no issues

Actual result

DB tables were added, but install failed with "Joomla Component Builder must first be installed from Joomla Component Builder."

System information (as much as possible)

OS Name & Version: Win11
MySql Version: MariaDB 11.1.2-win64
Apache Version: 2.4.58
PHP Version: 8.2.16
Joomla Version: 5.0.3
JCB Version: 5.0.0-Alpha1
Browser: MS Edge

Additional comments

### Steps to reproduce the issue Attempted install of v5.0.0-Alpha1 ### Expected result JCB would install with no issues ### Actual result DB tables were added, but install failed with "Joomla Component Builder must first be installed from Joomla Component Builder." ### System information (as much as possible) - OS Name & Version: Win11 - MySql Version: MariaDB 11.1.2-win64 - Apache Version: 2.4.58 - PHP Version: 8.2.16 - Joomla Version: 5.0.3 - JCB Version: 5.0.0-Alpha1 - Browser: MS Edge ### Additional comments

jcb5-error.png

65 KiB

mwweb commented

2024-03-09 21:10:23 +00:00

Author

Update, it looks as though JCB 5.0.0-alpha1 may have installed, even with the error.

Malachi commented

2024-03-09 22:13:08 +00:00

Member

Seems like the plugin is looking for the helper file, and fails since the location has changed.

AlexEdimensionz commented

2024-03-10 12:53:35 +00:00

I get the same error message. The plugin does install and seems to work.
The Component importer does not work, however

I get the same error message. The plugin does install and seems to work. The Component importer does not work, however

Llewellyn commented

2024-03-10 16:51:59 +00:00

Owner

Thank you for bringing this issue to our attention. We're actively working on a solution and anticipate it will be resolved with the upcoming Alpha2 release. Despite thorough testing over the past week—exclusively on Linux, using Firefox—we didn't encounter this bug. However, its emergence underscores the unpredictable nature of software development.

I must reiterate a point that has been made before: please use Firefox. For reasons that elude even me, JCB exhibits compatibility issues with other browsers.

Additionally, I urge you to implement the following settings in your development environments for Joomla versions 3, 4, and 5:

; Resource Limits and File Uploads
upload_max_filesize = 128M
post_max_size = 128M
max_execution_time = 60
max_input_vars = 3000
max_input_time = 60
memory_limit = 256M

Incorporating these configurations into the PHP.ini file will soon be recommended as part of the JCB package.

A Humble Request

For those of you developing on Windows, I kindly suggest considering a shift towards Ubuntu. Although I've come to terms with the widespread use of Windows, it's worth noting that the majority of servers operate on Linux. This is where JCB thrives, given its Linux-centric development by a dedicated yet small team. Our resources don't allow for extensive cross-OS optimization. I know that this limited focus on Linux is a constraint for projects in the gaming and broader tech industries. Yet, within the Joomla community, this focus on Linux often translates to a strategic advantage.

To facilitate this transition, I recommend following this tutorial on setting up OctoJoom in a virtual Ubuntu system on Windows. Ideally, however, running it directly on Ubuntu would align closely with my setup.

The Underlying Reason

The essence of this guidance stems from uncertainty regarding the nature of the reported issues—whether they are OS, PHP, or Joomla specific. By aligning our testing environments, we can more accurately pinpoint the problem, ensuring a more unified and focused approach to development.

Why we did not get those errors?

It seem to be due to the fact that some of our testers did not have their error reporting turned on correctly inside the docker containers they are using.

And that in Linux the package install the plugins after the component as they are listed in a specific order as seen here. But on Windows this order is ignored it seems ;)

What ever the case, we are going to fix this... and will push out Alpha2 soon.

Thank you for bringing this issue to our attention. We're actively working on a solution and anticipate it will be resolved with the upcoming Alpha2 release. Despite thorough testing over the past week—exclusively on Linux, using Firefox—we didn't encounter this bug. However, its emergence underscores the unpredictable nature of software development. I must reiterate a point that has been made before: **please use Firefox**. For reasons that elude even me, JCB exhibits compatibility issues with other browsers. > Additionally, I urge you to implement the following settings in your development environments for Joomla versions 3, 4, and 5: ```ini ; Resource Limits and File Uploads upload_max_filesize = 128M post_max_size = 128M max_execution_time = 60 max_input_vars = 3000 max_input_time = 60 memory_limit = 256M ``` Incorporating these configurations into the PHP.ini file will soon be recommended as part of the JCB package. ## A Humble Request For those of you developing on Windows, I kindly suggest considering a shift towards Ubuntu. Although I've come to terms with the widespread use of Windows, it's worth noting that the majority of servers operate on Linux. This is where JCB thrives, given its Linux-centric development by a dedicated yet small team. Our resources don't allow for extensive cross-OS optimization. I know that this limited focus on Linux is a constraint for projects in the gaming and broader tech industries. Yet, within the Joomla community, this focus on Linux often translates to a strategic advantage. To facilitate this transition, I recommend following this tutorial on setting up [OctoJoom](https://www.youtube.com/watch?v=owpxKie0I7s) in a virtual Ubuntu system on Windows. Ideally, however, running it directly on Ubuntu would align closely with my setup. # The Underlying Reason The essence of this guidance stems from uncertainty regarding the nature of the reported issues—whether they are OS, PHP, or Joomla specific. By aligning our testing environments, we can more accurately pinpoint the problem, ensuring a more unified and focused approach to development. # Why we did not get those errors? It seem to be due to the fact that some of our testers did not have their error reporting turned on correctly inside the docker containers they are using. And that in Linux the package install the plugins after the component as they are listed in a specific order as [seen here](https://git.vdm.dev/joomla/pkg-component-builder/src/branch/5.x/pkg_component_builder.xml#L24). But on Windows this order is ignored it seems ;) What ever the case, we are going to fix this... and will push out Alpha2 soon.

mwweb commented

2024-03-10 23:34:24 +00:00

Author

I don't like to argue, but I am going to argue the "accusation" that the error is because it a Windows environment. That almost always seems to be the immediate response when there is an issue with JCB. Even though it's a Windows environment, it still utilizes Apache, PHP, MySQL/Maria/DB. Your preferred environment is Ubuntu, and apparently it works good. Under the "it's the OS", if I was running CentOS/RockyLinux or another fork of CentOS, and I had an issue, the same issue, would that too be because it wasn't the preferred version of Ubuntu that you recommend?

I bring this up because as a test, and I have run this test other times that I have received an error with JCB and Windows was blamed. This test was to create an account on my production server which is running RockyLinux 8, Apache 2.4.58, PHP 8.2.16, 10.11.7-MariaDB.

Any, you know what? I got the EXACT same error that I got in the Windows environment. Does that mean that JCB is not Windows compatible, or now CentOS/RockyLinux/AlmaLinux compatible, only a specialized version of Ubuntu?

I don't like to argue, but I am going to argue the "accusation" that the error is because it a Windows environment. That almost always seems to be the immediate response when there is an issue with JCB. Even though it's a Windows environment, it still utilizes Apache, PHP, MySQL/Maria/DB. Your preferred environment is Ubuntu, and apparently it works good. Under the "it's the OS", if I was running CentOS/RockyLinux or another fork of CentOS, and I had an issue, the same issue, would that too be because it wasn't the preferred version of Ubuntu that you recommend? I bring this up because as a test, and I have run this test other times that I have received an error with JCB and Windows was blamed. This test was to create an account on my production server which is running RockyLinux 8, Apache 2.4.58, PHP 8.2.16, 10.11.7-MariaDB. Any, you know what? I got the EXACT same error that I got in the Windows environment. Does that mean that JCB is not Windows compatible, or now CentOS/RockyLinux/AlmaLinux compatible, only a specialized version of Ubuntu?

jcb_j5-2024-03-10.png

54 KiB

Llewellyn commented

2024-03-11 08:00:16 +00:00

Owner

So you want to argue with me? 😆 good luck.

So you want to `argue` with me? 😆 good luck.

Llewellyn commented

2024-03-11 08:04:09 +00:00

Owner

We're actively working on a solution and anticipate it will be resolved with the upcoming Alpha2 release.

#1068 (comment)

> We're actively working on a solution and anticipate it will be resolved with the upcoming Alpha2 release. https://git.vdm.dev/joomla/Component-Builder/issues/1068#issuecomment-27773

👍 1

Robot referenced this issue from a commit

2024-03-11 16:22:40 +00:00

Stable release of v4.0.0-alpha2

Robot referenced this issue from a commit

2024-03-11 16:31:20 +00:00

Stable release of v5.0.0-alpha2

Llewellyn commented

2024-03-11 16:45:14 +00:00

Owner

@mwweb can you test with v5.0.0-alpha2 if the issue is resolved, thanks!

@mwweb can you test with [v5.0.0-alpha2](https://git.vdm.dev/joomla/pkg-component-builder/archive/v5.0.0-alpha2.zip) if the issue is resolved, thanks!

Llewellyn commented

2024-03-26 04:28:42 +00:00

Owner

I assume this issue is resolved... if not let me know.