Re: [Radiant] [ANN] Styles 'n Scripts v0.7
Chris Parrish said the following on 11/24/2008 12:47 AM: Time for a new release. This is mostly bugfixes and a minor addition or two to work with other extension: Hint, please, as to the ways we might update depending on the way we installed. -- The Air Force is reacting to the EPA ban on CFC's by replacing them in the cooling systems of the ICBMs. If they are ever fired, it will be an environmentally friendly nuclear holocaust, not threatening the Ozone layer. -- _Access to Energy_, July 1993 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Styles 'n Scripts v0.7
Chris Parrish said the following on 11/24/2008 12:29 PM: Updating updating SnS is the same as every other extension, run: rake [your_env] radiant:extensions:sns:install OH WOW! All the git/svn stuff encoded in a rake file! Why has no-one ever done that before? Please can we have this done recursively from the root! Please! -- A lot of managers talk about 'thinking out of the box,' but they don't understand the communication process by which that happens. You do not think out of the box by commanding the box! You think out of the box precisely by bringing ideas together that don't allow dominant ideas to continue to dominate. - Stan Deetz ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Styles 'n Scripts v0.7
Um, no. (Though it would be very cool). In order to make use of the 'install' task, you have to have the latest version of SnS (or any extension) copied into the extension's directory (from github, svn, or wherever). Install in this sense, means: migrate the db, copy any needed files into your project's /public folder, do anything else the extension writer deems necessary to get things working and not: go get the latest version and then install that I think the Ray extension may do what you're looking for. -Chris Anton J Aylward wrote: Chris Parrish said the following on 11/24/2008 12:29 PM: Updating updating SnS is the same as every other extension, run: rake [your_env] radiant:extensions:sns:install OH WOW! All the git/svn stuff encoded in a rake file! Why has no-one ever done that before? Please can we have this done recursively from the root! Please! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] Styles 'n Scripts v0.7
Time for a new release. This is mostly bugfixes and a minor addition or two to work with other extension: * Renamed one of the TextAsset fields (internal change to let SnS work better with Andrew Neil's file_system extension). * The radiant:extensions:sns:config rake task was just plain broken. I think most folks out there don't know about this tool or I'd have heard more complaints by now. Please note that this is *the* way to change the SnS settings -- not directly in the db or with the settings extension as these bypass validations I have in place and, since I store these settings in memory, don't take effect until you restart your server. The rake task, however, works properly and immediately. * There was an issue with one of the migrations if you had existing stylesheets/javascripts from an early SnS version (fringe case). * Changed the name of a model so that SnS now just works with the import-export and super-export extensions (nice tools, BTW) * Added the radiant:extensions:sns:update_dependencies rake task to recreate the dependencies table if you had a problem importing existing data (see above). http://github.com/SwankInnovations/radiant-sns-extension/tree/master -Chris ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
