Metadata value for Declared Var

Hi,


We have a declared var that is assigned the value of a metadata value. For some page assets the metadata keyword is not converted into a value.



The declared var code is at top of page with print=no

    
    
    

and then used in a show if simple edit design area as a mysource_print tag.

    


So on some pages the keyword is printed to the front end (%asset_metadata_StudyArea%)
On other pages the value of the keyword is printed to the front end (eg. health)

nb. I cannot use a metadata design area in the content (rather than the mysource_print tag) as it would mean a design area within a design area.

More investigation has revealed that the keyword for the metadata studyarea is being saved in the design_file.php has plain text. See below…

    
    <?php; 
    } else {
    ?>
    
    
    <?php; }
    		?>


Is this meant to be happening? We've tested the same design on a different installation, and it does not do this.

Aleks

I didn't think it'd ever work. Its global keyword replacement at work, but one of the developers would have to respond.

I'm thinking of running the system_parse_design.php… I see there is a system_parse_designs.php - so I am assuming that the first one can parse a single design? Not one of the listed scripts in Admin Manual, any advice on running this one?

Correct. system_parse_design.php requires an asset ID and just parses that design. system_parse_designs.php finds all the Design files in the system and parses them all.


This is exactly the same as a manual reparse or saving the parse file in the Administration Interface, though.

Thanks Avi, can rule that out then. I have checked via history that this page has had this problem with the metadata value since creation it seems. That is relevant because we used the metadata design area back on the rollback version - not the declared var that uses the %asset_metadata_StudyArea% keyword for the value. The code that has always worked until this standard page asset has been:

    
    	  
    


To that end, the declared var using %asset_metadata_StudyArea% for the value works fine for the same design and same metadata schema on other standard pages... real mystery it seems...