When I try to save content (a custom type I've created) I get
PDOException: SQLSTATE[HY000]: General error: 1030 Got error -1 from storage engine: INSERT INTO {field_data_field_tags} (entity_type, entity_id, revision_id, bundle, delta, language, field_tags_tid) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6); Array ( [:db_insert_placeholder_0] => node [:db_insert_placeholder_1] => 4 [:db_insert_placeholder_2] => 4 [:db_insert_placeholder_3] => plants [:db_insert_placeholder_4] => 0 [:db_insert_placeholder_5] => und [:db_insert_placeholder_6] => 1 ) in field_sql_storage_field_storage_write() (line 424 of /home/joeshmoe/public_html/site/modules/field/modules/field_sql_storage/field_sql_storage.module).
The content still shows up in the dashboard but when I try to view it I get
Notice: Undefined property: stdClass::$comment_count in comment_node_page_additions() (line 724 of /home/joeshmoe/public_html/site/modules/comment/comment.module).
Regular pages and articles save and display properly. This is a fresh install of 7.9 on hostgator with no extra modules installed.
Thanks
Comments
Yuk. The db table is corrupt.
Yuk. The db table is corrupt. Clear caches. If that does not fix it, try creating the custom content type again, and see if it is working. If it is delete the old one if you have not much to lose. If you have content to lose, maybe think of ways to migrate it to the new content type.
If it does not fix things, obviously it will get more of a problem. If it was a database with lots of content you would have a bigger problem. As is, I would seriously try a fresh install with fresh database. Only takes 5 minutes plus the time to recreate your content type and other settings. Maybe in the middle of the night when the server is quiet, as I would suspect some problem with the hosting not giving the resources you need.
If you had server access I would say restart mysqld server first. But I guess that is not an option on shared hosting.
Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors
Well it turns out I needed an
Well it turns out I needed an .htaccess file in public_html with the following
# Use PHP 5.3
Action application/x-hg-php53 /cgi-sys/php53
AddHandler application/x-hg-php53 .php
# Disables existing custom php.ini and
# tells it to use the default PHP 5.3 php.ini instead.
suPHP_ConfigPath /opt/php53/lib
order allow,deny
deny from all
Without it the fantastico install was not creating a working drupal site. Not so automated after all.
Thanks for the help.
Ah. Thanks for the update. I
Ah. Thanks for the update. I had not come across x-hg-php and have never used it with Drupal. There are plenty of complaints about fantastico creating more problems than it solves, for the sake of saving 5 minutes.
Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors