5
Having dug through the archived forums on Solspace I found this gem: http://www.solspace.com/forums/viewthread/11282/P15/
Basically it appears that adding the id="" parameter in the Channel Form/Safecracker form tag somehow breaks things. Removing that parameter seems to have fixed the issue.
Thanks to Anna for the really useful suggestions, though :)
5
Just simple conditionals are parsed before the modules and plugins. Simple ones are the conditionals using just if and just early parsed variables. segment_N are early parsed variables, but your conditionals have an if:else.
So, try this:
{if segment_2 == ""}
{exp:calendar:cal date_range_start="today" date_range_end="today" show_days="1" pad_short_weeks="...
4
The short answer is to just pass in either the entry_id or the url_title for this calendar entry, either of which should be easy enough to do on a detail page.
To know which would be best in your case I'd need to see key parts of your template(s), but here are a couple examples.
Option 1: Use the entry_id for your event from the URL:
{exp:seo_lite ...
4
If you would like user submissions to directly polulate the calendar, then you should use Channel Form and have users submit the events as entries in the calendar Channel.
Assuming you are using Solspace Calendar, see the docs on Using with Channel Form.
This same approach of using Channel Form holds true if you are displaying events using the native ...
3
I hear what you're saying about automating but in reality just how many holidays do you honour? It's not going to take too long to do it manually.
I would create a channel for holidays and create an entry for each holiday with the entry and expiration dates set.
Then on your template use a channel entries tag pair with show_future_entries="no"
In theory ...
3
Calendar events do not use regular entry entry_date and expiration_date values, but rather specialized event data stored in Calendar itself. Since the EE simple search form uses the regular EE channel entries library, it won't be able to filter for upcoming events based on entry_date and expiration_date.
Further, occurrences of an event are not necessarily ...
3
Instead of limit="10", try using event_limit="10". From the {exp:calendar:events} documentation:
http://www.solspace.com/docs/calendar/events/#event_limit
2
Try passing the event_id to an embedded template to a calendar:events tag.
Which you would use to display the date.
something like:
{embed="my_date_template" event_id="{parents:entry_id}"}
then, your embedded template:
{exp:calendar:events event_id="{embed:event_id}"}
{event_start_date format="%F %d, %Y"}
{/exp:calendar:events}
2
Why not to use format="%U"?
From the documentation of Solspace Calendar:
In addition to standard EE date formatting, Calendar supports[...]
From the documentation of EECMS:
%U: seconds since the epoch
2
You are missing the paginate parameter on your opening calendar:events tag. Try adding paginate="bottom" and see if that fixes your issue.
2
First, I highly recommend having a look at this documentation page explaining the differences between some of the more common Calendar tags. Always useful:
http://www.solspace.com/docs/calendar/getting_started/
In detail, if you're looking to create a chronological list of events/occurrences, use {exp:calendar:cal}. This is the only tag that will make the ...
2
You must use the channels and custom field groups provided by Calendar when it's installed.
To create events in "Calendar: Events", you need to create a calendar in "Calendar: Calendars" first.
If you uninstalled Calendar and want to reinstall it, make sure to delete everything from the old Calendar install before you do, this includes the old Calendar ...
2
Try making this a global variable in your config file, then you can do all the date checking in PHP. Go to http://www.epochconverter.com/ and get the start and end date of when you're closed, then add this to your config.php file.
if (time() > 1387497600 && time() < 1388016000) {
// Use this in your template {hours_open} and it'll show if ...
2
Move the click handler to the wrapping div.
$('#cal_container').on('click', '#prev, #next', function(event) {
event.preventDefault(); /* Act on the event */
});
Has to do with the original event handler in your code not being passed to the dynamically inserted html. There's a good explanation found here: http://toddmotto.com/attaching-event-...
2
You need to compose the URL for the entry yourself depending on template group and template you want to use.
Looking at the sample URL you posted, I assume it will be something like
{path=events/test-speaker-series}#{url_title}
2
This is because Calendar uses ExpressionEngine's built in jQuery UI bundle to build the mini calendar popup. You will probably have to use some combination of the two with jQuery's noConflict method: http://api.jquery.com/jQuery.noConflict/
2
Use the documentation to determine how you should configure your templates.
https://solspace.com/expressionengine/calendar/docs/
Try using this parameter to filter by category:
https://solspace.com/expressionengine/calendar/docs/cal/#category
You'll have to be more specific about what you're trying to do for anyone to give you a good example. As for "...
1
The following solution, from the Solspace support site, might be what you are looking for:
How to display a chronological list of events, with each unique event appearing only once
It's also been mentioned in these threads:
Solspace Calendar Limit Occurrence Returned
Solspace Calendar: Only show next occurrence of recurring event in list of recurring and ...
1
Yes, just use the cal tag. If you click on view calendar events on this page, that is a Solspace calendar that is responsive. The cal tags allow you to do this easily, it's all just css.
1
Seems after not being able to find anything happening and following every hunch I could. It miraculously started worked after another uninstall -> reinstall. Thank you all for you help.
1
Except for event date/time data, Calendar channels, both "Calendar: Calendars" and "Calendar: Events", remain mostly channel entries. This means that you can use {exp:channel:entries} to get your parent entries like this:
{exp:channel:entries channel="calendar_events" /* your other parameters */}
{parents field="event"} {!-- <== Your "Articles" ...
1
{exp:calendar:cal} has the following tags that could be used:
{event_start_date}, which displays the occurrence's start date.
{event_first_date}, which displays the date of the event entry's first occurrence.
For example, if you have an event that starts and ends on April 11th, and repeats daily until April 17th, {event_first_date} will be April 11, but {...
1
try adding this to your calendar:events tag
event_id="{entry_id}"
You may need to stick it into an embed if nesting a calendar tag inside a channel entries tag gives you trouble.
EDITED
I believe A better approach to accomplish what you're after would be to use a {exp:channel:entries} tag for your news and a {exp:calendar:cal} tag for your events.
If ...
1
This doesn't works because this conditional isn't a simple one, so the template parser tries to parse the exp:calendar:cal before the conditional.
Simple conditionals looks like this:
{if foo == "bar"}
They are parsed before at the stage 13 on Rendering stages.
Everything else are advanced conditionals, parsed at stage 18.
So, {if {current_time format="%...
1
Sound like the theme files didn't get uploaded to the production server fulling. I suggest you delete the Solspace Calendar theme directory which should be located at /themes/third_party/solspace_calendar (or something like that)... then reupload the theme directory. If that doesn't get it working, also reupload the module files.
1
It seems to me that the best way may be to simply use Categories for both Regions and types of events. That's not native to the Calendar module, but seem like it wouldn't take much to filter by a category url title.
That is the direction I would go. Two category groups -- Region and Type -- with Areas being subcategories for the Regions. You'd want to make ...
1
Easy iCalendar?
SolSpace Calendar (hell of a price tag though!)
Note I've not used either so can't recommend and you'd need to explore further!
1
If you're looking to order occurrences chronologically, you should be using {exp:calendar:cal}. This is the only tag that will order occurrences in true chronological order. Details on why/how can be found here: http://www.solspace.com/docs/calendar/getting_started/
1
I actually just ran into a similar issue with Solspace Calendar. The add-on is written so that ordering in this way is not possible (it has a built-in ordering process). You can't even use the fixed_order= parameter.
In the end, I had to utilize Stash to first grab all the event occurrences and set them into a list, then grab that Stash list and sort using ...
1
Pretty sure you should be able to use multiple calendars on one page but in this case it didn't work so embedded each calendar in templates to solve.
Only top voted, non community-wiki answers of a minimum length are eligible