Question Deprecated: Creation of dynamic property Kunena\Forum\Libraries\Config\...

Hello, because the update to Kunena 6.3.10 does not work with the message "invalid extension update" I came here, and since there is no version 6.3.10 available for download, I downloaded 6.4.1. I installed it using the Joomla installer. When it seemed that everything was going to work, the site was full of errors in both the backend and frontend. The errors are:
Deprecated: Creation of dynamic property Kunena\Forum\Libraries\Config\KunenaConfig::$disable_re
Deprecated: Creation of dynamic property Kunena\Forum\Libraries\Config\KunenaConfig::$autoembedinstagram
Deprecated: Creation of dynamic property Kunena\Forum\Libraries\Config\KunenaConfig::$use_system_emails
Deprecated: Creation of dynamic property Kunena\Forum\Libraries\Config\KunenaConfig::$allow_edit_poll
Deprecated: Creation of dynamic property Kunena\Forum\Libraries\Config\KunenaConfig::$sef_redirect
Deprecated: Creation of dynamic property Kunena\Forum\Libraries\Config\KunenaConfig::$avatar_type
Deprecated: Creation of dynamic property Kunena\Forum\Libraries\Config\KunenaConfig::$search_id
In total 212 errors of this type and they all point to libraries\kunena\src\Config\KunenaConfig.php on line 1832 and refer to:
administrator\includes\app.php
administrator\components\com_kunena\api\api.php

Joomla 5.3.0, PHP 8.2.5, Mysql 8.0.18, when installing it did not abort and nor did it warn about mysql 8.4.0, what's wrong? Because the errors are in the backend and frontend, not a template issue.

Regards

== Post moved ==
I have created a new topic as the original topic is already 11 months old.

If you have database access, create a database backup of the #__kunena_configuration table. Then search for this entry in the text field: Note the capital letters!
Then delete everything that is entered after this entry. Finally, you must place this bracket } at the end and save.
Then go to the configuration in the backend and refresh the page.
These messages should then be gone.

Entries marked in green must be the last (see image).
.
 

Hi, I've searched for mailBodyUserUnBanned in the aforementioned table and throughout the entire database, and it doesn't exist. From what I can see, the error is in PHP.
Regards

I'm sorry, that was my mistake. I hadn't remembered that this entry has only existed since Kunena 6.4.2.
Take this entry "privateMessage":"1" and note the capital letters! Delete everything after that. The end must then look like this: "privateMessage":"1"}
Then go to the configuration in the backend and refresh the page.
The missing entries UserBanned and UserUnBanned are automatically entered in the database as soon as you save something in the configuration.

Alternatively, you can also try this:
It is important that you follow the order exactly!
1. upgrade to Kunena 6.4.2 and go to the dashboard afterwards
2. then go to the Kunena configuration and stay there
3. remove the entire text content from the params column in the #__kunena_configuration table and save
4. save the configuration before reloading the configuration page (for this reason it is important to already be in the configuration)
5. check the configuration, all your custom settings should have remained

Hi Rich.
After several months, I decided to update, and I think the easiest way to update the Kunena configuration is to follow your recommendation: delete the data from the params column of the #__kunena_configuration table. However, in my case, leaving the cell empty gives a 500 error, so I should leave {}, which is an empty JSON.

But I'm still having deprecation issues like the following:
Deprecated: Creation of dynamic property Kunena\Forum\Libraries\User\KunenaUser::$karma_time
Deprecated: Creation of dynamic property Kunena\Forum\Libraries\User\KunenaUser::$bebo
Deprecated: Creation of dynamic property Kunena\Forum\Libraries\User\KunenaUser::$digg
Deprecated: Creation of dynamic property Kunena\Forum\Libraries\User\KunenaUser::$icq
................
Another 28 or so until
Deprecated: Creation of dynamic property Kunena\Forum\Libraries\User\KunenaUser::$socialshare

From what I see, these issues come from the #__kunena_users table, which no longer has those columns in version 6.4.x. Instead, I see a column called socials. So, when making these changes to the table's database structure, wasn't a script created to alter the table and its contents when upgrading from 6.3.10 to version 6.4.x (6.4.5 in my case)?

In this case, what's the easiest way to fix this?

Thanks.

The upgrade should work for K 6.4.5 when you go to Kunena dashboard right after installing latest Kunena version so that database table are updated. So best solution is to restore a backup and do the upgrade again.