- This topic has 4 replies, 2 voices, and was last updated 12 years, 2 months ago by
.
-
Posts
-
I have been trying to resolve the issue of the Previous/Next Month navigation not working (spins without ever loading). If I stick to Events Calendar and Don’t Use WooCommerce, the hack in the functions.php that support recommended fixes it:
<body <?php body_class(array($avada_color_scheme,$body_class)); ?>>It works fine if I turn off the PRO version- but I really need to and want to use the PRO version. I also want to use WooCommerce tickets for the events and just purchased it.
Problem 1:
• The hack fixed Previous/Next only in Events Calendar but not in Pro
• When WooCommerce is installed for the Woo Tickets, my site goes white- totally blank.
• If I take out the hacked line of code that was put in to fix the Previous/Next issue, the site is again viewable.
So, the hacked code isn’t really working for me – it didn’t work in PRO and it interferes with using Woo Commerce/Woo Commerce tickets.uggghh. Please help. I really like your app. and want to get it working.
Good morning. I’m hoping that this issue can get resolved today as it is really hanging up a site launch. Thank you for your attention to this matter-
I turned on the debugging reporting and found that WordPress needed more memory to run- I Upped the memory and it looks like everything is working fine now- even the NEXT / PREVIOUS buttons! and I can use Events Calendar Pro now also.
Howdy susy,
I am so very sorry it took us this long to respond. We are not able to respond on weekends. Even still nine times out of ten we are able to respond to weekend questions by Monday night. While we only guarantee a response within 48hrs, we are normally quicker. This was a bit of a fluke and again I apologize since you are in a hurry.
Now to fixing this. Do you mind if I ask who recommended that line of code to you? Looking through your past posts here I did not see any mention of it. The thing is, that code uses two variables that are not universal, $avada_color_scheme and $body_class. Unless those are strings the code should actually generate an error, and definitely would wreak havoc. Even if they are strings, without being able to see what they contain it is hard for me to diagnose.
It looks like you are developing your site locally, so you can not provide a link. That is fine, I do the same thing usually. But, it does make it harder for me to assist you if you can not provide a link to the problem in action. To help alleviate this, could you email us a copy of your theme so that I can run it locally and see if I can reproduce the problem? That can be accomplished by placing a copy of your custom theme folder inside of a .zip file, and emailing that zip as an attachment to [email protected]. Please reference this thread in the body or subject of that email so that it gets forwarded to me.
I want you to be able to use the Pro version as well. If the issue really does boil down to something as simple as the <body> class, I think we should easily be able to get this working. I just need to see it to fix it. Let me know if you can send us a copy of the theme, and if you can provide a link to the live site somewhere. But, sending the theme is probably going to be the most help. Will that work for you? Any other questions I can help with? Cheers!
– Brook
- The topic ‘Next/Previous Not Working: Conflicts’ is closed to new replies.