Search Results (Searched for: rank)

10 Mar 2026 14:43
Hello,Since we migrated our site from Kunena 5 to 6 and now to 7, the e-mail notification for new posts no longer works properly. Possibly this is also a database problem that arose during the data migration - but in any case - here first the error description in Kunena 7.0.2 and Joomla 5.4.3:The notification for new forum posts is not working as expected.
  • Joomla can send e-mails - that works both with the test mail from the mail configuration as well as with serial mails.
  • Users without admin or moderator privileges never get any notification about new messages from kunena.
  • If an administrator or moderator is set in the security settings of the Kunena config to receive all messages, he gets them, but users without admin or moderator rights do not get any messages about answers - even if an admin or moderator replies to the thread and the user has a subscription for the thread.
  • If administrators and moderators are turned off in the security settings and instead "Send mail as system mail" is activated in the subscription settings, no one will receive a notification - not even moderators or admins who have systemails activated.
  • The problem is independent of the mail server settings and occurs with both PHP mail and SMTP Mail.
THXConfig attached:
This message contains confidential information

Database collation check: The collation of your table fields are correct

Joomla! SEF: Enabled | Joomla! SEF rewrite: Enabled | FTP layer: Disabled |   

This message contains confidential information
htaccess: Exists | PHP environment: Max execution time: 240 seconds | Max execution memory: 512M | Max file upload: 

Kunena menu details:

Warning: Spoiler!

Joomla default template details : tp_master | author: joomlaPlates | version: 2.6 | creationdate: 2025-11-12

Kunena default template details : Aurelia | author: Kunena Team | version: 7.0.2 | creationdate: 2026-03-03

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 7.0.2 | 2026-03-03 [ Git Repository ]    | Kunena detailed configuration:

Warning: Spoiler!
| Kunena integration settings:
Warning: Spoiler!
| Joomla! detailed language files installed:
Warning: Spoiler!

Third-party components: None

Third-party SEF components: None

Plugins: None

Modules: Kunena Stats 6.1.0

      
10 Mar 2026 13:59
Unfortunately the fix from CB & Kunena did not work. If you are not using forum rank as a field I would suggest disabling it. Then it works like a charm again.
10 Mar 2026 10:56
Hello xillibit,

I want to thank you and the others here very much. With the change of the two variable names, the test site now runs for the first time without visible error messages with debugging max - and the rank system also works again.

There are still some other problems to which I open a new thread.

Thanks again for the great support!
08 Mar 2026 20:35

Hi rich,

I'm maybe a step further: I turned the extended php debugging on and get two error messages, that I couldn't interpret well - it seems that they are caused by the migration - how ever I wondering how this could be possible because kunena was set up completely new (now with v. 7.0.1).

Do you have a idea, what causes the following error and how to fix it?:

Deprecated: Creation of dynamic property Kunena\Forum\Libraries\Forum\Category\KunenaCategory::$allow_ratings is deprecated in /mnt/web508/e1/97/510678697/htdocs/Update/libraries/kunena/src/Database/KunenaDatabaseObject.php on line 128 Deprecated: Creation of dynamic property



 
Hello,

Since K6.0.0 beta3 the column allow_ratings has been renammed in allowRatings, so make an export of the table #__kunena_categories with phpmyadmin just in case. Then you can apply this query to fix the table : 
Code:
ALTER TABLE `#__kunena_categories` CHANGE allow_ratings allowRatings tinyint(4) NOT NULL default '0';

and,

Warning: Undefined property: stdClass::$rankId in /mnt/web508/e1/97/510678697/htdocs/Update/libraries/vendor/joomla/database/src/DatabaseDriver.php on line 1309

THX
Same here on table #__kunena_ranks before K6.0.0 beta3 there was a column nammed rank_id which has been renammed. so make an export of the table #__kunena_ranks with phpmyadmin just in case, then apply this query : 
Code:
ALTER TABLE `#__kunena_ranks` CHANGE rank_id rankId mediumint(8) unsigned NOT NULL auto_increment;
08 Mar 2026 16:41
Hallo, ich habe jetzt erst einmal für die Profile eine Lösung gefunden. Ich habe einen weiteren Menüpunkt Kunena-Profil nicht übergeordnet erstellt, jetzt scheint mit den Profilen und deren Bearbeitung wieder alles zu funkrtionieren. Was weiterhin nicht geht sind die Ankündigungen und der Punkt alles als gelesen markieren. Nach wie vor funktioniert alles wenn ich SEO deaktiviere...
Ich nutze das Template NTS-KSamurai habe aber alle Fehler auch mit dem Standardtemplate. 
Ich habe auch nochmals ein Backup mit der Ver. 7.0.1 versucht, dort gibt es keinerlei Probleme, die treten erst mit dem Update 7.0.2 auf. 




This message contains confidential information

Database collation check: The collation of your table fields are correct

Joomla! SEF: Enabled | Joomla! SEF rewrite: Enabled | FTP layer: Disabled |

This message contains confidential information
htaccess: Exists | PHP environment: Max execution time: 180 seconds | Max execution memory: 512M | Max file upload:

Kunena menu details:

Warning: Spoiler!

Joomla default template details : tp_barrierefrei | author: joomlaPlates | version: 2.6 | creationdate: 2025-11-12

Kunena default template details : NTS KSamurai | author: Nice Theme Store Team | version: 7.0.0 | creationdate: 2026-02-01

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 7.0.2 | 2026-03-03 [ Git Repository ]
| Kunena detailed configuration:

Warning: Spoiler!
| Kunena integration settings:
Warning: Spoiler!
| Joomla! detailed language files installed:
Warning: Spoiler!

Third-party components: None

Third-party SEF components: None

Plugins: None

Modules: Kunena Latest 6.2.0 | Kunena Login 6.2.0

06 Mar 2026 17:01
note that the deprecated messages are not 'blocking', they are just messages thrown by php 8.4 where e.g. with php 8.3 they would not display.
It is more of a warning to tell you that in future php versions things might stop working.
With the information given it is hard to troubleshoot.
In the Kunena code pre 7.0.2 the dashboard was responsible for doing al kind of upgrade chores (like making changes in the database structure). When visiting the dashboard was 'skipped' and then another upgrade was done, then there was already the issue that the upgrade chores didn't run for the previous version and will not run as the version number was changed.
In version 7.0.2 this will never happen again as the update chores are now part of the upgrade itself, so no more visiting the dashboard after an update.

That said: likely your database is in an state of 'flux' where upgrades did happen and upgrades didn't happen. impossible to tell which ones did and which ones didn't

In the Kunena package there are upgrade xml file(s) with the logic that would run on each version.
I would walk through each one of these database lines and check if the current database tables have these changes and if not run the changes.

Easier said then done I know....
06 Mar 2026 12:52 - 06 Mar 2026 14:18
Hi ruud,

sorry my mistake I did't explain it well - it's a bit more complicated... I did several test. The test site that throw the error runs currently with a kunena that is updated from 6.4.6 to 7.0.1 on a Joomla 5.3.4, and a php 8.4.

The real site was migrated by a professional service from kunena 5 kunena 6 but unfortunately they did't finished the work very well and we still have many errors on the forum of our live site... So I set up copy of the site and started debugging. First I try to fix the database where I still found a lot of variables with utf8mb3_general_ci type and some missing or wrong fields (I had a clean installation - with kunena test data - in parallel, so that I could compare the database).

My fixes of the database where good enough to let the error messages disappear that I've got on the site (without debugging max on) - how ever it did't fix the existing problems (rank system doesn't work as expected and e-mail notification from the forum doesn't work.)

Interestingly in the clean test version, that uses the kunena test data only, every think works perfect so that I think, it have something to do with the data in the database itself that may not migrated very well.

My problem is, that I have no clue where to start because I could find a proper documentation of the data and I don't have the time and the knowledge to re-engineer the code. So my approach for now is trying to fix the obvious errors first and the see what's happen.

I think the problem is not a bug in kunena itself but probably a problem in the migration process of the existing data in database. My hope was that updating Kunea with the real data from 6.4.6 to 7.0.1 would fix these problems - but it seems that this was not the case...

Do you have any ideas where I can start to search?

THX
06 Mar 2026 11:47
Hi, can you tell me what you mean with completely new? Did you fresh install K7.0.1 on a site where there was no Kunena installed on previously?

I'm asking because 'allow_ratings' was used pre 6.0.0 and was change into allowRatings in 6.0.0

So it can only be referenced when there was on old version installed where the upgrade that goes via the Kunena dashboard didn't take place.
05 Mar 2026 11:05
Hi rich,

I'm maybe a step further: I turned the extended php debugging on and get two error messages, that I couldn't interpret well - it seems that they are caused by the migration - how ever I wondering how this could be possible because kunena was set up completely new (now with v. 7.0.1).

Do you have a idea, what causes the following error and how to fix it?:

Deprecated: Creation of dynamic property Kunena\Forum\Libraries\Forum\Category\KunenaCategory::$allow_ratings is deprecated in /mnt/web508/e1/97/510678697/htdocs/Update/libraries/kunena/src/Database/KunenaDatabaseObject.php on line 128 Deprecated: Creation of dynamic property


and,

Warning: Undefined property: stdClass::$rankId in /mnt/web508/e1/97/510678697/htdocs/Update/libraries/vendor/joomla/database/src/DatabaseDriver.php on line 1309

THX
04 Mar 2026 15:32

You have misunderstood something.

 

Thank you.
There are indeed many things I may not understand.
For example, in your last post, I do not understand which Russian and English versions you are referring to.
I will attempt to briefly describe my perspective.
I posted a file from my Russian website here in jpa format and  configuration reports.  
The  jpa file contains a database with information about 
a) posts, pictures, etc. of forum participants. This information is always in one language.  So what “the same prefixes” are we talking about?
b) information about the structure of the current version of the Kunen forum. I changed the Russian language of the Joomla backend and, accordingly, Kunen to English for the convenience of moderators. But isn't there more than one current language stored in the database at any given moment? I really don't understand the phrase “more recent version in English and an older version in Russian.”  Or is some rudimentary information about languages stored (it's not clear why)? 
But if I understand correctly, you are analyzing configuration reports. Obviously, they reflect the state of the database. If the scripts for compiling configuration reports are working correctly (and they must be), then somewhere in the tables there is incorrect (outdated) information. Is it possible to find and fix it?  

To move from “theory” to practice, I will post a configuration report from my working German website below. It has the same problem with updating to K6.4.9. It has been running in German for 20 years and the language on it (neither in the admin nor in the frontend) has never changed. 
I hope there will be no confusion with languages here and you will be able to understand the problems with the Kunen update without being distracted by languages. If it helps, I will provide the German jpa file in Google Docs.
Thanks again for your help.

This message contains confidential information

Database collation check: The collation of your table fields are correct
        

Joomla! SEF: Enabled | Joomla! SEF rewrite: Enabled | FTP layer: Disabled |
        

This message contains confidential information
htaccess: Exists | PHP environment: Max execution time: 120 seconds | Max execution memory: 256M | Max file upload:  

Kunena menu details:

Warning: Spoiler!

Joomla default template details : GiCh_site_template | author: lr | version: 1.0.2 | creationdate: 2025-04-20

Kunena default template details : Aurelia | author: Kunena Team | version: 6.3.10 | creationdate: 2025-03-14

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.3.10 | 2025-03-14 [ Git Repository ]
        | Kunena detailed configuration:

Warning: Spoiler!
| Kunena integration settings:
Warning: Spoiler!
| Joomla! detailed language files installed:
Warning: Spoiler!

Third-party components: CommunityBuilder 2.11.0

Third-party SEF components: None

Plugins: Content - Kunena Discuss 6.0.5

Modules: Kunena Latest 6.0.7

  Переведено с помощью DeepL.com (бесплатная версия) 
02 Mar 2026 22:08
Correct. Now there is no error message anymore, but if I try to assign a rank manually in the kunena user settings - despite which rank I chose - after saving the user settings the highest rank (that one with the highest number) is stored somewhere and there no change in the DB table kunena_users column rank (still 0).

But anyway - I thing there's probably much more screwed up in the database (even if the kunena configuration report and the kunena diagnostic say every think is fine...) I don't know how web-max did the migration, but I guess he simply try's to copy the old database and tweak some values directly in the database.

Meanwhile I made a second clean and empty installation and found out, that there are even more data types had changed in the new kunena version. More over a couple of new values were added which are partly missing in the current installation (e.g. timestamp in the user data). So I will now try to fix the datatypes and the missing colums first and then come back if the error still exists.

Migrating a old Forum ist really pretty complicated... I appreciate your help!

THX!
02 Mar 2026 19:58 - 02 Mar 2026 21:15
Thank you.

I made a local version of the site with the Cassiopeia template (and disabled some extentions).
Unfortunately, installing 6.4.9 over 6.3.10 failed again.:

Kunena 6.4 has not been installed, aborting!
Extension Update:
Custom install routine failure. Error installing package

Below is the Configuration Report for 6.3.10.

If it can help, I can try to arrange a temporary public URL where my WampServer will be accessible through the cpolar service.
UPDATE: Alternatively, I can upload the site file in the Akeeba Backup format (jpa or another) to my google drive and give it access.

This message contains confidential information

Database collation check: The collation of your table fields are correct
        

Joomla! SEF: Enabled | Joomla! SEF rewrite: Enabled | FTP layer: Disabled |
        

This message contains confidential information
htaccess: Exists | PHP environment: Max execution time: 120 seconds | Max execution memory: 512M | Max file upload:  

Kunena menu details:

Warning: Spoiler!

Joomla default template details : cassiopeia | author: Joomla! Project | version: 1.0 | creationdate: 2017-02

Kunena default template details : Aurelia | author: Kunena Team | version: 6.3.10 | creationdate: 2025-03-14

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.3.10 | 2025-03-14 [ Git Repository ]
        | Kunena detailed configuration:

Warning: Spoiler!
| Kunena integration settings:
Warning: Spoiler!
| Joomla! detailed language files installed:
Warning: Spoiler!

Third-party components: CommunityBuilder 2.11.0

Third-party SEF components: None

Plugins: None

Modules: Kunena Latest 6.0.7


 
02 Mar 2026 17:09

I'd tried to change the type to varchar(10).

Yes, it's varchar. The screenshot is from a K6.4.6 installation. Is there no longer an error message with varchar, not even with Error Reporting = Maximum?
.
 
01 Mar 2026 19:57
Hi, meanwhile I fixed the utf8mb3_general_ci problem - how ever the rank error still exists. My suspect is, that the data format for the table kunena_users column rank had somewhen changed (we're migrating from a very old version...). Old type was tinyint - how ever it looks like that Kunena 6.4.6 tries to store an other datatype what results in the error. I'd tried to change the type to varchar(10). That let the error message disappear - how ever nothing is written in the table and the rank system still doesn't work.

Do you have any ideas how to fix this?

THX
28 Feb 2026 19:01
Yes, Gindi, that's right, but this is usually fixed automatically when upgrading to 7.0.1. I have the configuration report for Joomla 5.4.4-dev and Kunena 6.3.10 here. I then updated to K6.4.5 and then to K7.0. This is the second configuration report. You can compare both yourself.

I remember that a long time ago, when the configuration table was changed, some users experienced errors, but these only affected the configuration itself. In any case, my old K6.3.10 also shows duplicate configurations in the report. However, this does not cause any errors.

Conf K6.3.10

This message contains confidential information

Database collation check: The collation of your table fields are correct
       

Joomla! SEF: Enabled | Joomla! SEF rewrite: Enabled | FTP layer: Disabled |
       

This message contains confidential information
htaccess: Exists | PHP environment: Max execution time: 60 seconds | Max execution memory: 384M | Max file upload:

Kunena menu details:

Warning: Spoiler!

Joomla default template details : cassiopeia | author: Joomla! Project | version: 1.0 | creationdate: 2017-02

Kunena default template details : Aurelia | author: Kunena Team | version: 6.3.10 | creationdate: 2025-03-14

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.3.10 | 2025-03-14 [ Git Repository ]
        | Kunena detailed configuration:

Warning: Spoiler!
| Kunena integration settings:
Warning: Spoiler!
| Joomla! detailed language files installed:
Warning: Spoiler!

Third-party components: CommunityBuilder 2.11.0+build.2026.01.12.21.55.56.a25ef0f6c

Third-party SEF components: None

Plugins: Content - Kunena Discuss 6.0.5

Modules: Kunena Latest 6.0.7 | Kunena Search 6.0.5


Upgraded from K6.3.10 -> K6.4.5 -> K7.0

This message contains confidential information

Database collation check: The collation of your table fields are correct
       

Joomla! SEF: Enabled | Joomla! SEF rewrite: Enabled | FTP layer: Disabled |
       

This message contains confidential information
htaccess: Exists | PHP environment: Max execution time: 60 seconds | Max execution memory: 384M | Max file upload: 

Kunena menu details:

Warning: Spoiler!

Joomla default template details : cassiopeia | author: Joomla! Project | version: 1.0 | creationdate: 2017-02

Kunena default template details : Aurelia | author: Kunena Team | version: 7.0.1 | creationdate: 2026-01-30

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 7.0.1 | 2026-01-30 [ Git Repository ]
        | Kunena detailed configuration:

Warning: Spoiler!
Kunena integration settings:
Warning: Spoiler!
| Joomla! detailed language files installed:
Warning: Spoiler!

Third-party components: CommunityBuilder 2.11.0+build.2026.01.12.21.55.56.a25ef0f6c

Third-party SEF components: None

Plugins: Content - Kunena Discuss 6.0.5

Modules: Kunena Latest 6.0.7 | Kunena Search 6.0.5




 
Displaying 16 - 30 out of 53 results.
Time to create page: 0.516 seconds