Forum Replies Created
-
Posts
-
Jamie,
I have carefully reviewed this and ensured that magnification is not on. I’ve also tried with W3TC disabled entirely. Lastly, I’ve ensure to clear Varnish on the server and I’ve done all of those cleared and still can not get this to work.
Even though I absolutely knew that due to the way in which the error happened that it absolutely was not the theme, I’ve also check that as well.
At this point, I’m very very frustrated with you and the type of support I’m getting here. I’me getting shifting blame on things that aren’t relevant if you listened to the order in which the issue happened, I’m getting terribly slow responses, and I’m getting ignored on some very important points I’m making here altogether.
At this point, I want this ticket to get escalated to someone that can help more. This is never going to get solved spending 1-2 days between responses, nor will it get solved when you are blaming things on a theme that could’t have possibly been the issue.
My client is getting very rightfully pissed off here that this still doesn’t work after a week and a half of this.
PLEASE, please get me someone who will speak with me on the phone, chat, or otherwise so we can make some real headway here.
I’m standing by!
Micha
Jamie,
I am really getting frustrated here. I know and understand your point about theme and plugin conflicts. I get it and deal with it daily.
However, I have said this a number of times, but you are not responding in a way that acknowledges this: When first installing this plugin a couple weeks ago, this issue did NOT occur. Then, without ANY update of ANY kind to plugins, theme OR WP core, the issue started manifesting.
I’m sorry, but if the theme was the culprit, then it would have been so at the start. Simple as that. If you think otherwise, then we have a big problem and I’m going to need someone else on this ticket who can address troubleshooting issues in a logical method. Put simply, there is not way that the theme or plugins caused this because none of theme were updated or changed in ANY capacity during the time frame that this worked, then stopped working.
Moving on…
The caching is a potential here and I will review these two suggestions and see if updates here will fix this issue. I’ll reply back after I’ve had a change so review this possibility.
Best,
MichaJaime,
This is frustrating to me, but we keep missing the fact that this worked for over a week using the same theme, the same plugins, the same everything. I’m all for trying new things, but if the theme didn’t change, then why did it work and then stop working? Why is it STILL working for a couple other sites in the same network?
If you can answer those questions in a logical way that illustrates how it could be working still for some users and did work for this user, but then suddenly stop all with the same theme version AND be caused by the theme, then I will most gladly do this testing.
Until then, I’m going to go under the logical assessment that it can’t be the theme if it’s still working for another user and it did for this user. My best guess is some cache change and/or something change with PayPal. But the plugs and themes don’t seem likely under what I’ve been saying.
Please advise.
Micha
Jaime,
Replies:
Multisite License – yes, I figured that out. We’re only using it on 2-3 sites currently, but if we get these bugs worked out, we may delay network side and get the unlimited license. We can’t do that under these conditions though.
Debug log – replied privately with link. Since it’s a multisite, and a large one at that, the logs will be rather large but I didn’t want to trim anything out.
Host – we are currently on Cloudways using a Digital Ocean stack
Theme related errors – So, yes and no. I have not ran through a purchase using the default theme. However, and this is huge, I very clearly told you that the first thee events published worked. they worked perfectly. Now, for some reason, the next ones published do not (12 of them). If this was theme caused, then that would have also been evident in the first three. So, at this time, I’m not going to switch and test something that isn’t the cause logically. The amount of effort to do this isn’t worth it.
Attendee Records – Please see above AND the initial bits of information on this thread. I’ve clearly stated several times now that the first three events DID WORK… and now the
Other notes – it’s worth noting here that since 3 events worked, then a week later the next 12 don’t, that no one changed any themes, plugins, snippets, etc. anywhere. The code base on this network is strictly controlled due to the nature of the client. I did, however, update the plugins at your request yesterday, but that was AFTER the failure.
Please let me know what is next.
Best,
MichaUpdate, while logically, this update wouldn’t have anything to do with it since it worked, then stopped all with the same previous version, I did do a manual update of everything as requested. The issue is still there.
Let me know what to try next.
Micha
Jamie,
So, I just updated The Events Calendar version 4.6.18. Pro and Tickets Pro and NOT showing on my site as having a new version when I go to the update tab.
Also, and more relevant, the issue and the timelines make these irrelevant updates. First, the issue on the first three events published did NOT occur, as mentioned above. then, the later events started having this issue, however no updates to anything were made in the middle. Not one.
Secondly, all the updates here appear to be related to Event Brite according to the dev notes. Not sure it would help anyways.
Where does that leave us?
Micha
Jaime,
this works. Please request that this get added to the core. when it does, you should notify us so those that have used this will remove this plugin.
I’m marking this closed. Thanks.
Micha
Jaime,
I found the culprit causing the issue, but need help fixing. So, after the last post, I went into the Divi settings because I remembered a post type limit setting. My theory is that somehow the setting is controlling all post types. So, I changed the setting “Number of Posts displayed on Archive pages”. Whatever number that shows, is how many events show in the events calendar slug. Similarly, the category will control the event category, etc.
This means that somehow this setting is effecting all post types, not just blogs.
What do I need to do here?
Micha
Jaime,
Like I’ve said in the other tickets, and like what you should see with the included support snapshot, these are the most recent versions.
That said, I did use the plugin you suggested and was able to turn on all plugins without failure, but when I turned on the theme, I got the failure. the theme is Divi (which I hate but am forced to use here).
Do you have any insight into what specifically in the theme could be causing this to happen?
Jaime,
In all my open tickets I have the most recent version of all of your plugins. You can see this in the support info I shared.
No, the users don’t see an error. the form is filled out, then redirect to PayPal happens and the payment is made, but the form nor the ticket purchase is being saved. So, the client has purchases coming in through PayPal, but no idea who is making them, other than the PayPal emails. In this case, there are critical questions being asked in the registration, but those aren’t being captured due to this issue.
I turned on logs and will send in a day once they collect some data.
Micha
Well, aside from the fact that that is a pretty slow response for paid support, yes you are correct in that is what we are using. We have tickets, tickets pro, using Tribe commerce.
Please advise when this patch is fixed.
Best,
Micha
