- Posts: 839
- Thank you received: 36
Kunena 6.3.0 released
The Kunena team has announce the arrival of Kunena 6.3.0 [K 6.3.0] in stable which is now available for download as a native Joomla extension for J! 4.4.x/5.0.x/5.1.x. This version addresses most of the issues that were discovered in K 6.2 and issues discovered during the last development stages of K 6.3
Solved [K.5.0.RC2] PHP Fatal error: Cannot use 'String' as class name as it is reserved
7 years 10 months ago - 7 years 10 months ago #1
by ssh
Tested with: PHP 7.0.7 + J.3.5.1 + K.5.0.RC2 + Crypsis
PHP Fatal error: Cannot use 'String' as class name as it is reserved in /home/username/public_html/libraries/vendor/joomla/string/src/String.php on line 19
PHP Fatal error: Cannot use 'String' as class name as it is reserved in /home/username/public_html/libraries/vendor/joomla/string/src/String.php on line 19
Last edit: 7 years 10 months ago by ssh.
Please Log in or Create an account to join the conversation.
7 years 10 months ago #2
by 810
Replied by 810 on topic [K.5.0.RC2] PHP Fatal error: Cannot use 'String' as class name as it is reserved
on which page do you get this error?
Please Log in or Create an account to join the conversation.
7 years 10 months ago #3
by 810
Replied by 810 on topic [K.5.0.RC2] PHP Fatal error: Cannot use 'String' as class name as it is reserved
i can't found any Joomla\String code anymore, they have all updated.
Please Log in or Create an account to join the conversation.
7 years 10 months ago #4
by ssh
Replied by ssh on topic [K.5.0.RC2] PHP Fatal error: Cannot use 'String' as class name as it is reserved
I haven't see the error in the frontend
I have only one line with this error in my error_log file
This was After migrate from K.4.0.11 to k.5.0.RC2
I have only one line with this error in my error_log file
This was After migrate from K.4.0.11 to k.5.0.RC2
Please Log in or Create an account to join the conversation.
7 years 10 months ago #5
by ssh
Replied by ssh on topic [K.5.0.RC2] PHP Fatal error: Cannot use 'String' as class name as it is reserved
Let's put this error on hold.
It just happens once, and I think it could be related to crypsis 4.0.11
I switch from blue eagle 4.0.11 to crypsis 4.0.11 just a few seconds before migrating to k.5.0RC2
It just happens once, and I think it could be related to crypsis 4.0.11
I switch from blue eagle 4.0.11 to crypsis 4.0.11 just a few seconds before migrating to k.5.0RC2
Please Log in or Create an account to join the conversation.
Time to create page: 0.501 seconds