Simple Access Module Issues

We have also encountered this situation. After running the "Deactivate" recommended in the documentation, we ended up with access to all content denied or a blank submission page, depending on whether there was a check on the module administration page for Simple Access. So far, we have changed "simple_access" to "all" as suggested by your posts and also encountered the issue with new content not appearing on the front page.

We have since dropped the two simple_access_* tables from the database, removed the simple_access_enabled variable from variables table, deleted the simple_access/ directory and its contents from our modules/ directory, removed the reference to the module in the system table, removed a reference called simple_access_id from the sequences table, ...

Needless to say, it should not require this much interaction, and we still haven't completely solved the issue.

The lines that appear to be intended to set up for and clean up after simple_access read:

function simple_access_initialize($initialize = TRUE) {
  if ($initialize) {
    // delete universal view grant
    db_query('DELETE FROM {node_access} WHERE nid = 0 AND realm = "all"');
    // set all nodes to viewable
    db_query("INSERT INTO {node_access} (nid, gid, realm, grant_view, grant_update, grant_delete) SELECT nid, 0, 'simple_access', 1, 0, 0 FROM {node}");
    variable_set('simple_access_active', TRUE);
    drupal_set_message(t('The database has been configured and simple_access module is ready for use.'));
  else {
    // delete all simple_access stuff
    db_query('DELETE FROM {node_access} WHERE realm = "simple_access"');
    // re-enable universal view grant
    db_query('INSERT INTO {node_access} (nid, gid, realm, grant_view, grant_update, grant_delete) VALUES (0, 0, "all", 1, 0, 0)');
    variable_set('simple_access_active', FALSE);
    drupal_set_message(t('The database has been re-configured. You should now visit %modules to disable the simple_access module itself.', array('%modules', l('the modules page', 'admin/modules'))));
  }
}

From this, it appears the cleanup should be as simple as removing all the "simple_access" records in the node_access table, create a new record with (0, 0, "all", 1, 0, 0), and remove the "simple_access_active" variable.

We just barely created the new record in node_access table, and it appears to have fixed the issue for us.

This code should have (but apparently did not) run from the Deactivate feature, and even if it had, it would have left a /lot/ of mess behind. Hope this helps.