Hi,
- foxwiki is in version 1.0b and not even a final 1.0
version
- when you try to install the FF extension it
says it's not compatible
with FF 3.6.3 (it doesn't work with other FF 3.6
versions either)
This is hard-coded in the xpi. Re-releasing with another max-version
would probably work.
One problem is that we don't have full control over the release of FoXWiki
because it is hosted at
addons.mozilla.org (as i remember, a release
requires few reviews and so on), and if we are to host it by ourselves, we
need to deploy the xpi file at a ssh secured url (otherwise firefox rejects
the addon as i recall).
See:
https://addons.mozilla.org/en-US/firefox/addon/2358 a lot of users are
complaining about version incompatibility :(
I did not have much time to work on this and I don't think I will have time
in comming months either. Sergiu, if you have an account at
addons.mozilla.org, i should be able to add you as a FoXWiki author so that
you can work on it.
Thus we have 2
choices:
- someone volunteers to work on it and make FoxWiki work with FF and IE
relatively
quickly since the feature is currently broken
- we move foxwiki to contrib/ and remove that
feature (ie. we could make
it active only if the extension is installed for ex)
WDYT?
FoXWiki can only work with FF, since it's a Firefox extension. In IE it
should work as long as a WebDAV client is configured.
Nope, IE should work out of the box, it only requires some javascript work.
A WebDAV client is only required if you need to mount XWiki into your file
system. I have tested this on IE a long time ago and it used to work.
However, recently jerome did some changes to WebDAV UI integration code that
allows admins to selectively disable WebDAV features, may be this is the
reason why it doesn't work on IE oob, jerome should be able to give more
details.
Finally, AFAIK there is absolutely 0 documentation on WebDAV XWiki UI
integration (I think I did not have time for that).
Another problem (not sure about this one) could be that if XE is running
behind an apache webserver (mod_jk) there will be issues since apache might
not forward webdav requests to tomcat by default. A user reported something
like this but I did not have time to look into it.
I know it is my responsibility to work / maintain webdav related work but I
was busy with some other work. If someone could take it over, i would be
glad to help out.
Thanks.
- Asiri