New JRE 1.7v25 doens't work with plugin

[Menno van Beek]

Filemaker crashes inmediately when i try to register the plugin with EmailRegister ( "Reg-code" ; "Company" ). I use version 1.964

I have cleared the java-cache en removed all old applications, all that doesn't help.

We heave tried this on 32 and 64 bit Windows7 systems.

 

Ik have re-installed JRE 1.7v21 and told my users to do the same and then there's no crash anymore.

 

regards, Menno

[ScotsJoe]

I've also verified this as an issue and have had to remove update 25 and re-install v21. v21 itself then causes other problems running in a browser and so this is very undesirable.

[David Wikström]

+ 1. This not surprisingly seems to be an issue with all the Java-based 360Works plugins.

 

This issue is of course extremely problematic, since it breaks any solution using these plugins, in particular in environments where we as developers can't influence what Java updates are installed. I'd really hate to have to abandon ScriptMaster and the other 360Works plugins!

[Joe Pampalon]

Hi everyone,

 

We are aware of the problem with Java 7u25 breaking our plug-ins in various ways, and we will have a fix out later today for all of our products and their plug-ins. There will be a press release with details and instructions. I will post again with a link to this release once it is out. Thanks for your patience!

[Joe Pampalon]

Hello all!

 

The updates are all ready for download. Please see the following releases: 

http://360works.com/news/detail/265

http://360works.com/news/detail/266

[wlitzau]

I am using the Install plug in script step to install the new set of plugins, but they fail to install. If I look in Edit > Preferences > Plug ins the old plugins don't even show up now. The only way to get around this is by manually putting the plugins into the extensions folder. Any idea how to fix this to work with the script?  

[wlitzau]

It seems that if I complete remove the plugin from extension folders that the install step works great. If the install step runs a second time it fails, removes the plugin from the list of installed plugins and adds a copy of the plugin file to my appdata folder called 360Works_Email.fmx.new  . Not sure if this if filemaker doing this or something with 360works. Removing the .new file allows the plugin to be recognized once again. 

 

I am running fmp 12 and win7.

[Joe Pampalon]

Hi,

 

Unfortunately, this is a problem with a small number of our Email plug-in versions. The initial update will require manually deleting the old plug-in before you can install the new one. After this update, any new versions will install over the old ones using the FM InstallPluginFile function

 

However, another issue may arise when trying to install the same version of a plug-in over itself. I recommend you avoid this entirely by adding a check to see if an update is necessary. You can use Get( InstalledFMPlugins ) and parse out the version number from there, or you can use each plug-in's personal version function (Email uses the function EmailVersion). 
 

Let me know how this works for you. Thanks!

[David Wikström]

I'm also having similar, very strange issues, including crashes. It's really a big pain in particular in "uncontrolled" environments (runtimes in my case). And even with users you can communicate with, there are so many possible plugin locations nowadays that doing a manual delete is a bit of an undertaking for a non-IT person!

 

One problem that should be mentioned with Get( InstalledFMPlugins ) is that it doesn't work well with the custom plugins you can build with ScriptMaster Advanced. The function returns the ScriptMaster version, not the version of the custom plugin.

[Menno van Beek]

I have had the same issue with both the email-plugin and the scribe-plugin. I did not want to go about the customer's company-building to manually remove plugins from 20+ workstations, so I created a batchscript that I export to the temporaryfolder from a containerfield and set it to open immediatly:

 

ping -n 2 127.0.0.1 > nul
taskkill /F /IM "Filemaker Pro.exe"
ping -n 2 127.0.0.1 > nul
CD C:Users%username%AppDataLocalFileMaker
DEL /S /F 360Works*
exit

 

After this the plugins are removed (for XP you may need to alter the path in after CD), filemaker has to be started again. Your autoupdate-scripts should now push the new 360works-plugins to the workstations.

 

Hope it helps you,

 

regards, Menno