Location: PHPKode > projects > Eocene (PHP Version) > eoceneSystem/readme.txt
Eocene Version 1.1.0

Please review the installation section of the manual (in doc directory), for running the 
examples included in the installation pack. However, the manual describes to change the rootFolder 
and rootURL in the config.xml. For Eocene 1.1, you do not have to do so becuase we are using 
relative path and virtual URL.

You should have the following directories and files in eoceneSystem
doc		(directory)
eocene		(directory)
examples	(directory)
lib		(directory)
config.xml	(file)
receiver.php	(file)

eocene folder contains the following files:

Every attempt is made to make the upgrade backward compatible. 
You should be able to replace all the files in Eocene and lib directory of version 1.0.0 with 
the modified files of version 1.1 and add the new files of version 1.1 in the two directories.

HOWEVER, you MUST change your RECEIVER file to matach the receiver of version 1.1 to work.

The best way to check your application compatibility with version 1.1 is to run your application 
using a different receiver and config file and Eocene version 1.1, extracted in a different directory 
than Eocene version 1.0.0

Release Notes, V 1.1.0
Bug Fixes
1. Fixed ini bug in receiver.php
   Now Eocene path is prepended to the exisitng path and it works for both Windows and *nix.

2. Now you can use arrays in query string and form action.

3. The rootURL in config file can be relative (or virtual) with respect to $_SERVER['HTTP_HOST'].
   When the rootURL is virtual, it must start with a / (forward slash).
   e.g. /webfolder1/webfolder2

4. The rootFolder in config file can be relative to the folder where config file is located.
   When the rootFolder is relative, it must start with a / (forward slash), except when it is only a . (dot).
   It can be /../../folder1/folder2
   The above indicates that move two levels up from the folder where config file is located 
   and then go to folder1 and then folder2.
   It can also be /folder1/folder2
   The above indicates that go inside folder1 and then into folder2 (folder1 is inside the folder where config 
   file is located).
   If your rootFolder is same as the folder where config file is located, put . in your rootFolder 
   e.g. <rootFolder>.</rootFolder>

4. Added SmartyWrapper class for using Smarty template engine, 
   instead of the built-in Eocene template engine.
   Please review howToUseSmarty.txt for more information on using Smarty with Eocene.
   The manual does not cover the smarty usage.

6. Search engine safe url
   e.g. .../receiver.php/command/param1/value1/param2/value2 

7. Added a library class PearDBWrapper for using database classes from PEAR.

8. Added an optional appSettings node in config file. It can be accessed from $fc->appSettings

9. Now there is support for separating your strings and using multiple languages.
   All eocene generated errors are separated and placed in the file eoceneStrings.txt in eocene directory.
   To define your default language, change the global variable $eoceneLanguage in the receiver.
   You should not add your own strings for errors and messages in this file. If you want to handle your 
   messages (errors or otherwise), please read User Defiend Language File seection. 
   However, if a language does not exist in the eoceneStrings.txt file for Eocene generated error messages, 
   you are welcome to translate the entire suite of eocene generated messages in your preferred language 
   and add the strings for that language in eoceneStrings.txt. If you do so, please post the language strings 
   in the forum at http://www.eocene.net so that we can include your modifications in our next release.
   The language strings in the eoceneStrings.txt file are in the format
        messageString can contain variables that are in sprintf format.

   You can still keep using $fc->writeError(aMessageString). It will display an error page with aMessageString.
   However, if you want to separate your strings (errors and messages), you should define a user language file.
   The location of this file should specified in a node, <langFile>, as a child of the node <appSettings>.
   The location of user defined language file should be relative with respect to <rootFolder>.
   Once you setup your language file, you can place your errors and message strings in the file using messageIDs
   starting from 10000. The format of the user language file is
        messageString can contain variables tat are sprintf format.
   Once you setup your language file, you can use 
        The variable length parameter values will be used to perform sprintf on messageString in the user defined
        language file.
        You can also get a string defined in the language file using:

10. You can get the front controller instance using theController=&FrontController::instance().
    You can, however, still use the global $fc to get the front controller instance.

Return current item: Eocene (PHP Version)