| verzia 1.45, 2004/11/10 17:00:14 |
verzia 1.46, 2004/11/20 02:24:34 |
|
|
| <!-- $Platon: phpMyEdit/doc/sgml/configuration.general.sgml,v 1.44 2004/07/15 13:41:16 nepto Exp $ --> |
<!-- $Platon: phpMyEdit/doc/sgml/configuration.general.sgml,v 1.45 2004/11/10 17:00:14 nepto Exp $ --> |
| |
|
| <sect1 id="configuration.mysql-options"> |
<sect1 id="configuration.mysql-options"> |
| <title id="configuration.mysql-options.title">Database connection</title> |
<title id="configuration.mysql-options.title">Database connection</title> |
| Riadok 922 The type of performed operation such as |
|
| Riadok 922 The type of performed operation such as |
|
| passed using a CGI variable named <varname>operation</>. When passed through a |
passed using a CGI variable named <varname>operation</>. When passed through a |
| link, for example when <varname>$opts['navigation']</varname> is set |
link, for example when <varname>$opts['navigation']</varname> is set |
| to <constant>'G'</constant> or <constant>'T'</constant>, the |
to <constant>'G'</constant> or <constant>'T'</constant>, the |
| value is an untranslated label prefixed with <constant>PME::op::</constant>. |
value is an untranslated label prefixed with <constant>PME_op_</constant>. |
| This prefix can be changed by setting the |
This prefix can be changed by setting the |
| <varname>$opts['cgi']['prefix']['operation']</varname> variable in the calling |
<varname>$opts['cgi']['prefix']['operation']</varname> variable in the calling |
| script. |
script. |
| Riadok 935 $opts['cgi']['prefix']['operation'] = 'o |
|
| Riadok 935 $opts['cgi']['prefix']['operation'] = 'o |
|
| </para> |
</para> |
| <para> |
<para> |
| |
|
| In the future, more and more CGI prefixes like form field names, button names |
If you already use in your project some CGI variables used internally by &name;, |
| and others will be configurable. |
like '<varname>operation</>, you may want to prefix &name;'s variables to avoid |
| |
collision. For the same reason, you may want to prefix the names of input |
| |
fields. |
| |
|
| |
<example><title>Custom name prefix for CGI variables</title> |
| |
<programlisting><![CDATA[ |
| |
$opts['cgi']['prefix']['sys'] = 'sys_prefix_'; |
| |
$opts['cgi']['prefix']['data'] = 'data_prefix_'; |
| |
]]></programlisting></example> |
| |
|
| |
</para> |
| |
</sect1> |
| |
|
| |
<sect1 id="configuration.js-and-dhtml"> |
| |
<title id="configuration.js-and-dhtml.title">Javascript and DHTML</title> |
| |
<para> |
| |
|
| |
CGI <varname>sys</varname> and <varname>data</varname> name prefixing may |
| |
especially be useful if you want to display two instance of &name; on the same |
| |
page. But you will require to prefix Javascript and DHTML tags as well, to make &name; |
| |
forms truely independant. |
| |
|
| |
</para> |
| |
<para> |
| |
|
| |
Javascript functions are default prefixed by <constant>PME_js_</constant> |
| |
string. DHTML ID tags are defaultly prefixed by |
| |
<constant>PME_dhtml_</constant> string. You may change this using the syntax |
| |
below. |
| |
|
| |
<example><title>Custom name prefix for JS and DHTML</title> |
| |
<programlisting><![CDATA[ |
| |
$opts['js']['prefix'] = 'js_prefix_'; |
| |
$opts['dhtml']['prefix'] = 'dhtml_prefix_'; |
| |
]]></programlisting></example> |
| |
|
| </para> |
</para> |
| </sect1> |
</sect1> |