Search

Searching KNOWLEDGEBASE

Export Page

After Publishing

Content of the website is being hidden by the Amplience tcplayer.

Check in your embed code the section of the “params:{ “ and add an extra parameter, wmode=”opaque”. Also, if you have used CSS, check if you have used float: left. This format can cause some content to be hidden. Deleting the CSS (float:left) will resolve this.

The HTML5 format is not displaying. 

Reference an xd in the embed code and upload the crossdomain in the appropriate place with the data files. When testing the module on your website, clear your browser cache then test the page.

My content is displaying blank after publishing.

If links have been used, this can be caused by an empty link within text. Links can be added to words in rich text and when these are removed they they need to be removed completely with the following button

  

If just the URL is deleted without removing the link this can cause the module to break and not display correctly after publishing. To prevent this from happening, the above button should be used when removing a link from text. 

An old background appears briefly as the Amplience content loads?

This is often caused by a background image being set below the module content. This can be removed by:

  • Opening the module.
  • Click on the grey background outside of the content.
  • A small menu will appear top left. Click on the image icon.
  • Click the reset image icon to the right to clear the background image.
  • The background image will now be removed.
  • Save and publish as normal.

When saving a module, Chrome is displaying a Shockwave error and crashing?

Issues with Shockwave can occur when 2 flash plugins are installed. Google Chrome includes an integrated version of Flash and a standalone version is often downloaded for other browsers, which together can conflict and cause chrome to crash.

To check this

  • Open Chrome and type about:plugins into the address bar at the top and press 'enter'. This will bring up Chrome's plugin list.
  • Look down the list. If it says 'Adobe Flash Player (2 files)' then you have both installed. If it says 'Adobe Flash Player (1 file)' then you have only the integrated version installed.
  • Click on the '+ Details' link at the top right of the page to expand the list of plugins. Scroll down to the Flash plugins for their full details and locations. The integrated version, PepperFlash, is in …Application Data\Google\Chrome\Application..., whilst the independent version is in the …Windows\system32\Macromed\Flash... directory.
  • If only one version is installed, go online and download the latest standalone version of Flash. Close Chrome and install this. Open chrome and go back to about:plugins. There should now be two. Click disable under the integrated, PepperFlash, version and ensure that the other Adobe version is enabled. Test page again.
  • If there are already two versions installed, click 'disable' under the PepperFlash version and ensure that the Adobe version is enabled. Test the page. If this still fails, swap the enabled version, enabling PepperFlash and disabling the Adobe version.

A video I have included in my module is not displaying in Chrome?

A video can sometimes fail to display after publishing if the interact.min.js and swfobject.min.js files are referenced within the page more than once. Even when multiple modules are used, these should only be referenced once, preferably in the page head.  This issue can also be caused when there are spaces at the beginning or the end of the video URL's being used.

I have created a single page module, but my content seems to flicker. Why is this?

This issue can appear when you have a single page carousel, which has Autoplay turned on.As there is only one page, each instance the carousel automatically scrolls the module is reloaded, which causes some content to flicker. 

To turn this option off, go to the associated Content Template and, under the Carousel settings, deselect the 'Auto Play' checkbox. You will also need to ensure that this option has also been deselected within the module itself. 

The text in my module doesn't display consistently/ correctly when changing between landscape and portrait on iPad?

At times switching between portrait and landscape view, on iOS devices, can cause text elements to display inconsistently or crop. 

To resolve this, a small addition needs to be made to the Amplience module embed code, on the affected pages.

Within the vars section of this, forceTransform:true will need to be added.

This update can be seen in the following code example:

 

 

 

  • No labels