Forum Replies Created
-
Posts
-
Hi!
Taking a look at the code in question (where the error – or at least one critical error – is arising) I can see this.
Note the closing and opening paragraph tags that have been injected inside that snippet of code – that’s likely to be the main problem here.
Some themes, possibly including yours, either re-order the stack of filters used to process content before it is displayed or else add on an extra layer of their own and this can have an unfortunate side effect in that paragraph and break tags are inserted in all the wrong places.
It could be worth checking in with your theme vendor and seeing what they recommend. Some themes for instance have special ‘shortcodes’ that look like this:
[raw] [/raw]
(It may be different in the case of your theme though) and these can be used to wrap up or mark areas that ought not to be affected by the extra processing. So, right now, I would suggest making your theme vendor the next port of call 🙂
3.0 is in beta – so we don’t support it via the forums.
You are welcome to ask for a copy and take it for a spin – but you do so at your own risk. It’s essentially an advanced preview aimed primarily at developers/designers. We hope of course to receive valuable feedback from our testers and in turn they get to look at the code and plan ahead accordingly so they can deliver the best service to their customers, update plugins etc.
The officially supported version (2.x) doesn’t work with current php and wordpress versions. At least from what I have tried in the free version.
We can definitely try to help with the current version – what are the specific issues you are seeing?
It’s hard to say without seeing how your theme is structured, but if that line of code isn’t called (by ecp-page-template.php – which could happen if it is not for instance inside your theme’s header.php template or you don’t have that template) then that might explain this.
OK – so can you clarify which issues remain (and if any relate to plugins such as Facebook Events please post in the corresponding forum so that the team member with the most knowledge in that area can respond)?
Hi Tin, all recurring instances share the same post ID as the ‘root’ event so you would need to think of an alternative approach here, such as loading by date.
Alternatively, if you are happy working with the WordPress API you could extract the relevant post meta entry ID. That’s not the sort of thing we can help you with (nor can we guarantee that recurring event data will always be stored using the same system going forward) but it could give you a new avenue to explore 🙂
Hi Warren,
Right now we don’t offer support for 3.0 via the forums as it is still in beta – once it has officially been released of course we’ll be happy to try and help with queries like this one.
Any other feedback/questions regarding beta code should be directed to Rob at [email protected].
Since there’s not too much more we can offer here I’m going to close this thread now – for any other issues please do feel free to create new ones as needed 🙂
Excellent – I’m very glad to hear that.
Since it sounds like this is resolved I’m going to go ahead and close this thread – of course please do create new threads as and when needed for support going forward 🙂
It’s definitely not something that Community Events is set up to facilitate ‘out of the box’ – and so I’d see this as squarely being the domain of custom development.
I’d imagine familiarity with your e-commerce plugin (if it’s a plugin you are using) is going to be the crucial thing here, as that is what will track and record sales and order data, etc.
So with thanks to all those who have contributed to this thread I’m going to go ahead and mark it as closed.
At least for the next release of WooTickets this sort of customization (individual attendee names and other details) remain something that hasto be added by customization or by using a third-party plugin – such as the one J-P kindly made available.
Do know however that we have definitely taken on board the general sentiment that some more baked-in features in this regard are desirable to quite a number of you – and we also encourage you to use our UserVoice page to share your opinions going forward.
Thanks!
I’ll go ahead and close this – as usual feel free to create new threads if you need further help on this end.
