|
News and Blog Postings from the EnterMedia DAM team.
OpenEdit Mini-Release v5.2059We have rolled out a new release version in response to the problems faced by several users with the last release. The main issues addressed in this release are: -Default Administrator permissions have been configured to allow access to the Asset Editor tool. -New folders created within the Asset Editor will now correctly display as folders. -The upload tool in the Asset Editor will now correctly unzip files when instructed to do so. -Clicking on an asset in the Asset Editor will now give you the option to open that asset in other tools.
You can download the new release from our Download Page. The instructions on this page have been improved, and windows users should note the need to rename ImageMagick's convert.exe to imconvert.exe in order to get around a conflict with a built-in Windows command. |
EnterMedia integrates with Episode by Telestream
(0 comments)
REST API using JQuery for EnterMedia
(0 comments)
Why do I need permissions and roles in DAM?
(0 comments) 
|
what's the best way to patch this? if we replace the ROOT.war, will Resin know to update it?
Putting in the new Root.war should work. Resin should unpack the .war file when it starts and just put the new files over top of the old ones.
However, a better solution is to use OpenEdit's update manager. From the Settings menu in the OE toolbar, select "Upgrade Plugins". Then check the box next to "Digital Assets", and all of the other plugins that are required should be automatically checked also. Then click the upgrade link.
When the upgrade is finished, you may need to restart your webapp. Also, if you are using Windows, you should go to <openedit directory>/WEB-INF/lib and remove any old jar files. OpenEdit tries to do this automatically but windows usually locks the files so the remove does not work. So, for example, if you see openedit-archive-v1.2345.jar and openedit-archive-v2.3456, you want to delete the older one (1.2345) so that when OE starts it will be running the correct version. This would probably also be an issue if you just redeploy the new Root.war.
Just FYI, the update manager will always give you the newest version of the plugin available. So, updating today, you should have a version that is very close to the release version from last week.