Franky
Forum Replies Created
-
Forum: Plugins
In reply to: [Events Made Easy] Membership Stripe paymentUpdate: small extra code fix added, best is to take eme_member_calc_status function from
https://plugins.trac.wordpress.org/browser/events-made-easy/trunk/eme_members.php?rev=2753443&format=txt(the extra changeset on itself is this: https://plugins.trac.wordpress.org/changeset/2753443/ )
- This reply was modified 3 years, 10 months ago by Franky.
Forum: Plugins
In reply to: [Events Made Easy] Membership Stripe paymentok, it seems in case “forever” membership and status calculation, things can go wrong. But that also means that it never could’ve worked in your memberships in the first place …
This changeset should fix it:
https://plugins.trac.wordpress.org/changeset/2753441/In fact, easier is to take the comple eme_members.php : https://plugins.trac.wordpress.org/browser/events-made-easy/trunk/eme_members.php?rev=2753441&format=txt and replace the function eme_member_calc_status in your existing file with the one from the file downloaded. You could replace the whole eme_members.php file, but other changes are present too and so I don’t recommend it.
Forum: Plugins
In reply to: [Events Made Easy] Membership Stripe paymentok, for now I’ll close this. If you can reproduce it, feel free to reopen this or open a new thread.
Forum: Plugins
In reply to: [Events Made Easy] Membership Stripe paymentI just tested a member-add + stripe payment : notification from stripe came through and was handled as expected (I even made sure the return-url for the user itself was not doing anything and printed all possible debug info in the notification callback to a logfile). The payment was marked as paid as the notification dictated, so all seems ok for me.
Forum: Plugins
In reply to: [Events Made Easy] Membership Stripe paymentWhen a person pays in stripe, stripe calls back to your server (from their infra, so not the ip of the client), while the client gets redirected to your server. So I check the callback (notification) for info *and* also check the client upon being redirected to EME. Since I can’t trust the latter for happening (like if someone closes the browser before redirection happens), the notification from stripe is equally important.
But a status code 500 normally means a php code issue, but since you’re saying other payments are managed just fine, it is something weird …I’ll try to test on my end too to make sure notifications are handled 100% correctly.
Forum: Plugins
In reply to: [Events Made Easy] Membership Stripe paymentThose lines come from stripe doing a callback to you (to inform you of a payment status).
But one of the calls gets a 500 reply back from your server, meaning some error occurred there. While I try to trap stripe errors, this code 500 typically means something happened on the server (code-wise error or something unexpected), most of the time your php logfile will then tell you what happened.
The other line is 200, which means there all was ok (in your booking/member overview you can see the payment date, normally that should be about the same time. Also your stripe portal might give you info on the failed call (unsure though).Forum: Plugins
In reply to: [Events Made Easy] Membership Stripe paymentI use other payment methods, which work ok for memberships, so: the error is not in the generic payment method handling for members. Since you also say it works fine for events/bookings, the error is not in the stripe payment handling code.
So: I’m guessing the user closed his/her tab immediately after stripe payment *and* the stripe notification did not come through on the website. Can you check your webserver logfiles for lines containing “eme_eventAction=stripe_notification” in the url?Also: can you reproduce the problem? Did you try with a stripe test account?
Forum: Plugins
In reply to: [Events Made Easy] Filtering discount codes not workingConfirmed (but it is there for some versions already 🙂 ).
This fixes it:
https://plugins.trac.wordpress.org/changeset/2750920/Forum: Plugins
In reply to: [Events Made Easy] Style for Markers on MapThe marker is an icon (image), not just something easy to change. When showing the map for a single location, you can already change the marker (map icon) to something of choice, but in the shortcode showing the list of locations this is currently not possible.
Forum: Plugins
In reply to: [Events Made Easy] Error after the validation of a formThe error message and your filter are not related. This error message pops up if a frontend nonce doesn’t correspond with the expected value. Typically caused by caching plugins that try to cache the whole page and thus prevent a correct nonce to be rendered in the form (as a hidden value). Try disabling the cache plugin.
Forum: Plugins
In reply to: [Events Made Easy] Bookings list images of usersJust checked #_IMAGE as per your example, and there it is first “taken” as a location placeholder, not a person placeholder. As the doc for person placeholders mentions, you should use #_PERSON as a prefix for person placeholders, in this case #_PERSONIMAGE. It doesn’t interfere for #_IMAGETHUMB because there – for a location – I only support #_LOCATIONIMAGETHUMB. The original use of #_IMAGE for a location comes from quite some time ago, but I’ve now removed it in the code (so in fact in the next version #_IMAGE will work, as it will only get interpreted for people).
Next version will show it as a separate column, see this changeset:
https://plugins.trac.wordpress.org/changeset/2746477/Forum: Plugins
In reply to: [Events Made Easy] future=0 is not working anymoreno reaction, marking resolved
Confirmed and fixed here:
https://plugins.trac.wordpress.org/changeset/2745899/Forum: Plugins
In reply to: [Events Made Easy] Bookings list images of usersJust tried #_IMAGE, and works fine in the templates used by the eme_people shortcode. In which context are you using it?