MM - Things to be aware of when updating and installing

Owned by Mathias Mattson (MHM)
Last updated: Dec 18, 2018

You should see DC - Things to be aware of when updating and installing as well, as some of them will impact MM as well (This should already have been done when installing/updating DC)

VersionThings to be aware of

MM 5.0.0

IE only supports 2048 characters in the URL. This means that - if you e.g. select 175 assets, the URL that will be created will only include around 155 assets - You'll be editing all 175 assets though. Were you to refresh the page afterwards - You'll now be editing around 155 assets, as a refresh uses the link as the data source, while the "175 assets way" doesn't. Chrome does not have this issue.


The following issues are related to DC 4.9.1:

  • Comment profile pictures: Going into comments, you will not be able to see the profile images of people who have commented
  • User self sign-up: This will simply not work
  • Sharing collection: When sharing a collection, the recipient of the collection will see an email that has been generated using the wrong email template

When you make a new installation of MM5, the schema table isn't created - so if you do not edit and run this: Create SchemaVersions.sql, then there's a real chance that the MM5 update scripts will not run

MM 4.13.0


When you make a new installation or update of/to MM 4.13.0 - please be aware that you must not set a default value for datetime metadata. Doing so will cause its metagroup to not load.

MM-3818 - Getting issue details... STATUS  (Setting default values on DateTime makes the metadata group not load)


MM 4.12.0

Link to the release notes for this release: MM 4.12.0

Known issues

Works with 4.9.0, and most likely every version afterwards.

MM-3723 - Getting issue details... STATUS

MM-3722 - Getting issue details... STATUS

MM-3720 - Getting issue details... STATUS

MM-3714 - Getting issue details... STATUS

MM-3713 - Getting issue details... STATUS

MM-3712 - Getting issue details... STATUS

MM-3709 - Getting issue details... STATUS

Sorting issues fix

You need to go to MM's Config Manager, and look if any languages are missing a sorting option (e.g. Alphabetically and/or Date). If one is missing in one language, set it up so it looks correct and save.

In this way, you'' not experience issues when trying to change language in the MM.

Easier language set up

The language picker in MM (In the lower right corner) will now automatically match the system languages set in the DC's "Languages" menu. This means that, by adding e.g. Swedish as a system language in the DC's Languages menu, will make MM automatically get the language as an option as well.

For the record, the now redundant Config Manager language picker config has not been removed, and is defunct. In the near future this is to be taken out of the Config Manager.  MM-3733 - Getting issue details... STATUS

Profile images workflow may not work

If a customer wants to use profile images in MM, then the consultant must verify that the AssetSyncFolder workflow "Media Manager - Profile Images sync til layout" has the correct values in the 2 fields "Sync rootfolder" and "Destination rootfolder" (the names are taken from the DAM Center UI and does not match the names in the database). Otherwise the workflow may not work.

In the worst case, fixing the "Sync rootfolder" and "Destination rootfolder" does not fix the issue, then the "FromSyncFolderType" node in the workflow XML in the database may not be correct. This cannot be corrected via the UI. 

To fix it in the DB execute (be aware that must absolutely know what you're doing)

select PluginName, cast(settings as xml) as settings from digimonitor_customer_settings where PluginName = 'AssetSyncFolder'

--update digimonitor_customer_settings set settings = '' where PluginName = 'AssetSyncFolder'


Select the XML, alter the FromSyncFolderType to 1 in the correct node, uncomment the update statement, paste in the altered XML (the entire text) and execute the script again. 

Splash screen text might have changed upon update

(First seen in DC 4.8.0 / MM 4.9.1) When you update to a newer version of DC or MM, it may cause the splash screen title and text to change back to the default. The reason for this, is that the links between the title and text in the config parameters and the labels, have been broken. Therefore, please verify that the text in the Config Parameters section is correct. If not, you need to copy the title and text from Labels (Usually on page 9) into Config Parameters - both for Danish and English.


Web.config's guest user issues

If, for some reason, you're experiencing "logging in" with the guest user, will result in the name "Guest" appearing in the top right corner, instead og "Log in" as it usually is, and that you therefore cannot login with any other user, you need to go to the web.config file, and make certain that the place where the guest user is defined, the user's casing is matching the one in the DAM. I.e. "Guest" mustn't have "guest" in the web.config.

MM-3753 - Getting issue details... STATUS


Avatar crop appears as an asset in MM

When a user uploads their profile image, the ItemWatcher workflow "(MM) OOBE Give access to admins" will place the image in MM's "Admin Access" channel. This results in the profile image beíng available in MM as an ordinary asset. The fix is really simple:

Add " && <UploadComputer>Digizuite Media Manager</UploadComputer>" to the "Process only where this validation applies" text field in the DAM Center's workflow editor. Then the workflow will only process assets, that are uploaded normally in MM.

The value of the element (in my example the value is Digizuite Media Manager) is the value set in MM' config manager's "Upload channel ID". Beware that the client may have changed this.

 The issue: MM-3763.


Combobox metadata field issue

Combobox metadata fields cannot be opened if they don't have enough space below them.

The workaround is to add a description field below it (use "Note" e.g.) - to put it below, make it be the highest index number in the metagroup (configuarable in the DC)

MM 4.11.0

Link to the release notes for this release: MM 4.11.0

Known issues

Doesn't work with DC 4.7.1 - and probably all predecessors to DC 4.7.1 as well. Works with 4.8.0, and most likely every version afterwards.

Install (You need to know this before installing)

(Rare) Some installations have the fabled "Solr core can't save" issue

Don't change names on the channels MM -> Content -> Internal & Public


Update (You need to know this before updating)

For audio preview of pre MM 4.12.0 audio files to work, you need to republish your MM audio files manually.

Nice for PS to know



You need to change the web.config of the MM to include "|api" on line 98, as password reset depends on this. (At least 4.12.0 needs this [it has been implemented here], and I've been told that 4.11.0 also needs this)

allowDownload must be removed from assetInfo search (MM config)

Remove allowDownload from assetInfo search.


Emails are not sent from MM

Remove the HouseCo from the template as shown below.


MM 4.10.0

Link to the release notes for this release: MM 4.10.1

Known issues

Profile images can't be changed

You maybe can't use custom qualities

Install (You need to know this before installing)

.

Update (You need to know this before updating)

Copy the username of the MM embed user before update

.

Update (Help with troubleshooting)

Media Manager won't load correctly

Nice for PS to know

  • There has been changes to the programs you need in order to be able to build the .less file. You can find these changes in the prerequisites document.
  • DAMstat equals true is no longer a prerequisite in the MM's web.config for being able to download assets from MM.

MM 4.9.0/1

  • 4.9.1 needs .NET 4.6.2 and will actively ask for it during the update script step. (Updating from 4.9.0 RC3 does not require the update scripts). The web.config of 4.9.1 says it needs .NET 4.6.2, where the 4.9.0 asks for .NET 4.5.2.

  • Autotranslate seems to have an issue from the 4.6.0 installation (PSU/PSI have the same issue) - where the SQL-value "autotranslateoverwriteexisting" is set to 1. This will make titles overwrite when you change in one language - no matter if the other languages already have content or not. LS recommends this to be visible from the UI, so we can control it. I've created a case for this. (Use:

    update item_metafield set autotranslateoverwriteexisting = 0 where item_metafieldid=[Metatafield ID]

    to update your value to 0) (Use

    select name, item_metafieldid, autotranslate, autotranslateoverwriteexisting
    from item_metafield
    where item_metafieldid in (50181, 50182, 10192)

     to find title/description/keyword)

  • You need to have installed .NET framework 4.6.2 on the machine where you're hosting the MM 4.9.1. The update script will automatically send you to it if you do not have it installed already. (When you press enter in CMD)
  • Disclaimer should not be enabled in 4.9.1 setups, as you cannot edit the content of disclaimer through the Media Manager's settings-menu.
  • You have to manually enter the RGB value of your styling's/skinning's theme color (HEX per default) in the settings menu, as it'll change the first time you save settings in the MM Settings menu.
  • I've gotten "change splash screen background" working - Update: It was due to !\2\0\ being a requirement now
  • Enable DAM Stat through the web.config - else you'll not be able to download assets from the MM. (Something about the access key disappearing) <add key="EnableDAMStats" value="true" /> (As of 4.9.1 it seems HTTP also requires DAMStat is enabled (Bogballe didn't work without it))
  • I had troubles with no images loading - I had to delete some cached data.
  • You cannot upload more than 10 files at the time from MM. (Additionally there's a limiting factor, where you have to manually remove assets from the work-list - else they'll count towards the 10 files)

General known issues

When you perform a new installation or update, and you get an issue with the SchemaVersions table, you can do the following to correct the errors:

  1. Use the following script "Create SchemaVersions.sql"
  2. Use the admin_xxxx_dam user during the installation.

The reason why this error is happening, is that the user you're using to install does not have rights to create the table.

This has been an issue for some SA users in the past. Luckily, the admin_xxxx_dam users are created correctly, so using these is probably the best way to go.

Ps. it's not recommended to use SA to install with. The best practice is to use the admin_xxxx_dam user.

Template

Known issues


Install (You need to know this before installing)

.

Update (You need to know this before updating)

.

Update (Help with troubleshooting)