Re: [Radiant] Simultaneous 0.8.2 and 0.9rc2

[john muhl]

freeze your 0.9rc2 app (requires git to be in your path).

cd /path/to/project
rake radiant:freeze:edge TAG=0.9.0.rc2

On Sun, May 16, 2010 at 1:39 PM, Jeff Casimir  wrote:
> All,
>
> I'm ready to deploy my first 0.9rc2 site, but my server has other
> existing 0.8.x sites that I don't want to mess with.  What should I
> put in the config files to explicitly set the radiant gem version
> number?
>
> Thanks,
> Jeff
>
> ---
> Jeff Casimir
> Jumpstart Lab by Casimir Creative, LLC
> http://jumpstartlab.com
> @jumpstartlab on twitter
>

Re: [Radiant] Re: Roles that allow different users to edit different parts of the page tree

[john muhl]

if you still need it i put together a quick demo here:


if you have rails/radiant setup to work with sqlite then you should be
able to just clone the repo, cd into it and then run ./script/server
to get going.

On Fri, May 14, 2010 at 5:16 AM, Johannes Fahrenkrug
 wrote:
> Hi John,
>
> that's great. Did you happen to share the source code for this
> somewhere? Github, maybe?
>
> That would be great :)
>
> Cheers,
>
> Johannes
>
> On May 13, 7:03 pm, john  wrote:
>> On May 13, 10:16 am, Johannes Fahrenkrug 
>> wrote:
>>
>> > My customer has a different departments. So they want different roles
>> > for editors that work in the "products" department and for editors
>> > that work in the "services" department. Those roles should enable the
>> > administrator to allow certain users only to edit pages that are
>> > children of the "Our Products" pages and others to only edit pages
>> > that are children of the "Our Services" page.
>>
>> > Is there an extension that does this already? I know about the RBAC
>> > extension, but I'm not sure if it fits the bill.
>>
>> i've setup a similar scheme using the rbac_* extensions and it worked
>> out pretty nicely.
>

Re: [Radiant] javascript

[john muhl]

var foo = ""; quote the value

var foo = /url/; syntax error

On Mon, May 17, 2010 at 6:27 PM, Osledy Bazó  wrote:
> Hello i need to get the url of a page to usit on a js script..
>
> i'm doing this:
> http://pastie.org/964651
> nothing seems to work can anyone helpme to do this?
>

Re: [Radiant] "Squashing" a directory

[john muhl]

On Tue, May 18, 2010 at 12:17 PM, D.Kreft  wrote:
> Under Radiant 0.6.9[1], it was possible to do this:
>
> [-] Home Page (slug: /)
>     [-] International (slug: international)
>         [+] DE (slug: /de)
>
> ...to get the the following URLs:
>
> http://foo.com/
> http://foo.com/de/
> [1] I don't think this is something that the previous site owner hacked into
> being, but I could be wrong.

maybe i'm wrong but i suspect some extension was making it possible to
bypass the page hierarchy. as far as i know the page hierarchy has
always directly corresponded to the url structure.

Re: [Radiant] Building a gem for 0.9.0.rc3 FAIL

[john muhl]

git submodule init
git submodule update

On Wed, May 19, 2010 at 2:41 PM, D.Kreft  wrote:
> I'm trying to build a gem for radiant-0.9.0.rc3, but it's not going too
> well. Is there some secret mojo I'm missing?
> % pwd
> /workplace/octane/src/RubyGem-radiant/radiant-0.9.0.rc3
> % gem build radiant.gemspec
> ERROR:  While executing gem ... (Gem::InvalidSpecificationException)
>     ["vendor/extensions/archive/app",
> "vendor/extensions/archive/app/models",
> "vendor/extensions/archive/app/models/archive_day_index_page.rb",
> "vendor/extensions/archive/app/models/archive_finder.rb",
> "vendor/extensions/archive/app/models/archive_month_index_page.rb",
> "vendor/extensions/archive/app/models/archive_page.rb",
> "vendor/extensions/archive/app/models/archive_year_index_page.rb",
> "vendor/extensions/archive/archive_extension.rb",
> "vendor/extensions/archive/lib",
> "vendor/extensions/archive/lib/archive_index_tags_and_methods.rb",
> "vendor/extensions/archive/lib/tasks",
> "vendor/extensions/archive/lib/tasks/archive_extension_tasks.rake",
> "vendor/extensions/archive/Rakefile", "vendor/extensions/archive/README",
> "vendor/extensions/archive/spec", "vendor/extensions/archive/spec/datasets",
> "vendor/extensions/archive/spec/datasets/archive_dataset.rb",
> "vendor/extensions/archive/spec/models",
> "vendor/extensions/archive/spec/models/archive_day_index_page_spec.rb",
> "vendor/extensions/archive/spec/models/archive_month_index_page_spec.rb",
> "vendor/extensions/archive/spec/models/archive_page_spec.rb",
> "vendor/extensions/archive/spec/models/archive_year_index_page_spec.rb",
> "vendor/extensions/archive/spec/spec.opts",
> "vendor/extensions/archive/spec/spec_helper.rb",
> "vendor/extensions/archive/test", "vendor/extensions/archive/test/fixtures",
> "vendor/extensions/archive/test/fixtures/pages.yml",
> "vendor/extensions/archive/test/functional",
> "vendor/extensions/archive/test/functional/archive_extension_test.rb",
> "vendor/extensions/archive/test/helpers",
> "vendor/extensions/archive/test/helpers/archive_index_test_helper.rb",
> "vendor/extensions/archive/test/test_helper.rb",
> "vendor/extensions/archive/test/unit",
> "vendor/extensions/archive/test/unit/archive_day_index_page_test.rb",
> "vendor/extensions/archive/test/unit/archive_month_index_page_test.rb",
> "vendor/extensions/archive/test/unit/archive_page_test.rb",
> "vendor/extensions/archive/test/unit/archive_year_index_page_test.rb",
> "vendor/extensions/dutch_language_pack/config",
> "vendor/extensions/dutch_language_pack/config/locales",
> "vendor/extensions/dutch_language_pack/config/locales/nl.yml",
> "vendor/extensions/dutch_language_pack/config/locales/nl_available_tags.yml",
> "vendor/extensions/dutch_language_pack/dutch_language_pack_extension.rb",
> "vendor/extensions/dutch_language_pack/lib",
> "vendor/extensions/dutch_language_pack/lib/tasks",
> "vendor/extensions/dutch_language_pack/lib/tasks/i18n_nl_extension_tasks.rake",
> "vendor/extensions/dutch_language_pack/Rakefile",
> "vendor/extensions/dutch_language_pack/README",
> "vendor/extensions/french_language_pack/config",
> "vendor/extensions/french_language_pack/config/locales",
> "vendor/extensions/french_language_pack/config/locales/fr.yml",
> "vendor/extensions/french_language_pack/config/locales/fr_available_tags.yml",
> "vendor/extensions/french_language_pack/french_language_pack_extension.rb",
> "vendor/extensions/french_language_pack/lib",
> "vendor/extensions/french_language_pack/lib/tasks",
> "vendor/extensions/french_language_pack/lib/tasks/i18n_fr_extension_tasks.rake",
> "vendor/extensions/french_language_pack/Rakefile",
> "vendor/extensions/french_language_pack/README",
> "vendor/extensions/german_language_pack/config",
> "vendor/extensions/german_language_pack/config/locales",
> "vendor/extensions/german_language_pack/config/locales/de.yml",
> "vendor/extensions/german_language_pack/config/locales/de_available_tags.yml",
> "vendor/extensions/german_language_pack/german_language_pack_extension.rb",
> "vendor/extensions/german_language_pack/lib",
> "vendor/extensions/german_language_pack/lib/tasks",
> "vendor/extensions/german_language_pack/lib/tasks/i18n_de_extension_tasks.rake",
> "vendor/extensions/german_language_pack/Rakefile",
> "vendor/extensions/german_language_pack/README",
> "vendor/extensions/italian_language_pack/config",
> "vendor/extensions/italian_language_pack/config/locales",
> "vendor/extensions/italian_language_pack/config/locales/it.yml",
> "vendor/extensions/italian_language_pack/config/locales/it_available_tags.yml",
> "vendor/extensions/italian_language_pack/italian_language_pack_extension.rb",
> "vendor/extensions/italian_language_pack/lib",
> "vendor/extensions/italian_language_pack/lib/tasks",
> "vendor/extensions/italian_language_pack/lib/tasks/i18n_it_extension_tasks.rake",
> "vendor/extensions/italian_language_pack/Rakefile",
> "vendor/extensions/italian_language_pack/README",
> "vendor/extensions/japanese_language_pack/config",
> "ven

Re: [Radiant] Building a gem for 0.9.0.rc3 FAIL

[john muhl]

you might have better luck with rake radiant:gem

On Wed, May 19, 2010 at 3:56 PM, D.Kreft  wrote:
> Thanks. Though now I have a different problem:
>
> % gem build radiant.gemspec
> ERROR:  While executing gem ... (ArgumentError)
>
>  /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/version.rb:56:in
> `initialize': Malformed version number string 0.9.0.rc3
>
> Do I just need to get into the gemspec and hack the version number?
> -dan
> On Wed, May 19, 2010 at 1:39 PM, john muhl  wrote:
>>
>> git submodule init
>> git submodule update
>>
>> On Wed, May 19, 2010 at 2:41 PM, D.Kreft  wrote:
>> > I'm trying to build a gem for radiant-0.9.0.rc3, but it's not going too
>> > well. Is there some secret mojo I'm missing?
>> > % pwd
>> > /workplace/octane/src/RubyGem-radiant/radiant-0.9.0.rc3
>> > % gem build radiant.gemspec
>> > ERROR:  While executing gem ... (Gem::InvalidSpecificationException)
>> >     ["vendor/extensions/archive/app",
>> > "vendor/extensions/archive/app/models",
>> > "vendor/extensions/archive/app/models/archive_day_index_page.rb",
>> > "vendor/extensions/archive/app/models/archive_finder.rb",
>> > "vendor/extensions/archive/app/models/archive_month_index_page.rb",
>> > "vendor/extensions/archive/app/models/archive_page.rb",
>> > "vendor/extensions/archive/app/models/archive_year_index_page.rb",
>> > "vendor/extensions/archive/archive_extension.rb",
>> > "vendor/extensions/archive/lib",
>> > "vendor/extensions/archive/lib/archive_index_tags_and_methods.rb",
>> > "vendor/extensions/archive/lib/tasks",
>> > "vendor/extensions/archive/lib/tasks/archive_extension_tasks.rake",
>> > "vendor/extensions/archive/Rakefile",
>> > "vendor/extensions/archive/README",
>> > "vendor/extensions/archive/spec",
>> > "vendor/extensions/archive/spec/datasets",
>> > "vendor/extensions/archive/spec/datasets/archive_dataset.rb",
>> > "vendor/extensions/archive/spec/models",
>> > "vendor/extensions/archive/spec/models/archive_day_index_page_spec.rb",
>> >
>> > "vendor/extensions/archive/spec/models/archive_month_index_page_spec.rb",
>> > "vendor/extensions/archive/spec/models/archive_page_spec.rb",
>> > "vendor/extensions/archive/spec/models/archive_year_index_page_spec.rb",
>> > "vendor/extensions/archive/spec/spec.opts",
>> > "vendor/extensions/archive/spec/spec_helper.rb",
>> > "vendor/extensions/archive/test",
>> > "vendor/extensions/archive/test/fixtures",
>> > "vendor/extensions/archive/test/fixtures/pages.yml",
>> > "vendor/extensions/archive/test/functional",
>> > "vendor/extensions/archive/test/functional/archive_extension_test.rb",
>> > "vendor/extensions/archive/test/helpers",
>> > "vendor/extensions/archive/test/helpers/archive_index_test_helper.rb",
>> > "vendor/extensions/archive/test/test_helper.rb",
>> > "vendor/extensions/archive/test/unit",
>> > "vendor/extensions/archive/test/unit/archive_day_index_page_test.rb",
>> > "vendor/extensions/archive/test/unit/archive_month_index_page_test.rb",
>> > "vendor/extensions/archive/test/unit/archive_page_test.rb",
>> > "vendor/extensions/archive/test/unit/archive_year_index_page_test.rb",
>> > "vendor/extensions/dutch_language_pack/config",
>> > "vendor/extensions/dutch_language_pack/config/locales",
>> > "vendor/extensions/dutch_language_pack/config/locales/nl.yml",
>> >
>> > "vendor/extensions/dutch_language_pack/config/locales/nl_available_tags.yml",
>> >
>> > "vendor/extensions/dutch_language_pack/dutch_language_pack_extension.rb",
>> > "vendor/extensions/dutch_language_pack/lib",
>> > "vendor/extensions/dutch_language_pack/lib/tasks",
>> >
>> > "vendor/extensions/dutch_language_pack/lib/tasks/i18n_nl_extension_tasks.rake",
>> > "vendor/extensions/dutch_language_pack/Rakefile",
>> > "vendor/extensions/dutch_language_pack/README",
>> > "vendor/extensions/french_language_pack/config",
>> > "vendor/extensions/french_language_pac

Re: [Radiant] Building a gem for 0.9.0.rc3 FAIL

[john muhl]

worked here with rake 0.8.7. may as well just change the version in the gemspec.

http://github.com/radiant/radiant/commit/7d0a0d2

On Wed, May 19, 2010 at 4:15 PM, D.Kreft  wrote:
> Negative, Ghost Rider, the pattern is full:
>
> dkr...@logos:~/radiant> rake radiant:gem
> (in /Users/dkreft/radiant)
> rake aborted!
> Malformed version number string 0.9.0.rc3
> /Users/dkreft/radiant/Rakefile:7
> (See full trace by running task with --trace)
>
>          dkr...@logos:~/radiant> rake --version
>          rake, version 0.7.3
> -dan
> On Wed, May 19, 2010 at 2:05 PM, john muhl  wrote:
>>
>> you might have better luck with rake radiant:gem
>>
>> On Wed, May 19, 2010 at 3:56 PM, D.Kreft  wrote:
>> > Thanks. Though now I have a different problem:
>> >
>> > % gem build radiant.gemspec
>> > ERROR:  While executing gem ... (ArgumentError)
>> >
>> >
>> >  /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/version.rb:56:in
>> > `initialize': Malformed version number string 0.9.0.rc3
>> >
>> > Do I just need to get into the gemspec and hack the version number?
>> > -dan
>> > On Wed, May 19, 2010 at 1:39 PM, john muhl  wrote:
>> >>
>> >> git submodule init
>> >> git submodule update
>> >>
>> >> On Wed, May 19, 2010 at 2:41 PM, D.Kreft  wrote:
>> >> > I'm trying to build a gem for radiant-0.9.0.rc3, but it's not going
>> >> > too
>> >> > well. Is there some secret mojo I'm missing?
>> >> > % pwd
>> >> > /workplace/octane/src/RubyGem-radiant/radiant-0.9.0.rc3
>> >> > % gem build radiant.gemspec
>> >> > ERROR:  While executing gem ... (Gem::InvalidSpecificationException)
>> >> >     ["vendor/extensions/archive/app",
>> >> > "vendor/extensions/archive/app/models",
>> >> > "vendor/extensions/archive/app/models/archive_day_index_page.rb",
>> >> > "vendor/extensions/archive/app/models/archive_finder.rb",
>> >> > "vendor/extensions/archive/app/models/archive_month_index_page.rb",
>> >> > "vendor/extensions/archive/app/models/archive_page.rb",
>> >> > "vendor/extensions/archive/app/models/archive_year_index_page.rb",
>> >> > "vendor/extensions/archive/archive_extension.rb",
>> >> > "vendor/extensions/archive/lib",
>> >> > "vendor/extensions/archive/lib/archive_index_tags_and_methods.rb",
>> >> > "vendor/extensions/archive/lib/tasks",
>> >> > "vendor/extensions/archive/lib/tasks/archive_extension_tasks.rake",
>> >> > "vendor/extensions/archive/Rakefile",
>> >> > "vendor/extensions/archive/README",
>> >> > "vendor/extensions/archive/spec",
>> >> > "vendor/extensions/archive/spec/datasets",
>> >> > "vendor/extensions/archive/spec/datasets/archive_dataset.rb",
>> >> > "vendor/extensions/archive/spec/models",
>> >> >
>> >> > "vendor/extensions/archive/spec/models/archive_day_index_page_spec.rb",
>> >> >
>> >> >
>> >> > "vendor/extensions/archive/spec/models/archive_month_index_page_spec.rb",
>> >> > "vendor/extensions/archive/spec/models/archive_page_spec.rb",
>> >> >
>> >> > "vendor/extensions/archive/spec/models/archive_year_index_page_spec.rb",
>> >> > "vendor/extensions/archive/spec/spec.opts",
>> >> > "vendor/extensions/archive/spec/spec_helper.rb",
>> >> > "vendor/extensions/archive/test",
>> >> > "vendor/extensions/archive/test/fixtures",
>> >> > "vendor/extensions/archive/test/fixtures/pages.yml",
>> >> > "vendor/extensions/archive/test/functional",
>> >> >
>> >> > "vendor/extensions/archive/test/functional/archive_extension_test.rb",
>> >> > "vendor/extensions/archive/test/helpers",
>> >> >
>> >> > "vendor/extensions/archive/test/helpers/archive_index_test_helper.rb",
>> >> > "vendor/extensions/archive/test/test_helper.rb",
>> >> > "vendor/extensions/archive/test/unit",
>> >> > "vendor/extensions/archive/test

Re: [Radiant] Hot to resolve rack version conflict?

[john muhl]

On 02 Jun 2010, at 3:06 PM, trans wrote:

> Can anyone fill me in on the fix?
> 
>  tr...@logisys:radiant$ rake production db:bootstrap
>  (in /home/trans/Company/PsyTech/jobs/sunventures/radiant)
>  rake aborted!
>  can't activate rack (~> 1.0.0, runtime) for [], already activated
> rack-1.1.0 for ["radiant-0.8.2"]

it's a well known issue (with rails i think) and usually the simplest fix is to 
uninstall rack 1.1.0 and install 1.0.1. i believe there was a commit recently 
that fixes this on master so at least 0.9 when its released won't suffer from 
this.

Re: [Radiant] Import/Export?

[john muhl]

the directory the extension resides in is misnamed. it should be
located at vendor/extensions/import_export

On Sun, Jun 6, 2010 at 6:38 PM, Alan Kucheck  wrote:
> I'm running Radiant 0.8.1 and wanting to upgrade to 0.9.0 rc2. I
> loaded up radiant-import-export and on execution get the following
> error:
>
> Condor:blog akucheck$ rake db:export
> (in /Users/akucheck/src/ruby/radiant/Sites/blog)
> Could not load extension from file: radiant-import-export-
> extension_extension.
> # extensionExtension>
> rake aborted!
> undefined method `feature_pattern=' for # 0x101f8d728>
> /usr/local/lib/ruby/gems/1.8/gems/radiant-0.8.1/Rakefile:10
>
> Does anyone have any insight on this?
>
> thanks,
>
> ak
>

[Radiant] separating the markdown and smartypants filters

[john muhl]

in  i have
extracted the smartypants filter from the markdown extension. the test
suite is passing and everything works how it did before; e.g. using
markdown still gets smartypants treatment, using smartypants skips
markdown processing etc etc.

is there any reason to keep them in the same extension?

Re: [Radiant] separating the markdown and smartypants filters

[john muhl]

On Thu, Jun 17, 2010 at 12:03 PM, Jim Gay  wrote:
> On Thu, Jun 17, 2010 at 12:12 PM, john muhl  wrote:
>> in <http://github.com/johnmuhl/radiant/commit/26668a0> i have
>> extracted the smartypants filter from the markdown extension. the test
>> suite is passing and everything works how it did before; e.g. using
>> markdown still gets smartypants treatment, using smartypants skips
>> markdown processing etc etc.
>>
>> is there any reason to keep them in the same extension?
>>
>
> In order for Markdown to perform according to expectation, does it
> require SmartyPants?
>
> In other words, could the following happen?
>
> Markdown + SmartyPants = good
> SmartyPants only = good
> Markdown only = errors on curly quotes
>
> Or does Markdown not care about curly quotes?

here is how the filters currently work:

when you choose the markdown filter:
- rdiscount does both MD processing and SP punctuation...or
- kramdown does both MD processing and SP punctuation

when you choose the smartypants filter:
- rubypants adds SP punctuation

so in no way does using the markdown filter involve rubypants* or the
smartypants filter; and using the smartypants filter does not involve
using rdiscount/kramdown or the markdown filter. the two are already
independent in this way. the change is just to put them in separate
extensions so you could disable markdown and continue to use
smartypants or visa-versa.

* in the past the markdown filter (when using bluecloth or kramdown;
rdiscount always had its own SP) used to invoke rubypants but the
recent upgrade to the bundled kramdown removed that behavior

Re: [Radiant] separating the markdown and smartypants filters

[john muhl]

On Thu, Jun 17, 2010 at 1:00 PM, Jim Gay  wrote:
> On Thu, Jun 17, 2010 at 1:42 PM, john muhl  wrote:
>> On Thu, Jun 17, 2010 at 12:03 PM, Jim Gay  wrote:
>>> On Thu, Jun 17, 2010 at 12:12 PM, john muhl  wrote:
>>>> in <http://github.com/johnmuhl/radiant/commit/26668a0> i have
>>>> extracted the smartypants filter from the markdown extension. the test
>>>> suite is passing and everything works how it did before; e.g. using
>>>> markdown still gets smartypants treatment, using smartypants skips
>>>> markdown processing etc etc.
>>>>
>>>> is there any reason to keep them in the same extension?
>>>>
>>>
>>> In order for Markdown to perform according to expectation, does it
>>> require SmartyPants?
>>>
>>> In other words, could the following happen?
>>>
>>> Markdown + SmartyPants = good
>>> SmartyPants only = good
>>> Markdown only = errors on curly quotes
>>>
>>> Or does Markdown not care about curly quotes?
>>
>> here is how the filters currently work:
>>
>> when you choose the markdown filter:
>> - rdiscount does both MD processing and SP punctuation...or
>> - kramdown does both MD processing and SP punctuation
>>
>> when you choose the smartypants filter:
>> - rubypants adds SP punctuation
>>
>> so in no way does using the markdown filter involve rubypants* or the
>> smartypants filter; and using the smartypants filter does not involve
>> using rdiscount/kramdown or the markdown filter. the two are already
>> independent in this way. the change is just to put them in separate
>> extensions so you could disable markdown and continue to use
>> smartypants or visa-versa.
>>
>> * in the past the markdown filter (when using bluecloth or kramdown;
>> rdiscount always had its own SP) used to invoke rubypants but the
>> recent upgrade to the bundled kramdown removed that behavior
>>
>
> That makes sense to me.
> I created a repo for it here
> http://github.com/radiant/radiant-smartypants_filter-extension

hope you don't mind but i renamed it
radiant-smarty_pants_filter-extension for historical reasons :)

<http://github.com/radiant/radiant-smarty_pants_filter-extension>

> We can change the default markdown filter and add this one into the
> main project.

<http://github.com/johnmuhl/radiant/commit/b3844da>
<http://github.com/johnmuhl/radiant/commit/d838f3d>

Re: [Radiant] Super Import/Export

[john muhl]

On Fri, Jun 18, 2010 at 9:33 PM, Marshal Linfoot  wrote:
> Jeff, thanks for your reply.
> I tried what you suggested, but the results were the same. It always hangs
> at the same place, so a bit more investigation and I found that the file it
> fails on looks like this:

if you can't get that working check out the taps gem. it can serialize
data into and out of any database supported by sequel.

Re: [Radiant] heroku and long wait after changes

[john muhl]

On Sat, Jun 19, 2010 at 2:00 PM, Steven Southard
 wrote:
> So what is up with the 5 minute wait to see results after making a change on
> Heroku?  I'm currently using Radiant Edge on the Bamboo Ruby enterprise
> edition 1.8.7 stack but I've also set up 8.1 using their standard setup.
>  This long wait to see the results of changes kind of ruins Radiant's great
> user experience.  Changes can be seen right away on the back-end which is
> helpful so is there a way it could be fixed so they could be seen right away
> on the front-end.

see . in other words it's just
the way it is. heroku restart or git push heroku master are the only
ways i know of to purge heroku's varnish cache.

Re: [Radiant] heroku and long wait after changes

[john muhl]

On Sat, Jun 19, 2010 at 2:25 PM, Steven Southard
 wrote:
>
> On Jun 19, 2010, at 2:22 PM, Jim Gay wrote:
>
>> On Sat, Jun 19, 2010 at 3:00 PM, Steven Southard
>>  wrote:
>>>
>>> So what is up with the 5 minute wait to see results after making a change
>>> on
>>> Heroku?  I'm currently using Radiant Edge on the Bamboo Ruby enterprise
>>> edition 1.8.7 stack but I've also set up 8.1 using their standard setup.
>>>  This long wait to see the results of changes kind of ruins Radiant's
>>> great
>>> user experience.  Changes can be seen right away on the back-end which is
>>> helpful so is there a way it could be fixed so they could be seen right
>>> away
>>> on the front-end.
>>> Steven
>>>
>>
>> No. Heroku has an HTTP cache which is outside Radiant's cache and is
>> hit before it.
>> Currently, the only way to clear that cache is to redeploy your app.
>
> Why can you see changes made on the backend?

(if i recall) the backend sets a "Cache-control: no-cache" header for
everything.

Re: [Radiant] Re: OSCON 2010

[john muhl]

On Tue, Jun 22, 2010 at 12:20 PM, Andrew vonderLuft  wrote:
> Any takers?  Would love to network with some Radiant folks in a few
> weeks...

there are a number of events that may lead to my being in the
northwest during that time (i wouldn't be at oscon though) but right
now it's too early to say for sure.

Re: [Radiant] Radiant 0.9 performance

[john muhl]

On Wed, Jun 23, 2010 at 1:56 PM, Marshal Linfoot  wrote:
> The http sever is litespeed.

what is behind there? fastcgi, mongrel, thin, unicorn etc.

> Database is mysql.

are you using the default mysql configuration? if i recall (it's been
a while since i used mysql) the default config isn't really optimized
for speed.


may be a useful read.

> Under these circumstances, I'm seeing these kinds of numbers in the
> production.log when accessing pages on the site:
>   Completed in 1445ms (DB: 127) ...
>   Completed in 1838ms (DB: 317) ...
>   Completed in 4037ms (DB: 998) ...
>   Completed in 4865ms (DB: 488) ...

yikes. are you accidentally running in development mode?

> These are "good" numbers; sometimes the total completed is in the
> 2-4ms range! I don't understand where the bottleneck is. The db
> times are consistently less than 1000ms and usually under 500ms.

1000ms to 500ms db responses sound way slow to me. i just looked at
one of the production servers (running ubuntu 9.10) i have access to
and db responses were all under 100ms using sqlite.

> What's worse though is over time, no idea why, the ruby processes will start
> to runaway and I'll end up with 8-10 of them each vying for 20-30% of
> memory. Machine load avg spikes up to 14 and the system is essentially
> unusable and needs a reboot.

sounds like fcgi. i just had a look at a different production server
that runs 10 thins and it has been up for 135 days with stable memory
usage over that time; no steady increase.

> I'm considering bumping the slice memory up to 512MB, but am concerned that
> all it will do is delay the inevitable runaway ruby processes.

i think you have other issues to track down but as a solution in the
meantime that may be the way to go.

Re: [Radiant] Radiant 0.9 performance

[john muhl]

On Wed, Jun 23, 2010 at 6:22 PM, Marshal Linfoot  wrote:
> Thanks William and John.
> The http server is Litespeed. No mongrel, thin, etc. One of the reasons I've
> been using it is because it is dead simple to setup/configure and run. It
> was recommended in some Slicehost tutorials as the easiest way to get up and
> running with Rails apps, no need for backend servers or load balancers. It

(just out of curiosity) which article? i did a quick search of their
articles site but didn't see anything that "had" to be the one you're
talking about.

> supports Rack and Rails 2.3.2. BUT, maybe it's time to look at something
> else. What do you suggest, nginx and thin, mongrel, ...? I'm game to try
> something new.

lately i've been using nginx+passenger. if you go with apache use the
mpm worker variant (if at all possible) since it will use less memory
than the prefork version.

since you're on slicehost i'd also look at their 32bit os options (if
it's not too much of a hassle to switch at this point) which will
greatly reduce the amount of ram dedicated to all the stuff that isn't
your rails/radiant app. i recently setup a 32bit debian 5 there and if
i recall the base system used about 30mb of ram instead of the roughly
100mb for the 64bit version; the difference is probably enough to
support one extra (passenger or whatever) process which is nice. so
far i haven't noticed any difference in performance.

Re: [Radiant] Problems after upgrade from 0.8.1 to 0.9.0

[john muhl]

2010/6/25 Artem Zhirkow 
>
> Hi,
> I just upgraded my website with rake to 0.9.0 version and got application 
> error on the main page of website. Below you can see message from logs:

looks like 
so you may want to try running from the master for now.

Re: [Radiant] Radiant 0.9 performance

[john muhl]

On Thu, Jun 24, 2010 at 12:19 PM, Marshal Linfoot  wrote:
> John, I decided to give nginx+passenger a try. Installed the passenger gem
> and then "passenger-install-nginx-module" to compile nginx with the
> passenger module. Little bit of configuring and started it up.

i'm pretty much out of ideas about what the problem may be. i've never
seen numbers like that ever; not even running in development with
webrick.

perhaps there is a problem with the slice itself. you could always try
taking a snapshot of your setup and boot a new slice using that
snapshot and compare performance on the new slice.

> and 10 minutes later the load avg is back up to 7 and the site is
> unresponsive. Taking nginx down and restarting litespeed.
> What the heck is going on??? Desperate for a fix!!!

this sounds like you're using the passenger default which is to run up
to six application servers. here is an except from an nginx
configuration file that i use on a 32bit 256mb slicehost server that
is dedicated to running a single site .
that server has been running for over a month now with no runaway
resource usage.

> The mysql database was loaded using taps to copy from my desktop
> development environment to the slicehost server. Could the database be
> corrupted? How can I check?

try running in production using your sqlite database.

Re: [Radiant] Radiant 0.9 performance

[john muhl]

one other thing that comes to mind is maybe you're missing the mysql
driver (i don't have any evidence or references but i seem to recall
reading that not having it will result in degraded mysql performance).
does `gem list mysql` show something like "mysql (2.8.1)"?

On Sat, Jun 26, 2010 at 11:36 AM, john muhl  wrote:
> On Thu, Jun 24, 2010 at 12:19 PM, Marshal Linfoot  wrote:
>> John, I decided to give nginx+passenger a try. Installed the passenger gem
>> and then "passenger-install-nginx-module" to compile nginx with the
>> passenger module. Little bit of configuring and started it up.
>
> i'm pretty much out of ideas about what the problem may be. i've never
> seen numbers like that ever; not even running in development with
> webrick.
>
> perhaps there is a problem with the slice itself. you could always try
> taking a snapshot of your setup and boot a new slice using that
> snapshot and compare performance on the new slice.
>
>> and 10 minutes later the load avg is back up to 7 and the site is
>> unresponsive. Taking nginx down and restarting litespeed.
>> What the heck is going on??? Desperate for a fix!!!
>
> this sounds like you're using the passenger default which is to run up
> to six application servers. here is an except from an nginx
> configuration file that i use on a 32bit 256mb slicehost server that
> is dedicated to running a single site <http://gist.github.com/454173>.
> that server has been running for over a month now with no runaway
> resource usage.
>
>> The mysql database was loaded using taps to copy from my desktop
>> development environment to the slicehost server. Could the database be
>> corrupted? How can I check?
>
> try running in production using your sqlite database.
>

[Radiant] page_attachments interface enhancements

[john muhl]

Jim (saturnflyer) and i have been working (most of the important work
is Jim's) on a branch of page_attachments that adds some new interface
features to the page_attachments extension and i'd like to have some
feedback on the work so far (note the "grid" view still needs some
work but you can get the basic idea). you can check out the code at
 and in
case you don't have the time/inclination to install it and test it
locally i've setup a demo at  (use
admin/radiant to login; feel free to upload some files and mess
around).

are there any objections or concerns with having these changes merged
into the official p_a repo?

any feedback is appreciated.

Re: [Radiant] page_attachments interface enhancements

[john muhl]

On Tue, Jun 29, 2010 at 9:03 AM, Jeff Casimir  wrote:
> - It took me awhile to find the plus sign.  Maybe between the header
> row and the attachments themselves there could be a "+ Add" that, when
> clicked, could expand the form in place kinda like you do now.
> Otherwise, I think it could slam to the left against the "Attachments
> (count)"
> - I think the (-) image is too prominent, being the first thing you
> see when scanning the line.  Removing attachments is probably the
> least common action, so I think it should be somewhere with lower
> importance. Maybe the order could be: Thumbnail, Filename, Magnifier
> icon for view, minus icon for delete, then description below

good points. i guess these have been that way since the very first
version of page_attachments and are probably due for some attention as
well.

> - Given that the whole image row is draggable, it'd be nice if I could
> drag it into the body text and drop it to have the radius tags put in
> that cursor spot

that's an interesting idea. i wonder how difficult acts_as_list makes
it for you to get control back during/after the drag event.

> - When adding a new file...
> - - The (-) for cancel is kinda floating in space.
> - - I don't think the average user would expect to hit "Save and
> Continue Editing" just to upload the file.
> - - It might be most reasonable to have a fourth line with an "Upload"
> button and a "cancel" text link

indeed. i think the interface has been that way since forever; and
looking at it now i see that the appearance is inconsistent across the
3 browsers radiant supports. so yeah it should probably be given some
attention as well.

> - - I wonder if the file selection/upload wouldn't best be handled in
> a modal dialog

you mean put the inputs into one of those popup box things like a
lightbox? i don't really like stuff popping up and in that case you'd
have two things popping up; first the inputs and then the os file
selection dialog. do you know of a site that works like what you're
suggesting? perhaps if i could see it i'd appreciate it.

> Overall I really like the functionality, so apologies if this feedback
> sounds overly critical!

is there really such a thing as "overly critical"? ;)

Re: [Radiant] restricted users

[john muhl]

On Tue, Jun 29, 2010 at 6:22 PM, Franky De Schampheleer
 wrote:
> is there any extension for restricting users?
>
> for example a user that only access the pages ?

the "normal" user (i.e. neither an admin or designer/developer) role
ought to do that by default. for more sophisticated role setup i like
the rbac set of extensions; they're simple to build on top of or
extended as well.

Re: [Radiant] What is Radiant 1.0 and which Asset extension to use, was: page_attachments interface enhancements

[john muhl]

On Tue, Jun 29, 2010 at 7:51 PM, Jim Gay  wrote:
> On Tue, Jun 29, 2010 at 2:24 PM, Haselwanter Edmund
>  wrote:
>>
>> On 29.06.2010, at 19:47, Jim Gay wrote:
>>
>>> I'm glad you brought this up for discussion.
>>
>> It just felt right after following the github discussion :-)
>>
>>>
>>> On Tue, Jun 29, 2010 at 11:59 AM, Edmund Haselwanter
>>>  wrote:
>>>> A question for clarification:
>>
>> [ .. snippet .. ]
>>
>>>> wouldn't it be wise to concentrate on just one (nifty) asset
>>>> extension?
>>>> I see an asset extension as a vital part of a CMS (=> see, it says
>>>> content ;-)
>>>
>>> Yes.
>>> Check out the prototype http://github.com/radiant/radiant-prototype
>>>
>>> And there are tickets like
>>> http://github.com/radiant/radiant/issues#issue/28 (sns) and
>>
>> 
>>
>> jlong February 18, 2010 | link
>> There's a little more work to do on this in the prototype, mainly the upload
>> interface. I believe Chris Parish has had ambitions for simplifying his 
>> styles 'n
>> scripts extension to serve this purpose. If it is going to make it into 0.9 
>> it
>> should be implemented as an extension that ships with the core.
>>
>> 
>>
>> That's exactly how I see it too :-)
>
> SNS needs some more thought (which I happen to be doing
> http://www.saturnflyer.com/blog/jim/2010/06/29/ruby-metaprogramming-is-awesome/
> ) but I see that as a necessity for managing a site (along with
> image/file management of course).

having your css and js in the admin interface is a necessity? i tried
to love sns but never could find any benefit to not having the files
on disk. perhaps the extension has matured since i last looked (an
admittedly long time ago). if anybody has a compelling reason why it's
better to have that stuff in radiant than on disk i'd be happy to give
it another try.

the only reason for having your css/js in radiant i could ever dream
up was being able to stick radius tags in your css or js but that
didn't work with sns...until today. in the past when i ran into a
place where i needed that functionality i would just stick that little
bit of css/js inline in a layout or snippet; i think i needed to do
that once or twice in three years and more sites than i can remember.

>>> The greatness behind paperclipped is paperclip (not to take away from
>>> all the work that Keith and many others put in to make a really useful
>>> extension). I like page_attachments too and recently did a lot of work
>>> to change it on my fork with John Muhl's help, but for a recent
>>> project I was again looking for an asset manager and even though I did
>>> all that work to update page_attachments (and it still needs more) I
>>> chose paperclipped because of paperclip.
>>
>> Yes. You are right. And there are some extensions which add to paperclipped.
>> This is some kind of vote of the community, isn't it ;-)
>
> Yes, but partly because paperclipped had so much more done. Keith did
> a great job creating it and it's feature set blows page_attachments
> out of the water, but as I've heard John Muhl point out, some users
> find the interface (like the assets bucket) confusing and the
> simplicity of a list on a page (a la page_attachments) is very easy to
> understand.

it's true. i've tried paperclipped on three occasions and all three
times it ended up being pulled due to the "commoners" not really
getting the interface. with p_a they get it almost immediately; it's
like attachments in email and everybody seems to understand that.

i have an extension tied up in a client site that uses carrierwave
<http://github.com/jnicklas/carrierwave> and provides a similar
experience to page_attachments that i could try to get permission to
extract and open source if there is any interest in yet another file
manager (i can't imagine there would be but who knows) and honestly it
doesn't do anything more interesting than p_a but at least it's not
dependent on attachment_fu :)

>>>> and with this comes another question:
>>>>
>>>> Ok, I know that Radiant is "different". And I love it. I recently did
>>>> a presentation in my web 2.0 community meeting about radiant. And one
>>>> statement burned so hard: No end user will use this!
>>>
>>> Bullshit. It's just not true. I've had plenty of non-technical,
>>> non-tech-savvy users enjoying Radiant.
>>
>> Hm. Its not bullshit. It's how some people see it. I had to fight 2

Re: [Radiant] What is Radiant 1.0 and which Asset extension to use, was: page_attachments interface enhancements

[john muhl]

On Tue, Jun 29, 2010 at 7:50 PM, Jeff Casimir  wrote:
> I'd like to see radiant follow some of the footsteps from merb and
> have two gems: radiant-core and radiant-more.  The 'radiant' gem would

that sounds like a fine idea; and has been discussed in the past but
it wasn't particularly feasible until recently

> And if someone really wants a stripped down version they can just
> install radiant-core, barebones but fully functional.

radiant-core would be for the hardcore :)

seriously though i think you'd have radiant-blog, radiant-portfolio,
radiant-catalog etc. springing up then which would be a killer feature
in my opinion.

Re: [Radiant] Disabling Radiant cache completely in production environment

[john muhl]

On Wed, Jul 7, 2010 at 4:55 AM, weyus  wrote:
> I don't want this thing to cache ever.  I've looked at several pages,
> and Googled, and either I see a bunch of reference to ResponseCache
> which no longer work since I'm on Radiant 0.9.1 or other references
> which assume that I want to turn off the cache interactively.
>
> I want to be able to set something in my production.rb file to tell
> Radiant to never cache a page.

http://docs.heroku.com/http-caching

Re: [Radiant] New radiant installation fails: ArgumentError in SiteController#show_page

[john muhl]

On Sat, Jul 10, 2010 at 12:23 PM, Aleksey Kunitskiy  wrote:
> I don't understand what I'm doing wrong. I have ruby 1.9.1 and latest
> radiant installed via gems. Note that the admin (/admin) panel works
> fine

radiant is not currently compatible with ruby 1.9.x; only 1.8.6 and 1.8.7

Re: [Radiant] Understanding snippets

[john muhl]

On Sat, Jul 10, 2010 at 12:10 PM, Wes Gamble  wrote:
> All,
>
> In the Radiant ethic, it states: " Radiant is primarily designed for static
> Web sites (that is, sites that are not dynamically generated). It is not,
> and should not become, portal software."
>
> I was under the assumption that snippets were roughly equivalent to Rails
> partials, and assumed that snippets could take local data as input just like
> partials, but this doesn't appear to be the case, based on the snippet
> documentation at http://wiki.github.com/radiant/radiant/snippets and the
> quote above.
>
> I'd just like to verify: Can one pass variable data "into" a snippet and
> have it evaluated at runtime in any way?

you can `yield` inside of snippets which allows for some sort of
"variable data". for example:

snippet "x": 

usage:

 
 

Re: [Radiant] Problems with installing Radiant extensions

[john muhl]

On Sun, Jul 11, 2010 at 6:51 PM, Nikus  wrote:
> [z...@web108 radiant]$ ./script/extension install tags

could you give some more details of your environment so that i can try
to replicate it and reproduce the error. as is i don't get any error
from that command and tags gets installed properly.

> [z...@web108 radiant]$ rake ray:extension:install name=reorder

i guess i screwed something up with the http installation method. i'll
have a look later tonight or tomorrow and get that fixed.

Re: [Radiant] Re: Problems with installing Radiant extensions

[john muhl]

On Tue, Jul 13, 2010 at 2:49 AM, Nikus  wrote:
> What deatils do you need to know?

operating system, radiant version, ruby version, rubygems version,
anything else that could help replicate your system.

also i just pushed a change to ray that (should have) fixed the error
you were having before. could you update to the latest version and let
me know if you still get an error. in your situation the easiest way
to update might be to simply remove the `vendor/extensions/ray`
directory and download or clone the latest version.

Re: [Radiant] Correct way to eliminate page caching in Radiant?

[john muhl]

On Wed, Aug 4, 2010 at 11:35 AM, Wes Gamble  wrote:
> I've Googled and seen several approached to turning off page caching in
> Radiant - what is the most correct way to do this for a production
> environment?

have you tried modifying the response headers?

gem install rack-contrib

# environment.rb
require 'rack/contrib'
...
config.middleware.use ::Radiant::Cache
config.middleware.use Rack::ResponseHeaders do |headers|
  headers['Cache-Control'] = 'no-cache'
end
...

Re: [Radiant] Generating thumbnails using paperclipped extension with S3 storage on Heroku

[john muhl]

On Thu, Aug 5, 2010 at 8:46 PM, Wes Gamble  wrote:
> Don't I need ImageMagick or something similar for the thumbnail generation
> or other image manipulation?  How does one set that up on Heroku?  Or is
> that even an issue?

ImageMagick is installed on heroku just add mini_magick or rmagick or
whatever thumbnailer you like to your .gems file and deploy as usual.

Re: [Radiant] Search on http://ext.radiantcms.org/

[john muhl]

http://www.google.com/search?q=0.9+site:ext.radiantcms.org

On Wed, Aug 11, 2010 at 7:44 AM, Christian Aust
 wrote:
> Hi all,
>
> is there a way to serach for all extensions marked as 0.9-compatible on 
> http://ext.radiantcms.org/? Regards,
>
> Christian
>

Re: [Radiant] forms extensions installed, but no Forms tab appears

[john muhl]

On Wed, Aug 11, 2010 at 4:09 PM, Lindsay Morris  wrote:
> So I tried another installer:
>   git clone git://github.com/squaretalent/radiant-forms-extension
> vendor/extensions/forms
> That seemed happy, and I now have a vendor/extensions/forms directory.  Yay!
> Then:
> rake radiant:extensions:forms:migrate
>
> blew up like this:
> /home/lindsay/rails_apps/radiant/config/environment.rb:13
>
>   config.gem 'radiant-forms-extension'

it looks like you're mixing the two types of extension installation;
vendor/extensions/xyz and installed as a gem. you only need to do one
or the other and since it looks like gems were not working remove the
`config.gem 'radiant-forms-extension' line. then re-run the
installation task(s).

Re: [Radiant] rack 1.0.1 and rack 1.1.0 problem with radiant-0.9.0.rc2 and rails 2.3.8

[john muhl]

On Wed, Aug 11, 2010 at 2:06 PM, Paulo Abreu  wrote:
> I'm trying to install radiant cms version 0.9.0 rc2 in ubuntu with
> passenger and rails 2.3.8 and I'm having the following error:

if this is a new installation i'd recommend using 0.9.1 as it will be
more stable than an outdated rc version.

Re: [Radiant] Addition to wiki (need a little help)

[john muhl]

On Sat, Aug 14, 2010 at 2:46 PM, Wes Gamble  wrote:
> All,
>
> I've added a page to the wiki about how to merge two or more extensions
> here: http://wiki.github.com/radiant/radiant/merging-existing-migrations
>
> But I mis-titled it "Merging existing migrations" when it should be "Merging
> existing extensions"  I can't figure out how to modify the title/page name.
>
> Can someone change the name of this page to "Merging existing extensions"
> and link to it under the "Creating Your Own Extensions" section?

i don't think the title can be changed after the page is created. it
looks like the new wiki system has this ability though. maybe we
should upgrade the radiant wiki to the new system?

Re: [Radiant] Addition to wiki (need a little help)

[john muhl]

On Sat, Aug 14, 2010 at 2:46 PM, Wes Gamble  wrote:
> Can someone change the name of this page to "Merging existing extensions"
> and link to it under the "Creating Your Own Extensions" section?

done and done.

http://github.com/radiant/radiant/wiki
http://github.com/radiant/radiant/wiki/Merging-existing-extensions

anyone looking to do some wiki-tending might want to start by fixing
the wiki links that the new format broke; e.g. [[url|page title]] is
now [[page title|url]]. a global search and replace ought to do the
trick. i'll have some time later this week to do some work to get
things ready for the forced upgrade in september but help is always
appreciated.

Re: [Radiant] Addition to wiki (need a little help)

[john muhl]

is there a public issue for that? i don't to start working on it and
end up filing duplicate issues.

On Sun, Aug 15, 2010 at 9:47 PM, John W. Long  wrote:
> Some of the pages haven't transfered over yet. I've notified GitHub
> and they are working on it.
>
> --John
>
> On Sun, Aug 15, 2010 at 7:53 PM, john muhl  wrote:
>> On Sat, Aug 14, 2010 at 2:46 PM, Wes Gamble  wrote:
>>> Can someone change the name of this page to "Merging existing extensions"
>>> and link to it under the "Creating Your Own Extensions" section?
>>
>> done and done.
>>
>> http://github.com/radiant/radiant/wiki
>> http://github.com/radiant/radiant/wiki/Merging-existing-extensions
>>
>> anyone looking to do some wiki-tending might want to start by fixing
>> the wiki links that the new format broke; e.g. [[url|page title]] is
>> now [[page title|url]]. a global search and replace ought to do the
>> trick. i'll have some time later this week to do some work to get
>> things ready for the forced upgrade in september but help is always
>> appreciated.
>>
>

Re: [Radiant] Search on Heroku

[john muhl]

http://tenderlovemaking.com/2009/10/17/full-text-search-on-heroku/ might help.

i've been meaning to use that technique to whip up an extension but
haven't got around to it yet.

On Tue, Aug 24, 2010 at 3:05 PM, Jeff Casimir  wrote:
> Hi all,
>
> Is anyone using 0.9 with Heroku and making use of a search extension?
> Unless I'm missing something, Heroku pushes you toward Websolr.  The
> Solr extensions for Radiant if found looked out of date.
>
> Anyone solved this problem, or should I start digging/updating the
> older extension(s)?
>
> - Jeff
>
> ---
> Jeff Casimir
> Jumpstart Lab by Casimir Creative, LLC
> http://jumpstartlab.com
> @jumpstartlab on twitter
>

Re: [Radiant] Radiant on Heroku: Javascript Caching in Admin

[john muhl]

create it locally (by running in production) and commit it to your repo.

On Wed, Sep 8, 2010 at 9:38 AM, Jeff Casimir  wrote:
> Hey all,
>
> I have what is hopefully a quick issue.  My public facing site is
> running great, but the admin side doesn't work in production on
> Heroku.  Here's the trace:
>
> ActionView::TemplateError (Read-only file system -
> /disk1/home/slugs/261976_f884c4e_6faa/mnt/public/javascripts/admin/all.js
> - Heroku has a read-only filesystem.  See
> http://docs.heroku.com/constraints#read-only-filesystem) on line #9 of
> /home/slugs/261976_f884c4e_6faa/mnt/.bundle/gems/ruby/1.8/gems/radiant-0.9.1/app/views/layouts/application.html.haml:
> 6:     - @stylesheets.uniq.each do |stylesheet|
> 7:       = stylesheet_link_tag stylesheet
> 8:     %script{:type=>"text/javascript"}="var relative_url_root =
> '#{ActionController::Base.relative_url_root}';"
> 9:     = javascript_include_tag %w(admin/prototype admin/effects
> admin/lowpro admin/dateinput admin/pagestatus admin/cookie admin/popup
> admin/status admin/utility admin/codearea admin/tabcontrol
> admin/ruledtable admin/sitemap admin/shortcuts admin/toggle
> admin/validationerror admin/application), :cache => 'admin/all'
> 10:     - @javascripts.uniq.each do |javascript|
> 11:       = javascript_include_tag javascript
> 12:     - if @content_for_page_scripts
>
> This is Radiant 0.9.1.  It looks like the javascript_include_tag is
> trying to cache into 'admin/all' but failing because of the read-only
> file system.
>
> Tips?
>
> Thanks,
> Jeff
>
> ---
> Jeff Casimir
> Jumpstart Lab by Casimir Creative, LLC
> http://jumpstartlab.com
> @jumpstartlab on twitter
>

[Radiant] restricting tab visibility in 0.9

[john muhl]

i'm upgrading an extension from 0.8 to 0.9 and can't seem to find a
replacement for `:visibility => [:admin]` using the new tab method. is
there any?

Re: [Radiant] restricting tab visibility in 0.9

[john muhl]

On Wed, Sep 8, 2010 at 8:09 PM, Jim Gay  wrote:
> On Wed, Sep 8, 2010 at 7:59 PM, john muhl  wrote:
>> i'm upgrading an extension from 0.8 to 0.9 and can't seem to find a
>> replacement for `:visibility => [:admin]` using the new tab method. is
>> there any?
>>
>
> It's done in your controller now. For example
> http://github.com/radiant/radiant/blob/master/app/controllers/admin/layouts_controller.rb#L3

thanks. i figured i had to be just overlooking it.

> Often in the past, extension developers would set the visibility of a
> tab, but not restrict access. Now, you just restrict access in the
> controller and the links will appear based upon your access.

makes sense.

Re: [Radiant] textile_editor extension

[john muhl]

On Fri, Sep 10, 2010 at 12:39 AM, Steven Southard
 wrote:
> On Sep 9, 2010, at 5:16 PM, Steven Southard wrote:
>
>> Does anyone have a working 9.1 version of this extension?

i'm in the middle of upgrading a site from 0.8 to 0.9 and this is one
of the last few extensions holding me back. i hope it's nothing too
tricky. a couple of weeks ago i actually setup a site on 0.81 just
because t_e was incompatible with 0.9 and there was no time in the
budget to bother upgrading it.

> Who knows what it would take to update the 8.1 version?  I was noticing that
> someone had started another extension that seemed like it did mostly the
> same thing.  Is this a new start because there was something difficult about
> continuing with textile_editor?  It was nice but I always wish in integrated
> with assets better.  Maybe that was the issue? Or is the new design causing
> the issues?  I'm a fan of that extension and I'd love to start using it with
> .91 sites.

i think it's by far the best "editor for normal people" available for
radiant (even though it insist upon `em` and `strong` for
italic/oblique and bold). in my experience it works nicely with
page_attachments (at least in 0.8). what do you mean about not
integrating with assets?

Re: [Radiant] Re: How to use the toggle effect on pages?

[john muhl]

On Sat, Sep 11, 2010 at 8:16 AM, Allan MacGregor  
wrote:
> Is there a way to specify the onClick event for radius tags? for
> example for a set checkboxes or a dropdown?

radius is just a template language for outputting other formats; (i
guess) most often html. so simply have radius output the html that
makes it easiest for you to script. for example:


  A
  B
  C


outputs:


  
A
  
B
  
C


which you can script however you normally script html.

in plain old javascript style:

var target = function (e) {
 e = e || window.event;
 return e.target || e.srcElement;
};
document.forms['mailer'].onclick = function (e) {
 var t = target(e);
 if (t.type == 'checkbox') alert(t.value);
};

or in jquery style:

$('input[type=checkbox]').click(function () { alert(this.value) });

> On Sep 10, 5:55 pm, Wes Gamble  wrote:
>>   You may want to check out jQuery, which allows you to do effects like
>> this.
>>
>> See:http://api.jquery.com/category/effects/for the jQuery API
>> documentation on the show() and hide() methods.
>> Download:http://docs.jquery.com/Downloading_jQuery
>> Tutorials:http://docs.jquery.com/Tutorials
>>
>> Given:
>>
>> 
>>       This content will be shown/hidden.
>> 
>>
>> You would use something like
>>
>> $('.x').show() to show it and $('x').hide() to hide it.
>>
>> Good luck,
>> Wes
>>
>> On 9/10/10 3:32 PM, Horst Rischbode wrote:
>>
>>
>>
>> >  Hi,
>>
>> > I want to show (and be able to hide it again) a div on user's demand.
>> > I want to appear it similar to the 'less' & 'more' attributes
>> > behaviour of the edit page view.
>>
>> > I'm not familar with haml, so I don't understand, how to get this
>> > working on my gallery pages. Please be patient...
>>
>> > Can anybody point out, which JS libraries to include and how to build
>> > up a simple example with html?
>>
>> > Thanks for any advice!
>>
>> > Horst

Re: [Radiant] Upgrading: 0.6.7 -> 0.9.1

[john muhl]

On Thu, Sep 23, 2010 at 3:17 PM, D.Kreft  wrote:
> I'm attempting to upgrade Radiant from 0.6.7 to 0.9.1 and it's proving to be
> quite a pain.

i prefer to upgrade one version at a time. so in your case i'd first
go to 0.6.9, then 0.7.1, 0.8.1 and finally 0.9.1

Re: [Radiant] textile_editor extension

[john muhl]

On Fri, Sep 10, 2010 at 10:08 AM, Steven Southard
 wrote:
> On Sep 10, 2010, at 12:54 AM, john muhl wrote:
>
>> On Fri, Sep 10, 2010 at 12:39 AM, Steven Southard
>>  wrote:
>>>
>>> On Sep 9, 2010, at 5:16 PM, Steven Southard wrote:
>>>
>>>> Does anyone have a working 9.1 version of this extension?

davec (David Cato) has done the dirty work[1]. i pulled in his
changes, made a couple of insignificant fixes and updated the image
and link popups to be vaguely 0.9ish[2]. everything seems to be
working as expected so far.

1: http://github.com/davec/radiant-textile_editor-extension/tree/0.9
2: http://github.com/johnmuhl/radiant-textile_editor-extension

>> i'm in the middle of upgrading a site from 0.8 to 0.9 and this is one
>> of the last few extensions holding me back. i hope it's nothing too
>> tricky. a couple of weeks ago i actually setup a site on 0.81 just
>> because t_e was incompatible with 0.9 and there was no time in the
>> budget to bother upgrading it.
>>
>>> Who knows what it would take to update the 8.1 version?  I was noticing
>>> that
>>> someone had started another extension that seemed like it did mostly the
>>> same thing.  Is this a new start because there was something difficult
>>> about
>>> continuing with textile_editor?  It was nice but I always wish in
>>> integrated
>>> with assets better.  Maybe that was the issue? Or is the new design
>>> causing
>>> the issues?  I'm a fan of that extension and I'd love to start using it
>>> with
>>> .91 sites.
>>
>> i think it's by far the best "editor for normal people" available for
>> radiant (even though it insist upon `em` and `strong` for
>> italic/oblique and bold). in my experience it works nicely with
>> page_attachments (at least in 0.8). what do you mean about not
>> integrating with assets?
>
> I should have said paperclipped.  I haven't used page_attachments in a while
> but last time I did it worked well with this extension too.  I agree that
> this extension is very important for introducing textile to people that are
> new to code.  I wouldn't think it would hold me up from using .9.1 but now
> trying get people to accept textile without the extension is harder then I
> expected.
>
>

Re: [Radiant] Missing Images on Demo site and bootstrapped site.

[john muhl]

i believe they've been moved to http://demo-assets.radiantcms.org/

On Sun, Oct 3, 2010 at 3:29 PM, Chales  wrote:
> I've been eyeing the demo website for some time and finally had time
> this weekend to do an install and bootstapped my copy to use the same
> template. However all the images on the demo site and on the template
> reference http://spurrd.com/assets/... That domain redirects to
> http://readymadeit.com/assets/ which does not have the images. I plan
> of course to replace the images in my design, but having them as
> placeholders till I replace them would be nice as I'm hoping to
> present the layout to work soon. Is there any way to get a copy of the
> images and/or correct the http://demo.radiantcms.org/ site?
>
> Thanks,
> Cliff Hales

Re: [Radiant] How does one selectively hide tabs?

[john muhl]

On Tue, Oct 5, 2010 at 3:43 PM, D.Kreft  wrote:
> [Using Radiant 0.9]
> I've got an extension that adds a tab and two sub tabs, and I'd like the top
> tab to be visible only when the current user meets certain criteria (e.g.
> whose username is part of a hard-coded list, to use a simple example). How
> would I pull this off? I'm looking at the SNS extension as an example of an
> extension that adds two sub tabs if the user is an admin, but I'm not really
> "getting" what's going on--it seems to me that I should be seeing some sort
> of conditional logic before the call to 'tab', but I'm not seeing it.

it's in the controller.
http://goo.gl/VbJY

Re: [Radiant] strange behavior with git and extensions(and Capistrano)

[john muhl]

On Wed, Oct 13, 2010 at 9:51 AM, Blake  wrote:
> my setup is a local version of radiant with two custom extensions, and
> few installed ones (mailer, mediamaid, settings, share_layouts). I
> have a git repo of the project that I can cap deploy to my server
> successfully, but the extensions that I installed do not get copied
> up, meaning that the 'folder' gets added to git and and empty folder
> is pushed to the server.

i believe `./script/extension install` adds extensions as git
submodules. try adding:

set :git_enable_submodules, 1

to your config/deploy.rb file.

Re: [Radiant] Error when installing on Godaddy Shared Linux

[john muhl]

On Sun, Oct 17, 2010 at 4:35 PM, Lord.Quackstar
 wrote:
> Apparently when installing gem compiles the scripts to native code
> using make, gcc, and several other commands. I've had to manually
> download and add make and gcc to my PATH.
>
> Here's what happens
>
> [[na...@p3nlhjava006 html]$ gem install radiant
> Building native extensions.  This could take a while...
> ERROR:  Error installing radiant:
>        ERROR: Failed to build gem native extension.
> ...
> make: *** [/home/content/i/h/a/[name]/.gems/gems/RedCloth-4.2.3/lib/
> redcloth_scan.so] Error 1

i can't be of any help figuring out how to compile stuff on a godaddy
server but to skip the RedCloth installation altogether try:

gem install rake will_paginate
gem install rack -v 1.1.0
gem install radiant --ignore-dependencies

this will cause Radiant to fallback on its vendored (older, pure ruby) RedCloth.

Re: [Radiant] Quick question about updating extensions with git

[john muhl]

On Tue, Oct 19, 2010 at 2:56 PM, Nate Turnage  wrote:
> Hey all,
>
> It's been a while since I've worked with Radiant and Git, and I now need to
> update a couple of apps to, at least, 0.8.2.
>
> So I was wondering if somebody could help me out by listing the command used
> to update an extension that was added as a git submodule?
>
> Also, how can I specify which branch/tag to use?

off the top of my head (but hopefully close)

cd vendor/extension/ext
git fetch
git checkout -b new_branch repo_branch_name
cd ../..
rake radiant:extensions:ext:update
rake radiant:extensions:ext:migrate
git add vendor/extension/ext [other files]
git commit -m 'update ext'

Re: [Radiant] Stacktrace when using taggable_events in Radiant 0.9.1 - Undefined method `attached_tags'

[john muhl]

On Tue, Oct 26, 2010 at 2:02 PM, SS  wrote:
> Hi,
> Does anyone know why I'm getting this stacktrace when I try to add a
> new Event in my Radiant project?
>
> Am I missing another extension/plugin that is not mentioned in the
> documentation for taggable_events extension?

i don't have any first hand experience but a quick poke around the
repo it looks like you need at least event_calendar. do you have that
installed properly?

Re: [Radiant] Strange markup help

[john muhl]

On Wed, Oct 27, 2010 at 12:56 PM, D.Kreft  wrote:
> I'm (still) working on an upgrade from Radiant 0.6.7 to 0.9.1 and I'm seeing
> some markup in pages that rendered fine under the old system but not under
> the new. To cite a specific example:
>     %(h3)%(carat)›%"Contact Us":../contact-us%

%(XYZ)abc%

is textile for abc. so the output you get is
correct. but i've never seen it nested like that (and testing with the
latest redcloth shows that nesting is not allowed there). perhaps the
old cms had some textile extensions or just a different parser that
supported `span class` differently. to replicate it in radiant with
redcloth just replace the outer span.h3 with a real html element:

%(caret)›%"Contact Us":../contact-us

Re: [Radiant] Fresh install (error): comparison of String with 60 failed

[john muhl]

On Wed, Nov 3, 2010 at 2:51 PM, Jordon Bedwell  wrote:
> Rack 1.2
> Rails 3
> Ruby 1.9.2
>
> Perhaps you guys and gals can help me figure out how to fix this error:

try:

Rack 1.1.0
Rails 2.3.8 (Radiant has it vendored so your Rails 3 above is not
being loaded; i.e. you don't need to install Rails at all)
Ruby 1.8.7

Radiant does not run on any of the software you mentioned.

Re: [Radiant] rack/cache issue

[john muhl]

On Wed, Nov 3, 2010 at 7:02 PM, Rek2GNULinux  wrote:
> Hello decided to try radiant but I keep getting this error... any
> idea?
>
> rake production db:bootstrap
> (in /var/www/dev.binaryfreedom.info)
> rake aborted!
> no such file to load -- rack/cache

probably a bum install. could you explain how you installed radiant
and setup your site. and gist or pastie the output of `rake production
db:bootstrap --trace`

Re: [Radiant] Re: rack/cache issue

[john muhl]

On Wed, Nov 3, 2010 at 7:15 PM, Rek2GNULinux  wrote:
> I use gentoo so I emerge radiant then I run:
> radiant --database=mysql
> I created the mysql databases
> configure the /config/databases.yml
> and then I try
> rake db:bootstrap  and I get that error...

i don't know anything about gentoo or emerge. do they do anything
non-standard to
rubygems before releasing them in emerge? it sounds like something is butchering
the radiant gem you're getting a hold of (e.g. removing vendor/...).

you might try installing manually:
wget http://rubygems.org/downloads/radiant-0.9.1.gem
gem install radiant-0.9.1.gem

Re: [Radiant] Cache 404 responses or serve more static response?

[john muhl]

On Thu, Nov 4, 2010 at 2:25 PM, Jim Gay  wrote:
> On Thu, Nov 4, 2010 at 2:29 PM, Jordon Bedwell  wrote:
>> Is there a way I can force Radiant to cache error responses?
>>
>
> Override this 
> https://github.com/radiant/radiant/blob/master/app/models/file_not_found_page.rb#L29

if you're using nginx maybe you can use proxy_cache_valid. wouldn't
nginx win out (at least if you had a page not found page)?

http://wiki.nginx.org/NginxHttpProxyModule#proxy_cache_valid

Re: [Radiant] Ruby on Rails application could not be started

[john muhl]

On Thu, Nov 4, 2010 at 2:27 PM, Obi  wrote:
> I suddenly got this message on all my site pages today, can anyone please 
> explain what's causing it?:
>
> Error message: uncaught throw `Custom Fields Extension must be loaded before 
> Stereotype Extension'

looks like you need to install the custom_fields extension or track
down why it's suddenly gone missing if you had it installed previously

Re: [Radiant] Re: trouble running rake for custom extension

[john muhl]

On Sun, Nov 7, 2010 at 10:06 AM, Tobi
 wrote:
> Besides the complaint about missing jeweler it's still the same, but
> thanks for the reply.
> Anyone else got an idea?
> Where spec/rake/spectask is supposed to go. And what it should
> contain? I didn't find it anywhere at my system.

seems like something up with rspec. do you have it installed? do you
have an appropriate version installed (e.g. something from the 1.3
series)? is that version being loaded or are you getting a newer (or
older) version in your environment?

Re: [Radiant] Pull articles from multiple sources

[john muhl]

On Mon, Nov 8, 2010 at 6:49 PM, Jordon Bedwell  wrote:
> Is there a way to pull archives from multiple urls, something like:

...

check the in page tag reference for more aggregate tags

(if you're on 0.8 install the radiant/aggregation extension)

Re: [Radiant] Forms extension

[john muhl]

On Fri, Nov 12, 2010 at 9:34 AM, Marshal Linfoot  wrote:
> Has anyone used a forms/mailer extension for Radiant that allows a file to
> be attached and sent with the form? I have a form working -- users fills in
> text, selects choices from dropdown, checks radio buttons -- everything
> works, contents emailed successfully. I'm trying to add the capability for
> people to select a file (photo) from their computer to be attached to the
> email but I can't get it to work. If you've got it working, could you please
> share your solution?

try the aissac fork. i've setup mailer with attachments before and i
think that was the fork i used (if not poke around the network and
you'll find it).

Re: [Radiant] sheets extension and packing/minification

[john muhl]

can you set your server to gzip them? it ought to be nearly as
effective as minification.

On Fri, Nov 19, 2010 at 3:30 PM, Stan Rawrysz  wrote:
> Has anyone had any success with packing/minifying/compressing the css and
> javascript when using the sheets extension or sns extension? We're currently
> using the sns extension, but I'm looking to update the site to use sheets
> and am just doing research. Would like to know if anyone has already done
> any work on the compression front.
>
> Thanks,
> Stan

Re: [Radiant] how to upgrade from 0.8 to 0.9?

[john muhl]

On Sat, Nov 20, 2010 at 12:06 PM, Eric  wrote:
> The docs/wiki are way out of date and there is no RADIANT_* in

fortunately it's a wiki so you could clean it up if it has incorrect
information; or point me to the page and as soon as time allows i'll
look at it.

> environment.rb (or environments/*) at all. I've found that 0.8.1 (or
> some plugin) has disabled ctrl-right arrow, which I use to navigate
> through text quite often, so I'd like to check whether 0.9 will fix it
> or if it's a bigger problem.

if you have some extension that is highjacking keystrokes upgrading
your radiant isn't going to change that (unless 0.9 breaks that
extension and you can no longer use it). do you know which extension
is causing the problem? if not try disabling all of your extensions
and add them back one at a time until you find the culprit. personally
i've found managing radiant versions with rubygems a pain in the ass
and freeze projects to the version of radiant they need. which i find
makes upgrades easier.

- trash vendor/radiant
- disable all extensions
- freeze radiant to new version
- run the db:migrate and radiant:update rake tasks
- grab the latest versions of extensions
- enable them one at a time until everything is working

Re: [Radiant] Running 0.8.1 though having 0.9 gem installed

[john muhl]

On Wed, Nov 24, 2010 at 4:49 AM, T.N.T.  wrote:
> Is is possible to run different Radiant versions in parallel or do I
> need to deinstall 0.9 completely to be able to run 0.8.1?

i find the easiest way to handle it is to lock each project to the
version of radiant needed.

(from inside your project directory)

rake radiant:freeze:gems # locks to the version of radiant you
installed through rubygems

rake radiant:freeze:edge TAG=0.8.2 # locks to version 0.8.2 - requires
git to be in your PATH

you could also download an archive of a previous version and unpack it
to /your/project/vendor/radiant
archives are available at https://github.com/radiant/radiant/downloads

with any of these you will end up with a completely isolated version
of radiant kept in each project in the vendor/radiant directory.

Re: [Radiant] Help Error: Mongrel/Radiant Config Issue

[john muhl]

On Tue, Nov 30, 2010 at 9:31 AM, bh7322  wrote:
> Object is not missing constant ShopProductAttachment! (ArgumentError)

looks like something called "ShopProductAttachment" might be having a
problem. do you have any extensions installed that are named like
that? what happens if you disable it (move it out of vendor/extensions
or remove the config.gem line that loads it from
config/environment.rb) and try to start mongrel?

Re: [Radiant] Re: Radiant as Rails3 engine & RADIANT_ROOT

[john muhl]

On Tue, Nov 30, 2010 at 2:48 PM, Marc  wrote:
> I was wondering if it would be
> possible to fix the rails version to say 2.3.8?

radiant has a frozen version of rails in the gem (and repo in case you
don't use the gem). so none of your rails gems matter to radiant (you
could uninstall them all and radiant will still run).

Re: [Radiant] Re: Radiant as Rails3 engine & RADIANT_ROOT

[john muhl]

looks like it might be coming from the member extension (or not it was
just the first hit in google).

https://github.com/Aissac/radiant-member-extension

On Tue, Nov 30, 2010 at 3:07 PM, Marc  wrote:
> That is good to know, and now means I have to work out why I am
> getting:
>
>  undefined method `home_path' for #
>
> when creating the admin user…
>
> On Dec 1, 8:01 am, john muhl  wrote:
>> On Tue, Nov 30, 2010 at 2:48 PM, Marc  wrote:
>> > I was wondering if it would be
>> > possible to fix the rails version to say 2.3.8?
>>
>> radiant has a frozen version of rails in the gem (and repo in case you
>> don't use the gem). so none of your rails gems matter to radiant (you
>> could uninstall them all and radiant will still run).

Re: [Radiant] best code syntax highlighting solution

[john muhl]

On Wed, Dec 8, 2010 at 1:39 AM, craayzie  wrote:
> I've begun to explore Radiant as a publishing/blogging platform. At
> the moment, I'm trying to nail down is how to best format command-line
> output or code as the majority of the content published will be of a
> technical nature.
>
> Can someone point me in the right direction of what I should use to
> get the "desired" affect :P
>
> I found http://alexgorbatchev.com/SyntaxHighlighter/ which is a
> JavaScript-based solution. Unfortunately it doesn't appear to support
> formatting/highlighting command-line output.
>
> What's the best Radiant filter / JS library / some-other-solution out
> there for both command-line output and code syntax highlighting?

i like kramdown + coderay.

Re: [Radiant] Contact form debugging as Radiant new user learning opportunity...

[john muhl]

On Wed, Dec 8, 2010 at 9:55 AM, rosslaird  wrote:
> I am a new user to Radiant (coming from Drupal), and so far I've found
> Radiant to be a great application. I have also received excellent help
> from the community (here and on github), and this is also great.
> (Actually, a strong and helpful community is the most important thing
> of all.) I have almost finished rebuilding my website in Radiant, but
> I just need to get the contact form working properly. I have installed
> and setup the mailer extension and the contact form. The form seems to
> work, but does not redirect me to the thanks page. Also I do not
> receive the email (I'm working from localhost at the moment, on
> Ubuntu, so the fact that I do not get the email is not overly
> surprising. It could be caused by a number of things, though the mailq
> is empty). The log, however, says "Sent mail to em...@address.com," so
> at least something is working. I am in the process now of debugging
> this, and I've started to look at various posts that discuss
> validation, changing environments.rb, and so on. Before I wade too
> deeply into this process, I thought I'd ask for a bit of help. I don't
> want to do anything to break the whole system. So:
>
> 1. I've seen in various posts that I should add some email info to
> environments.rb. There is currently no reference to such things in
> that file. In the following two tutorials (let's hope the url's don't
> get scrubbed here), different methods of adding email details are
> offered:
>
> http://railsforum.com/viewtopic.php?id=404
> http://wiki.rubyonrails.org/rails/pages/HowToSendEmailsWithActionMailer
>
> Which of these should I use, or should I do something else? For now, I
> have simply changed one line in environment.rb, as suggested by the
> mailer documentation. I changed this:
>
> config.frameworks -= [ :action_mailer ]
>
> To this:
>
>  config.frameworks -= [ ]
>
> So, I haven't added mailing details (smtp, user, and so on) anywhere.
> Perhaps that's the place to start. Suggestions most welcome.

does https://github.com/radiant/radiant/wiki/mailer-extension help at all?

Re: [Radiant] best code syntax highlighting solution

[john muhl]

http://johnmuhl.com/tmp/kramdown-coderay

the kramdown looks like (replace - with space):

def meth options
--p options
end
{:lang="ruby"}

just a standard markdown code block followed by {:lang="lang"}

http://coderay.rubychan.de/ list the supported languages.

On Wed, Dec 8, 2010 at 12:37 PM, Fima Leshinsky  wrote:
> Thanks John - will take a look. Do you have any public pages you can share
> as examples?

Re: [Radiant] Re: best code syntax highlighting solution

[john muhl]

gem install radiant-kramdown_filter-extension
gem install coderay

then in config/environment.rb

...
require 'radius'
require 'coderay' # add this line
...
config.gem 'will_paginate', :version => '~> 2.3.11'
config.gem 'radiant-kramdown_filter-extension' # add this line
...

then restart radiant and you should be all set.

On Sun, Dec 12, 2010 at 5:23 PM, Fima Leshinsky  wrote:
> So looks like there are two radiant extensions below that allow you to
> leverage the coderay gem:
> https://github.com/phallstrom/code_ray
> https://github.com/alno/radiant-code-extension
> I'm inclined to use the the 2nd one since it supports other syntax
> highlighters beyond coderay. What are your thoughts on which one to use?
>
> Also, I'm curious, why use kramdown over the existing Markdown radiant
> filter? Speed or other reasons as well?
> Thanks!

Re: [Radiant] Re: Re: best code syntax highlighting solution

[john muhl]

On Mon, Dec 13, 2010 at 8:56 AM, Fima Leshinsky  wrote:
> Looks like coderay is working well. I installed:
> coderay gem + radiant extension @ https://github.com/phallstrom/code_ray
> and now I can specify  blocks!
> not sure what the benefits are of kramdown over the existing Markdown
> radiant filter that comes with the "Coffee blog" template. If you guys can
> shed some light on why kramdown is a better option I'd appreciate it.

it's not better. it's the same but with kramdown specific options enabled.

Re: [Radiant] Kramdown vs. markdown filter

[john muhl]

i can't remember for sure but i think you can have both installed and
kramdown will appear as a distinct filter alongside markdown in the
menu.

On Thu, Dec 16, 2010 at 4:24 PM, Wes Gamble  wrote:
> Radiant 0.9.1
>
> I see that the kramdown_filter extension just got updated to the kramdown
> 0.12 gem.
>
> If I want to use the kramdown_filter, should I remove the existing
> markdown_filter extension?
>
> Thanks,
> Wes
>

Re: [Radiant] Kramdown vs. markdown filter

[john muhl]

On Thu, Dec 16, 2010 at 6:42 PM, Wes Gamble  wrote:
> Thanks John,
>
> I installed the kramdown filter, took a page and switched it from "markdown"
> to "kramdown" and got this error:

apparently i guessed wrong. disable markdown and see if it works.

Re: [Radiant] Edge Radiant on Heroku SASS/Compass problem

[john muhl]

On Sat, Dec 18, 2010 at 1:31 PM, Martin Silenus  wrote:
> Hi everyone. I have a problem with my Radiant application. I try
> running it on heroku.com, but can't get it work.

i put `Sass::Plugin.options[:never_update] = true` at the end of my
environment and use `sass --watch` to keep things up to date in
development. you'll need to commit the static versions to your repo.
there's also a plugin called hassle that works by emitting generated
css to RAILS_ROOT/tmp

Re: [Radiant] Pre-loading cache

[john muhl]

On Mon, Dec 20, 2010 at 7:13 PM, Wes Gamble  wrote:
> All,
>
> Is there any way to pre-load the Radiant cache so that initial page view
> times are improved?

i'd just hook wget to a post-deploy task. surely there is something
more elegant though.

Re: [Radiant] Date picker from Radiant admin

[john muhl]

On Sun, Jan 16, 2011 at 7:12 AM, Martin Silenus  wrote:
> Can I use date picker script(published_at field) from radiant admin in
> my own extension? How to do that? Thanks.

https://github.com/jlong/dateinputjs

[Radiant] Re: best code syntax highlighting solution

[john muhl]

(whoops. accidentally sent off list)

looks at my previous posts in this thread. i explained it there. you
only need the kramdown_filter extension and the coderay gem (not the
coderay extension). usage looks like:

def meth options
--p options
end
{:lang="ruby"}

where - is replaced with space as you would in regular markdown `pre`
blocks. i don't think it gets easier than that.

On Mon, Jan 17, 2011 at 4:52 PM, craayzie  wrote:
> My coderay + kramdown markup is really heavy/cumbersome. Is there a
> better way?
>
> Here's an example:
>
> # heading
> 
> ## sub-heading
> 
> 
> code-goes-here
> 
>
> Ideally I could just write:
>
> # heading
> ## sub-heading
> $
> code-goes-here
> $
>
> (using '$' to endicate start/end coderay blocks)
>
> Any advice/guidance on how to best simplify the markup?

Re: [Radiant] Crazy,crazy,You have never seen such perfect N*U*D*E ART

[john muhl]

stop replying and making it show up in everyone's inbox. most of us
have good enough spam filters that this garbage does not make it
through...until someone replies...

On Tue, Jan 18, 2011 at 8:25 AM, William Ross  wrote:
> It was splendid, wasn't it? But it shouldn't have got through. Sorry about 
> that. I've blocked the sender so there shouldn't be another.
>
> best,
>
> will
>
>
>
> On 18 Jan 2011, at 09:47, Arthur Gunn wrote:
>
>> wow, what a truly incredible spam specimen.
>>
>
>