Kunena 7.0.2 Released

The Kunena team has announce the arrival of Kunena 7.0.2 [K 7.0.2] in stable which is now available for download as a native Joomla extension for J! 5.3.x/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

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 Installation process loops and won't stop

More
11 years 10 months ago #155930 by sozzled

colin99 wrote: I have done AUTO-UPDATE

and then Package Upload.

Both fail -- I can upload any screen grabs that might help us.

Ouch!

You may have seen the notice on the K 3.0 Upgrade Guide that refers to problems that people can have after a failed attempt to use the Joomla autoupdate procedure.

This is a real problem and sorting it out can be tricky.

In short, in earlier versions of Joomla, there were problems with the autoupdate process. If it failed it corrupted the _assets table and prevented subsequent attempts to upgrade the Joomla extension that was affected. It is a known problem with Joomla.

Fixing it requires clearing out the corrupted records in the _assets table and then the "normal" upgrade should work without any hitches. It's a beast of a job to do and it's regrettable that these kinds of things happen. That's why it's always important that you should always make a site backup even if you entrust the "autopudate" process to do its work because, even in those instances, recovery of your site is best done from a backup ... unless you're comfortable rolling up your sleeves and diving into the database to correct the data corruption.

That's what I think has happened in this case. There is a data corruption.

I recall seeing something about this on the Joomla site but I can't remember exactly where I found the answer.

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

More
11 years 10 months ago - 11 years 10 months ago #155942 by colin99

sozzled wrote: Fixing it requires clearing out the corrupted records in the _assets table and then the "normal" upgrade should work without any hitches. It's a beast of a job to do and it's regrettable that these kinds of things happen. That's why it's always important that you should always make a site backup even if you entrust the "autopudate" process to do its work because, even in those instances, recovery of your site is best done from a backup ... unless you're comfortable rolling up your sleeves and diving into the database to correct the data corruption.

That's what I think has happened in this case. There is a data corruption.

I recall seeing something about this on the Joomla site but I can't remember exactly where I found the answer.


I am very comfortable holding electric prods to my test MySQL databases -- so if someone knows a link to this procedure, I am totally game.

This explains why I get mixed results on the different Kunena forums that I maintain.

All good - still love and support the product.
I cannot imagine my websites without Kunena and that has kept me from jumping ship to
*gasp* Wordpress from time to time.

Joomla rocks.
Last edit: 11 years 10 months ago by sozzled. Reason: minor chages to fix odd use of [quote] tags

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

More
11 years 10 months ago #155944 by sozzled
I have assisted other people with this problem before (as a professional private consultation, of course). You could, if you like, search the Joomla site for discussion topics that deal with autoupdate failures and matters that affect the _assets table. My recollection of this was that Elin Waring posted something on the Joomla forum in the last couple of years about the issue but, as I wrote before, my recollection is a little hazy.

Would you be interested in engaging me to research this matter further for you? I won't be offended in the least if you're not interested in the professional consultation services that I offer outside this site; that's entirely a matter for you. :)

Good luck. I'm sure that, with a bit of patience and some skill, the answer will reveal itself in time.

I don't really have too many comments to make about Wordpress - my comments would be off-topic and unproductive as far as your current issues are concerned - except to say that people should use whatever approach suits their particular needs. If that approach involves the use of Wordpress-plus-bbPress, Drupal (which has a forum module built into its core), phpBB (as a standalone forum product) or Joomla-plus-Kunena then I say good luck and every success to you.

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

More
11 years 10 months ago - 11 years 10 months ago #155956 by colin99
Thank you! (for the offer and everything...)

Like you, I am a roll up your sleeves kind of guy -- like to dig in and fix things myself --

So...

Found an asset table repair hack in the joomla forum -- ATTACHED FILE

Ran that -- and it fixed a LOT of stuff.
Cleaned my menu set up.
UPLOADED Kunena to the latest from 3.03
And it looped around 7 - 9 times but finally came to its senses and stuck.
All good now -- might not be the solution for everyone but it is at least a great
place to start!

Many thanks again!
Last edit: 11 years 10 months ago by colin99.
The following user(s) said Thank You: sozzled

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

More
11 years 10 months ago #155958 by sozzled
I knew the discussion about Joomla extension autoupdate failures cause (and cure) was there (in the Joomla forum) somewhere. I am thankful that you found it and shared your findings with the rest of the community. Your findings may well help someone else.

The important lessons from this discussion are:
  1. The Joomla autoupdate procedure sometimes fails.
  2. When the Joomla autoupdate procedure fails it can corrupt the integrity of your website and prevent you from later upgrading Joomla extensions that you may have installed.
  3. To overcome the likelihood that the Joomla autoupdate procedure may fail, part-way through its operation and leaving your site in a mess in future, you should always have a standby backup available just in case. You may need to revert to your backup.
  4. The Joomla autoupdate process is "simple" - that is to say, it assumes that nothing will go wrong. When it does go wrong, you may or may not get any information that informs you of its success or failure. The Joomla autoupdate feature "hopes for the best" - but you should always be on the alert for the worst. ;)
  5. If the Joomla autoupdate process does fail, for some reason, and you don't have a site backup, then you need to explore other options to discover the thing that prevents the normal Joomla Extension Manager from being able to upgrade the Joomla extensions you use. One such way of exploring these things is to participate in the Joomla forum on a regular basis. Another way is to search the internet.
  6. When all else fails, there are professional consultants who can do the heavy job of repairing your website - and do it quickly - for a very reasonable fee.
  7. Joomla is not perfect.
  8. Kunena is not perfect either (but the guys are doing the best that they can)!
The following user(s) said Thank You: colin99

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

More
11 years 10 months ago #155959 by colin99
I am committed to spending more time in the forums "giving back..."

Because this forum (and the mother ship forum over at Joomla...)
certainly has done a lot of hand holding for me.

And when/if I need some professional help, you sir, will be one of the 1st ones that I look to.

If you do not mind, pop over to my blog at coffee DOT bc DOT ca
and send me an e-mail with your contact info...

Many thanks -- Colin in Canada

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

Time to create page: 0.320 seconds