Panels 6.x-3.4 breaks Views

same problem here.

Attempted to recreate front page view starting from scratch and came across these issues:

I can create panel without issue until attempting to add content into panel.

1) I can select default drupal content (i.e. Who's online, Recent Blog Posts, etc.), custom content (i.e., previously created mini-panels) or a freshly enabled front_page view, but when I click Finish it freezes and nothing happens.
2) When I click Close Window the content shows up in the layout designer for default drupal content. Any custom views or mini panels show only "No Info"
3) Without clicking Update or Update and Save, I can click the Save button and the content remains in the panel, but if I click either Update or Update and Save, the content disappears.
4) Alternatively, sometimes when attempting to add content there is no Save button at the bottom of the page, only the Update or Update and Save. If i immediately choose a different tab (i.e., Summary or Layout) and then choose the Content Tab again, I am finally presented with the option to Save.

When I set the homepage to be this view it shows up partially. In this situation I added the drupal activity pane "who's new" and a custom mini panel I created. The "who's new" block shows up fine, but the custom mini panel has no content. The title shows up but no content.

I have not fully tested the mini panels to see what issues arise there.

me too subscribing.

same here.

I too have the same issue, had to go back to prior version and ctools. How do we fix this security updates with these modules. Will there be a new version fix rolled out soon

they are working on it..

Is there anyone in this issue who is not using the Views Bonus Pack? For people who are, it seems likely your problem is http://drupal.org/node/804336 (and it contains a hack to help you work around it). If you are not we need to know so we can tell if there are multiple problems here or not.

After the upgrade (yesterday), trying to update a panel to add some extra content and I am stuck like #2:

I can select default drupal content (i.e. Who's online, Recent Blog Posts, etc.), custom content (i.e., previously created mini-panels) or a freshly enabled front_page view, but when I click Finish it freezes and nothing happens.

I am Not using the view bonus pack module.

i am not using the bonus pack either.

same problem, not using the bonus pack.

Same here. I'm using 'domains' - killed everything.

I AM using View Bonus Pack along with Hierarchical Select for Views too. 6x-3.3 for nicely. Panels and CTools Security upgrade just did not go well so I rolled back to prior version and things work again. However I do get the security update notification but our site is live so we cannot have it down as we have use CTools, Panels and Views extensively

Happy to provide more info is someone has a question.

not using views bonus pack either.

@laroccadahouse Looks like #804198: Ajax doesn't work reliable using Safari. Especially (1) & (2).

I have same problems as described in #2. And i'm not using "View Bonus Pack".

subscribing!

I have this issue, I have Panels 6.x-3.4, with mini-panels and panel-nodes also enabled.
No views bonus pack here.

Found the same issue here today also, in that upgrading chaos tools and panels broke my mini-panel.
I've also tried upgrade only panels (and then running update.php) as well as only C-tools (and then running update.php) and had broken mini-panels.

My only resolution was to step back on both versions. Interestingly, I needed to delete the 2 module folders before extracting the old modules into them before I was able to have a successful view of my panels again.

I recommend taking down the updates to both panels and c-tools modules until the issue is understood and resolved. It will save a lot of man-hours for the folks out there who haven't upgraded these modules yet.

@jjmackow: Considering those were security updates and there's people using them with no issues, I don't think that's a practical idea.

Michelle

@michelle: I take your point, but given the number of issues reported since May 20th, the release of the 2 modules is causing quite a bit of lost time by many site developers. Perhaps they should be release candidates or beta versions, but clearly they aren't ready for prime time. I lucked out and lost only 1 - 2 hours, but another gentleman's post noted losing 8 hours of time before going back to the earlier versions.

Since we have the knowledge now of the fact that there are issues, it is a responsible move to make developers aware of the fact that there is a high probability that the updates will cause problems. This is how I interpret the use of the suffix, 'Release Candidate' or Beta for that matter.

I do respect your point of view though.

jj

No question, these release issues are causing lots of extra cycles and overhead, definitely painful for many sites out there. I would agree the security purpose of the release of both modules puts creates a bind, hard to go back to previous release and sustain security exposure, and not possible to move forward with new release until these issues are fixed.

Per @jjmackow, any way to take the last working release and just apply security patches only, as an interim measure? Then leave 6.x-3.4 as a release candidate while remaining show-stopper issues are worked out.

Bob

Ok, this issue is ultimately very frustrating for the us, because it's really hard to pull useful information out of it.

1) The initial post was not a very useful bug report
2) The first response seems to be something that isn't even related
3) "Me too" posts aren't very useful. Worse, they're less useful here because by response #2 there's two different scenarios, and only 1 or 2 of the "me too" posters are saying which scenario they're still getting.

So far only #2 and #8 actually contain useful information. #14 suggests that those two problems may indeed be the javascript aggregation issue. It's hard to say.

As for #17, PLEASE, don't derail an issue talking about whether or not a release is up. Issues need to be clean.

What I'm left with on this issue is that I have no idea what to even *look* at to see what people are experiencing. So thanks to everyone who posts little to no useful information, or actively seems to want to derail the topic. Way to go. I'd like to figure out what's wrong and fix things, but I don't even know where to start now.

I'm going to mark this a dup based on #14. If you've got actual, reproducible, identifiable issues, please post new ones so I can address them.

I rolled back both versions for the moment so our site would not be down. That worked without issue (of course we seee security update notificatiosn but obviously that is to be expected.)

We are using the frontpage view along with the panels style of one top two below.
Panels said it was missing mini-panels and I saw the temporary fix for the missing mini-panels at http://drupal.org/node/804336
but we were not sure if this was a good idea or if this will cause Ctools to be unhappy and we did not want to make a mess for ourselves if that is the case.

We are also using mini-panels with user profile and content profile.

I'm sorry venus; the only problem I saw that you had that I could concretely identify was the missing function call that the bonus pack is using. Do you have some other problem that isn't related to that, because I can't tell.

#2 is definitely due to js aggregation. I had the same problem some time ago and turning js aggregation off fixed it. I just tried turning it back on and can replicate the same problem. So if anyone is having that problem, just turn js aggregation off under performance. The missing function call with bonus pack also has an issue with a fix.

I agree with merlinofchaos that this issue is confusing. I'm trying to lend a hand with testing but it's hard to tell what the issues are when they're all mixed into one issue like this.

Michelle

@ #21:

We are experiencing a problem with the 3.4 release. I cannot say - for obvious reasons - wether it's the same as OP.

The specific issue for us is as following:

* We have several panels with embedded Views Panes and Views Blocks. The problem - for us - is with a specific type of pane: The summaries used as links to news archive (se http://ting.dk/tingconcept/news right sidebar).
* The pane is setup to print "Summary, sorted ascending", "Show" when no argument is given. That is also whats happening with Panels 3.3
* When upgrading to Panels 3.4 and the corresponding release of CTools the panes output changes to a long list of full nodes with title and body, sorting ascending.

Please let me know what other pieces of info you need. If needed I can give you a dump of the site, if it's helpfull.

@ #25

We have currently rolled back to 3.3 while we are investigation. I can prob. set up a clone site with the 3.4 release of Panels.

This issue is no longer relevant, 3.4 is dead. Stop investigating, and update to 3.5.