Forum Replies Created
-
Posts
-
Hi Josh, does this example help you out here?
OK, thanks for the offer guys. I’ll pass that on to the assigned developer – I’m not sure if he’ll need this but if he does we’ll try and grab hold of you here.
In the meantime, we may realistically still be waiting until the next release of Facebook Events before we see this fix.
Hi Craig – as I wrote in my previous post, I’m still unsure if you or your colleagues have run through our standard troubleshooting steps in their entirety, that is:
- Ensure your plugins are up to date
- Disable all non-Modern Tribe plugins
- Also switch back to a default, unmodified theme such as Twenty Eleven
- Now test to see if the problem remains or is resolved
Again, I note that you stated you had run through disabling other plugins but you did not mention your theme, so I’d like to confirm that you have indeed run through the above steps before taking this further.
Thanks!
* Made a typo there – the slug is irrelevant here, what I meant to say is the taxonomy is already in the code. It’s represented by TribeEvents::TAXONOMY.
Hi Andrew. You need only set $id to 287. The slug is already in there and it will (try to) determine the post ID automatically.
If you take a peak at the WordPress documentation for has_term() you’ll see how the pieces fit together.
Yes some new CSS or minor changes to your HTML should do the trick.
If you look at 306pheonixhouse.com, one notable difference is that content in the event page you linked to is contained within div#main-fullwidth which doesn’t have any padding or margin.
So one approach would be to target div#main-fullwidth in your theme’s stylesheet and add some padding.
By comparison, if we look at the homepage of that site, it’s content is wrapped in div#main which is padded, 15 pixels on all sides. So perhaps you could swap out div#main-fullwidth with plain old div#main in the relevant template?
Remember also that you can choose specific templates to use from Events > Settings.
Hopefully that makes sense – but please let me know if it doesn’t.
Sure – the Themer’s Guide can be found here (and there is also a link under Useful Resources over on the right).
There are some existing threads re Yoast’s plugin on the forum you might be interested in and if you browse around you may come across some work by Andy Fraggen who I believe wrote a plugin that changes the way in which a custom events.css file is loaded (ie, the original plugin copy is also enqueued – bringing about more traditional cascading behaviour as you then need only override specific rules).
Have fun and thanks for your support 🙂
Hi Gahlord:
Quite possibly the order could be changed, however an alternative approach that is currently supported is to copy the plugin’s events.css into your theme’s events folder (if you haven’t already created this, please see our Themer’s Guide and tutorial on template overrides).
This CSS file is then used in place of the one contained in the plugin directory: for that reason you cannot simply put in the one or two (or however many) changes you wish to make – it should normally start with all of the same rules that are contained in the default Events stylesheet.
Does that make sense and/or sound like a workable approach here?
Hi Craig, I’m not sure if you need further support here or not – if you do please post back, otherwise I’ll assume you’ve got everything working and will close this thread out.
I replied to your email – just for completeness, deactivating all other plugins and switching to a default theme does seem to have resolved this and you should now complete the following steps:
* Reactivate each plugin (and then your theme) one at a time, checking at each point to see if the problem has returned
* If/when the problem becomes apparent again the last item you reactivate will very likely be the cause of this problemWe can then consider other options, such as swapping out the conflicting theme/plugin for something different.
Hope that gets you on track 🙂
