[email protected]

In following the code, I find this in wp-fullcalendar.php:
do_action('wpfc_calendar_search', self::$args);

I tracked ‘wpfc_calendar_search’ to em-wpfc.php. There I find this:

//this never worked because the action was never correctly called, until we add a setting for this in the options page, uncomment the line below or paste it in your functions.php file
//add_action('wpfc_calendar_search','wpfc_em_calendar_search', 10, 1);

Is this a problem? I can’t find the action referenced or defined in any other php file. Where else might I look?

This should be the correct syntax?

[fullcalendar type="event"]

I’ve tried with and without the type attribute, which seems redundant since I’ve defined this within the config pages. I’ve tried “events_fullcalendar” as well. Same result.

Also, I’m going to step through the code that tries to render this section and see what’s going on. The only other plugin I’m using is EM, so it would be odd if that were the issue.

If you have any other suggestions, please pass them on!

Because something is generated by the shortcode, it seems like the place to start looking is what comes after. Is there an ajax call to get the calendar? I don’t see any failures, so perhaps there is some other reason why this fails. Maybe all I need is a place to look that might help me unravel this.

I tried creating a post with the included shortcode. No luck. Same markup is generated, but nothing is visible on the page.

Yes. I’ve tried both ways. (And thanks for responding!)

Update:

Here’s what is generated by the shortcode. Nothing appears on the screen:

<div id="wpfc-calendar-wrapper">
<form id="wpfc-calendar"></form>
<div class="wpfc-loading"></div>
</div>
<div id="wpfc-calendar-search" style="display:none;"> </div>
</div>

Thanks.

Thanks for the quick resolution, and apologies for asking in both places. Good to know both discussion forums are monitored.

To fill in the rest of the conversation for anyone who may stumble upon this problem:

I switched Stripe to live mode and copied my live keys from Stripe’s config pages. I just double-clicked the value, pasted it into my PMPro config page, and trimmed off the white space at the end. I failed to notice that there was another space at the beginning of the string.

The result was that when I tried to pay on my PMPro checkout page, the form was submitted — clearly not supposed to happen. So I set a break point in Firebug at the function that’s called when the submit button is clicked. The call to Stripe.createToken() failed, but I could see no indication of why.

I’m sure Jason has this covered, but a few things that would have helped me find the issue (putting to one side the fact that I made the mistake in the first place!):

— some sort of trim() on saving the key
— trim() when getting the key from the DB

Then things get a bit less clear because the right solution depends on internals that I’ve not looked at. But maybe:

— a try{} block containing the call to Stripe.createToken (if in fact an exception is raised when the key is wrong)
— some sort of debug output that would indicate what the problem is.

In any case, thanks again Jason for the prompt response. It’s very helpful, and guarantees that I and others will recommend your plugin to anyone looking for such a thing.

Charles.

Seems like the problem is occurring in the call to Stripe.createToken(). What are some possible reasons for failure here? The key being used appears to be correct.

The response handler is never called.

Thanks, C.

I believe I found the issue. There’s an email address listed under General Settings that needed to be changed — not just the site admin’s email address.

This of course makes sense, since there might be more than one user with admin privileges.

Thanks.