Index: branches/release-41/lib/MT/App.pm =================================================================== --- branches/release-41/lib/MT/App.pm (revision 2741) +++ branches/release-41/lib/MT/App.pm (revision 2745) @@ -3346,32 +3346,4 @@ The -=head2 $app->template_paths - -Returns an array of directory paths where application templates exist. - -=head2 $app->find_file(\@paths, $filename) - -Returns the path and filename for a file found in any of the given paths. -If the file cannot be found, it returns undef. - -=head2 $app->load_tmpl($file[, @params]) - -Loads a L template using the filename specified. See the -documentation for the C method to learn about how templates -are located. The optional C<@params> are passed to the L -constructor. - -=head2 $app->set_default_tmpl_params($tmpl) - -Assigns standard parameters to the given L C<$tmpl> object. -Refer to the L section for a -complete list of these parameters. - -=head2 $app->charset - -Gets or sets the application's character set based on the "PublishCharset" -configuration setting or the encoding of the active language -(C<$app-Ecurrent_language>). - =head2 $app->add_return_arg(%param) @@ -3471,8 +3443,4 @@ This method is deprecated. - -=head2 $app->static_path - -Returns the application's static web path. =head2 $app->takedown @@ -3588,97 +3556,4 @@ child objects were changed during the application request. -=head2 $app->build_page($tmpl_name, \%param) - -Builds an application page to be sent to the client; the page name is specified -in C<$tmpl_name>, which should be the name of a template containing valid -L markup. C<\%param> is a hash ref whose keys and values will -be passed to L for use in the template. - -On success, returns a scalar containing the page to be sent to the client. On -failure, returns C, and the error message can be obtained from -C<$app-Eerrstr>. - -=head3 How does build_page find a template? - -The C function looks in several places for an app -template. Two configuration directives can modify these search paths, -and application and plugin code can also affect them. - -The I config directive is an absolute path to the directory -where MT's core application templates live. It defaults to the I -plus an additional path segment of 'tmpl'. - -The optional I config directive is a path (absolute -or relative) to a directory where some 'override templates' may -live. An override template takes the place of one of MT's core -application templates, and is used interchangeably with the core -template. This allows power users to customize the look and feel of -the MT application. If I is relative, its base path -is the value of the Movable Type configuration file. - -Next, any application built on the C foundation can define -its own I parameter, which identifies a subdirectory of -TemplatePath (or AltTemplatePath) where that application's templates -can be found. I defaults to C. Most templates will -be found in this directory, but sometimes the template search will -fall through to the parent directory, where a default error template -is found, for example. I should rightly have been named -I, since it is application-specific. - -Finally, a plugin can specify its I, which -locates a directory where the templates for that plugin's own -interface are found. If the I is relative, it -may be relative to either the I, or the I; the former -takes precedence if it exists. (for a definition of I and -I, see L) - -Given these values, the order of search is as follows: - -=over 4 - -=item * I - -=item * I - -=item * IFI - -=item * I/I - -=item * I - -=back - -If a template with the given name is not found in any of these -locations, an ugly error is thrown to the user. - -=head2 $app->build_page_in_mem($tmpl, \%param) - -Used internally by the L method to render the output -of a L object (the first parameter) using the parameter -data (the second parameter). It additionally calls the L -method (to process any EMT_ACTIONE and EMT_X:YE marker tags) -and then L (to process any EMT_TRANSE tags). - -=head2 $app->process_mt_template($str) - -Processes the EMT_ACTIONE tags that are present in C<$str>. These tags -are in the following format: - - - -The mode parameter is required (and must be the first attribute). The -following attributes are appended as regular query parameters. - -The MT_ACTION tag is a preferred way to specify application links rather -than using this syntax: - - ?__mode=mode_name¶meter=value - -C also strips the C<$str> variable of any tags in -the format of CMT_\w+:\w+E>. These are 'marker' tags that are -used to identify specific portions of the template page and used in -conjunction with the transformer callback helper methods C, -C, C, C. - =head2 $app->tmpl_prepend(\$str, $section, $id, $content)