Needs work
Project:
Chaos Tool Suite (ctools)
Version:
6.x-1.x-dev
Component:
Code
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Aug 2010 at 17:25 UTC
Updated:
19 May 2013 at 09:45 UTC
Jump to comment: Most recent file
Comments
Comment #1
merlinofchaos commentedAre you using the latest -dev? If not, please try the latest CTools -dev.
If so, please be more specific about what precipitated the message.
Comment #2
Starminder commentedI am - I think what was happening was I had the plug-in tools off. Turned those on, then off again and the message has gone away (at least for now). Will advise if I see it again, thanks!
Comment #3
Ivanhoe123 commentedHad the same issue, turned the module off then on and the message disappeared at least for now.
I'm using CTools 1.7
The message appeared when I enabled the module. Did not happen on a clean install though.
This is the full message:
Comment #4
merlinofchaos commentedYeah, there's a bug that makes that message appear when the module is enabled. It doesn't actually mean anything (the failure is because of the order things happen in during module install, and isn't actually fatal at all)
Comment #5
BadDrupalSucks commentedBut apart from that, there's a weird header, too. Any insight into this issue?
Comment #6
merlinofchaos commentedI'm really confused about the weird header. I don't have any idea where it's even coming from. It's not being output by CTools directly, there's nothing it does that is even like that. So it's got to be some interaction...with something...that's causing it. But what? I don't know. :/
Comment #7
BadDrupalSucks commentedIt's quite strange. It's definitely not Ctools directly, but I guess the other components. First, it was with the Custom Content Panes part of the Ctools package (as per jimsweb.tk), but now I'm finding that some other components cause this header too, even when Custom Content Panes is disabled. Am I the only one experiencing this issue? I've tried both -dev and -1.7.
Perhaps something to do with panels, or some other module?
Comment #8
BadDrupalSucks commentedWhen I do a new installation of drupal on a test site, and only enable the Ctools module with no other modules enabled, the header returns... Strange. No warning however.
Comment #9
Deleted Drupal Account commented@merlinofchaos: Can you look into this issue, please? It's coming up repeatedly, with different scenarios of installation. Will using previous releases of the Ctools package work for now? (both -dev (Aug 27) and -1.7 don't work)
Comment #10
merlinofchaos commentedI have looked into the issue.
I don't have any idea where the weird header is coming from. Most users aren't seeing this, and I've never seen it in over a dozen different installations. I'm unfortunately not psychic. I simply don't know where this is coming from, so please tell me what more I'm supposed to do?
Comment #11
BadDrupalSucks commentedAlright, then... I'll investigate myself. Maybe something with settings.
Comment #12
Deleted Drupal Account commentedHmmm. Could it be themes? What themes do you use? Garland seems to have some problems, so does bluemarine.
Comment #13
BadDrupalSucks commentedHi everyone,
Ok, I spent all afternoon doing tests, and here is my result.
The simple fix, which may not be recommended, is to downgrade to Ctools v.6.x-1.4. In this release, the header is just cosmetic in the module enabling page only, but it disappears.
Yay. Finally I can get to the fun part: actually using these modules (Ctools and Panels)
Pat
Comment #14
Deleted Drupal Account commentedd
Comment #15
BadDrupalSucks commentedComment #16
BadDrupalSucks commentedd
Comment #17
webwriter commentedSubscribe. Using latest dev, have turned all Ctools modules off then back on again, still getting the following:
# The plugin definition of ctools_access_ruleset cannot locate schema ctools_access_ruleset.
# The plugin definition of ctools_custom_content cannot locate schema ctools_custom_content.
# The plugin definition of panels_layouts cannot locate schema panels_layout.
This is appearing at the top of my Views list page at the moment, although I am seeing variations of it throughout the site.
Comment #18
zero1eye commentedI too am experiencing this issue.
Comment #19
zero1eye commentedI was able to fix this by first disabling all of the ctools modules, then performing a complete uninstall.
Then I went into the `system` mysql table and deleted all references to ctools.
Then I loaded the latest dev release, and re-enabled everything, then ran update.php.
All errors seem to have gone away. We shall see. :)
Comment #20
zero1eye commentedOh I also hit "save" on my theme a lot, not that I know completely what that does, but it felt like I was refreshing things, along with clearing the cache a lot... lol. Yep, I'm sure I sound like a n00b saying that but it worked. :)
Comment #21
summit commentedHi,
I first had not installed the Chaos Tools (CTools) Plugin Example module, then I got these messages. Then I installed the module and the messages went away!
greetings, Martijn
Comment #22
uwe_a commentedi tried #21 suggestion, did not work
facing this when using feeds_tamper module ( http://drupal.org/project/feeds_tamper )
Comment #23
jmary commentedI got this at enabling 6.x-1.8 and some panels stuffs. Maybe it will help to define the problem.
* The plugin definition of panels_layouts cannot locate schema panels_layout.
* The plugin definition of ctools_custom_content cannot locate schema ctools_custom_content.
* The plugin definition of stylizer cannot locate schema stylizer.
* The plugin definition of panels_mini cannot locate schema panels_mini.
Comment #24
jmary commentedComment #25
intyms commentedI have installed Advanced Help module. And everything is ok now.
By the way, i am using latest dev of ctools and panels.
Comment #26
b-prod commentedIn the file ctools/includes/export.inc, try to modify the line:
$schema = drupal_get_schema($table);to
$schema = drupal_get_schema($table, TRUE);This solves the issue, which seems to be caused by the cached schema data. I do not provide a patch because I am not sure what such changes means about performances.
Comment #27
lpalgarvio commented+1
Comment #28
tlangston commented+1
Comment #29
decibel.places commentedIn my case, the instability seemed to be caused by:* Adding the Ctools Page to a Feature* Exporting and Importing the page in Page Manager without using FeaturesOnce I went back to enabling it as a Feature the warnings went away(I had some issue originally with porting the Feature, which is why I tried just porting the Page...)nope
the Ctools page comes and goes, then I have to disable and re-enable the Feature for it to reappear
:-(
(later)
I have come to suspect the db is not finishing its processes, I have seen "MySQL has gone away" on Backup & Migrate pages...
(another day)
I've looked into this more and checked other duplicate issues such as #893174: Warning when you install the panels module but I tried the latest 6.x-1.x-dev for ctools from 2011-07-21 and I still get the error
It's not just cosmetic: my Page manager page displays for a while, then it disappears and it's gone from admin/build/pages until I re-enable the Feature with the page. Maddening. (and this was working fine on local dev, trying to figure out what is wonky on the remote server)
(a bit later)
I have created a separate issue #1254620: Custom page goes away on its own in ctools page manager
I suspect this is a problem with my server config and not a Drupal code problem at all. Will update that thread when I find a fix.
Comment #30
Remon commented@decibel.places, applauds for your efforts!
I'm facing the same issue with services:
The plugin definition of services_ctools_export_ui cannot locate schema services_endpoint.Comment #31
decibel.places commentedfound the fix and posted it here #1267954: Feature dependencies can break schema in ctools page manager
Comment #32
fugazi commented# 26 worked for me. I hope that the hack is ok and no more problems occur because the module was modified.
Comment #33
purna_dey commentedThanks B-Prod!!!
#26 It works for Me!! Thanks
Comment #34
klokie commented#26 works for me too. Thanks
Comment #35
sblommers commentedVery good! #26 works like a charm, i'm using 6.x-1.9 ! I had trouble after running update.php without clearing the cache first from restoring a database dump (some views dissappeared because they seemed broken by this). I added #26 to 1.9 and everything works like a charm i can now restore the database even when forgetting to delete from cache table before update.php.
Comment #36
sblommers commentedAdded a patch for 6.x-1.9 for those who us who is lazy, this won't be fixed for ctools but for those who cannot upgrade this might come in handy
Comment #37
claudiu.cristeaI can confirm the bug and also the fix from #26. Moving to branch and marking as "needs review".
Note: The site needs a cache clear all after the patch is applied.
Comment #38
claudiu.cristeaSorry to say that #26 is causing other error:
Still not resolved.