Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
That has to be the case as I can't imagine why it works on localhost, but not live with exact same configuration other than something server related. What is the MYSQL version on localhost compared to live site? If you were going localhost to live then it could've been the cloning software, but since it's live to localhost it's even weirder.I'm beginning to think the problem must be environmental, so I'm going to compare the two environments in detail and see if I can track down exactly what triggered the problem.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
autobahn wrote: I don't believe this! I checked the queries on the live site using debug after applying the nightly build and all the integrations; the date ranges were correct, valid and possible. So, I ran it again just now with debug as you suggested and got this:
SELECT * FROM `abs_cbsubs_subscriptions` AS m WHERE (m.`expiry_date` <= '2016-02-04 21:30:36') AND (m.`expiry_date` >= '2016-02-19 21:30:36') AND m.`plan_id` = 3 AND m.`status` = 'A' ORDER BY m.`id` DESC
Unless I am reading this wrong (it's getting late here!) it's testing for EARLIER THAN/EQUAL 4th February 2016 AND EQUAL/LATER THAN 19th February 2016 which is impossible!
I checked all the other _cbsubs_subscriptions queries and they are all impossible.
Shall I try applying the latest nightly build and the integrations again tomorrow?
Please Log in or Create an account to join the conversation.