Forum Replies Created
-
Posts
-
Yep that’s going to be a nice feature for sure … and sorry we can’t do more on this occasion re the beta release.
I’m guessing you don’t need further help here and will now close this thread. Feel free to create new threads as and when needed, though 🙂
Hi artifaktcom I’m guessing you don’t need further support on this one but if you do feel free to open a new thread.
Hi Stu,
Sorry for the lack of response however you are correct – we typically do not provide weekend coverage. We also do not support beta code here on the forums (and because it is beta code we largely do not recommend it be used in a production environment).
However, I’d invite you to email my colleague Rob who collates reports and feedback from our beta testers. You can email him at [email protected].
It may well be that the current version of WooTickets does not play too nicely with the new version of The Events Calendar (though a revised version of the plugin is in development and will be released in synch with 3.0), in which case you would need to wait until the official release dates to progress this, unless Rob can provide a development snapshot of WooTickets – though I can’t guarantee he will be able to do so you could definitely ask 🙂
Thanks for contacting us,
Barry
Which version of WooCommerce are you using? Also, to clarify the above steps – if you happened to have any WooCommerce add-ons then they too would need to have been deactivated (the best test case here being a default, unmodified theme plus WooTickets, WooCommerce and The Events Calendar running).
Are you familiar with your browser’s developer tools and are you comfortable looking at and monitoring the Javascript console to see if anything of interest is being reported there?
Do you/have you previously installed any security plugins that ‘lock down’ WordPress?
Does this thread help? (I’ll move this thread to the Events Calendar PRO forum as it is not specific to Community Events).
Using a media query to change the layout would probably be the first thing I’d look at here. A more ‘advanced’ method would be to detect that the request is coming in from a handheld device and redirect to the upcoming list.
Neither is fullproof and they are not mutually exclusive, either, so you could do both and/or roll in some other techniques 🙂
I’m afraid there isn’t too much more we can suggest – the code Polylang’s author suggested you remove is needed by our plugin and ordinarily works without any issues.
If you do remove it then please bear in mind that you do so at your own risk – with the very real possibility of new problems appearing.
It’s definitely unfortunate that it happens to cause a problem with Polylang (though if I understand things correctly it may be the true problem is in the internals of WordPress) but unfortunately we can’t really offer much more in this direction.
I don’t see any obvious reason why there would be a problem. As I understand things, you have deactivated all other plugins and are using a default, unmodified theme (but correct me if I’m wrong) which is the basis of our troubleshooting process.
The only thing that stands out as atypical is that it looks as though your web server is IIS 6.x, which can be problematic when working with a number of popular PHP web apps (and to add perspective, the current stable version of IIS is 8.0 and that is itself 8 months old, version 6 is much older).
Using something like IIS 6 probably should be possible but I’m afraid there is a limit to how much support we can offer in that direction. Is a change to a more modern version such as IIS 8 or even to the Linux/Apache platform (which the overwhelming majority of WordPress installations sit on top of) a possibility?
While I can’t guarantee that such a move will instantly solve this it would at least put us in a position where we could offer a degree of further support – very few of our team have a working knowledge of the IIS series of web servers.
It’s difficult to say, it could also depend on the user agent (ie, the particular browser software running on the test device). Does the same problem occur if you resize your desktop browser to those dimensions?
In the best case a width of 320px only leaves around 45px per column and less than that is likely to be usable space when you factor in ‘losses’ due to padding, margins and borders needed for legibility.
It might be better in those circumstances to break away from a grid of 7 columns altogether – there’s not really a ‘correct’ solution here, it depends on a huge number of variables and what will work well for you may be unacceptable for someone else.
Excellent: we’re certainly keen to collate a collection of great examples of WooCommerce in practice and have a (currently empty 🙁 ) sticky thread for that: https://theeventscalendar.com/support/forums/topic/made-something-youre-proud-of/
Great to hear you’re on track 🙂
I can’t really offer anything beyond what they have suggested, I’m afraid.
There are a few theme frameworks out there, Gantry included, which – although they doubtless provide an excellent foundation for building themes – are structured in a way that differs notably from the norm. That is partly how each builds in its own set of unique selling points, however it can on occasion be problematic when the time comes to use other plugins, etc.
We do plan to look into compatibility with Gantry at a future date and if possible we will write a set of tutorials to support our Gantry-userbase … right now however I could only recommend following their advice and even engaging a designer/developer to assist.
Hi again Wojciech –
So one of our devs, Paul, looked at this. His recommendation was that you should not remove (or comment out) that function.
It’s possible that it’s purpose isn’t something you currently need (or, that you have needed so far) however it isn’t something we can remove from our code and to do so with your own copy would be likely to cause problems later on – particularly if you use the Save Draft functionality and are working with venues and organizers.
