Conflict between 3.2 and WP E-Commerce

[liblogger]

Hi Kelly – I hadn’t seen the last reply (didn’t get an email update for some reason?).

I suspect I’ll need more specific instructions than ‘somewhere after’?

[Neill]

Hi Liblogger,

Sorry for the confusion. I believe you should be ok adding what was mentioned above after line 1124 in wp-e-commerce/wpsc-core/wpsc-functions.php

As we do not have access to replicate the issue here please let us know how it works, or if there are any other pointers we can offer. Good Luck!

Neill

[liblogger]

Thanks Neill – unfortunately, it doesn’t seem to have any effect?

(I don’t know if this is connected, but when I deactivated WP E-Commerce to see if re-activating it with the edit would make a difference, I noticed that the events list, although displaying in the correct order, was displaying recurring events from October…)

[Neill]

Hi Liblogger,

Sorry that didn’t work – let me check with the devs again and see if there’s something we’re missing. Thanks for your patience!

Neill

[Neill]

Hi Liblogger,

Sorry for the confusion yesterday. Lets try this again. First of all make sure you’ve removed everything from wp-e-commerce/wpsc-core/wpsc-functions.php that we added yesterday.

Add the following code to your functions.php file: http://pastebin.com/ePTaKt1G

Usually I would be happy to test this all out and make sure this all works on our end, but as this fringe case, and is only occurring on your site we’re working blind. If this doesn’t looks like it fixes the issue this time around then let us know and we’ll see what we can do next. But from talking to the devs we are pretty confident this is the issue and that this should work.

Thanks again for baring with us. 🙂

Neill

[liblogger]

Hi Neill – adding this to the theme’s functions.php (both TwentyTwelve and our own) doesn’t have any effect.

I tried setting up a fresh installation of WP with the three plugins and imported our events into it, and that version didn’t have this display problem, so I’m prepared to believe it is specific to our site 🙂

One thing that I noticed with the fresh installation is that the database for the basic WP installation uses InnoDB, whereas the databases for our existing site and the crashtest site is MyISAM (in both cases the WP E-Commerce tables are MyISAM). Would this be enough to cause the SQL error you mentioned?

If it’s an underlying problem with our installation, I’d rather address that than using a workaround (as it would seem liable to recur), but I don’t have any idea where to start with pinning down the problem.

[Neill]

Hi Liblogger,

Sorry for the late reply – I’m not 100% confident, that this will solve the issue once and for all. Its very unfortunate that your site seems to be picking up on this bug – and so far you are the only one to report it. I have posed this senario to one of our devs and I’d like him to double check. If

Bare with me and I should be back to you pretty soon.

Neill

[Neill]

Hi Liblogger,

Just one last point that might cut down on a few more back and forths, which will hopefully get this issue wrapped up sooner for you. Would you be able to paste your entire functions.php file (with the snippet that we provided inserted) into a tool like pastebin? We’ll be able to get a look at whats going on there too at the same time. If the devs believe that the fresh database install isn’t going to be enough of a fix then I’d like to come back to you with a plan B.

Neill

[liblogger]

Hi Neill – I’ve posted the amended twentytwelve functions.php file to pastebin here: http://pastebin.com/AWtru7MN (I’d tried adding the suggested code at the end of the functions file as well, but it didn’t appear to make a difference).

[Neill]

Hi Liblogger

Looks like this one got away from us a little. Sorry about that. Its such an edge case of a mix a small issue in our code and a small issue in your themes code that is causing the conflict.

A dev looked at everything a little closer and we realized the timing of the code we gave you before may not be doing the trick. As a result we came up with another snippet of code: http://pastebin.com/reXSbkhg – try adjusting the original code for functions.php that we provided with this one.

I understand that you may not have the issue any more since the re installation of your DB but let us know if the issue has cropped up again, and if this snippet we offer may help?

Apologies for the slow replies also, hope we’re getting a little closer for you.

Neill

[liblogger]

Thanks Neill – I haven’t had a chance to try this before we close for the holidays, but I’ll try it out asap in the New Year (I’ve not reinstalled our db – time, again – so hopefully this will help!)

[Neill]

Thanks Liblogger – I’ll leave this ticket open for now as I want to make sure you are taken care of in the new year.

Neill

[Neill]

Hi Liblogger,

Just touching base with you now that we are in the new year. If you have had a chance to look at this issue again please let us know what the outcome was. No rush though, just want to make sure we’re still concerned in resolving this for you.

Neill

 

[liblogger]

Hi Neill – That does seem to be working, both on the crashtest site and on our offline test site (which is running WP 3.8 and EC 3.3/ECP 3.3). I’m going through updates on our live site and will get back to you.

thanks,
Helen

[liblogger]

Hi there – this does seem to be working on our live site, which is great! Thanks for your persistence in working out this fix.

[Author]

Posts