AJAX HTTP 200 error + postgreSql not listed as a DB during install [#1342958]

Using the off-site tarball instead of drush - I ended up with errors at the 'Import Terms' step...

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://127.0.0.1/recruiter/install.php?profile=recruiter&locale=en&id=2&op=do StatusText: OK ResponseText: Home | a-i-r-Jobs @import url("http://127.0.0.1/recruiter/modules/system/system.messages.css?lup16c"); @import url("http://127.0.0.1/recruiter/modules/system/system.menus.css?lup16c"); @import url("http://127.0.0.1/recruiter/modules/system/system.theme.css?lup16c"); @import url("http://127.0.0.1/recruiter/modules/system/system.base.css?lup16c"); @import url("http://127.0.0.1/recruiter/misc/ui/jquery.ui.core.css?lup16c"); @import url("http://127.0.0.1/recruiter/themes/seven/jquery.ui.theme.css?lup16c"); @import url("http://127.0.0.1/recruiter/modules/overlay/overlay-parent.css?lup16c"); @import url("http://127.0.0.1/recruiter/modules/comment/comment.css?lup16c"); @import url("http://127.0.0.1/recruiter/modules/field/theme/field.css?lup16c"); @import url("http://127.0.0.1/recruiter/modules/node/node.css?lup16c"); @import url("http://127.0.0.1/recruiter/modules/user/user.css?lup16c"); @import url("http://127.0.0.1/recruiter/profiles/recruiter/modules/views/css/views.css?lup16c"); @import url("http://127.0.0.1/recruiter/modules/system/system.admin.css?lup16c"); @import url("http://127.0.0.1/recruiter/modules/system/system.maintenance.css?lup16c"); @import url("http://127.0.0.1/recruiter/profiles/recruiter/modules/ctools/css/ctools.css?lup16c"); @import url("http://127.0.0.1/recruiter/profiles/recruiter/modules/date/date_api/date.css?lup16c"); @import url("http://127.0.0.1/recruiter/themes/seven/reset.css?lup16c"); @import url("http://127.0.0.1/recruiter/themes/seven/style.css?lup16c"); Home Installation tasksChoose profile(done)Choose language(done)Verify requirements(done)Set up database(done)Install profile(done)Configure site(done)Import terms(active)Finished SQLSTATE[42S22]: Column not found: 1054 Unknown column 'recruiter_t.vid' in 'where clause'

The error doesn't allow the install script to finish, and as noted at the end of the errors, there is not a column for 'recruiter_t.vid'. Install attempted on a Win7 x64 dev server, running recruiter in a sub-directory, with the following:
mySql - 5.1.41 (since postgreSql wasn't a select-able option)
postgreSql - 9.1
php - 5.3.1
Apache - 2.2.14

Comments

Comment #1

klausi

he/him||they/them

German

🇦🇹 Vienna

CreditAttribution: klausi commented 1 December 2011 at 10:35

Looks like the taxonomy csv import fails. Did you use any DB table prefix?

Postgres should be supported as for any other Drupal installation. Are the PHP PDO Postgres Drivers installed?

Comment #2

HumanTex CreditAttribution: HumanTex commented 30 December 2011 at 16:52

Wow... your post fell through the 'e-mail crack' on my end - sorry for the delay in answering.

I see there's a prefix of "recruiter_" in the tables, but I honestly don't remember if I specified it, or if ended up that way as a default install (??). I could certainly try a re-install without it to verify if that's the cause. I also wonder if it being installed to a sub-directory and not to 'root' could cause problems.

Not a real big deal on the postgre issue for now - since it would be on a dev server initially - but I can see it as an advantage to use it on a higher volume site if it were required, so I wanted to give it a try in that configuration. It simply didn't show up as an install option, however that doesn't mean that my postgre setup is correct for Drupal use either. As for PHP support, a quick check shows PostgreSQL(libpq) v.8.4.1 is enabled and active, but PDO wasn't... and likely why it failed to list it.

Comment #3

dasjo

he/him

German

Zurich

CreditAttribution: dasjo commented 30 December 2011 at 19:24

Priority:	Critical	» Normal
Status:	Active	» Postponed (maintainer needs more info)

Comment #4

HumanTex CreditAttribution: HumanTex commented 31 December 2011 at 11:34

I got PDO installed and enabled, then Recruiter freshly re-installed (without any table prefix) on Postgre. The only install issue was at the end of the 'terms' import... it hung the browser at the end of the last set of terms, and was extremely slow all throughout the DB and terms setup. I started Solr, launched the site, and got the frontpage with a full set of confirmations on all the imports, so it may have hung, but I presume it did finish correctly.

There are still other post install errors, but I'll split them off into another issue.