• 3. Place <code>scheduler_plugin</code> in your templates

    If I just want to create a separate WP-page with your calender, a “Schedule an Appointment” page. What template file do I need to put this in, then how do I call it? For example, I thought maybe you just put the code <code>scheduler_plugin</code> in the HTML of the blog post after you activate the plugin. However, if I put <code>scheduler_plugin</code> in the HTML of a blog post, wordpress shows nothing on the page, so I assume this is not where I put this.

    The directions are not very clear and unfortunately my PHP knowledge is somewhat limited. Do I go to the template editor? If so, which file should I edit and where? Then how do I call the calendar to show in a post?

    http://wordpress.org/extend/plugins/event-calendar-scheduler/

Viewing 15 replies - 1 through 15 (of 21 total)
  • Are you placing the “scheduler_plugin” text or “[[scheduler_plugin]]” ?
    The brackets around the text is necessary part of markup

    Thread Starter andrewsauter

    (@andrewsauter)

    Yes, every time I try to put the code in here (even with the backticks) it makes it a link, but yes, I’m including the brackets.

    I’ll try again: <a href="http://codex.wordpress.org/scheduler_plugin">scheduler_plugin</a>

    EDIT: Nope, still makes it a link, how do you get it to include the brackets in your post? I tried the code tag, but that doesn’t seem to work either.

    Hi andrewsauter,
    I just added the code in the “html editor”, and it worked fine.

    I’m having the same problem. What files should be modified and where does the code go. Is there an example that shows how and where the scheduler_plugin should be placed.

    lovedirections
    I put the plugin in the wp-content/plugins/
    directory.
    Turned it on.
    And then went to a new page, under the html editor, entered:

    [ [ scheduler_plugin ] ]
    (Without the spaces. I added the spaces to avoid the wiki-style of these forum)

    And it worked great for me.

    Consider a plugin conflict.

    Tal

    lovedirections
    I put the plugin in the wp-content/plugins/
    directory.

    Done

    Turned it on.

    Done

    And then went to a new page, under the html editor, entered:

    [ [ scheduler_plugin ] ]
    (Without the spaces. I added the spaces to avoid the wiki-style of these forum)

    Done

    And it worked great for me.

    Did not. I have the page title, blank, and then Add Comment block

    Consider a plugin conflict.

    Went back and turned off ALL other plugins. Same problem.

    If it goes into a page, then why does the instructions say to add it to a Template?

    lokrin2000
    I know what the instructions says. I am telling you it worked for me inside a page.
    Last option: change the theme to something else and then check.

    Also check with adding the code to the template, and see if then it works.

    Please let me know, it’s always nice to know 🙂

    Tal

    I did just check the theme and that’s why I’m back. That’s the problem. I’m using the Mandigo theme and it just does not work at all.

    I have about a dozen themes installed and I tested it with several. I notice various problems with various themes. Some are blank. Some are fine. One forces each day block to about 10 pixels wide. One places the events outside the sidebars rather than in the calendar. Looks like I’ll have to try playing with CSS and see if that helps anything. I’m not that great at PHP, but I may have to try playing there as well.

    Does your code make use of its own CSS names – e.g. td.eventcalendar or some such? That way you could make sure each element retains the properties that you want them to have and not be overwritten by a template CSS?

    I realize that this is version 1.0 and things are bound to crop up, but I would really like a calendar that works with a template that also works with my site.

    One of the main reasons I use the Mandigo template is the way it has drop-downs for the page navigation across the top.

    Just found the major culprit. I had the theme option for Drop Caps turned on. That changed the code to read

    ...
    <span class="dropcap">w</span>indow.onload =   function init() {
    scheduler.config.xml_date=%Y-%m-%d %H:%i";
    ...

    I went back into theme options and turned the dropcaps off (checkbox) and it shows up now.

    Other changes:

    Had to modify scheduler.php and change bottom:5px to bottom:-20px to lower line outside of calendar.

    <div style='position:absolute; bottom:-20px; right:20px; font: Tahoma 8pt; color:black;'>Powered by <a href='http://dhtmlx.com' target='_blank' style='color:blue;'>dhtmlxScheduler</a>

    And in dhtmlxscheduler.css, I had to modify .dhx_cal_event_clear to change from Height:13px to Height 23px because I could only read the top half of the words and not the bottom.

    Wonderful detective work lokrin2000,
    Thanks for sharing!

    Tal

    FYI I also had an issue with the calendar showing up. Needed to edit scheduler.php, all instances of the following:

    href=\"wp-content

    needed to be changed to my site path,

    href=\"http://www.mysite.com/wp-content

    (this should really use the ABSPATH variable though)

    (as should the following)

    src=\"wp-content

    needed to be changed to my site path,

    src=\"http://www.mysite.com/wp-content

    Not sure what was going on there but since I put the scheduler call in a 2nd level page, it wasn’t working (couldn’t find the required files).

    Hope that helps somebody.

    Thanks for the sharing linkingarts 🙂

    got a problem with this plugin too. currently testing it here: http://021club.co.za/events/ the plugin loads, but all I see is powered by 🙁

    any ideas? tried the default theme, same problem…

    @linkingarts:

    that fixed my problem too, at least partway… now I get a pop up error: http://screencast.com/t/ZERavrTUaf

    can’t create events 🙁 getting the same pop up error…

Viewing 15 replies - 1 through 15 (of 21 total)
  • The topic ‘[Plugin: Event Calendar / Scheduler] How to call the calendar in a page?’ is closed to new replies.