Kunena 6.1.3.2 Released

The Kunena team has announce the arrival of Kunena 6.1.3.2 [K 6.1.3] which is now available for download as a native Joomla extension for J! 4.2.x/4.3.x. This version addresses most of the issues that were discovered in K 6.1.0 and issues discovered during the last development stages of K 6.1

Solved Attachments unrelated to any posts

More
4 months 1 week ago - 4 months 1 week ago #1 by lemur
Attachments unrelated to any posts was created by lemur
I found attachments unrelated to any posts. They also don't show the author's nickname.
 

At the same time, the image is shown in its place in the post.


Post #12399 "England 900-1600 wurde erstellt von Reiner" with the first image was created in May 2021, that is, on joomla 3.

How to fix it in Kunena Forum: Attachments ?
Thanks
----
This message contains confidential information

Database collation check: j3d_kunena_aliases have wrong collation of type utf8_unicode_ci on field alias  j3d_kunena_aliases have wrong collation of type utf8_unicode_ci on field type  j3d_kunena_aliases have wrong collation of type utf8_unicode_ci on field item  j3d_kunena_announcement have wrong collation of type utf8_unicode_ci on field title  j3d_kunena_announcement have wrong collation of type utf8_unicode_ci on field sdescription  j3d_kunena_announcement have wrong collation of type utf8_unicode_ci on field description  j3d_kunena_attachments have wrong collation of type utf8_unicode_ci on field hash  j3d_kunena_attachments have wrong collation of type utf8_unicode_ci on field folder  j3d_kunena_attachments have wrong collation of type utf8_unicode_ci on field filename  j3d_kunena_attachments have wrong collation of type utf8_unicode_ci on field filename_real  j3d_kunena_attachments have wrong collation of type utf8_unicode_ci on field caption  j3d_kunena_categories have wrong collation of type utf8_unicode_ci on field name  j3d_kunena_categories have wrong collation of type utf8_unicode_ci on field alias  j3d_kunena_categories have wrong collation of type utf8_unicode_ci on field icon  j3d_kunena_categories have wrong collation of type utf8_unicode_ci on field accesstype  j3d_kunena_categories have wrong collation of type utf8_unicode_ci on field channels  j3d_kunena_categories have wrong collation of type utf8_unicode_ci on field description  j3d_kunena_categories have wrong collation of type utf8_unicode_ci on field headerdesc  j3d_kunena_categories have wrong collation of type utf8_unicode_ci on field class_sfx  j3d_kunena_categories have wrong collation of type utf8_unicode_ci on field iconset  j3d_kunena_categories have wrong collation of type utf8_unicode_ci on field params  j3d_kunena_configuration have wrong collation of type utf8_unicode_ci on field params  j3d_kunena_logs have wrong collation of type utf8_general_ci on field ip  j3d_kunena_logs have wrong collation of type utf8_general_ci on field operation  j3d_kunena_messages have wrong collation of type utf8_unicode_ci on field name  j3d_kunena_messages have wrong collation of type utf8_unicode_ci on field email  j3d_kunena_messages have wrong collation of type utf8_unicode_ci on field subject  j3d_kunena_messages have wrong collation of type utf8_unicode_ci on field ip  j3d_kunena_messages have wrong collation of type utf8_unicode_ci on field modified_reason  j3d_kunena_polls_options have wrong collation of type utf8_unicode_ci on field text  j3d_kunena_sessions have wrong collation of type utf8_unicode_ci on field allowed  j3d_kunena_sessions have wrong collation of type utf8_unicode_ci on field readtopics  j3d_kunena_smileys have wrong collation of type utf8_unicode_ci on field code  j3d_kunena_smileys have wrong collation of type utf8_unicode_ci on field location  j3d_kunena_smileys have wrong collation of type utf8_unicode_ci on field greylocation  j3d_kunena_topics have wrong collation of type utf8_unicode_ci on field subject  j3d_kunena_topics have wrong collation of type utf8_unicode_ci on field first_post_message  j3d_kunena_topics have wrong collation of type utf8_unicode_ci on field first_post_guest_name  j3d_kunena_topics have wrong collation of type utf8_unicode_ci on field last_post_message  j3d_kunena_topics have wrong collation of type utf8_unicode_ci on field last_post_guest_name  j3d_kunena_topics have wrong collation of type utf8_unicode_ci on field params  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field status_text  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field view  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field signature  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field avatar  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field personalText  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field location  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field icq  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field yim  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field skype  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field twitter  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field facebook  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field myspace  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field linkedin  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field delicious  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field friendfeed  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field digg  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field blogspot  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field flickr  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field bebo  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field websitename  j3d_kunena_users have wrong collation of type utf8_unicode_ci on field websiteurl  j3d_kunena_users_banned have wrong collation of type utf8_unicode_ci on field ip  j3d_kunena_users_banned have wrong collation of type utf8_unicode_ci on field reason_private  j3d_kunena_users_banned have wrong collation of type utf8_unicode_ci on field reason_public  j3d_kunena_users_banned have wrong collation of type utf8_unicode_ci on field comments  j3d_kunena_users_banned have wrong collation of type utf8_unicode_ci on field params  j3d_kunena_version have wrong collation of type utf8_unicode_ci on field version  j3d_kunena_version have wrong collation of type utf8_unicode_ci on field versionname  j3d_kunena_version have wrong collation of type utf8_unicode_ci on field state  
        

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

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

Kunena menu details:

Warning: Spoiler!

Joomla default template details : purity_III | author: JoomlArt.com | version: 2.0.2 | creationdate: October 21th, 2022

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

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.0.11 | 2023-05-05 [ 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.0+build.2023.05.16.19.40.40.f3776312c

Third-party SEF components: None

Plugins: Content - Kunena Discuss 6.0.2-DEV

Modules: Kunena Latest 6.0.2

Last edit: 4 months 1 week ago by lemur.

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

More
4 months 1 week ago #2 by lemur
Replied by lemur on topic Attachments unrelated to any posts
I checked also another site and also found attachments on it that are not related to any posts. They also do not indicate the author's nickname.
 

At the same time, the images are shown in their places in the post.
Post #2847 was created on April 08, 2023, that is, on Joomla 4.2.8 and Kunena 6.0.9.1.
 
And this means that the error may be present now.

How to avoid such situations and how to fix it on the Kunena forum: Attachments ?

Thanks

---
This message contains confidential information

Database collation check: j3r_kunena_aliases have wrong collation of type utf8_unicode_ci on field alias  j3r_kunena_aliases have wrong collation of type utf8_unicode_ci on field type  j3r_kunena_aliases have wrong collation of type utf8_unicode_ci on field item  j3r_kunena_announcement have wrong collation of type utf8_unicode_ci on field title  j3r_kunena_announcement have wrong collation of type utf8_unicode_ci on field sdescription  j3r_kunena_announcement have wrong collation of type utf8_unicode_ci on field description  j3r_kunena_attachments have wrong collation of type utf8_unicode_ci on field hash  j3r_kunena_attachments have wrong collation of type utf8_unicode_ci on field folder  j3r_kunena_attachments have wrong collation of type utf8_unicode_ci on field filename  j3r_kunena_attachments have wrong collation of type utf8_general_ci on field filename_real  j3r_kunena_attachments have wrong collation of type utf8_general_ci on field caption  j3r_kunena_categories have wrong collation of type utf8_unicode_ci on field name  j3r_kunena_categories have wrong collation of type utf8_unicode_ci on field alias  j3r_kunena_categories have wrong collation of type utf8_general_ci on field icon  j3r_kunena_categories have wrong collation of type utf8_unicode_ci on field accesstype  j3r_kunena_categories have wrong collation of type utf8_unicode_ci on field channels  j3r_kunena_categories have wrong collation of type utf8_unicode_ci on field description  j3r_kunena_categories have wrong collation of type utf8_unicode_ci on field headerdesc  j3r_kunena_categories have wrong collation of type utf8_unicode_ci on field class_sfx  j3r_kunena_categories have wrong collation of type utf8_general_ci on field iconset  j3r_kunena_categories have wrong collation of type utf8_unicode_ci on field params  j3r_kunena_configuration have wrong collation of type utf8_unicode_ci on field params  j3r_kunena_logs have wrong collation of type utf8_general_ci on field ip  j3r_kunena_logs have wrong collation of type utf8_general_ci on field operation  j3r_kunena_messages have wrong collation of type utf8_unicode_ci on field name  j3r_kunena_messages have wrong collation of type utf8_unicode_ci on field email  j3r_kunena_messages have wrong collation of type utf8_unicode_ci on field subject  j3r_kunena_messages have wrong collation of type utf8_unicode_ci on field ip  j3r_kunena_messages have wrong collation of type utf8_unicode_ci on field modified_reason  j3r_kunena_polls_options have wrong collation of type utf8_unicode_ci on field text  j3r_kunena_sessions have wrong collation of type utf8_unicode_ci on field allowed  j3r_kunena_sessions have wrong collation of type utf8_unicode_ci on field readtopics  j3r_kunena_smileys have wrong collation of type utf8_unicode_ci on field code  j3r_kunena_smileys have wrong collation of type utf8_unicode_ci on field location  j3r_kunena_smileys have wrong collation of type utf8_unicode_ci on field greylocation  j3r_kunena_topics have wrong collation of type utf8_unicode_ci on field subject  j3r_kunena_topics have wrong collation of type utf8_unicode_ci on field first_post_message  j3r_kunena_topics have wrong collation of type utf8_unicode_ci on field first_post_guest_name  j3r_kunena_topics have wrong collation of type utf8_unicode_ci on field last_post_message  j3r_kunena_topics have wrong collation of type utf8_unicode_ci on field last_post_guest_name  j3r_kunena_topics have wrong collation of type utf8_unicode_ci on field params  j3r_kunena_users have wrong collation of type utf8_general_ci on field status_text  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field view  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field signature  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field avatar  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field personalText  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field location  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field icq  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field yim  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field skype  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field twitter  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field facebook  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field myspace  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field linkedin  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field delicious  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field friendfeed  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field digg  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field blogspot  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field flickr  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field bebo  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field websitename  j3r_kunena_users have wrong collation of type utf8_unicode_ci on field websiteurl  j3r_kunena_users_banned have wrong collation of type utf8_unicode_ci on field ip  j3r_kunena_users_banned have wrong collation of type utf8_unicode_ci on field reason_private  j3r_kunena_users_banned have wrong collation of type utf8_unicode_ci on field reason_public  j3r_kunena_users_banned have wrong collation of type utf8_unicode_ci on field comments  j3r_kunena_users_banned have wrong collation of type utf8_unicode_ci on field params  j3r_kunena_version have wrong collation of type utf8_unicode_ci on field version  j3r_kunena_version have wrong collation of type utf8_unicode_ci on field versionname  j3r_kunena_version have wrong collation of type utf8_unicode_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: 30 seconds | Max execution memory: 256M | Max file upload:  

Kunena menu details:

Warning: Spoiler!

Joomla default template details : purity_III | author: JoomlArt.com | version: 2.0.2 | creationdate: October 21th, 2022

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

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.0.11 | 2023-05-05 [ 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.0+build.2023.05.16.19.40.40.f3776312c

Third-party SEF components: None

Plugins: Content - Kunena Discuss 6.0.2-DEV

Modules: Kunena Latest 6.0.2

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

More
4 months 6 days ago #3 by rich
Replied by rich on topic Attachments unrelated to any posts
You have orphaned attachments in the database. You can test how to get orphaned attachments. Orphaned attachments occur when users upload attachments sloppily. This means that the user has used the browser's back button and again the forward button before saving. Kunena registers this as a cancel and does not enter a message ID for that image.
Or a user does not use the cancel button if they do not send their message after uploading the image. All these attachments will receive the mesid 0 in the #__kunena_attachments table and will be shown as orphaned in the diagnostic tool.
Example:
attachmentOrphaned - TEST FAILED - xx problems.

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

More
4 months 6 days ago #4 by lemur
Replied by lemur on topic Attachments unrelated to any posts
Thank you.

I will check these considerations and report them to the users.

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

More
4 months 5 days ago #5 by lemur
Replied by lemur on topic Attachments unrelated to any posts
I would like to make a few comments on the topic of this thread.

1. I performed diagnostics in Kunena Tools. And I received the message "attachment Orphaned - TEST FAILED - 3 problems".
OK, but at the same time, immediately after running the test, I was informed in the same line that orphaned attachments were removed.
But I didn't want that at all! Prior to the diagnosis, all orphan attachments were shown in their place. And now I had to look for these images in the backup of the site and insert them.

Suggestion: report such a diagnostic effect in the documentation, or ask a question about removal during diagnostics.

2. 

Orphaned attachments occur when users upload attachments sloppily. This means that the user has used the browser's back button and again the forward button before saving. Kunena registers this as a cancel and does not enter a message ID for that image.
Or a user does not use the cancel button if they do not send their message after uploading the image.


Suggestion: try to exclude such a possibility from the user, that is, enable "fool protection".

3. (Off top). What I noticed when inserting lost images. 
The current date has been added to the file names. 
That is, instead of Geozentrism.jpg a file appeared in the Kunena attachments as Geozentrism_2023-05-24.jpg .

Yesterday, when I created a new post, the date was not added to the file names. And now, when editing an existing post, it has been added. 
I don't see any problems in this, maybe it's even better, but this change caught my eye. If adding a date was conceived by the developers, then you may insert it also when creating a post.

Thanks.

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

More
4 months 3 days ago #6 by rich
Replied by rich on topic Attachments unrelated to any posts

1. I performed diagnostics in Kunena Tools. And I received the message "attachment Orphaned - TEST FAILED - 3 problems".
OK, but at the same time, immediately after running the test, I was informed in the same line that orphaned attachments were removed.

Orphaned attachments are only deleted when the Fix button is clicked.
.

Suggestion: report such a diagnostic effect in the documentation, or ask a question about removal during diagnostics.

There is a hint that items will be removed when you click on "Help".
.

What I noticed when inserting lost images.
The current date has been added to the file names.

The date is added if the same filename already exists. The diagnostic tool only removes orphaned database entries, but not the file.

Finally, a tip if you have experience with the database:
Orphaned attachments get the mesid 0.
If you know to which post ID the attachment belongs, you can also enter the correct mesid instead of 0 in the table #__kunena_attachments.
Then you don't have to upload the attachment again.
 
The following user(s) said Thank You: lemur

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

More
4 months 2 days ago #7 by lemur
Replied by lemur on topic Attachments unrelated to any posts
Thank you very much for the detailed and useful explanation.

"Orphaned attachments are only deleted when the Fix button is clicked."

Yes, I checked, it is. The problem I have (!) aroused due to a bad translation in the Russian version. In the German version, after pressing the button "Run Diagnostics to see if Kunena is working properly." the message "GEBROCHENE ELEMENTE LÖSCHEN" appears in the list of results. And in Russian - "орфанные файлы удалены" (in the past perfect tense).

The topic can be closed. 
[img
.

 

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

Time to create page: 0.453 seconds