refinerycms: New Project doesn't load Home Page and can't add pages.
When I first install the project and go to localhost:3000, the server redirects me to the standard 404 page. I’m able to navigate to localhost:3000/refinery and access the admin pages. When I go to add a new page I get this error.
SQLite3::ConstraintException: refinery_page_translations.refinery_page_id may not be NULL: INSERT INTO "refinery_page_translations" ("created_at", "custom_slug", "locale", "menu_title", "refinery_page_id", "slug", "title", "updated_at") VALUES (?, ?, ?, ?, ?, ?, ?, ?)
There was also another person on the IRC that was having the same issue. I’m running on OSX 10.9 if that may be an issue also. I can provide more info if needed. Thanks.
About this issue
- Original URL
- State: closed
- Created 11 years ago
- Comments: 68 (38 by maintainers)
Commits related to this issue
- remove :null => false condition on reference to parent model in translation table migration to fix refinery/refinerycms#2450 — committed to globalize/globalize by shioyama 11 years ago
- add inverse_of option to translations as suggested in refinery/refinerycms#2450. — committed to globalize/globalize by shioyama 11 years ago
- remove :null => false condition on reference to parent model in translation table migration to fix refinery/refinerycms#2450 — committed to globalize/globalize by shioyama 11 years ago
- add inverse_of option to translations as suggested in refinery/refinerycms#2450. — committed to globalize/globalize by shioyama 11 years ago
- fixes refinery/refinerycms#2450 but requires globalize to be updated with globalize/globalize#296. — committed to shioyama/refinerycms by shioyama 11 years ago
- add inverse_of option to translations as suggested in refinery/refinerycms#2450. — committed to globalize/globalize by shioyama 11 years ago
- add inverse_of option to translations as suggested in refinery/refinerycms#2450. — committed to globalize/globalize by shioyama 11 years ago
- explicit expose locale field globalize gem add a validation for locale field in translation table we should be explicit expose locale more details see #140 — committed to xiaods/refinerycms-news by deleted user 11 years ago
If it’s possible, could you try dropping the db and running
rake db:migrate db:seed? Does that produce the same error?