Andrew Jardine 4 Years Ago - Edited As a long time Liferay developer and community member, I know I have a bias, but I have to say that, after playing with this release for almost two days now, it's really exciting to see the direction Liferay is heading in. The power and control it gives to users who are less technical, or less familiar with Liferay is great, but the fact that Liferay is not doing this at the expense of the developers (by continuing to provide such a rich API) is awesome. Well done once again. Each release of this product continues to keep me excited about what's next. :) Please sign in to reply. Reply as... Cancel
Krzysztof Gołębiowski 4 Years Ago - Edited It's great to have URL redirection finally in Liferay! I can't count how many times I implemented it on my own in the past :) Please sign in to reply. Reply as... Cancel
Eric D 4 Years Ago - Edited Great, I like this rolling release mode... It is always great to have new functionalities. We will upgrade from 7.3.1 ga2 to 7.3.2 ga3 in few days.. I have only one question : The new release.portal.api property is available for maven projects ? Eric. Please sign in to reply. Reply as... Cancel Jamie Sammons Eric D 4 Years Ago Hi Eric, Yes I believe it will work with Maven as well: https://mvnrepository.com/artifact/com.liferay.portal/release.portal.api/7.3.2-ga3 Please sign in to reply. Reply as... Cancel
Jamie Sammons Eric D 4 Years Ago Hi Eric, Yes I believe it will work with Maven as well: https://mvnrepository.com/artifact/com.liferay.portal/release.portal.api/7.3.2-ga3 Please sign in to reply. Reply as... Cancel
Christoph Rabel 4 Years Ago - Edited How do I create a fragment with a dropzone? Bug: jQuery is used in the carousel fragment. But jQuery is disabled per default in 7.3. -> Carousel does not work. Please sign in to reply. Reply as... Cancel Christoph Rabel Christoph Rabel 4 Years Ago - Edited Ok, found it. Works perfectly in a quick test. <lfr-drop-zone id="123"></lfr-drop-zone> Please sign in to reply. Reply as... Cancel
Christoph Rabel Christoph Rabel 4 Years Ago - Edited Ok, found it. Works perfectly in a quick test. <lfr-drop-zone id="123"></lfr-drop-zone> Please sign in to reply. Reply as... Cancel
gnp present 4 Years Ago - Edited Hi..jQuery not works even i checked enabled in system settings/third party. What i'm missing?? Please sign in to reply. Reply as... Cancel Jamie Sammons gnp present 4 Years Ago When I ran into this I believe it was a browser caching issue. Try incognito or another browser to see if that fixes it. Please sign in to reply. Reply as... Cancel
Jamie Sammons gnp present 4 Years Ago When I ran into this I believe it was a browser caching issue. Try incognito or another browser to see if that fixes it. Please sign in to reply. Reply as... Cancel
Fuad Efendi 4 Years Ago - Edited Is it easy to upgrade from 7.3.0 GA1 to 7.3.2 GA3? I still remember days when starting new version will upgrade everything automatically Please sign in to reply. Reply as... Cancel Jamie Sammons Fuad Efendi 4 Years Ago Upgrading between 7.3.x versions seems to be working better for me in my testing. It's faster and I seem to have less issues with it. You have the option of upgrading on startup again by setting upgrade.database.auto.run=true in your properties file. I would be hesitant to use it in production but it's nice in test/dev. Please sign in to reply. Reply as... Cancel Fuad Efendi Jamie Sammons 4 Years Ago - Edited Hi Jamie, where can I find documentation for Liferay CE upgrade? My understanding is I don't need do download full new distribution and point it to existing database; instead, upgrade tool will do it for me? liferay-ce-portal-tools-[version].zip (with properly configured property files pointing to existing location) will download even new Tomcat version if needed? I am confused. Please sign in to reply. Reply as... Cancel Olaf Kock Fuad Efendi 4 Years Ago You should run the standalone upgrade tool. Since the rolling releases, there are new features in every GA, and they might require database upgrades. The full portal doesn't do this any more. With regards to code/binary updates: This is up to you. The upgrade routines won't touch your application server, and not even Liferay's code - only the stored data: While Tomcat is provided in a bundle, and newer tomcat versions will be used in later bundles, upgrading and maintaining tomcat is fully on your end. Nothing within Liferay (not even within Liferay DXP) will touch that part of your installation. Naturally, if you unzip an upgraded bundle to a new location, you'll end up with that bundle's tomcat version. With Liferay DXP, you'll get a Patching Tool that will take care of binary updates to Liferay components (e.g. jars, and other files living within the web application), but none of that will touch the appserver either. And the Patching Tool doesn't touch the database at all. E.g. you might need to run the upgrade tool on top of the patching tool. Please sign in to reply. Reply as... Cancel Fuad Efendi Olaf Kock 4 Years Ago - Edited UNCLEAR: why database upgrade tool needs app-server.properties file? Documentation says I need to configure it before running upgrade tool. It must be independent, isn't it, WebLogic vs. Tomcat - database must be the same. Another bug? Please sign in to reply. Reply as... Cancel Fuad Efendi Fuad Efendi 4 Years Ago - Edited I suspect upgrade tool needs access to portal classpath (at least, JDBC driver which is in tomcat-x.y.zz/lib/ext in tomcat bundle) that's why we have to configure app-server.properties? and default setting is to pick dependencies from same unpacked bundle; otherwise we need to point explicitly. Thanks. Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 4 Years Ago - Edited The full portal can do it too, the feature was reintroduced in 7.3, but the upgrade tool is the recommended way. You can set the property "upgrade.database.auto.run=true" in portal-ext. The feature is there for docker environments. @Fuad Efendi: https://learn.liferay.com/dxp-7.x/installation-and-upgrades/upgrading-liferay-dxp/upgrade_basics.html Please sign in to reply. Reply as... Cancel
Jamie Sammons Fuad Efendi 4 Years Ago Upgrading between 7.3.x versions seems to be working better for me in my testing. It's faster and I seem to have less issues with it. You have the option of upgrading on startup again by setting upgrade.database.auto.run=true in your properties file. I would be hesitant to use it in production but it's nice in test/dev. Please sign in to reply. Reply as... Cancel Fuad Efendi Jamie Sammons 4 Years Ago - Edited Hi Jamie, where can I find documentation for Liferay CE upgrade? My understanding is I don't need do download full new distribution and point it to existing database; instead, upgrade tool will do it for me? liferay-ce-portal-tools-[version].zip (with properly configured property files pointing to existing location) will download even new Tomcat version if needed? I am confused. Please sign in to reply. Reply as... Cancel Olaf Kock Fuad Efendi 4 Years Ago You should run the standalone upgrade tool. Since the rolling releases, there are new features in every GA, and they might require database upgrades. The full portal doesn't do this any more. With regards to code/binary updates: This is up to you. The upgrade routines won't touch your application server, and not even Liferay's code - only the stored data: While Tomcat is provided in a bundle, and newer tomcat versions will be used in later bundles, upgrading and maintaining tomcat is fully on your end. Nothing within Liferay (not even within Liferay DXP) will touch that part of your installation. Naturally, if you unzip an upgraded bundle to a new location, you'll end up with that bundle's tomcat version. With Liferay DXP, you'll get a Patching Tool that will take care of binary updates to Liferay components (e.g. jars, and other files living within the web application), but none of that will touch the appserver either. And the Patching Tool doesn't touch the database at all. E.g. you might need to run the upgrade tool on top of the patching tool. Please sign in to reply. Reply as... Cancel Fuad Efendi Olaf Kock 4 Years Ago - Edited UNCLEAR: why database upgrade tool needs app-server.properties file? Documentation says I need to configure it before running upgrade tool. It must be independent, isn't it, WebLogic vs. Tomcat - database must be the same. Another bug? Please sign in to reply. Reply as... Cancel Fuad Efendi Fuad Efendi 4 Years Ago - Edited I suspect upgrade tool needs access to portal classpath (at least, JDBC driver which is in tomcat-x.y.zz/lib/ext in tomcat bundle) that's why we have to configure app-server.properties? and default setting is to pick dependencies from same unpacked bundle; otherwise we need to point explicitly. Thanks. Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 4 Years Ago - Edited The full portal can do it too, the feature was reintroduced in 7.3, but the upgrade tool is the recommended way. You can set the property "upgrade.database.auto.run=true" in portal-ext. The feature is there for docker environments. @Fuad Efendi: https://learn.liferay.com/dxp-7.x/installation-and-upgrades/upgrading-liferay-dxp/upgrade_basics.html Please sign in to reply. Reply as... Cancel
Fuad Efendi Jamie Sammons 4 Years Ago - Edited Hi Jamie, where can I find documentation for Liferay CE upgrade? My understanding is I don't need do download full new distribution and point it to existing database; instead, upgrade tool will do it for me? liferay-ce-portal-tools-[version].zip (with properly configured property files pointing to existing location) will download even new Tomcat version if needed? I am confused. Please sign in to reply. Reply as... Cancel Olaf Kock Fuad Efendi 4 Years Ago You should run the standalone upgrade tool. Since the rolling releases, there are new features in every GA, and they might require database upgrades. The full portal doesn't do this any more. With regards to code/binary updates: This is up to you. The upgrade routines won't touch your application server, and not even Liferay's code - only the stored data: While Tomcat is provided in a bundle, and newer tomcat versions will be used in later bundles, upgrading and maintaining tomcat is fully on your end. Nothing within Liferay (not even within Liferay DXP) will touch that part of your installation. Naturally, if you unzip an upgraded bundle to a new location, you'll end up with that bundle's tomcat version. With Liferay DXP, you'll get a Patching Tool that will take care of binary updates to Liferay components (e.g. jars, and other files living within the web application), but none of that will touch the appserver either. And the Patching Tool doesn't touch the database at all. E.g. you might need to run the upgrade tool on top of the patching tool. Please sign in to reply. Reply as... Cancel Fuad Efendi Olaf Kock 4 Years Ago - Edited UNCLEAR: why database upgrade tool needs app-server.properties file? Documentation says I need to configure it before running upgrade tool. It must be independent, isn't it, WebLogic vs. Tomcat - database must be the same. Another bug? Please sign in to reply. Reply as... Cancel Fuad Efendi Fuad Efendi 4 Years Ago - Edited I suspect upgrade tool needs access to portal classpath (at least, JDBC driver which is in tomcat-x.y.zz/lib/ext in tomcat bundle) that's why we have to configure app-server.properties? and default setting is to pick dependencies from same unpacked bundle; otherwise we need to point explicitly. Thanks. Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 4 Years Ago - Edited The full portal can do it too, the feature was reintroduced in 7.3, but the upgrade tool is the recommended way. You can set the property "upgrade.database.auto.run=true" in portal-ext. The feature is there for docker environments. @Fuad Efendi: https://learn.liferay.com/dxp-7.x/installation-and-upgrades/upgrading-liferay-dxp/upgrade_basics.html Please sign in to reply. Reply as... Cancel
Olaf Kock Fuad Efendi 4 Years Ago You should run the standalone upgrade tool. Since the rolling releases, there are new features in every GA, and they might require database upgrades. The full portal doesn't do this any more. With regards to code/binary updates: This is up to you. The upgrade routines won't touch your application server, and not even Liferay's code - only the stored data: While Tomcat is provided in a bundle, and newer tomcat versions will be used in later bundles, upgrading and maintaining tomcat is fully on your end. Nothing within Liferay (not even within Liferay DXP) will touch that part of your installation. Naturally, if you unzip an upgraded bundle to a new location, you'll end up with that bundle's tomcat version. With Liferay DXP, you'll get a Patching Tool that will take care of binary updates to Liferay components (e.g. jars, and other files living within the web application), but none of that will touch the appserver either. And the Patching Tool doesn't touch the database at all. E.g. you might need to run the upgrade tool on top of the patching tool. Please sign in to reply. Reply as... Cancel Fuad Efendi Olaf Kock 4 Years Ago - Edited UNCLEAR: why database upgrade tool needs app-server.properties file? Documentation says I need to configure it before running upgrade tool. It must be independent, isn't it, WebLogic vs. Tomcat - database must be the same. Another bug? Please sign in to reply. Reply as... Cancel Fuad Efendi Fuad Efendi 4 Years Ago - Edited I suspect upgrade tool needs access to portal classpath (at least, JDBC driver which is in tomcat-x.y.zz/lib/ext in tomcat bundle) that's why we have to configure app-server.properties? and default setting is to pick dependencies from same unpacked bundle; otherwise we need to point explicitly. Thanks. Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 4 Years Ago - Edited The full portal can do it too, the feature was reintroduced in 7.3, but the upgrade tool is the recommended way. You can set the property "upgrade.database.auto.run=true" in portal-ext. The feature is there for docker environments. @Fuad Efendi: https://learn.liferay.com/dxp-7.x/installation-and-upgrades/upgrading-liferay-dxp/upgrade_basics.html Please sign in to reply. Reply as... Cancel
Fuad Efendi Olaf Kock 4 Years Ago - Edited UNCLEAR: why database upgrade tool needs app-server.properties file? Documentation says I need to configure it before running upgrade tool. It must be independent, isn't it, WebLogic vs. Tomcat - database must be the same. Another bug? Please sign in to reply. Reply as... Cancel Fuad Efendi Fuad Efendi 4 Years Ago - Edited I suspect upgrade tool needs access to portal classpath (at least, JDBC driver which is in tomcat-x.y.zz/lib/ext in tomcat bundle) that's why we have to configure app-server.properties? and default setting is to pick dependencies from same unpacked bundle; otherwise we need to point explicitly. Thanks. Please sign in to reply. Reply as... Cancel
Fuad Efendi Fuad Efendi 4 Years Ago - Edited I suspect upgrade tool needs access to portal classpath (at least, JDBC driver which is in tomcat-x.y.zz/lib/ext in tomcat bundle) that's why we have to configure app-server.properties? and default setting is to pick dependencies from same unpacked bundle; otherwise we need to point explicitly. Thanks. Please sign in to reply. Reply as... Cancel
Christoph Rabel Olaf Kock 4 Years Ago - Edited The full portal can do it too, the feature was reintroduced in 7.3, but the upgrade tool is the recommended way. You can set the property "upgrade.database.auto.run=true" in portal-ext. The feature is there for docker environments. @Fuad Efendi: https://learn.liferay.com/dxp-7.x/installation-and-upgrades/upgrading-liferay-dxp/upgrade_basics.html Please sign in to reply. Reply as... Cancel
Matthieu GENOVESE 3 Years Ago - Edited Hello and thanks for this update :). All works good for us. Have you an idea if the integration of elasticsearch Connector 7 will be release soon ? i tried it with GA3 but still doesn't work :( Please sign in to reply. Reply as... Cancel
Max Max Max 3 Years Ago - Edited I love the new functionality that comes with Liferay but absolutely dread the upgrade. In the past each upgrade has failed and I end up recreating the whole thing from scratch. This time I cannot, and need to perform an upgrade from 7.3.0 to 7.3.2. There are lots of comments here referencing an upgrade tool and the documentation. Unfortunately none of the referenced links work and also the links are all for the paid DXP version not the CE version. I looked at the upgrade documentation for DXP 7.1 (7.2 is not accessible to CE users) here: https://help.liferay.com/hc/en-us/articles/360018176751-Running-the-Upgrade-Tool- These instructions are also not clear to me, as a simple user not a full-time Liferay administrator. There seem to be lots of documentation for all sorts of side cases and it looks like a full days reading to understand how to perform an upgrade. Can someone maybe direct me to a simple set of instructions to upgrade a vanilla 7.3.0 to 7.3.2 please. My current installation is not Docker, so I am assuming the Docker based upgrade is not for me. I ran the db_upgrade.sh tool under the /tools directory of the freshly downloaded and extracted 7.3.2 bundle. These instructions never seem to ask for the old installation directory of Liferay 7.3.0 and after successfully running it, it made changes to my DB but what about the files under the old /data/document_library? As the upgrade tool didn't explicitly ask for my old installation directory and the database itself doesn't know where the actual old installation is, does this mean my documents are no longer there? I looked everywhere online for a simple set up upgrade instructions and came up empty. No You Tube videos, only references to DXP super tools that are unavailable to the CE community on this website. Is the CE upgrade tool able to migrate anything else but the DB? Do I have to read pages up DXP documentation to figure out how to move the other data, or is there a utility like db_upgrade that asks: 1) Where is your old Liferay directory, 2) Where is your new Liferay directory, 3) Click upgrade? Surely all the information required is already all there? Sorry for the rant, love the software, but Liferay upgrades are not my best friend. Please sign in to reply. Reply as... Cancel Christoph Rabel Max Max Max 3 Years Ago - Edited The upgrade tool often only upgrades the database (some Liferay version upgrades also moved files around, but often the data folder is ignored). You have to copy it manually and I recommend to do it before you start the upgrade process. The steps to upgrade are basically: 1) Create a backup/test the upgrade and everything on the backup till everything works 2) Unpack new version 3) Copy data/* from old Liferay to new Liferay/data/ 4) Update portal-*.properties according to old files 5) Update server.xml, setenv.sh, ... (Well, basically apply all configuration changes to new Liferay) 6) Start dbupgrade.sh 7) Check logs for errors, if everything is fine, proceed 8) Start Liferay 9) Check if everthing works, files should be there 10) Probably reindex 11) Update your modules and deploy them 12) Check if everthing works as expected 13) Repeat with production hth Please sign in to reply. Reply as... Cancel Max Max Max Christoph Rabel 3 Years Ago - Edited Hi Christoph, Thank you for these instructions, very helpful. I followed them with the following exceptions and got the upgrade to work: When copying the data/* directory a) I copied only the document_library dir because when I copied the elasticsearch dir as well I got exceptions thrown during the db_upgrade.sh process, as well 100's of framework exceptions during liferay startup. b) I also first deleted the content of the new installations /data/document_library dir. I had a few issues with portal-*.properties files, I only copied the root portal-setup-wizard.properties file across and also edited the file to change the location of the home dir for the app server. New install seems to be running fine now, so thank you very much for your help. Max Please sign in to reply. Reply as... Cancel Christoph Rabel Max Max Max 3 Years Ago - Edited All fine. a) I usually use an external ES server, it's better for performance and management reasons. Only the document_library folder is needed. Note: It is also recommended to disable the indexer for the upgrade. See: https://help.liferay.com/hc/en-us/articles/360017896372-Preparing-an-Upgrade-to-Liferay-DXP-7-0 b) Yes, good. Personal opinion: Upgrades have become better. I had a lot more troubles with Liferay 6.x -> 6.y than with any 7.x -> 7.y upgrade. Please sign in to reply. Reply as... Cancel Max Max Max Max Max Max 3 Years Ago - Edited Spoke too soon. Seems like I'm already down the Liferay upgrade rabbit hole and I didn't know it. After the upgrade all my users have simply vanished from the user list. When I try and recreate a user who I know used to exist, I get an error saying the screen name is already taken, so I know there're in there somewhere. I'm getting errors in the logs like: /group/control_panel/manage?p_p_id=com_liferay_roles_admin_web_portlet_RolesAdminPortlet&p_p_lifecycle=0&p_p_state=normal&p_p_state_rcv=1&p_p_auth=jLefuZys is not allowed Does this mean my old admin user is no longer an admin user in the upgraded system? If this is the wrong forum to post this for CE questions, please will someone direct me to the correct forum. Thx, Max Please sign in to reply. Reply as... Cancel Jorge Ferrer Max Max Max 3 Years Ago Hey Max, It seems your index is not complete. You should be able to solve this by going to Control Panel > Configuration > Search and do a reindex Please sign in to reply. Reply as... Cancel Max Max Max Jorge Ferrer 3 Years Ago - Edited Hi Jorge. Thanks, this did the trick for the missing Users. I have an additional problem. I have images embedded in content pages. The images show up correctly in the page when viewed, but only as a little gray rectangle when in the editor. The name of the image seems correct, but it doesn't display at all in the editor. Any ideas why? Please sign in to reply. Reply as... Cancel Max Max Max Max Max Max 3 Years Ago - Edited Sorry, meant to also say that the images all appeared in the editor fine before the upgrade. Please sign in to reply. Reply as... Cancel Christoph Rabel Max Max Max 3 Years Ago - Edited Questions, especially complicated ones, are best asked in the forum: https://liferay.dev/forums Only people who read the blog or have answered previously to the blog post here, will see here. It is also more comfortable to answer there and faster, since posts there aren't reviewed. Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Thank you for listing these, Christoph. These steps and more information are included in the Upgrade Overview: https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay-dxp/upgrade-basics/upgrade-overview.html Please sign in to reply. Reply as... Cancel Christoph Rabel Jim Hinkey 3 Years Ago - Edited Ok, where does it explain that the content of the data folder has to be copied to the new instance? The section in "Using the Database Upgrade Tool" makes some assumptions that I are almost never true. -- cp /old-version/liferay-home/ /new-version/liferay-home/ cd /new-version/liferay-home/tools/portal-tools-db-upgrade-client db_upgrade.sh -j "-Dfile.encoding=UTF-8 -Duser.timezone=GMT -Xmx2048m" -l "output.log" -- Apart from the obviously missing "-r" parameter, an average user would here copy the old liferay folder (containing the old binaries and everything) and execute the db upgrade client of the old version. Maybe wondering why he was doing that. This text obviously assumes that Liferay Home is "elsewhere", and not equal to the unzipped Liferay folder. Nice idea, but I have never ever seen a CE installation where Liferay home is set manually to an external folder. If this is documented somewhere, fine. But still, nobody does that and so, that upgrade description won't work. Please sign in to reply. Reply as... Cancel Olaf Kock Christoph Rabel 3 Years Ago > where does it explain that the content of the data folder has to be copied to the new instance? It says, in the warning in the beginning: "Testing the upgrade process on backup copies is advised." Instead of "copying random data from left to right", I'd personally rather restore a backup on completely unrelated hardware, without any connection to production servers. Then assert that my backup is worth it's money by assuring that it's an exact copy of my production environment. Only then start upgrade work. Upon any problem: Rinse/Repeat. It's sooo relaxing to have proof that a backup actually can be used to reliably restore a system Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 3 Years Ago - Edited You still need to know what you have to change in your restored backup to upgrade it, so you need to know which steps are necessary and which files are relevant to the upgrade. The described upgrade steps are simply not correct. Please sign in to reply. Reply as... Cancel Olaf Kock Christoph Rabel 3 Years Ago On the one hand: Yes. On the other hand: You hopefully have figured out what to back up (and how to restore) loooooong before you ever attempt an upgrade. IMHO the steps can be simplified by "restore your backup to a completely new system - just the same way as you've tested before for cases when your main server disappears. Then use this restored system for further upgrade operations." That's a universal way to phrase the instructions. Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 3 Years Ago - Edited Well. Not really. I have seen several companies, where the backup strategy is: "We take snapshots of the VM ..." Also, if you backup the whole Liferay folder and the database, it will work too. So. Now what? Anyway, this is nitpicking. The upgrade guide should be like a cooking recipe and/or a checklist. Unzip new package. Copy these folders. Copy portal-*.properties Check portal-*.properties and update liferay.home Check ... Did you update any files manually? Please check especially server.xml, setenv.sh, files in osgi/configuration folder, ... Hint: Unpack the file with the old Liferay version and use a compare tool. and so on ... I know what to do because I did it countless times. But for people, who do this the first time, it should be cover as many bases as possible. Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Hi Christoph, We're fixing the upgrade steps and making them clearer. Regarding the "-r" parameter you're mentioning for db_upgrade.sh, I'm not familiar with it (it doesn't come up in --help) and will ask about it. Thank you for your input. Jim Please sign in to reply. Reply as... Cancel Christoph Rabel Jim Hinkey 3 Years Ago - Edited -r for cp (Linux shell copy), not db_upgrade. -r is necessary for directories. "cp /old-version/liferay-home/ /new-version/liferay-home/" --> Error Things like that make it perfectly clear for me that nobody has ever tested these steps because the first line fails always without exception. I think the upgrade steps should first explain, what each folder* does. If something like that doesn't exist already, it would be really helpful so that people understand what is tomcat, what is configuration, what is data, what is temporary(and can be deleted). * Some files should be explained too. Please sign in to reply. Reply as... Cancel Krzysztof Gołębiowski Max Max Max 3 Years Ago - Edited Hi Max, the upgrade process is quite simple in general, most of the other things you mentioned (document library, properties) are just being copied from old Liferay to new "as they are". There might be some problems with 7.3 as it is still unstable and hasn't been officially released yet, but usually, it's quite straightforward. You could write a post on Liferay forums if you have some issues, I think it's a better place to get help than here. Please sign in to reply. Reply as... Cancel Jorge Ferrer Max Max Max 3 Years Ago Hey Max Max Max, I'm sorry to hear that you have had so many problems upgrading between rolling releases. Our promise is that those upgrades should be very easy in a wide majority of cases (the only exceptions could be when there are heavy customization or db inconsistencies). In order to improve, I'd like to know more about your problems to find out if the root cause is in lack or inaccurate documentation or actual problems in the automated upgrade processes. Did the steps mentioned by Christoph help? Are you able to successfully upgrade following them or do you find still run into problems? Please sign in to reply. Reply as... Cancel Max Max Max Jorge Ferrer 3 Years Ago - Edited Hi Jorge, I can't remember the details of my past upgrade problems but I often remember db errors appearing everywhere. The main problem with this upgrade was to find the set of instructions that Christoph was so kind as to type up. If these instructions are elsewhere in the Liferay documentation, then it would be good to link tho this in the release notes or in this announcement for us plebs. Max Please sign in to reply. Reply as... Cancel Jim Hinkey Max Max Max 3 Years Ago Hi Max, Updating from one 7.3 Liferay Portal CE GA to another GA is demonstrated in the following article: Updating Liferay Portal CE - https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/maintaining-a-liferay-dxp-installation/patching-liferay/updating-liferay-portal-ce.html I'm sorry you didn't find it. We're going to add the article to the upgrade section so that it can be found there too. My apologies. Note, if you do need to upgrade from an earlier version (e.g., from 7.2 Liferay Portal CE) you can run the upgrade using a Docker image. That is, you can continue using an on-premises installation but simply use a Docker image to upgrade your database. The CE Docker images are mentioned in the second paragraph in the article Upgrading Via Docker - https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay-dxp/upgrade-basics/upgrading-via-docker.html I hope that makes your upgrade a quick success! Jim Please sign in to reply. Reply as... Cancel Max Max Max Jim Hinkey 3 Years Ago - Edited Hi Jim, Thanks for pointing me to the upgrade page. The upgrade instructions on that page are very different to the instructions given by other to me here. There are also ambiguities if you can please clear up for me before I attempt this upgrade again. - There is no mention of any copying of the data directory across. - There is no mention of using the db_upgrade.sh script. Using this script sounds MUCH easier than a) learning how to use the gogo shell and b) going through 5 different gogo steps for each module. - Step 5: Clean up DXP cache. - I assume this is on the new installation? - Step 6: Start the application server again. - According to the instructions I have not started the new server yet, so do I start the old server 'again'. Why? - I assume again I run the gogo shell here against the new server and no the old. @Jorge: I am certainly not looking forward to going through all this every time I upgrade . This is exactly what scares me about every Liferay upgrade I have to do. I just read a post that there is some error in the 7.3.2 upgrade script where some db column is not properly upgraded and users cannot be deleted anymore. Any small DB error seems to propagate through the upgrades and after two upgrades the DB breaks and I end up having to throw it away and start from scratch. My above mentioned upgrade attempt that resulted in my users disappearing and permissions broken leaves me with the permanent niggle in my back of my mind that my DB is corrupted and there are other things that will just break down the line and I will sit for days on forums trying to figure out what. That is why I often just cave in an install from scratch and manually copy stuff over because that crazily feels easier to me than the potential future issues. But that is not a real solution long term. Please sign in to reply. Reply as... Cancel Christoph Rabel Jim Hinkey 3 Years Ago - Edited Where does it explain that the document_library folder has to be copied? Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Hi Christoph, We're still in the process of fixing and improving the documentation for upgrading a Portal CE rolling release. You can follow progress at https://issues.liferay.com/browse/LRDOCS-8053. The steps include copying the data folder, which includes the document library if that's where you have configured you've configured your File Store to be there. Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Christoph, Max, The upgrade documentation has been improved based on your questions and suggestions. Here's a summary of the changes: Upgrade Overview https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/upgrade-overview.html - The overview is always the best place to start when considering an upgrade for DXP or CE. It explains what areas to consider and which database upgrade approach(es) to consider. The articles that follow center on database upgrade, but list steps for all parts of the upgrade (including migrating data/ folder contents and configuration files) and link to detail articles where needed. Backing up your existing installation and using a backup installation/db copy is essential--we warn about this in the overview and articles on upgrading using Docker and the Database Upgrade Tool. Upgrading Via Docker https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/upgrading-via-docker.html - Is for non-critical CE upgrades, especially upgrading from one rolling release to another (e.g., 7.3.0 - 7.3.x). Note, your new installation need not be a Docker image, you're just using the Docker image to upgrade your database. Using the Database Upgrade Tool https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/using-the-database-upgrade-tool.html - Is for any Liferay edition (DXP or CE), but is a must for DXP, critical servers, and clustered environments. It allows you to dive deeper into database upgrades, when things don't work in one shot (e.g., Upgrading via Docker). I hope you find the improvements helpful and easy to follow. We're open to more suggestions. And thank you for your patience. Jim Please sign in to reply. Reply as... Cancel
Christoph Rabel Max Max Max 3 Years Ago - Edited The upgrade tool often only upgrades the database (some Liferay version upgrades also moved files around, but often the data folder is ignored). You have to copy it manually and I recommend to do it before you start the upgrade process. The steps to upgrade are basically: 1) Create a backup/test the upgrade and everything on the backup till everything works 2) Unpack new version 3) Copy data/* from old Liferay to new Liferay/data/ 4) Update portal-*.properties according to old files 5) Update server.xml, setenv.sh, ... (Well, basically apply all configuration changes to new Liferay) 6) Start dbupgrade.sh 7) Check logs for errors, if everything is fine, proceed 8) Start Liferay 9) Check if everthing works, files should be there 10) Probably reindex 11) Update your modules and deploy them 12) Check if everthing works as expected 13) Repeat with production hth Please sign in to reply. Reply as... Cancel Max Max Max Christoph Rabel 3 Years Ago - Edited Hi Christoph, Thank you for these instructions, very helpful. I followed them with the following exceptions and got the upgrade to work: When copying the data/* directory a) I copied only the document_library dir because when I copied the elasticsearch dir as well I got exceptions thrown during the db_upgrade.sh process, as well 100's of framework exceptions during liferay startup. b) I also first deleted the content of the new installations /data/document_library dir. I had a few issues with portal-*.properties files, I only copied the root portal-setup-wizard.properties file across and also edited the file to change the location of the home dir for the app server. New install seems to be running fine now, so thank you very much for your help. Max Please sign in to reply. Reply as... Cancel Christoph Rabel Max Max Max 3 Years Ago - Edited All fine. a) I usually use an external ES server, it's better for performance and management reasons. Only the document_library folder is needed. Note: It is also recommended to disable the indexer for the upgrade. See: https://help.liferay.com/hc/en-us/articles/360017896372-Preparing-an-Upgrade-to-Liferay-DXP-7-0 b) Yes, good. Personal opinion: Upgrades have become better. I had a lot more troubles with Liferay 6.x -> 6.y than with any 7.x -> 7.y upgrade. Please sign in to reply. Reply as... Cancel Max Max Max Max Max Max 3 Years Ago - Edited Spoke too soon. Seems like I'm already down the Liferay upgrade rabbit hole and I didn't know it. After the upgrade all my users have simply vanished from the user list. When I try and recreate a user who I know used to exist, I get an error saying the screen name is already taken, so I know there're in there somewhere. I'm getting errors in the logs like: /group/control_panel/manage?p_p_id=com_liferay_roles_admin_web_portlet_RolesAdminPortlet&p_p_lifecycle=0&p_p_state=normal&p_p_state_rcv=1&p_p_auth=jLefuZys is not allowed Does this mean my old admin user is no longer an admin user in the upgraded system? If this is the wrong forum to post this for CE questions, please will someone direct me to the correct forum. Thx, Max Please sign in to reply. Reply as... Cancel Jorge Ferrer Max Max Max 3 Years Ago Hey Max, It seems your index is not complete. You should be able to solve this by going to Control Panel > Configuration > Search and do a reindex Please sign in to reply. Reply as... Cancel Max Max Max Jorge Ferrer 3 Years Ago - Edited Hi Jorge. Thanks, this did the trick for the missing Users. I have an additional problem. I have images embedded in content pages. The images show up correctly in the page when viewed, but only as a little gray rectangle when in the editor. The name of the image seems correct, but it doesn't display at all in the editor. Any ideas why? Please sign in to reply. Reply as... Cancel Max Max Max Max Max Max 3 Years Ago - Edited Sorry, meant to also say that the images all appeared in the editor fine before the upgrade. Please sign in to reply. Reply as... Cancel Christoph Rabel Max Max Max 3 Years Ago - Edited Questions, especially complicated ones, are best asked in the forum: https://liferay.dev/forums Only people who read the blog or have answered previously to the blog post here, will see here. It is also more comfortable to answer there and faster, since posts there aren't reviewed. Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Thank you for listing these, Christoph. These steps and more information are included in the Upgrade Overview: https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay-dxp/upgrade-basics/upgrade-overview.html Please sign in to reply. Reply as... Cancel Christoph Rabel Jim Hinkey 3 Years Ago - Edited Ok, where does it explain that the content of the data folder has to be copied to the new instance? The section in "Using the Database Upgrade Tool" makes some assumptions that I are almost never true. -- cp /old-version/liferay-home/ /new-version/liferay-home/ cd /new-version/liferay-home/tools/portal-tools-db-upgrade-client db_upgrade.sh -j "-Dfile.encoding=UTF-8 -Duser.timezone=GMT -Xmx2048m" -l "output.log" -- Apart from the obviously missing "-r" parameter, an average user would here copy the old liferay folder (containing the old binaries and everything) and execute the db upgrade client of the old version. Maybe wondering why he was doing that. This text obviously assumes that Liferay Home is "elsewhere", and not equal to the unzipped Liferay folder. Nice idea, but I have never ever seen a CE installation where Liferay home is set manually to an external folder. If this is documented somewhere, fine. But still, nobody does that and so, that upgrade description won't work. Please sign in to reply. Reply as... Cancel Olaf Kock Christoph Rabel 3 Years Ago > where does it explain that the content of the data folder has to be copied to the new instance? It says, in the warning in the beginning: "Testing the upgrade process on backup copies is advised." Instead of "copying random data from left to right", I'd personally rather restore a backup on completely unrelated hardware, without any connection to production servers. Then assert that my backup is worth it's money by assuring that it's an exact copy of my production environment. Only then start upgrade work. Upon any problem: Rinse/Repeat. It's sooo relaxing to have proof that a backup actually can be used to reliably restore a system Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 3 Years Ago - Edited You still need to know what you have to change in your restored backup to upgrade it, so you need to know which steps are necessary and which files are relevant to the upgrade. The described upgrade steps are simply not correct. Please sign in to reply. Reply as... Cancel Olaf Kock Christoph Rabel 3 Years Ago On the one hand: Yes. On the other hand: You hopefully have figured out what to back up (and how to restore) loooooong before you ever attempt an upgrade. IMHO the steps can be simplified by "restore your backup to a completely new system - just the same way as you've tested before for cases when your main server disappears. Then use this restored system for further upgrade operations." That's a universal way to phrase the instructions. Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 3 Years Ago - Edited Well. Not really. I have seen several companies, where the backup strategy is: "We take snapshots of the VM ..." Also, if you backup the whole Liferay folder and the database, it will work too. So. Now what? Anyway, this is nitpicking. The upgrade guide should be like a cooking recipe and/or a checklist. Unzip new package. Copy these folders. Copy portal-*.properties Check portal-*.properties and update liferay.home Check ... Did you update any files manually? Please check especially server.xml, setenv.sh, files in osgi/configuration folder, ... Hint: Unpack the file with the old Liferay version and use a compare tool. and so on ... I know what to do because I did it countless times. But for people, who do this the first time, it should be cover as many bases as possible. Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Hi Christoph, We're fixing the upgrade steps and making them clearer. Regarding the "-r" parameter you're mentioning for db_upgrade.sh, I'm not familiar with it (it doesn't come up in --help) and will ask about it. Thank you for your input. Jim Please sign in to reply. Reply as... Cancel Christoph Rabel Jim Hinkey 3 Years Ago - Edited -r for cp (Linux shell copy), not db_upgrade. -r is necessary for directories. "cp /old-version/liferay-home/ /new-version/liferay-home/" --> Error Things like that make it perfectly clear for me that nobody has ever tested these steps because the first line fails always without exception. I think the upgrade steps should first explain, what each folder* does. If something like that doesn't exist already, it would be really helpful so that people understand what is tomcat, what is configuration, what is data, what is temporary(and can be deleted). * Some files should be explained too. Please sign in to reply. Reply as... Cancel
Max Max Max Christoph Rabel 3 Years Ago - Edited Hi Christoph, Thank you for these instructions, very helpful. I followed them with the following exceptions and got the upgrade to work: When copying the data/* directory a) I copied only the document_library dir because when I copied the elasticsearch dir as well I got exceptions thrown during the db_upgrade.sh process, as well 100's of framework exceptions during liferay startup. b) I also first deleted the content of the new installations /data/document_library dir. I had a few issues with portal-*.properties files, I only copied the root portal-setup-wizard.properties file across and also edited the file to change the location of the home dir for the app server. New install seems to be running fine now, so thank you very much for your help. Max Please sign in to reply. Reply as... Cancel Christoph Rabel Max Max Max 3 Years Ago - Edited All fine. a) I usually use an external ES server, it's better for performance and management reasons. Only the document_library folder is needed. Note: It is also recommended to disable the indexer for the upgrade. See: https://help.liferay.com/hc/en-us/articles/360017896372-Preparing-an-Upgrade-to-Liferay-DXP-7-0 b) Yes, good. Personal opinion: Upgrades have become better. I had a lot more troubles with Liferay 6.x -> 6.y than with any 7.x -> 7.y upgrade. Please sign in to reply. Reply as... Cancel Max Max Max Max Max Max 3 Years Ago - Edited Spoke too soon. Seems like I'm already down the Liferay upgrade rabbit hole and I didn't know it. After the upgrade all my users have simply vanished from the user list. When I try and recreate a user who I know used to exist, I get an error saying the screen name is already taken, so I know there're in there somewhere. I'm getting errors in the logs like: /group/control_panel/manage?p_p_id=com_liferay_roles_admin_web_portlet_RolesAdminPortlet&p_p_lifecycle=0&p_p_state=normal&p_p_state_rcv=1&p_p_auth=jLefuZys is not allowed Does this mean my old admin user is no longer an admin user in the upgraded system? If this is the wrong forum to post this for CE questions, please will someone direct me to the correct forum. Thx, Max Please sign in to reply. Reply as... Cancel Jorge Ferrer Max Max Max 3 Years Ago Hey Max, It seems your index is not complete. You should be able to solve this by going to Control Panel > Configuration > Search and do a reindex Please sign in to reply. Reply as... Cancel Max Max Max Jorge Ferrer 3 Years Ago - Edited Hi Jorge. Thanks, this did the trick for the missing Users. I have an additional problem. I have images embedded in content pages. The images show up correctly in the page when viewed, but only as a little gray rectangle when in the editor. The name of the image seems correct, but it doesn't display at all in the editor. Any ideas why? Please sign in to reply. Reply as... Cancel Max Max Max Max Max Max 3 Years Ago - Edited Sorry, meant to also say that the images all appeared in the editor fine before the upgrade. Please sign in to reply. Reply as... Cancel Christoph Rabel Max Max Max 3 Years Ago - Edited Questions, especially complicated ones, are best asked in the forum: https://liferay.dev/forums Only people who read the blog or have answered previously to the blog post here, will see here. It is also more comfortable to answer there and faster, since posts there aren't reviewed. Please sign in to reply. Reply as... Cancel
Christoph Rabel Max Max Max 3 Years Ago - Edited All fine. a) I usually use an external ES server, it's better for performance and management reasons. Only the document_library folder is needed. Note: It is also recommended to disable the indexer for the upgrade. See: https://help.liferay.com/hc/en-us/articles/360017896372-Preparing-an-Upgrade-to-Liferay-DXP-7-0 b) Yes, good. Personal opinion: Upgrades have become better. I had a lot more troubles with Liferay 6.x -> 6.y than with any 7.x -> 7.y upgrade. Please sign in to reply. Reply as... Cancel
Max Max Max Max Max Max 3 Years Ago - Edited Spoke too soon. Seems like I'm already down the Liferay upgrade rabbit hole and I didn't know it. After the upgrade all my users have simply vanished from the user list. When I try and recreate a user who I know used to exist, I get an error saying the screen name is already taken, so I know there're in there somewhere. I'm getting errors in the logs like: /group/control_panel/manage?p_p_id=com_liferay_roles_admin_web_portlet_RolesAdminPortlet&p_p_lifecycle=0&p_p_state=normal&p_p_state_rcv=1&p_p_auth=jLefuZys is not allowed Does this mean my old admin user is no longer an admin user in the upgraded system? If this is the wrong forum to post this for CE questions, please will someone direct me to the correct forum. Thx, Max Please sign in to reply. Reply as... Cancel Jorge Ferrer Max Max Max 3 Years Ago Hey Max, It seems your index is not complete. You should be able to solve this by going to Control Panel > Configuration > Search and do a reindex Please sign in to reply. Reply as... Cancel Max Max Max Jorge Ferrer 3 Years Ago - Edited Hi Jorge. Thanks, this did the trick for the missing Users. I have an additional problem. I have images embedded in content pages. The images show up correctly in the page when viewed, but only as a little gray rectangle when in the editor. The name of the image seems correct, but it doesn't display at all in the editor. Any ideas why? Please sign in to reply. Reply as... Cancel Max Max Max Max Max Max 3 Years Ago - Edited Sorry, meant to also say that the images all appeared in the editor fine before the upgrade. Please sign in to reply. Reply as... Cancel Christoph Rabel Max Max Max 3 Years Ago - Edited Questions, especially complicated ones, are best asked in the forum: https://liferay.dev/forums Only people who read the blog or have answered previously to the blog post here, will see here. It is also more comfortable to answer there and faster, since posts there aren't reviewed. Please sign in to reply. Reply as... Cancel
Jorge Ferrer Max Max Max 3 Years Ago Hey Max, It seems your index is not complete. You should be able to solve this by going to Control Panel > Configuration > Search and do a reindex Please sign in to reply. Reply as... Cancel Max Max Max Jorge Ferrer 3 Years Ago - Edited Hi Jorge. Thanks, this did the trick for the missing Users. I have an additional problem. I have images embedded in content pages. The images show up correctly in the page when viewed, but only as a little gray rectangle when in the editor. The name of the image seems correct, but it doesn't display at all in the editor. Any ideas why? Please sign in to reply. Reply as... Cancel Max Max Max Max Max Max 3 Years Ago - Edited Sorry, meant to also say that the images all appeared in the editor fine before the upgrade. Please sign in to reply. Reply as... Cancel
Max Max Max Jorge Ferrer 3 Years Ago - Edited Hi Jorge. Thanks, this did the trick for the missing Users. I have an additional problem. I have images embedded in content pages. The images show up correctly in the page when viewed, but only as a little gray rectangle when in the editor. The name of the image seems correct, but it doesn't display at all in the editor. Any ideas why? Please sign in to reply. Reply as... Cancel Max Max Max Max Max Max 3 Years Ago - Edited Sorry, meant to also say that the images all appeared in the editor fine before the upgrade. Please sign in to reply. Reply as... Cancel
Max Max Max Max Max Max 3 Years Ago - Edited Sorry, meant to also say that the images all appeared in the editor fine before the upgrade. Please sign in to reply. Reply as... Cancel
Christoph Rabel Max Max Max 3 Years Ago - Edited Questions, especially complicated ones, are best asked in the forum: https://liferay.dev/forums Only people who read the blog or have answered previously to the blog post here, will see here. It is also more comfortable to answer there and faster, since posts there aren't reviewed. Please sign in to reply. Reply as... Cancel
Jim Hinkey Christoph Rabel 3 Years Ago Thank you for listing these, Christoph. These steps and more information are included in the Upgrade Overview: https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay-dxp/upgrade-basics/upgrade-overview.html Please sign in to reply. Reply as... Cancel Christoph Rabel Jim Hinkey 3 Years Ago - Edited Ok, where does it explain that the content of the data folder has to be copied to the new instance? The section in "Using the Database Upgrade Tool" makes some assumptions that I are almost never true. -- cp /old-version/liferay-home/ /new-version/liferay-home/ cd /new-version/liferay-home/tools/portal-tools-db-upgrade-client db_upgrade.sh -j "-Dfile.encoding=UTF-8 -Duser.timezone=GMT -Xmx2048m" -l "output.log" -- Apart from the obviously missing "-r" parameter, an average user would here copy the old liferay folder (containing the old binaries and everything) and execute the db upgrade client of the old version. Maybe wondering why he was doing that. This text obviously assumes that Liferay Home is "elsewhere", and not equal to the unzipped Liferay folder. Nice idea, but I have never ever seen a CE installation where Liferay home is set manually to an external folder. If this is documented somewhere, fine. But still, nobody does that and so, that upgrade description won't work. Please sign in to reply. Reply as... Cancel Olaf Kock Christoph Rabel 3 Years Ago > where does it explain that the content of the data folder has to be copied to the new instance? It says, in the warning in the beginning: "Testing the upgrade process on backup copies is advised." Instead of "copying random data from left to right", I'd personally rather restore a backup on completely unrelated hardware, without any connection to production servers. Then assert that my backup is worth it's money by assuring that it's an exact copy of my production environment. Only then start upgrade work. Upon any problem: Rinse/Repeat. It's sooo relaxing to have proof that a backup actually can be used to reliably restore a system Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 3 Years Ago - Edited You still need to know what you have to change in your restored backup to upgrade it, so you need to know which steps are necessary and which files are relevant to the upgrade. The described upgrade steps are simply not correct. Please sign in to reply. Reply as... Cancel Olaf Kock Christoph Rabel 3 Years Ago On the one hand: Yes. On the other hand: You hopefully have figured out what to back up (and how to restore) loooooong before you ever attempt an upgrade. IMHO the steps can be simplified by "restore your backup to a completely new system - just the same way as you've tested before for cases when your main server disappears. Then use this restored system for further upgrade operations." That's a universal way to phrase the instructions. Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 3 Years Ago - Edited Well. Not really. I have seen several companies, where the backup strategy is: "We take snapshots of the VM ..." Also, if you backup the whole Liferay folder and the database, it will work too. So. Now what? Anyway, this is nitpicking. The upgrade guide should be like a cooking recipe and/or a checklist. Unzip new package. Copy these folders. Copy portal-*.properties Check portal-*.properties and update liferay.home Check ... Did you update any files manually? Please check especially server.xml, setenv.sh, files in osgi/configuration folder, ... Hint: Unpack the file with the old Liferay version and use a compare tool. and so on ... I know what to do because I did it countless times. But for people, who do this the first time, it should be cover as many bases as possible. Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Hi Christoph, We're fixing the upgrade steps and making them clearer. Regarding the "-r" parameter you're mentioning for db_upgrade.sh, I'm not familiar with it (it doesn't come up in --help) and will ask about it. Thank you for your input. Jim Please sign in to reply. Reply as... Cancel Christoph Rabel Jim Hinkey 3 Years Ago - Edited -r for cp (Linux shell copy), not db_upgrade. -r is necessary for directories. "cp /old-version/liferay-home/ /new-version/liferay-home/" --> Error Things like that make it perfectly clear for me that nobody has ever tested these steps because the first line fails always without exception. I think the upgrade steps should first explain, what each folder* does. If something like that doesn't exist already, it would be really helpful so that people understand what is tomcat, what is configuration, what is data, what is temporary(and can be deleted). * Some files should be explained too. Please sign in to reply. Reply as... Cancel
Christoph Rabel Jim Hinkey 3 Years Ago - Edited Ok, where does it explain that the content of the data folder has to be copied to the new instance? The section in "Using the Database Upgrade Tool" makes some assumptions that I are almost never true. -- cp /old-version/liferay-home/ /new-version/liferay-home/ cd /new-version/liferay-home/tools/portal-tools-db-upgrade-client db_upgrade.sh -j "-Dfile.encoding=UTF-8 -Duser.timezone=GMT -Xmx2048m" -l "output.log" -- Apart from the obviously missing "-r" parameter, an average user would here copy the old liferay folder (containing the old binaries and everything) and execute the db upgrade client of the old version. Maybe wondering why he was doing that. This text obviously assumes that Liferay Home is "elsewhere", and not equal to the unzipped Liferay folder. Nice idea, but I have never ever seen a CE installation where Liferay home is set manually to an external folder. If this is documented somewhere, fine. But still, nobody does that and so, that upgrade description won't work. Please sign in to reply. Reply as... Cancel Olaf Kock Christoph Rabel 3 Years Ago > where does it explain that the content of the data folder has to be copied to the new instance? It says, in the warning in the beginning: "Testing the upgrade process on backup copies is advised." Instead of "copying random data from left to right", I'd personally rather restore a backup on completely unrelated hardware, without any connection to production servers. Then assert that my backup is worth it's money by assuring that it's an exact copy of my production environment. Only then start upgrade work. Upon any problem: Rinse/Repeat. It's sooo relaxing to have proof that a backup actually can be used to reliably restore a system Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 3 Years Ago - Edited You still need to know what you have to change in your restored backup to upgrade it, so you need to know which steps are necessary and which files are relevant to the upgrade. The described upgrade steps are simply not correct. Please sign in to reply. Reply as... Cancel Olaf Kock Christoph Rabel 3 Years Ago On the one hand: Yes. On the other hand: You hopefully have figured out what to back up (and how to restore) loooooong before you ever attempt an upgrade. IMHO the steps can be simplified by "restore your backup to a completely new system - just the same way as you've tested before for cases when your main server disappears. Then use this restored system for further upgrade operations." That's a universal way to phrase the instructions. Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 3 Years Ago - Edited Well. Not really. I have seen several companies, where the backup strategy is: "We take snapshots of the VM ..." Also, if you backup the whole Liferay folder and the database, it will work too. So. Now what? Anyway, this is nitpicking. The upgrade guide should be like a cooking recipe and/or a checklist. Unzip new package. Copy these folders. Copy portal-*.properties Check portal-*.properties and update liferay.home Check ... Did you update any files manually? Please check especially server.xml, setenv.sh, files in osgi/configuration folder, ... Hint: Unpack the file with the old Liferay version and use a compare tool. and so on ... I know what to do because I did it countless times. But for people, who do this the first time, it should be cover as many bases as possible. Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Hi Christoph, We're fixing the upgrade steps and making them clearer. Regarding the "-r" parameter you're mentioning for db_upgrade.sh, I'm not familiar with it (it doesn't come up in --help) and will ask about it. Thank you for your input. Jim Please sign in to reply. Reply as... Cancel Christoph Rabel Jim Hinkey 3 Years Ago - Edited -r for cp (Linux shell copy), not db_upgrade. -r is necessary for directories. "cp /old-version/liferay-home/ /new-version/liferay-home/" --> Error Things like that make it perfectly clear for me that nobody has ever tested these steps because the first line fails always without exception. I think the upgrade steps should first explain, what each folder* does. If something like that doesn't exist already, it would be really helpful so that people understand what is tomcat, what is configuration, what is data, what is temporary(and can be deleted). * Some files should be explained too. Please sign in to reply. Reply as... Cancel
Olaf Kock Christoph Rabel 3 Years Ago > where does it explain that the content of the data folder has to be copied to the new instance? It says, in the warning in the beginning: "Testing the upgrade process on backup copies is advised." Instead of "copying random data from left to right", I'd personally rather restore a backup on completely unrelated hardware, without any connection to production servers. Then assert that my backup is worth it's money by assuring that it's an exact copy of my production environment. Only then start upgrade work. Upon any problem: Rinse/Repeat. It's sooo relaxing to have proof that a backup actually can be used to reliably restore a system Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 3 Years Ago - Edited You still need to know what you have to change in your restored backup to upgrade it, so you need to know which steps are necessary and which files are relevant to the upgrade. The described upgrade steps are simply not correct. Please sign in to reply. Reply as... Cancel Olaf Kock Christoph Rabel 3 Years Ago On the one hand: Yes. On the other hand: You hopefully have figured out what to back up (and how to restore) loooooong before you ever attempt an upgrade. IMHO the steps can be simplified by "restore your backup to a completely new system - just the same way as you've tested before for cases when your main server disappears. Then use this restored system for further upgrade operations." That's a universal way to phrase the instructions. Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 3 Years Ago - Edited Well. Not really. I have seen several companies, where the backup strategy is: "We take snapshots of the VM ..." Also, if you backup the whole Liferay folder and the database, it will work too. So. Now what? Anyway, this is nitpicking. The upgrade guide should be like a cooking recipe and/or a checklist. Unzip new package. Copy these folders. Copy portal-*.properties Check portal-*.properties and update liferay.home Check ... Did you update any files manually? Please check especially server.xml, setenv.sh, files in osgi/configuration folder, ... Hint: Unpack the file with the old Liferay version and use a compare tool. and so on ... I know what to do because I did it countless times. But for people, who do this the first time, it should be cover as many bases as possible. Please sign in to reply. Reply as... Cancel
Christoph Rabel Olaf Kock 3 Years Ago - Edited You still need to know what you have to change in your restored backup to upgrade it, so you need to know which steps are necessary and which files are relevant to the upgrade. The described upgrade steps are simply not correct. Please sign in to reply. Reply as... Cancel Olaf Kock Christoph Rabel 3 Years Ago On the one hand: Yes. On the other hand: You hopefully have figured out what to back up (and how to restore) loooooong before you ever attempt an upgrade. IMHO the steps can be simplified by "restore your backup to a completely new system - just the same way as you've tested before for cases when your main server disappears. Then use this restored system for further upgrade operations." That's a universal way to phrase the instructions. Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 3 Years Ago - Edited Well. Not really. I have seen several companies, where the backup strategy is: "We take snapshots of the VM ..." Also, if you backup the whole Liferay folder and the database, it will work too. So. Now what? Anyway, this is nitpicking. The upgrade guide should be like a cooking recipe and/or a checklist. Unzip new package. Copy these folders. Copy portal-*.properties Check portal-*.properties and update liferay.home Check ... Did you update any files manually? Please check especially server.xml, setenv.sh, files in osgi/configuration folder, ... Hint: Unpack the file with the old Liferay version and use a compare tool. and so on ... I know what to do because I did it countless times. But for people, who do this the first time, it should be cover as many bases as possible. Please sign in to reply. Reply as... Cancel
Olaf Kock Christoph Rabel 3 Years Ago On the one hand: Yes. On the other hand: You hopefully have figured out what to back up (and how to restore) loooooong before you ever attempt an upgrade. IMHO the steps can be simplified by "restore your backup to a completely new system - just the same way as you've tested before for cases when your main server disappears. Then use this restored system for further upgrade operations." That's a universal way to phrase the instructions. Please sign in to reply. Reply as... Cancel Christoph Rabel Olaf Kock 3 Years Ago - Edited Well. Not really. I have seen several companies, where the backup strategy is: "We take snapshots of the VM ..." Also, if you backup the whole Liferay folder and the database, it will work too. So. Now what? Anyway, this is nitpicking. The upgrade guide should be like a cooking recipe and/or a checklist. Unzip new package. Copy these folders. Copy portal-*.properties Check portal-*.properties and update liferay.home Check ... Did you update any files manually? Please check especially server.xml, setenv.sh, files in osgi/configuration folder, ... Hint: Unpack the file with the old Liferay version and use a compare tool. and so on ... I know what to do because I did it countless times. But for people, who do this the first time, it should be cover as many bases as possible. Please sign in to reply. Reply as... Cancel
Christoph Rabel Olaf Kock 3 Years Ago - Edited Well. Not really. I have seen several companies, where the backup strategy is: "We take snapshots of the VM ..." Also, if you backup the whole Liferay folder and the database, it will work too. So. Now what? Anyway, this is nitpicking. The upgrade guide should be like a cooking recipe and/or a checklist. Unzip new package. Copy these folders. Copy portal-*.properties Check portal-*.properties and update liferay.home Check ... Did you update any files manually? Please check especially server.xml, setenv.sh, files in osgi/configuration folder, ... Hint: Unpack the file with the old Liferay version and use a compare tool. and so on ... I know what to do because I did it countless times. But for people, who do this the first time, it should be cover as many bases as possible. Please sign in to reply. Reply as... Cancel
Jim Hinkey Christoph Rabel 3 Years Ago Hi Christoph, We're fixing the upgrade steps and making them clearer. Regarding the "-r" parameter you're mentioning for db_upgrade.sh, I'm not familiar with it (it doesn't come up in --help) and will ask about it. Thank you for your input. Jim Please sign in to reply. Reply as... Cancel Christoph Rabel Jim Hinkey 3 Years Ago - Edited -r for cp (Linux shell copy), not db_upgrade. -r is necessary for directories. "cp /old-version/liferay-home/ /new-version/liferay-home/" --> Error Things like that make it perfectly clear for me that nobody has ever tested these steps because the first line fails always without exception. I think the upgrade steps should first explain, what each folder* does. If something like that doesn't exist already, it would be really helpful so that people understand what is tomcat, what is configuration, what is data, what is temporary(and can be deleted). * Some files should be explained too. Please sign in to reply. Reply as... Cancel
Christoph Rabel Jim Hinkey 3 Years Ago - Edited -r for cp (Linux shell copy), not db_upgrade. -r is necessary for directories. "cp /old-version/liferay-home/ /new-version/liferay-home/" --> Error Things like that make it perfectly clear for me that nobody has ever tested these steps because the first line fails always without exception. I think the upgrade steps should first explain, what each folder* does. If something like that doesn't exist already, it would be really helpful so that people understand what is tomcat, what is configuration, what is data, what is temporary(and can be deleted). * Some files should be explained too. Please sign in to reply. Reply as... Cancel
Krzysztof Gołębiowski Max Max Max 3 Years Ago - Edited Hi Max, the upgrade process is quite simple in general, most of the other things you mentioned (document library, properties) are just being copied from old Liferay to new "as they are". There might be some problems with 7.3 as it is still unstable and hasn't been officially released yet, but usually, it's quite straightforward. You could write a post on Liferay forums if you have some issues, I think it's a better place to get help than here. Please sign in to reply. Reply as... Cancel
Jorge Ferrer Max Max Max 3 Years Ago Hey Max Max Max, I'm sorry to hear that you have had so many problems upgrading between rolling releases. Our promise is that those upgrades should be very easy in a wide majority of cases (the only exceptions could be when there are heavy customization or db inconsistencies). In order to improve, I'd like to know more about your problems to find out if the root cause is in lack or inaccurate documentation or actual problems in the automated upgrade processes. Did the steps mentioned by Christoph help? Are you able to successfully upgrade following them or do you find still run into problems? Please sign in to reply. Reply as... Cancel Max Max Max Jorge Ferrer 3 Years Ago - Edited Hi Jorge, I can't remember the details of my past upgrade problems but I often remember db errors appearing everywhere. The main problem with this upgrade was to find the set of instructions that Christoph was so kind as to type up. If these instructions are elsewhere in the Liferay documentation, then it would be good to link tho this in the release notes or in this announcement for us plebs. Max Please sign in to reply. Reply as... Cancel Jim Hinkey Max Max Max 3 Years Ago Hi Max, Updating from one 7.3 Liferay Portal CE GA to another GA is demonstrated in the following article: Updating Liferay Portal CE - https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/maintaining-a-liferay-dxp-installation/patching-liferay/updating-liferay-portal-ce.html I'm sorry you didn't find it. We're going to add the article to the upgrade section so that it can be found there too. My apologies. Note, if you do need to upgrade from an earlier version (e.g., from 7.2 Liferay Portal CE) you can run the upgrade using a Docker image. That is, you can continue using an on-premises installation but simply use a Docker image to upgrade your database. The CE Docker images are mentioned in the second paragraph in the article Upgrading Via Docker - https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay-dxp/upgrade-basics/upgrading-via-docker.html I hope that makes your upgrade a quick success! Jim Please sign in to reply. Reply as... Cancel Max Max Max Jim Hinkey 3 Years Ago - Edited Hi Jim, Thanks for pointing me to the upgrade page. The upgrade instructions on that page are very different to the instructions given by other to me here. There are also ambiguities if you can please clear up for me before I attempt this upgrade again. - There is no mention of any copying of the data directory across. - There is no mention of using the db_upgrade.sh script. Using this script sounds MUCH easier than a) learning how to use the gogo shell and b) going through 5 different gogo steps for each module. - Step 5: Clean up DXP cache. - I assume this is on the new installation? - Step 6: Start the application server again. - According to the instructions I have not started the new server yet, so do I start the old server 'again'. Why? - I assume again I run the gogo shell here against the new server and no the old. @Jorge: I am certainly not looking forward to going through all this every time I upgrade . This is exactly what scares me about every Liferay upgrade I have to do. I just read a post that there is some error in the 7.3.2 upgrade script where some db column is not properly upgraded and users cannot be deleted anymore. Any small DB error seems to propagate through the upgrades and after two upgrades the DB breaks and I end up having to throw it away and start from scratch. My above mentioned upgrade attempt that resulted in my users disappearing and permissions broken leaves me with the permanent niggle in my back of my mind that my DB is corrupted and there are other things that will just break down the line and I will sit for days on forums trying to figure out what. That is why I often just cave in an install from scratch and manually copy stuff over because that crazily feels easier to me than the potential future issues. But that is not a real solution long term. Please sign in to reply. Reply as... Cancel Christoph Rabel Jim Hinkey 3 Years Ago - Edited Where does it explain that the document_library folder has to be copied? Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Hi Christoph, We're still in the process of fixing and improving the documentation for upgrading a Portal CE rolling release. You can follow progress at https://issues.liferay.com/browse/LRDOCS-8053. The steps include copying the data folder, which includes the document library if that's where you have configured you've configured your File Store to be there. Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Christoph, Max, The upgrade documentation has been improved based on your questions and suggestions. Here's a summary of the changes: Upgrade Overview https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/upgrade-overview.html - The overview is always the best place to start when considering an upgrade for DXP or CE. It explains what areas to consider and which database upgrade approach(es) to consider. The articles that follow center on database upgrade, but list steps for all parts of the upgrade (including migrating data/ folder contents and configuration files) and link to detail articles where needed. Backing up your existing installation and using a backup installation/db copy is essential--we warn about this in the overview and articles on upgrading using Docker and the Database Upgrade Tool. Upgrading Via Docker https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/upgrading-via-docker.html - Is for non-critical CE upgrades, especially upgrading from one rolling release to another (e.g., 7.3.0 - 7.3.x). Note, your new installation need not be a Docker image, you're just using the Docker image to upgrade your database. Using the Database Upgrade Tool https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/using-the-database-upgrade-tool.html - Is for any Liferay edition (DXP or CE), but is a must for DXP, critical servers, and clustered environments. It allows you to dive deeper into database upgrades, when things don't work in one shot (e.g., Upgrading via Docker). I hope you find the improvements helpful and easy to follow. We're open to more suggestions. And thank you for your patience. Jim Please sign in to reply. Reply as... Cancel
Max Max Max Jorge Ferrer 3 Years Ago - Edited Hi Jorge, I can't remember the details of my past upgrade problems but I often remember db errors appearing everywhere. The main problem with this upgrade was to find the set of instructions that Christoph was so kind as to type up. If these instructions are elsewhere in the Liferay documentation, then it would be good to link tho this in the release notes or in this announcement for us plebs. Max Please sign in to reply. Reply as... Cancel Jim Hinkey Max Max Max 3 Years Ago Hi Max, Updating from one 7.3 Liferay Portal CE GA to another GA is demonstrated in the following article: Updating Liferay Portal CE - https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/maintaining-a-liferay-dxp-installation/patching-liferay/updating-liferay-portal-ce.html I'm sorry you didn't find it. We're going to add the article to the upgrade section so that it can be found there too. My apologies. Note, if you do need to upgrade from an earlier version (e.g., from 7.2 Liferay Portal CE) you can run the upgrade using a Docker image. That is, you can continue using an on-premises installation but simply use a Docker image to upgrade your database. The CE Docker images are mentioned in the second paragraph in the article Upgrading Via Docker - https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay-dxp/upgrade-basics/upgrading-via-docker.html I hope that makes your upgrade a quick success! Jim Please sign in to reply. Reply as... Cancel Max Max Max Jim Hinkey 3 Years Ago - Edited Hi Jim, Thanks for pointing me to the upgrade page. The upgrade instructions on that page are very different to the instructions given by other to me here. There are also ambiguities if you can please clear up for me before I attempt this upgrade again. - There is no mention of any copying of the data directory across. - There is no mention of using the db_upgrade.sh script. Using this script sounds MUCH easier than a) learning how to use the gogo shell and b) going through 5 different gogo steps for each module. - Step 5: Clean up DXP cache. - I assume this is on the new installation? - Step 6: Start the application server again. - According to the instructions I have not started the new server yet, so do I start the old server 'again'. Why? - I assume again I run the gogo shell here against the new server and no the old. @Jorge: I am certainly not looking forward to going through all this every time I upgrade . This is exactly what scares me about every Liferay upgrade I have to do. I just read a post that there is some error in the 7.3.2 upgrade script where some db column is not properly upgraded and users cannot be deleted anymore. Any small DB error seems to propagate through the upgrades and after two upgrades the DB breaks and I end up having to throw it away and start from scratch. My above mentioned upgrade attempt that resulted in my users disappearing and permissions broken leaves me with the permanent niggle in my back of my mind that my DB is corrupted and there are other things that will just break down the line and I will sit for days on forums trying to figure out what. That is why I often just cave in an install from scratch and manually copy stuff over because that crazily feels easier to me than the potential future issues. But that is not a real solution long term. Please sign in to reply. Reply as... Cancel Christoph Rabel Jim Hinkey 3 Years Ago - Edited Where does it explain that the document_library folder has to be copied? Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Hi Christoph, We're still in the process of fixing and improving the documentation for upgrading a Portal CE rolling release. You can follow progress at https://issues.liferay.com/browse/LRDOCS-8053. The steps include copying the data folder, which includes the document library if that's where you have configured you've configured your File Store to be there. Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Christoph, Max, The upgrade documentation has been improved based on your questions and suggestions. Here's a summary of the changes: Upgrade Overview https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/upgrade-overview.html - The overview is always the best place to start when considering an upgrade for DXP or CE. It explains what areas to consider and which database upgrade approach(es) to consider. The articles that follow center on database upgrade, but list steps for all parts of the upgrade (including migrating data/ folder contents and configuration files) and link to detail articles where needed. Backing up your existing installation and using a backup installation/db copy is essential--we warn about this in the overview and articles on upgrading using Docker and the Database Upgrade Tool. Upgrading Via Docker https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/upgrading-via-docker.html - Is for non-critical CE upgrades, especially upgrading from one rolling release to another (e.g., 7.3.0 - 7.3.x). Note, your new installation need not be a Docker image, you're just using the Docker image to upgrade your database. Using the Database Upgrade Tool https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/using-the-database-upgrade-tool.html - Is for any Liferay edition (DXP or CE), but is a must for DXP, critical servers, and clustered environments. It allows you to dive deeper into database upgrades, when things don't work in one shot (e.g., Upgrading via Docker). I hope you find the improvements helpful and easy to follow. We're open to more suggestions. And thank you for your patience. Jim Please sign in to reply. Reply as... Cancel
Jim Hinkey Max Max Max 3 Years Ago Hi Max, Updating from one 7.3 Liferay Portal CE GA to another GA is demonstrated in the following article: Updating Liferay Portal CE - https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/maintaining-a-liferay-dxp-installation/patching-liferay/updating-liferay-portal-ce.html I'm sorry you didn't find it. We're going to add the article to the upgrade section so that it can be found there too. My apologies. Note, if you do need to upgrade from an earlier version (e.g., from 7.2 Liferay Portal CE) you can run the upgrade using a Docker image. That is, you can continue using an on-premises installation but simply use a Docker image to upgrade your database. The CE Docker images are mentioned in the second paragraph in the article Upgrading Via Docker - https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay-dxp/upgrade-basics/upgrading-via-docker.html I hope that makes your upgrade a quick success! Jim Please sign in to reply. Reply as... Cancel Max Max Max Jim Hinkey 3 Years Ago - Edited Hi Jim, Thanks for pointing me to the upgrade page. The upgrade instructions on that page are very different to the instructions given by other to me here. There are also ambiguities if you can please clear up for me before I attempt this upgrade again. - There is no mention of any copying of the data directory across. - There is no mention of using the db_upgrade.sh script. Using this script sounds MUCH easier than a) learning how to use the gogo shell and b) going through 5 different gogo steps for each module. - Step 5: Clean up DXP cache. - I assume this is on the new installation? - Step 6: Start the application server again. - According to the instructions I have not started the new server yet, so do I start the old server 'again'. Why? - I assume again I run the gogo shell here against the new server and no the old. @Jorge: I am certainly not looking forward to going through all this every time I upgrade . This is exactly what scares me about every Liferay upgrade I have to do. I just read a post that there is some error in the 7.3.2 upgrade script where some db column is not properly upgraded and users cannot be deleted anymore. Any small DB error seems to propagate through the upgrades and after two upgrades the DB breaks and I end up having to throw it away and start from scratch. My above mentioned upgrade attempt that resulted in my users disappearing and permissions broken leaves me with the permanent niggle in my back of my mind that my DB is corrupted and there are other things that will just break down the line and I will sit for days on forums trying to figure out what. That is why I often just cave in an install from scratch and manually copy stuff over because that crazily feels easier to me than the potential future issues. But that is not a real solution long term. Please sign in to reply. Reply as... Cancel Christoph Rabel Jim Hinkey 3 Years Ago - Edited Where does it explain that the document_library folder has to be copied? Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Hi Christoph, We're still in the process of fixing and improving the documentation for upgrading a Portal CE rolling release. You can follow progress at https://issues.liferay.com/browse/LRDOCS-8053. The steps include copying the data folder, which includes the document library if that's where you have configured you've configured your File Store to be there. Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Christoph, Max, The upgrade documentation has been improved based on your questions and suggestions. Here's a summary of the changes: Upgrade Overview https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/upgrade-overview.html - The overview is always the best place to start when considering an upgrade for DXP or CE. It explains what areas to consider and which database upgrade approach(es) to consider. The articles that follow center on database upgrade, but list steps for all parts of the upgrade (including migrating data/ folder contents and configuration files) and link to detail articles where needed. Backing up your existing installation and using a backup installation/db copy is essential--we warn about this in the overview and articles on upgrading using Docker and the Database Upgrade Tool. Upgrading Via Docker https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/upgrading-via-docker.html - Is for non-critical CE upgrades, especially upgrading from one rolling release to another (e.g., 7.3.0 - 7.3.x). Note, your new installation need not be a Docker image, you're just using the Docker image to upgrade your database. Using the Database Upgrade Tool https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/using-the-database-upgrade-tool.html - Is for any Liferay edition (DXP or CE), but is a must for DXP, critical servers, and clustered environments. It allows you to dive deeper into database upgrades, when things don't work in one shot (e.g., Upgrading via Docker). I hope you find the improvements helpful and easy to follow. We're open to more suggestions. And thank you for your patience. Jim Please sign in to reply. Reply as... Cancel
Max Max Max Jim Hinkey 3 Years Ago - Edited Hi Jim, Thanks for pointing me to the upgrade page. The upgrade instructions on that page are very different to the instructions given by other to me here. There are also ambiguities if you can please clear up for me before I attempt this upgrade again. - There is no mention of any copying of the data directory across. - There is no mention of using the db_upgrade.sh script. Using this script sounds MUCH easier than a) learning how to use the gogo shell and b) going through 5 different gogo steps for each module. - Step 5: Clean up DXP cache. - I assume this is on the new installation? - Step 6: Start the application server again. - According to the instructions I have not started the new server yet, so do I start the old server 'again'. Why? - I assume again I run the gogo shell here against the new server and no the old. @Jorge: I am certainly not looking forward to going through all this every time I upgrade . This is exactly what scares me about every Liferay upgrade I have to do. I just read a post that there is some error in the 7.3.2 upgrade script where some db column is not properly upgraded and users cannot be deleted anymore. Any small DB error seems to propagate through the upgrades and after two upgrades the DB breaks and I end up having to throw it away and start from scratch. My above mentioned upgrade attempt that resulted in my users disappearing and permissions broken leaves me with the permanent niggle in my back of my mind that my DB is corrupted and there are other things that will just break down the line and I will sit for days on forums trying to figure out what. That is why I often just cave in an install from scratch and manually copy stuff over because that crazily feels easier to me than the potential future issues. But that is not a real solution long term. Please sign in to reply. Reply as... Cancel
Christoph Rabel Jim Hinkey 3 Years Ago - Edited Where does it explain that the document_library folder has to be copied? Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Hi Christoph, We're still in the process of fixing and improving the documentation for upgrading a Portal CE rolling release. You can follow progress at https://issues.liferay.com/browse/LRDOCS-8053. The steps include copying the data folder, which includes the document library if that's where you have configured you've configured your File Store to be there. Please sign in to reply. Reply as... Cancel Jim Hinkey Christoph Rabel 3 Years Ago Christoph, Max, The upgrade documentation has been improved based on your questions and suggestions. Here's a summary of the changes: Upgrade Overview https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/upgrade-overview.html - The overview is always the best place to start when considering an upgrade for DXP or CE. It explains what areas to consider and which database upgrade approach(es) to consider. The articles that follow center on database upgrade, but list steps for all parts of the upgrade (including migrating data/ folder contents and configuration files) and link to detail articles where needed. Backing up your existing installation and using a backup installation/db copy is essential--we warn about this in the overview and articles on upgrading using Docker and the Database Upgrade Tool. Upgrading Via Docker https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/upgrading-via-docker.html - Is for non-critical CE upgrades, especially upgrading from one rolling release to another (e.g., 7.3.0 - 7.3.x). Note, your new installation need not be a Docker image, you're just using the Docker image to upgrade your database. Using the Database Upgrade Tool https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/using-the-database-upgrade-tool.html - Is for any Liferay edition (DXP or CE), but is a must for DXP, critical servers, and clustered environments. It allows you to dive deeper into database upgrades, when things don't work in one shot (e.g., Upgrading via Docker). I hope you find the improvements helpful and easy to follow. We're open to more suggestions. And thank you for your patience. Jim Please sign in to reply. Reply as... Cancel
Jim Hinkey Christoph Rabel 3 Years Ago Hi Christoph, We're still in the process of fixing and improving the documentation for upgrading a Portal CE rolling release. You can follow progress at https://issues.liferay.com/browse/LRDOCS-8053. The steps include copying the data folder, which includes the document library if that's where you have configured you've configured your File Store to be there. Please sign in to reply. Reply as... Cancel
Jim Hinkey Christoph Rabel 3 Years Ago Christoph, Max, The upgrade documentation has been improved based on your questions and suggestions. Here's a summary of the changes: Upgrade Overview https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/upgrade-overview.html - The overview is always the best place to start when considering an upgrade for DXP or CE. It explains what areas to consider and which database upgrade approach(es) to consider. The articles that follow center on database upgrade, but list steps for all parts of the upgrade (including migrating data/ folder contents and configuration files) and link to detail articles where needed. Backing up your existing installation and using a backup installation/db copy is essential--we warn about this in the overview and articles on upgrading using Docker and the Database Upgrade Tool. Upgrading Via Docker https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/upgrading-via-docker.html - Is for non-critical CE upgrades, especially upgrading from one rolling release to another (e.g., 7.3.0 - 7.3.x). Note, your new installation need not be a Docker image, you're just using the Docker image to upgrade your database. Using the Database Upgrade Tool https://learn.liferay.com/dxp/7.x/en/installation-and-upgrades/upgrading-liferay/upgrade-basics/using-the-database-upgrade-tool.html - Is for any Liferay edition (DXP or CE), but is a must for DXP, critical servers, and clustered environments. It allows you to dive deeper into database upgrades, when things don't work in one shot (e.g., Upgrading via Docker). I hope you find the improvements helpful and easy to follow. We're open to more suggestions. And thank you for your patience. Jim Please sign in to reply. Reply as... Cancel