In php 8.3 there are some deprecated warnings. I see most of the compiler templates already have it set correctly. Only a couple are missing. I did a regex search in the whole joomla install and found the below ones.
A simple search and replace for these instances:
MVCFactoryInterface $factory = null
Registry $input = null (in rules)
Table $table = null
string $section = null
It just needs a ? added in front of these to fix it but you already knew that of course.
Steps to reproduce the Bug
turn on reporting to max on php 8.3
Which Joomla version are you compiling in?
5.4
Which PHP version are you compiling in?
8.3
Which Joomla versions are you targeting?
5.4
Which PHP version are you targeting?
8.3
Which Web server is JCB running on?
litespeed
Which Relational Database is JCB running on?
mariadb
Which OS is JCB running on?
almalinux
Which JCB version are you using?
5.1.3
Where in JCB did this issue occur?
Compilation of a component
On which browsers did you encounter the issue?
Safari
Additional Comments
No response
### What Happened?
In php 8.3 there are some deprecated warnings. I see most of the compiler templates already have it set correctly. Only a couple are missing. I did a regex search in the whole joomla install and found the below ones.
A simple search and replace for these instances:
MVCFactoryInterface $factory = null
Registry $input = null (in rules)
Table $table = null
string $section = null
It just needs a ? added in front of these to fix it but you already knew that of course.
### Steps to reproduce the Bug
turn on reporting to max on php 8.3
### Which Joomla version are you compiling in?
5.4
### Which PHP version are you compiling in?
8.3
### Which Joomla versions are you targeting?
5.4
### Which PHP version are you targeting?
8.3
### Which Web server is JCB running on?
litespeed
### Which Relational Database is JCB running on?
mariadb
### Which OS is JCB running on?
almalinux
### Which JCB version are you using?
5.1.3
### Where in JCB did this issue occur?
Compilation of a component
### On which browsers did you encounter the issue?
Safari
### Additional Comments
_No response_
I have fixed these in the templates (today) but those in the rules are DB values, and while I fixed them on my end, so new systems will start with them fixed, you will manually have to update those in your respective systems.
I have fixed these in the templates (today) but those in the rules are DB values, and while I fixed them on my end, so new systems will start with them fixed, you will manually have to update those in your respective systems.
@TLWebdesign is this still a active bug or can we close this issue.
We want to release a stable and it would be greatly appreciated if we can close all issues that has been resolved.
@TLWebdesign is this still a active bug or can we close this issue.
We want to release a stable and it would be greatly appreciated if we can close all issues that has been resolved.
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?
In php 8.3 there are some deprecated warnings. I see most of the compiler templates already have it set correctly. Only a couple are missing. I did a regex search in the whole joomla install and found the below ones.
A simple search and replace for these instances:
MVCFactoryInterface $factory = null
Registry $input = null (in rules)
Table $table = null
string $section = null
It just needs a ? added in front of these to fix it but you already knew that of course.
Steps to reproduce the Bug
turn on reporting to max on php 8.3
Which Joomla version are you compiling in?
5.4
Which PHP version are you compiling in?
8.3
Which Joomla versions are you targeting?
5.4
Which PHP version are you targeting?
8.3
Which Web server is JCB running on?
litespeed
Which Relational Database is JCB running on?
mariadb
Which OS is JCB running on?
almalinux
Which JCB version are you using?
5.1.3
Where in JCB did this issue occur?
Compilation of a component
On which browsers did you encounter the issue?
Safari
Additional Comments
No response
I have fixed these in the templates (today) but those in the rules are DB values, and while I fixed them on my end, so new systems will start with them fixed, you will manually have to update those in your respective systems.
@TLWebdesign is this still a active bug or can we close this issue.
We want to release a stable and it would be greatly appreciated if we can close all issues that has been resolved.