Question Install/Update Failure 4.0.10

I have done that also and still wont worrk?

I hit this problem a lot! Today I was updating a website that was using K 3.0.8 and I was installing K 4.0.10. Obviously I took a lot of precautions before starting the update (backup the site, copy the backup off-site). Anyway, I used my usual installation method—upload file—the Kunena installer halted and, the only way I could recover, was to use the browser back-button. :pinch: :dry:

Ah, but all was not lost! Even though the "Kunena installer" had failed, go to Components » Kunena Forum » Configuration and, sure enough, the rest of the installation went ahead. :woohoo:

I've never run into the problem of having to "clear the cache". I realise this is the answer/response given most often by the developers but, to be totally honest with everyone, I've never had to do it! (And, as for trying with a different kind of browser, that sounds a bit absurd to me.)

So, maybe I'm just one lucky person out of 30,000? Or maybe I have more patience than other people?

Looks like I am running into the same sort of problem. Updated to 4.0.10 and now my categories all say they are Orphaned in the administrator. I can see them in the live forum and click on them but get a notice of "Access Denied-You do not have permissions to access this page.".

If I click on the category in the administrator, I get this error: "Call to a member function get() on string".

If I try to unpublish the category, I get a really scary SQL error, the start of which says: Duplicate entry '3' for key 'PRIMARY' SQL=INSERT INTO `#__kunena_categories`. This is followed by a whole lot of database speak.

I am attaching my configuration report.


I have placed the forum offline for the moment.
I have cleared all of the caches and tried other browsers.

I am afraid if I uninstall Kunena that I will lose all my forum content. Is this correct?

Thanks for any assistance,

Mike

"Call to a member function get() on string". is a php7.0.6 bug.

So i suggest to go to php 5.6

That worked. Reverting the site's PHP version from 7.0.6 to 5.6.21 brought the orphans home! Thank you!

Hi

I've run into the same problem.

Your suggestion is a work around.

Is there a solution which will allow PHP 7?

Regards
David