My test site:
Drupal core : 7.0
views : 7.x-3.0-alpha1
date: : 7.x-1.0-alpha1
calendar : 7.x-1.0-alpha1
My test step:
(1) clone the default calendar views and save as a new test calendar.
(2) delete field in Arguments, and add my date field to Arguments.
(3) add my date field to Fields section.
(4) calendar page preview do not show any event I've created.
(5) change Arguments from my date field to node update date field.
(6) calendar page preview show events as usual.
Anyone could help ??
Comments
Comment #1
pivica commentedsubscribing
Comment #2
karens commentedViews made lots of changes to field handling just before the new release, which broke lots of things here. I issued a new release with some work-arounds to get things working again and am waiting until the dust settles on how the new core fields will be handled in Views before doing much more with the Views integration. These changes should get things working with latest Views release.
Comment #3
gorillaz.f commentedyeah~ it works with date & calendar alpha2 , thank you ~
Comment #4
sven.lauer commentedReopening this because I think this probably has to do with this issue.
Using alpha3 of both modules, the calendar page display works fine regardless of which argument is used, but as soon as I switch to using a date field as argument, the block view stops displaying any events (i.e. it does not display links for any of the days, but instead looks as if there were no events).
Comment #5
David van Diepen commentedI am experiencing the exact same thing as sven.lauer.
Comment #6
sven.lauer commentedInvestigating a bit, I find that, in
calendar-datebox.tpl.php$selectedisTRUEfor days that have events, and consequently,$linkis displayed---but$linkis no link, but simply the day.In the preprocess function for that template, we find:
I am not sure what the test is there for, and my knowledge of calendar/view internals is limited, but I thought it might tip someone else off ....
Comment #7
Renegadez commentedI have my original calendar running fine for a private calendar I need a public permissions calendar so I created a clone version as stated below the same steps as op in post 1.
I create an event under the new public calendar event content type I post the event and it shows promoted to my front page, but do not show up in my calendar view on the public calendar.
Now both the original private (default) calendar look the same as the new cloned (public) calendar except I changed the argument to the new argument to be used for public and the name so i can tell them apart
BUT i notice under the
CALENDAR PAGE > Basic settings >Machine Name: calendar_1
Is the same in both calendars is this the problem?? or is something else? Thanks
My test site:
Drupal core : 7.0
views : 7.x-3.0-alpha1
date: : 7.x-1.0-alpha2
calendar : 7.x-1.0-alpha3
My test step:
(1) clone the default calendar views and save as a new test calendar.
(2) delete field in Arguments, and add my date field to Arguments. EXample: Arguments
Date: Date (node) Fields: field_pub_calendar_event
(3) add my date field to Fields section.
(4) calendar page do not show any event I've created.
Thanks
Comment #8
rublev_green commentedI have similar configuration
views : 7.x-3.0-alpha1
date: : 7.x-1.0-alpha2
calendar : 7.x-1.0-alpha3
List of events.
Default(just after installation) calendar view shows all events on the dates they were created (everything on one day pretty much).
After changing argument to the actual 'Date: Date (node) Fields:event_date' value no events are shown.
Under Fields section tried with or without event_date field.
Also noticed that if in default configuration I remove 'Node: Updated date' from Fields calendar also becomes empty.
Thanks for any help
Comment #9
Renegadez commentedIs it possible the Content Type EVENT DATE was created incorrectly or does not have datetime selected? that happened to me the first time I created it also I used the SORT under views and used the same event_date and selected descended at the bottom of the page to make sure the calendar sorted the days correctly sorry i am way new to this to
Comment #10
rublev_green commentedThanks Renegadez, you're right, field was just Date, after changing it to DateTime, events start to appear.
Comment #11
Renegadez commented@ rublev_green Awesome glad I actually helped someone back!!
Comment #12
harriska2 commentedDrupal core : 7.0
views : 7.x-3.0-alpha1
date: : 7.x-1.0-alpha2
calendar : 7.x-1.0-alpha3
Same as original poster. Although if I use updated date for the argument I get all postings (and all types) listed in the calendar.
Nevermind - my original field was not of datetime - that seemed to fix my first problem. Then I got caught by the argument issue - add the date: date (node) and from there add my date field. Ugh - you'd think I'd get that by the second time...
Comment #13
Renegadez commentedI use Content Type EVENT DATE with datetime in 3 places
argument
fields
sort and I sort by desc
I learned this from the is badass 10 minute video got drual site rocks check it out Thanks
http://gotdrupal.com/videos/drupal-calendar
Comment #14
David van Diepen commentedThank you Renegadez, your last post helped me out too. Apparently the custom datetime field has to go into those 3 places as you indicated otherwise the calendar view won't work.
Comment #15
agdjenn commentedMy custom datetime field is not showing up under the "Date Fields" check boxes.
Comment #16
Renegadez commented@agdjenn did you this your issue figured out?
Comment #17
tbenice commentedhaving the same issue, using datetime field in a custom content type. Date shows fine in page view but not in block
Comment #18
tbenice commentedHi All, I have a workaround until this issue is worked out. Create a new block with php and enter
print(views_embed_view('calendar', 'calendar_1'));this will embed the page view into a block.
Comment #19
arlinsandbulte commented#1094408: Date field not showing up in views arguments in localized site might have affected or fixed this issue.
Please verify this issue exists with the March 28 -dev
Comment #20
sven.lauer commentedThis issue has gone away for me a while ago, so I assume that @arlinsandbulte supposition was right.