Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EE Version 2.5 Install Issue #5

Closed
ghost opened this issue May 30, 2012 · 2 comments
Closed

EE Version 2.5 Install Issue #5

ghost opened this issue May 30, 2012 · 2 comments

Comments

@ghost
Copy link

ghost commented May 30, 2012

On a fresh install of EE, version 2.5, been getting an error when I try to do an installation of the extension.

I believe this is the same error as http://devot-ee.com/add-ons/support/draggable/viewthread/3031

A Database Error Occurred

Error Number: 1364

Field 'settings' doesn't have a default value

INSERT INTO exp_extensions (class, method, hook, priority, version, enabled) VALUES ('Draggable_ext', 'update_order', 'sessions_end', 10, '1.3', 'y')

Filename: codeigniter\system\database\DB_driver.php

Line Number: 330


Thanks!

@kevinthompson
Copy link
Owner

Sorry for the delay in responding to this. Are you still experiencing this issue? I've just gotten around to setting up a local development environment for ExpressionEngine after being away from it for several months and Draggable seems to install fine on a fresh EE 2.5.2 installation.

Please let me know if you're still having issues with this.

@ghost
Copy link
Author

ghost commented Jul 26, 2012

Hey Kevin,

We finally uncovered what the problem was. Apologies for the delay on our end as well. So, our DB was running with STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION. We experienced odd behavior with a few other plugins that lead us to discover this.

It is our guess that on a lot of shared hosting services, none of these modes are set in MySql which is why in the past we had no problems with the plugin. In this case, we were not using a shared hosting site.

There was two possible solutions for this. Disable all modes globally, or per session. We opted for the later and all is good.

Thanks for the response! Hopefully somebody finds this useful.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant