discotoast

That clears things up, absolutely.

Thank you for the quick reply Marho!

I know that there’s no/limited support for the PDF Tickets extension, however is there somewhere you would like me to submit a ticket for this other than here?

Other than that, this topic can be closed and marked resolved.

Thanks Again,

Cameron

Update:

I was able to resolve the issue in regards to the email that contains the ticket(s) using Post SMTP, however I’m still not seeing the emails from the eCommerce handler (Tickets Commerce) to either the admin or the purchaser.

I’ve checked the Email Log in Post SMTP and confirmed there was no send attempt for either of the eCommerce handler emails to the admin or the purchaser – is this due to being in Test Mode?

It’s also worth noting that the PDF Tickets extension (v1.2.2) isn’t attaching the PDF to the tickets email.

• This reply was modified 2 years, 10 months ago by discotoast.
• This reply was modified 2 years, 10 months ago by discotoast.

I was having this issue last night and found that it didn’t work IF you created the sandbox account through the plugin or through sandbox.paypal.com.

Instead, login using your normal credentials on https://developer.paypal.com/ and create a sandbox account there, then use those generated login credentials within the plugin. (Once logged in, Choose ‘Accounts’ under ‘Sandbox’ on the left menu, then choose ‘Create Account’ and choose ‘Business’ when prompted. The platform will then provide you with a generated user login/password).

You can also generate test credit card numbers for testing the plugin through that same Paypal Developer platform.

Have you checked the Defaults tab on the Post Expirator Options page? You’ll want to go there and ensure that the “Auto-Enable?” option is set to “Enabled” under your desired post-type.

Note: This bug is fixed in v3.1.8.
– Cam

@ingraye ‘s solution threw a php warning for us when there was a single term or no term selected, where an array was being expected in the second argument. Solved by replacing line 487 with the following (on v3.1.7 of this plugin) which should allow for some backwards compatibility with multiselect fields from older versions of gravity forms and the above scenario:

// New versions of GF store multiselect values as a JSON string.
$values = json_decode($entry[ $field->id ] );
// Older versions of Gravity Forms store the multiselect values as a comma-delimited list.
if( ! $values ) {
    $values = explode( ',', $entry[ $field->id ] );
}
$terms = array_map( 'intval', $values);

• This reply was modified 7 years, 6 months ago by discotoast.

Any luck finding something on this one? I am currently mapping a similar solution design and at this point, I’m thinking building this functionality by creating some custom components to augment some plugins with complimentary functionality is going to be our best approach.

Having same issues – across multiple sites. All within the past month-ish. Tried updating everything – still having connection errors. Have confirmed with mail server support ports are open (and otherwise active).