Script Execution Issues

Hello fellow WAMPStack users. I’m experiencing a consistent problem that’s dogged me since I decided to setup my own local machine testing server. I’ve installed the WAMPStack to my C:\ drive on an Acer Aspire running 32/64-bit Windows 7 Ultimate (please don’t ask me how that happened or even how it manages to work with NO PROBLEM), since I was having permission issues due to the fact of the previous installation having existed in the C:\Program Files directory. Every thing is running flawlessly except for the fact that if I have more than 2 – 3 scripts running on any given page, one of those scripts will cease to function, but I’m given no error message, and if any of those pages are uploaded to my production server, they perform without a hitch. Since I’m having no other problem to speak of outside of that, I’m considering it to be a problem of something I didn’t do or set in the secondary installation of WAMPStack. On a personal note, I’m absolutely in love with it and the ease of functionality and utter simplicity. I just had a thought that there must be a web-based control panel for the server, but haven’t managed to make out where it could be. I’ve been plumbing whatever documentation there is with the application, but I’m coming up empty trying to answer it. It’s not killing me since I know that those scripts work. Thanks for any pointers or advice that ANYONE can give me. I don’t like to not be able to see parts of my pages not functioning.

Guess I should mention that all the scripts on a troubled page I’m dealing with are external JavaScript and I even tried to import in the troubled script into the body of the HTML document. Still, no luck with getting it to function. The funny thing is that the previous WAMP packages I used reproduced the described error. This is what makes me think it’s a simple issue as I never got to the root of what was causing this problem in the past. Like I said, EVERYTHING else about the Stack rawks.

I’m glad you like the BitNami Stacks. We included a control panel for the servers for OS X and will include for other platforms in the future.You can find more info about BitNami Stacks at http://wiki.bitnami.com

Could you check the Apache log file your_installdir/apache2/log/error ?

Thank you for stepping in, Mr. Rueda (appreciate that). Your suggestion was the FIRST thing I’d implemented before I posted, and there was nothing by way of error for the functionality of the current installation as I’d previously uninstalled and then re-installed to avoid the Windows 7 permissions snafu (problem with installation to C:\Program Files).
This problem that I’d posted has recurred over all the various WAMP packages I’d used before (EasyPHP/WAMPServer/etc.), and I can’t see what it could be. Error report;

And just to clarify WHAT the problem is (just in case I wasn’t crystal-clear before): On the page I intend to be the index.html search engine landing page, I have three external JS scripts. Of those three, only the slideshow won’t function when viewing the page via the “localhost” setup in the browser. But if I navigate to the directory and doubleclick the page for regular browser viewing, that “missing” script is happily functional along with the other two JS scripts living on the same page. BIZARRE as I said before since this problem has replicated itself over the range of WAMP packages I’ve used in the last six weeks (and what led me to BitNami’s WAMPStack package). Do you need anymore info, sir? Please let me know what this is even remotely symptomatic of, because I’m sure it’s me and the problem is because of something I haven’t done. Thanks for everything, Beltran.

OK, WEIRD…..After my initial post, I went back to tweakle with things a bit more and realized the problem of the “missing” code functionality on the page. The script didn’t like having the JS and CSS separated from each other, even though when the former code structuring is uploaded to a production server, it goes off without a hitch. Anyway, the mistake emanated from my end, so I guess my issue is resolved. But it still doesn’t answer why the “localhost” view refuses to present the same view as pointing the browser at a production value version of the same page. My head hurts now (lol!)…..