Question Install Error

Hate to say "bump"

But... I can't figure out why the component is looking for AJAX in the wrong path. Where can I change where it's looking for that?

For whatever reason, my host did not or Joomla did not put AJAX under the \administrator folder.

If I could modify where it's looking for AJAX, I am guessing the install would complete.

Tried the XML file but there's no mention of it.

I'm a beginner. I read somewhere that you're supposed to remove fireboard completely before installing kunena

I found it. It says here ( docs.kunena.com/index.php/Installation_Instructions ) that you can install normally if You are not running a prior version of Fireboard or Kunena. ......

and here ( docs.kunena.com/index.php/Technical_Requirements ) - Fireboard Compatibility

Starting with Kunena 1.0.8 You can no longer run FireBoard in parallel with Kunena. You must uninstall any prior release prior to upgrading to Kunena. Several structural bugs required upgrades to the database structure that make the database incompatible with FireBoard or any fork based on 1.0.5. ......

Great find!

Except I wasn't able to install 1.0.7 which should have no issue. If I must uninstall Fireboard, that presents a ton of re-work and potentially no migration path.

Huge... issue for anybody considering migrating with a current Fireboard setup.

I'm not sure why 1.0.7 wouldn't install but it would on other boxes. Seems to me, the error I see is that AJAX is being called for in a location that it's not present on my system.

If Kunena 1.0.8 does not work for you, it is possible to uninstall it and install FB 1.0.5RC2 back to your system. It should work just fine and without any problems.

But using them at the same time will get you issues in Kunena.

Finally...

Seems like it's an issue with Joomla and my host. I had to view the Sys Info within Joomla. Noticed some directories were not writeable. Used FTP to just 777 them all.

Updated worked.

Then set them back to 755.

I think it's between my host and Joomla. How it works or something. It ended up being a permissions issue.