› ›
CRITICAL SECURITY VERSION UPDATE:
https://github.com/daylightstudio/FUEL-CMS/releases/tag/1.4.13

Is it possible to install Fuel on an IIS server?

JavaJunkyJavaJunky
edited August 2011 in Installation
I've been developing a site on our apache server and our client's hosting company only has IIS servers. Does not having the ability to use htaccess mean it's impossible for Fuel to run on it?

Uploading the site to the IIS server and loading up the homepage just spits out:
Your system folder path does not appear to be set correctly. Please open the following file and correct this: index.php

Any insight would be appreciated!

Comments

  • adminadmin
    edited 6:30AM
    You can definitely run FUEL without .htaccess just like a normal CodeIgniter application. You will just need to add index.php to the "$config['index_page']" configuration parameter in the fuel/application/config/config.php file.
  • JavaJunkyJavaJunky
    edited 6:30AM
    Thanks for the response. I tried what you suggested. But it's still only spitting out the above error. I also did a lot of searching around for CI + IIS6 installs, but all of it is not working yet. I tried changing "$config['index_page']" to 'index.php' and also 'index.php?' as some have suggested. I'm going to keep trying different things. If you have any other ideas, let me know. Thanks again!
  • adminadmin
    edited 6:30AM
    Did you check the index.php file to fix the paths? Perhaps the INSTALL_ROOT needs to be changed in that file?
  • JavaJunkyJavaJunky
    edited 6:30AM
    hmm, so I'm echoing out what dirname(__FILE__) and realpath(dirname(__FILE__)) are.
    dirname(__FILE__) outputs:
    \\f810-e4.msp.eschelon.com\customer-home\M\mysitename
    realpath(dirname(__FILE__)) returns an empty string.

    What should 'INSTALL_ROOT' be if I were to set it manually?
  • adminadmin
    edited 6:30AM
    It should be the server path to the "fuel" folder (e.g. /var/www/httpdocs/fuel/)
  • JavaJunkyJavaJunky
    edited 6:30AM
    So I'm trying to do a clean install of Fuel CMS first just to see if I can get it working. I manually set the 'INSTALL_ROOT' and I'm not getting the original error now. I think it's seeing the system folder path. However I'm getting these two errors now.

    Warning: require(/f810-e4.msp.eschelon.com/customer-home/M/salessite/fuel/application/config/constants.php) [function.require]: failed to open stream: No such file or directory in \\f810-e4.msp.eschelon.com\customer-home\M\salessite\fuel\codeigniter\core\CodeIgniter.php on line 49 Fatal error: require() [function.require]: Failed opening required '/f810-e4.msp.eschelon.com/customer-home/M/salessite/fuel/application/config/constants.php' (include_path='.;C:\php5\pear') in \\f810-e4.msp.eschelon.com\customer-home\M\salessite\fuel\codeigniter\core\CodeIgniter.php on line 49

    I verified that 'constants.php' is there in /fuel/application/config/.
  • adminadmin
    edited 6:30AM
    Have you tried installing just a normal CI instance on the server to see if that works? I'm seeing similar issues in CodeIgniter forum posts with just normal CI installs and thought if it is just a CI issue we could solve that first then work with the FUEL install.

    You've probably seen these in your search venture but I'm posting links I've found here just in case it helps:
    http://codeigniter.com/forums/viewthread/72013/
    http://stackoverflow.com/questions/5408111/codeigniter-2-on-iis-with-web-config-file
    http://codeigniter.com/forums/viewthread/91954
  • JavaJunkyJavaJunky
    edited 6:30AM
    That's a good idea. I'm going to try that. Thanks!
  • JavaJunkyJavaJunky
    edited 6:30AM
    Just to follow up, the IIS server was spitting out error after error. I'd fix one thing only to see a new set of errors displayed. I think it is mostly because the server was running an old version of IIS. Anyway, we got the client working on a new Apache server and everything is running smoothly now. Only took a short while to migrate the website from our test server to the new Apache server.

    Thanks for all the help. Dealing with IIS is a bit of a headache.
Sign In or Register to comment.