I got a PM with questions that I thought might be of value to EE users, so here is my reply:
Quote from: noahlearner at Mar 15, 2008, 09:49 PM
I installed 1.0 and it seemed to work well...So I decided to updgrade to 1.5
Good. 1.0 will not be supported and has severe limitations.
... all I can get to work is for the calendar to display with out any events. I also noticed that when I preview the ajax page I get a fairly lengthy error message as seen below...
Looks like a node specification problem - I’ll get to that in a second.
1. Is there a demo that I can look inside the manager so that I can see how the pages / documents are structured? I think that I will understand how to set it up correctly if I see it set up correctly.
No. Allowing unknown users inside your manager is a recipe for disaster.
2. Where exactly do I put the :
<div id="ee_miniCalendarContainer">
[+miniCalPlaceholder+]
</div>
<div id="ee_listDetailsContainer">
[+listDetailsPlaceholder+]
</div>
[!EasyEvents_ListMini? &nodes=`83`!]
Do I put it on the page where I want the calendar to live?
Yes. And no. It doesn’t have to be all one block as in this example code. What is important is that somewhere, either in your content, or in your template, you have both placeholders (miniCalPlaceholder and listDetailsPlaceholder) inside their corresponding DIVs. Then the snippet call itself - which generates output only for the placeholder locations, NOT its own location, needs to be called (again from the template or more likely, the content).
What exactly is the node? Is that the root folder where the calendars live?
A node is where the
events live. Not necessarily the calendar. Consider the following document set up:
- Calendar of Events Page ( 12 )
- Events (1 )
- - Conferences ( 2 )
- - - Conf 1 ( 4 )
- - - Conf 2 ( 5 )
- - - Conf 3 ( 6 )
- - Meetings ( 3 )
- - - Meeting 1 ( 7 )
- - - Meeting 2 ( 8 )
- - Shows ( 9 )
- - - Show A ( 10 )
- - - Show B ( 11 )
If you want the calendar on page 12 to include conferences, meetings, and shows, then you would use "node" 1. That is to say include all events below document 1. If you wanted just conferences, you’d use node 2, likewise, just meetings would be node 3. But there is NO DEFAULT NODE. So you have to specify at least one. You can specify more than one. If you wanted just shows and meetings but not conferences, you could specify "3,9" so you snippet call would look like this:
[!EasyEvents_ListMini? &nodes=`3,9`!]
On the easy event pages, what do I need to do with the following settings?
Container?
Rich text?
Published?
Searchable
Cacheable
Empty cache?
Content Type: text/csstext/htmltext/javascripttext/plaintext/xml
Content Disposition: Inline Attachment
Treat the Easy Event document like any other web page, because that’s what it is. If you think about it, all Easy Events does is examine those pages for you and present a new way to navigate to them. If you were to go directly to one of those pages, they would look pretty much like any other document. So for my Easy Event pages, I use the following:
Container: (I let MODx handle this for me, sometimes Yes, sometimes No)
Rich text: Yes
Published: Yes
Searchable: Yes
Cacheable: Yes
Empty cache: MODx default
Content Type: text/html
Content Disposition: inline
But again, use what you normally use for your pages.
Much more important than those settings is being certain you have your Template Variables set up correctly and your Easy Events configuration file edited correctly.