Demo only works if site database does not have prefixes [#1135814]

I tried this on a D7 multisite installation where I use table prefixes. As you can imagine, I got a huge list of errors!

I then tried it on a stand alone installation and it works great.

This is not even worth trying to find a solution.

Just please be advised that this only works on stand alone databases with no prefixes.

Just a thank you folks for this module. It's just the thing for trying out different modules, configurations etc.

MrPhilbert

Comment	File	Size	Author
#7	1135814-7.patch	638 bytes	gaurav.kapoor

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

ajaysolutions CreditAttribution: ajaysolutions commented 1 May 2011 at 08:44

Priority:

Normal

» Major

I've just installed Demo for the first time, on a D7 site using table prefixes, and confirmed - I get a page of errors and snapshots won't get created.

This must be a very common occurance, rendering Demo unusable - I'm surprised it's only been mentioned once before.

Look forward to an update. Thanks for the module! :)

Comment #2

lahode CreditAttribution: lahode commented 11 July 2011 at 11:58

7.x-1.x-dev works fine for me with prefixed tables, I just replace
if ($prefixes[$plain_table] == $table_prefix || $prefixes['default'] == $table_prefix) {
by
if ((isset ($prefixes[$plain_table]) && $prefixes[$plain_table] == $table_prefix) || $prefixes['default'] == $table_prefix) {
at line 628 in demo.admin.inc, to get rid of the anoying errors.

Cheers

Comment #3

ajaysolutions CreditAttribution: ajaysolutions commented 28 July 2011 at 16:18

Status:

Active

» Needs review

Thanks for posting a suggested fix lahode. I've changed the status of this issue so it can hopefully be reviewed and patched.

Comment #4

70111m CreditAttribution: 70111m commented 28 July 2011 at 18:25

Subscribing

Comment #5

fedbccer CreditAttribution: fedbccer commented 14 August 2011 at 12:34

I had the same problem on D7
Applied patch in post #2 on demo-7.x-1.x-dev (2011-Feb-25)
Corrected the line 627 (not 628)
Tested the module creating a snapshot, installing a new module (Administration Menu), writing a page, and then reset

Now everything works fine
Thank you for the "demo" module and for the patch