[interchange-docs] xmldocs - docelic modified 4 files
docs at icdevgroup.org
docs at icdevgroup.org
Sat Nov 10 18:24:34 EST 2007
User: docelic
Date: 2007-11-10 23:24:33 GMT
Modified: . TODO
Modified: glossary UserDB
Modified: refs space_to_nbsp.filter
Added: glossary affiliate
Log:
* small updates/fixes
Revision Changes Path
1.108 +0 -5 xmldocs/TODO
rev 1.108, prev_rev 1.107
Index: TODO
===================================================================
RCS file: /var/cvs/xmldocs/TODO,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -r1.107 -r1.108
--- TODO 10 Nov 2007 22:45:41 -0000 1.107
+++ TODO 10 Nov 2007 23:24:33 -0000 1.108
@@ -188,12 +188,7 @@
-$Session->{source} bzw. [data session source] comes from:
-
-http://host/cgi-bin/cat?;;thesource (old MV 3 way, still works)
-http://host/cgi-bin/cat?mv_pc=thesource (current way)
http://host/cgi-bin/cat?mv_pc=RESET (clears it, for debugging)
-
Otherwise mv_pc does double duty as a cache foiler, and is a meaningless,
incrementing integer.
1.7 +5 -2 xmldocs/glossary/UserDB
rev 1.7, prev_rev 1.6
Index: UserDB
===================================================================
RCS file: /var/cvs/xmldocs/glossary/UserDB,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- UserDB 10 Nov 2007 22:25:03 -0000 1.6
+++ UserDB 10 Nov 2007 23:24:33 -0000 1.7
@@ -163,9 +163,12 @@
&conf-ValuesDefault;).
</para><para>
Often times, you would like to save users' data back to the user
- database, be it during or at the end of user session. To that
- effect, use the following simple yet powerful code:
+ database, be it during or at the end of user session. You can
+ automatically do this with a combination of form processing
+ directives, but if you want to do it manually,
+ use the following simple yet powerful code:
<programlisting>
+[update values]
[userdb save]
</programlisting>
The above code saves all users' &glos-value;s back to the database.
1.1 xmldocs/glossary/affiliate
rev 1.1, prev_rev 1.0
Index: affiliate
===================================================================
When giving links to your website to your partners, often times you want
to embed an identification string that will link visits or eventual
sales to the corresponding partner.
</para><para>
&IC; supports affiliate tracking; the source of the visit or order
is always accessible using <code>[data session source]</code>.
</para><para>
So when giving links to your affiliates, make sure the affiliate code
you assign them is embedded in one of the following ways:
<programlisting>
http://&def-hostname;/cgi-bin/&std-catalog;/index?;;thesource (old Minivend 3 way, still works)
http://&def-hostname;/cgi-bin/&std-catalog;/index?mv_pc=thesource (Interchange way, still works)
http://&def-hostname;/cgi-bin/&std-catalog;/index?mv_source=thesource (current way)
</programlisting>
Note that <mv>mv_source</mv> was added as an affiliate code-passing option
only in &IC; 4.9.x. Before that, affiliate code was passed in <mv>mv_pc</mv>.
The <mv>mv_pc</mv> variable is used as a variable containing a random number
to prevent caching of pages. So if you want to use mv_pc as a way of
carrying over the affiliate code, it must contain at least one non-digit.
(<literal>mv_pc=A12</literal> is a good affiliate code,
<literal>mv_pc=12</literal> is not). If using <mv>mv_source</mv>, affiliate
code is free of this restriction.
</para><para>
Sometimes you want the affiliate code to disappear from the URL after
the visitors get redirected to your page. To enable that feature, see
&conf-BounceReferrals; configuration directive.
1.2 +11 -10 xmldocs/refs/space_to_nbsp.filter
rev 1.2, prev_rev 1.1
Index: space_to_nbsp.filter
===================================================================
RCS file: /var/cvs/xmldocs/refs/space_to_nbsp.filter,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- space_to_nbsp.filter 10 Nov 2007 22:25:03 -0000 1.1
+++ space_to_nbsp.filter 10 Nov 2007 23:24:33 -0000 1.2
@@ -1,5 +1,5 @@
__NAME__ purpose
-replace all spaces (" ") with null ("\0") characters
+replace all spaces (" ") with nonbreakable space ("&nbsp;") characters
__END__
@@ -10,18 +10,18 @@
__NAME__ description
The filter replaces all space ("<literal> </literal>") characters
-with &glos-HTML;'s Non-breakable-space ("<literal>&nbsp;</literal>")
+with &glos-HTML;'s nonbreakable-space ("<literal>&nbsp;</literal>")
characters.
</para><para>
This is useful for places where you want strings to appear in a single
-line, without word-wrapping to the next row.
+line, without word-wrapping to the next line.
__END__
__NAME__ notes
-In &glos-HTML;, multiple spaces in a row render as just one space on the
+In &glos-HTML;, multiple spaces in a line render as just one space on the
screen. When the spaces are converted to "&nbsp;", however, every
-non-breakable space will produce one space character on the screen —
-it's how &glos-HTML; works..
+nonbreakable space will produce one space character on the screen —
+it's how &glos-HTML; works.
Use the &glos-filter;'s <option>compress</option> when you want to
preserve the behavior of only one space being visible on the screen.
__END__
@@ -29,13 +29,13 @@
__NAME__ online: Filter example
<programlisting><![CDATA[
<div style="width: 80px;">
-This is a very small DIV and will surely word-wrap this text to multiple lines..
-With the filter applied, however, it will force the DIV to stretch and render as single line.
+This is a very small DIV and will surely word-wrap this text to multiple lines.
+With the filter applied, however, it will force the DIV to stretch and render as single line.
</div>
<div style="width: 80px;">
[filter space_to_nbsp]
-With the filter applied, however, it will force the DIV to stretch and render as single line.
+With the filter applied, however, it will force the DIV to stretch and render as single line.
[/filter]
</div>
]]></programlisting>
@@ -47,8 +47,9 @@
<programlisting><![CDATA[
<div>
[filter space_to_nbsp.compress]
-Multiple spaces in a row will render as just single space.
+Multiple spaces in a line will render as just single space.
[/filter]
</div>
]]></programlisting>
__END__
+
More information about the docs
mailing list