Error on install [#1516528]

When I installed the latest dev version. It gave me a Table Exists error exception (Line 652 from schema.inc). I figured it was from the old version of NO so I double checked the DB and there were no entrys left from the old version and I had completed the install so its weird that it would find an existing table. I will take a screen shot and better instructions to recreate if you guys can replicate.

Comment	File	Size	Author
#3	nodeownership-table-removed.png	63 bytes	Donovan

Comments

Comment #1

vyasamit2007 commented 6 April 2012 at 03:56

You might have disabled the module but didn't uninstalled before you install a dev version. Please send some screenshots to understand the problem in better way, they will be useful. Also send the steps you followed to uninstalled and install a dev version. I'll install the dev module and let you know of this kind happens.

Thanks!!

Comment #2

grasmash commented 11 June 2012 at 20:16

Status:

Active

» Closed (works as designed)

Closing due to lack of response.

Comment #3

Donovan commented 8 March 2014 at 18:33

Issue summary:

View changes

Status	File	Size
new	nodeownership-table-removed.png	63 bytes

I am encountering this issue as well. Here is the error:

DatabaseSchemaObjectExistsException: Table nodeownership already exists. in DatabaseSchema->createTable() (line 657 of /home/.../public_html/includes/database/schema.inc).
The website encountered an unexpected error. Please try again later.

Please see attached screenshot of tables from phpmysql. As can be seen, the node ownership table is missing -- yet the error persists.

The problem is with the dev version.

Any suggestions on how to correct this problem is appreciated.

Thanks!

Comment #4

Donovan commented 4 March 2014 at 05:52

Status:

Closed (works as designed)

» Active

Changing status to open based on most recent comment.

Comment #5

sja1 commented 29 December 2014 at 20:05

I just downloaded the latest dev, and the module folder contains a "7.x-1.0" subfolder which contains a second copy of the module. Because there are two complete copies of the module files (one in /nodeowership, and the other in /nodeownership/7.x-1.0) the error probably occurs because drupal tries to install both copies. When it tries to install the second copy, it finds that the tables already exist as they were created during installation of the first copy.

Furthermore, though the module files are not identifical, they are both dated march 28 2011 12:27, which is much earlier than the release date shown on drupal.org (Oct 2013).

Could the maintainer please create a new version of the dev release? That should fix the problem.

Comment #6

sja1 commented 29 December 2014 at 20:06

Status:

Active

» Needs review

Changing to needs review. There is no patch, but the solution doesn't seem to require a patch.

Comment #7

sja1 commented 29 December 2014 at 20:22

In the meantime, for anyone who wants to download a properly packaged dev version, if you have drush you can use the following command:
drush dl nodeownership-7.x-1.x --package-handler=git_drupalorg