Closed (fixed)
Project:
Panels
Version:
5.x-2.0-beta3
Component:
Panel pages
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Jan 2008 at 05:23 UTC
Updated:
26 Dec 2008 at 07:11 UTC
Jump to comment: Most recent file
Comments
Comment #1
merlinofchaos commentedHmm. You should try updating to beta1. I don't even know where to start in looking for this error.
If you update to beta1 and still get this error, I may need you to put in some debugging messages for me.
Comment #2
gracearoha commentedmerlinofchaos,
i ended up deleting the view (from the table) that i was last editing before the error started - a calendar view.
And now it seems to be okay. the problem was occurring on my production site but not on my development site (????).
Anyway, i have installed the beta 1 on my development site and will play around a bit with it before putting it on my production site. What a great module! I look forward to checking out the beta 1.
Thank you!
Comment #3
gracearoha commentedi upgraded to the latest version of panels 2 beta 1 (january 9). Since i already had panels pages set up from the 2.0-alpha 14 that i wanted to use, i also enabled the panels_views_legacy module. I checked all my panels pages and everything looked great. Until i went in to edit one of the views in one of my panels pages.
Now i receive the following error when i try to access that panel page or the admin/panels/.../edit/content:
Fatal error: Cannot use object of type panels_context as array in /opt/lampp/htdocs/drupal/sites/all/modules/panels/panels_views_legacy/panels_views_legacy.module on line 77
Here is what i did:
1. Disabled panels alpha 14 and removed the directory from the file system
2. installed beta 1
3. enabled the beta 1 panels along with the views legacy
4. turned all appropriate permissions on
5. When into views/edit to edit one of the panels pane views
6. went to check the view in the panels page and received the error message
As in the above fix, i then went into the panels pane table to delete the newly edited view from the panels page and again i could access the panels page and the edit content. However, when i went to add the view back in, i received the message, "the input was invalid".
I will probably just go ahead and learn how to set up all my views according to the new system and get rid of legacy as that seems to be the way to go. But thought i'd post this here for others who need to keep their old panels view and may be having a similiar issue.
Shall i change the title of this issue or start another?
Comment #4
merlinofchaos commentedThis looks like the right issue for that, and is detailed enough that I might be able to reproduce it. Thank you!
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #6
gracearoha commentedhi,
sorry to re-open this again, but this problem seems to have re-appeared.
I am now using panels 2 beta 2 and was using it just fine to create several panels and had no problem editing the panels.
then all of a sudden i starting getting the "input was invalid" message in the pop-up window every time i tried to edit or add new content.
I have disabled and re-installed a fresh version of panels, i have not updated my jquery, but i have installed the mc.js_0.patch, i have disabled the devel module.
I am running Linux with FF2 and i have pop-up windows enabled. I also tested on IE6 and receive the same error. My development site on the other hand, works just fine. Can't for the life of me figure out what's happening here. Any ideas of where i might look?
Comment #7
gracearoha commentedto add onto my previous post:
i have upgraded my site to devel 2.2 and still i am having problems with the pop-up window.
I have tried disabling tinymce and nicemenus but neither seems to make a difference.
Again, it works fine on my local server but not on my remote server.
i'm at my wits end after playing around with it for 3 days.
Any ideas where else i could look?
could it be some settings on my server that i need to check?
Comment #8
merlinofchaos commentedI have identified a bug with the popups in that the necessary panels.js doesn't get added if you do not have view pane admin links access. Is this your problem?
Comment #9
gracearoha commentedno this is not my problem. i do have access to view pane admin links.
another strange thing that i noticed is that on my development site, when i enable the legacy views panes, then i receive the same error message in the content add ajax box. However, on my live site, it doesn't seem to matter whether or not legacy views is enabled or not.
Comment #10
gracearoha commentedalso i noticed that the pop-up windows in "context" work just fine i can add arguments, relationships and contexts, but when i go to add new content - or edit existing content - no go.
please help. i really need this function.
Comment #11
gracearoha commentedi was beginning to think this was some sort of problem with my server since it wasn't happening on my local server, but i exported all the panels tables from my live site to my local site thinking that i could edit them there and then return them to my live site, but alas, it broke my local site as well.
i wonder if i'm just using the program incorrectly. Am i not supposed to use both the views panes and the legacy views panes at the same time? I'm thinking that may be where the problem lies...
Comment #12
okday commentedHi,
Have you resolved your issue. I have the same problem and I'm unable to get the panel working on my website.
thank you.
Comment #13
gracearoha commentedNo, im sorry to say that i still have not been able to get the add/ or edit content window to work.
I have upgraded to D7 and have tried both Panels 2 beta2 and Panels 2 dev, but neither one works. It's a bit frustrating as i have created 77 views that are waiting to be entered into panels pages. :(
Comment #14
merlinofchaos commentedI'm not ignoring this, and I know it's a huge problem, but I don't have any idea what is causing this; it isn't something I am able to reproduce on my servers at all.
Comment #15
gracearoha commentedyes, i know that you're really working hard on this and i am grateful. It really is a great program.
i will continue to experiment and let you know if i come across anymore clues.
Comment #16
okday commentedHi,
On one of my websites, the "blockanonymouslinks" module was the problem. I disabled the module and the error dissapeared.
I have not found the problem on my second site. I will try to disable other modules one by one tomorrow. I will post my results here.
thank you.
Comment #17
okday commentedThe panel module is ncompatible with these modules.
block anonymous links
quickstats
VIDEO
The incompatibility with VIDEO module is a big problem....
Comment #18
gracearoha commentedI don't have any of these modules enabled and still i am having problems with panels.
I completely removed my panels module and the db tables. I did a fresh install of panels 2x-2dev (feb 21) with many of my contrib. modules disabled. I have upgraded to D5.7 and have only panels-pages and panes views enabled
i re-built 2 panels pages with about 10 panes each (using flexible layout) and had no problems. Then on my 3rd panels page it started acting up again. I received the "input was invalid" message when i tried to add a new pane. I cleared my caches, logged out, logged back in and was able to add a couple more panes successfully. Then on the next pane, i could get as far as adding the pane, but when i clicked save at the bottom of the form, the pane disappeared. I tried several times, but with the same results. Cannot find any errors in my watchdog logs.
I did find the following errors in my FF error console, but not sure they would have anything to do with this problem, would they?
Any ideas would be most welcomed. I am really at my wits end :(
Comment #19
gracearoha commentedDrat! I just disabled nice menus and the panels began working again. I had thought i tested it before with nice menus disabled and it didn't make a difference. Must be a combination of nice menus and something else, perhaps?
Anyone else had a problem with nice menus and panels and been able to patch it somehow?
Comment #20
merlinofchaos commentedNice Menus!
That's very valuable information!
The fatal error you mention is a fleeting but that I've seen but cannot figure out at this time where it comes from. The rough description of what's happening is that content types advertise what contexts they accept and it can either be a scalar (just a single context object) or an array (which may contain 0 or more context objects). Views *always* advertises that it wants an array, but for some reason in rare cases it's not getting the array it needs. I don't know why, but hopefully will be able to figure this out.
What's interesting is that if you're using beta2, you shouldn't even have a views.inc -- that file is empty and was replaced by panels_views_legacy.module -- so I'm not sure how you're actually getting that error.
Comment #21
gracearoha commentedActually, i haven't had the error mentioned in the 1st post since alpha14 (perhaps the title needs to be changed?).
I am now using the latest dev version (feb21). see post #18 and #19. (And some of the previous ones). Seems several of us are trying to figure out what's happening with the pop-up window and the "input was invalid" message. Perhaps it all has to do with the combination of other .js modules installed?
Comment #22
merlinofchaos commentedIt does seem very likely that it's some kind of conflict. Either other javascript modules or modules like securepages or something along those lines.
Comment #23
gracearoha commentedAt this point, i'm ready to go back to the pre-ajax version of panels. I don't know what else to try.
I thought it was just my nice menus cuz panels seemed to work again after i disabled it. But it seems it only worked for a little while. Now it's acting up again.
I was able to create 2 new panels pages both using the flexible layout and each having 10 panes. But as i started to add more pages i was only able to add a few panes before panels started acting up again. It either gives me the "input was invalid" error or it lets me add the pane but then does not save it in the panel page.
It seems i can keep adding new pages, my ability to add or edit new content diminishes as i add more.
Is it possible that there is a limit to how many panes can be added?
I have disabled or uninstalled every module that using js.
i have never used the jquery update nor the js tools nor securepages.
I also wonder about the "position" field in the panels_pane table. Should this be a unique number for each pane?
Most of my positions show "0". Is this correct?
Comment #24
merlinofchaos commentedThe position is within the panel, so a lot of the panes will have a position of 0; but panes that are in the same panel should have a unique position number.
When you receive "the input is invalid" have you checked your HTTP error log for some kind of error message that could give some kind of indicator what's happening?
There should be no limit to the number of panes or panels or displays that can be in use.
Comment #25
gracearoha commentedaha, i am in fact getting errors.
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '%1) AND (MONTH(event.event_start) = %1) AND (DAYOFMONTH(event.event_start) = %1)' at line 1 query: views_build_view SELECT DISTINCT(node.nid), event.event_start AS event_event_start, node.title AS node_title, node.changed AS node_changed, event.event_end AS event_event_end, event.timezone AS event_timezone FROM node node LEFT JOIN term_node term_node ON node.nid = term_node.nid LEFT JOIN term_hierarchy term_hierarchy ON term_node.tid = term_hierarchy.tid LEFT JOIN event event ON node.nid = event.nid WHERE (node.status = '1') AND (node.type IN ('volunteer_timeslots','event')) AND (term_node.tid IN ('177')) AND (event.event_start >= DATE_ADD('2008-02-27 05:30', INTERVAL 0 SECOND)) AND (YEAR(event.event_start) = %1) AND (MONTH(event.event_start) = %1) AND (DAYOFMONTH(event.event_start) = %1) ORDER BY event_event_start DESC LIMIT 0, 4 in /opt/lampp/htdocs/drupal/includes/database.mysql.inc on line 172.
looks like there's a problem with my upcoming events view...
but would this cause a problem even with editing or adding content to panels pages that don't contain this view?
Comment #26
merlinofchaos commentedIndeed. Does excluding this view from your panels make them work again?
Comment #27
gracearoha commentedi deleted all the offending views from panels and was able to successfully add two new panes and then, once again it stopped saving my additions. But this time no errors in the log. Perhaps i had already polluted the database somehow.
i will start with a fresh install again tomorrow and see what happens. (didn't have much time to play with it today).
Comment #28
gracearoha commentedWell i seem to be going round and round here and can't seem to identify the problem with panels dev.
i can create 3 to 4 panels pages of 9 panes each and then i can create a few more, but never with more than 3 to 4 panes on each before i either receive the "input was invalid" message or the new panes just don't save.
I receive no error messages in my logs.
I've completely fixed my views module which had been acting up, i went through each of the 63 vviews that i am trying to put into panels and doubled checked to make sure everything was working (found no errors here).
Completely uninstalled and re-installed panels several times and started fresh with the same results each time.
One thing i noticed just recently as i was checking into the database is that although i never enable the panels cache, a db table is created for it and it is in fact caching. Should this be happening?
On my last re-install and start over, i had entered 35 views in the panels view and started to re-build my panels pages. This time i was able to create only one panel page with only six panes before it again stopped saving any new panes.
(Attached is the export from my cache table). Not sure if any can be seen from this.
Tried to clear the panels cache and see if this helped, but alas, no.
Any ideas of what else i could try or where to look for clues?
Comment #29
gracearoha commentedAt last i found the solution to my problem. It was in fact that panels_object_cache.data is too small. I used John Morahan's sql suggestion at http://drupal.org/node/230337. I hope this is helpful to others as well.
Comment #30
merlinofchaos commentedthe panels_object_cache table is where it stores a panel while you're working on it so it doesn't modify the real panel until the end when you click save. So yea, now I understand how this was creating your difficult to identify problem.
Comment #31
john morahan commentedCopying the patch from the dupe
Comment #32
sdboyer commentedThanks for the patch, John. The update looks just fine, so I'll commit it and we'll roll it in with beta3.
Re: your point in the other issue regarding pgsql - I did a little digging around, and unless the PostGreSQL documentation itself is wrong, we should be good without changing anything on the pgsql side. Evidently, the pgsql 'text' column type has no maximum length: http://www.postgresql.org/docs/8.3/interactive/datatype-character.html.
Thanks also for your perseverance with this problem, gracearoha!
Comment #33
sdboyer commentedChanges have been committed, and will be available officially as of panels2 beta3.
Comment #34
PawelPohl commentedHi guys,
I have a problem that seems very similar to this, only in beta3 (also in dev). The difference is that I only get the "Input was invalid" message when I am trying to add content to a "separate display" (both general separate and per-content type separate). It was working OK to a point, but something messed it up. I tried to remove the offending view panel, view, even clean the panels tables - to no avail.
Thanks for your hard work!
Comment #35
PawelPohl commentedRe-opening the issue and marking for beta3.
Comment #36
sdboyer commentedFirst off, just to note - the -dev waters aren't safe for swimming :)
Ugh, I was hoping we were done with this one. Well, let's start with the obvious - if you could provide me with every debugging & error message related to this that you can dig up, PowerPohl, it'd help me know where to start.
Just to make sure - you're sure you've run update.php in order to increase the size of those cache fields, right?
Comment #37
PawelPohl commentedI wish I could give you more info, sdboyer, but that's pretty much all I have, I was stupid enough not to save the db errors while they were occuring, and now the only symptom I got is what I described above.
However, I found that going to Layout Settings > Node 1 ID News Item, changing whatever and saving settings actually makes the Content > Node 1 ID News Item work OK. So it would seem that whatever is created when you save those settings and is passed to the modal popups in the DnD was not present until I visited the tab in Layout Settings.
Hope this helps...
PS. lol@PowerPohl:)
Comment #38
sun@PawelPohl: Please open a new issue (but search for existing first). This issue has been fixed already.
Comment #39
radyaweb commented@Pawelpohl: Your solution is working for me, Thanks.
At least I can insert content to my panels page.
Actually my problem occurred when using new themes.
If I'm using default themes like garland or bluemarine, no problem occured.
But, when I change the theme to other contributed themes, the modal pop-up menu gives error like this: " Error: The input was invalid".
When I try Pawelpohl solution by click save button in layout setting for every content type, those error is dissapearing.
Thanks to Pawelpohl. :)