Installing Magento on a Godaddy Web Hosting Account

Updated: Sun, 07/17/2013 - 00:34

After reading about how difficult it is to install Magento on a Godaddy standard web hosting account, I decided to give it a shot. At first, I thought this would be a breeze, but I was amazed at how difficult it truly is due to all the files that have to be edited. This was actually my first time playing around with Magento and I was quite disappointed to say the least.

For years I have been using osCommerce and Magento is much slower because of the way the code was written. Therefore, if you are planning to run a Magento powered store on Godaddy, know that an economy web hosting plan isn't really powerful enough to handle it. Godaddy actually recommends a virtual dedicated or dedicated server for use with Magento, but that decision is of course up to you.

Either way, the video below proves that it's possible to install Magento (community edition) on an economy web hosting account from Godaddy even though many people say it's not. Please see the video below and the step by step written tutorial beneath it:

Can't view the video? Watch it on YouTube

Download the files below:

Magento download the one with the tar.gz extension (You will need to create an account with them if you don't already have one).

Try to download the tar.gz file because this way we can upload just 1 single file and then unarchive.

If you are on a Mac as I am, click Safari then preferences then General and untick the Open "safe" files after downloading option.

If using Internet Explorer check whether the files are automatically unarchived upon downloading. If they do get unarchived, adjust your settings so that the file remains archived.

Now download FileZilla because Godaddy's web based FTP client will probably timeout while uploading the file.

FileZilla this is the FTP client that I use in the video. If you use a different FTP client, Dreamweaver or other web development software it's fine.


Make sure your Godaddy hosting account is running Linux because it is one of the Magento requirements.

Begin the installation process:

Now log into your Godaddy account, go to the web hosting section and choose the account that you will be uploading Magento to.

Next (once on the hosting control panel), copy the IP address in the server details section because we will need to populate the host field in FileZilla with this information.

Now install FileZilla if you haven't already. Once installed, open FileZilla and paste the IP address from the server section in the host field.

Also fill in the Username field and Password field associated with your web hosting account and then click Quickconnect.

Once logged in, find the Magento file that you downloaded and double click it so that we move it to our web hosting account.

I used the web based FTP file manager that Godaddy provides to move, create and edit files. Of course if you're using Dreamweaver or another web development program, you can use that.

Create a PHP file to check your server's specs:

Now we create a PHP file name "info.php" and paste the code below into it:

<?php echo phpinfo();?>

Next we go to your store's web address and access this file by going to:

This screen will show the server specs for your hosting account. Check whether the servers meets Magento's requirements.

Unarchive the Magento file:

Now we unarchive the Magento file that we just uploaded by ticking the box next to the Magento file and clicking the Unarchive button (icon) -- we will be unarchiving this file into the root directory of our web hosting account.

After the file has been unarchived you will see a new directory which is named "magento" -- this directory contains our Magento installation.

After you have unarchived the files, you can delete the archived file if you'd like.

Move the Magento files to the root directory:

Since we will be installing Magento into the root directory of our web hosting account, we need to move all the files from within the Magento directory to the root directory.

You can do this by going into the Magento directory and ticking every file within it and then click move.

If you do not do this, people will access your store by going to rather than

If there is a prompt asking you whether to replace some files, click yes -- double check whether these files are of importance to you.

After you have moved all the files you can delete the Magento directory.

Configure your hosting account:

Next, we copy the contents of the php.ini.sample file that is in the root directory of our hosting account and paste the contents into the php.ini file.

You can paste this information beneath the last line of code in the php.ini file.

Also change the allow_url_fopen option in the php.ini file from off to on.

Edit the upload_tmp_dir from /tmp to the path of your web hosting account with the directories /media/tmp appended to the end. In the video I show you how to find this info.

You can find it by visiting your webstore and look for a path that looks something like this: /home/content/y/o/u/yourusername/html/

You can also get this path by going to Godaddy control panel and in the server details section, look for the absolute hosting path section (you may need to click show details to view this section) and copy that path.

You will basically see that the path contains the root directory of your web hosting account. In my case it was html so the new path for upload_tmp_dir looked something like: /home/content/y/o/u/yourusername/html/media/tmp

Therefore, your ini.php file would look something like:

upload_tmp_dir = /home/content/y/o/u/yourusername/html/media/tmp

Also, you might need to add cgi.fix_pathinfo = 1 to the php.ini file.

Of course, if you get any errors during the installation processes, try to remove the cgi.fix_pathinfo = 1 line, wait a few minutes for the changes to take effect and try installing again.

In the php.ini file I turned zlib.output_compression from on to off, but you can leave it on if you wish. I basically turned it off because I feel the web hosting account isn't powerful enough to handle compression.

Afterwards rename the php.ini file to php5.ini

Next, we need to wait for the changes to take effect and this can take 10-20 minutes.

A good way to check is by accessing your info.php file again by visiting and looking in the upload_tmp_dir section and checking whether the output reflects the changes that we just made above.

Next we tick the box next to .htaccess file and click edit.

In the ## GoDaddy specific options section you will see the line #Option -MultViews

While many say that this line needs to be uncommented, from my experience, uncommenting creates errors. So try to leave it commented.

However, if you do experience errors during the installation process, try to remove the # (hash tag) next to Option -MultViews and try the installation process again. 

Now in the section #RewriteBase /magento/

We remove the # (hash tag) and rename /magento/ to / 

We do this because in this tutorial we are installing Magento in the root directory. Of course if you are installing Magento in a subdirectory, you will want to rename /magento/ to the name of the subdirectory or leave it as /magento/ if that is the name of your subdirectory. 

Next we need to go back to our FTP manager and add the directory tmp within the Magento "media" directory.

Make sure that the tmp directory is writeable by ticking it and clicking the Permissions button (icon) -- make sure all the permission options in "Advanced Permissions" are ticked off and click ok.

Begin the installation process:

Now we begin the install by going to:

If the installation wizard appears, we did everything correctly.

If you are getting a blank page with a "no file input specified" message, that means that either the changes to our php5.ini file haven't taken effect or our configuration is wrong.

As mentioned earlier you can try to comment or uncomment the "Option -MultViews" line in .htaccess or remove or add the cgi.fix_pathinfo = 1 line in php5.ini.

Create your MYSQL database:

Next we create a MYSQL database.

Go back to the Godaddy FTP manager and hover over Databases and click the MYSQL link.

Now we click "add one now" and populate the required fields.

Next we click "ok" and wait for the database to be setup.

Once the database has been setup, we click the actions button and then "Details" and you will see a popup. In that popup look for the hostname section and copy that URL and paste it into the host field of our Magento installation wizard.

Next fill in the "Database Name", "User Name" and "User Password" fields with your databases' information.

Resume the installation with the Magento installation wizard:

In the Web access options section I ticked off "Use Web Server (Apache) Rewrites" because I wanted search engine friendly URLs.

If you have an SSL certificate also tick off the box next to "Use Secure URLs (SSL)".

If you want the admin to run with SSL you tick off the box next to "Run admin interface with SSL".

For the "Session Storage Options" I have it setup as "File System", if you want the session data stored in your MYSQL database, you choose the "Database" option.

Of course with the "Database" option, your store might run slower if the database isn't properly maintained (optimized).

On the next screen you create an admin account for your Magento installation -- just fill in the required information.

Also read the Installation Guide which tells you which directories need to be writeable.

The URL to this guide is: 

This guide basically tells us that the following directories and files need to be writeable:

  • var
  • var/.htaccess
  • app/etc
  • media and all the directories within the media directory 

Again this can be done by ticking off the boxes next to the desired directories and clicking the Permissions button (icon), and ticking off all the boxes within the permissions section and clicking ok.

Next click continue -- at this point, everything should have been installed. Copy the encryption key and hold onto it. Now go to the admin section by clicking the "Go to Backend" button and log in.

Image error fix:

Now when you upload images you might receive an "Internal Server Error" message when you try to view any of your product images. The .htaccess file within the "media" directory is causing this issue.

You basically want to edit that file by going to the Godaddy FTP file manager and ticking off the box next to the .htaccess file within the media folder, click edit and comment out the line:

Options All -Indexes 

Once commented, it should look like the example below:

#Options All -Indexes

Now click save and close.

Try to speed up Magento:

Note: This sort of contradicts what I said about turning zlib.output_compression off in the php5.ini file because by uncommenting the lines below, you are actually enabling compression.

Also if you have zlib.output_compression turned on in your php5.ini file, you don't need to uncomment the first line of code below:

Edit the .htaccess file by going to the Godaddy FTP manager, tick the box next to .htaccess file and click edit. and remove the # (hash tags) next to:

php_flag zlib.output_compression on

SetOutputFilter DEFLATE

BrowserMatch ^Mozilla/4 gzip-only-text/html

BrowserMatch ^Mozilla/4\.0[678] no-gzip

BrowserMatch \bMSIE !no-gzip !gzip-only-text/html

SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip dont-vary

Header append Vary User-Agent env=!dont-vary

Basically, you'll want to check your store's performance with compression enabled as well as disabled. From my experience, compressing data makes the server work harder and when there are limited resources available, this can be an issue.

Now you should be good to go! Enjoy!

Ed requested that I add my php5.ini configuration so I did below:

Note: that you may need to update your upload_tmp_dir to the full path of your tmp directory as I mentioned in the "configure your hosting account" section of this article. I also left "zlib.output_compression" on because it's not necessary to turn it off. Also note that SMTP will differ from my example below based on your server settings.

register_globals = off

allow_url_fopen = on

expose_php = Off

max_input_time = 60

variables_order = "EGPCS"

extension_dir = ./

upload_tmp_dir = /tmp

precision = 12


url_rewriter.tags = "a=href,area=href,frame=src,input=src,form=,fieldset="

;Only uncomment zend optimizer lines if your application requires Zend Optimizer support







;-- Be very careful to not to disable a function which might be needed!

;-- Uncomment the following lines to increase the security of your PHP site.

;disable_functions = "highlight_file,ini_alter,ini_restore,openlog,passthru,

;phpinfo, exec, system, dl, fsockopen, set_time_limit,

;popen, proc_open, proc_nice,shell_exec,show_source,symlink"

;This file is for CGI/FastCGI installations.

;Try copying it to php5.ini, if it doesn't work

;adjust memory limit

memory_limit = 64M

max_execution_time = 18000

;disable magic quotes for php request vars

magic_quotes_gpc = off

;disable automatic session start

;before autoload was initialized

flag session.auto_start = off

;enable resulting html compression

zlib.output_compression = on

;disable user agent verification to not break multiple image upload

suhosin.session.cryptua = off

;turn off compatibility with PHP4 when dealing with objects

zend.ze1_compatibility_mode = off

;PHP for some reason ignores this setting in system php.ini

;and disables mcrypt if this line is missing in local php.ini

cgi.fix_pathinfo = 1

At this point your Magento store should be up and running. Now if you'd like to customize your new store, you may be interested in my video which shows you how to install a new theme in Magento and if you'd like to look at some themes, you can check out my list of Magento 1.7.x.x themes over here.


JACK's picture

actually i am a very new to this website stuff ,would like to try it myself, so learn a lots from your video, it was working perfect for me ,anyhow thank you for your video that really helps me went through all of the magento installation on godaddy shared server.
As you mentioned ,shared server is too slow for magento ,actually i am trying to move on to godaddy virtual private server, and i was using the same steps ,but it wasn't working on virtual private server ,it always show me PHP extension "mcrypt" must be loaded. on the magento installation wizard ,any help or do you have a video that can show me step by step to install magento into godaddy VPS thanks a lot !!
Danny's picture

First off thanks for stopping by and I'm glad my video helped you. Magento is a resource hog and a VPS is definitely a good route to take.

I was actually going to do a video on installing Magento on a private server, but that would require me to rent a server for a month and I haven't decided if I'm willing to do this LOL. I do have a dedicated server now, but I can't play around with it because it's currently occupied by one of my websites.

See the main problems with private servers is that they have basic configurations. Godaddy shared hosting servers are configured by Godaddy so that they are compatible with various applications because we don't have access to the server's system files on those plans.

Installing mcrypt isn't too difficult, but you need to do it through SSH. You can use PuTTY which can be found here:

Once you have connected to your server through PuTTY (you need your IP address,user id and password) you need to switch to root user by typing:

su root

then type:

yum install mcrypt*
yum install mhash*

and answer y to the prompts.

then enter:

yum install php-mcrypt*
yum install php-mhash*

Answer y to the prompts and then you will want to restart the server and you can do this with:

/etc/init.d/httpd restart

I don't know if the path in the command is correct on your server so you can also restart through your Godaddy control panel by clicking request power cycle in the support section.

Also remember to modify the php.ini file as well and maybe the httpd.conf file.

The php.ini file on a VPS is typically located in:



httpd.conf is typically in


or you can use "locate httpd.conf" in ssh to find it.

Also, so that you can upload images, remember to set your folder permissions so that they are writeable by Magento.

Good luck and if you run into any other issues, just let me know.
Ed Sparks's picture

Please post the entire php5.ini file in its entirety.
Danny's picture

I added the contents of my php5.ini file in the article. Please note that some variables require different values based on your server's configuration which is why I was hesitant of adding the file contents to the article.
kevin's picture

Hi Danny,

Every link clicked takes me to the Internal Server Error page. Even /admin.
Kevin's picture

Followed the directions completely and got to the LAST step of adding the product. When trying to test the category by clicking on Test Cat, I got Internal Servor Error.

Please Help!
Danny's picture

Since you managed to get that far, I wouldn't be too worried if I were you. Based on the error, I can only assume that something is wrong with your .htaccess file. Make sure that the configuration on that file is correct. I think it has something to do with the URL rewrites, so again, make sure that the file is correct. To do this, I would just replace the contents of the existing file with the contents of an unedited Magento .htaccess file and follow the steps over again.

If that doesn't work, check your php.ini file again. Other than this, I can't see it being anything else as long as you are hosted with Godaddy because we are all pretty much setup the same way with them.
Suraj's picture

Completed installtion but images are broken and to solve that, as per your tutorial, i could able to find Options All -Indexes to comment, i have installed magento on Godaddy Ultimate-Linux Hosting Package.

My Php5.ini file is as bellow:
;; NOTE: installed/managed by puppet on hostingcms02

; About php.ini ;
; This file controls many aspects of PHP's behavior. In order for PHP to
; read it, it must be named 'php.ini'. PHP looks for it in the current
; working directory, in the path designated by the environment variable
; PHPRC, and in the path that was defined in compile time (in that order).
; Under Windows, the compile-time path is the Windows directory. The
; path in which the php.ini file is looked for can be overridden using
; the -c argument in command line mode.
; The syntax of the file is extremely simple. Whitespace and Lines
; beginning with a semicolon are silently ignored (as you probably guessed).
; Section headers (e.g. [Foo]) are also silently ignored, even though
; they might mean something in the future.
; Directives are specified using the following syntax:
; directive = value
; Directive names are *case sensitive* - foo=bar is different from FOO=bar.
; The value can be a string, a number, a PHP constant (e.g. E_ALL or M_PI), one
; of the INI constants (On, Off, True, False, Yes, No and None) or an expression
; (e.g. E_ALL & ~E_NOTICE), or a quoted string ("foo").
; Expressions in the INI file are limited to bitwise operators and parentheses:
; | bitwise OR
; & bitwise AND
; ~ bitwise NOT
; ! boolean NOT
; Boolean flags can be turned on using the values 1, On, True or Yes.
; They can be turned off using the values 0, Off, False or No.
; An empty string can be denoted by simply not writing anything after the equal
; sign, or by using the None keyword:
; foo = ; sets foo to an empty string
; foo = none ; sets foo to an empty string
; foo = "none" ; sets foo to the string 'none'
; If you use constants in your value, and these constants belong to a
; dynamically loaded extension (either a PHP extension or a Zend extension),
; you may only use these constants *after* the line that loads the extension.
; About this file ;
; This is the recommended, PHP 5-style version of the php.ini-dist file. It
; sets some non standard settings, that make PHP more efficient, more secure,
; and encourage cleaner coding.
; The price is that with these settings, PHP may be incompatible with some
; applications, and sometimes, more difficult to develop with. Using this
; file is warmly recommended for production sites. As all of the changes from
; the standard settings are thoroughly documented, you can go over each one,
; and decide whether you want to use it or not.
; For general information about the php.ini file, please consult the php.ini-dist
; file, included in your PHP distribution.
; This file is different from the php.ini-dist file in the fact that it features
; different values for several directives, in order to improve performance, while
; possibly breaking compatibility with the standard out-of-the-box behavior of
; PHP. Please make sure you read what's different, and modify your scripts
; accordingly, if you decide to use this file instead.
; - register_globals = Off [Security, Performance]
; Global variables are no longer registered for input data (POST, GET, cookies,
; environment and other server variables). Instead of using $foo, you must use
; you can use $_REQUEST["foo"] (includes any variable that arrives through the
; request, namely, POST, GET and cookie variables), or use one of the specific
; $_GET["foo"], $_POST["foo"], $_COOKIE["foo"] or $_FILES["foo"], depending
; on where the input originates. Also, you can look at the
; import_request_variables() function.
; Note that register_globals is going to be depracated (i.e., turned off by
; default) in the next version of PHP, because it often leads to security bugs.
; Read for further
; information.
; - register_long_arrays = Off [Performance]
; Disables registration of the older (and deprecated) long predefined array
; variables ($HTTP_*_VARS). Instead, use the superglobals that were
; introduced in PHP 4.1.0
; - display_errors = Off [Security]
; With this directive set to off, errors that occur during the execution of
; scripts will no longer be displayed as a part of the script output, and thus,
; will no longer be exposed to remote users. With some errors, the error message
; content may expose information about your script, web server, or database
; server that may be exploitable for hacking. Production sites should have this
; directive set to off.
; - log_errors = On [Security]
; This directive complements the above one. Any errors that occur during the
; execution of your script will be logged (typically, to your server's error log,
; but can be configured in several ways). Along with setting display_errors to off,
; this setup gives you the ability to fully understand what may have gone wrong,
; without exposing any sensitive information to remote users.
; - output_buffering = 4096 [Performance]
; Set a 4KB output buffer. Enabling output buffering typically results in less
; writes, and sometimes less packets sent on the wire, which can often lead to
; better performance. The gain this directive actually yields greatly depends
; on which Web server you're working with, and what kind of scripts you're using.
; - register_argc_argv = Off [Performance]
; Disables registration of the somewhat redundant $argv and $argc global
; variables.
; - magic_quotes_gpc = Off [Performance]
; Input data is no longer escaped with slashes so that it can be sent into
; SQL databases without further manipulation. Instead, you should use the
; function addslashes() on each input element you wish to send to a database.
; - variables_order = "GPCS" [Performance]
; The environment variables are not hashed into the $_ENV. To access
; environment variables, you can use getenv() instead.
; - error_reporting = E_ALL [Code Cleanliness, Security(?)]
; By default, PHP surpresses errors of type E_NOTICE. These error messages
; are emitted for non-critical errors, but that could be a symptom of a bigger
; problem. Most notably, this will cause error messages about the use
; of uninitialized variables to be displayed.
; - allow_call_time_pass_reference = Off [Code cleanliness]
; It's not possible to decide to force a variable to be passed by reference
; when calling a function. The PHP 4 style to do this is by making the
; function require the relevant argument by reference.

; Language Options ;

; Enable the PHP scripting language engine under Apache.
engine = On

; Enable compatibility mode with Zend Engine 1 (PHP 4.x)
zend.ze1_compatibility_mode = Off

; Allow the tags are recognized.
; NOTE: Using short tags should be avoided when developing applications or
; libraries that are meant for redistribution, or deployment on PHP
; servers which are not under your control, because short tags may not
; be supported on the target server. For portable, redistributable code,
; be sure not to use short tags.
short_open_tag = On

; Allow ASP-style <% %> tags.
asp_tags = Off

; The number of significant digits displayed in floating point numbers.
precision = 14

; Enforce year 2000 compliance (will cause problems with non-compliant browsers)
y2k_compliance = On

; Output buffering allows you to send header lines (including cookies) even
; after you send body content, at the price of slowing PHP's output layer a
; bit. You can enable output buffering during runtime by calling the output
; buffering functions. You can also enable output buffering for all files by
; setting this directive to On. If you wish to limit the size of the buffer
; to a certain size - you can use a maximum number of bytes instead of 'On', as
; a value for this directive (e.g., output_buffering=4096).
output_buffering = Off

; You can redirect all of the output of your scripts to a function. For
; example, if you set output_handler to "mb_output_handler", character
; encoding will be transparently converted to the specified encoding.
; Setting any output handler automatically turns on output buffering.
; Note: People who wrote portable scripts should not depend on this ini
; directive. Instead, explicitly set the output handler using ob_start().
; Using this ini directive may cause problems unless you know what script
; is doing.
; Note: You cannot use both "mb_output_handler" with "ob_iconv_handler"
; and you cannot use both "ob_gzhandler" and "zlib.output_compression".
; Note: output_handler must be empty if this is set 'On' !!!!
; Instead you must use zlib.output_handler.
;output_handler =

; Transparent output compression using the zlib library
; Valid values for this option are 'off', 'on', or a specific buffer size
; to be used for compression (default is 4KB)
; Note: Resulting chunk size may vary due to nature of compression. PHP
; outputs chunks that are few hundreds bytes each as a result of
; compression. If you prefer a larger chunk size for better
; performance, enable output_buffering in addition.
; Note: You need to use zlib.output_handler instead of the standard
; output_handler, or otherwise the output will be corrupted.
zlib.output_compression = Off

; You cannot specify additional output handlers if zlib.output_compression
; is activated here. This setting does the same as output_handler but in
; a different order.
;zlib.output_handler =

; Implicit flush tells PHP to tell the output layer to flush itself
; automatically after every output block. This is equivalent to calling the
; PHP function flush() after each and every call to print() or echo() and each
; and every HTML block. Turning this option on has serious performance
; implications and is generally recommended for debugging purposes only.
implicit_flush = Off

; The unserialize callback function will be called (with the undefined class'
; name as parameter), if the unserializer finds an undefined class
; which should be instantiated.
; A warning appears if the specified function is not defined, or if the
; function doesn't include/implement the missing class.
; So only set this entry, if you really want to implement such a
; callback-function.

; When floats & doubles are serialized store serialize_precision significant
; digits after the floating point. The default value ensures that when floats
; are decoded with unserialize, the data will remain the same.
serialize_precision = 100

; Whether to enable the ability to force arguments to be passed by reference
; at function call time. This method is deprecated and is likely to be
; unsupported in future versions of PHP/Zend. The encouraged method of
; specifying which arguments should be passed by reference is in the function
; declaration. You're encouraged to try and turn this option Off and make
; sure your scripts work properly with it in order to ensure they will work
; with future versions of the language (you will receive a warning each time
; you use this feature, and the argument will be passed by value instead of by
; reference).
allow_call_time_pass_reference = Off

; Safe Mode
safe_mode = Off

; By default, Safe Mode does a UID compare check when
; opening files. If you want to relax this to a GID compare,
; then turn on safe_mode_gid.
safe_mode_gid = Off

; When safe_mode is on, UID/GID checks are bypassed when
; including files from this directory and its subdirectories.
; (directory must also be in include_path or full path must
; be used when including)
safe_mode_include_dir = "~"

; When safe_mode is on, only executables located in the safe_mode_exec_dir
; will be allowed to be executed via the exec family of functions.
safe_mode_exec_dir =

; Setting certain environment variables may be a potential security breach.
; This directive contains a comma-delimited list of prefixes. In Safe Mode,
; the user may only alter environment variables whose names begin with the
; prefixes supplied here. By default, users will only be able to set
; environment variables that begin with PHP_ (e.g. PHP_FOO=BAR).
; Note: If this directive is empty, PHP will let the user modify ANY
; environment variable!
safe_mode_allowed_env_vars = PHP_ LANG LANG_

; This directive contains a comma-delimited list of environment variables that
; the end user won't be able to change using putenv(). These variables will be
; protected even if safe_mode_allowed_env_vars is set to allow to change them.
safe_mode_protected_env_vars = LD_LIBRARY_PATH

; open_basedir, if set, limits all file operations to the defined directory
; and below. This directive makes most sense if used in a per-directory
; or per-virtualhost web server configuration file. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
;open_basedir =

; This directive allows you to disable certain functions for security reasons.
; It receives a comma-delimited list of function names. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
disable_functions =

; This directive allows you to disable certain classes for security reasons.
; It receives a comma-delimited list of class names. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
disable_classes =

; Colors for Syntax Highlighting mode. Anything that's acceptable in
; would work.
;highlight.string = #DD0000
;highlight.comment = #FF9900
;highlight.keyword = #007700
;highlight.default = #0000BB
;highlight.html = #000000

; If enabled, the request will be allowed to complete even if the user aborts
; the request. Consider enabling it if executing long request, which may end up
; being interrupted by the user or a browser timing out.
; ignore_user_abort = On

; Misc
; Decides whether PHP may expose the fact that it is installed on the server
; (e.g. by adding its signature to the Web server header). It is no security
; threat in any way, but it makes it possible to determine whether you use PHP
; on your server or not.
expose_php = Off

; Resource Limits ;

max_execution_time = 30 ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
memory_limit = 64M ; Maximum amount of memory a script may consume (8MB)

; Error handling and logging ;

; error_reporting is a bit-field. Or each number up to get desired error
; reporting level
; E_ALL - All errors and warnings (doesn't include E_STRICT)
; E_ERROR - fatal run-time errors
; E_WARNING - run-time warnings (non-fatal errors)
; E_PARSE - compile-time parse errors
; E_NOTICE - run-time notices (these are warnings which often result
; from a bug in your code, but it's possible that it was
; intentional (e.g., using an uninitialized variable and
; relying on the fact it's automatically initialized to an
; empty string)
; E_STRICT - run-time notices, enable to have PHP suggest changes
; to your code which will ensure the best interoperability
; and forward compatibility of your code
; E_CORE_ERROR - fatal errors that occur during PHP's initial startup
; E_CORE_WARNING - warnings (non-fatal errors) that occur during PHP's
; initial startup
; E_COMPILE_ERROR - fatal compile-time errors
; E_COMPILE_WARNING - compile-time warnings (non-fatal errors)
; E_USER_ERROR - user-generated error message
; E_USER_WARNING - user-generated warning message
; E_USER_NOTICE - user-generated notice message
; Examples:
; - Show all errors, except for notices and coding standards warnings
;error_reporting = E_ALL & ~E_NOTICE
; - Show all errors, except for notices
;error_reporting = E_ALL & ~E_NOTICE | E_STRICT
; - Show only errors
; - Show all errors, except coding standards warnings
error_reporting = E_ALL & ~E_NOTICE

; Print out errors (as a part of the output). For production web sites,
; you're strongly encouraged to turn this feature off, and use error logging
; instead (see below). Keeping display_errors enabled on a production web site
; may reveal security information to end users, such as file paths on your Web
; server, your database schema or other information.
display_errors = On

; Even when display_errors is on, errors that occur during PHP's startup
; sequence are not displayed. It's strongly recommended to keep
; display_startup_errors off, except for when debugging.
display_startup_errors = Off

; Log errors into a log file (server-specific log, stderr, or error_log (below))
; As stated above, you're strongly advised to use error logging in place of
; error displaying on production web sites.
log_errors = Off

; Set maximum length of log_errors. In error_log information about the source is
; added. The default is 1024 and 0 allows to not apply any maximum length at all.
log_errors_max_len = 1024

; Do not log repeated messages. Repeated errors must occur in same file on same
; line until ignore_repeated_source is set true.
ignore_repeated_errors = Off

; Ignore source of message when ignoring repeated messages. When this setting
; is On you will not log errors with repeated messages from different files or
; sourcelines.
ignore_repeated_source = Off

; If this parameter is set to Off, then memory leaks will not be shown (on
; stdout or in the log). This has only effect in a debug compile, and if
; error reporting includes E_WARNING in the allowed list
report_memleaks = On

; Store the last error/warning message in $php_errormsg (boolean).
track_errors = Off

; Disable the inclusion of HTML tags in error messages.
; Note: Never use this feature for production boxes.
;html_errors = Off

; If html_errors is set On PHP produces clickable error messages that direct
; to a page describing the error or function causing the error in detail.
; You can download a copy of the PHP manual from
; and change docref_root to the base URL of your local copy including the
; leading '/'. You must also specify the file extension being used including
; the dot.
; Note: Never use this feature for production boxes.
;docref_root = "/phpmanual/"
;docref_ext = .html

; String to output before an error message.
;error_prepend_string = ""

; String to output after an error message.
;error_append_string = ""

; Log errors to specified file.
;error_log = filename

; Log errors to syslog (Event Log on NT, not valid in Windows 95).
;error_log = syslog

; Data Handling ;
; Note - track_vars is ALWAYS enabled as of PHP 4.0.3

; The separator used in PHP generated URLs to separate arguments.
; Default is "&".
;arg_separator.output = "&"

; List of separator(s) used by PHP to parse input URLs into variables.
; Default is "&".
; NOTE: Every character in this directive is considered as separator!
;arg_separator.input = ";&"

; This directive describes the order in which PHP registers GET, POST, Cookie,
; Environment and Built-in variables (G, P, C, E & S respectively, often
; referred to as EGPCS or GPC). Registration is done from left to right, newer
; values override older values.
variables_order = "GPCS"

; Whether or not to register the EGPCS variables as global variables. You may
; want to turn this off if you don't want to clutter your scripts' global scope
; with user data. This makes most sense when coupled with track_vars - in which
; case you can access all of the GPC variables through the $HTTP_*_VARS[],
; variables.
; You should do your best to write your scripts so that they do not require
; register_globals to be on; Using form variables as globals can easily lead
; to possible security problems, if the code is not very well thought of.
register_globals = Off

; Whether or not to register the old-style input arrays, HTTP_GET_VARS
; and friends. If you're not using them, it's recommended to turn them off,
; for performance reasons.
register_long_arrays = Off

; This directive tells PHP whether to declare the argv&argc variables (that
; would contain the GET information). If you don't use these variables, you
; should turn it off for increased performance.
register_argc_argv = On

; When enabled, the SERVER and ENV variables are created when they're first
; used (Just In Time) instead of when the script starts. If these variables
; are not used within a script, having this directive on will result in a
; performance gain. The PHP directives register_globals, register_long_arrays,
; and register_argc_argv must be disabled for this directive to have any affect.
auto_globals_jit = On

; Maximum size of POST data that PHP will accept.
post_max_size = 33M

; Magic quotes

; Magic quotes for incoming GET/POST/Cookie data.
magic_quotes_gpc = On

; Magic quotes for runtime-generated data, e.g. data from SQL, from exec(), etc.
magic_quotes_runtime = Off

; Use Sybase-style magic quotes (escape ' with '' instead of \').
magic_quotes_sybase = Off

; Automatically add files before or after any PHP document.
auto_prepend_file =
auto_append_file =

; As of 4.0b4, PHP always outputs a character encoding by default in
; the Content-type: header. To disable sending of the charset, simply
; set it to be empty.
; PHP's built-in default is text/html
default_mimetype = "text/html"
;default_charset = "iso-8859-1"

; Always populate the $HTTP_RAW_POST_DATA variable.
;always_populate_raw_post_data = On

; Paths and Directories ;

; UNIX: "/path1:/path2"
;include_path = ".:/php/includes"
; Windows: "\path1;\path2"
;include_path = ".;c:\php\includes"

; The root of the PHP pages, used only if nonempty.
; if PHP was not compiled with FORCE_REDIRECT, you SHOULD set doc_root
; if you are running php as a CGI under any web server (other than IIS)
; see documentation for security issues. The alternate is to use the
; cgi.force_redirect configuration below
doc_root =

; The directory under which PHP opens the script using /~username used only
; if nonempty.
user_dir =

; Directory in which the loadable extensions (modules) reside.
extension_dir = "./"

; Whether or not to enable the dl() function. The dl() function does NOT work
; properly in multithreaded servers, such as IIS or Zeus, and is automatically
; disabled on them.
enable_dl = On

; cgi.force_redirect is necessary to provide security running PHP as a CGI under
; most web servers. Left undefined, PHP turns this on by default. You can
; turn it off here AT YOUR OWN RISK
; **You CAN safely turn this off for IIS, in fact, you MUST.**
; cgi.force_redirect = 1

; if cgi.nph is enabled it will force cgi to always sent Status: 200 with
; every request.
; cgi.nph = 1

; if cgi.force_redirect is turned on, and you are not running under Apache or Netscape
; (iPlanet) web servers, you MAY need to set an environment variable name that PHP
; will look for to know it is OK to continue execution. Setting this variable MAY
; cause security issues, KNOW WHAT YOU ARE DOING FIRST.
; cgi.redirect_status_env = ;

; FastCGI under IIS (on WINNT based OS) supports the ability to impersonate
; security tokens of the calling client. This allows IIS to define the
; security context that the request runs under. mod_fastcgi under Apache
; does not currently support this feature (03/17/2002)
; Set to 1 if running under IIS. Default is zero.
; fastcgi.impersonate = 1;

; Disable logging through FastCGI connection
; fastcgi.log = 0

; cgi.rfc2616_headers configuration option tells PHP what type of headers to
; use when sending HTTP response code. If it's set 0 PHP sends Status: header that
; is supported by Apache. When this option is set to 1 PHP will send
; RFC2616 compliant header.
; Default is zero.
;cgi.rfc2616_headers = 0

; File Uploads ;

; Whether to allow HTTP file uploads.
file_uploads = On

; Temporary directory for HTTP uploaded files (will use system default if not
; specified).
upload_tmp_dir = /home/content/70/10866570/html/media/tmp

; Maximum allowed size for uploaded files.
upload_max_filesize = 32M

; Fopen wrappers ;

; Whether to allow the treatment of URLs (like http:// or ftp://) as files.
allow_url_fopen = On

; Define the anonymous ftp password (your email address)

; Define the User-Agent string
; user_agent="PHP"

; Default timeout for socket based streams (seconds)
default_socket_timeout = 60

; If your scripts have to deal with files from Macintosh systems,
; or you are running on a Mac and need to deal with files from
; unix or win32 systems, setting this flag will cause PHP to
; automatically detect the EOL character in those files so that
; fgets() and file() will work regardless of the source of the file.
; auto_detect_line_endings = Off

; Dynamic Extensions ;
; If you wish to have an extension loaded automatically, use the following
; syntax:
; extension=modulename.extension
; For example, on Windows:
; extension=msql.dll
; ... or under UNIX:
; Note that it should be the name of the module only; no directory information
; needs to go here. Specify the location of the extension with the
; extension_dir directive above.

; Windows Extensions
; Note that ODBC support is built in, so no dll is needed for it.
; Note that many DLL files are located in the extensions/ (PHP 4) ext/ (PHP 5)
; extension folders as well as the separate PECL DLL download (PHP 5).
; Be sure to appropriately set the extension_dir directive.



; Module Settings ;

; Defines the default timezone used by the date functions
date.timezone = America/Phoenix

; Whether or not to define the various syslog variables (e.g. $LOG_PID,
; $LOG_CRON, etc.). Turning it off is a good idea performance-wise. In
; runtime, you can define these variables by calling define_syslog_variables().
define_syslog_variables = Off

[mail function]
; For Win32 only.
smtp_port = 25

; For Win32 only.
;sendmail_from =

; For Unix only. You may supply arguments as well (default: "sendmail -t -i").
;sendmail_path =

; Force the addition of the specified parameters to be passed as extra parameters
; to the sendmail binary. These parameters will always replace the value of
; the 5th parameter to mail(), even in safe mode.
;mail.force_extra_parameters =

sql.safe_mode = Off

;odbc.default_db = Not yet implemented
;odbc.default_user = Not yet implemented
;odbc.default_pw = Not yet implemented

; Allow or prevent persistent links.
odbc.allow_persistent = On

; Check that a connection is still valid before reuse.
odbc.check_persistent = On

; Maximum number of persistent links. -1 means no limit.
odbc.max_persistent = -1

; Maximum number of links (persistent + non-persistent). -1 means no limit.
odbc.max_links = -1

; Handling of LONG fields. Returns number of bytes to variables. 0 means
; passthru.
odbc.defaultlrl = 4096

; Handling of binary data. 0 means passthru, 1 return as is, 2 convert to char.
; See the documentation on odbc_binmode and odbc_longreadlen for an explanation
; of uodbc.defaultlrl and uodbc.defaultbinmode
odbc.defaultbinmode = 1

; Allow or prevent persistent links.
mysql.allow_persistent = On

; Maximum number of persistent links. -1 means no limit.
mysql.max_persistent = -1

; Maximum number of links (persistent + non-persistent). -1 means no limit.
mysql.max_links = -1

; Default port number for mysql_connect(). If unset, mysql_connect() will use
; the $MYSQL_TCP_PORT or the mysql-tcp entry in /etc/services or the
; compile-time value defined MYSQL_PORT (in that order). Win32 will only look
mysql.default_port =

; Default socket name for local MySQL connects. If empty, uses the built-in
; MySQL defaults.
mysql.default_socket =

; Default host for mysql_connect() (doesn't apply in safe mode).
mysql.default_host =

; Default user for mysql_connect() (doesn't apply in safe mode).
mysql.default_user =

; Default password for mysql_connect() (doesn't apply in safe mode).
; Note that this is generally a *bad* idea to store passwords in this file.
; *Any* user with PHP access can run 'echo get_cfg_var("mysql.default_password")
; and reveal this password! And of course, any users with read access to this
; file will be able to reveal the password as well.
mysql.default_password =

; Maximum time (in secondes) for connect timeout. -1 means no limit
mysql.connect_timeout = 30

; Trace mode. When trace_mode is active (=On), warnings for table/index scans and
; SQL-Errors will be displayed.
mysql.trace_mode = Off


; Maximum number of links. -1 means no limit.
mysqli.max_links = -1

; Default port number for mysqli_connect(). If unset, mysqli_connect() will use
; the $MYSQL_TCP_PORT or the mysql-tcp entry in /etc/services or the
; compile-time value defined MYSQL_PORT (in that order). Win32 will only look
mysqli.default_port = 3306

; Default socket name for local MySQL connects. If empty, uses the built-in
; MySQL defaults.
mysqli.default_socket =

; Default host for mysql_connect() (doesn't apply in safe mode).
mysqli.default_host =

; Default user for mysql_connect() (doesn't apply in safe mode).
mysqli.default_user =

; Default password for mysqli_connect() (doesn't apply in safe mode).
; Note that this is generally a *bad* idea to store passwords in this file.
; *Any* user with PHP access can run 'echo get_cfg_var("mysqli.default_pw")
; and reveal this password! And of course, any users with read access to this
; file will be able to reveal the password as well.
mysqli.default_pw =

; Allow or prevent reconnect
mysqli.reconnect = Off

; Allow or prevent persistent links.
msql.allow_persistent = On

; Maximum number of persistent links. -1 means no limit.
msql.max_persistent = -1

; Maximum number of links (persistent+non persistent). -1 means no limit.
msql.max_links = -1

; Allow or prevent persistent links.
pgsql.allow_persistent = On

; Detect broken persistent links always with pg_pconnect().
; Auto reset feature requires a little overheads.
pgsql.auto_reset_persistent = Off

; Maximum number of persistent links. -1 means no limit.
pgsql.max_persistent = -1

; Maximum number of links (persistent+non persistent). -1 means no limit.
pgsql.max_links = -1

; Ignore PostgreSQL backends Notice message or not.
; Notice message logging require a little overheads.
pgsql.ignore_notice = 0

; Log PostgreSQL backends Noitce message or not.
; Unless pgsql.ignore_notice=0, module cannot log notice message.
pgsql.log_notice = 0

; Allow or prevent persistent links.
sybase.allow_persistent = On

; Maximum number of persistent links. -1 means no limit.
sybase.max_persistent = -1

; Maximum number of links (persistent + non-persistent). -1 means no limit.
sybase.max_links = -1

;sybase.interface_file = "/usr/sybase/interfaces"

; Minimum error severity to display.
sybase.min_error_severity = 10

; Minimum message severity to display.
sybase.min_message_severity = 10

; Compatability mode with old versions of PHP 3.0.
; If on, this will cause PHP to automatically assign types to results according
; to their Sybase type, instead of treating them all as strings. This
; compatability mode will probably not stay around forever, so try applying
; whatever necessary changes to your code, and turn it off.
sybase.compatability_mode = Off

; Allow or prevent persistent links.
sybct.allow_persistent = On

; Maximum number of persistent links. -1 means no limit.
sybct.max_persistent = -1

; Maximum number of links (persistent + non-persistent). -1 means no limit.
sybct.max_links = -1

; Minimum server message severity to display.
sybct.min_server_severity = 10

; Minimum client message severity to display.
sybct.min_client_severity = 10

; Number of decimal digits for all bcmath functions.
bcmath.scale = 0

;browscap = extra/browscap.ini

; Default host for ifx_connect() (doesn't apply in safe mode).
ifx.default_host =

; Default user for ifx_connect() (doesn't apply in safe mode).
ifx.default_user =

; Default password for ifx_connect() (doesn't apply in safe mode).
ifx.default_password =

; Allow or prevent persistent links.
ifx.allow_persistent = On

; Maximum number of persistent links. -1 means no limit.
ifx.max_persistent = -1

; Maximum number of links (persistent + non-persistent). -1 means no limit.
ifx.max_links = -1

; If on, select statements return the contents of a text blob instead of its id.
ifx.textasvarchar = 0

; If on, select statements return the contents of a byte blob instead of its id.
ifx.byteasvarchar = 0

; Trailing blanks are stripped from fixed-length char columns. May help the
; life of Informix SE users.
ifx.charasvarchar = 0

; If on, the contents of text and byte blobs are dumped to a file instead of
; keeping them in memory.
ifx.blobinfile = 0

; NULL's are returned as empty strings, unless this is set to 1. In that case,
; NULL's are returned as string 'NULL'.
ifx.nullformat = 0

; Handler used to store/retrieve data.
session.save_handler = files

; Argument passed to save_handler. In the case of files, this is the path
; where data files are stored. Note: Windows users have to change this
; variable in order to use PHP's session functions.
; As of PHP 4.0.1, you can define the path as:
; session.save_path = "N;/path"
; where N is an integer. Instead of storing all the session files in
; /path, what this will do is use subdirectories N-levels deep, and
; store the session data in those directories. This is useful if you
; or your OS have problems with lots of files in one directory, and is
; a more efficient layout for servers that handle lots of sessions.
; NOTE 1: PHP will not create this directory structure automatically.
; You can use the script in the ext/session dir for that purpose.
; NOTE 2: See the section on garbage collection below if you choose to
; use subdirectories for session storage
; The file storage module creates files using mode 600 by default.
; You can change that by using
; session.save_path = "N;MODE;/path"
; where MODE is the octal representation of the mode. Note that this
; does not overwrite the process's umask.
;session.save_path = "/tmp"

; Whether to use cookies.
session.use_cookies = 1

; This option enables administrators to make their users invulnerable to
; attacks which involve passing session ids in URLs; defaults to 0.
; session.use_only_cookies = 1

; Name of the session (used as cookie name). = PHPSESSID

; Initialize session on request startup.
session.auto_start = 0

; Lifetime in seconds of cookie or, if 0, until browser is restarted.
session.cookie_lifetime = 0

; The path for which the cookie is valid.
session.cookie_path = /

; The domain for which the cookie is valid.
session.cookie_domain =

; Handler used to serialize data. php is the standard serializer of PHP.
session.serialize_handler = php

; Define the probability that the 'garbage collection' process is started
; on every session initialization.
; The probability is calculated by using gc_probability/gc_divisor,
; e.g. 1/100 means there is a 1% chance that the GC process starts
; on each request.

session.gc_probability = 1
session.gc_divisor = 100

; After this number of seconds, stored data will be seen as 'garbage' and
; cleaned up by the garbage collection process.
session.gc_maxlifetime = 1440

; NOTE: If you are using the subdirectory option for storing session files
; (see session.save_path above), then garbage collection does *not*
; happen automatically. You will need to do your own garbage
; collection through a shell script, cron entry, or some other method.
; For example, the following script would is the equivalent of
; setting session.gc_maxlifetime to 1440 (1440 seconds = 24 minutes):
; cd /path/to/sessions; find -cmin +24 | xargs rm

; PHP 4.2 and less have an undocumented feature/bug that allows you to
; to initialize a session variable in the global scope, albeit register_globals
; is disabled. PHP 4.3 and later will warn you, if this feature is used.
; You can disable the feature and the warning separately. At this time,
; the warning is only displayed, if bug_compat_42 is enabled.

session.bug_compat_42 = 0
session.bug_compat_warn = 1

; Check HTTP Referer to invalidate externally stored URLs containing ids.
; HTTP_REFERER has to contain this substring for the session to be
; considered as valid.
session.referer_check =

; How many bytes to read from the file.
session.entropy_length = 0

; Specified here to create the session id.
session.entropy_file =

;session.entropy_length = 16

;session.entropy_file = /dev/urandom

; Set to {nocache,private,public,} to determine HTTP caching aspects
; or leave this empty to avoid sending anti-caching headers.
session.cache_limiter = nocache

; Document expires after n minutes.
session.cache_expire = 180

; trans sid support is disabled by default.
; Use of trans sid may risk your users security.
; Use this option with caution.
; - User may send URL contains active session ID
; to other person via. email/irc/etc.
; - URL that contains active session ID may be stored
; in publically accessible computer.
; - User may access your site with the same session ID
; always using URL stored in browser's history or bookmarks.
session.use_trans_sid = 0

; Select a hash function
; 0: MD5 (128 bits)
; 1: SHA-1 (160 bits)
session.hash_function = 0

; Define how many bits are stored in each character when converting
; the binary hash data to something readable.
; 4 bits: 0-9, a-f
; 5 bits: 0-9, a-v
; 6 bits: 0-9, a-z, A-Z, "-", ","
session.hash_bits_per_character = 5

; The URL rewriter will look for URLs in a defined set of HTML tags.
; form/fieldset are special; if you include them here, the rewriter will
; add a hidden field with the info which is otherwise appended
; to URLs. If you want XHTML conformity, remove the form entry.
; Note that all valid entries require a "=", even if no value follows.
url_rewriter.tags = "a=href,area=href,frame=src,input=src,form=,fieldset="

; Allow or prevent persistent links.
mssql.allow_persistent = On

; Maximum number of persistent links. -1 means no limit.
mssql.max_persistent = -1

; Maximum number of links (persistent+non persistent). -1 means no limit.
mssql.max_links = -1

; Minimum error severity to display.
mssql.min_error_severity = 10

; Minimum message severity to display.
mssql.min_message_severity = 10

; Compatability mode with old versions of PHP 3.0.
mssql.compatability_mode = Off

; Connect timeout
;mssql.connect_timeout = 5

; Query timeout
;mssql.timeout = 60

; Valid range 0 - 2147483647. Default = 4096.
;mssql.textlimit = 4096

; Valid range 0 - 2147483647. Default = 4096.
;mssql.textsize = 4096

; Limits the number of records in each batch. 0 = all records in one batch.
;mssql.batchsize = 0

; Specify how datetime and datetim4 columns are returned
; On => Returns data converted to SQL server settings
; Off => Returns values as YYYY-MM-DD hh:mm:ss
;mssql.datetimeconvert = On

; Use NT authentication when connecting to the server
mssql.secure_connection = Off

; Specify max number of processes. -1 = library default
; msdlib defaults to 25
; FreeTDS defaults to 4096
;mssql.max_procs = -1

; Specify client character set.
; If empty or not set the client charset from freetds.comf is used
; This is only used when compiled with FreeTDS
;mssql.charset = "ISO-8859-1"

; Assert(expr); active by default.
; = On

; Issue a PHP warning for each failed assertion.
;assert.warning = On

; Don't bail out by default.
;assert.bail = Off

; User-function to be called if an assertion fails.
;assert.callback = 0

; Eval the expression with current error_reporting(). Set to true if you want
; error_reporting(0) around the eval().
;assert.quiet_eval = 0

[Verisign Payflow Pro]
; Default Payflow Pro server.
pfpro.defaulthost = ""

; Default port to connect to.
pfpro.defaultport = 443

; Default timeout in seconds.
pfpro.defaulttimeout = 30

; Default proxy IP address (if required).
;pfpro.proxyaddress =

; Default proxy port.
;pfpro.proxyport =

; Default proxy logon.
;pfpro.proxylogon =

; Default proxy password.
;pfpro.proxypassword =

; path to a file containing GUIDs, IIDs or filenames of files with TypeLibs
;com.typelib_file =
; allow Distributed-COM calls
;com.allow_dcom = true
; autoregister constants of a components typlib on com_load()
;com.autoregister_typelib = true
; register constants casesensitive
;com.autoregister_casesensitive = false
; show warnings on duplicate constat registrations
;com.autoregister_verbose = true

; language for internal character representation.
;mbstring.language = Japanese

; internal/script encoding.
; Some encoding cannot work as internal encoding.
; (e.g. SJIS, BIG5, ISO-2022-*)
;mbstring.internal_encoding = EUC-JP

; http input encoding.
;mbstring.http_input = auto

; http output encoding. mb_output_handler must be
; registered as output buffer to function
;mbstring.http_output = SJIS

; enable automatic encoding translation according to
; mbstring.internal_encoding setting. Input chars are
; converted to internal encoding by setting this to On.
; Note: Do _not_ use automatic encoding translation for
; portable libs/applications.
;mbstring.encoding_translation = Off

; automatic encoding detection order.
; auto means
;mbstring.detect_order = auto

; substitute_character used when character cannot be converted
; one from another
;mbstring.substitute_character = none;

; overload(replace) single byte functions by mbstring functions.
; mail(), ereg(), etc are overloaded by mb_send_mail(), mb_ereg(),
; etc. Possible values are 0,1,2,4 or combination of them.
; For example, 7 for overload everything.
; 0: No overload
; 1: Overload mail() function
; 2: Overload str*() functions
; 4: Overload ereg*() functions
;mbstring.func_overload = 0

;fbsql.allow_persistent = On
;fbsql.autocommit = On
;fbsql.default_database =
;fbsql.default_database_password =
;fbsql.default_host =
;fbsql.default_password =
;fbsql.default_user = "_SYSTEM"
;fbsql.generate_warnings = Off
;fbsql.max_connections = 128
;fbsql.max_links = 128
;fbsql.max_persistent = -1
;fbsql.max_results = 128
;fbsql.batchSize = 1000

; Exif UNICODE user comments are handled as UCS-2BE/UCS-2LE and JIS as JIS.
; With mbstring support this will automatically be converted into the encoding
; given by corresponding encode setting. When empty mbstring.internal_encoding
; is used. For the decode settings you can distinguish between motorola and
; intel byte order. A decode setting cannot be empty.
;exif.encode_unicode = ISO-8859-15
;exif.decode_unicode_motorola = UCS-2BE
;exif.decode_unicode_intel = UCS-2LE
;exif.encode_jis =
;exif.decode_jis_motorola = JIS
;exif.decode_jis_intel = JIS

; The path to a default tidy configuration file to use when using tidy
;tidy.default_config = /usr/local/lib/php/default.tcfg

; Should tidy clean and repair output automatically?
; WARNING: Do not use this option if you are generating non-html content
; such as dynamic images
tidy.clean_output = Off

; Enables or disables WSDL caching feature.
; Sets the directory name where SOAP extension will put cache files.
; (time to live) Sets the number of second while cached file will be used
; instead of original one.

; xxx: mailquota not used anymore. functionality removed from php and placed in gdmailwrap
hosting_root_dir = /home/content
mailquota_dir = /home/mailquota
mailquota_dir_tree_depth = 3
hosting_dir_tree_depth = 3
max_mail_allowed = 1000
max_mail_trigger = 800
sendmail_from =

dbx.colnames_case = "unchanged"

; Local Variables:
; tab-width: 4
; End:

cgi.fix_pathinfo = 1
; This file is for CGI/FastCGI installations.
; Try copying it to php5.ini, if it doesn't work

; adjust memory limit

memory_limit = 64M

max_execution_time = 18000

; disable magic quotes for php request vars

magic_quotes_gpc = off

; disable automatic session start
; before autoload was initialized

flag session.auto_start = off

; enable resulting html compression

zlib.output_compression = on

; disable user agent verification to not break multiple image upload

suhosin.session.cryptua = off

; turn off compatibility with PHP4 when dealing with objects

zend.ze1_compatibility_mode = off

; PHP for some reason ignores this setting in system php.ini
; and disables mcrypt if this line is missing in local php.ini


and my .htaccess file is as below:

## uncomment these lines for CGI mode
## make sure to specify the correct cgi php binary file name
## it might be /cgi-bin/php-cgi

# Action php5-cgi /cgi-bin/php5-cgi
# AddHandler php5-cgi .php

## GoDaddy specific options

Options -MultiViews

## you might also need to add this line to php.ini
## cgi.fix_pathinfo = 1
## if it still doesn't work, rename php.ini to php5.ini

## this line is specific for 1and1 hosting

#AddType x-mapp-php5 .php
#AddHandler x-mapp-php5 .php

## default index file

DirectoryIndex index.php

<IfModule mod_php5.c>

## adjust memory limit

# php_value memory_limit 64M
php_value memory_limit 256M
php_value max_execution_time 18000

## disable magic quotes for php request vars

php_flag magic_quotes_gpc off

## disable automatic session start
## before autoload was initialized

php_flag session.auto_start off

## enable resulting html compression

#php_flag zlib.output_compression on

# disable user agent verification to not break multiple image upload

php_flag suhosin.session.cryptua off

# turn off compatibility with PHP4 when dealing with objects

php_flag zend.ze1_compatibility_mode Off


<IfModule mod_security.c>
# disable POST processing to not break multiple image upload

SecFilterEngine Off
SecFilterScanPOST Off

<IfModule mod_deflate.c>

## enable apache served files compression

# Insert filter on all content
###SetOutputFilter DEFLATE
# Insert filter on selected content types only
#AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript

# Netscape 4.x has some problems...
#BrowserMatch ^Mozilla/4 gzip-only-text/html

# Netscape 4.06-4.08 have some more problems
#BrowserMatch ^Mozilla/4\.0[678] no-gzip

# MSIE masquerades as Netscape, but it is fine
#BrowserMatch \bMSIE !no-gzip !gzip-only-text/html

# Don't compress images
#SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip dont-vary

# Make sure proxies don't deliver the wrong content
#Header append Vary User-Agent env=!dont-vary


<IfModule mod_ssl.c>

## make HTTPS env vars available for CGI mode

SSLOptions StdEnvVars


<IfModule mod_rewrite.c>

## enable rewrites

Options +FollowSymLinks
RewriteEngine on

## you can put here your magento root folder
## path relative to web root

RewriteBase /

## uncomment next line to enable light API calls processing

# RewriteRule ^api/([a-z][0-9a-z_]+)/?$ api.php?type=$1 [QSA,L]

## rewrite API2 calls to api.php (by now it is REST only)

RewriteRule ^api/rest api.php?type=rest [QSA,L]

## workaround for HTTP authorization
## in CGI environment

RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

## TRACE and TRACK HTTP methods disabled to prevent XSS attacks

RewriteRule .* - [L,R=405]

## redirect for mobile user agents

#RewriteCond %{REQUEST_URI} !^/mobiledirectoryhere/.*$
#RewriteCond %{HTTP_USER_AGENT} "android|blackberry|ipad|iphone|ipod|iemobile|opera mobile|palmos|webos|googlebot-mobile" [NC]
#RewriteRule ^(.*)$ /mobiledirectoryhere/ [L,R=302]

## always send 404 on missing files in these folders

RewriteCond %{REQUEST_URI} !^/(media|skin|js)/

## never rewrite for existing files, directories and links

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-l

## rewrite everything else to index.php

RewriteRule .* index.php [L]


## Prevent character encoding issues from server overrides
## If you still have problems, use the second line instead

AddDefaultCharset Off
#AddDefaultCharset UTF-8

<IfModule mod_expires.c>

## Add default Expires header

ExpiresDefault "access plus 1 year"


## By default allow all access

Order allow,deny
Allow from all

## Deny access to release notes to prevent disclosure of the installed Magento version

order allow,deny
deny from all

## If running in cluster environment, uncomment this

#FileETag none

Kindly help
Danny's picture

By looking at your .htaccess file, it seems you are trying to edit the one in your root directory and not the one located in your media directory. The .htaccess file from within the media directory contains: Options All -Indexes
Suraj's picture

Thanks Dear, i modified .htaccess, one which is located in media folder. now its working well.. thanks a lot for your tutorial and amazing quick support.

Thanks a lot again.

hope i will help you one day. ..

Suraj Patil
Joey 's picture

Thanks for the tutorial. I followed exactly. For some reason, no products or images shows up anything on the frontend. Any ideas? thanks
Danny's picture

Yes, there is a problem with images not showing up. I address this issue towards the end of the video and in the above article. You basically have to edit the .htaccess file in your image directory.
Darren's picture

Hi Danny, thanks for the tutorial. I followed all of the steps above but I am constantly encountering errors this error "One or more of the Cache Types are invalidated: Blocks HTML output. Click here to go to Cache Management and refresh cache types." Do you have any fix for this?
Danny's picture

I personally haven't come across this error but I have read in the Magento forum that people are running into this problem. I don't know if you're doing a fresh install or not... Maybe changed your theme? Added modules? Are your folder permissions setup properly? Keep in mind that these are just guesses, but this is what I would look at first if I were in your situation...

Other than that, I did read some have temporarily fixed the issue by changing their cache settings. You can read the forum thread for yourself here:
There seem to be other tips there that might be useful.
Darren's picture

previously when I encountered that problem it was a fresh install, but later I found out it's just some permission issues.

Btw, have you tried before EMthemes? I am currently encountering some problems with the theme, perhaps you can help me out if I were to offer you the theme files?
Danny's picture

I haven't tried EM themes but I did create a video on installing Magento themes which I haven't had a chance to upload to Youtube. I actually hope to upload that video as soon as I'm done with some other projects, but I don't know how soon that will be.

As for EM Themes, the name rings a bell, so I just Googled them and saw that they sell themes. Now I see why the name sounded familiar. Since it's just a theme, the issue shouldn't be too difficult to diagnose unless that theme itself is causing problems that would require a fix to the actual files. What type of errors are you encountering?
marie's picture

I had follow the all installation but I am getting the error message There has been an error processing your request
Danny's picture

I don't know if you managed to get to the part where Magento tells you "you're all set!"... If you didn't make it, I'd go over all of the steps carefully once again. If you did make it to this message, I'd make sure that everything is correctly configured and that all of your Magento files are where they should be.
Anna's picture

Hi. I have installed magento admin pannel on my go daddy account.

Every time I log into my magento admin pannel and try to upload a product image, there is no browse and upload button.

Someone help!
Danny's picture

Hello Anna,

Interesting question and it's a bit difficult for me to answer it since I don't exactly know how the installation process went. While I do believe that you did, but I have to mention it anyway, I recommend watching the entire video if you haven't because I go through the steps of listing a product in Magento.

Aside from that which internet browser are you using? I am asking because it might not be a server side issue. Try another browser to see if that helps.

If that doesn't work, check to see if there are other errors since maybe, you didn't install everything properly.
Robert Stutzman's picture

Hello, first off, thank you for taking the time to make this video. during your video I noticed that the has changed. When i go to the install portion, this is what comes up:

Warning: include_once(Mage/Core/functions.php) [function.include-once]: failed to open stream: No such file or directory in /home/content/20/11331320/html/app/Mage.php on line 49

Warning: include_once() [function.include]: Failed opening 'Mage/Core/functions.php' for inclusion (include_path='/home/content/20/11331320/html/app/code/local:/home/content/20/11331320/html/app
sr/local/php5_3/lib/php') in /home/content/20/11331320/html/app/Mage.php on line 49

Warning: include(Mage/Core/Model/App.php) [function.include]: failed to open stream: No such file or directory in /home/content/20/11331320/html/lib/Varien/Autoload.php on line 93

Warning: include() [function.include]: Failed opening 'Mage/Core/Model/App.php' for inclusion (include_path='/home/content/20/11331320/html/app/code/local:/home/content/20/11331320/html/app
sr/local/php5_3/lib/php') in /home/content/20/11331320/html/lib/Varien/Autoload.php on line 93

Fatal error: Class 'Mage_Core_Model_App' not found in /home/content/20/11331320/html/app/Mage.php on line 608

I triple checked everything. Unless something has changed on there servers I don't know what to do.
Danny's picture

I haven't checked Godaddy in some time, but I will do so when I get a chance. Therefore, I don't really know how much they've changed, but even if they did change I don't think the procedure would be that far off since it might just be a UI update or something like that.

From the looks of the errors, I would guess that your files are in the wrong location. First thing to look into is whether you moved the files to the correct locations. For example, if you misplaced the directories, you will get this error when Magento starts looking for the files because Magento uses paths to include files that it reads off. For this reason, when it can't find a file things go wrong since the code that is supposed to make it work, is missing.

Another thing to make sure is that you are entering the paths of your server correctly when you are required to do so.
stephen g's picture


thank you for posting this great great video. even more, thank you for showing me the simple fix to the broken image problem. you are the only one i found that identified this specific issue and had a simple fix for it
Danny's picture

Thanks for the kind words. I appreciate it Stephen.
JOELLE's picture

I have installed a fresh install on a Godaddy Shared environment. when I got it redirects me to and that says no
input file specified but i manually go to it goes to the
correct page to accept terms of agreement. The problem is when I accept it redirects me to and that also returns
no input file specified

Danny's picture

If you are getting the no input file message, your setup is wrong. I actually mention this in the video and it's one of the biggest struggles that people are having with Magento. When I was learning to install Magento, it actually took me some time to figure out how to get rid of that error in particular.

Unfortunately though, I cannot pinpoint the reason you are getting the error because it could be for many reasons -- especially since I don't know which steps you took before receiving the error. Therefore, the best way to figure it out is by following each step in the video closely and making sure that you are installing everything correctly on your end. In addition to this, I mention in the video a couple of things that you can do to fix the no input file error.
Chirag Patel's picture

I keep getting a "[an error occurred while processing this directive]" error when I try and access the install.php fille. I have my Magento configuration as "/transpose/" instead of at the root. I modified the htpaccess file for rewrites to account for this opposed to what you had for the root. any ideas on why this is occuring?
Danny's picture

I can only assume that maybe somewhere along the line you entered the information wrong especially since my video focuses on installing Magento in the root directory. Best solution would be when installing, to try and make sure that you upload the Magento directory to your server and try to rename it from magento to transpose and then try to do a search and replace on the .htaccess file -- but that may be what you did already?

I also just did a quick search to see if someone else had these issues and it seems like it might not be related to Magento, but to file and folder permissions instead. Personally, I never came across this error so I wouldn't know for sure, but did you upload the zipped archive or did you unzip and then upload? I ask because your permissions may have changed with the latter.
Chirag Patel's picture

Thanks for the response. I kept doing some Google searches and came up with some other things.

1. GoDaddy recently updated their Apache from 2.2 to 2.4. Not sure if that causes problems with htaccess or they say that you have to change any "include virtual..." to "include file.." in all html files. Not sure if this is the problem.

2. I came across the file permission issue also. I have changed all my file permisisons to what is recommended. Folders are 755 and files are 644.

This was working great on my local drive. I unzipped on my Windows machine and then ftped everything over. The directory structure did not change.

I will try a fresh reinstall tomm where I upload the zipped archive and try loading that.


Danny's picture

I didn't realize that Godaddy upgraded to Apache v2.4 which is definitely interesting to say the least since there have been some minor changes made to Apache that can give people problems due to old configuration in their .htaccess files.

I know someone else mentioned some upgrades on Godaddy but I haven't had a chance to really dig into them so this is the first time that I am looking closer at things.

Now while I am not entirely sure that the .htaccess changes are causing the "an error occurred while processing this directive" because I've never really experienced this issue, it sound like it could very well be what is causing your problem.

So I just downloaded Magento again to find the lines that need to be changed so that I can show people how to do it.

First off, here is the link from the Apache site which explains what has changed:

Note that I haven't tested the changes I am about to post, but I believe this should fix things -- if not revert back to old configuration, but please let me know if it helped so that I can confirm that these changes helped.

Oh boy, does Magento have a lot of .htaccess files...

In the root .htaccess file, change these lines:

Order allow,deny
Allow from all


Require all granted

In the rest of the directories such as: 'app' , 'downloader', 'errors ', 'includes', 'lib', 'pkginfo' and 'var' change .htaccess lines:

Order deny,allow
Deny from all


Require all denied

If I missed any files, feel free to let me know.
Dru's picture

I have a number of issues at the moment.

First, the new php5.ini file is not being updated when I bring up the info.php file I have deleted all information and re-upload three times, and still noting. Also I noticed that the original php.ini fill is not contained with the zip, or gz file.

My info.php below even with a php5.ini file on the root

Configuration File (php.ini) Path /web/conf
Loaded Configuration File /web/conf/php5.ini
Scan this dir for additional .ini files (none)

Danny's picture

The php.ini isn't included in the zip and you wouldn't want it included because it's better to have a php.ini that is setup for your server. From what I can recall, Godaddy php.ini files have some custom values in them which is why you'd want the original file...

I know some of my readers have accidentally deleted their original php.ini files so this might have happened to you as well. If I were you, I'd try to get Godaddy to restore the original php.ini file.

Are you seeing the upload_tmp_dir and cgi.fix_pathinfo variables change? What do you see showing for these variables?
Dru's picture

Nothing is changing Below is my php5.ini file, also I noticed that when I go to edit under the goDaddy FTP manager it says false before displaying text and before it saves the file.............I have come to the conclusion that goDaddy,

cgi.fix_pathinfo = 1
; This file is for CGI/FastCGI installations.
; Try copying it to php5.ini, if it doesn't work
; adjust memory limit
memory_limit = 128M
max_execution_time = 18000
; disable magic quotes for php request vars
magic_quotes_gpc = off
; disable automatic session start
; before autoload was initialized
flag session.auto_start = off
; enable resulting html compression
zlib.output_compression = on
; disable user agent verification to not break multiple image upload
suhosin.session.cryptua = off
; turn off compatibility with PHP4 when dealing with objects
zend.ze1_compatibility_mode = off
; PHP for some reason ignores this setting in system php.ini
; and disables mcrypt if this line is missing in local php.ini

P Version 5.3.24


Local Value

Master Value

allow_call_time_pass_reference Off Off
allow_url_fopen On On
allow_url_include Off Off
always_populate_raw_post_data Off Off
arg_separator.input & &
arg_separator.output & &
asp_tags Off Off
auto_append_file no value no value
auto_globals_jit On On
auto_prepend_file no value no value
browscap no value no value
default_charset no value no value
default_mimetype text/html text/html
define_syslog_variables Off Off
disable_classes no value no value
disable_functions no value no value
display_errors On On
display_startup_errors Off Off
doc_root no value no value
docref_ext no value no value
docref_root no value no value
enable_dl On On
error_append_string no value no value
error_log no value no value
error_prepend_string no value no value
error_reporting 30711 30711
exit_on_timeout Off Off
expose_php Off Off
extension_dir ./ ./
file_uploads On On #FFFFFF #FFFFFF
highlight.comment #FF8000 #FF8000
highlight.default #0000BB #0000BB
highlight.html #000000 #000000
highlight.keyword #007700 #007700
highlight.string #DD0000 #DD0000
html_errors On On
ignore_repeated_errors Off Off
ignore_repeated_source Off Off
ignore_user_abort Off Off
implicit_flush Off Off
include_path .:/usr/local/php5_3/lib/php .:/usr/local/php5_3/lib/php
log_errors Off Off
log_errors_max_len 1024 1024
magic_quotes_gpc On On
magic_quotes_runtime Off Off
magic_quotes_sybase Off Off
mail.add_x_header Off Off
mail.force_extra_parameters no value no value
mail.log no value no value
max_execution_time 30 30
max_file_uploads 20 20
max_input_nesting_level 64 64
max_input_time 60 60
max_input_vars 1000 1000
memory_limit 64M 64M
open_basedir no value no value
output_buffering no value no value
output_handler no value no value
post_max_size 33M 33M
precision 14 14
realpath_cache_size 16K 16K
realpath_cache_ttl 120 120
register_argc_argv On On
register_globals Off Off
register_long_arrays Off Off
report_memleaks On On
report_zend_debug On On
request_order no value no value
safe_mode Off Off
safe_mode_exec_dir no value no value
safe_mode_gid Off Off
safe_mode_include_dir ~ ~
sendmail_path /usr/sbin/sendmail -t -i /usr/sbin/sendmail -t -i
serialize_precision 100 100
short_open_tag On On
smtp_port 25 25
sql.safe_mode Off Off
track_errors Off Off
unserialize_callback_func no value no value
upload_max_filesize 32M 32M
upload_tmp_dir /tmp /tmp
user_dir no value no value
user_ini.cache_ttl 300 300
user_ini.filename .user.ini .user.ini
variables_order GPCS GPCS
xmlrpc_error_number 0 0
xmlrpc_errors Off Off
y2k_compliance On On
zend.enable_gc On On
Danny's picture

I see you mentioned that Godaddy's text editor may be giving you errors... Have you tried creating the php5.ini file on your local computer and then uploading it? I would try that. You can also try downloading the existing php5.ini file to your local computer and opening it with a text editor to see if your edits are doing anything to the file.

Godaddy also created a help article with tips on what to do if you don't see the changes taking effect over here:
Dru's picture

I have created the file on my computer and upload with a FTP client I have also killed the processes over a dozen times.
Danny's picture

Interesting... I wish I knew the answer then... From my experience, when you drop the file into your root directory, Godaddy picks up on it. Now I might be mentioning this a little late since my server's configuration seems to be a bit different from your, but at one point you mentioned a directory /web/conf/ which is where you stated that your php5.ini file is being read from.

Do you see these directories? If you do, try looking in there for the php5.ini and try editing that file. I know I have a hosting plan with a company other than Godaddy and the file structure of the server is a bit different and my php.ini isn't located in the root. Which is why I think Godaddy might have a similar setup on certain hosting accounts.

If that doesn't work, I'd contact Godaddy about it because maybe there is something going on with the configuration of the server.
Philip's picture

After a few days of frustration with Godaddy Shared hosting, I decided to try my luck at They have mojomarket place and it got installed in 5 minutes.

One caveat with my godaddy account was that I had several sites there in wordpress and drupal. They all worked, but I was never able to install Magento to a sub folder.
Danny's picture

I agree that installing Magento on Godaddy can be a pain. In fact, I do recommend a couple of sites in this article that also offer quick installation similar to the way that Bluehost does.

Of course I am not saying this because I want people to leave Godaddy... I actually have been using them for years so I am somewhat of a dedicated customer. It's just that it would be nice if Godaddy added a Magento quick install option on their hosting plans similar to the way that they offer them for WordPress, Drupal and other CMSs, but based on the recommendation that Godaddy makes, I think they'd prefer to see their customers install Magento on a virtual or dedicated server.

Then again, maybe I should be happy that Godaddy isn't offering quick installs since my video wouldn't be so popular if they did LOL ;)
Natarajan's picture

I followed each and every sentence in your blogs but still i am getting this error when I try to instal magento please check my site

server is godaddy
Danny's picture

I see your site is up and running so I assume you fixed the problem.
SARAVENAN's picture

i have the similar issue. please share your finding. Can you send the php5.ini and htaccess files ?
Adam's picture


First I would like to thank you for such a great site! and Second, for any assistance you can provide to my issue. I am using Godaddy Deluxe Shared Hosting and have successfully (I believe) installs Magento CE 1.8 to the root directory. Now for Magento seems all fine and good. But I cant seem to get a second store working on the same install correctly. I have set up per Godaddy and directing of subdirectory as follow: ==>

I am pretty sure I have the Magento backend configured right for a second domain store setup but I am having a helluva time getting the .htaccess and index.php right for the second store setup! Are you familiar with a multi store multi domain setup on a shared Godaddy server and specifically what the .htaccess and index.php file should actually look like to work? I have read well over 10 write-ups on this and actually now think I am even more confused!!!

Your help for a layman is very much appreciated!

Danny's picture

Hey Adam,

I do see that you have Magento installed since the url you have your name linked to is pointing to it. As far as multi stores are concerned, I haven't really dug that deep into Magento but I guess one day I should. As for now, what is happening exactly? Is Godaddy not pointing to the subdirectory or is your Magento installed wrong? When you go to where is it pointing?

Also do you want to be a completely different store? Or do you want to show just a section of your other store?

Personally I'd just install Magento in another directory and setup an additional database and then point the 2nd domain to that directory via these instructions: but since Magento supports multi stores this may not be the most ideal solution.
Ajinkya's picture

Nice tutorial. I was trying to install Magneto on go daddy shared hosting. Was not able to install with given values.
if I want to install Magneto on sub directory instead of web root folder lets say webroot/myStore. What will be the corresponding values for php5.ini and .htmlacees file? Also where to keep php5.ini? in root or sub-directory like /root/myStore?
Luz's picture

Thanks for the tutorial. I've tried following the video but I run into issues i'm sure because of changes made inside GoDaddy. I haven't been able to find the .htaccess file you mention in the video, and the php.ini file is rather short in comparison to yours. nonetheless, I've read a lot of the comments here and on youtube to make sure I haven't missed anything but I"m receiving the "PHP extension mcrypt and gd must be loaded". I've already tried the same via PuTTY and I get back that there are no packages by those names, nothing to do.
Do you have any ideas? I can't believe I'm the only one experiencing this issue...
Danny's picture

For the .htaccess, if you are on cPanel and are using the file manager, be sure to check off the box show hidden files upon launching the file manager.

As for the php.ini file, you don't really need to worry about how long it is, you basically just need to make sure that the needed system values are added to it.

As for mcrypt and gd, you will want to use easyapache. I actually have a video on this here:
tomiwa's picture

Please i have this error Warning: require(app/Mage.php) [function.require]: failed to open stream: No such file or directory in /home/content/32/11401332/html/Hezra/install.php on line 125

Fatal error: require() [function.require]: Failed opening required 'app/Mage.php' (include_path='/home/content/32/11401332/html/Hezra:.:/usr/local/php5_3/lib/php') in /home/content/32/11401332/html/Hezra/install.php on line 125
Danny's picture

Based on the error, I believe you didn't upload all the files correctly.
Noshi Francis's picture

Hello i tried to follow the steps today to install it on my godaddy account however i found that godaddy only supports MySQL version 5.45 and it requires version 5.6 or more to work, how did you get over this limitation?

please help


Add new comment