Forum Replies Created
-
AuthorPosts
-
Nico
MemberFolks!
Here’s the updated snippet for the ‘Custom QR Check in’. Just to be sure we are all in the same page let me review what the snippet does, where to place it and how to customize it:
What’s the snippet doing? Basically it’s disabling the default mechanism for checking in tickets via QR tickets. On the other side we are proving a new method to do this, which is basically the same but redirecting the user to the front-end of the site instead of redirecting them to the back-end attendee list. This also enables tweaks on the conditional to set which user is allowed to do the checkins.
Where to place this code? Easiest way is to place it in the theme’s (or child theme) functions.php file (making sure yo don’t copy the php opening tag unless it’s necessary). But as this article explains there are some options: Adding Code to Your Site When Youβre Not a βCoderβ.
How can I customize the snippet? You can change the URLs for successful / failed QR checkin. Successful meaning the user had the permissions to checkin the ticket and failed meaning the opposite (for example if a non-logged in user tries to checkin a ticket).
All that said, here’s the snippet:
https://gist.github.com/niconerd/24bc1f048b652e4677ccf9dc408da7ed
Just let me know if it works for you,
Best,
NicoNico
MemberGood news! Looks like the issue with ZIPs containing the wrong license has been fixed. The workaround in your case should be the same, just making sure the correct license is in place π
Nico
MemberHi there Karen,
Thanks for getting in touch with us! I can help you here…
For some cases it’s possible to use the same license for both sites as explained here: Using One License for Live and Dev Sites. If that’s not possible for your case, just download the latest release candidate for PRO (from your downloads section) and just ignore the messages. If that’s the case then make sure to keep the plugin up to date (specially if you think you’ve hit a bug).
Hope this helps,
Best,
NicoNico
MemberHi there Richard,
Thanks for reaching out to us! I just fixed that for you π
Please let me know if everything looks right from your side,
Best,
NicoNico
MemberHi there Sonovia,
Thanks for reaching out to us on this!
First of all I’m sorry but it’s not possible to add another contact email to your account, but you change the email if you want from your account in the site.
Regarding the license key issues, you can use the steps in this article to get the right domain on the license: Moving Your License Keys. You are probably missing the step to disconnect the license.
Please give that a try and let me know if it fixes the issue,
Best,
NicoNico
MemberHey @dallasanimals,
Thanks for the report, and sorry to hear about this issue. I could confirm the issue and our team is working on a solution for this. Seems like ZIPs downloaded from the site are not getting the correct license in.
For now you can go to ‘WP-Admin > Events > Settings > Licenses’ and enter the correct license from your account and ‘Save Changes’.
Please let me know if that makes things right on your end,
Best,
NicoNico
MemberThanks! Noting that in the ticket π
Nico
MemberOne question I forgot to ask, Do you recall how the renewal was triggered? Was it from the renewal email? From the WordPress back-end? Directly from your account in the site?
Thank you very much,
NicoNico
MemberHey Jared,
Thanks for getting in touch with us and sorry to hear about this issue with your renewals π
We are actively looking at the issue right now, to see what happened. For now please note this won’t affect the plugins functionality in the site.
I’ll get back to you on this as soon as possible…
Best,
NicoNico
MemberHi there Nicole,
Thanks for getting in touch with us and sorry to hear about this issue π
Before we jump into seeing what’s going on please note that these notices don’t affect the plugin functionality in the site. This might have happened because the ‘Personal’ license type allows just one site per license. As the domain changed our system is understand you are still using the license on the old domain + the new domain is trying to use it as well. To avoid this you should dis-connect the license from the old site as this articles explains β https://theeventscalendar.com/knowledgebase/moving-your-license-keys/
Please let me know if that fixes the issue,
Best,
NicoMay 8, 2017 at 7:24 am in reply to: Can I detach licenses from one site and move it to another? #1280250Nico
MemberHowdy John,
Welcome to our support forums and thanks for reaching out to us!
Sure, you can move your license from one site to the other. In some cases you can use the same license in both environments: Using One License for Live and Dev Sites.
Hope this helps, please let me know if there’s anything else I can do for you,
Best,
NicoNico
MemberHey Mark,
Thanks for reaching out! I just adjusted your license manually, seems that this was due to a minor update in our site that allowed customer to re-new + change license level at the same time.
Please let me know if there’s anything else I can help you with,
Best,
NicoNico
MemberHi there Tina,
Thanks for getting in touch with us and sorry to hear about this issue π
We are aware of some issues with the update notices and invalid license messages, and we are in the road to fix those. In the meantime can you please share a screenshot of your license tab in the backend (WP-Admin > Events > Settings License Keys). Be sure to mark the reply as private to this is not publicly visible in the forums.
Thanks,
NicoNico
MemberHey Tina,
This thread seems to be a duplicate of: https://theeventscalendar.com/support/forums/topic/your-license-key-is-invalid/
I will close this one and help you over the original one π
Best,
NicoNico
MemberThanks for chiming in Stein! And thanks as well for reporting this to the Ninja folks.
In any case I just logged an improvement ticket to make sure this is not incorrectly marked as suspicious / malicious by any of this scanners. I’ve linked the new ticket with this thread so we can give you a heads-up when this is “fixed” (not that there’s anything wrong, but we can surely refactor the offending line to not be flagged).
Hopefully we can fix this soon to avoid further confusion π
Thanks once again for the report folks,
Best,
Nico -
AuthorPosts
