Question 1.5.14 upgrade issue

Ping?

The missing encoding declaration impacts both K1.6 and K2.0 as well.

kmilos wrote: @Scottux, @810
Yep, editing only manifest.xml is not enough (at least not after the build is done.)

For a long term solution maybe adding

Code:

encoding="utf-8"

to the /trunk/1.5/administrator/components/com_kunena/install/kunena.install.upgrade.xml template would be best?

Yes, this a good solution

Just saw another user running into this problem.

It's been weeks, and no commits to 1.5, 1.6 nor 2.0 in SVN, and no comments to the bug report on Forge.

Is there a problem with this patch being applied?

I understand resources are limited and devs are busy, but this is how things get forgotten and fall through the cracks.

The issue isn't in /trunk/1.5/administrator/components/com_kunena/install/kunena.install.upgrade.xml but in \administrator\components\com_kunena\manifest.xml and this file has already encoding="utf-8"

I beg to differ.

As mentioned in the earlier post in this thread, changes to manifest.xml alone were not enough, because the install package build script creates kunena.install.upgrade.xml using the checked in template the same way it does manifest.xml. If I understand correctly from kunena.build.xml:


This why the problematic unicode character in ${xml.versionname} appeared ok in manifest.xml and not in kunena.install.upgrade.xml

Because the template kunena.install.upgrade.xml has no encoding it presumably gets processed as latin-1 and that's where the problem comes from (it didn't hit before because there were no unicode characters used in version names). There is potential this will hit again in all versions: 1.5, 1.6, and 2.0.

Thanks you guys for putting these tips in here but it really would help to have the install fixed.

I already learned I can't use 1.6 without solving some template issues so I need to stay with 1.5 for the immediate term. It's cruddy for us all to have 1.5.14 not install either.