*** empty log message ***

git-svn-id: svn://pmwiki.org/trunk/pmwiki@631 524c5546-5005-0410-9a3e-e25e191bd360

1 files changed, 7 insertions, 7 deletions

diff --git a/wikilib.d/PmWiki.LocalCustomizations b/wikilib.d/PmWiki.LocalCustomizations
index 7dc9de2f..b6d6f9e9 100644
--- a/wikilib.d/PmWiki.LocalCustomizations
+++ b/wikilib.d/PmWiki.LocalCustomizations
@@ -1,10 +1,10 @@
-version=pmwiki-2.0.beta26
+version=pmwiki-2.0.beta28
 newline=²
-text=From its inception, PmWiki has been designed so that [[WikiAdministrator]]s can greatly customize the way PmWiki displays pages and the markup sequences used to generate pages.  (This is even mentioned explicitly in [[PmWikiPhilosophy]] #4.)  As a result, the core ''pmwiki.php'' script makes extensive use of [[PmWiki.Variables]] to determine how markup sequences will be processed and what each individual page will output.  Thus, a WikiAdministrator can make a lot of customizations simply by setting variables in the ''config.php'' (formerly called the ''local.php'') file.²²The bulk of this page describes how customizations work in general, see [[PmWiki.DocumentationIndex]] for specific customizations that are commonly performed at many PmWiki installations, including:²²* [[Layout Basics]]²* [[Internationalizations]]²* [[Custom Markup]]²* [[Custom InterMap]]s²²The ''scripts/'' subdirectory (below the directory holding the ''pmwiki.php'' script) and the PmWiki [[(Cookbook:)Cookbook]] contain many example customizations that you can include in your ''config.php'' site configuration.  The first few lines of each of these scripts generally contain instructions about how to enable (and use) the feature provided by the script--for most scripts, simply adding a line like²²        include_once("scripts/''scriptfile.php''");²²in the ''config.php'' file will enable it.  Some of the scripts are automatically enabled for you via the ''scripts/stdconfig.php'' script unless you disable them by setting @@$EnableStdConfig=0@@ in ''config.php''.²²Note that you should strongly resist the temptation to directly modify the ''pmwiki.php'' script or the scripts in the ''scripts/'' subdirectory.  Any modifications you make to these files will probably be overwritten whenever you perform a [[PmWiki.Upgrade(s)]].  Instead, look at some of the sample scripts for examples of customizations that can be performed from ''config.php''. You can even create your own script to do a customization and use @@include_once(...)@@ to include it from ''config.php''.  If you do make your own customization script, you can safely put it in the ''local/'' subdirectory--it won't get overwritten by an upgrade there.  You might also want to submit your customization to the [[http://www.pmichaud.com/lists/pmwiki-users pmwiki-users mailing list]] or the [[(Cookbook:)Cookbook]] so that others can benefit from your effort and so that it can perhaps be included in future releases of PmWiki.²²<<|PmWiki.DocumentationIndex|>>
-time=1110383211
+text=From its inception, PmWiki has been designed so that [[WikiAdministrator]]s can greatly customize the way PmWiki displays pages and the markup sequences used to generate pages.  (This is even mentioned explicitly in [[PmWikiPhilosophy]] #4.)  As a result, the core ''pmwiki.php'' script makes extensive use of [[PmWiki.Variables]] to determine how markup sequences will be processed and what each individual page will output.  Thus, a WikiAdministrator can make a lot of customizations simply by setting variables in the ''config.php'' (formerly called the ''local.php'') file.²²The bulk of this page describes how customizations work in general, see [[PmWiki.DocumentationIndex]] for specific customizations that are commonly performed at many PmWiki installations, including:²²* [[Layout Basics]]²* [[Internationalizations]]²* [[Custom Markup]]²* [[Custom InterMap]]s²²The ''scripts/'' subdirectory (below the directory holding the ''pmwiki.php'' script) and the PmWiki [[(Cookbook:)Cookbook]] contain many example customizations that you can include in your ''config.php'' site configuration.  The first few lines of each of these scripts generally contain instructions about how to enable (and use) the feature provided by the script--for most scripts, simply adding a line like²²        include_once("scripts/''scriptfile.php''");²²in the ''config.php'' file will enable it.  Some of the scripts are automatically enabled for you via the ''scripts/stdconfig.php'' script unless you disable them by setting @@$EnableStdConfig=0@@ in ''config.php''.²²Note that you should strongly resist the temptation to directly modify the ''pmwiki.php'' script or the scripts in the ''scripts/'' subdirectory.  Any modifications you make to these files will probably be overwritten whenever you perform a [[PmWiki.Upgrade(s)]].  Instead, look at some of the sample scripts for examples of customizations that can be performed from ''config.php''. You can even create your own script to do a customization and use @@include_once(...)@@ to include it from ''config.php''.  If you do make your own customization script, you can safely put it in the ''local/'' subdirectory--it won't get overwritten by an upgrade there.  You might also want to submit your customization to the [[http://www.pmichaud.com/lists/pmwiki-users|pmwiki-users mailing list]] or the [[(Cookbook:)Cookbook]] so that others can benefit from your effort and so that it can perhaps be included in future releases of PmWiki.²²<<|PmWiki.DocumentationIndex|>>
+time=1112078600
 name=PmWiki.LocalCustomizations
-host=208.54.94.65
-agent=Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
-rev=3
+host=66.92.171.251
+agent=Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
+rev=4
 targets=PmWiki.WikiAdministrator,PmWiki.PmWikiPhilosophy,PmWiki.Variables,PmWiki.PmWiki,PmWiki.DocumentationIndex,PmWiki.LayoutBasics,PmWiki.Internationalizations,PmWiki.CustomMarkup,PmWiki.CustomInterMap,PmWiki.Upgrades,PmWiki.InitialSetupTasks
-author=Pm
+author=bev