Fix session problem on iPage.

iPage: setting up the server for jT CarFramework

iPage requires some work before you can actually use jT CarFramework. We got reports regarding problems with .htaccess settings and SESSION issues too.

We don’t really understand why iPage sets it’s accounts like this but, fortunately, you can tweak your account and set it to what you need. Each part (below) refers to a specific problem.

Solution for “suexec policy violation” error that occurs in some web hosts You may get this error when trying to use the framework.

This is a server configuration which has nothing to do at all with the software but, it has a easy fix. To fix this error, open your FTP software and set all files to 750 or 755. I mean, all directories and files. This should solve that. This error is more detailed explained here.

Can’t login!

It REALLY sucks but, iPage seems to have session settings screwed up by default. jT CarFramework makes use of sessions to track data therefore, it’s required. To fix that, login to your cPanel and go to cPanel > php.ini QuickConfig > and check for:

session.save_handler = files
session.save_path = /tmp

Fixing it step-by-step:

  1. login to your ipage hosting account
  2. go to Additional Tools -> CGI and Scripted Language Support
  3. there choose PHP Scripting
  4. there you will see “Edit your php.ini file for PHP 5.3″ click on edit.
  5. change value of session.save_path `s value to “/tmp”
  6. it should be working now :)

The session.save_path = xxx it’s usually the part messed up. If you are unsure or is having trouble changing that, as the support guys to help you out. They are awesome and very patience (y)

Problems with error 500

If you’re getting error 500 after installing jT CarFramework, do the following:

[update March 11th, 2014] If you’re getting error 403, follow the same steps. Thanks to Brent for pointing that out!

replace the entire content of root/.htaccess by the following code:

# rewrite URL from ?url=slug to /slug
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule (.*) index.php?url=$1 [L,QSA]
# redirect www to non www
RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC]
RewriteRule ^(.*)$ http://%1/$1 [R=301,L]

Some hosts (like iPage) do not support stuff like MultiView, hence the error. It should be working now, test it out!

If you ask me, iPage illustrates a not-good hosting service but, don’t take my word for it, just Google it yourself. (

Anyways, don’t hesitate in contacting us if you still having trouble! Cheers!


  1. Sadeghayoubi

    thank for ur hard work :)
    i page is good coz it cheep

    1. Jay

      this is probably the sole reason iPage can be called “good” :)

  2. Cody Unrath

    Howdy jT,

    I tried the above code for my .htaccess file, however instead of the 500 error (which doesn’t show up in the apache2 log for some odd reason), it echos the page code instead of rendering it.
    I’ve tried switching the MultiView (in the .conf below) with -Multiview but that got me to the same effect as the above code .

    I also tried changing one of the lines to :

    RewriteRule ^(.*)$ /index.php?url=$1 [L,QSA]

    Note the ^ and / have been added per:

    I’m running virtualmin GPL (Debian 7) and supposedly MOD_REWRITE is working with the following apache2 site-available conf:


    /* code removed for security reason */


    Thanks for having the code up for us to test :^),

  3. sewa kendaraan

    Thanks for one’s marvelous posting! I genuinely enjoyed reading
    it, you’re a great author.I will ensure that I bookmark your blog and may come back very soon. I want to encourage you to continue your great writing,
    have a nice holiday weekend!

Leave a Comment

Your email address will not be published. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>