Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
After installing and enabling Schema on Drupal 7, I get an http 500 error when I choose the Admin configuration page or when I try to access the schema under structure. I have tried both the beta and devel build and get the same results. When I uninstall schema, everything works fine. There is nothing recorded in the error log regarding this event.
Comment | File | Size | Author |
---|---|---|---|
#4 | schema-1850196-autoslave_incompatibility-4.patch | 3.78 KB | GuyPaddock |
Comments
Comment #1
Dave ReidPlease test again with the latest 7.x-1.0-rc1 release. I'm unable to replicate this bug so far.
Comment #2
GuyPaddock CreditAttribution: GuyPaddock commentedVerified.
After upgrading to MySQL 5.6 with PHP 5.3.3, I'm also seeing this behavior. I get the following error:
Fatal error: Call to a member function inspect() on a non-object in modules/contrib/schema/schema.module on line 396
Have tried to disable and uninstall Schema, then enable it again. Always the same behavior. When Schema is disabled, pages load fine. Even tried latest Dev.
Comment #3
GuyPaddock CreditAttribution: GuyPaddock commentedOkay, looks like
schema_dbobject()
is returningNULL
. We're using autoslave with MASTER->SLAVE replication, so my guess is it isn't loading the right database class.Here's our database config:
Setting down to "major" since this only affects Auto Slave users like ourselves.
Comment #4
GuyPaddock CreditAttribution: GuyPaddock commentedAttached is a patch to make Schema able to work with Auto Slave.
Comment #5
GuyPaddock CreditAttribution: GuyPaddock commentedSetting to NR.
Comment #6
dobe CreditAttribution: dobe commentedI am experiencing the same problem. The UI is not accessible. No errors. I do not have auto slave though either.
Comment #7
ybabel CreditAttribution: ybabel commentedworked for me
Comment #8
coreyp_1 CreditAttribution: coreyp_1 commentedThis patch (#4) absolutely solves my problem on our production database. Thank you, GuyPaddock!!!
Comment #9
greggles@dobe, @ybabel, @coreyp_1 - are you using a slave database at all? Can you post a redacted copy of your $databases array like GuyPaddock did? That would help to understand the bug and therefore understand if the fix is right.
Comment #10
dobe CreditAttribution: dobe as a volunteer commentedI'm going to be honest. I don't remember this issue. Or the environment that it affected.
Comment #11
joachim CreditAttribution: joachim as a volunteer commentedPatch needs some clean-up work:
Surplus blank line between @params.
What's Auto Slave (I googled and I found a band...?)
Why not make 'default' the default for the parameter then, rather than NULL?
Missing full stop.
Whitespace.
This looks like an unrelated fix.
Lots of
tags that shouldn't be here.
Also, first paragraph of docblock should be a single line.
Please break this up into assignments to meaningful variables. I can't follow this at all.
More missing full stops.