Forum Replies Created
-
Posts
-
I appreciate the update Nathan. I too have been looking into this a bit more. If I discover anything of interest I will share it on wp.org with the other author. Cheers!
– Brook
Since this topic has gone for a spell without and update we are going to archive it. If anyone needs assistance with this, or a similar matter, please open a new topic. We would love to help.
Cheers!
– Brook
Since this topic has gone for a spell without and update we are going to archive it. If anyone needs assistance with this, or a similar matter, please open a new topic. We would love to help.
Cheers!
– Brook
Since this topic has gone for a spell without and update we are going to archive it. If anyone needs assistance with this, or a similar matter, please open a new topic. We would love to help.
Cheers!
– Brook
Since this topic has gone for a spell without and update we are going to archive it. If anyone needs assistance with this, or a similar matter, please open a new topic. We would love to help.
Cheers!
– Brook
Since this topic has gone for a spell without and update we are going to archive it. If anyone needs assistance with this, or a similar matter, please open a new topic. We would love to help.
Cheers!
– Brook
Could you try getting all those folks to use the same API key? If that’s not an option, you could swap around user permission so that only the one admin who needs to can edit events. Either option would almost definitely stop this from happening in the future. There is very little doubt that some form of edit, whether it is bulk or perhaps incidental edits made from another plugin to the posts database is causing this issue. So if everyone shares the same key, or if folks are prevented from making edits, it should fic the problem.
Longer term, event 3.10 will slo help by notifying people when this is about to happen.
Will one of those options work?
– Brook
Howdy again Nathan,
I am not sure what happened to my response from the other day. I was checking back in to see if you had followed up, when I noticed the response I drafted never submitted. đ
I really appreciate the offer to login. Unfortunately due to legal reasons we can almost never do that.
I tested your API key on my website. I was able to import that event fine. Only a second import had the issue. I then did my best to replicate all of your sites settings, same thing. It worked great for me. It was only after I had already imported an event that it would give me the duplicate error message, and that message went away the instant I trashed an event.
This leaves us with only one remaining likely cause, a plugin conflict. It is very possible that a conflicting plugin, or perhaps even your theme, has something about it that does not mix well with certain imports. Particularly if that plugin has a Facebook API tie-in of its own. Would you mind doing a testing if there is a conflict? If you diligently follow the steps in that first subheading, disabling your other plugins and switching themes and such, then try importing event again, does it work?
Please let me know if you have any questions. Cheers!
– Brook
Thanks for sharing what you’ve tried so far. Good call updating those plugins.
Also, because our site is live, we did a dev. installation for additional testing, but there we cannot update the plugin, because it doesnât recognize the Verif. code.
I understand that. We actually have a knowledgebase article about this problem. It also outlines that you even transfer the license from your dev site to your main one rather easily.
Activate debug mode and get the results. There is nothing related to the plugin directory or URL of the form in the debug.log file. Are you able to give us more information how to find where in your scripts this data about who can submit and who cant is stored, because what we see now is that â if the person is logged â its working?
I definitely can get you the script. I hope it will be of help to your debugging, but I worry that it won’t shed much light on the matter. The file is /wp-content/plugins/the-events-calendar-community-events/tribe-community-events/tribe-community-events.php and the line 1369 within that file.
Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /public_html/wp-includes/functions.php on line 3370
Notice: wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in public_html/wp-includes/functions.php on line 3370
I am glad you got your logging setup. Those do not appear to be errors related to our problem though. đ Those are PHP Notices. Usually notices do not prevent the page from loading. And actually, it’s unclear if those notices are even coming from the Community Submission page without the full log. We are likely looking for a PHP Fatal Error, or perhaps a Warning rather than a Notice.
If I were in your shoes the next thing I would do would be to try a conflict test. But, perhaps you prefer to keep looking through the log file or investigate that script you asked for? Definitely go with your preference. But, just know that often times conflict tests can take as little as 5 minutes, and can narrow down the problem. Sometimes even solve. Usually when I am debugging they are one of the first thing I try.
Please let me know how it goes, or if you have any more questions along the way. Cheers!
– Brook
That is not right, and definitely the source of the problem. That really helps narrow matters down. Thank you! It would seem that first of all reimporting this event will fix it.
Do you have any other admins on the site? When one of them edits an event, but either does not have an EventBrite API key or has one that is not authorized by EventBrite to make changes to that event, then the event becomes decoupled from Eventbrite. When it’s decoupled tickets will no longer appear because it is no longer an EventBrite event in WordPress’ eyes. This is certainly annoying, and we are adding a nice warning in 3.10 in scenarios where this might happen, asking users if they are sure they want to decouple the event. One permanent fix to avoid this in the future is to make sure every admin shares the same EventBrite key, and make sure that each of them has it in the Profile as an empty one can also cause problems.
There are also some possible hypothetical scenarios where the event can be decoupled. But, usually it is another admin on the site. Does that sound like it might be the source of your problem?
Does that all make sense? Please let me know. Cheers!
– Brook
Alright Jay,
I was just able to import that event on an install with your API key, and the ticket area showed properly.
Could you go that event in WordPress, click Edit Event, then scroll down to the ticket area? Does it show the Community Meeting ticket, and an “End sales” date of “2015-05-06”. I know it shows those things on Eventbrite.com, but I am wondering if your WordPress install shows the same.
After doing the above, could you try moving the event to the trash in WordPress, emptying it from the trash, then reimporting it? That could help narrow the problem further. If you are able to import it and it works, then at least we have a temporary solution as well.
Thanks Jay. As ever let me know if you have any questions along the way, or if anything was unclear. I definitely want to be of assistance wherever I can.
Cheers!
– Brook
