onorok

keesiemeijer,

Is it possible to view the current year for the page you’re on?

I tried using km_dp_date_pagination_get_date(‘Y’, $posts) but it didn’t work for me, it returned the previous year.

Any ideas?

I greatly appreciate this plugin, it’s exactly what I was needing!

Well, that was easy! Just wanted to make sure. I appreciate the quick response!

I believe I’ve figured out the problem, and it isn’t one. It’s just a bi-product of a bunch of testing on my site. The above issues would not occur under normal operations. Sorry for the mixup.

I was just introduced to another, related, issue. Apparently, when someone updates their Billing Address / Card (in combo) they are charged for their subscription right then and there…

That can’t be right. Any ideas?

Also, this is happening when using Stripe as a payment gateway.

Cole,

Yesterday after refreshing my cache a bunch I found an error in my installation where I couldn’t upload image files. After much playing around with WordPress to get it working again, I did a completely fresh install and moved my wp-config.php back into my wordpress root folder. This fixed my image upload issue as well as the login modal!

I imagine, all along, that my wp-config.php being outside of my root folder has been the problem. I just didn’t know it, because I was using a cached version of it.

I’m not sure how that would affect anything like this, but apparently it did, and I am now able to log in just fine using your plugin.

Laura, you might check the same thing with your installation.

Good luck, man! Also, if you need anything from logs, just let me know, I’m super familiar with Google Developer tools so can get that information for ya.

Just tried from my macbook pro and got the same results, in both safari and chrome. I humored myself and disabled all plugins and am still getting the same results, the only thing I can imagine at this point that is different is that my wp-config is outside of my root. I don’t imagine that would break this though.

Also, the new update didn’t fix it for me, and that’s after clearing cache. I dunno what else to try on this end…

I’m getting 200 ok returned message, but it’s returning a 0 in place of the login information.

After clearing cache I’m getting a 302, moved temporarily, and nothing returned.

After looking at it more in depth, I can’t see the problem. I’m getting a 200 OK message back from the ajax call, but nothing happens.

I do think a simple fix for the broken ‘Back To Login’ link, would just be to remove the ‘Lost your password?’ link from the password reset screen once it’s loaded, because it only breaks the ‘Back To Login’ link when you click it on the password reset screen…

That probably makes no sense, but that’s exactly what’s happening, lol.

Windows 7 64bit with Chrome 27.0.1453.94.

Never tried it in IE or Firefox. I did try the demo on your plugin’s website, and it worked a little better there, it did return the ajax call in that case. It was still buggy with switching back and forth between Login and Reset Password though.

I think the modal’s state should be completely reset when it’s closed, because it was holding information in it between instances.

When I get home today, I’ll run it through my version of Chrome again and see if I can pull any error information for you.

No worries, Cole. That’s why we run test versions of sites ??

I love the direction you’re taking this in, the features you’ve implemented are some of the things I wish this plugin had to begin with!

Can’t wait to get this fully working version, I’m looking forward to the changes.

Thanks for the hard work you do to make this plugin happen.

I just updated to the new version and am getting the same thing.

Also, when clicking “Reset password” and returning to the login page, it keeps the “Back to login” link.

This version seems pretty buggy overall. :\ Especially, in comparison to the older one.

Lisa,

This is in regards to changing Membership Levels (from one level to another), a feature which is currently in place in PMPro and has been for a while, and it’s buggy functionality with Stripe. Not for multiple concurrent subscriptions.

It honestly doesn’t affect my blog, just wanted it to come to light so that Jason could have a look at it and possibly fix it. I think with the information provided he should be able to narrow it down and get it done.

As of now this issue has been resolved for me, just wanted this information to be available for others who may be having similar issues.

Thanks for all you guys do!

After looking at the stripe-webhook.php, it is obvious what is going on. I imagine Stripe is sending multiple customer.subscription.deleted messages now.

Adding your GitHub code for removing WP users when they cancel their memberships fixes it for cancellation scenarios. However, I’m unsure as of now if it would fix the problem for members moving from one subscription to another. Essentially, one subscription is being cancelled and another created, so I imagine the problem will still persist for those scenarios.

(I’m actually going to test this now to see if it works)

Using your current method for sending these emails, and if Stripe is now sending multiple subscription.deleted messages, then I imagine it would be a hard fix without adding a new table and keeping record of people who have changed subscriptions instead of cancelling.

Just my two cents. I imagine you probably have already figured all of this out if you’ve looked into it any, but I figured I’d at least leave this tidbit of info here for reference.

Thanks again, Jason. I love what you’re doing for the WordPress community with this amazing plugin.

I’ve gone over everything on my side and can’t find a cause for this error. Looking at the Stripe logs, there has only been one sent message regarding a cancelled account for one that I did last night. The problem still persists, I get an email every hour, on the hour, for upgraded/cancelled accounts. Just wondering if you’ve come across anything yet?

I may look into the PMPro code on my side this evening to see where this email is being sent and try to fix it myself. If I find anything out, I’ll keep you updated.

As far as I know this post has yet to be resolved, so please don’t mark it as so.