This discussion got closed, but wasn't resolved...??

https://isenselabs.com/forum/discussion/after-install-finalise-button-not-working

My last post was:-

Thanks Stoyan, but I don't appear to be getting much closer to resolving this issue.

We're running PHP 5.4.2.29, which is pretty new. Is there anything glaringly obvious in our PHP Info file? http://dev.allflags.com.au/phpinfo.php

I have directory RW & Modify permissions set as per Open Cart's requirements:- - IUSR - Network Service - IIS_IUSRS

And as for the .htaccess file(s) ... we're not using them - and I've even deleted them to see if that made any difference.

I've even tried re-installing CodeManager from scratch, but again no difference.

Really hope you can help me here, as CodeManager looks great.

Hello Simon, 

Apologies for that. The last user in the previous thread posted a solution I thought that it should work for you as well.

Have you tried setting 777 permissions to the root folder of your store?

Hope this helps.

As explained above...

I have directory RW & Modify permissions set as per Open Cart's requirements:- - IUSR - Network Service - IIS_IUSRS

This is a Windows server, how do you perform a chmod? I thought setting the above was the same as a chmod.

If you do not know, CodeManager is based on the Codiad IDE and according to the Codiad developers:

Currently the system is only tested on Apache 2+ and Nginx in a Unix filesystem. Use on a Windows server will most likely cause pathing issues.

Unfortunately, the module is not compatible with Windows servers at the moment.

Thanks for the feedback, albeit it could have saved me a lot of time if CodeManager actually states that it's only supported on Apache. Neither the OpenCart website or the iSenseLabs website state that...

http://www.opencart.com/index.php?route=extension/extension/info&extension_id=17423&filter_search=codemanager

https://isenselabs.com/products/view/codemanager-web-based-ide-framework-for-opencart

Never mind, thanks for your help.

Actually we have not tested it on Windows Server and this is why we were not aware of this issue.

We will try to fix this in one of the future releases of the module.

Hope this helps!

On windows I was able to fix the issue by changing the backslashes in my both admin and frontend config.php files  to forward slashes. and remove "c:" from the beginning of the paths so it begins as /wamp instead of c:/wamp ..Ajax doesnt seem to like the backslashes in the the paths and is removing them and causing the finish button to throw a bunch of errors.