Forum Replies Created
-
Posts
-
Hi theresajennings,
You’re right that editing core plugin code is, generally, a bad idea. In this case you’d need to work with the Tribe Meta Walker – we’ve got documentation on doing just that over here (linked to from our tutorials page). In essence, you probably will be aiming to unregister those fields from one group and register them with another.
For your second question, please take a look at this related thread and proposed solution. We do have this on our bug tracker, though, so in a future release that workaround should cease to be necessary.
Last but not least, we are building a filters plugin which may meet your search requirements and as soon as it is ready an announcement will be made – so keeping an eye on our blog or ensuring you are subscribed to our newsletters is a great idea to stay up-to-date 🙂
Please note that we prefer to stick to one issue per thread – so if you need any further support on the last two questions I would ask that you break them out into new threads.
Thanks!
Hi fusionstudio: as this relates to Community Events I’m going to move your thread over to that forum so you can receive help from our expert there 🙂
Hi fusionstudio,
You’re correct that this is all by design and indeed was originally modelled on what we perceived to be the prevailing industry standards, notably with reference to Google Calendar (I’m not saying it duplicates all of that product’s behaviours exactly, just that that is the sort of reference point we used during the design phase).
All I can say is we’re open to suggestions – our UserVoice page is the place to post any ideas for improvements – but right now any change to this process is, I’m afraid, something you’d need to figure out and develop for yourself.
Hi ngaire,
First let me start by saying we appreciate your cooperation and patience so far. Unfortunately, we’re at a bit of a loss on this side – and this is not a widespread issue across the community. Added to which, the fact that you seem to experience it even with only our plugins running and nothing else does hint at some sort of environmental issue.
Sadly, at this time, we can’t really put more time into troubleshooting this one. That’s bound to be disappointing but reflects the reality of having limited resources along with the inherent difficulty of remotely troubleshooting something we don’t (and shouldn’t) have direct access to.
What I can say is, the next release incorporates a number of fixes that might just impact on this … as I’m sure you can appreciate that is not a guarantee at all, just a possibility, however at this stage I’m not sure there’s much more we can offer.
Thanks again for your support and understanding.
OK, so it sounds like you may simply be exceeding the available memory. In the first instance can you investigate increasing that (seeking the advice of your web host if necessary)?
Thanks!
Hi fknippenberg,
We have been looking at solutions that we might be able to offer the community in the meantime, but that isn’t always easy to achieve especially in as short a timespan as we expect this issue to linger for before it vanishes and indeed before our next release, which ought to address it, arrives.
It’s not that we don’t care by any means and I can assure you considerable efforts are made whenever something like this occurs – ultimately though we have to be practical here and all we can really do at this point is offer as accurate information as we can about the nature and scope of the problem and when we expect it to be fixed.
Can it be related to the translation into german? (just a poor guess).
An excellent guess. On setting the language in my test installation to de_DE I was able to replicate this. Please bear with us a little longer – now we can see the issue troubleshooting should be easier 🙂
Hi Rubie31.
For the problem that is similar to what others described, please see my earlier reply. In your case there is a separate problem occurring and for that what I’d recommend as the next step is checking your DB_CHARSET setting in wp-config.php and ensuring it is UTF8.
Even if it is, it may be that it is “fixed” at server level to some different charset and so it could also be worth checking in with your web host to confirm if this might be the case.
While I certainly don’t want to start a game of pingball with your web host, unless you have a dedicated server and your site is the only one on it then that doesn’t necessarily provide as with a lot to go on, since – assuming for the moment this is actually a regular shared hosting plan – those formidable resources will be split across all the different sites/accounts that share that particular server.
Beyond what Chris has suggested, then, I’d recommend setting up an appropriate level of caching and possibly also jumping to a hosting plan that can better accommodate this situation – right now I’m afraid there is little else for us to do or suggest (and keeping in mind that, as above, we are continually working to improve performance across the board).
Just a note that our fix has been tested and ought to roll out with the next maintenance release. Thanks for your patience – and I’ll go ahead and close this thread.
Cheers!
Pretty much – and do remember that there are some great guides and tutorials out there on the wider web to help learn the basics of CSS, which could be a good starting point if you are unfamiliar with this sort of thing.
No problem and hopefully this should clear up as described – again, please accept our apologies for the inconvenience in the meantime.
