Forum Replies Created
-
Posts
-
Good evening W David,
I’m sorry this made you site crash. Thank you for trying.
Just out of curiosity, did you copy the<?phpstatement as well ?Perhaps, I should have specified, but this is not necessary if there is already such a statement in your functions.php file.
In any case, as promised, you will be notified as soon as the bugfix is out.
Thank you for your patience,
Best regards,
Geoff B.
Good evening Robert,
Thank you for answering my questions. I appreciate your patience while we are trying to figure out what is going on.
From the screenshot you sent me of a ticket, I can still see 10 tickets available, so I am pretty sure this specific ticket is not affected by the behaviour you described.
Could I have a screenshot of a ticket who’s stock goes to zero after clicking on “Update” ?
In full disclosure, we greatly improved the way stock is handled for WooCommerce tickets in 4.1.
To make a long story short, here are a few of the improvements in question:- We reuse WooCommerce’s exact functions to handle stock, including removing the stock of a ticket when the order is not yet set to “completed”.
- We now breakdown the remaining stock based on status of the order (pending, completed, etc..)
Which leads me to another test I would like you to try. Once you click on Update and the stock of the ticket goes to zero, would you mind going over to the actual WooCommerce product and telling me what the stock count is on it?
Best regards,
Geoff B.
Hey Roxanne,
I’m happy to know this worked out for you!
You are welcome back on our support forums any time 🙂
For now, I am going to close this thread.
Have a great week!
Geoff B.
Hey Greg,
I’m sorry this didn’t work out for you.
The dates and months names will not come from the Events Calendar directly, so although your idea is good, we’ll have to find the root of the issue elsewhere.
As a first troubleshooting step, could you please provide us with your system information in a private reply ? (following the instructions found in the link)
Also, could you provide me with the actual URL to the site so that I can run some tests ?
Best regards,
Geoff B.
Good evening Milan,
Thank you for your answers.
I am glad you could isolate the issue to only one event.That being said, I would still love to get to the bottom of this and find out why the event in question is not translating properly.
To be able to do so, I will need to be able to reproduce your exact conditions. For that purpose, could you:
- As a first troubleshooting step, could you please provide us with your system information in a private reply ? (following the instructions found in the link)
- Send me a link to a screenshot of the details of the untranslatable event in question (the “Edit Event” screen) and a similar screenshot of a previous event that worked properly
- Tell me which is your default language in your WPML setup
Best regards,
Geoff B.
Hey Malcom,
Actually this is not due to a conflict, but rather to a fix provided with the latest update. We apologize for the confusion created by the nature of these messages.
Would you mind reactivating the proper plugins manually in your plugins page and checking if the issue still persists ?
Best regards,
Geoff B.
Hey Stu,
I’m really glad that this worked out for you.
I will totally take you up on your suggestion and investigate this further on a build of mine and get back to you with my findings.
Have a great day!
Geoff B.
Hey Lang,
I’m happy we finally solved everything.
You are welcome back on our support forums any time 🙂
For now, I am going to close this thread.
Have a great week!
Geoff B.
Hey Brian,
You are so right, this is an odd one.
I’m not sure what happened there, but I’m mostly happy that the issue is gone on your end.I also want to reiterate that your CSS skills are spot-on so don’t let a “ghost in the machine” tell you otherwise.
You are welcome back on our support forums any time 🙂
For now, I am going to close this thread.
Have a great week!
Geoff B.
Hey Amy,
Thank you for providing the additional information I requested.
This allowed me to run a bunch of tests.
When the extra info fields are indeed set to “required”, there is no way to bypass the extra information fields. So the good news is that there is no glitch with the plugin per se.But the bad news is that what can be done is to input a “blank space” in each of these fields. I have a gut feeling this is what this user did (if you get a chance to ask the question, I would like to know if that’s the case out of curiosity).
I wish I had a better answer for you, but for now it’s the best one I have.
Is there anything else I can help you with on this topic today ?
Best regards,
Geoff B.
Good morning Gordon,
Don’t be embarrassed about this, we are definitely here to help.
My question was just to make sure to leave no stone unturned. I’m super happy that it worked for you!You are welcome back on our support forums any time 🙂
For now, I am going to close this thread.
Have a great week!
Geoff B.
Hey Christian,
I’m sorry this did not work out for you. The reason I suggested these steps is because the main 2 causes for error 500s are:
- Corrupted .htaccess files
- Plugin not found
With that in mind, could you:
- Go over to Events -> Settings -> Community and take a look at the community rewrite slug to see if it’s still intact ? If it is, could you re-save it the settings on that page ?
- Go through our testing for conflicts procedure (preferably in a staging/dev environment or local install of your WordPress website) and let us know what you find out.Basically the goal here is to revert back to a bare WordPress installation to see if the problem persists. It also allows us to pinpoint what the cause of the issue is.
Best regards,
Geoff B.
Good morning Lee,
I am sorry the import did not work out for you.
I tried to reproduce this on my end, and I think there are couple of things that might explain what’s going on:- First of all, I am noticing a non-standard character just after “Marquee Dayclub” (I’m not sure what that is supposed to be, but I am positive it is not UTF-8.
- The other thing that might be going on is that there is a trace of previous import attempts on your website. The way this works is that the plugin is trying to prevent duplicate imports. As such, if it can match the event you are trying to import to an already existing event, the event will not be imported. To be sure, the best way would be to clean the tribe_events post types from your Database prior to the import. I would recommend a backup first before you try this manually or with the aid of a plugin such as: https://wordpress.org/plugins/wp-optimize/
If none of these explanations seem to fit the bill, would you mind telling me step-by-step what happens as you are trying to import the said files ?
Best regards,
Geoff B.
Good evening Torey and welcome back!
Thank you for reaching out to us.
We are sorry to hear about Facebook picking the broken version of the URL.
I would love to help you with this topic.You are absolutely right, the front-end URL works great, but slugs with the “-” characters are generating an extra backslash in the backend and apparently for some applications such as Facebook.
The good news is that this is a known bug and that our Dev team is working on a solution.
Unfortunately, I cannot commit to a release date at this point. But stay tuned, you will be contacted as soon as a fix is out!In the meantime, here’s a snippet that was used to make that URL work with another application (RevSlider).
Perhaps you could tweak it and adapt it to your liking as a temporary solution ? https://git.io/vVlM5We apologize for any inconvenience this is causing in the meantime.
Best regards,
Geoff B.
Hello again Robert,
Wow, this is an unlucky streak for you.
Hopefully we can resolve this quickly.It seems like you might be experiencing some type of conflict with your WordPress theme, a customization or one of your plugins.
Could you also please go through our testing for conflicts procedure (preferably in a staging/dev environment or local install of your WordPress website) and let us know what you find out.
Basically the goal here is to revert back to a bare WordPress installation to see if the problem persists. It also allows us to pinpoint what the cause of the issue is.
Let me know how that goes.
Best regards,
Geoff B.
