Skip to content

Commit c6e0b1b

Browse files
committedApr 2, 2013
Fix #15704: Wrong description of writing custom_functions
1 parent e312d22 commit c6e0b1b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed
 

‎docbook/Admin_Guide/en-US/Customizing.xml

+2-2
Original file line numberDiff line numberDiff line change
@@ -866,15 +866,15 @@ $g_status_enum_workflow[CLOSED] ='20:feedback,50:assigned';
866866
<para>User versions of these functions (overrides) are named like
867867
<emphasis>custom_function_override_descriptive_name</emphasis>,
868868
and placed in a file called
869-
<filename>custom_constants_inc.php</filename> that must be saved in
869+
<filename>custom_functions_inc.php</filename> that must be saved in
870870
MantisBT's root directory (This is the same place where the
871871
<filename>config_inc.php</filename> file resides).
872872
In normal processing, the system will look for override functions
873873
and execute them instead of the provided default functions.
874874
</para>
875875
<para>The simplest way to create a custom function is to copy the
876876
default one from the api to your override file
877-
(<filename>custom_constants_inc.php</filename>), and rename it
877+
(<filename>custom_functions_inc.php</filename>), and rename it
878878
(i.e. replacing 'default' by 'override').
879879
The specific functionality you need can then be coded into the
880880
override function.

0 commit comments

Comments
 (0)
Please sign in to comment.