Forum Replies Created
-
Posts
-
Hi Dave – great question! Unfortunately, as discussed in this thread, that isn’t currently possible due to limitations in the Eventbrite API.
My understanding is that the payment options our plugin facilitates are the only ones currently supported – unless you set up an event directly on eventbrite.com itself, of course – and anything beyond this will only become possible as and when Eventbrite further develop their API.
To summarize for the benefit of anyone else who might encounter similar difficulties, the problem seems to have been a directory named events at the same level as the WordPress installation (which happened to contain a file called index.html in this case).
That meant requests such as website.com/events/ were returning the HTML from that directory, due to the way the web server is configured to work.
David: if that answers your query I’m inclined to close this thread – but let me know if we’re off-beam here or if you need further assistance 🙂
Excellent, I’mm close this thread in that case. Of course if you need further assistance please don’t hesitate to create a new discussion and one of the team will be happy to help 🙂
Hi webplacement, so you’d need to add a link somewhere to your Add Events page, which can be found at this URL:
http://livekauai.com/calendar/events/community/add
You might do this by placing a link in your menu (login and navigate to Appearance > Menus) or by adding a bit of HTML (possibly using our Before HTML option found at Events > Settings > Template > Add HTML before calendar).
Does that help here?
Hey again Roberto!
Rob is currently busy overseeing the latest set of releases and has asked me to take point here – he had jumped in here to try and facilitate resolution as quickly as possible for you and, of course, he will continue to monitor the thread – however his day-to-day role isn’t really in answering threads here and I’ll be more than happy to take over.
As I see it, there are two things to tackle here: the first is how you might introduce the change suggested by your theme’s developer in an update-resistant manner (ie, not having to “hack the core” of our plugins). The second is whether we should introduce the code change suggested by the team you enlisted.
Template Overrides
Happily, all templates contained in the plugin’s views directory, including list.php, can be safely overridden – reducing the risk of an update wiping them out – by simply creating an events directory in your theme folder and adding the customization there.
We have a great tutorial for this, you can find it here, which will walk you through the steps involved.
Suggested Fix
One of our concerns with introducing the change suggested is that, while it plays well (and is even necessary) in the case of your site and theme, it may have an adverse impact on other users of The Events Calendar if we were to include it in our default views – we also know from experience that it is generally unnecessary (indeed this is the first time I have heard of a theme requiring this particular injection of code).
Also, we do have a slight concern about the nature of the “fix”:
wp_reset_query();To paraphrase the WordPress documentation, this function destroys the previous query used on a custom loop and should be called after running a (custom) loop to ensure conditional tags work as expected.
That does rather suggest that your theme has introduced a custom loop which runs before our list template and for whatever reason doesn’t clean up after itself. For that reason we will not be introducing this code into our plugin.
I hope that explains our position a little better – in addition to giving you a means of safely operating both your theme and our plugin.
If you have any further questions please don’t hesitate to get back in touch.
Thanks!
So as per our emails I’m going to close this since it no longer seems to be a problem – of course feel free to create a new thread as needed!
I’d be happy to 🙂
That url brings a login necessity which I dontn want to have
So if you take a look here you can see that there is an option to allow anonymous submissions, negating the need for users to login.
more importantly, there is a mouse-over add when you mouseover the “login” link.
Not quite sure what you are referring to here – can you explain further and/or link to the page where you are seeing this?
Well, realistically this will take some re-engineering followed by a round of quality assurance to establish a final solution.
Using different venues/venue names on Eventbrite, importing and manually editing locally and on Eventbrite – and I totally appreciate that is cumbersome – is the only workaround at present, unfortunately.
Hi Greg!
Unfortunately it is sounding like you are up against a recognised issue, as detailed in this thread:
Currently I understand this is slated for revision in our 3.0 release. I’m really sorry for any inconvenience this creates in the meantime.
Well, that’s what the Community Events plugin does. Once activated, your users should be able to visit a form on the front end of your site and submit events. Normally that form is found at:
www.your-website.com/events/community/add
That isn’t a capability that Eventbrite Tickets will bring to the table – I just want to be certain we’re understanding each other there.
If you’re absolutely sure you want to make a change what I would suggest is emailing us with a copy of your receipt for one of the plugins, reference this thread and request a refund – you can then purchase Eventbrite Tickets as a replacement (so far as I know our system will not simply allow us to transfer your license from one product to another).
Thanks!
Hi Roberto: Rob may not be able to answer this until later in the day or possibly tomorrow, but I just wanted to acknowledge that we had indeed seen your post.
Hi webplacement!
What I need is for users to be able to post their own events on the front end, which looks like I need EventBrite.
Sounds like Community Events should meet your needs: our Eventbrite add on allows events to be submitted to (and imported from) the Eventbrite platform, which is slightly different from simply creating events to be displayed on the front-end.
Does that clarify things at all?
