Images and document not visible after migration to liferay 6.1.0 GA1 - liferay-6

I upgrade from liferay 5.2.3 to 6.0.6 , it was successfully done without any error left; but when I upgrade from 6.0.6 to 6.1.0 GA1, unable to see the images and documents.
Steps related to images and documents I have done during migration(only related to documents are described).
during migration to 6.0.6 I wrote following lines to my portal-ext.prropeties file
image.hook.impl=com.liferay.portal.image.FileSystemHook
image.hook.file.system.root.dir=${liferay.home}/data/images
dl.hook.impl=com.liferay.documentlibrary.util.FileSystemHook
dl.hook.file.system.root.dir=${liferay.home}/data/document_library
I know in liferay 5.2.3 we have saved the images and documents to file system.
after this I start the server and migrated legacy permission to 6. It was successful , I was able to see the documents and images.
Now it turn to migrate from 6.0.6 to 6.1.0 GA1 , for that I wrote in these lines
image.hook.impl=com.liferay.portal.image.FileSystemHook
image.hook.file.system.root.dir=${liferay.home}/data/images
dl.hook.impl=com.liferay.documentlibrary.util.FileSystemHook
dl.hook.file.system.root.dir=${liferay.home}/data/document_library
start tomcat, migrate permissions to 6, after successful migration , re start the server but unable to see the documents and images. when ever trying to access the file in contents getting this error in tomcat console
Current URL /c/document_library/get_file?uuid=be4eecc7-8e9a-416c-aa4d-f3cbd855d759&groupId=14 generates exception: No file versions found for fileEntryId 61901
05:50:48,093 INFO [PortalImpl:4894] com.liferay.portlet.documentlibrary.NoSuchFileVersionException: No file versions found for fileEntryId 61901
com.liferay.portlet.documentlibrary.NoSuchFileVersionException: No file versions found for fileEntryId 61901
at com.liferay.portlet.documentlibrary.service.impl.DLFileVersionLocalServiceImpl.getLatestFileVersion(DLFileVersionLocalServiceImpl.java:67)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
can any one suggest what I am missing ?

image.hook.impl=com.liferay.portal.image.FileSystemHook
image.hook.file.system.root.dir=${liferay.home}/data/images
dl.hook.impl=com.liferay.documentlibrary.util.FileSystemHook
dl.hook.file.system.root.dir=${liferay.home}/data/document_library
is for telling liferay 6.1 from where to migrate documents and images
and to tell where to migrate them to you need to use new properties (this is what you were missing)
dl.store.impl=com.liferay.portlet.documentlibrary.store.FileSystemStore
dl.store.file.system.root.dir=/path/to/liferay6.1/document_library
Upgrade process will copy images and documents to new location (dl.store.file.system.root.dir) so be sure not to have same values for dl.hook.file.system.root.dir and dl.store.file.system.root.dir
EDIT
Above is for 6.1 EE.
For CE version only images should stay in original location and documents must manualy be moved/copied to new location.

Related

Sitefinity upgrade from 8.2 to 12.2 - Build succeeded but while running the project it gets stuck in between and nothing seems to be happening

I was trying to upgrade Sitefinity from 8.2 to 12.2 using the Sitefinity upgrade document. https://www.progress.com/documentation/sitefinity-cms/122/upgrade-from-sitefinity-cms-8.0-and-below
Steps followed :
Uninstalled the old version from Nuget
Changed the .Net framework to 4.7.2
Reinstall all packages
Added few properties in assemblyinfo.cs
Installed Sitefinity 12.2
Uninstalled Thunder, Dropbox libraries, Telerik.Sitefinity.MobileAppBuilder, Telerik.Sitefinity.DAM
Telerik.Sitefinity.EverliveConnector
Now the build is successful but it is getting stuck. Need some help with this. Is it ok to directly upgrade from 8.2 to 12.2 or upgrade from 8.2 to 10 and from 10 to 12.2? Which approach is preferred?
From the error messages in the comments of your post:
Value of 'null' is not valid for 'stream'...
Telerik.Sitefinity.Modules.Pages.PageTemplateHelper.UpdateDefaultTemplateImages(PageManager pageManager, LibrariesManager librariesManager, Album album) at Telerik.Sitefinity.Modules.Libraries.LibrariesModule.Upgrade(SiteInitializer initializer, Version upgradeFrom) at Telerik.Sitefinity.Services.ModuleBase.Install(SiteInitializer initializer, Version upgradeFrom) at Telerik.Sitefinity.Services.SystemManager.InitializeModuleTelerik.Sitefinity.Modules.Pages.PageTemplateHelper.UpdateDefaultTemplateImages(PageManager pageManager, LibrariesManager librariesManager, Album album) at
Telerik.Sitefinity.Modules.Libraries.LibrariesModule.Upgrade
(SiteInitializer initializer, Version upgradeFrom) at Telerik.Sitefinity.Services.ModuleBase
.Install(SiteInitializer initializer, Version upgradeFrom) at Telerik.Sitefinity.Services.SystemManager.InitializeModule
It looks the upgrade fails due to a problem with a page template thumbnail.
I suggest you run this SQL script towards the database - it will return all Image records (media content) for the page template thumbnails:
select * from sf_media_content as mc
join sf_content_link as cl
on cl.child_item_id = mc.content_id
where parent_item_type = 'Telerik.Sitefinity.Pages.Model.PageTemplate'
Have a look at the returned results and see if any of them looks suspicious.
Export the results to csv for easy access.
Then do a database backup.
Then, you can pick one of the images, e.g. one with default_url of: /images/SystemLibrariesProvider/template-thumbnails/mvc_default
and record its content_id, e.g. 78EB6662-F8C9-4A2E-85CA-966898D433F1
Then execute this SQL:
update sf_content_link
set child_item_id = '78EB6662-F8C9-4A2E-85CA-966898D433F1'
where parent_item_type = 'Telerik.Sitefinity.Pages.Model.PageTemplate'
Then kill the process and start the site.
If that image is good, the upgrade should proceed, if you were not lucky - then pick another content_id from your CSV and run the same update sql script with the new Id.
Restart and repeat until it works.
If all is good - you will end up with all page templates having the same thumbnail, but that's not a critical issue and can be fixed later.

Why is Talend giving ClassNotFoundException for SQLServerDriver

I've installed Talend ESB 6.5.1 and am trying to connect to a SQL Server database.
I tried using the JTDS driver, but that didn't work, and it appeared that I needed a DLL that wasn't included in the , and do I installed the pure java MS driver instead.
Talend has put the MS driver into Studio\workspace\xxx\temp\dbWizard having renamed it, but when I try to use it I get
Database connection is failed.
java.lang.RuntimeException: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
at org.talend.core.model.metadata.builder.database.JDBCDriverLoader.getConnection(JDBCDriverLoader.java:195)
...
It looks like Talend has put the jdbc driver somewhere, but it not referencing it correctly.
Any ideas what I need to do to get Talend to find it? (I've looked inside the .jar file and the class is definitely there.)
(Taking the generated JDBC URL and using this directly in a tJDBCInput with the driver jar selected works fine... bizarre)
The location where your jar was put does not look familiar. Try deleting all the jtds jar versions in the following locations :
<Talend root folder>\configuration\.m2\repository\org\talend\libraries
<Talend root folder>\lib\java
And restart your studio. When you go back to your component, you'll see an install button. You should be able to download and install the jar.

Upgrading to AEM 6.3

I just upgraded AEM from version 6.2 to Version 6.3. I see a folder called archived-versions created under crx-quickstart. Is it safe to delete the contents inside that folder?
I found a reference to archived-versions in an older upgrade documentation.
Note that your existing crx-quickstart/bin/ will be archived below crx-quickstart/archived-versions/. The precise path is given in the output of the above java -jar command. If you have customized any of the scripts in this directory, you can find those changed files in the archive.
https://docs.adobe.com/content/docs/en/cq/5-6-1/deploying/upgrading.html
From what I can tell it's safe to delete unless you've made modifications to start up scripts you may wish to keep.
Maybe moving all the content to a new AEM 6.3 instance instead of upgrading it is a better solution. This is usually what Adobe does with its AMS service.

Upgrading from Liferay 6.1.10 to Liferay 6.1.20

How to upgrade from Liferay 6.1.10 to Liferay 6.1.20 in a production environment? I haven't done this before, so might need some help/guide. As I understood from the searches, I need to download the 6.1.20 bundle, point to the database in the portal-ext.properties and start liferay. Is this the correct process? Thanks.
In theory (assuming that there is no custom code - we bare Liferay) like this:
perform backup
stop portal
unzip next Liferay 6.1.1
Copy it (replacing) files settings (portal-ext.properties, portal-wizard-setup.properties and others - if you were), it is important to follow that would:
сonnection settings copied to the database - that is, portal use the same database as the previous; portal-setup-wizard.properties correct liferay.home - that would be shown on a new directory (or, that which then will run a new version of Liferay)
copied from the old portal folder "data" and place it in the new.
That is, you get a new portal that looks into the old database and used old data. Further launching a new version Liferay.
At the start of Liferay itself has cut the base is old and will perform its update (automatically). After that, put all the additional portlets that were with you before.
This theory - practically there are deviations (for backup and done - that we could quickly rever back)

Error using MongoDB.Web: MongoDB.Driver.SafeModeResult MongoDB.Driver.MongoCollection.Insert(!!0)

I am getting the following error using the MongoDB.Web membership provider:
Method not found: 'MongoDB.Driver.SafeModeResult MongoDB.Driver.MongoCollection.Insert(!!0)'.
I have the simplest of implementations:
Visual Studio Express 2012
Empty Website project (VB.NET) with a standard index.aspx added
Nuget packages: MongoDB.Web 1.2, mongocsharpdriver 1.7
MongoDB db version 2.2.3
Windows 7 64-bit
(All Mongo elements downloaded fresh today.)
I copied and pasted the Membership provider web.config details from the FreshLogic site, and modified only the database and collection attributes to reference my desired collection.
I have one line of code in the Page.Load event of my index.aspx:
Membership.CreateUser("fred124243", "Passw0rd$123")
I get the aforementioned error when I run the solution. I can see that my collection gets created, so the solution is communicating with MongoDB.
Any help greatly appreciated!
Answering my own question... I had to download MongoDB.Web source from Git and recompile.