Search Results (Searched for: message)

08 Mar 2026 14:10 - 08 Mar 2026 14:10

Then I completely deactivated your Joomla template Gich via extensions and used Joomla's default htaccess during installation. 
I also reinstalled K6.3.10 over it before the upgrade.
The upgrade from K6.3.10 -> K6.4.9 -> K7.0.2 went smoothly.
Finally, I removed the database column “twitter” to fix an error message related to it.
The forum is now running smoothly.

 
Dear Rich,
no matter how hard I tried, I couldn't repeat this operation on the German website. Therefore, I kindly ask you to install K7 on your server and provide me with the received file as last time. On the first site, K7.0.2 works fine.
In this file, I completely deactivated my templates and used Joomla's default template Cassiopia.
I also reinstalled K6.3.10. 
Before updating K6.3.10, to reduce the file size by half, I copied and deleted the /media/kunena folder, so that it does not contain any data now.
Thank you.

This message contains confidential information


 
08 Mar 2026 11:03 - 08 Mar 2026 11:07
Hi tried this but still got this error showing after the Thank you.

0
Kunena6ActivityEasySocial::onAfterThankyou(): Argument #3 ($message) must be of type int, Kunena\Forum\Libraries\Forum\Message\KunenaMessage given, called in /var/www/vhosts/site.com/httpdocs/libraries/kunena/src/Integration/KunenaActivity.php on line 101
07 Mar 2026 15:59
Hi with the new kunena 7.0.2 with Joomla 6.0.3 and php 8.4.18 I got this error, any tips what is wrong, when doing a Thank you for a post:0Kunena6ActivityEasySocial::onAfterThankyou(): Argument #3 ($message) must be of type int, Kunena\Forum\Libraries\Forum\Message\KunenaMessage given, called in /var/www/vhosts/site.com/httpdocs/libraries/kunena/src/Integration/KunenaActivity.php on line 101
07 Mar 2026 15:29 - 07 Mar 2026 15:31
We have seen that a "Quick Reply" leads to a website "404" error.
BTW, a "Reply" (not Quick Reply) seems to be working.

12 {main}
2026-03-06T13:01:11+00:00 CRITICAL 212.39.101.112 error Uncaught Throwable of type Error thrown with message "Call to undefined method Joomla\CMS\Document\HtmlDocument::addItem()". Stack trace: #0 [ROOT]/components/com_kunena/src/Controller/Application/Category/Feed/CategoryDisplay.php(99): Kunena\Forum\Site\Controller\Application\Category\Feed\CategoryDisplay->createItem()
#1 [ROOT]/libraries/kunena/src/Controller/KunenaControllerDisplay.php(150): Kunena\Forum\Site\Controller\Application\Category\Feed\CategoryDisplay->before()
#2 [ROOT]/components/com_kunena/src/Dispatcher/Dispatcher.php(107): Kunena\Forum\Libraries\Controller\KunenaControllerDisplay->execute()
#3 [ROOT]/libraries/src/Component/ComponentHelper.php(361): Kunena\Forum\Site\Dispatcher\Dispatcher->dispatch()
#4 [ROOT]/libraries/src/Application/SiteApplication.php(217): Joomla\CMS\Component\ComponentHelper::renderComponent()
#5 [ROOT]/libraries/src/Application/SiteApplication.php(271): Joomla\CMS\Application\SiteApplication->dispatch()
#6 [ROOT]/libraries/src/Application/CMSApplication.php(320): Joomla\CMS\Application\SiteApplication->doExecute()
#7 [ROOT]/includes/app.php(58): Joomla\CMS\Application\CMSApplication->execute()
#8 [ROOT]/index.php(51): require_once('...')
#9 {main}
2026-03-06T13:02:05+00:00 CRITICAL 185.191.171.17 error Uncaught Throwable of type Twig\Error\RuntimeError thrown with message "An exception has been thrown during the rendering of a template ("DOM Error 76: Unexpected end tag : head
 while parsing:
<!doctype html>
<html><head>    <link rel="stylesheet" href="gantry-engine://css-compiled/nucleus.css" type="text/css"/>
                <link rel="stylesheet" href="epsilon.scss" type="text/css"/>            <br />
<b>Deprecated</b>:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in <b>[ROOT]/libraries/gantry5/compat/vendor/twig/twig/src/Extension/CoreExtension.php</b> on line <b>996</b><br />
   
                                     <link rel="stylesheet" href="/media/gantry5/engines/nucleus/css-compiled/bootstrap5.css?69a3a543" type="text/css" />
                        <link rel="stylesheet" href="/media/system/css/joomla-fontawesome.min.css" type="text/css" />
           
                                    <link rel="stylesheet" href="/media/plg_system_debug/css/debug.css" type="text/css"/>
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
05 Mar 2026 21:41 - 05 Mar 2026 21:45
I did not receive any error messages in any of my test versions.

When I hover over ‘Select All’ with the mouse in Joomla 5.4.3 and Kunena 6.4.8, right-click and then click on Inspect (Q), a blue line is displayed.
<a id="link_sel_all" class="btn btn-small btn-outline-primary" href="#" name="link-sel-all" type="button"> (event)
The # has an underscore and event is in a light-coloured ‘bubble’.
At the very bottom, under the bin, it says ‘Copying text command was successful’. 

When I perform the same operation in Joomla 6.0.0 and Kunena 6.4.8, (event) is missing from the blue line and at the very bottom it says: ‘For further info see ’https://en.wikipedia.org/wiki/Self-XSS‘ 

gindi
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 18:07
Hello,

I have something in K7.0.2 to fix that when update hadn't it. You need to make a backup of table #__kunena_users, then when your are logged in backend you have to call this url : administrator/index.php?option=com_kunena&task=tools.setupcolumnlanguage
04 Mar 2026 16:27 - 04 Mar 2026 16:28
@rich
Excellent. Now I need to repeat the same steps you took.

So far, it hasn't worked.
I deleted my Gich template.
I deleted everything with the word Kunena in Joomla.
However, I still got: Warning
Incorrect date value: '' for column `mde`.`j5r_kunena_version`.`versiondate` at row 1
Did you get this message? 
Maybe this is important?

I reinstalled K6.3.10. - OK.

Then I installed K6.4.9 and again got:
Kunena 6.4 has not been installed, aborting!
Etension Install: Custom install routine failure.
Error installing package

The main thing is that now I can be sure that the problem is solved (and judging by your description, it's easy).
But I need to figure out what's wrong with me.

This is a premature question, but could you please clarify the statement "I removed the database column 'twitter' to fix an error message related to it." Was this already done in K7.0.2? In which table?  @rich
 
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 14:57 - 04 Mar 2026 15:03
First, I had to increase the database size in Xammp, as it didn't work with the default size because you have quite large tables.
Then I completely deactivated your Joomla template Gich via extensions and used Joomla's default htaccess during installation. 
I also reinstalled K6.3.10 over it before the upgrade.
The upgrade from K6.3.10 -> K6.4.9 -> K7.0.2 went smoothly.
Finally, I removed the database column “twitter” to fix an error message related to it.
The forum is now running smoothly.
I posted the link to download the file privately and removed your links to Google Drive in your message. You should never disclose such information publicly.
03 Mar 2026 22:23

In my test version, I updated to Kunena 6.4.5 via System/Install/Extensions with the files pkg_kunena_v.6.4.5_2025-08-23.zip and pkg_kunena_languages_v.6.4.5_2025-08-23.zip without any error messages. 

 
Thank you so much.
I wanted to follow your path, but I don't understand how to upgrade from the test version with Kunena 6.4.8 to the version with my data. And doesn't 6.4.8 have a different database structure than 6.3.9? Or have I misunderstood, and you haven't worked with my data either?
I hope to receive detailed instructions.

If you've reached 6.4.5 with my data, perhaps you could try further upgrades to 6.4.9 and 7.0.1?
03 Mar 2026 21:16 - 03 Mar 2026 21:21
The configuration report for 6.3.10 still contains duplicate entries in different versions.
I created a test version on localhost with a backup of Joomla 5.4.3 and Kunena 6.4.8.
Then I completely deleted Kunena 6.4.8 and installed Kunena 6.3.10.The version was now Joomla 5.4.3 and Kunena 6.3.10. I then compared the latest configuration report from lemur with mine in the test version.
In my configuration report, under Kunena detailed configuration: the last three lines are ‘blueskyappHandleOf App , blueskyappPasswordOfApp and mailBodyUserUnBanned’.
Lemur instead shows ‘mailBodyUserBanned, twitterConsumerKey and twitterConsumerSecret’.
After that, the repetition begins with ‘board_title’.
In my test version, I updated to Kunena 6.4.5 via System/Install/Extensions with the files pkg_kunena_v.6.4.5_2025-08-23.zip and pkg_kunena_languages_v.6.4.5_2025-08-23.zip without any error messages. 
 
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!
Displaying 91 - 105 out of 320 results.
Time to create page: 0.302 seconds