Search Results (Searched for: you do not have)

08 Mar 2026 18:31
I don't know the reason why it pass an int instead a message object, i'am not able to reproduce. Do-you have a test site on which i have a FTP acess to try to investigate ?
08 Mar 2026 12:14

Hello,

The issue is still opened, it seems that the datepicker doesn't find the HTML item in the CKeditor context.

I will look for the see less which works for the first time and not for the others.

Hello, do you have any update about this issue? Thanks!

Hello, do you have any update about this issue? Do you think it will be fixed? Thanks.
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
04 Mar 2026 16:43 - 04 Mar 2026 16:55
When upgrading from K6.3 to K6.4, the database is adjusted. Because Twitter no longer exists, so this column, among others, also should be removed. For some reason, this column was not removed from the #__kunena_users table. However, this does not mean that this is always the case.
Have you tried the jpa file I uploaded? I don't know if you could see the private text.
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 (бесплатная версия) 
04 Mar 2026 11:48 - 04 Mar 2026 11:50
You have misunderstood something.
Since I wanted to create system equality for the test but did not have a backup with Joomla 5.4.3 and Kunena 6.3.10, I installed a backup with Joomla 5.4.3 and Kunena 6.4.8 and then completely deleted Kunena.
After that, I installed Kunena 6.3.10.
Then I updated Joomla 5.4.3 with Kunena 6.3.10 to Kunena 6.4.5.
I suspect that your error lies in the fact that a more recent version in English and an older version in Russian are present in the database at the same time.
Do these two versions have the same prefixes or are they different?
I don't know how to reproduce this error in my database. 
 
01 Mar 2026 23:07
Dear Gindi,
I really appreciate your support, although I'm very sorry that you're doing it even on weekends.
GiCh_site_template and GiCh_forum_template are custom templates made specifically for my websites, and they've worked perfectly well for me so far.

Tomorrow I'll set up the site and forum on Cassiopeia and let you know immediately.

However, I'd like to point out the following. Finding the error in the standard template could be important if other users have encountered a similar problem. On the one hand, given the huge number of Kunena users, this would be natural. But so far, I haven't noticed much interest in this topic.
On the other hand, it could be due to the somewhat "unique" nature of my websites—I've been using successive versions of Kunena almost since the very first versions, and over 18 years, some rudiments and pitfalls may have accumulated.

If this is the case, I'm willing to perform the update on a case-by-case basis.

Specifically: update the tables modified in K7 directly in phpMyAdmin, especially if the developers deem it possible to provide me with the appropriate scripts. Then I'll uninstall Kunena completely, as Rich suggested, install a clean version, fix the tables modified in K7 in the K6.3.10 tables backup, and import them into the database. I hope this plan works.

Although, of course, I'd prefer a regular solution.

Thanks again.
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




 
27 Feb 2026 22:49
Dear Rich,
I've been trying to implement your advice ever since. Unfortunately, without success.

I'm reporting on my progress, which might help you. Since I have two similar websites—one German and one Russian—I tried working on a local server with copies of both.

Since I don't have the Aurelia template on Joomla 5.4.3, I installed Cassiopeia - Default.

1. The Joomla installer! option in step 5 returned the message for both sites:
JInstaller: :Install: Unable to find XML file for package installation.
Incorrect date value: '' for column `mru`.`j5r_kunena_version`.`versiondate` at row 1
Error deleting package.
( ! ) Warning: Attempt to read property "version" on null in W:\wamp64\www\locde\administrator\manifests\packages\kunena\script.php on line 148
Call Stack ...

I couldn't find the cause of the problem with `versiondate` at row 1, so I'm copying the contents of both kunena_version tables:
Code:
SELECT * FROM j5d_kunena_version Daten für Tabelle j5d_kunena_version id    version    versiondate    installdate    build    versionname    sampleData    state 1    1.0.5RC2    2008-10-27    2008-11-22    817    Redwood    0     2    1.0.5    2008-12-01    2009-03-23    855    Redwood    0     3    1.0.6    2009-01-10    2009-03-23    870    Communicate    0     4    1.0.8    2009-02-17    2009-03-23    1166    Speakup!    0     5    1.0.9    2009-04-03    2009-04-06    1231    Sprich!    0     6    1.0.10    2009-05-21    2009-06-21    1344    Parier!    0     7    1.5.6    2009-10-02    2009-10-18    1806    Speaker    0     8    1.5.12    2010-06-19    2010-06-23    1897    Calificar    0     9    2.0.4    2013-01-18    2013-04-17        Pharmacopoeia    0     10    3.0.8    2015-04-05    2018-11-05        Imperium    0     11    4.0.11    2016-06-05    2018-11-11        Barcelona    0     12    4.0.12    2016-10-01    2018-11-11        Lima    0     13    5.1.7    2018-11-20    2018-12-07    5.1.7    Hyperion    0     14    5.1.8    2018-12-30    2019-01-08    5.1.8    Janus    0     15    5.1.9    2019-02-15    2019-02-24    5.1.9    Kerberos    0     16    5.1.10.1    2019-03-04    2019-03-14    5.1.10.1    Janus    0     17    5.1.12.1    2019-04-22    2019-05-06    5.1.12.1    Kerberos    0     18    5.1.13    2019-07-21    2019-07-22    5.1.13    Mimas    0     19    5.1.13.1    2019-07-22    2019-07-25    5.1.13.1    Mimas    0     20    5.1.14    2019-08-13    2019-08-13    5.1.14    Nix    0     21    5.1.15    2019-10-27    2019-10-30    5.1.15    Oberon    0     22    5.1.16    2020-03-17    2020-03-22    5.1.16    Pallene    0     23    5.1.17    2020-06-09    2020-06-09    5.1.17    Quaoar    0     24    5.1.18    2020-06-30    2020-07-19    5.1.18    Rhea    0     25    5.1.19    2020-08-15    2020-08-27    5.1.19    Tethys    0     26    5.2.0    2020-12-09    2020-12-22    5.2.0    Nyx    0     27    5.2.0    2020-12-09    2020-12-22    5.2.0    Nyx    0     28    5.2.1    2020-12-27    2020-12-28    5.2.1    Hebe    0     29    5.2.2    2021-01-13    2021-01-14    5.2.2    Iris    0     30    5.2.2    2021-01-13    2021-01-14    5.2.2    Iris    0     31    5.2.4    2021-04-04    2021-05-13    5.2.4    Koios    0     32    5.2.8    2022-01-01    2022-02-05    5.2.8    Alcora    0     33    6.0.9.1    2023-02-22    2023-03-26    6.0.9.1    Limana    1     34    6.0.10    2023-04-02    2023-04-02    6.0.10    Veglie    1     35    6.0.11    2023-05-05    2023-05-06    6.0.11    Brezovica    1     36    6.1.0    2023-05-29    2023-07-17    6.1.0    Sakko i Vantsetti    1     37    6.1.2    2023-07-08    2023-07-17    6.1.2    Lavizzara    1     38    6.1.3    2023-08-10    2023-08-17    6.1.3    Bruzella    1     39    6.1.3.1    2023-08-21    2023-08-27    6.1.3.1    Piedicavallo    1     40    6.1.3.2    2023-09-05    2023-09-16    6.1.3.2    Sophiana    1     41    6.1.4    2023-10-05    2023-10-16    6.1.4    Constantinovca    1     42    6.2.0    2023-10-17    2023-11-10    6.2.0    Cortinhola    1     43    6.2.1    2023-11-10    2023-11-10    6.2.1    Eianina    1     44    6.2.2    2023-12-09    2023-12-15    6.2.2    Lavertezzo    1     45    6.2.3    2024-01-11    2024-01-18    6.2.3    Fiadeira    1     46    6.2.4    2024-02-11    2024-02-13    6.2.4    Kozarno    1     47    6.2.5    2024-03-21    2024-03-22    6.2.5    Barbacena    1     48    6.2.6    2024-04-16    2024-04-16    6.2.6    Satarma    1     49    6.3.0    2024-04-22    2024-04-25    6.3.0    Roncegno    1     50    6.3.1    2024-05-16    2024-05-16    6.3.1    Bombile    1     51    6.3.2    2024-06-14    2024-06-16    6.3.2    Gerovo    1     52    6.3.3    2024-07-16    2024-07-20    6.3.3    Viceno    1     53    6.3.4    2024-08-16    2024-08-19    6.3.4    Segheria    1     54    6.3.5    2024-09-22    2024-10-06    6.3.5    Kolarina    1     55    6.3.6    2024-10-28    2024-11-10    6.3.6    Crampiolo    1     56    6.3.7    2024-11-26    2024-12-13    6.3.7    Mezzolago    1     57    6.3.8    2024-12-29    2025-01-03    6.3.8    Komarivka    1     58    6.3.9    2025-02-21    2025-02-22    6.3.9    Ligomena    1     59    6.3.10    2025-03-14    2025-05-04    6.3.10    Fondovalle    1     Daten für Tabelle j5r_kunena_version id    version    versiondate    installdate    build    versionname    sampleData    state 1    1.0.5RC2    2008-10-27    2008-11-22    817    Redwood    0     2    1.0.5    2008-12-01    2009-03-23    855    Redwood    0     3    1.0.6    2009-01-10    2009-03-23    870    Communicate    0     4    1.0.8    2009-02-17    2009-03-23    1166    Speakup!    0     5    1.0.9    2009-04-03    2009-04-06    1231    Sprich!    0     6    1.0.10    2009-05-21    2009-06-14    1344    Parier!    0     7    1.5.12    2010-06-19    2010-06-24    1897    Calificar    0     8    2.0.4    2013-01-18    2015-03-27        Pharmacopoeia    0     9    3.0.7    2015-02-01    2015-03-27        Galah    0     10    3.0.8    2015-04-05    2015-04-22        Imperium    0     11    4.0.11    2016-06-05    2018-11-10        Barcelona    0     12    4.0.12    2016-10-01    2018-11-10        Lima    0     13    5.1.6    2018-11-09    2018-11-10    5.1.6    Ganymede    0     14    5.1.7    2018-11-20    2018-12-22    5.1.7    Hyperion    0     15    5.1.8    2018-12-30    2019-01-08    5.1.8    Janus    0     16    5.1.9    2019-02-15    2019-02-26    5.1.9    Kerberos    0     17    5.1.10.1    2019-03-04    2019-03-14    5.1.10.1    Janus    0     18    5.1.12.1    2019-04-22    2019-05-06    5.1.12.1    Kerberos    0     19    5.1.13    2019-07-21    2019-07-22    5.1.13    Mimas    0     20    5.1.13.1    2019-07-22    2019-07-24    5.1.13.1    Mimas    0     21    5.1.14    2019-08-13    2019-08-13    5.1.14    Nix    0     22    5.1.14    2019-08-13    2019-10-17    5.1.14    Nix    0     23    5.1.15-DEV    2019-10-21    2019-10-21    5.1.15-DEV    Internal    0     24    5.1.15    2019-10-27    2019-10-30    5.1.15    Oberon    0     25    5.1.16    2020-03-17    2020-03-22    5.1.16    Pallene    0     26    5.1.17    2020-06-09    2020-06-09    5.1.17    Quaoar    0     27    5.1.18    2020-06-30    2020-07-19    5.1.18    Rhea    0     28    5.1.19    2020-08-15    2020-08-27    5.1.19    Tethys    0     29    5.2.0    2020-12-09    2020-12-22    5.2.0    Nyx    0     30    5.2.0    2020-12-09    2020-12-22    5.2.0    Nyx    0     31    5.2.1    2020-12-27    2020-12-28    5.2.1    Hebe    0     32    5.2.1    2020-12-27    2020-12-28    5.2.1    Hebe    0     33    5.2.2    2021-01-13    2021-01-14    5.2.2    Iris    0     34    5.2.4    2021-04-04    2021-05-13    5.2.4    Koios    0     35    5.2.8    2022-01-01    2022-02-05    5.2.8    Alcora    0     36    5.2.10.1    2022-09-28    2022-10-07    5.2.10.1    Queiriga    0     37    5.2.14    2022-12-14    2023-03-07    5.2.14    Tharsis    0     38    6.0.9.1    2023-02-22    2023-03-10    6.0.9.1    Limana    1     39    6.0.10    2023-04-02    2023-04-03    6.0.10    Veglie    1     40    6.0.11    2023-05-05    2023-05-06    6.0.11    Brezovica    1     41    6.1.0    2023-05-29    2023-07-13    6.1.0    Sakko i Vantsetti    1     42    6.1.2    2023-07-08    2023-07-13    6.1.2    Lavizzara    1     43    6.1.3    2023-08-10    2023-08-16    6.1.3    Bruzella    1     44    6.1.3.1    2023-08-21    2023-08-27    6.1.3.1    Piedicavallo    1     45    6.1.3.2    2023-09-05    2023-09-14    6.1.3.2    Sophiana    1     46    6.1.4    2023-10-05    2023-10-07    6.1.4    Constantinovca    1     47    6.2.1    2023-11-10    2023-11-11    6.2.1    Eianina    1     48    6.2.3    2024-01-11    2024-01-20    6.2.3    Fiadeira    1     49    6.2.4    2024-02-11    2024-02-13    6.2.4    Kozarno    1     50    6.2.5    2024-03-21    2024-03-22    6.2.5    Barbacena    1     51    6.2.6    2024-04-16    2024-04-16    6.2.6    Satarma    1     52    6.3.0    2024-04-22    2024-04-25    6.3.0    Roncegno    1     53    6.3.1    2024-05-16    2024-05-16    6.3.1    Bombile    1     54    6.3.2    2024-06-14    2024-06-16    6.3.2    Gerovo    1     55    6.3.3    2024-07-16    2024-07-20    6.3.3    Viceno    1     56    6.3.4    2024-08-16    2024-08-19    6.3.4    Segheria    1     57    6.3.5    2024-09-22    2024-10-06    6.3.5    Kolarina    1     58    6.3.6    2024-10-28    2024-11-10    6.3.6    Crampiolo    1     59    6.3.7    2024-11-26    2024-12-13    6.3.7    Mezzolago    1     60    6.3.8    2024-12-29    2025-01-03    6.3.8    Komarivka    1     61    6.3.9    2025-02-21    2025-02-21    6.3.9    Ligomena    1     62    6.3.10    2025-03-14    2025-03-17    6.3.10    Fondovalle    1    

As you can see, the sites have changed many versions – perhaps an error occurred somewhere along the way. But I don't recall a problem like this one.

I also tried finding the versiondate in all Kunena tables, but to no avail:
SHOW TABLES LIKE '_kunena_%';
_kunena_aliases
_kunena_announcement
_kunena_attachments
_kunena_categories
_kunena_configuration
_kunena_discussbot
_kunena_karma
_kunena_logs
_kunena_messages
_kunena_messages_text
_kunena_polls
_kunena_polls_options
_kunena_polls_users
_kunena_private
_kunena_private_attachment_map
_kunena_private_post_map
_kunena_private_user_map
_kunena_ranks
_kunena_rate
_kunena_sessions
_kunena_smileys
_kunena_thankyou
_kunena_topics
_kunena_user_categories
_kunena_user_read
_kunena_user_topics
_kunena_users
_kunena_users_banned
_kunena_version


To implement step 5, I tried removing all Kunena extensions through Extensions: Manage – everything was removed.

When installing Kunena 6.4.9, I got the error:
Kunena 6.4 has not been installed, aborting!
Extension: Installation: Error in custom installation script.
Package installation error.

I tried installing in two stages again - 6.3.10 - 6.4.5 and 6.4.5 - 6.4.9, but I got the errors described in the previous posts.
Deprecated: Creation of dynamic property Kunena\Forum\Libraries\Config\KunenaConfig::$_errors is deprecated in W:\wamp64\www\locru\libraries\src\Cache\Controller\OutputController.php on line 71
This message contains the word "Cache," but I disabled Cache as per your instructions.

2. Kunena -> Tools and remove Kunena completely

After completely removing Kunena, I
Imported the Kunena 6.3.10 Database tables and the folder media/kunena

Installing Kunena 6.4.9 returned the same error:
Kunena 6.4 has not been installed, aborting!
Extension: Update: Error in custom installation script.
Package installation error.

3. I tried installing 6.4.5 2025-08-23
Package installation completed successfully.

At this point, the contents of the kunena_version table were:
6.4.5 2025-08-23 2026-02-27 6.4.5 Montesiro 0

I was already looking forward to installing 6.4.9 over 6.4.5. And yes, I received:
Package installation completed successfully.
BUT the current version remains 6.4.5 (2025-08-23).
The kunena_version table hasn't changed either.

I'm attaching the Kunena detailed configuration for this site state.

I hope you find some useful information in my message.

I'm ready to provide you with any additional information immediately and, if necessary, grant you access to the server.

Thank you.

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.4.5 | creationdate: 2025-08-23

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.4.5 | 2025-08-23 [ 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

26 Feb 2026 22:35 - 26 Feb 2026 22:36
Hello,

Like said in another topic , i have made a pull request with a fix, so if you can try it please : github.com/Kunena/Kunena-Addons/pull/328 ?
26 Feb 2026 14:27
The Kunena menu is fine, only the menu item in the main menu (itemid 3022) that links to the forum is in the trash; it can be republished. 
I tried to reproduce the error using an old backup file (with CB, Kunena Discuss, and Kunena Latest), but I couldn't.

Try the following:
1. If you are using a cache, clear it and disable it.
2. Disable Kunena Discuss.
3. Disable Community Builder.
4. Select the Joomla default template Aurelia.
5. Uninstall Kunena via the Joomla installer!
5. Try to install Kunena 6.4.9 again.
If you get deprecated messages, scroll down and go to the Kunena dashboard and wait until the page has finished loading.
Then refresh the page again.

If does not help and you have Kunena database tables of Kunena 6.3.10, try these steps:
1. If you are using a cache, clear it and disable it.
2. Export the folder media/kunena as backup
3. Disable Kunena Discuss.
4. Disable Community Builder.
5. Select the Joomla default template Aurelia.
6. Go to Kunena -> Tools and remove Kunena complete
7. Import the Kunena 6.3.10 Database tables
8. Import the folder media/kunena
9. Install Kunena 6.4.9
You will see lots of deprecated messages.
Wait until the page has finished loading, then scroll all the way down. If you are not in the Kunena Dashboard, go there and wait again until the page has loaded. Then refresh the page again.
The disadvantage of this method is that you will then have to recreate the Kunena menus.
25 Feb 2026 21:23

Something is wrong with your Kunena detailed configuration:’ , the entries are duplicated.In the Kunena menu details, I am missing the entry mainmenu under menutype.

 
Thanks again for your comment. I couldn't figure it out until I found a link to troubleshooting recommendations for the Kunena menu in another thread: www.kunena.org/docs/en/troubleshooting/menu-issues .

I followed those recommendations, but unfortunately, I still can't upgrade from Kunena 6.3.10 to 6.4.9.

When installing 6.4.9 over 6.3.10, I get the message:
Kunena 6.4 has not been installed, aborting!
Extension: Update: Error in custom installation script.
Package installation error.

A two-step installation of 6.4.9—first installing 6.4.5 over 6.3.10, and then installing 6.4.9 on top of that—results in the following messages (both times): "Package installation completed successfully." , but it throws a bunch of errors:
( ! ) Deprecated: Creation of dynamic property Kunena\Forum\Libraries\Config\KunenaConfig::$_errors is deprecated in W:\wamp64\www\locru\libraries\src\Cache\Controller\OutputController.php on line 71. The dashboard shows version 6.4.5, and the forum doesn't work properly.

I kindly ask you to check the current state of Kunena. Have I fixed the error you mentioned: "I am missing the mainmenu entry under menutype."?

If not, what should I do?

Thanks in advance.

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 : 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

24 Feb 2026 14:29 - 24 Feb 2026 14:32
UPDATE 24 Feb 2026
I originally tried to upgrade Kunena to 7.0.1 on my Joomla 6.0.3 site and got the "Class "Kunena\Forum\Plugin\Kunena\Easysocial\Extension\Easysocial" not found" error. I don't use EasySocial on my site and the Kunena - EasySocial Integration plugin is disabled. Why does this error message happen?

Today I tried upgrading version 6.4.9 of Kunena on my Joomla 6.0.3 test site to 7.0.1 again, but this time the installation completely failed. After the failure I did not try and install pkg_kunena_languages_v7.0.1
I then uninstalled version 6.4.9 but the complete site stopped working, so I had to restore the database and files for a second time.

I believe I have met all the requirements for Kunena 7.0, except perhaps the following installed modules may have been developed for previous versions of Kunena? What should I do?
Kunena Statistics 6.2.0
Kunena Search 6.2.0
Kunena Latest 6.2.0

Lastly, my database is MySQLi 11.4.10-MariaDB, however the requirement is MySQL: version 8.4.0 or greater. Is this OK?

Thank you,

Andy
Displaying 46 - 60 out of 102 results.
Time to create page: 0.492 seconds