Written by techmatters on

Hello? Anybody? This is a little on the "urgent" side...

Written by tenzo

Newbie(2)

Profile of tenzo Add a Friend All User Topics Send Message

on

I have the same issue :(

Written by techmatters on

I am absolutely appalled at the "support" from Mighty Resources.

Last night, without permission or without any advice from you (before or after) a Mighty Resources staffer logged into our LIVE website and proceeded to upgrade to the latest version. This was at about 9pm Australian time. It was not until the client noticed something seriously wrong with their website the next morning that we discovered that all our template changes and cutomisations we had put in place to get this system working the the way we needed it had been destroyed!

Oh, and the IE checkout problem was still there.

At no point did any Mighty staffer advise us that this had been done. Thankfully we tracked it back to you because of the special login we gave you to use, and we could see that the time the files all changed was 20 minutes after you logged in.

We have spent all morning tracking this problem and had to do a full restore from backup, closing the website for around 2 hours in prime time for my client.

This is VERY VERY BAD FORM. And totally unprofessional. I cannot believe that you did this.

For all of you out there suffering with the inability to checkout under IE - we have noted that an earlier version of mighty commerce (that we have installed on another client's website) does not have this problem. We are currently working on downgrading the mighty commerce implementation to take it back to 1.0.0.beta4  - at least we think this is a better option than waiting for 4 days to get a non-reply on a "critical" status ticket on a so-called commercial product.

Written by Katerina

Expert(10140)

Profile of Katerina Add a Friend All User Topics Send Message

on

Hello! The problem of 'all our template changes and cutomisations' can be caused by the updating or reinstalling your components - all customization doesn`t remain. We cannot get this error on our test installations that is why we have to update component. We didn`t know about your customizations. Every time when user says about changes in the code we warn him that all of them will not remain after update. If problem persist you need to check what can influence on it process. Sorry for all inconveniences. Regards

Written by techmatters on

Dear Katerina,

Yes, we know that updating will wipe out our customisations. That's why we can't do it easily.

I know of no other component supplier in this space that would not check with the client first and get permission before upgrading their software. Also even AFTER doing it you did not post any notification to us.

Even after you did the update, the problem with IE remained.

This is how we see the problem compared to what we see in Firefox:

The querystring in the url that is posted when you "checkout" from the shopping cart loses the bill= and itemid= parameters and is replaced with ie=1 in the querystring.

So there seems to be some "test"?? on IE that is inserting this ie=1 and losing the rest of the info.

As most of your code is encrypted we have not been able to resolve this ourselves and downgrading our versions have been a problem for us so far (although we DO have this working OK on another installation with earlier versions).

If you can do something based on the querystring parameters I would be pleased to know so we can fix this ASAP. If you have a patch and would like us to test it please email this through and we will install it ourselves. Do not attempt any upgrade without our permission.

Written by JS.Support

Expert(13158)

Profile of JS.Support Add a Friend All User Topics Send Message

on

Hello, we are sorry for the delay with answer, it's really debug this problem as it does not appears in our project. We have checked one client's project with this problem and find out that sql server time and main server server time are different so bills created with start future start date. Please make following test: make purchase to get error, see bill id in the url then go to the back-end to check start date and time of new bill. If you get future date then you need ask hoster to change sql server time to make fit to the main server time. regards

Written by JS.Support on

P.S. I need make small correction, sql server has no its own time, it gets time from OS, so you need make sure that GMT time of server OS and GMT time of apache server is the same.