Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: No Longer Reproducible
-
Affects Version/s: 6.1.1 CE GA2
-
Fix Version/s: 6.2.0 CE M4
-
Component/s: WCM, WCM > Staging, WCM > Web Content Administration
-
Labels:
-
Similar Issues:
Description
When staging is enabled and the theme applied has the capability to display footer web content, there is an issue. Take for example the new Zoe themes which have theme settings where you can put in web content ID's to display content.
Steps to reproduce:
- Install/choose a theme that has settings for footer content (Zoe themes, for example).
- Enable staging for the site
- Create web content (note the web content ID for next step)
- Paste web content ID in theme's settings for one of the footer content locations
- Observe that the content is displayed in the footer as expected in the staging environment.
- Mark for publication
- Publish to live
- Observe that the footer content is not displayed at all.
I realized that this is caused by the differing content ID's in staging/live. As a workaround, I took the following steps:
- Place a web content portlet on the page
- Select the web content I would have placed in the footer
- Mark for publication
- Publish to live
- View source and observe the web content div's id (something like id="article_17037_17062_32860_1.0")
- Write down the last 5 numbers of the id (32860)
- Go back to staging environment
- Remove web content display
- Place the id number obtained previously in the theme settings for footer content
- Observe that the footer content is NOT displayed because we are still in staging.
- Mark for publication
- Publish to live
- Observe that the web content IS displayed because we used the live web content id rather than the staging id.
This should help to illustrate the problem. As you can see, this is not really a viable work around because it's so involved.

Drew Blessing, Thank you for your report. Have you had the
opportunity to discuss this issue on the community forums? If so, were there other users
who were also experiencing this problem?
Thanks!
This issue will be closed