Al Brookbanks

Exactly that. Please upgrade manually.

Hi @LWartist I'm really sorry but I don't remember. I work on thousands of stores a year and I don't remember this case. I can certainly upgrade it respecting any customisations under the Technical Support & Management service.

If you are having trouble installing CubeCart or you would like someone to upgrade your store to the latest version please checkout our "Technical Support & Management" plan. You can relax and our experienced staff can take care of it for you.

This isn't something I've heard about.

Thanks. Our success helps your success.

Please consider keeping it to help us grow.

I'm going to add an extra step to the joyride on first admin login.

We have support services available if you wanted us to upgrade your store and fix any skin compatibility issues. More info at https://www.cubecart.com/technical-support I hope that either we can work with you or you manage to get this resolved.

HI Roger, I'd suggest restoring a backup and then try upgrading again. There shouldn't be any issues upgrading to and from those versions.

I'll see if I can find an hour or two this afternoon to test the cache read/writes. Hopefully we can optimise it.

Guys thanks for looking into this. I'm really tied up at the moment but I'll get involved when I can.

Yes if you are a fairly experienced developer.

I had to get 6.2.2 out due to XSS vulnerability and included these code changes.

We are pleased to announce the release of CubeCart 6.2.2. This is a maintenance release which also patched a new XSS vulnerability found by Zekvan at Netsparker. We urge all merchants to upgrade to this version at their earliest convenience. What's New? 30 issues have been closed but notably those listed below. Admin CP 404 Error XSS Vulnerability PHP 7.2 support with OpenSSL support to replace Mcrypt. Caching optimisation Download: CubeCart-6.2.2.zip

I'm pretty confident we solved this one now. See: https://github.com/cubecart/v6/issues/2051#issuecomment-410987558 Thanks so much Alec.. top bloke. 😀👌

Ok thanks so much. Looking at the logic of the code it does look like it writes everything though so it does look to me like we have found the problem.

Don't worry I'm on this. Just waiting for an update.

Can you change: https://github.com/cubecart/v6/blob/6.2.0-branch/classes/db/mysqli.class.php#L224 To: if($cache) $this->_writeCache($this->_result, $this->_query); ... same in mysql class.

Great. Sounds like progress.

You could just bop and fwrite above this line of code: https://github.com/cubecart/v6/blob/6.2.0-branch/classes/db/mysqli.class.php#L224 $fp = fopen('query_log.txt', 'a+'); fwrite($fp, $this->_query."\r\n"); fclose($fp);

It could potentially be debugged by changing the way the cache file name is stored or a flat file could be written to with each cache write to store the SQL query. CubeCart caches by default so it might be worth checking 3rd party extensions too. The code in CubeCart has a lot of SQL queries.. multipied by 3,500 products could be massive. Let me know if you find anything. I got back from a stag do in Bournemouth last night so a little hazy still today.

None of these are strictly errors but actually best practice warnings and notices. Please turn off debug mode and they will no longer be logged

I just tested across different browsers and the cache only added a few extra files for new queries. I can't see any problems.

I'd be very surprised if that was the case as there is no session data tied to cache storage at all.

The cache is going to get big. Imagine 50 SQL queries cached on product detail page multiplied by 750 items. Well thats 37,500 files for just that bit of the catalog. I suppose the test is to clear the cache and refresh certain pages and see how much it grows.