Kunena 7.1.1 & Kunena 6.4.17 – Security Updates Released

The Kunena team has announce the arrival of Kunena 7.1.1 [K 7.1.1] in stable which is now available for download as a native Joomla extension for J! 5.4.x/6.0.x./6.1.x./6.2.x This version addresses most of the issues that were discovered in K 6.2 / K 6.3 / K 6.4 / K7.0 and issues discovered during the last development stages of K 7.1
Just a reminder: K6.4.17 receives only securities fixes until end of 2026, so it's advised for users to upgrade to K7.1.

Topics that are moved into this category are generally considered to be closed. Users may want to add additional information but these topics should not be resurrected in order to discuss new problems or unrelated matters.

Solved Need help with mySQL command / purging deleted topics

More
14 years 1 month ago #135152 by GJSchaller
I migrated from Kunena 1.7 to 2.0, and seem to have 383 deleted messages still left in my database (from before the migration) that I simply cannot purge.

If a new message is deleted, it can be purged normally, so that is not an issue.

I have determined that the messages that need to be purged all have a "hold" value of 2 in the mySQL table XXX_kunena_messages, and the message body is still there in the XXX_kunena_message_text table as well.

I'd like to run a simple operation on my table, using either a simple PHP file or phpMySQL, to remove these entries, but I lack the knowledge to construct this myself.

What command can I run on the system that will:

  • Delete a record with a "hold" value of 2 in the table XXX_kunena_messages
  • Delete the corresponding record with a matching "id" value in XXX_kunena_messages_text

Thank you!

Geoffrey Schaller
Technical Officer
Knight Realms

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

More
14 years 1 month ago #135155 by sozzled
What you will see below is only a very rough guide:

You probably need to run two queries in as follows and, remember, this is only a rough guide and I haven't tested it:
Code:
DELETE FROM XXX_kunena_messages_text AS a INNER JOIN XXX_kunena_messages AS b ON a.mesid = b.id WHERE b.hold=2 DELETE FROM XXX_kunena_messages WHERE hold=2

I would suggest that you run these as SELECT queries first, to make sure that you get the right records before you run them as DELETE queries.

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

More
14 years 1 month ago #135158 by GJSchaller
Thank you, Sozzled!

Here's the error I am getting when I run it:
Code:
#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'FROM XXX_kunena_messages_text AS a INNER JOIN XXX_kunena_messages AS b ON a.mesi' at line 1

(XXX is, of course, replaced with the actual table prefix.)

Forum Config in message to follow.

Geoffrey Schaller
Technical Officer
Knight Realms

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

More
14 years 1 month ago #135159 by GJSchaller
This message contains confidential information

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

Legacy mode: Disabled | 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: 16M

Kunena menu details:

Warning: Spoiler!

Joomla default template details : knightrealms | author: Geoffrey Schaller | version: 1.7.0 | creationdate: 12th August 2011

Kunena default template details : Travance 2.0 | author: Geoffrey Schaller | version: 2.0.2 | creationdate: 2012-09-04

Kunena version detailed: Kunena 2.0.2 | 2012-09-02 [ Botschafter ]
| Kunena detailed configuration:

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

Third-party components: CommunityBuilder 1.8.1 | UddeIM 2.8

Third-party SEF components: None

Plugins: None

Modules: Kunena Stats 2.0.2 | Kunena Login 2.0.2


Geoffrey Schaller
Technical Officer
Knight Realms

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

More
14 years 1 month ago #135162 by sozzled
For $100 I can fix most SQL syntax errors. :laugh:

But, seriously, I dashed off my rough guide information after spending about 10 minutes running a quick test using phpMyAdmin looking at the question, because I found it interesting from an "academic" perspective. Perhaps the syntax is different with phpMYSQL (which I've never heard of).

Your configuration report doesn't help in this situation. This is probably something you need to experiment with yourself. My advice is to start simple with
Code:
SELECT * FROM XXX_kunena_messages_text AS a INNER JOIN XXX_kunena_messages AS b ON a.mesid = b.id WHERE b.hold=2 SELECT * FROM XXX_kunena_messages WHERE hold=2
... and above all else, please read How To Destroy your forum data... first! ;)
The following user(s) said Thank You: GJSchaller

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

More
14 years 1 month ago #135164 by GJSchaller
The newer ones worked great - thank you, VERY much! I'm seeing the same 383 rows I am seeing in the Kunena Trash Manager.

Backups will be made, verified, and backed up again, before I run the DELETE version.

Again, thank you, Sozzled. :-)

Geoffrey Schaller
Technical Officer
Knight Realms

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

Time to create page: 0.152 seconds