Jump to content

[SOLVED] Stuck at Step 3 - Not continuing, No Errors, Model.php not firing, Windows 2008 PHP5.3


Recommended Posts

I'm running Windows 2008 R2 IIS 7 w/ PHP 5.3 and Latest MySQL. This is a stable, standalone server, and has been running several PHP e-commerce apps with no issues.

 

Step 2 comes out clean - no errors.

Database check shows no problems

Email is configured advanced, and it passed with no problems.

 

Upon hitting Next, Ajax spins and quits, no error messages, no progression, nothing.

 

All variations have been tried - no magic quotes, ISAM vs InnoDB, etc. No errors at all, not on debugger and not in logs. All directories have been made written that are required based on the installation step by step on a previous post.

 

createDB within controller.js is firing, however success: function() does not fire. No DB connections made besides my test connection. Model.php is not being called at all - and it isn't even being populated.

 

Any ideas?

Link to comment
Share on other sites

  • 2 weeks later...

I'm running Windows 2008 R2 IIS 7 w/ PHP 5.3 and Latest MySQL. This is a stable, standalone server, and has been running several PHP e-commerce apps with no issues.

 

Step 2 comes out clean - no errors.

Database check shows no problems

Email is configured advanced, and it passed with no problems.

 

Upon hitting Next, Ajax spins and quits, no error messages, no progression, nothing.

 

All variations have been tried - no magic quotes, ISAM vs InnoDB, etc. No errors at all, not on debugger and not in logs. All directories have been made written that are required based on the installation step by step on a previous post.

 

createDB within controller.js is firing, however success: function() does not fire. No DB connections made besides my test connection. Model.php is not being called at all - and it isn't even being populated.

 

Any ideas?

 

Hi,

 

Thanks for your detailed feedback, very helpful :)

 

Can you send me an FTP access by PM, I can't reproduce the issue in my environment but I would like to offer you to fix it on your server (and copy/paste the fix on SVN before the upcoming release).

 

Regards,

Link to comment
Share on other sites

  • 7 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...