Well I installed xampp for the hell of it and of course it works. But, xampp is a development environment. It is meant to be as open as possible. I do not want to serve up web pages to the internet with an open development system.
To that end I tried to install the apache win32 binary on the official apache website with php 5.2 VC6. Needless to say that failed. I could not even get modx installed. "500 internal server error" When I clicked on the javascript link to "test database and collation."
This whole system is fighting me tooth and nail.
So now what do I do? I uninstalled all my previous MySQL PHP and IIS before installing xampp. Guess my first question now is, is there a way to install another AMP without interfering with xampp? Like installing another MySQL, PHP, apache
-
☆ A M B ☆
- 1,780 Posts
Are you intending to serve the website yourself? If so, is that to save hosting costs?
Would you be interested in a host offering properly configured servers for MODX? I can find you one... (look below in my sig - good peeps, promise!). The reseller options (not public just yet, but you can inquire) are very reasonably priced, and you can serve all your client's sites without the hassles of managing the server yourself. My client's sites run there happily and the MODX support is superb!
The fact that the Apache server works, means the formIt hook issue has something to do with the IIS server itself. While MODX can run on IIS, there's talk of unknown magic and sorcery that can be difficult to solve, so most of us avoid it and stick to Linux environments.
-
☆ A M B ☆
- 2,475 Posts
You've jumped from FormIt issues to environment issues, so you might want to open a separate thread for that.
500 internal server errors is fairly broad -- could be an error in your .htaccess file or any number of other things. Re clearing your cache: that could be easily related to permissions on your server, e.g. PHP running as admin writing files that you as a regular user don't have permissions to delete. But yes, you can delete all the contents of the core/cache/ directory and MODX will regenerate them.
Anytime I run a local environment like WAMP or MAMP, I have to put on my sysadmin hat to troubleshoot my server. E.g. installing both XAMPP and the Apache binary is probably a recipe for disaster: the skills required to configure one instance of Apache and PHP are not trivial. Configuring your server to tolerate 2 or more versions PHP and/or Apache is a lot more complicated.
If you think environment issues are at play here, then it might be good to test your code on a shared server somewhere where you know MODX is working normally. I find far fewer problems on Linux servers, for what it's worth.
My purpose in doing this myself is because I can. There is a great sense of accomplishment in doing things yourself from the bottom up. At one time I ran an ArchLinux environment for nearly 3 years as my main desktop PC a few years ago. I never had so many issues with installing a working AMP environment. The fact that I have windows 8 on my desktop now is because of other apps that I must use on a daily basis that are not available in a *nix enviroment. I figured it would be rather simple to setup a IIS, MySQL, PHP environment and have it serve a web page.
The fact that it **WAS** working is what really grinds my gears. I have been pondering on this issue of what did I change to stop if from working for nearly 3 days now. The error is effectively junk, in the sense that it gives no credible information. I don't know enough about the code to actually figure anything out without a primer on php. I am lost and it seems like I am getting no where. I don't give up easy, but there is no sense in spinning my wheels.
@Everett Yeah I realize that, but I am not too interested in figuring that issue out till I get the chance to install the newest apache 2.4.4. I was following a youtube tutorial. No need to open up another thread and waste space and time on something I am not interested in getting working. Hopefully I can find a good tutorial on installing apache and go from there.
Moral of this story, buy a cheap tower and setup a non-graphical *nix environment with SSH access and just get it done!
-
☆ A M B ☆
- 1,780 Posts
I'd have to argue that, just because you "can" do something, doesn't mean that it's worth doing it. The amount of time wasted on server issues outweighs the benefits both in cost and time, but that's just my opinion after working in both XAMPP locally and with a host as a reseller of hosting for my clients. I do use both still, but I don't have to fiddle with my hosted servers. If I have an issue, I have the host deal with it.
If you want to get into the serving business and build it from scratch, you could always buy an unmanaged VPS server. That way you have complete control of everything except for the hardware itself.
Personally, I'd rather get to building MODX websites and leave the server issues to the MODX professionals at my host. Not all hosting companies are created equal, and while I had few issues previously, once I switched to a host configured for MODX with actual MODX support, life did get much easier.
Best of luck with this endeavor if you decide to continue. Yes, it can be done. But should it? If you do figure it out, please do let us know how you did it. Chances are someone else will want the information someday.
And your issue is when adding the hooks. That's the low down dirty of it. IIS doesn't recognize the FormIt hooks for some reason. Yet hooks are what makes FormIt work the way we want it to. Why doesn't it work? Bleh. Who has time to worry about that when there are websites to build?
