Upgrade from 5.x to 6.x: user relationship blocks tables are not created

Have you tried to uninstall the UR after disabling it as well? If not, it will not attempt to create missing tables when you re-enable it.

Looks to be taken care of, closing.

I just upgraded from 5.x to 6.x and I'm getting this same error for the relationships modules.

user_relationship_blocks' doesn't exist query: SELECT * FROM user_relationship_blocks WHERE bid = 'actions' in \modules\user_relationships\user_relationship_blocks\user_relationship_blocks.module on line 327.

I've tried the above suggestions, still no joy. I followed the instructions for the upgrade, got the most recent 5 version before upgrading to the most recent 6 version of UR. Is is possible to manually install the missing table? Thanks

This is being worked on to enable table creation when upgrading from 5.x to 6.x, actually... As a workaround, if you disable and uninstall UR-Blocks, then install again, the table will be created.

I understand how to disable UR blocks, but when you say "uninstall UR-Blocks", do you mean just delete it from the modules directory? Then add it back? I've tried that, maybe I'm missing a step or just not doing it correctly. Thank you for the prompt response.

There should be an 'uninstall' tab on the modules page, which lets you delete all data defined by a module.

The only item related to UR in the uninstall tab is "UR Migrate Buddylist2". Nothing else is listed.

Can I manually get it "uninstalled"? This is pretty much the last item I have to overcome before I can upgrade my site to 6, otherwise I'll have to stay on 5.

If you try executing this query (pls back up beforehand):

delete from system where name='user_relationship_blocks';

this should make Drupal forget that you had the module. Then it will install it anew. If that doesn't work, it will be easiest to create the needed table, actually:

CREATE TABLE IF NOT EXISTS user_relationship_blocks (
  bid varchar(255) NOT NULL default '',
  size int(10) unsigned default '10',
  sort varchar(255) default 'newest',
  get_account longtext NOT NULL,
  PRIMARY KEY  (bid)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

Pls mind the table prefix if your site uses it.

Thanks for the ideas, I will post back when I get a chance to try this and let you know how it goes.

A fix for this has been committed earlier, so a -dev release of 6.x will take care of table creation. See also #575506: Error message during upgrade 5.x-2.x.dev to 6.x-1.0-rc2. Please reopen if further support is needed.