WAMP Usage Issues

[gmoore]

I would like to start this topic for any issues that are know to WAMP users. Development is doing in XAMPP but we recognize the user base for WAMP and would like to be able to support it. Any of your findings would be great to hear in this topic.

Thank you!
Greg

[gmoore]

Error on install:


( ! ) Warning: mysqli::close(): Couldn't fetch mysqli in C:\wamp\www\libs\db.php on line 58

Call Stack

# Time Memory Function Location

1 0.0015 368384 {main}( ) ..\index.php:0
2 0.0206 1143776 include( 'C:\wamp\www\install\installer.php' ) ..\index.php:39
3 0.0290 1352296 Database->Close( ) ..\installer.php:248
4 0.0290 1352344 close ( ) ..\db.php:58

[KyleMassacre]

I was doing some reading around and it seems that WAMP 64bit doesn't like cURL all that much out of the gate. After some research you may want to check your ini file for your PHP and check to see if the cURL lib is commented out along with th ini file in your Apache folder.

http://stackoverflow.com/a/13219082

But first, for troubleshooting sake, I would maybe remove the use of cURL in the check license function and just use the fsockopen or file_get_contents method which ever it is and see if that works. I don't know for sure how php or Apache checks to see if a module is installed, so it may be installed just not activated.

[gmoore]

Actually if I ignore that 'Close' error and continue with the installation it goes fine. Now running a local version of NWE 119 through WAMP. It authenticates with my license code and has updated modules and such.

I thought maybe it was some settings in the WAMP engine or PHP.ini. I didn't change anything. Nice little program.

So at some point I will check out the 'Close' error but it doesn't seem to stop testing.

Can anyone give anything else to look at from a WAMP perspective? I would need error messages and such so I don't chase ghosts. If you mentioned it before, please do so again.

Thank you!
Greg