Daddy Posted September 17, 2022 Share Posted September 17, 2022 When you delete a previous version on IP.Downloads file it throws a template error on the download button. You can also reproduce this by changing the changelog ID to one that doesn't exist and it'll produce the same error. Was able to reproduce it on the IPS website as well. BertT 1 Link to comment Share on other sites More sharing options...
Marc Stridgen Posted September 18, 2022 Share Posted September 18, 2022 Please could you provide exact steps to reproduce this? Im not able to reproduce in the manner I was using to delete, so I may be misunderstanding here Link to comment Share on other sites More sharing options...
Daddy Posted September 18, 2022 Author Share Posted September 18, 2022 1 hour ago, Marc Stridgen said: Please could you provide exact steps to reproduce this? Im not able to reproduce in the manner I was using to delete, so I may be misunderstanding here If the changelog ID doesn't exist, IE after you delete a previous version, or you purposely select an ID that doesn't exist, you get a template error where the download button would be. https://invisioncommunity.com/files/file/8797-block-from-downloading-my-files/?changelog=269801111 Link to comment Share on other sites More sharing options...
Marc Stridgen Posted September 19, 2022 Share Posted September 19, 2022 Im a little confused here, as you cannot get to an item that no longer exists to get the error. I need the exact steps you are taking to delete it, and how you are then accessing the page (where are you getting the link from) Link to comment Share on other sites More sharing options...
Daddy Posted September 21, 2022 Author Share Posted September 21, 2022 (edited) On 9/19/2022 at 3:18 AM, Marc Stridgen said: Im a little confused here, as you cannot get to an item that no longer exists to get the error. I need the exact steps you are taking to delete it, and how you are then accessing the page (where are you getting the link from) Did you click that link? The error happens when the the changelog in the URL is pointing to an ID that doesn't or no longer exist. You can reproduce it by purposely using an ID that doesn't exist. But this happens when you delete a changelog and the page reloads with the same changelog id on the URL. Edited September 21, 2022 by Daddy Link to comment Share on other sites More sharing options...
Marc Stridgen Posted September 21, 2022 Share Posted September 21, 2022 Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release. Link to comment Share on other sites More sharing options...
Daddy Posted October 12, 2022 Author Share Posted October 12, 2022 Still not fixed? Link to comment Share on other sites More sharing options...
Daddy Posted November 9, 2022 Author Share Posted November 9, 2022 Not to be a pain but it's been a few months and this is still an issue. It's being reported daily from our users. Link to comment Share on other sites More sharing options...
Gary Posted November 9, 2022 Share Posted November 9, 2022 Hi @Daddy, We're sorry your community is still experiencing this issue. There has been traction on this one as I can see recent activity from our developers. We should have more information once the developers have completed their investigation and performed the required fixes. Marc Stridgen and Daddy 2 Link to comment Share on other sites More sharing options...
Gary Posted December 13, 2022 Share Posted December 13, 2022 I just thought I'd give a heads up that this bug has been fixed and will be resolved in a future release. Once you have updated, please let us know if you encounter the same issue. I'm sure you know this already, but just for reference, you can find a full list of bug fixes on the link below: Release Notes - Invision Community Link to comment Share on other sites More sharing options...
Marc Stridgen Posted January 10, 2023 Share Posted January 10, 2023 This has now been resolved in our latest 4.7.6 release. Please upgrade to that release if you are seeing this issue. If you have the same problem after upgrading, please let us know. Link to comment Share on other sites More sharing options...
Recommended Posts