Forum Replies Created
-
Posts
-
I’m not completely sure if that is possible but let me check and I’ll get back to you. It is alternatively possible to show the actual WooTicket price on the front end (rather than entering the price data twice) if you don’t mind doing a little customization work?
Very soon!
I can’t give a firm date, but beta testing is complete and essentially we’re doing the last round of checks and updating our documentation in preparation – so I would tentatively suggest sometime within the next month.
Moving from 1.3 to 2.0.11 is quite a jump and ideally we recommend regular updates from one minor release to the next to avoid problems like this.
What I’d suggest here, if possible, is upgrading your 1.3 site to 1.3.3 first of all and then upgrading to the current version. You should then be able to export/import a little more easily. You can grab 1.3.3 here:
http://cl.ly/1j0n2y132F0i0n332w2m
If that isn’t possible you might need to manually amend the import data so that references to sp_events are replaced with tribe_events.
I don’t believe any of the built-in settings are going to help here – all I can really suggest (particularly since this still seems to relate to a custom piece of work, rather than a view generated by the plugin itself) is building a custom query to extract exactly the information that is required to fit your needs.
Sorry we can’t offer up more here – and good luck!
It’s hard to say; one thing that frequently causes problems with menus is the use of default permalinks, so if your URLs look like:
abc.com/?p=123
Then please try enabling “pretty” permalinks instead, as this is virtually a requirement of our plugin:
http://codex.wordpress.org/Using_Permalinks
Beyond that it’s difficult to provide much advice since right now we can’t access your site. I hope the above steps help, however. If not and you can post screenshots or share code I might be able to offer a couple of other suggestions.
Hi tempomedia,
That’s unfortunate – it does sound like it might be a conflict, however. If you are unable to run through our normal troubleshooting steps in your production environment perhaps you could replicate the site in a development environment and run through them there?
Alternatively, I would like to do a fresh install of the plugin, but obviously I want to keep all my listings. Where are they kept? And kind of file is it – can be easily re-imported afterwards?
They are maintained as database entries, primarily within the posts and postmeta tables. Deactivating the plugin should not result in those same entries being lost – so assuming no core files within the plugin have been edited if you simply deactivate, upload a fresh copy of the same plugin and reactivate they would all simply come ‘back to life’.
It’s not impossible that this would solve the problem, but it’s also quite possible that it would not as, essentially, nothing would have changed (unless you or someone else has edited core plugin files, of course).
Actually exporting then purging all events data (including settings), reinstalling and finally importing that data would be more involved and if you are unsure of how to proceed on that front then I’d recommend you use the services of a suitably skilled developer.
What I really have to stress though is that you should make a complete backup and ensure you know how to restore that backup before you begin!
Caching (including query caching at the database level) can make a huge difference when set up correctly.
Regarding 3.0 all I can say is … we’re very close!
I can’t find an existing discussion about this either (not to say that there aren’t related threads out there) but what I can say is that this is not currently supported by the widget.
So, at this time, you would really need to do some customization to make this happen – and based on what you’re describing that would basically mean creating a new widget (albeit you might base it on the code of the existing list widget).
It would of course be great to hear back from you and see your final solution if you do press ahead with this. Remember also that you can suggest new features on our UserVoice page, which also lets other users indicate their support:
You can indeed suggest features and others can then show their support:
https://tribe.uservoice.com/forums/195723-feature-ideas
Thanks for the feedback!
The good news is tickets will be created as virtual products by default as of WooTickets 2.0.
In the meantime you could take a look at the snippet suggested here – you would probably need to tweak it a little but it might form a starting point for you.
Anything is possible!
You would need to implement this as a piece of custom work, however, as there are no pre-built tools that do quite what I think you want. There are some great resources (check out the list in our Useful Resources widget over on the right) on this site and various tips and snippets in the forum that could help.
Good luck!
You could probably tweak the event stylesheet to do this … can you look over our themer’s guide and see if that gets you headed in the right direction?
