<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
<head>
<meta name="Generator" content="Kopano WebApp v-6.0.0.57-1+2026.1">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>RE: [BlueOnyx:26663] Re: jquery warning</title>
</head>
<body>
<p style="font-family: arial,helvetica,sans-serif; font-size: 11pt; padding: 0; margin: 0;">Well, I have been quite sure that my "short question" wasn't to be answered as short..</p>
<p style="font-family: arial,helvetica,sans-serif; font-size: 11pt; padding: 0; margin: 0;"><span style="font-size: 11pt; font-family: arial, helvetica, sans-serif;"><br /></span></p>
<p style="font-family: arial,helvetica,sans-serif; font-size: 11pt; padding: 0; margin: 0;"><span style="font-size: 11pt; font-family: arial, helvetica, sans-serif;">So thank you Michael for the detailed analysis.</span></p>
<p style="font-family: arial,helvetica,sans-serif; font-size: 11pt; padding: 0; margin: 0;"><span style="font-size: 11pt; font-family: arial, helvetica, sans-serif;"><br /></span></p>
<p style="font-family: arial,helvetica,sans-serif; font-size: 11pt; padding: 0; margin: 0;"><span style="font-size: 11pt; font-family: arial, helvetica, sans-serif;">Reaction-wise I don't like obfuscation as a reaction. But I see your point in not replacing the used jQuery version with reasonable effort. So I think, working on the new UI version is the right way to go!</span></p>
<p style="font-family: arial,helvetica,sans-serif; font-size: 11pt; padding: 0; margin: 0;"><br /></p>
<p style="font-family: arial,helvetica,sans-serif; font-size: 11pt; padding: 0; margin: 0;"><span style="font-size: 11pt; font-family: arial, helvetica, sans-serif;">Thanks again,<br /></span></p>
<div class="signatureContainer">
<div class="signature">
<p style="padding: 0; margin: 0;"><span style="font-size: 11pt; font-family: arial, helvetica, sans-serif;"></span></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p style="padding: 0; margin: 0;"></p>
<p>Tobias Gablunsky<br /> IT-Infrastruktur & Lösungen<br /> ____________________________________________<br /> CBXNET combox internet GmbH<br /> Landhausstr. 22 | 10717 Berlin<br /> Tel: +49 (30) 5900 69-00<br /> Fax: +49 (30) 5900 69-99<br /> <a href="https://webmail.cbxnet.combox.group/www.cbxnet.de" target="_blank" title="https://webmail.cbxnet.combox.group/www.cbxnet.de
Klicken Sie auf den Link, um die URL in einem neuen Fenster zu öffnen." rel="noopener">www.cbxnet.de</a><br /></p>
<p>Rechenzentren für sichere Geschäftsanwendungen<br /> Tel: +49 (30) 5900 69-80<br /> <a href="https://combox.bln.de/" target="_blank" title="https://combox.bln.de/
Klicken Sie auf den Link, um die URL in einem neuen Fenster zu öffnen." rel="noopener">https://combox.bln.de</a><br /></p>
<p>Amtsgericht Berlin-Charlottenburg HRB 71171<br /> Geschäftsführer: Stephan Höhn</p>
</div>
</div>
<p style="padding: 0; margin: 0; min-height: 11pt; font-family: arial,helvetica,sans-serif; font-size: 11pt;"><br /></p>
<p style="padding: 0; margin: 0; min-height: 11pt; font-family: arial,helvetica,sans-serif; font-size: 11pt;"><br /></p>
<blockquote style="border-left: 2px solid #325FBA; padding-left: 5px; margin: 0px 5px;"><span style="font-family: tahoma,arial,helvetica,sans-serif; font-size: 10pt;">-----Ursprüngliche Nachricht-----<br /><span><strong>Von:</strong> Michael Stauber via Blueonyx <blueonyx@mail.blueonyx.it></span><br /><span><strong>Gesendet:</strong> Dienstag 12. Dezember 2023 23:25</span><br /><span><strong>An:</strong> blueonyx@mail.blueonyx.it</span><br /><span><strong>Betreff:</strong> [BlueOnyx:26663] Re: jquery warning</span><br /><br /></span>
<div>
<pre style="white-space: pre-wrap; word-wrap: break-word;">Hi all,<br /><br />> I'll take a look at this today. If I can't upgrade jQuery and retain <br />> compatibility with the offered migration plugins I'll at least replace <br />> jQuery with a patched version that's floating around and being <br />> maintained for those who can't do a straight up move to the latest version.<br /><br />Yeah, ok. Bad idea. This is like a heart transplantation.<br /><br />I just played around with it and here is what I did for testing:<br /><br />I upgraded jQuery from v1.7.2 to the latest stable v1.12.4 (last of the <br />v1 tree). Added the jQuery migrate script for jQuery 1.x that supposedly <br />fixes compat issues from v1.7.2 -> 1.9 (and newer) and updated jQuery-UI <br />to a more recent version. I also tried it with an updated jQuery UI <br />v1.13 (and without).<br /><br />And that's where the train jumped right off the tracks:<br /><br />Tooltips were no longer working, because the tooltip plugin Adminica <br />uses has been deprecated an no newer version is available. It can't be <br />fixed either, as it's an unmaintainable mess that relies on deprecated <br />means and methods.<br /><br />So I had ChatGPT hammer out a replacement jQuery script that dynamically <br />creates tooltips with the given HTML. That restored tooltip <br />functionality in a fashion not unlike the one we use in the new Elmer <br />GUI that is in development.<br /><br />But there are additional glitches such as all pop-up modals ("Do you <br />really want to log out ..." or "Do you really want to delete ..."), <br />which now show up in places other than the intended ones.<br /><br />Which is fixable, too. But this needs time and I'm certain there might <br />be other glitches as well, which I haven't yet run into.<br /><br />So yeah: This can be done, but right now? I have five days left before a <br />holiday travel and am still up to my ears embedded in hammering out the <br />new and more modern GUI for BlueOnyx. Which is another heart <br />transplantation (where other assorted bits and pieces are also getting <br />replaced) and that's incredibly time consuming. I also don't want to <br />deeply modify the 5211R (production) code base, because upon release of <br />the new GUI I have to merge four weeks of multiple daily code changes <br />back into the existing 5211R code tree from this devel repo:<br /><br />https://devel.blueonyx.it/trac/log/BlueOnyx/5311R<br /><br />All things considered: Going on a full rampage to deal with this minor <br />issue is not worth it at this time.<br /><br />So here is my road-map for the jQuery v1.7.2 issues on 5209R/5210R/5211R <br />in the Adminica part of the GUI:<br /><br />5211R/5210R/5209R Immediate action: Those will (today) receive a YUM <br />update that obfuscates the version number of the used jQuery. That at <br />least prevents the run of the mill "security scanners" (aka: "Snake <br />Oil") from tripping over it.<br /><br />5211R/5210R Short term action: In January I will release the updated GUI <br />for 5211R and will then also begin to back-port it to 5210R. This new <br />GUI will be the default GUI and if Adminica is still present and usable <br />(as currently planned) I will modify the Adminica jQuery in so far that <br />modals and tooltips will work with a slightly more modern jQuery.<br /><br />5209R long term: Won't fix beyond the basic obfuscation of the version <br />number. Six months before the EOL? Not worth it, given that the issue is <br />non-exploitable in real world scenarios due to other preventive measures <br />already present.<br /><br />-- <br />With best regards<br /><br />Michael Stauber<br />_______________________________________________<br />Blueonyx mailing list<br />Blueonyx@mail.blueonyx.it<br />http://mail.blueonyx.it/mailman/listinfo/blueonyx<br /></pre>
</div>
</blockquote>
</body>
</html>