View Issue Details

IDProjectCategoryView StatusLast Update
0004298OXID eShop (all versions)1.04. Content, static (register, contact etc.) pagespublic2014-02-18 16:46
Status resolvedResolutionfixed 
Product Version4.6.1 revision 45706 
Target Version4.7.0_5.0.0_RC1Fixed in Version4.7.0_5.0.0_beta1 
Summary0004298: Sometimes wrong content loaded on CMS page
DescriptionClick on different CMS page ling and u may get wrong content data (when content::getParsedContent() is used in template). And my fix was following (added content id parameter oxUtilsView::parseThroughSmarty() and for multilanguage solutions language id woucl also be recommended, or, even better - getViewId()..):

 * Fixes content view issue
class fixcontent extends fixcontent_parent
     * Returns content parsed through smarty
     * @return string
    public function getParsedContent()
        return oxUtilsView::getInstance()->parseThroughSmarty( $this->getContent()->oxcontents__oxcontent->value, $this->getContent()->getId() );
TagsNo tags attached.
PHP Versionany
Database Versionany


has duplicate 0004082 resolvedsaulius.stasiukaitis CMS - content not changed when containig picture path with Smarty 
has duplicate 0004581 closeddainius.bigelis content::getParsedContent() missing oxid argument 
related to 0004996 resolvedmantas.vaitkunas CMS cache fails if Smarty conditions are available. 



2012-10-01 11:41

reporter   ~0007515

Why is this still not fixed? We've just launched a Shop version 4.6.4 and after changing settings for live mode, some cms pages show same content. This could cause that an imprint (german Impressum) will never show. A serious legal issue, not to mention the user experience..
The fix works!


2012-10-01 12:42

reporter   ~0007516

related to this one maybe?


2012-10-01 13:38

reporter   ~0007517

In our setup there are no images in contents of the cms page.
As far as I can see the bug occurs regardless of images.


2012-10-02 14:53

reporter   ~0007528

The bug occurs if any smarty tag is present in CMS content. I think the fix provided is sufficient, multilanguage is already handled in parseThroughSmarty. The Bug is also in 4.7.0 beta 2.