Kunena 7.0.4 Released

The Kunena team has announce the arrival of Kunena 7.0.4 [K 7.0.4] in stable which is now available for download as a native Joomla extension for J! 5.4.x/6.0.x. This version addresses most of the issues that were discovered in K 6.2 / K 6.3 / K 6.4 and issues discovered during the last development stages of K 7.0

Topics must relate to a currently supported version of Kunena. If you are unsure what is the current supported version of Kunena, please go to the download page.

If you are having problems then, for your own benefit, it would save us all a lot of time if you would kindly post your configuration report when you ask for help from this forum. If you do not post your configuration report we will not ask you for it but you will probably not get your problem solved, either.

Question Kunena & Captha

More
2 years 5 months ago - 2 years 5 months ago #230092 by Hifi2you
Kunena & Captha was created by Hifi2you
Hi.
After update to Joomla 5,0,1 and Kunena 6.1.4 it seems like Captha is gone ?

Is there anorther option ?
My web hotel provider does not like the fact that there is no captha
[img
Last edit: 2 years 5 months ago by Hifi2you.

Please Log in or Create an account to join the conversation.

More
2 years 5 months ago #230097 by rich
Replied by rich on topic Kunena & Captha
Is there an error message? What happens if you set the captcha for Guests and Registered in Kunena?
Important! Always create a backup before you make any changes to your website!

Please Log in or Create an account to join the conversation.

More
2 years 5 months ago - 2 years 5 months ago #230100 by Hifi2you
Replied by Hifi2you on topic Kunena & Captha
I don't know why there have to be errors all the time with this Kunena.
I have updated Joomla and Kunena and now a new user cannot be created and I do not receive an email about errors during creation.
It is so ridiculously annoying that there must be errors upon errors every time there is an update.I spoke to a Joomla consultant who said that Captha was gone after the update and he didn't know if it came back in Kunena 6.2.1.
Right now there is - again - not much that works.
Users are also not notified of new posts, etc.
So all in all, the update is a massive downgrade

This message contains confidential information

Database collation check: db2023_kunena_aliases have wrong collation of type utf8mb3_general_ci on field alias  db2023_kunena_aliases have wrong collation of type utf8mb3_general_ci on field type  db2023_kunena_aliases have wrong collation of type utf8mb3_general_ci on field item  db2023_kunena_announcement have wrong collation of type utf8mb3_general_ci on field title  db2023_kunena_announcement have wrong collation of type utf8mb3_general_ci on field sdescription  db2023_kunena_announcement have wrong collation of type utf8mb3_general_ci on field description  db2023_kunena_attachments have wrong collation of type utf8mb3_general_ci on field hash  db2023_kunena_attachments have wrong collation of type utf8mb3_general_ci on field folder  db2023_kunena_attachments have wrong collation of type utf8mb3_general_ci on field filename  db2023_kunena_attachments have wrong collation of type utf8mb3_general_ci on field filename_real  db2023_kunena_attachments have wrong collation of type utf8mb3_general_ci on field caption  db2023_kunena_categories have wrong collation of type utf8mb3_general_ci on field name  db2023_kunena_categories have wrong collation of type utf8mb3_general_ci on field alias  db2023_kunena_categories have wrong collation of type utf8mb3_general_ci on field accesstype  db2023_kunena_categories have wrong collation of type utf8mb3_general_ci on field channels  db2023_kunena_categories have wrong collation of type utf8mb3_general_ci on field description  db2023_kunena_categories have wrong collation of type utf8mb3_general_ci on field headerdesc  db2023_kunena_categories have wrong collation of type utf8mb3_general_ci on field class_sfx  db2023_kunena_categories have wrong collation of type utf8mb3_general_ci on field iconset  db2023_kunena_categories have wrong collation of type utf8mb3_general_ci on field params  db2023_kunena_configuration have wrong collation of type utf8mb3_general_ci on field params  db2023_kunena_logs have wrong collation of type utf8mb3_general_ci on field ip  db2023_kunena_logs have wrong collation of type utf8mb3_general_ci on field operation  db2023_kunena_messages have wrong collation of type utf8mb3_general_ci on field name  db2023_kunena_messages have wrong collation of type utf8mb3_general_ci on field email  db2023_kunena_messages have wrong collation of type utf8mb3_general_ci on field subject  db2023_kunena_messages have wrong collation of type utf8mb3_general_ci on field ip  db2023_kunena_messages have wrong collation of type utf8mb3_general_ci on field modified_reason  db2023_kunena_polls have wrong collation of type utf8mb3_general_ci on field title  db2023_kunena_polls_options have wrong collation of type utf8mb3_general_ci on field text  db2023_kunena_sessions have wrong collation of type utf8mb3_general_ci on field allowed  db2023_kunena_sessions have wrong collation of type utf8mb3_general_ci on field readtopics  db2023_kunena_smileys have wrong collation of type utf8mb3_general_ci on field code  db2023_kunena_smileys have wrong collation of type utf8mb3_general_ci on field location  db2023_kunena_smileys have wrong collation of type utf8mb3_general_ci on field greylocation  db2023_kunena_topics have wrong collation of type utf8mb3_general_ci on field subject  db2023_kunena_topics have wrong collation of type utf8mb3_general_ci on field first_post_message  db2023_kunena_topics have wrong collation of type utf8mb3_general_ci on field first_post_guest_name  db2023_kunena_topics have wrong collation of type utf8mb3_general_ci on field last_post_message  db2023_kunena_topics have wrong collation of type utf8mb3_general_ci on field last_post_guest_name  db2023_kunena_topics have wrong collation of type utf8mb3_general_ci on field params  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field status_text  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field view  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field signature  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field avatar  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field personalText  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field location  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field icq  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field yim  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field microsoft  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field telegram  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field vk  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field skype  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field twitter  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field facebook  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field google  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field myspace  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field linkedin  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field delicious  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field friendfeed  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field digg  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field instagram  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field qzone  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field weibo  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field wechat  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field apple  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field blogspot  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field flickr  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field bebo  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field websitename  db2023_kunena_users have wrong collation of type utf8mb3_general_ci on field websiteurl  db2023_kunena_users_banned have wrong collation of type utf8mb3_general_ci on field ip  db2023_kunena_users_banned have wrong collation of type utf8mb3_general_ci on field reason_private  db2023_kunena_users_banned have wrong collation of type utf8mb3_general_ci on field reason_public  db2023_kunena_users_banned have wrong collation of type utf8mb3_general_ci on field comments  db2023_kunena_users_banned have wrong collation of type utf8mb3_general_ci on field params  db2023_kunena_version have wrong collation of type utf8mb3_general_ci on field version  db2023_kunena_version have wrong collation of type utf8mb3_general_ci on field versionname  db2023_kunena_version have wrong collation of type utf8mb3_general_ci on field state  
 

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: 2048M | 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.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: UddeIm 3.7

Third-party SEF components: None

Plugins: Content - Kunena Discuss 6.0.2-DEV

Modules: Kunena Latest 6.0.2


 

 
Last edit: 2 years 5 months ago by Hifi2you.

Please Log in or Create an account to join the conversation.

More
2 years 5 months ago #230101 by 9themestore
Replied by 9themestore on topic Kunena & Captha
Hi,
The captcha has been removed from j5. You can check in the Joomla 5 core ( issues.joomla.org/tracker/joomla-cms/42033 ). Try to check in the plugin list on your site and publish it if it has been disabled.
- Please provide your site url if it has been lived.
- Please share tip if it worked fine with you.
- Don't be shy about using the "Thanks" button below if you found my comment helpful :)
The following user(s) said Thank You: Hifi2you

Please Log in or Create an account to join the conversation.

More
2 years 5 months ago - 2 years 5 months ago #230102 by ruud
Replied by ruud on topic Kunena & Captha
Kunena doesn't 'honor' the selected captcha plugin in Joomla Global Config. instead it uses the first capctha that 'responds' to the init and display triggers.
So if you want to switch captcha for kunena then you need to disable all captcha plugins except the one you want for your site.
What I also see in the code is that is assumes a Google captcha, so not sure if having a different captcha will work.
This needs testing.

edit: it hardcodes google recapctha settings into any captcha displayed, so this needs refactoring in the code to: 1. display the captcha set in Joomla global config 2. not do it's own implementation but build on the default Joomla captcha implementation.

This is something i could work on, but I am currently swamped with work and do not know how much work this will be... need to check that

 
sharing = caring
Last edit: 2 years 5 months ago by ruud.
The following user(s) said Thank You: xillibit

Please Log in or Create an account to join the conversation.

More
2 years 5 months ago #230103 by xillibit
Replied by xillibit on topic Kunena & Captha

Kunena doesn't 'honor' the selected captcha plugin in Joomla Global Config. instead it uses the first capctha that 'responds' to the init and display triggers.

 
Hello,

I will look to change that and load the plugin set in the Joomla! configuration panel
I don't provide support by PM, because this can be useful for someone else.

Please Log in or Create an account to join the conversation.

Time to create page: 0.327 seconds