|
Tim Martin
|
May 24, 2013 at 3:32 pm
Between a rock and a hard place.
Installing and making Apache run side by side versus trying to get EE to work under IIs. Any success stories? I would rather run WordPress/EE under IIS but that may be based on IIS being the devil I know (somewaht) versus the devil I know not at all. Not happy about trying to make Apache work side by side with IIS because I will have the extensive multi application company web site in my hands with the covers off and deeply fear stepping on something. No good network/server admins people to help with unfamiliar things. But I am willing to consider it.
At this point I have a WP site running as an application in a IIS web site. So that is not so difficult. I have seen posts from folks who are successfully using EE with IIS. Haven’t reloaded the EE Personal PlugIn yet although it was working pretty well on a test/dev site. Not porting anything , just doing from it from scratch. Hoping our relatively modest requirements will allow everything to work without a lot of blood, sweat and tears.
Yes, I will be working off and on throughout the weekend because attempting to get EE working under IIS the way the client wants it will be difficult at best. As we know there will be only minimum sympathy from the EE support folks since they have taken pains in forums and documentation to emphasize they think it is a bad idea.
|
|
Tim Martin
|
May 24, 2013 at 7:17 pm
Minor update in case EE addicts find themselves deathly bored sometime this weekend.
Smoothly installed WordPress and the Personal level EE plug in. They worked. Had to use FireFox to set the PayPay IPN activation. I don’t like the URL structure but that is proabably my own fault and perhaps it can be mitigated somewhat, a minor ding. Thought putting WP at the root level might have allowed an earl like http://right.here.com but looked a little closer to the edge than is comfortable.
Set up and event with PayPal. PayPal takes the money, people are registered including multiple attendees. Hurray.
Problems that remain.
1. Email not sent even after manually taking the payment and selecting to send.
2. Reason manually taking the payment is that even though PayPal takes the money EE is still not recognizing the IPN. More on that in a sec.
As far as the mail goes, I think that will disapear with Easy SMTP or whatever it is that fixed the same problem over on my test and learn site.
Although slightly improved from that first cut the PayPal interface is still broken. PayPal does show the IPNs as Sent. It allows one Resend. So that is better than having them just stew away in Retry or worse Disabled status. Something is happening. But in order to complete the process it is necessary to manually update the attendee. And checking the gateway log in WP for PayPay there are entries but nothing like VERIFIED to mark a successful round.
Like the test site, when the trnasactions page URL includes “/transactions/” it fails. If the “/?page_id=999999/” is sent then the No ID message comes as it should.
Tried setting the Default Payment Status so it would at least go to pending, but still the registration gets the red circle. Rats.
Note this. I’m doing better on IIS7 on Windows 2008 R2 that under full throttle Apache/PHP/mySQL.
So……just saying EE is a great product and a super, super value but….but……the PayPal IPN seems to be a real fish bone in the throat for a lot of folks (ncluding EE support to be fair).
|
|
Tim Martin
|
May 25, 2013 at 2:40 pm
Get the email working as expected with the WP Easy SMTP plugin. Shouldn’t have needed it in theroy but no biggie.
The PayPal IPN problem I will pursue seperately.
I hope my experience will helpful for anyone else faced with the IIS being the client platform. Very savy tech people with good backups and the bandwidth might attempt Apache side by side with IIS but I felt it was a pretty crunchy way to go.
At this point, it feels pretty solid and that I will be able to safely apply the client’s modest appearance and work flow configurations with no problems.
Closing this and marking as “not support’.
|
|
Dean
|
May 27, 2013 at 2:07 am
Hi Tim,
Thank you for providing your experiences on this, IIS is tricky to work with and as your rightly mentioned we dont really recommend it.
However it seems you have managed to get it functioning quite well which is great!
|
