Newbies Bart Posted April 10, 2011 Newbies Share Posted April 10, 2011 This happens regardless on Windows OS version: AutoUpdate successfully recognizes a need for the new version on the server and starts the update process. The plugin is placed in the appropriate Extensions folder for the OS. Instead of moving the older plugin to the \Saved folder within the Extensions folder, it leaves it where it was and renames the new plugin 360Works_pluginname.fmx.new. All other plugins from other vendors work as advertised. Please help with this. Link to comment Share on other sites More sharing options...
Smef Posted April 11, 2011 Share Posted April 11, 2011 There was an issue with older versions of our plugins where files would not be released properly and auto-update would not work successfully. Our latest build of our plugins resolves this issue. You will need to either manually remove the old plugins from the auto-update directory before allowing the script to install the new versions, or you can use our plugin-remover utility on our site at http://360works.com/remove-plugins/ which will do this for you. Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 4756 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now