Andrew Neil wrote:
Hello all (and especially Mohit),
Hello Drew (and everyone)
A couple of weeks ago I started work on the article "Using the
built-in tags" for the Summer Reboot. My intention was to go over a
handful of Radius tags which carry out 'typical' functions, such as
inserting cont
john wrote:
Nevermind, a little patching and it's up and running, now just to
figure out what "To enable spam protection, you will need to set your
Akismet key and url in the Radiant config." is supposed to mean...
Hi John
Can I urge you to please consider writing out the steps and a bit of
You might try specifying the production database in your rake
commands, like
rake production radiant:extensions:paperclipped:migrate
rake production radiant:extensions:paperclipped:update
by default the rake commands run on the development database. Or in
your database.yml file set your deve
I am very new, but I am having fun and learning everyday.
mysaw.com is up !!! I actually go this running on hostingrails.com
without any help. I KNOW I have a lot of work to do, but it's start and
it's real. BTW, this is my hobby site. My hobby is woodworking !!! If
you are interested here is th
Hello all (and especially Mohit),
A couple of weeks ago I started work on the article "Using the built-
in tags" for the Summer Reboot. My intention was to go over a handful
of Radius tags which carry out 'typical' functions, such as inserting
content, changing scope, showing content on cond
Nevermind, a little patching and it's up and running, now just to
figure out what "To enable spam protection, you will need to set your
Akismet key and url in the Radiant config." is supposed to mean...
On 2008/08/31, at 12:22, john wrote:
If there is any actual documentation for the "artof
I could use some help installing RoR, Radiant, and setting it up to allow to
host multiple sites.
If anyone can help, please email me and tell me know how much you will
charge (PayPal).
My CrucialP.com account has Ruby on Rails and RubyGems links and also
provides instructions to setting it up (y
Hi,
I solved the same problem by having my data insertion code as part of a
migration. That way, when you run the
rake production db:migrate:extensions
all your data is inserted. It's a fairly common command to run anyway
when installing a new extension.
You could even put it in your extensio
In the extension creation tutorial
http://wiki.radiantcms.org/Creating_Radiant_Extensions It's
recommended to keep to convention about installing extensions like:
radiant:extensions:shiny_new_extension:install
radiant:extensions:shiny_new_extension:uninstall
Correct me if I'm wrong but it's just
