Documentation
Fuel supports a wide variety of configurations. Sometimes the configuration needs some work in order to work properly. Listed below are a couple of scenarios that may pop up when setting up Fuel on your machine.
When your problem is not listed below or is listed but no proper solution is provided, please report this at the issue tracker ( http://dev.fuelphp.com ).
When your HTTP server has insufficient permissions to follow symbolic links around the filesystem.
Check the .htaccess file and modify the following line
Option +FollowSymLinksso that it reads:
Option +SymLinksIfOwnerMatchParse error: syntax error, unexpected T_FUNCTION, expecting ')' in /Users/info/Sites/fuel/public/index.php on line 9When running Fuel on a PHP version prior to 5.3.
Check the phpinfo(); in a separate testfile and see if you're running 5.3 or higher. More info on requirements is here.
When developing locally, update your server to the latest version of PHP 5.3. If you are not developing locally you'll need to ask your hosting company. Versions of PHP below 5.3 have lost support not just by us, but by PHP themselves.
Under unknown circumstances when using multibyte support.
This seems to be a PHP bug, for which at the time of writing no fix has been released. Most people using PHP 5.3.x and multi-byte support don't report this issue. We have not seen reports of users with PHP 5.4.x that experience this same error.
As a workaround, it is suggested to disable zend-multibyte and mbstring, or try using a different version of PHP.
On some php installations it's necessary to add a question-mark in the .htaccess file after index.php
Add the question-mark like so:
# Turn on URL rewriting
RewriteEngine On
# Installation directory
RewriteBase /
# If fuel is not a level up
# RewriteBase /public
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?/$1 [L]
# Notice the ? after index.php
Some fcgi installations require a variant of this solution:
RewriteRule ^(.*)$ index.php?$1 [L]
# Notice the fact that the slash has been removed after the ?
#Other possible setups:
RewriteRule ^(.*)$ /index.php/$1 [L]
# Notice the leading slash added before index.php
mysql_connect(): [2002] No such file or directory (trying to connect via unix:///var/mysql/mysql.sock) in /Users/phil/Sites/fuel/fuel/core/classes/database/mysql/connection.php on 73Happens when you try to interact with the database via the command line, often when using MAMP for your MySQL server. The reason for this is that PHP-CLI is a different installation to the MAMP provided by MAMP, so PHP knows nothing of the database server.
Note: Before performing the following step to fix the problem, verify the database connection via normal browser access.
Change "localhost" to "127.0.0.1" in your database.php
Failing that:Create a symlink pointing at MAMP's mysql.socket.
$ sudo ln -s /Applications/MAMP/tmp/mysql/mysql.sock /var/mysql/mysql.sockIn some cases you have to create the directory first:
$ sudo mkdir /var/mysql
$ sudo ln -s /Applications/MAMP/tmp/mysql/mysql.sock /var/mysql/mysql.sockFuel has a security measure called "output encoding" which is switched on by default. This means that any value passed to the View or Presenter is considered dangerous unless you explicitly mark it as safe. All values that aren't safe will be put through htmlentities, including the contents of arrays and the properties of objects.
Learn more about security in the View class.
Orm\Exception [ Error ]: Listing columns not failed, you have to set the model properties with a static $_properties setting in the model.Working with ORM models when not connecting via mysql.
Make sure the db config values are correct and test your database connection.
Update the model to contain the properties.
protected static $_properties = array('id', 'title', 'contents', 'publish');Or set the change the db type to "mysql" in APPATH/config/db.php
That is because your path is not defined correctly, the Asset class uses a path relative to index.php.
To fix that you have to modify the app/config/asset.php to set the correct path. Notice in index.php that a constant named DOCROOT is being defined:
define('DOCROOT', __DIR__.DIRECTORY_SEPARATOR);You can use that in app/config/asset.php. This will set the asset path back to the default folder DOCROOT/public/assets, where the subfolders for css/ img/ and js/ are located:
'paths' => array(DOCROOT.'public/assets/'),This my happen because in DOCROOT/index.php, realpath() is used to deal with relative paths, which will cache path information, including the symlink.
To fix that you have to modify the DOCROOT/index.php and use clearstatcache() for each of the paths containing a symlink to clear the cache. Alternatively, you can reload your webserver to clear the path cache. You can not manually issue the clearstatcache() command, since it is cached per thread, and issuing the command will only clear the cache for the current thread.
The cause of this message is that an error occured while PHP is already in its tear-down phase, and no error handler is available anymore.
There are a lot of reasons why this can happen. We'll try do document the most obvious ones here: