Leogui2k3 Posted December 6, 2022 Share Posted December 6, 2022 Hello. why autocomplete throws an error. Due to this error, the radical tags application does not work properly, see the attachment Link to comment Share on other sites More sharing options...
Jim M Posted December 6, 2022 Share Posted December 6, 2022 Please contact the author of the third party application for any issues within their application. You may also wish to switch to an unmodified language pack. Link to comment Share on other sites More sharing options...
Leogui2k3 Posted December 6, 2022 Author Share Posted December 6, 2022 and what is the point of contacting the author of radical tags since everything worked without a problem on the ips 4.7.4 version and after updating to 4.7.5 this error suddenly appeared and on the default style Link to comment Share on other sites More sharing options...
Jim M Posted December 6, 2022 Share Posted December 6, 2022 19 minutes ago, Leogui2k3 said: and what is the point of contacting the author of radical tags since everything worked without a problem on the ips 4.7.4 version and after updating to 4.7.5 this error suddenly appeared and on the default style That would indicate it’s not compatible with the latest release and therefore needs to be updated to do so. Leogui2k3 1 Link to comment Share on other sites More sharing options...
Leogui2k3 Posted January 13, 2023 Author Share Posted January 13, 2023 after contacting the author of the application, it appears that it was supposed to be fixed by you in version 4.7.6 after the update it still occurs! Maybe a fix for this will come from you in the near future? Link to comment Share on other sites More sharing options...
Randy Calvert Posted January 14, 2023 Share Posted January 14, 2023 That’s something the script author would need to address with IPB if they feel there is an error in the core platform still. Link to comment Share on other sites More sharing options...
Jim M Posted January 14, 2023 Share Posted January 14, 2023 15 hours ago, Leogui2k3 said: after contacting the author of the application, it appears that it was supposed to be fixed by you in version 4.7.6 after the update it still occurs! Maybe a fix for this will come from you in the near future? The author will need to report any bugs to us directly with examples if they believe there is a core issue. However, they would also need to evaluate this in their application if there are any residual effects leading to your issue. Link to comment Share on other sites More sharing options...
Gary Posted January 21, 2023 Share Posted January 21, 2023 Topic has been locked as requested by the original poster. Please feel free to open a new topic should you encounter any further issues. Link to comment Share on other sites More sharing options...
Recommended Posts