Forum Replies Created
-
Posts
-
Guys I’m inclined to see this as a WooCommerce issue rather than WooTickets as such, but as always we’re open to your feedback if you can see merit in us changing the default product type.
Hi guys – just jumping in here since Jonah is away right now.
Are you aware of any errors that are being reported during the import process – or is this occurring during auto-imports?
I do know that historically certain categories of error could cause Facebook Events to “jettison” the import, however this sometimes took place after the event post itself had been created – so that’s a possibility here.
One way to try and ascertain if this is happening is to visit Events > Import FB Events and see if you can manually reimport the same event as before. If you can, look out for any errors that might be reported.
Thanks!
If I add an “echo” to the php inside of the JS, no alerts come up at all.
Can you share the actual generated output, so we can see what is being placed inside the double quotes?
Hi Jenny – You would need to echo the output from tribe_get_full_address() otherwise it won’t be printed out inside the script element.
Hi Tim! I’m going to move this across to the WooTickets forum, but the URL for the thread will remain the same.
The basic answer is yes, you could use it to sell beach permits – especially if they were date-bound and so they are basically similar to any other ticketed event.
A PDF ticket is emailed to the customer; currently customizing this isn’t particularly easy and would require some solid coding skills – however it is definitely possible.
Hi Toru – so you would really just need to include an appropriate definition in the arguments you pass in when creating your settings tab:
I don’t know of any perfect solutions that are out there, off the top of my head. There are one or two threads here on the Pro forum where we looked at a system of checking if an event was recurring then listing the recurring dates discreetly underneath the main event (or even hiding them altogether).
The downside was that, particularly on a site with a full and busy calendar, pagination on the upcoming events list was affected and the number of results per page was potentially inconsistent.
Probably the best solution here is to build a custom view and create your own logic for retrieving and paginating results that meets your precise requirements.
With The Events Calendar 3.0 on the horizon, I’d also be wary of committing time to something that might not work or may be unnecessary when that version arrives.
Hi Karen: the micro-data format for events which as you say is used by Google Data Highlighter is integrated by default.
No that’s a good catch – after all the default country is selected, so it’s not unreasonable to expect the province/state to also be populated. I’ll log it as a bug, thanks.
Excellent, glad we could help.
Just to highlight: Andy is a member of the community, rather than a Modern Tribe team member as such – but he’s extremely knowledgeable about our products and helpful to boot, so particular credit is due to him 🙂
Hi Salvador: is the remaining problem simply getting the full month name? If so, simply replace ‘M’ with ‘F’ – it’s the same format as used by PHP to describe date formats.
Anne: I’m just jumping in here as Jonah will not be around this week. Regarding that fatal error, where are you seeing it exactly – in a table in the database, or is Portable PMA failing with that error when you try to access it?
And finally, I’d love to be able to just turn off the image importing. I love importing the images, but I hate that the system is importing the Facebook default image over and over and over again.
A related problem was reported last month, I think, except in that case the aim was to replace the default Facebook image with something different.
In any event I believe a change was put in place and ought to be available as of the next release which should allow additional control over this sort of thing, albeit it will still be necessary to add a code snippet (ie, to your theme’s functions.php file).
I do think it would be useful to have a facility to turn off image import though, and will log that as a feature request.
In addition, if I choose not to import an event or I delete an imported event, instead of publishing it, I’d love for it to go away.
I see the problem; and I’m not sure that there is a good solution here. I can propose this as a feature – but I’d definitely appreciate your further thoughts on how for instance you’d deal with a scenario where you accidentally delete an event and do wish to re-import it?
My colleague Leah and I were discussing this and thought a viable approach could be to auto-import only events created after the last import took place – does that sound like a strategy that would work for you here? I can’t guarantee it will be implemented, but I can certainly log it as a new feature request.
