Forum Replies Created
-
Posts
-
No, it’s probably just that that isn’t the problem 🙂 Did you restore your events page? I’m still seeing the Hello This is a test! message when I visit this page.
The other thing I notice (on that same page) is that it seems to be generated by Magento, rather than WordPress, so you’d need to resolve that – basically allow WordPress to serve up those pages – in the first instance.
Thanks!
I’m trying to get some input from some other team members on this one – I appreciate your patience and will get back to you as soon as I can.
I’m a bit puzzled, it certainly sounds like your theme is the culprit though. Can you send a copy over (as a .zip file so I can take a quick look? Send to [email protected] and mark the email for my attention. Please also include a link back to this thread) … I can’t guarantee anything but I’ll certainly do a quick check and see if I can replicate this using your theme and if there are any straightforward fixes.
Hi Phillip.
I visited the URL you provided when you created this thread however it results in a 404. Can you confirm which URL I would need to look at to see this problem?
Ah hah!
OK, that’s the missing link here. The short answer is, you cannot do that. What we’d recommend is using the widget in an actual widgetized sidebar (and creating a new one if you need to position the widget outside of any existing sidebars – though in your case it would seem a widgetized sidebar would fit in there quite nicely).
We are aware that direct calls via the_widget() to the mini calendar will cause problems and I believe the dev team are working on a solution, for the time being though you’ll have to do things differently.
We’re genuinely sorry to hear that you feel that way and that neither The Events Calendar/Events Calendar PRO or our support for those plugins has met you’re expectations.
Nonetheless we certainly wish you all the best and hopefully the next solution you pick works out for you.
Just for clarity – within a php.ini file I believe that memory_limit ought to be expressed as 64M rather than just 64 (just pointing this out in case the setting is not being followed due to the missing M).
Can you double check that and then let me know if you made the correction and if it made any difference?
To clarify, as well as seeing this error on the frontend you are seeing this in the admin environment when trying to publish events to Eventbrite?
Did you find about about your memory_limit setting/were you able to increase this?
Thanks for posting back Luke, we’ll leave this open to give people an opportunity to ask about your solution 🙂
Hi Nenad – you mean for the months, days of the weeks etc? I believe these are actually obtained from WordPress’s global WP_Locale object and so you would need to ensure the relevant translations exist in the core WP language files.
Hi Esteban.
Though this article stems from an issue experienced using Django rather than WordPress it sounds like it might be the same basic issue.
Can you take a look at your database, perhaps using a graphical tool like phpMyAdmin, and check out which storage engines are in use?
Sure – well, one further troubleshooting exercise that could be helpful while I wait for a chance to discuss this with other team members would be to set up a duplicate site, with only WordPress and The Events Calendar/Events Calendar PRO initially running within the same hosting environment (in a sub-directory for instance) or else in a duplicate environment.
If that’s possible, we’ll have a safe place to troubleshoot and the first step would be to see if this same problem happens on a fresh install straight away.
Assuming for the moment there are no problems, start introducing all the other components such as your theme, any other plugins and see if this problem starts occurring at some point.
On the other hand, if the problem starts up straight away that would be a clue that the problem is environmental in nature and would in itself be useful information here.
I do appreciate you want to resolve this as soon as possible – and so do we – but we do have a limited amount of support bandwidth and need to support a large number of users, so we are genuinely thankful for your patience and will do our best to work through this with you as expeditiously as possible.
