Hi,

I just tried to install the newest version of Open Atrium (7.x-2.4.3). But I got this error message

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: http://noob.company/install.php?profile=openatrium&locale=en&db_import_filename=/w

...

Home Installation tasksChoose profile(done)Choose language(done)Verify requirements(done)Set up database(done)Choose installation method(done)Install profile(active)Configure siteVerify Apps supportInstall AppsFinished SQLSTATE[42000]: Syntax error or access violation: 1059 Identifier name 'openatrium_search_api_db_database_node_index_oa_section_ref_title' is too long

I think it's something with the identifier name. Can I configure this in my MySQL Database? Or is it another problem?

Comments

dpoletto’s picture

dpoletto CreditAttribution: dpoletto commented

65 chars...so over the consent limit of 64 chars (see here if your MySQL is 5.6)?

mpotter’s picture

mpotter CreditAttribution: mpotter commented

Maybe you tried to use a database prefix? Looks like your table name starts with "openatrium_". Try getting rid of the table prefix or choose something shorter given the MySQL restrictions.

sxbxstxxn’s picture

sxbxstxxn CreditAttribution: sxbxstxxn commented

oh my god... thanks... didn't notice my prefix... but this would be good to know BEFORE I install it... maybe as a note or something when it asks me if I want a prefix ;)
Tanks guys...

hefox’s picture

hefox CreditAttribution: hefox at Phase2 commented

To rephrase what is happening, search api exports table names that it uses for indexing content. The table names were made on a pre-fixless database so comply with length requirments there, but on a site with database prefixes in use (which is a perfectly acceptable practice), this makes the prefixes too long. The current solution is to use shorter prefixes or override the search filter with shorter names. The alternate solution would be to change how search api works, but that is likely to be a slow process.

JKingsnorth’s picture

JKingsnorth CreditAttribution: JKingsnorth commented

We should close this issue here and open one against the Search API module then since it is not an OA-specific issue?

hefox’s picture

hefox CreditAttribution: hefox at Phase2 commented

I think I'm part of at least one issue that deals with it -- the whole table names being part of the export is ..problamatic. @mpotter, want to keep this open?

mpotter’s picture

mpotter CreditAttribution: mpotter commented
Status: Active » Closed (won't fix)

Don't think we need this open for Atrium as it's a larger issue with Search API.