Kunena 6.2.6 released

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

Solved Migrated posts cannot be edited

More
1 year 5 months ago #1 by mark0w
after updating to the latest version 6.0.4, you still cannot edit pre-migration posts.

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

More
1 year 5 months ago #2 by rich
Do you have experience with the database? With phpMyAdmin you can insert this sql command. Instead of #__ you have to enter your prefix.
UPDATE `#__kunena_messages` SET `email` = NULL;
This should solve the problem, but create a database backup first.

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

More
1 year 5 months ago - 1 year 5 months ago #3 by mark0w
You will not be confused by the title of the topic that I put on from an unsolved thread that has been closed.

After upgrading to 6.0.4, as I edited posts from pre-migration, the message "Cannot save message: Invalid email address!" problem no longer exists and changes (edit post) are not taken into account. After pressing save just nothing happens (returns to its original state without any message).

It's ok in new posts. This is for pre-migration posts.
Last edit: 1 year 5 months ago by mark0w.

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

More
1 year 5 months ago #4 by rich
Have you already recounted the statistics and synchronized the users (in the Backend -> Kunena ->Tools)?
If that does not help, open the browser console (press F12) and edit a post. Maybe an error message will be displayed.

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

More
1 year 5 months ago #5 by mark0w
After calculating the statistics and synchronizing the users (done positively),
after editing a post from before migration, now two known messages are displayed:

1) The message has been successfully edited - (this is not true because no changes have been made).
2) Cannot save message: Invalid email address!

Briefly describing it is as it was before the update to 6.0.4.

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

More
1 year 5 months ago #6 by rich
Maybe this table was not adjusted properly during the upgrade. Try what I suggested in my first answer.

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

More
1 year 5 months ago #7 by mark0w
My base prefix is ​​"new".
Should the query be like this?

Instead of #__new. UPDATE `new__kunena_messages` SET `email` = NULL;

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

More
1 year 5 months ago - 1 year 5 months ago #8 by mark0w


My test version is here:

: slash slash willanowa dot pl slash zone2

Log in to the test account with administrator rights and try to edit any post.
This message contains confidential information

Part of the message is hidden for the guests. Please log in or register to see it.
Last edit: 1 year 5 months ago by mark0w.

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

More
1 year 5 months ago #9 by Leen
Hi, I don't think it's really wise to post a login with administrator data.
better to hide something like that
secret = only visible to moderators hidden = not visible to guests
but it's true that he reports wrong email address if you want to update a message. Can an e-mail address be used more than once? And can you post a Report Configuration here

L.v.d.A
Attachments:

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

More
1 year 5 months ago #10 by mark0w
ok, I hid my login details.
The e-mail address can ONLY be used once.

This message contains confidential information

Part of the message is hidden for the guests. Please log in or register to see it.


This message contains confidential information

Part of the message is hidden for the guests. Please log in or register to see it.

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

Time to create page: 0.936 seconds