Closed (duplicate)
Project:
Drupal core
Version:
6.20
Component:
database system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Dec 2010 at 05:16 UTC
Updated:
22 Dec 2010 at 02:55 UTC
Jump to comment: Most recent file
Comments
Comment #1
mscharley commentedTake 2 on the diff, this one should apply.
Comment #2
mscharley commentedTake 3...
Comment #3
mscharley commentedLast attempt at the patch, then someone will have to tell me why it won't apply if it still won't.
Comment #5
Juan C commentedSubscribe. I have a multisite setup with WSOD upon upgrading from 6.19 to 6.20.
I have to reuse old 'includes' folder to make it works.
Comment #6
mscharley commentedAnother attempt at a working patch. This one works locally, so I'm stumped if it doesn't work.
To #5, Juan, this shouldn't cause WSOD's, just weird behavior in a few modules.
Comment #7
mscharley commentedComment #9
mscharley commentedCan someone please look at the patch and tell me why it's not working? It applies locally, and I'm new to the Drupal patch system.
Comment #10
mscharley commentedAttempting to use a patch generated by git rather than mercurial as a last ditch effort.
Comment #12
mscharley commentedThis is up to the review stage, I just can't figure out how to get my patch in a state that the Drupal bot can patch against 6.20. It works locally though against a fresh copy of the tarball.
Comment #13
mscharley commentedThis is up to the review stage, I just can't get my patch to a state where the Drupal bot will apply it. It works locally though against a fresh copy of the tarball for 6.20.
Comment #14
mscharley commentedDuplicate of #286986: MySQL: SHOW TABLES LIKE database.tablename doesn't work.
Like my patch better, but lets not pollute things more than they need to be.