Thanks Sean and John. John, I will try to work on that. Right now, I have to get this done for my client. :)
This is for the staging extension that I wrote. The extension was working great and we had planned to deploy it to production this weekend. Then, at the last minute, the client's IT department said we couldn't run the staging instance and the production instance on the same physical server (they said it was maxed out), so I'm scrambling to change the extension to allow us to run the staging instance and the production instance on separate servers. Probably a better design decision in the long-run, but my initial assignment was just to get the damn thing working without spending a lot of hours doing it. :) Anyway, thanks for the responses. Hopefully I can find some time to work on John's suggestion. Jamey On Fri, Jun 20, 2008 at 10:12 AM, John W. Long <[EMAIL PROTECTED]> wrote: > > On Jun 20, 2008, at 9:27 AM, Jamey Cribbs wrote: > >> I've googled a lot, but have not found anything. Is my >> only alternative to manually replace the older version of highline in the >> radiant gem's vendor directory with the newer version of highline? >> > > You could try that. The other alternative would be to freeze Radiant into > your vendor directory and make your changes there. > > If you really wanted to get your hands dirty, forking Radiant on github, > updating and testing the new lib, and then submitting a pull request would > be ideal. > > -- > John Long > http://wiseheartdesign.com > > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
