Custom Meta Tags
Hero Banner

Site Guidelines

Component Documentation

Common mistakes

Using CONFIGURE instead of Edit Shared Settings in the Display Portlet Menu

This cause a very big issue.  In the past, we have remove access to the system to a person when this was done.

The Display Portlet Menu looks like this:

Content creators would hardly ever have to work with this menu but it may happen if you are trying to link existing content to a page.  The option Edit Shared Setting is used to update the behavior of that specific piece of content.  The Configure option is used to update the behavior of ALL the content pieces on the whole web site. 

DO NOT EVER USE THE CONFIGURE OPTION

 

Embedding Images / Documents

While using the Static HTML component you need to add a link to an image or a document.  We see many mistakes with these.  The ones most often seen is:

Leaving the cache id as part of the URL to the document or image

  1. When you follow the instructions to load an image you are shown how to get the URL to that image.  As part of thos einstruction you need to edit the URL.
  2. When you now paste this URL it would look like this:
    https://onesite-preprod.avnet.com/wps/wcm/myconnect/onesite/f02ee3d5-686d-4235-822c-8b10b5dea6e5/Avnet-subpage-layout.jpg?MOD=AJPERES&CACHEID=ROOTWORKSPACE.Z18_G95I1CC0M85R60ABIK9ULJ3000-f02ee3d5-686d-4235-822c-8b10b5dea6e5-nHlsrxu&cache=none
  3. If you just leave the all of this URL as part of the embed, it will work when you check everything but it will not work after you published the content to PRODUCTION.  This CACHEID is only valid on the servers you are working on and does not exist on the production servers.  Therefore this would be an invalid URL in production and you will get a 404 error.
  4. You need to remove the CACHEID as part of the URL and the correct URL will look like this:
    /wps/wcm/connect/f02ee3d5-686d-4235-822c-8b10b5dea6e5/Avnet-subpage-layout.jpg?MOD=AJPERES

Leaving the host information on the URL

  1. Using the same URL from above, when you embed an image or document you need to use relative URLs.  This mean you need to remove the host information from the URL.  The host information is the onesite-preprod.avnet.com in this URL https://onesite-preprod.avnet.com/wps/wcm/myconnect/onesite/f02ee3d5-686d-4235-822c-8b10b5dea6e5/Avnet-subpage-layout.jpg?MOD=AJPERES&CACHEID=ROOTWORKSPACE.Z18_G95I1CC0M85R60ABIK9ULJ3000-f02ee3d5-686d-4235-822c-8b10b5dea6e5-nHlsrxu&cache=none
  2. If you do not remove the host information, the link will work but when somebody clicks on it they would load the content from our content development servers and not from production.  You will switch our customers to servers that is not in production.
  3. Remove the host information and now that URL will look like this:
    /wps/wcm/connect/f02ee3d5-686d-4235-822c-8b10b5dea6e5/Avnet-subpage-layout.jpg?MOD=AJPERES

Leaving a secured URL

  1. All the content creators are logged into the system while creating content.  When a content creator queries the URL for an image or a document, the system gives a secured URL for that image/document.  This secured URL have MY as part of URL /wps/wcm/myconnect/f02ee3d5-686d-4235-822c-8b10b5dea6e5/Avnet-subpage-layout.jpg?MOD=AJPERES
  2. When the content is published thecontent creator may see the image in PREPROD if they are logged in but they will not see it when logged out.  In PRODUCTION you will see the same issue where the image does not display if you are not logged in
  3. Remove the MY to create an unauthenticated URL.  The URL now looks like this:
    /wps/wcm/connect/f02ee3d5-686d-4235-822c-8b10b5dea6e5/Avnet-subpage-layout.jpg?MOD=AJPERES

Leaving ONESITE as part of the URL

  1. The URL contains the words onesite as part of the context root of the image.  In the URL https://onesite-preprod.avnet.com/wps/wcm/myconnect/onesite/f02ee3d5-686d-4235-822c-8b10b5dea6e5/Avnet-subpage-layout.jpg?MOD=AJPERES is valid but it limits where this URL can be used.
  2. For wider use of the URL remove the ONESITE from the URL.  This will also make it easier to migrate to a full DAM in the future. 
  3. The final valid URL to  use to embed images or documents should look like this:
    /wps/wcm/connect/f02ee3d5-686d-4235-822c-8b10b5dea6e5/Avnet-subpage-layout.jpg?MOD=AJPERES

 

Copying pages with Embedded/Shared content

When copying pages from one region to another with embedded content tag/path it is important to update the tag/path to the local content once the page has been copied to avoid overwriting the original content. 

Embedded content path

When copying a page, all the content within the page's site area is copied to the new location automatically but the path in the embedded content is not updated to the new location and will need to be refreshed. IF the content resides outside the page's site area, the content will need to copied  separately making sure it is copied under the same project.

This type of embed is usually done in the body when pointing to content when creating pages like NPIs or custom formatted content on pages.

NOTE: only content that is published or in draft in the same project can be embedded.  

Content path via the container Shared Settings

Again, all the content within the page's site area is copied to the new location automatically but the path in the container will still be pointing to the original content and will need to be refreshed. IF the content resides outside the page's site area, the content will need to copied  separately and path updated.

 

Using the Default Project Template instead of the Onesite Project Template.

While creating a new page in a project you may get the following error

 

OG image and image path do not match

When updating an OG image, MAKE SURE to also update the path of the image or the new image will not be recognized in the OG meta tags
 

 

NOTE,  the path picked up by the meta tags will be what is designated in the image URL field: