This is a pretty poor showing from Devs for such a minor yet potentially highly impactful defect. This should've been hot fixed and patch released day 1.
I assume the release was patched since I have not seen complaints about this since, and yes, it should have been announced as a PL release so those that had the issue weren't finding out this way.
I assume the release was patched since I have not seen complaints about this since, and yes, it should have been announced as a PL release so those that had the issue weren't finding out this way.
I don't know if it was patched. Do you? Don't think I saw any communication beyond what Jeremy wrote here. I can probably find out but anyone not following this thread might be SOL hence my concern here.
Stuff like this is child's play to communicate clearly. We've hotfixed it, please redownload x, y file and replace or here's a PL1 or working as designed but if you don't like it here's a patch file. Why is it becoming such a nuisance to pull info from staff on here.
I don't believe it's fixed in the actual release, but I haven't confirmed. I'd expect there would've been an announcement if it were. You could probably download the latest XF and compare the appropriate file with the patch that @Jeremy P posted here:
I've attached a patch, you'll need to unzip it and replace the enclosed js/xf/attachment_manager-compiled.js file, which should resolve this. You'll want to rebuild the master data and/or clear your browser cache to pick up the changes, too.