toddhuish

I had this same problem and did some digging. this test is not extensively tested but it works now and I activated facebook, twitter and google+. I kept getting into conflict because the email address for FB was different than the one stored for WP.

Look around line 493 for the following

$hybridauth_user_email = $requested_user_email;

// Bouncer::Filters by e-mails addresses

and replace it with

if($wordpress_user_id){
    $u = get_userdata( $wordpress_user_id );
    $hybridauth_user_email = $u->data->user_email;
    $hybridauth_user_profile->emailVerified = $hybridauth_user_email;
} else {
    $hybridauth_user_email = $requested_user_email;
}

// Bouncer::Filters by e-mails addresses

All this is saying is that since the name/pass worked earlier to WP then we have a good user to connect to and to use the WP email, not the external social one.

@ahancock The version has been bumped. I sincerely wish the WP release procedure was a tad less complicated. You should see a 2.0.10 update notification shortly.

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

@chtombleson The newest edition (v2.0.9) should have gotten rid of all the notices if debug is turned on.

@chtombleson The newest edition (v2.0.9) should have gotten rid of all the notices if debug is turned on.

As long as your Curl supports TLS version 1.2 the plugin should work. I just updated the plugin to version 2.0.9 which gives you a quick status on the Curl you’re using as well as forces the plugin to use TLS v1.2 if it is available.

Update to 2.0.9 and see if that fixes your problems.

Local modifications…disregard

Seconded. I wish I had found this 2 hours ago. This was the exact fix I needed to clear all my AMP validation errors. Well, most. Went from 5209 to 72. There’s a manageable number.

Apparently removing the scheme is now anti-pattern. Se la vie.

So @vegasgeek solved this one for me

svn add --force * --auto-props --parents --depth infinity -q

After that the checkin worked normally.

I don’t understand why this worked but it did. I didn’t have any un added files so how this changed anything is a mystery to me. Regardless, maybe someone else will run across this and it’ll help them too.

When using an offset you also have to make sure that the number you are returning is less than the total otherwise you get the whole list so you have to offset by the count of the first list and explicitly tell it to grab what’s left.

$terms = get_terms( 'organization', array('offset' => $firstcolumn ));

becomes

$terms = get_terms( 'organization', array('offset' => $firstcolumn , 'number' => $secondcolumn));

The only time I’ve seen this particular error pop up is when you are attempting to use live credentials on sandbox or vice versa.

Figured I would add a quick note for the 2 multisite issues I had with this plugin but here ‘s what I did to fix it.

1) I’m using domain mapping so I had to add the real name of my site to the timthumb $ALLOWED_SITES array before timthumb would allow the requests. I think I can add it to that array with DOMAIN_CURRENT_SITE but I haven’t tried that part yet.

2) in includes/Options.php I had to change the !current_user_can(‘edit_plugins’) to !current_user_can(‘manage_options’) otherwise only network admins can see the options on sub-sites which seems a little too restrictive.

Are you using the newest version of the plugin? Version 1.3? This was a bug a couple editions ago but it’s been fixed for quite a while.

There isn’t a printable ticket. Normally what you’d have during an even it that you’d print out the attendee list and have the attendees show ID at the door. Th form you’re seeing when you click the link is the form to fill out all the information required of an attendee. Unfortunately printed tickets are not a feature we have in the ticketing system yet.

After Chargify is setup (wp-admin Settings->Chargify) you will see something like the following on your add post/page screens

https://screencast.com/t/o2hEsKtAzMnO

Make sure you get all of the setup steps from the readme.txt in the plugin directory. Unfortunately there is a fair amount of work to be done on the chargify.com side before everything can work.

Check the on sale dates on the packages that you’ve added and make sure that they’re active on the packages page. As for the ticket info, only name/email get collected at purchase time, the rest of the data gets collected after the purchase has been made. The customer is sent a link to fill out the rest of the questions you’ve asked for.