Search Results (Searched for: rank)

Today 11:38
Replied by stnw on topic Error - Unknown column 'a.rankId' in 'field list'
Hello,
no i don't opend it just after the update. There were some other errors after the Update, but they are fixed now.
So I don't konow if the Update actually is the reason of this Error.

There are no alerts about updates. I have Kunena Version 6.2.6 .

This two Errors are left (I think they are related):

If I click in the backend (components -> kunea Forum)  to the menue item "ranks" I get the message:
An error has occurred. Unknown column 'a.rankId' in 'field list' Unknown column 'a.rankId' in 'field list'
Button: Back to the dashboard

In the Frontend over a topic this message appears:
Warning: Undefined property: stdClass::$rankId in /var/www/html/libraries/vendor/joomla/database/src/DatabaseDriver.php on line 1382

 
Yesterday 15:41
Replied by xillibit on topic Error - Unknown column 'a.rankId' in 'field list'
Hello,

The Kunena tables hasn't been updated during the update from K5.x to K6.x

Did-you have opened the kunena dashboard just after the update ? Is-that showed some alert about updates ?
Yesterday 11:48
Error - Unknown column 'a.rankId' in 'field list' was created by stnw
Hello,
after the Update from Joomla 3 to Joomla 4 and Kunea 5 to Kunea 6, i become Error messages.

In top of a topic and next to an Admin-User this error message appears:
Warning: Undefined property: stdClass::$rankImage in /var/www/html/libraries/kunena/src/User/KunenaUser.php on line 1720
and/or
Warning: Undefined property: stdClass::$rankId in /var/www/html/libraries/vendor/joomla/database/src/DatabaseDriver.php on line 1382

And if I click in the backend (components -> kunea Forum)  to the menue item "ranks" I get the message:
An error has occurred. Unknown column 'a.rankId' in 'field list' Unknown column 'a.rankId' in 'field list'
Button: Back to the dashboard

Can anyone help me?

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: 30 seconds | Max execution memory: 128M | Max file upload:

Kunena menu details:

Warning: Spoiler!

Joomla default template details : YOOtheme | author: YOOtheme | version: 4.3.11 | creationdate: April 2024

Kunena default template details : Aurelia | author: Kunena Team | version: 6.2.6 | creationdate: 2024-04-16

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.2.6 | 2024-04-16 [ 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: None

22 Apr 2024 18:07 - 22 Apr 2024 22:22
Replied by derekk on topic protected category shows 500 error
EDIT:
This setting under security tab title "Registered Users Only" Set to Yes to limit all forum access to registered users (view and post).
Set to No to allow any Guest (non registered visitor) to at least see the forum. See 'Allow Guests to post/write' for additional Guest access control.

If I set to "no" then there is no 500 error for logged in or out going to forum both receive correct login message
If logged out go to protected category directly from link they get correct message without 500 error message.
If logged in go to protected category directly from link they get access to protected category correctly without 500 error message.
This is now working as expected

The problem remaining is that if If logged out go to forum or any category, whether the category is protected or not, they get the following
Please Log In
Only community members can participate in this forum. You must register or log in to contribute.

I want the main forum home page to be viewable by logged out showing to the public logged out viewers all the categories
and showing any category I set and want to be viewed by logged out
In other words I want Kunena to work correctly and show the categories I want to show to logged out and not shoow categories I have protected and do not want to show to   logged out with the correct message to log in to view.

If I set this to "yes" then the 500 error incorrectly shows to logged out visitors.
Please advise on how to correct this?

Dont know if this is related but I also get this system error message now?
Please check your Joomla menus: Default Menu Item in Entry Page is not pointing to Kunena.


















here is my configuration report
Please read my edited reply above as well?


This message contains confidential information

Database collation check: gic_guru_kunena_courseslinkage have wrong collation of type utf8_general_ci on field coursename gic_guru_kunena_lessonslinkage have wrong collation of type utf8_general_ci on field lessonname

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

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

Kunena menu details:

Warning: Spoiler!

Joomla default template details : t4_blank | author: JoomlArt | version: 1.1.4 | creationdate: January 14, 2022

Kunena default template details : Aurelia | author: Kunena Team | version: 6.2.0 | creationdate: 2023-10-17

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.2.0 | 2023-10-17 [ Git Repository ]
| Kunena detailed configuration:

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

Third-party components: CommunityBuilder 2.8.2

Third-party SEF components: None

Plugins: Content - Kunena Discuss 6.0.2-DEV

Modules: Kunena Latest 6.0.2 | Kunena Search 5.2.2

19 Apr 2024 12:03
Replied by stnw on topic Editor Field is missing
I just noticted. If I click in the backend (components -> kunea Forum)  to the menue item "ranks" I get the message:

An error has occurred. Unknown column 'a.rankId' in 'field list' Unknown column 'a.rankId' in 'field list'
Button: Back to the dashboard
19 Apr 2024 11:54
Replied by stnw on topic Editor Field is missing
I installed Kunena complete new on a test Website. Then I take a look in the database, table "kunena_smileys". And replace this database table with my old one.
Now the Editor ist working.

Only these Error Messages appears over a admin post:
Warning: Undefined property: stdClass::$rankId in /var/www/html/libraries/vendor/joomla/database/src/DatabaseDriver.php on line 1382
Warning: Undefined property: stdClass::$rankImage in /var/www/html/libraries/kunena/src/User/KunenaUser.php on line 1720
18 Apr 2024 14:08
Replied by stnw on topic Editor Field is missing
Hello rich,

I have repair these two menu items and update kunea to 6.2.6 but the descriped error messages are still there. Also the Editor field is missing.

Here the new Configuration report:

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: 30 seconds | Max execution memory: 128M | Max file upload:

Kunena menu details:

Warning: Spoiler!

Joomla default template details : YOOtheme | author: YOOtheme | version: 4.3.11 | creationdate: April 2024

Kunena default template details : Aurelia | author: Kunena Team | version: 6.2.6 | creationdate: 2024-04-16

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.2.6 | 2024-04-16 [ 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: None

18 Apr 2024 12:24
Editor Field is missing was created by stnw
Hello,
after the Update from Joomla 3 to Joomla 4 and Kunea 5 to Kunea 6, i become Error messages.

In top of a topic and next to an Admin-User this error message appears:
Warning: Undefined property: stdClass::$rankImage in /var/www/html/libraries/kunena/src/User/KunenaUser.php on line 1720
or
Warning: Undefined property: stdClass::$rankId in /var/www/html/libraries/vendor/joomla/database/src/DatabaseDriver.php on line 1382

The next Error is when i want to answer to a topic or click on "new topic". I can't write any text because the Editor field missing. Just the field "subject" is there. Instead of the editor field this error message appears:
Rendering Error in layout Widget/Editor: The image file does not exist. in /var/www/html/components/com_kunena/template/aurelia/layouts/widget/editor/ckeditor.php on line 49
Layout was rendered in /var/www/html/components/com_kunena/template/aurelia/layouts/topic/edit/default.php on line 373

Can anyone help me?



This message contains confidential information

Database collation check: st_kunena_logs have wrong collation of type utf8mb3_general_ci on field ip st_kunena_logs have wrong collation of type utf8mb3_general_ci on field operation st_kunena_ranks have wrong collation of type utf8mb3_general_ci on field rank_title st_kunena_ranks have wrong collation of type utf8mb3_general_ci on field rank_image st_kunena_sessions have wrong collation of type utf8mb3_general_ci on field allowed st_kunena_sessions have wrong collation of type utf8mb3_general_ci on field readtopics st_kunena_smileys have wrong collation of type utf8mb3_general_ci on field code st_kunena_smileys have wrong collation of type utf8mb3_general_ci on field location st_kunena_smileys have wrong collation of type utf8mb3_general_ci on field greylocation st_kunena_user_categories have wrong collation of type utf8mb3_general_ci on field params st_kunena_user_topics have wrong collation of type utf8mb3_general_ci on field params st_kunena_users have wrong collation of type utf8mb3_general_ci on field status_text st_kunena_users have wrong collation of type utf8mb3_general_ci on field view st_kunena_users have wrong collation of type utf8mb3_general_ci on field signature st_kunena_users have wrong collation of type utf8mb3_general_ci on field avatar st_kunena_users have wrong collation of type utf8mb3_general_ci on field personalText st_kunena_users have wrong collation of type utf8mb3_general_ci on field location st_kunena_users have wrong collation of type utf8mb3_general_ci on field icq st_kunena_users have wrong collation of type utf8mb3_general_ci on field yim st_kunena_users have wrong collation of type utf8mb3_general_ci on field skype st_kunena_users have wrong collation of type utf8mb3_general_ci on field twitter st_kunena_users have wrong collation of type utf8mb3_general_ci on field facebook st_kunena_users have wrong collation of type utf8mb3_general_ci on field myspace st_kunena_users have wrong collation of type utf8mb3_general_ci on field linkedin st_kunena_users have wrong collation of type utf8mb3_general_ci on field delicious st_kunena_users have wrong collation of type utf8mb3_general_ci on field friendfeed st_kunena_users have wrong collation of type utf8mb3_general_ci on field digg st_kunena_users have wrong collation of type utf8mb3_general_ci on field blogspot st_kunena_users have wrong collation of type utf8mb3_general_ci on field flickr st_kunena_users have wrong collation of type utf8mb3_general_ci on field bebo st_kunena_users have wrong collation of type utf8mb3_general_ci on field websitename st_kunena_users have wrong collation of type utf8mb3_general_ci on field websiteurl st_kunena_users_banned have wrong collation of type utf8mb3_general_ci on field ip st_kunena_users_banned have wrong collation of type utf8mb3_general_ci on field reason_private st_kunena_users_banned have wrong collation of type utf8mb3_general_ci on field reason_public st_kunena_users_banned have wrong collation of type utf8mb3_general_ci on field comments st_kunena_users_banned have wrong collation of type utf8mb3_general_ci on field params

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

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

Kunena menu details:

Warning: Spoiler!

Joomla default template details : YOOtheme | author: YOOtheme | version: 4.3.11 | creationdate: April 2024

Kunena default template details : Aurelia | author: Kunena Team | version: 6.1.4 | creationdate: 2023-10-05

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.1.4 | 2023-10-05 [ 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: None

06 Apr 2024 15:50 - 06 Apr 2024 15:52
Replied by zumbador on topic Getting a fatal error when accessing profile
Did not see any errors with error reporting. Here is the page I get when I try to edit my profile. Configuration follows. 


#FunctionLocation1()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:10652FWD\Illuminate\Foundation\Application->abort()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php:423fwd_abort()JROOT/components/com_jreviews/routes/web-legacy-joomla.php:1204JReviewsLegacyRouting()JROOT/components/com_jreviews/routes/web.php:735FWD\Illuminate\Support\ServiceProvider->{closure}()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/CallableDispatcher.php:366FWD\Illuminate\Routing\CallableDispatcher->dispatch()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Route.php:2067FWD\Illuminate\Routing\Route->runCallable()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Route.php:1818FWD\Illuminate\Routing\Route->run()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Router.php:6789FWD\Illuminate\Routing\Router->FWD\Illuminate\Routing\{closure}()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:12410FWD\Illuminate\Pipeline\Pipeline->FWD\Illuminate\Pipeline\{closure}()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php:4411FWD\Illuminate\Routing\Middleware\SubstituteBindings->handle()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:15812FWD\Illuminate\Pipeline\Pipeline->FWD\Illuminate\Pipeline\{closure}()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:10113FWD\Illuminate\Pipeline\Pipeline->then()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Router.php:67814FWD\Illuminate\Routing\Router->runRouteWithinStack()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Router.php:66515FWD\Illuminate\Routing\Router->runRoute()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Router.php:63816FWD\Illuminate\Routing\Router->dispatchToRoute()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Router.php:62817FWD\Illuminate\Routing\Router->dispatch()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:15018FWD\Illuminate\Foundation\Http\Kernel->FWD\Illuminate\Foundation\Http\{closure}()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:12419FWD\Illuminate\Pipeline\Pipeline->FWD\Illuminate\Pipeline\{closure}()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Http/Middleware/HandleCors.php:4520FWD\Illuminate\Http\Middleware\HandleCors->handle()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:15821FWD\Illuminate\Pipeline\Pipeline->FWD\Illuminate\Pipeline\{closure}()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:10122FWD\Illuminate\Pipeline\Pipeline->then()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:12823FWD\Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:10924FWD\Illuminate\Foundation\Http\Kernel->handle()JROOT/components/com_s2framework/build/bootstrap/joomla.php:9325s2framework\s2_dispatch()JROOT/components/com_jreviews/jreviews/cms_compat/joomla/bootloader.php:1326require()JROOT/components/com_jreviews/joomla.php:2627JReviews\JReviews->__invoke()JROOT/components/com_jreviews/jreviews.php:2528require_once()JROOT/libraries/src/Dispatcher/LegacyComponentDispatcher.php:7129Joomla\CMS\Dispatcher\LegacyComponentDispatcher::Joomla\CMS\Dispatcher\{closure}()JROOT/libraries/src/Dispatcher/LegacyComponentDispatcher.php:7330Joomla\CMS\Dispatcher\LegacyComponentDispatcher->dispatch()JROOT/libraries/src/Component/ComponentHelper.php:36131Joomla\CMS\Component\ComponentHelper::renderComponent()JROOT/libraries/src/Application/SiteApplication.php:21832Joomla\CMS\Application\SiteApplication->dispatch()JROOT/libraries/src/Application/SiteApplication.php:26133Joomla\CMS\Application\SiteApplication->doExecute()JROOT/libraries/src/Application/CMSApplication.php:30634Joomla\CMS\Application\CMSApplication->execute()JROOT/includes/app.php:5835require_once()JROOT/index.php:32



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: 30 seconds | Max execution memory: 128M | Max file upload:  

Kunena menu details:

Warning: Spoiler!

Joomla default template details : shaper_helixultimate | author: JoomShaper.com | version: 2.0.18 | creationdate: Feb 2018

Kunena default template details : Aurelia | author: Kunena Team | version: 6.2.5 | creationdate: 2024-03-21

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.2.5 | 2024-03-21 [ 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 Login 6.0.6

22 Mar 2024 13:18
Error while rendering KunenaLayout was created by stnw
Hello,
after the Update from Joomla 3 to Joomla 4 and Kunea 5 to Kunea 6, i become an Error message. If i click to "new topic" or if i want to read an old topic i get this error message:

Error while rendering KunenaLayout.
Table 'xx.xx_kunena_private' doesn't exist

I changend the template to the Joomla Standard Template Cassiopeia, but here also the same Error message.
Have anyone an idea where the error comes from?

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: 30 seconds | Max execution memory: 128M | Max file upload:

Kunena menu details:

Warning: Spoiler!

Joomla default template details : YOOtheme | author: YOOtheme | version: 4.3.8 | creationdate: March 2024

Kunena default template details : Aurelia | author: Kunena Team | version: 6.2.5 | creationdate: 2024-03-21

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.2.5 | 2024-03-21 [ 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: Content - Kunena Discuss 6.0.5

Modules: Kunena Latest 6.0.5 | Kunena Stats 6.0.5 | Kunena Login 6.0.6 | Kunena Search 6.0.5

03 Mar 2024 17:02
Replied by ruud on topic Kunena 6.3.0-BETA2-DEV User incorrect filter options
Hi Gindi,
that is 'correct'. this is due to both fields (rank and banned) being dynamically assigned a value after (!) the data is fetched (sorted) from the database.
so the sorting is correct, but because banned rank is set after the data has been fectched it sorts not okay. Same for banned field: this sorts okay but after the sorting the banned field for blocked users is set to banned so these are not sorted as banned )because basically they are not banned but blocked).

Need to think if this can be solved in another way, maybe Xillibit has an idea?
03 Mar 2024 09:15
Replied by Gindi on topic Kunena 6.3.0-BETA2-DEV User incorrect filter options
Do the changes to the J5 view in the user area only relate to the filter options or to "Sort table by:" ?
I have noticed that the sorting works well almost everywhere, only for "Rank" and "Banned" there is no sorting.
My Kunena 6.3.0-BETA is up to date as of 02.03.2024

gindi
 
29 Feb 2024 09:16 - 29 Feb 2024 09:17
Replied by ruud on topic Kunena 6.3.0-BETA2-DEV User incorrect filter options
Hi, just took a deeper dive into the code and the banned status of a user can have two 'meanings'.
When a user is banned, the banned field in the database is set (with a banned date).

When selecting 'banned=yes' in the users view that is where the filter is acting on: list the users that have a banned date set.

but.....

The user is also listed as banned when he is blocked. So a blocked user is also labeled banned, but actually is not banned as the banned date is not filled in.

so if you have 5 blocked users and 1 user actually banned, then 6 users will have the 'ranks' banned and the banned toggle for these users will be set to yes

when you filter on blocked, then only the 5 blocked users will display,
when you filter on banned then only the one user (who is actually banned) will be displayed.

This is confusing and I think this is what is causing this issue here...

Code:
    /**      * Return if the user is banned, there are two cases banned for life (9999-12-31 23:59:59) and banned for a short      * time with a date in near future      *      * @return  boolean      *      * @since   Kunena 6.0      */     public function isBanned()     {         if (!$this->banned) {             return false;         }         if ($this->blocked] || $this->banned == '9999-12-31 23:59:59') {             return true;         }         $expiration = new Date($this->banned);         $now        = new Date();         if ($expiration->toUnix() > $now->toUnix() && $expiration->toUnix() < '9999-12-31 23:59:59') {             return true;         }     }
 
28 Feb 2024 13:18
Session timeout was created by makitso
Joomla 4.4.3, Kunena  6.2.4.
I have the Joomla timeout is set to 60 minutes. The kunena session timeout is set to 3600 seconds. 
However, I have Kunena users complaining about their session timing out while editing a post sooner than these limits.
Am I missing somethin

This message contains confidential information

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

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

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

Kunena menu details:

Warning: Spoiler!

Joomla default template details : cassiopeia_webtrees | author: Rob | version: 1.0 | creationdate: August 2023

Kunena default template details : Aurelia | author: Kunena Team | version: 6.2.4 | creationdate: 2024-02-11

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.2.4 | 2024-02-11 [ 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.0.5 | Kunena Search 6.0.5



 
22 Feb 2024 23:33
"404 - View not found [name, type, prefix]: topic, html, site" error was created by beanman1
When clicking Reply, Quote, Edit, Moderate, or Delete, I get the 404 - View not found [name, type, prefix]: topic, html, site error screen.  The only button that works is Quick Reply.  

Figured it was a version issue, so I updated Joomla and Kunena as well as a new template and the issue persists.

Attached is the 404 error with the F12 Console details showing.   

Any ideas on how to fix this?

This message contains confidential information

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

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

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

Kunena menu details:

Warning: Spoiler!

Joomla default template details : a4joomla-dark-free | author: a4joomla.com | version: 4.0 | creationdate: Oct 2021

Kunena default template details : NTS KUnity | author: Nice Theme Store Team | version: 6.1.3 | creationdate: 2024-02-16

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.2.4 | 2024-02-11 [ 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.0.5 | Kunena Search 6.0.5

Displaying 1 - 15 out of 7470 results.
Time to create page: 2.386 seconds