- Posts: 10
- Thank you received: 2
Kunena 6.4.8 Released
The Kunena team has announce the arrival of Kunena 6.4.8 [K 6.4.8] in stable which is now available for download as a native Joomla extension for J! 5.0.x/5.1.x/5.2.x/5.3.x/5.4.x. This version addresses most of the issues that were discovered in K 6.2 / K 6.3 / K 6.4 and issues discovered during the last development stages of K 6.4
Important note: Go to the Kunena Dashboard after an upgrade so that the Kunena database tables are also updated. This is particularly necessary for major version jumps so that the table changes are adapted.
Question Deprecated: Creation of dynamic property Kunena\Forum\Libraries\Config\...
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
Please Log in or Create an account to join the conversation.
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:
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).
.
Important! Always create a backup before you make any changes to your website!
Please Log in or Create an account to join the conversation.
Regards
Please Log in or Create an account to join the conversation.
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
Important! Always create a backup before you make any changes to your website!
Please Log in or Create an account to join the conversation.
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.
Please Log in or Create an account to join the conversation.
- Posts: 951
- Thank you received: 148
Please Log in or Create an account to join the conversation.
Since I didn't have a backup, what I did was change all versions from 6.4.5 to 6.3.10 in the database extensions table and delete the record for version 6.4.5 in the kunena_versions table, without changing the update site URL. If I change it to version 3.6, it won't have the update to 6.4.x. Then, using the Joomla updater, I performed the update and then went to the Dashboard as Pikeltje recommended. All the updates were performed, and almost everything was fixed, with the exception of:
Deprecated: Creation of dynamic property Kunena\Forum\Libraries\User\KunenaUser::$twitter
And when I check the users table, it still has the "twitter" column. Instead, the "socials" column contains "x" (previously "twitter"). Therefore, I think the "twitter" column should also be removed from the users table in the next version.
Thank you.
Please Log in or Create an account to join the conversation.
The twitter was renammed into x_social when updating to K6.3.3, i will add something in the update process of K6.4.6 to check all columns in table kunena_users and clean the ones which no need to be here.
I don't provide support by PM, because this can be useful for someone else.
Please Log in or Create an account to join the conversation.
In version 6.3, there was an option to disable social media, which was in Settings >> Users. Now it's gone, and I can't find where to disable it. Is it possible to disable it?
Thanks.
Please Log in or Create an account to join the conversation.
Template Overrides | Kunena Docs
I removed lines 213–215 in .../site/template/aurelia/layouts/user/item/summary/default.php
and lines 131–145 in .../site/template/aurelia/layouts/user/edit/profile/default.php.
Unzip this uploaded zip file and copy the folder to .../yourJoomlaTemplatefolder/html
Important! Always create a backup before you make any changes to your website!
Please Log in or Create an account to join the conversation.