Timeline for Config Path variables available in Static Blocks
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 29, 2015 at 21:48 | comment | added | mpchadwick | Great point. It most certainly is affected by those changes magento.com/security/patches/supee-6788-technical-details "Magento now includes a white list of allowed blocks or directives. If a module or extension uses variables like {{config path=”web/unsecure/base_url”}} and {{block type=rss/order_new}} in CMS pages or emails, and the directives are not on this list, you will need to add them with your database installation script." | |
| Dec 29, 2015 at 21:40 | comment | added | philwinkle | @mpchadwick I wonder how this is impacted by the whitelist of the latest round of SUPEE 6788 changes? | |
| Dec 29, 2015 at 21:38 | comment | added | mpchadwick | This thread is old, but I was trying to do the same thing today. Not sure that this is the best way but this worked for me <img src="{{skin url=''}}{{config path='design/header/logo_src'}}"> | |
| Jul 14, 2014 at 13:51 | vote | accept | Maxi | ||
| Jul 11, 2014 at 20:30 | comment | added | Maxi | Hi philwinkle. Even thought I did manage to get the logo_src variable, I still can't achieve what I was looking for, since it's a skin path. What would the best way to print that image be? I tried nesting config paths, but doesn't seem to work: {{skin url='{{config path="design/header/logo_src"}}'}}. Thanks! | |
| Jul 11, 2014 at 20:18 | vote | accept | Maxi | ||
| Jul 11, 2014 at 20:28 | |||||
| Jul 11, 2014 at 20:18 | comment | added | Maxi | Thank you very much for your reply. After reading to your response, I realized for whatever reason, there was an extra closing quote mark ('") on all the variables. I might have copied them wrongly or something, but simply reassuring it should work really helped me! | |
| Jul 11, 2014 at 19:49 | history | answered | philwinkle | CC BY-SA 3.0 |