Vincent Massol wrote:
On Oct 18, 2007, at 11:59 PM, Lilianne E. Blaze wrote:
Vincent Massol wrote:
Hi Lilianne,
On Oct 17, 2007, at 9:50 PM, Lilianne E. Blaze wrote:
Hello, What's the current status on 913, can we expect it reasonably soon? I have a couple of projects I'd love to use XWiki with, but I really need 913 first.
I think this is kind of low priority compared to other issues (like bug fixes for example) but it only takes one committer to work on it. Right now nobody is working on it AFAIK so there's no ETA yet.
What you could do to help and speed up things would be to apply the patch in your install, possibly improve the code if need be, verify it works, prepare some documentation for it and report all in jira.
Then it would be very easy to apply it in a few minutes so you'd have it in the official distribution.
Thanks -Vincent
I'm afraid I simply don't know enough about XWiki code to do this.
Ah... I assumed you knew since you're posting on xwiki devs and xwiki devs is... well... for xwiki developers...
Oh. Well, that's a logical assumption. I did contribute some trivial patch or two ages ago, but since then I wasn't really tracking the source.
Applying patches shouldn't be too hard...
It's not the patch itself I'm worried about, that I probably could do (well, assuming I'd have the time, which I don't have at the moment), but it seems like one of these things that can break hundred other things all over the place when done by someone not having enough general knowledge of a system's architecture.
So if you're not a developer you have 2 options I can think of:
1) pay a XWiki developer to work on it. 2) wait... :)
But it is still scheduled for 1.2m2, right?
As I said nobody is working on it so there's no ETA right now. It all depends on someone having an itch to scratch. I personally don't have that itch right now, especially since I've already implemented this feature using the new XWiki V2 component architecture model but that's not going to be used for a long time...
-Vincent Ok, guess I'll just write a simple filter to redirect "/ ( main | other | another ) / *" -> "/bin/view/*/*" for now, it would solve, well, 1/3 of the problem. I assume there are no reasons for client redirect not to work, but server forward would probably mess up relative paths, correct?
Greetings, Lilianne E. Blaze