I experimented with the custom router feature, then disabled it again and was experiencing errors.
Steps to reproduce the Bug
Initially I had code in [constructor_before_parent] and [methods]. Having these set, JCB automatically created some getter methods (e.g. "getWorldSegment") in my Service/Router.php file. Later I changed the router settings back to "Default" and compiled again. It retained those getter methods, which caused errors. It was resolved when I entered "//" in the Code area and compiled again.
### What Happened?
I experimented with the custom router feature, then disabled it again and was experiencing errors.
### Steps to reproduce the Bug
Initially I had code in [constructor_before_parent] and [methods]. Having these set, JCB automatically created some getter methods (e.g. "getWorldSegment") in my Service/Router.php file. Later I changed the router settings back to "Default" and compiled again. It retained those getter methods, which caused errors. It was resolved when I entered "//" in the Code area and compiled again.
### Which Joomla version are you compiling in?
6.0.2
### 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
### Which JCB version are you using?
6.1.4 beta 3
### Where in JCB did this issue occur?
Compilation of a component
### On which browsers did you encounter the issue?
Firefox
### Additional Comments
_No response_
When upgrading JCB to the latest version, you must also update all Super Powers. Many of these classes have been improved, and JCB now relies on those improvements.
To resolve your issue, go to the Power area, select the classes associated with the errors you are seeing, and click Reset. This will realign the selected classes with their current global versions and should resolve the issue.
When upgrading JCB to the latest version, you must also update all [Super Powers](https://git.vdm.dev/joomla/super-powers). Many of these classes have been improved, and JCB now relies on those improvements.
To resolve your issue, go to the **Power** area, select the classes associated with the errors you are seeing, and click **Reset**. This will realign the selected classes with their current global versions and should resolve the issue.
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?
I experimented with the custom router feature, then disabled it again and was experiencing errors.
Steps to reproduce the Bug
Initially I had code in [constructor_before_parent] and [methods]. Having these set, JCB automatically created some getter methods (e.g. "getWorldSegment") in my Service/Router.php file. Later I changed the router settings back to "Default" and compiled again. It retained those getter methods, which caused errors. It was resolved when I entered "//" in the Code area and compiled again.
Which Joomla version are you compiling in?
6.0.2
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
Which JCB version are you using?
6.1.4 beta 3
Where in JCB did this issue occur?
Compilation of a component
On which browsers did you encounter the issue?
Firefox
Additional Comments
No response
When upgrading JCB to the latest version, you must also update all Super Powers. Many of these classes have been improved, and JCB now relies on those improvements.
To resolve your issue, go to the Power area, select the classes associated with the errors you are seeing, and click Reset. This will realign the selected classes with their current global versions and should resolve the issue.