XH 1.6.2: Filebrowser blocks other file browsers
Posted: Thu Jun 12, 2014 10:44 pm
Hello Community,
I've just noticed that my careless implementation of r1269 introduced a severe regression bug: other filebrowsers are no more accessible from the admin menu, when they are loaded after the filebrowser (note that since XH 1.6 the loading always happens in alphabetic order); otherwise the filebrowser is active additionally.
Of course the relevant code in the filebrowser's admin has to be guarded according to $cf['filebrowser']['external'].
We better may not postpone the bugfix for too long, so we should start voting on the 1.6.3 roadmap today. What do you think?
Christoph
PS: the issue was reported by Holger, and we had some email discussion regarding a solution. If anybody else than myself will implement it, just contact me; otherwise note to myself: <539A21EC.4040905@t-online.de>.
I've just noticed that my careless implementation of r1269 introduced a severe regression bug: other filebrowsers are no more accessible from the admin menu, when they are loaded after the filebrowser (note that since XH 1.6 the loading always happens in alphabetic order); otherwise the filebrowser is active additionally.
Of course the relevant code in the filebrowser's admin has to be guarded according to $cf['filebrowser']['external'].
We better may not postpone the bugfix for too long, so we should start voting on the 1.6.3 roadmap today. What do you think?
Christoph
PS: the issue was reported by Holger, and we had some email discussion regarding a solution. If anybody else than myself will implement it, just contact me; otherwise note to myself: <539A21EC.4040905@t-online.de>.