From 6c46d97eea313a73b55e34e80fe1030b97f4654e Mon Sep 17 00:00:00 2001
From: Colin Kuskie
Date: Mon, 30 Oct 2006 18:37:29 +0000
Subject: [PATCH] update help mentioning RawHeadTags macro
---
docs/changelog/7.x.x.txt | 2 ++
lib/WebGUI/i18n/English/Asset.pm | 6 +++---
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/docs/changelog/7.x.x.txt b/docs/changelog/7.x.x.txt
index e045d116c..7e92b236f 100644
--- a/docs/changelog/7.x.x.txt
+++ b/docs/changelog/7.x.x.txt
@@ -24,6 +24,8 @@
- Tried to clean up some HttpProxy code. Still very ugly. (need rewrite?)
- fix: HttpProxy would not put correct values for multiple query params with
same name.
+ - fix: metadata (WebGUI Help). Removed mention of the RawHeadTags macro
+ from the Metadata help.
7.1.2
diff --git a/lib/WebGUI/i18n/English/Asset.pm b/lib/WebGUI/i18n/English/Asset.pm
index 3e30628a0..64d14f6ce 100644
--- a/lib/WebGUI/i18n/English/Asset.pm
+++ b/lib/WebGUI/i18n/English/Asset.pm
@@ -615,11 +615,11 @@ each asset under the tab "Meta" in the asset properties.
Metadata fields are exposed to the asset templates as their property name. So you can actually display the metadata
to the rendered page using a template variable like <tmpl_var propertyname>
Meta tags
- Since the meta data is exposed as template variables, you can use that in combination with the ^RawHeadTags();
- macro to create meta tags from meta data, including the tags from the Dublin Core standard.
+ Since the meta data is exposed as template variables, you can use them in the Head Block of Style templates
+ to create meta tags from meta data, including the tags from the Dublin Core standard.
|,
context => q|Metadata help|,
- lastUpdated => 1110530955
+ lastUpdated => 1162233025
},
'metadata edit property' => {