From f0b3994f51937c643200a0547f70b1fa7d94f88a Mon Sep 17 00:00:00 2001
From: Derek Jones CodeIgniter does not load Helper Files by default, so the first step in using
a Helper is to load it. Once loaded, it becomes globally available in your controller and views. Helpers are typically stored in your system/helpers, or system/application/helpers directory. CodeIgniter will look first in your system/application/helpers
+ Helpers are typically stored in your system/helpers, or application/helpers directory. CodeIgniter will look first in your application/helpers
directory. If the directory does not exist or the specified helper is not located there CI will instead look in your global
system/helpers folder. By default it is assumed that you only intend to use CodeIgniter to manage one application, which you will build in your
-system/application/ directory. It is possible, however, to have multiple sets of applications that share a single
+application/ directory. It is possible, however, to have multiple sets of applications that share a single
CodeIgniter installation, or even to rename or relocate your application folder.Managing your Applications
Renaming the Application Folder
@@ -83,29 +83,29 @@ To do so open your main index.php and set a full server path
put all of the directories located inside your application folder into their
own sub-folder.
For example, let's say you want to create two applications, "foo" and "bar". You will structure your -application folder like this:
- -system/application/foo/
-system/application/foo/config/
-system/application/foo/controllers/
-system/application/foo/errors/
-system/application/foo/libraries/
-system/application/foo/models/
-system/application/foo/views/
-system/application/bar/
-system/application/bar/config/
-system/application/bar/controllers/
-system/application/bar/errors/
-system/application/bar/libraries/
-system/application/bar/models/
-system/application/bar/views/
+For example, let's say you want to create two applications, "foo" and "bar". You could structure your +application folders like this:
+ +applications/foo/
+applications/foo/config/
+applications/foo/controllers/
+applications/foo/errors/
+applications/foo/libraries/
+applications/foo/models/
+applications/foo/views/
+applications/bar/
+applications/bar/config/
+applications/bar/controllers/
+applications/bar/errors/
+applications/bar/libraries/
+applications/bar/models/
+applications/bar/views/
To select a particular application for use requires that you open your main index.php file and set the $application_folder variable. For example, to select the "foo" application for use you would do this:
-$application_folder = "application/foo";
+$application_folder = "applications/foo";
Note: Each of your applications will need its own index.php file which calls the desired application. The index.php file can be named anything you want.
diff --git a/user_guide/general/profiling.html b/user_guide/general/profiling.html index 8622edeb9..f8650314d 100644 --- a/user_guide/general/profiling.html +++ b/user_guide/general/profiling.html @@ -87,7 +87,7 @@ This information can be useful during development in order to help with debugginEach section of Profiler data can be enabled or disabled by setting a corresponding config variable to TRUE or FALSE. This can be done one of two ways. First, you can set application wide defaults with the system/application/config/profiler.php config file.
+Each section of Profiler data can be enabled or disabled by setting a corresponding config variable to TRUE or FALSE. This can be done one of two ways. First, you can set application wide defaults with the application/config/profiler.php config file.
$config['config'] = FALSE;
$config['queries'] = FALSE;
--
cgit v1.2.3-24-g4f1b