[BUG]: Cannot compile my project anymore since upgrade to 3.2.1 (J3) #1135

New Issue

Closed

opened 2024-05-23 14:40:12 +00:00 by vistamedia · 1 comment

vistamedia commented

2024-05-23 14:40:12 +00:00

Member

What Happened?

I have a project that I started 2 years ago. Since I upgraded from 3.1.4 to 3.2.1 I cannot compile it anymore. I included the backtrace. I also included an install script issue that I had after the upgrade.

Steps to reproduce the Bug

I only occurs with this project so I don't really know what I can say here :)

Which Joomla version are you compiling in?

3.10.12

Which PHP version are you compiling in?

8.0.33

Which Joomla versions are you targeting?

3.10.12

Which PHP version are you targeting?

8.0.33

Which Web server is JCB running on?

Apache 2.4.54

Which Relational Database is JCB running on?

Mysql 5.7

Which OS is JCB running on?

MacOS 14.5 Sonoma

Which JCB version are you using?

3.2.1 stable

Where in JCB did this issue occur?

Compilation of a component

On which browsers did you encounter the issue?

Firefox

Additional Comments

No response

### What Happened? I have a project that I started 2 years ago. Since I upgraded from 3.1.4 to 3.2.1 I cannot compile it anymore. I included the backtrace. I also included an install script issue that I had after the upgrade. ### Steps to reproduce the Bug I only occurs with this project so I don't really know what I can say here :) ### Which Joomla version are you compiling in? 3.10.12 ### Which PHP version are you compiling in? 8.0.33 ### Which Joomla versions are you targeting? 3.10.12 ### Which PHP version are you targeting? 8.0.33 ### Which Web server is JCB running on? Apache 2.4.54 ### Which Relational Database is JCB running on? Mysql 5.7 ### Which OS is JCB running on? MacOS 14.5 Sonoma ### Which JCB version are you using? 3.2.1 stable ### Where in JCB did this issue occur? Compilation of a component ### On which browsers did you encounter the issue? Firefox ### Additional Comments _No response_

2024-05-23_16-04-13.jpg

1.1 MiB

2024-05-23_16-01-45.jpg

278 KiB

vistamedia added the

Bug

label 2024-05-23 14:40:12 +00:00

Llewellyn commented

2024-05-26 16:03:22 +00:00

Owner

It is at times needed to remove the old folders of JCB under the library path library/jcb_powers just to remove all of those.

This you should do with care, since some of your components might still use some of those classes, yet there is now in each component under the Dynamic Integration tab of the component an option to add a library path (JCB Powers Path) that is unique to that component. You can also in the settings tab add a namespace prefix that is unique to that component, and then in all powers you can with the [[[NamespacePrefix]]] at the front of all your namespace dynamically link the powers to each component on compilation.

This is how we resolve some of these collusion issues.

Since I already spoke with you, and believe this is resolved... this note is as reference to other having this same issue.

It is at times needed to remove the old folders of JCB under the library path `library/jcb_powers` just to remove all of those. This you should do with care, since some of your components might still use some of those classes, yet there is now in each component under the `Dynamic Integration` tab of the component an option to add a library path (**JCB Powers Path**) that is unique to that component. You can also in the `settings` tab add a namespace prefix that is unique to that component, and then in all powers you can with the `[[[NamespacePrefix]]]` at the front of all your namespace dynamically link the powers to each component on compilation. This is how we resolve some of these collusion issues. Since I already spoke with you, and believe this is resolved... this note is as reference to other having this same issue.