Installing a package on your site makes some obvious changes - like updating templates and creating content. It also makes some more subtle changes: some of the status icons on your site will be different and you may start to see new warning messages about package conflicts that you did not see before. This lesson will focus on the less obvious changes as well as provide tips on how you should manage content created or updated by a package.
On top of the normal status icon, some objects on your site may start displaying a new "package" icon. The "package" icon has 2 states - one which identifies that the object is from a particular package and is consistent with the definition of that object at the time that it was installed, and one which identifies that the object is from a particular package but has been modified from its definition in the package as of the time that it was installed.
Additionally, when you edit an object that is from a particular package - particularly if it has not been modified yet - you should notice a warning message about creating conflicts with the source package if you make edits. You will be prompted to confirm that you want to make any changes before you will be able to save these objects.
The easiest way to find all of the assets installed by the package is to go to the "Site Packages" dialog and clicking on the "Browse" button. You should see a list of all of the assets from your most recent installation of that package.
In order to avoid conflicts with future updates to packages, you should avoid making changes to assets installed from packages if possible. One of the simplest ways to do that is to read the package documentation. Many packages provide simple ways to customize the package without having to edit core files. Other times you may want to copy templates and other assets and modify your copies instead of the original. And sometimes you will decide that it is worth a few warnings and a potential conflict to simply go ahead and make the updates anyway. It is up to you.
Please fill out the form below with your feedback or any questions you may have after working through the "Managing package assets after installation" lesson.