The new 0.6.8 release seems to have fixed this problem for me.
Something good has happened during the weekend, since I was running
off trunk from Friday :)
/Casper
On 25/07/2008, at 17:24, aslak hellesoy wrote:
On Fri, Jul 25, 2008 at 1:16 PM, Casper Fabricius
<[EMAIL PROTECTED]> wrote:
> Please choose an alternative and run this generator again.
I'd suggest doing just that...
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: htt
There's a minor error in the radiant:update:configs task that I
discovered this morning when fixing the demo site -- this should only
affect upgrades from older versions. I have pushed the fix to github.
If you want to stay on the gem, the workaround is to do two things:
1) Make sure you hav
Hi Chris. I hate to say it, but no change. Downloaded the latest
version from the link in your message to vendor/extensions/sns. Ran
the rake tasks again just to be safe. Page still displays without any
styling.
Here's what I see when accessing the css/elastic page directly:
[EMAIL PROTECTED]> cu
A brand new installation seems to require specifying the name of the
directory for your installation. So, for example:
-bash-3.00$ radiant
Usage: /home/danorine/ruby/bin/radiant /path/to/radiant/app [options]
Options:
-r, --ruby=path Path to the Ruby binary of your choice
(o
Oh, I forgot to mention, you'll need to clear the text asset cache too
so that the new status header gets updated. You can do this one of two
ways:
1. Save a javascript or stylesheet file (this will clear the cache
for all javascripts and stylesheets).
2. Delete the text asset cache
That did it! Working like a charm now.
Thank you very much Chris for a great extension and for all the help
getting it to work with LiteSpeed.
On Mon, Jul 28, 2008 at 12:33 PM, Chris Parrish
<[EMAIL PROTECTED]> wrote:
> Oh, I forgot to mention, you'll need to clear the text asset cache too so
> t
