Try our conversational search powered by Generative AI!

Jeff Wallace
Nov 12, 2009
  7042
(5 votes)

EPiServer Composer 3.2.x Installation and Configuration Instructions – Including the Extra Details You May Want to Know

Some good documentation on initial Composer installation steps already exists.  I’d rather not re-invent the wheel here but instead will point you to that information and expand upon it with additional details to help you get started.

 

Initial Installation

1) Check the EPiServer Version Relations matrix to ensure you are installing the correct Composer version which will work with your CMS version:

http://world.episerver.com/Documentation/Categories/Version-Relations/EPiServer-CMS-5-Relations/

Note, if you are installing with CMS 5.2 R2 you may notice that the Composer version indicated is labeled “RC1”.  If you are wondering if a release candidate is the correct version, it is.

2) Follow the installation steps posted at the link below.  Please note, the final section titled “Setting up and Configuring EPiServer Composer 3.2.6” on this page is very brief, so I’ve included more detailed information below in the “Additional Set Up and Configuration” section.  You may find it beneficial to return to this page and follow my instructions once you reach this point.

http://world.episerver.com/Documentation/Items/Installation-Instructions/EPiServer-Composer/Installation-Instructions---Composer-326RC1/

Note, during Composer installation the MSI will show an initial dialog and will close automatically without notification upon completion.

3) If you need to add a license after installation you will have to create the appropriate directory structure and rename the license file.  The correct directory path is in a sub-directory of your site specific installation path at in a \Dropit\License\.  An example is below:

C:\EPiServer\Sites\<mySiteName>\Dropit\License

The license must be placed in this directory and named “Extension3License.config”.  Rename it accordingly if necessary.

 

Additional Set Up and Configuration

1) Compile ComposerSampleTemplates.csproj:

a) After the installation, locate the “ComposerSampleTemplates” project.  This file is located at your site installation path (e.g. C:\EPiServer\Sites\<mySiteName>\ComposerSampleTemplates.csproj

b) Open the file in a text editor rather than Visual Studio (so it can be edited directly).

c) Find the section that looks similar to the following:

<IISUrl>http://localhost/</IISUrl>

d) Change “localhost” to your actual site URL.  Include port if necessary (e.g. <IISUrl>:17000">http://JEFF-DESKTOP:17000/</IISUrl>)

Note, if you do not make this change you may see the following error:

image

e) Save and close the csproj file.

f) Re-open the csproj file with Visual Studio and build the project.  This will create a DLL in the site bin directory for the Composer functions and page templates.

2) Set the page ID of root Composer data container:

a) Login to the site.

b) Switch to Admin mode.

c) Navigate to the “Config” tab.

d) Select “Plug-in manager” in the “’Tools” section.

e) Select the “Dropit.Extension” plug-in.

image

f) Set the Root page ID to the [Extension data Container] page by navigating to it via the browse button.  This page was added to your tree structure as a part of the Composer installation.

image

3) Import page and function type definitions:

a) In Admin mode, go to "Composer - Import/Export" in the “Tools” section.

b) Select the “Browse…” button and locate the file “ComposerSampleTemplatesData.xml” located in the “Setup folder for the installed site (by default this is c:\EPiServer\Sites\<mySiteName>\Setup). 

c) Select the “Begin Import” button.  If everything is successful you should see a log of several new items added below the “Export” section as pictured below.

image

5) Configure rules and permissions:

a) Switch to Admin mode.

b) On the “Admin” tab navigate to the “Tools” section and select “Composer” to display the page below.

image

c) For each Content function ensure that the appropriate rules are configured.  These rules determine where each function is able to be used.  Start by selecting the Content function you would like to configure.

d) Select the “Rules” tab.

e) Configure rules as appropriate.  For example, select “YouTube video” to display the page below.  In this page you can determine in which pages/content functions the user will be able to add YouTube videos.  Configuration is done by checking/un-checking items under each page type or content function.

Note, if you choose to skip this step, and you later start seeing errors suggesting that you do not have permissions to use certain functions this is likely due to these settings.

image

 

Troubleshooting

1) What if when using the Composer toolbox selection of the arrow on the right side of the control does not result in expansion of the options below that item?  While I don’t know if it is the shortest path to resolution, a reboot will typically fix this issue.

image

2) What if when attempting to drag content blocks to layout blocks and an error is displayed indicating a lack permissions to use the function (i.e. “You do not have permission to create the content function here”)?  See the “Configure rules and permissions” section above.

Nov 12, 2009

Comments

Sep 21, 2010 10:32 AM

Great stuff, been struggling with that myself

Sep 21, 2010 10:32 AM

Thanks for clarifying and adding the missing piece Jeff, will add this to de existing installation documentation for Composer.

Sep 21, 2010 10:32 AM

Thanks Andrea!

Sep 21, 2010 10:32 AM

Please note, the original link to installation steps has been updated in this blog to: http://world.episerver.com/Documentation/Items/Installation-Instructions/EPiServer-Composer/Installation-Instructions---Composer-326RC1/. Additionally items from this blog have been added to that page as well to help you in your installation. :)

Sep 21, 2010 10:32 AM

I am having a small issue when I come to configuring the plugin manager. When I click on the Dropit.Extension.UI I get a page saying "This plug-in has no settings".

Sep 21, 2010 10:32 AM

Hi Greg. Please select "Dropit.Extension", not "Dropit.Extension.UI". They look very similar but are different.

Cheers

Sep 21, 2010 10:32 AM

Also note that if you are running Internet Explorer 8 and Composer 3.2.6, you will need to be in Compatibility View mode when editing on page or you will get the following error when you drag a content or layout block onto the page... "An error has occured Could not load function. Please see log for details."

Please login to comment.
Latest blogs
Microsoft announces Natural language to SQL

Finally, Microsoft launches "Natural language to SQL," after it has been available for several months in Optimizely CMS!

Tomas Hensrud Gulla | May 23, 2024 | Syndicated blog

Five easy ways to start personalizing your content right now

If you clicked on this article, you already know that getting the right message to the right person at the right time helps drive conversions and...

Kara Andersen | May 23, 2024

ExtendedCms.TinyMceEnhancements – serwer side webp support

Today I will introduce another small feature of TinyMceEnhancements plugin. The functionality is used to automatically detect whether a browser...

Grzegorz Wiecheć | May 22, 2024 | Syndicated blog

Azure AI Language– Detect Healthcare Content in Optimizely CMS

In this blog post, I showcase how the Azure AI Language service's Text Analytics for health feature can be used to detect healthcare content within...

Anil Patel | May 22, 2024 | Syndicated blog

Stott Security Version 2 So Far

In December 2023, I unveiled the initial version of Stott Security version 2. Although I typically announce each version I release on LinkedIn and...

Mark Stott | May 22, 2024

Optimizely Data Platform (ODP) Page Scroll Tracking

As with my last post, this isn’t a “getting started with ODP” — to get started with ODP, check out the developer docs,   “Implement the ODP...

Daniel Isaacs | May 22, 2024