The Kunena team has announce the arrival of Kunena 6.2.1 [K 6.2.1] which is now available for download as a native Joomla extension for J! 4.3.x/4.4.x/5.0.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
Use this category:
- to ask how to install or upgrade; or
- if you encountered problems during the installation or upgrade procedure.
Use a different category to ask questions about problems that you may be having after you successfully installed or upgraded the currently supported version. If you are unsure what is the current supported version of Kunena, please go to the download page.
Question JInstaller: :Install: SQL-Fehler Duplicate entry 'com_kunena.reply-' for key 'PR
I upgraded from Joomla 3 to J4. I could install several extensions without probs. Just with Kunena it went wrong. In Joomla 3 before upgrade I use V 5.2. and I uninstalled Kunena as described. Now in Joomla 4 I wanted to install V6 but the error "JInstaller: :Install: SQL-Fehler Duplicate entry 'com_kunena.reply-' for key 'PRIMARY'" comes. Server should be ok. What to do?
thnx in advance
"Remove the kunena entries in the table #__mail_templates "
there is no table like this im my database. see www.loom.com/share/0284e0294d5c42b0a8a8bfba26c3df1b
might be useful to have a Create and Post Configuration Report
Is the error displayed in the Backend -> System -> Database? If so, try the repair option.
yes i checked database. it says there are no errors and it has current state.
Shall I overwride all joomla core files again via ftp? ( with fielzilla for ex.)
I would go mad. How else can I fix it? Can I not just import tables? Which one exactly?
(By the way everything else works except Kunena)
And what you might try (but I would first do this locally with Wamp or Xampp) is to export all your prefix_kunena from your database to your pc and then save it then remove everything from kunena from the database and then see if you can install kunena. if that works you might remove all kunena from database again and then import the saved kuena.sql