when trying to edit views (Advance profile kit)
im here:


Click on:


and i im here:


with this:

Fatal error: Call to a member function set_display() on a non-object in /sites/all/modules/ctools/views_content/plugins/content_types/views_panes.inc on line 430

Please advise .. im no programmer (0 in php) and very new to drupal.

thanks in advance.


jannalexx’s picture

Category: support » bug

same issue in Advance profile kit 6.x-1.0-beta1 panel.
probably Advance profile kit beta1 issue after panels/ctools update. beta2 has to be tested but there are some other things we have to consider about beta1->beta2 update http://drupal.org/node/579830 (author pane 1.x / advanced forum 1.x compatibility).

merlinofchaos’s picture

Status: Active » Fixed

This is fixed in -dev. I thought I got all these before 1.2. =(

seanmagnan’s picture

I am having the same problem and I'm not sure where to go or how to work around this. I'd really like to use these modules. I am pretty good with php, can I get some instruction on this matter or is there an update for this?

elle.santos’s picture

Hi, same problem. Do we have an update on this?

merlinofchaos’s picture

As I stated in #2, this is fixed in the -dev version.

seanmagnan’s picture

is there a url where I can get the dev version, I'm sorry I know you guys are busy but I'm not sure where to go to get the patched version and the one posted in the modules section of drupal.org says -beta2. I've reinstalled with this a couple time and I'm still getting the same thing. Your help is greatly appreciated and I thank you for your efforts in creating an awesome plug-in

Platinum’s picture

wrong post sorry

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

seanr’s picture

Component: Miscellaneous » Code
Status: Closed (fixed) » Active

Could we possibly get this in an official release? Why is the dev release three months newer (with, I presume, all kinds of critical bug fixes) than the official release? The trouble is that drush by default gets the official one and people won't know to specify the dev version.

sdboyer’s picture

Version: 6.x-1.2 » 6.x-1.x-dev
Status: Active » Closed (fixed)

I think you misunderstand how the release system works. -dev is always the same or newer than an official release...because it's -dev.

We're working on rolling a new official release. I really wanted to do it this week, but I came across a few really nasty things that I'd like to resolve, and convinced merlinofchaos to wait. Expect one very soon, though.

Also, it's totally inappropriate to reopen the issue. The problem has been fixed, ergo the issue is closed. I'll update the version number for clarity, though.

seanr’s picture

FWIW, I think you misunderstand how people use modules. Most people don't use dev versions of modules on productions sites because they've been rightly warned by developers. When there's a fatal error in a module's release, I think it's somewhat irresponsible of developers to not at least post a release that fixes that fatal error. That was my reason for reopening the issue.

That said, it is working well now. Thanks for posting a fixed release.

merlinofchaos’s picture

When you can choose between being irresponsible by making a new release or being irresponsible by not making a new release, all you can do is bear the slings an arrows of people who like to complain about free stuff.