Files isn't converted when upgrading to 6.2.1 from 4.6.2

Questions
1

Hi,

Values in field of type File in CMS isn’t converted when upgrading from 4.6.2 to 6.2.1. Data is still stored in old format in table CMS_PagePropertValue and CMS_PageProperty. PropertyType and ValueType have the value 4 (FILE) which will cause error in Accelerator Controllers when mapping to model.

Not valid authority.

When adding files in Backoffice after upgrade the value in PropertyType and ValueType are set to 17 (FILE_FROM_MEDIA_ARCHIVE).

Is there a sql script that converts the files to the new property type? Otherwise I guess we have to delete the files in the db and then add them manually in backoffice? Or is there another solution the problem?

Litium version: 6.2.1

2

This is tracked by https://docs.litium.com/support/bugs/bug_details?id=45295 and will be included in the next 6.x release. Prerelease exists that you can use until the new release is out.

3

Thanks! I will try the prerelease

4

We’ve tried the prerelease 6.3.2-patch-1903221330 and now the page loads without exception and the list of files is displayed as it should. But unfortunately the links generated isn’t correct, we get a 404 when clicking on the links.

When downloading the file in media library the link look like this:
/storage/ma/118a01fed0064bb6b31a59b77c2d015e/f0c8b0b3556b4f57b1946021035d501a/pdf/41B099E998C17A7BAF5178044A567A223A3E8810/Test.pdf

The link generated in the page look like this:
/storage/cms/1accfe6da8c64107ab735a3401beaac7/698df6da264946e8ad49ae3f89877807/pdf/3BA45B2E93CA4B9A48633475257786607EC47D30/Test.pdf

The Guid “1accfe6da8c64107ab735a3401beaac7” is the PageID and “698df6da264946e8ad49ae3f89877807” is a part of the FileStoragePath

5

The files that are directly uploaded in the editor or attached to the file/image properties in older version is not moved into media so you will not find them there. the ma/cms part is identifier for where in the system and from the above link it is not the same Test.pdf you have in media as you are using on your page.

Please, check that you have the actual file on disk, should exists in the storage\cms-directory belov the commonFiles (or files) folder. the sub-directories are created from the file-storage-path-UUID. Also check that your user have read-access to the page where the file is added to.

6

The files do exist on disc but are located here for instance:
“/storage/CMS/3e/a3/3ea33604-ef49-4604-8e81-0a528a7ace9d.pdf”

This link is stored correct in column “FileStoragePath” in table “CMS_PagePropertyValue”

Link generated on the page for the same pdf is:
“/storage/cms/29b653bd4c994944b13166fe3c398ae1/1dede1e1a2934194afe1b27c9e2093b3/pdf/602B87F27FB2E0816BDE3E8CAC67D0D705E73842/Retur%20av%20gods.pdf”

7

You pointing out that the physical file have the 3ea33604-ef49-4604-8e81-0a528a7ace9d as storage id and the generated link have 1dede1e1-a293-4194-afe1-b27c9e2093b3, that does not seams correct. Are you checking the link on the public site and not in the editor inside BO? When an working copy is created a copy of the file will be created and when you publish the original file will be deleted.

With the information in this thread it is hard to say what your issue depend on. Please, open a support ticket at support@litium.com to get help with solving the issue.