Panels - Loading...

I'm sorry that I can't provide better help, but there is just no information what so ever in this post that would allow me to even begin guessing what's wrong. It seems highly likely that this is something local to your particular setup, and I can't do anything about that.

Until there is some technical information provided about the error that allows some form of debugging, I will close this issue. Feel free to open it again once there is new information.

I am having this problem too, with no helpful information to give???

I too was having this problem, but found out how to solve it!

I am using D7, Views 3 and Panels 3.0-alpha3

When I initialled installed and set up my first Pages, I had the module Overlay enabled. Since then I had disabled Overlay to save and resources.

I was doing some updates to the Views Module from Views 3.0-rc3 to Views 3.0 (that might be completely unrelated, but just some info) which is when I noticed my Panels page had stopped working.

I solved the problem by re-enabling the Overlay module and the overlays in the Panels module worked again!

I hope this helps!

Thanks for reporting this, IamOnStage.

I am having this same problem and for the life of me I can't figure out how to fix this. Unless I get all my settings right the first time when creating my panels, I cannot go back to change anything.

I am using D7, Views 3, and Panels 7.x-3.0-alpha3

same for me

Thanks for your comment (#3).
I had exactly the same trouble where attempts to add content or change visibility rules were met by a page continually attempting to load... but never getting there!
I too had turned off Overlays to save precious resources - especially as enabling modules keeps hitting the PHP memory_limit.
So I've had to turn Overlays back on, and sure enough the add content (and add visibility rule) panel loads.
Bit of a shame you can't turn off the Admin Overlays (making Admin pages load faster) without wrecking the Panels functionality!
Regards,
John

That's really weird that turning *off* the overlay breaks it. I often use this stuff without overlay (it drives me crazy) so that can't be the only thing going on here.

I tried messing around with the overlays but the problem persisted. Installed the update for panels today and it seems to be working fine, we'll see. One thing that was strange was sometimes if I switched browsers 'Firefox > Chrome' it would work once or twice, but then would stop again.

Hopefully this update fixes it.

enable and disable overlay solution

Will this be added in the stable version any time soon?

I updated to the dev version, but that made no change for me. I have disabled all modules I don't think I need to see if there was any conflict, but that made no different. It's very hard to see what is wrong, and why the plugin just hangs when trying to add ore edit content.

In most cases I can add a new pane, but I can't add "New custom content" on the first try, nothing happens when I click on "New custom content". But if I click on something else and then again on "New custom content" I get to add custom content.

But than I want to edit the content and I can't get the editor up, id just hangs on "loading..." and the editor never shows.

This problem is making panels useless and I would really like to know if there are any debugging information I can give you to help you fix this problem. I'm just not sure what to look for. I use default setups, most common models and zen theme (how ever I have default drupal theme for the administrator and the same problem there when trying to edit the content).

In some cases trying to add new panes gives me the same problem.

Here is some error message I get (in the console) when I click on the edit button of the pane:

Uncaught TypeError: Object [object Object] has no method 'once'
Drupal.behaviors.fillUserInfoFromCookie.attach    lausnir:65
Drupal.attachBehaviors     drupal.js:55
b.extend.each     jquery.js:33
Drupal.attachBehaviors     drupal.js:53
Drupal.ajax.commands.insert     ajax.js:542
Drupal.ajax.success     ajax.js:400
Drupal.ajax.ajax.options.success     ajax.js:164
c.extend.handleSuccess     jquery.js:143
c.extend.ajax.w.onreadystatechange   jquery.js:142

There is a possibility that this has something to do with my theme. Do you know what themes can do to brake the plugin? I'm not sure if the Zen plugin is braking the module ore if my sub-zen theme is doing it. I'm not sure how to debug it. Let me know if there is any more info you need from me, and where I can find that information.

Update: This is definitely a problem with my sub-zen theme, what is it that I might have done to make this conflicted in my theme development, I'm note sure what to look for?

I'm so sorry for my ramblings, I was getting frustrated. I finally found out what the problem was and it was that drupal only uses jquery 1.4.4, but when I updated to 1.7.x the panel loading failed.

I ran into this issue. I'm digging into it now.

The Spark distro loads jQuery 1.7.1 On the page with the error, the jQuery version is 1.7.2. Something is loading its own version of jQuery and blowing away the global jQuery object that should be there.

....

hmmm, something is loading require.js and that's calling in 1.7.2, but it should not trample on the global jQuery object. mysteries

...

It's the aloha editor. If I disable the aloha editor, the Panels IPE works just fine. Looking into how we can resolve this conflict between the modules.

Sorry! Same issue, different setup. I've got a couple issue threads open and I pasted to the wrong one. I haven't been able to reproduce this error in the same way described here.

Same issue here, using panels 7.x-3.3 and omega subtheme. I have tested enabling and disabling overlay, and with all versions of jquery and in all cases error always happens.

Changing default theme, the error seems not to reproduce, so only happens when using omega subtheme. I have downloaded module admin_theme to configure administration theme seven path to use it in:

• admin/*
• node/*/edit
• node/*/panel*

So it is using administration theme (Seven) for editing panel layout and panel content of node panels.

This workaround solves my problem, but seems that it is a bad combination between panels, jquery and omega theme.

#16 worked for me, jquery 1.7 instead of 1.8.

Confirming that #16 works to fix get it to work again, you have to switch the default one (when using Jquery Update).

For me it only worked with Jquery 1.5
(Panels 7.x-3-3, Views 7.x-3.7, Jquery Update 7.x-2.3)

For me, it was an interaction with the flexslider module. The problem went away when I disabled that.

I tried a variety of things to try and get panels editor working with flexslider, and so I can't be 100% sure which one solved it. My best bet is that was related to an error I had visible in Firebug: "ReferenceError: onTouchStart is not defined". It seems that this might be a peculiarity of Firefox v26 - many thanks to stevenaanen who posted the following comment

Cause

Firefox has the Responsive Design View as part of Developer Tools. It features touch gesture simulation using the mouse. When this has been used, Firefox enables touch events, but for some reason it doesn't always turn these back off after disabling it.

Solution

Go to about:config, search for setting dom.w3c_touch_events.enabled and put it back to 0 if not already there. For me this was sufficient.

As mentioned in #20 - Only JQuery 1.5 did it for me and my setup was the same plus Omega 3.

I have the same problem. Please Fix

Shame this is still not solved. It seem to be related to ckeditor. I turned off the "wysiwyg text format" on a local dev version to get it working but I can't do that on a live version because "diabling" the wysiwyg text format actually deletes it so all the body of your nodes that were authored with wysiwyg would simply disapear until you manually change the text format in them to something else.

Another thing to try and which worked once is to make the "wysiwyg" text format down the list of text format. That way it does not get selected by default for any content field. But this time around it wasn't enough and the "edit custom content" keeps loading with a weird message "wyciwyg://242/https://domainname.com/admin/structure/mini-panel/list" (note: why "wyciwyg" instead of "wysiwyg")

Update: I was able to solve this by updating drupal core's administration seven theme Jquery to 1.5 from the default 1.4. Weird because it used to work fine with both jquery 1.4 and ckeditor text format enabled.

Turned out to be the "Chosen" module for me. I updated it from an older version and the problem began. Disabling and re-enabling it fixed the issue.

Correction: After the update of chosen, I failed to update the library for it as well... After updating the library which got rid of a function error, the loading problem went away.

#24 did the trick for me. I've set the Alternate jQuery version for administrative pages to version 1.5 (default is set to 1.7) and everything works fine now

I ran into this issue as well, with admin jQuery set to site default of 1.4. Togged to 1.7, flushed caches, no change. Also tried 1.8, 1.11, no change. Only after enabling the Overlay module was I able to see content in the popup.

hi
i was facing this issue to with chosen modules .. on my own side just update the chosen's library with command drush chosenplugin and clearing cache worked for me

thanks

This is happening to me, since I upgraded Drupal core to 7.57 yesterday. I can add content to my panel page, but I can't edit existing content, because that edit page just continues to load forever. I tried enabling Overlay. I tried toggling through every available jQuery setting for admin. Nothing seems to work. I'm on Panels 7.x-3.9 and every other module on my site is current. Normally, I'm running jQuery 1.9 and Drupal default for Admin. Any suggestions?