daylightstudio / FUEL-CMS

A CodeIgniter Content Management System
http://www.getfuelcms.com
1.01k stars 453 forks source link

FuelCMS installation issues #247

Open chaudruc opened 10 years ago

chaudruc commented 10 years ago

Hi, I am trying to install FuelCMS on a mediatemple (gs) account. I have installed codeigniter with db access several times in the past for other projects and have had no issues. But FuelCMS is testing me.

1) I have entered my encryption key. 2) I have set ADMIN = true 3) Loaded DB schema 4) Set the db config file with mysql access 5) Double checked db config file

Issues encountered: 1) If I change db config to use mysqli I get a bug - so changed to just mysql 2) mysql driver errors - around line 300 you use mysql_escape_string instead of mysql_real_escape_string 3) another error mysql_real_escape_string is going to be deprecated blah blah so I had to put @ in front of those 2 lines 4) Finally the admin login screen loads. 5) Logging in with admin/admin fails - unauthorized 6) Went into db and added my email to user table row 1 7) Recover pw does not work - no user found with that email.

Not sure what to do next but would love to try to develop my new project using FuelCMS but it is giving me fits.

Any ideas what I can check?

Thanks, CC

daylightstudio commented 10 years ago
  1. FUEL only supports mysql.
  2. Is this referencing the native CI drivers for mysql?
  3. Same questions as #2?
  4. admin/admin - not sure why that wouldn't work for you. Similar to #7. Are you sure you are pointing it to the correct database? Does the installation work correctly locally for you?
chaudruc commented 10 years ago

David - Thanks for the quick reply... I think it has to do with this db test I was doing... working around it now

When I do a mysql_connect I get the error. mysqli_connect does fine.

ERROR Warning: mysql_connect(): mysqlnd cannot connect to MySQL 4.1+ using the old insecure authentication. Please use an administration tool to reset your password with the command SET PASSWORD = PASSWORD('your_existingpassword'). This will store a new, and more secure, hash value in mysql.user. If this user is used in other scripts executed by PHP 5.2 or earlier you might need to remove the old-passwords flag from your my.cnf file in /nfs/c02/h04/mnt/28148/domains/termreach.com/html/test.php http://termreach.com/html/test.php_ on line 2

On Mon, Apr 28, 2014 at 11:52 AM, David McReynolds <notifications@github.com

wrote:

  1. FUEL only supports mysql.
  2. Is this referencing the native CI drivers for mysql?
  3. Same questions as #2https://github.com/daylightstudio/FUEL-CMS/issues/2 ?
  4. admin/admin - not sure why that wouldn't work for you. Similar to #7https://github.com/daylightstudio/FUEL-CMS/issues/7. Are you sure you are pointing it to the correct database? Does the installation work correctly locally for you?

— Reply to this email directly or view it on GitHubhttps://github.com/daylightstudio/FUEL-CMS/issues/247#issuecomment-41583154 .

daylightstudio commented 9 years ago

When you say redirect to itself, do you mean it appears to be submitting but instead of going into the CMS you are being redirected back to the login form. Also, just to confirm, this is the URL you are using to login:

sample.mydomain.com/fuel/login
daylightstudio commented 9 years ago

Are there any error messages being displayed in the login? If not, it sounds like a problem creating the session. Can you try deleting your CI session cookie?

daylightstudio commented 9 years ago

I'm not sure what the issue would be without having access to the server and looking at the setup unfortunately. Are you able to get the site working locally without the issue?

daylightstudio commented 9 years ago

I see the issue happening. However, I can't really diagnose anything else without actual access to the server and test different files unfortunately. I'm curious why this URL doesn't work and instead gives a 404: http://sample.mydomain.com/index.php/fuel/login/ Does this issue happen for you locally?

daylightstudio commented 9 years ago

Sorry... I meant that having index.php in the URL should still go to the same place (.htaccess is what is used to ignore that). In your case, it goes to a 404 error (using your correct domain). Do you have this issue on your local machine?

daylightstudio commented 9 years ago

Do you have this issue on your local machine?

daylightstudio commented 9 years ago

Is this a fresh installation without any major changes? Normally, you should see a page and not a 404 error at http://japanautostar.petrunko.com/index.php. Is the .htaccess from the main domain causing issues?

daylightstudio commented 9 years ago

I'm suspicious of the .htaccess files causing the problem. Can you try to get a base installation running perhaps even in a subdirectory on your main domain and just changing the the default .htaccess file's RewriteBase to /myfolder/ where "myfolder" is the subfolder you place it in.

altazar commented 9 years ago

After installation I try to login as admin and get this:

A Database Error Occurred

Error Number: 1054

Unknown column 'salt' in 'field list'

UPDATE fuel_users SET password = '...

daylightstudio commented 9 years ago

Does your database fuel_users table have a field of "salt"?

altazar commented 9 years ago

A Database Error Occurred

Nope. After I added "salt" field, I logged in, and now have this error:

Error Number: 1146 Table 'fuel.fuel_categories' doesn't exist SHOW COLUMNS FROM fuel_categories Filename: /home/.../fuel/fuel/modules/fuel/core/MY_Model.php Line Number: 406

I can create "fuel_categories" but don't know the number and names of the columns it should have.

daylightstudio commented 9 years ago

It looks like you have an old database installed? Did you load the fuel/instlall/fuel_schema.sql file?

altazar commented 9 years ago

Thanks, now I've uploaded a fresh fuel_schema.sql and it works.

trysten commented 9 years ago

I believe this issue can be closed, though I think that the original poster was having the same issue i am. a similar URL and a blank page. I'm trying to figure out Vdebug right now, so I might have more useful information today.