|
Hi Brian, I think this was discussed earlier. From
what I recall, the solution was to not use a mapping at all. Instead, you put the
reactor package in a subfolder called ”reactor” from within your
application folder. One problem discussed using a mapping was
that someone else might have defined a ”/reactor” mapping as well,
pointing somewhere else. From what you write, I gather that’s what your
shared host is trying to avoid, by appending your siteID to the mapping. Anyway, it should work by putting the
reactor code in a reactor subfolder, although it might not be the perfect
solution… If you use it in several applications, you would have to keep
several copies of the code, which is not good at all.. Maybe there is others out there with a
better solution? Regards, Tormod Boga Inbusiness AS Fra: Brian Rinaldi
[mailto:[EMAIL PROTECTED] I was wondering if anyone has experience getting Reactor
working at a shared host. I am hosting with HostMySite and when I add a mapping
they automatically append my site ID to it. So my mapping for Reactor looks
like /reactorH74732. Obviously this is causing a problem. Any recommendations
on how to resolve this? My only thought so far was to create a seperate copy of
Reactor and do a search and replace...but for obvious reasons this seems like a
less than desirable solution. |
- Reactor For CF Reactor on shared hosting Brian Rinaldi
- SV: Reactor For CF Reactor on shared hosting Tormod Boga
- Re: Reactor For CF Reactor on shared hosting Sean Corfield
- re: SV: Reactor For CF Reactor on shared hosting Brian Rinaldi
- [Reactor for CF] Re: SV: Reactor For CF Reactor... Jared Rypka-Hauer
- Re: Reactor For CF Reactor on shared hosting Brian Rinaldi

