Just installed this module to try it out as an alternative to the calendar module ... I have the latest -dev version sof Date and cTools installed, and installed -dev version of FullCalendar ... libraries are in place ... when I go to View -> Add View -> Continue (as per Usage instructions), I go to Add a Date Field ... choose the one that is attached to my Event Content Type, hit submit, and I get this very long one liner, that starts with:

[{"command":"settings","settings":{"basePath":"\/","pathPrefix":"","ajaxPageState":{"theme":"seven","theme_token":"O0u68cKKfLiDlw7_lYKbkoXDSA ...

and goes on forever ...

Has anyoen tested this against the latest/greatest version of Views/cTools? Or is that where my issue is?

Comments

tim.plunkett’s picture

Assigned: Unassigned » tim.plunkett
Status: Active » Postponed (maintainer needs more info)

Sorry you're having trouble.

Can you paste the entirety of it (http://paste.pocoo.org) and link to it?
Also check your browser's JS Console for errors.

Set back to active when you do so, thanks.

tim.plunkett’s picture

Assigned: tim.plunkett » Unassigned
Priority: Major » Normal
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Please reopen with more information if you are still having this issue.

knsheely’s picture

I am having the same problem. Here is the entire string:

http://paste.pocoo.org/show/572795/

As a side note, in a different browser, instead of getting the display of the json when I click apply (all displays), I am asked to download the json as a file.

kahezi’s picture

Hello,

i have the same problem. The link here is death.
Who now's the solution?

Thanks for all answers

snowmountain’s picture

Status: Active » Closed (cannot reproduce)

I also have the same problem. I just installed fullcalendar and updated all modules yesterday - May 28, 2013, so have the latest of everything.

The problem appeared when I was editing the fullcalendar view page display. When trying to change the title, or the AJAX setting, or the access, applying the change - not saving the view, just the change in the popup window - resulted in the code filling my browser window.

This happened in both Firefox and Chromium.

It did NOT happen while first working on the view, for I turned AJAX on and set the title. Later, when returning to change them, is when this happened.

Oh! I just discovered that the problem disappeared. I had disabled these modules:

fullcalendar colors
colors
colorbox

A few minutes ago, immediately after disabling these modules the problem was still there, but after a few minutes, the problem disappeared. Maybe cron ran during this time?

I was going to paste in some of the code, which did look exactly like the code in the first post, but now things seem to be working.

FOUND IT! I had turned AJAX off for the view. That seemed to fix it.

I turned AJAX back on, and even with those modules disabled, the problem reappeared.

I turned AJAX off, and the problem was there when I applied the change. The code filled the window. But I could go back with the browser button, and then save the view, which saved the change to turn AJAX off, and then things worked normally!

It seems to be AJAX "on" for the fullcalendar view that triggers this.

Module version:

Drupal core: 7.22
FullCalendar: 7.x-2.0
Views: 7.x-3.7

EDIT: also

CTools: 7.x-1.3

snowmountain’s picture

Status: Closed (cannot reproduce) » Active

Setting to active since more info was provided....

snowmountain’s picture

Status: Closed (cannot reproduce) » Active

The previous post implies that this can now be reproduced.

TO REPRODUCE:

- Install the modules mentioned in the above post #5

- Create a fullcalendar view with a page display

- Turn AJAX on and Save the view

- Then try changing the title, etc. in the view and applying the change - the result will be, if the problem is reproduced, the code's appearing in the browser window.

snowmountain’s picture

More info:

When I saw the problem, my FullCalendar compression level was set to Development, uncompressed code on this configuration page

.../admin/config/user-interface/fullcalendar

dcam’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

I've volunteered to help clean up the FullCalendar issue queue. As part of that effort I'm closing issues open for unsupported versions of the module as "Closed (outdated)". That includes any Drupal 7-compatible versions because no active maintainer is supporting them.

If this issue is still relevant for version 3.x of FullCalendar, then feel free to re-open it and update the issue version number.