- Posts: 21
- Thank you received: 0
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
Solved Problem with writing new posts
10 years 2 months ago #173195
by dimov
Replied by dimov on topic Problem with writing new posts
Hello, is there anyone who can help me?
If I have to pay for solving this problem - it's not a problem, just write me.
I want to solve this report asap and no one can...
If I have to pay for solving this problem - it's not a problem, just write me.
I want to solve this report asap and no one can...
Please Log in or Create an account to join the conversation.
10 years 2 months ago #173262
by 810
Replied by 810 on topic Problem with writing new posts
1) make backup
2) Remove kunena tables
3) Install kunena
4) Check if its working
5) replace kunena table 1 by 1, by the old kunena database.
6) Until it breaks, then you know where the issue is
2) Remove kunena tables
3) Install kunena
4) Check if its working
5) replace kunena table 1 by 1, by the old kunena database.
6) Until it breaks, then you know where the issue is
Please Log in or Create an account to join the conversation.
10 years 1 month ago #173697
by dimov
Replied by dimov on topic Problem with writing new posts
Hi,
Ok, I found in which tables I got this problem.
This is problem is from tables: messages and messages_text.
If I insert standard messages, messages_text tables is working perfect.
So the main problem is inside this two tables.
And I found one more problem:
If I use my table topics and after that try to create a new topic - there is a problem which told me that I didn't insert name for topic.
And if I use the standard topics table everything goes perfect.
So do you know how can I fix this two problems regarding my messages, messages_text and topics tables, because this tables contains all my data?
Ok, I found in which tables I got this problem.
This is problem is from tables: messages and messages_text.
If I insert standard messages, messages_text tables is working perfect.
So the main problem is inside this two tables.
And I found one more problem:
If I use my table topics and after that try to create a new topic - there is a problem which told me that I didn't insert name for topic.
And if I use the standard topics table everything goes perfect.
So do you know how can I fix this two problems regarding my messages, messages_text and topics tables, because this tables contains all my data?
Please Log in or Create an account to join the conversation.
10 years 1 month ago #173698
by dimov
Replied by dimov on topic Problem with writing new posts
Ok, I found the solution.
There was a problem with Unique ID, duplicate it.
Here is the solution:
"This table does not contain a unique column. Grid edit, checkbox, Edit, Copy and Delete features are not available."
There are several working solutions depending on your exact scenario.
For example, as long as all of your AI or Unique identifier field are unique then you can simply alter the table and ensure this is the Primary key and set to unique value.
I solved this with this solution on one of my tables.
The other table had multiple AI int values that were the Primary field, but there were multiple values of the same kind.
The simple fix for this was to just add a column to the end of the table as Unique AI Int. Basically all MySQL is saying is it needs a unique value in each record to differentiate the rows.
There was a problem with Unique ID, duplicate it.
Here is the solution:
"This table does not contain a unique column. Grid edit, checkbox, Edit, Copy and Delete features are not available."
There are several working solutions depending on your exact scenario.
For example, as long as all of your AI or Unique identifier field are unique then you can simply alter the table and ensure this is the Primary key and set to unique value.
I solved this with this solution on one of my tables.
The other table had multiple AI int values that were the Primary field, but there were multiple values of the same kind.
The simple fix for this was to just add a column to the end of the table as Unique AI Int. Basically all MySQL is saying is it needs a unique value in each record to differentiate the rows.
Please Log in or Create an account to join the conversation.
Time to create page: 0.260 seconds