I actually had to do a different step which makes more sense. I edited:
/opt/ruby-enterprise-1.8.7-2010.02/lib/ruby/gems/1.8/gems/radiant-0.8.2/vendor/rails/actionpack/lib/action_controller.rb
And changed the gem rack line to 1.1.0. Now I'm flying.
Changing the gemspec should just change the i
Is sphinx easy to install? We would probably need to get Andrew
vonderLuft our sys admin to set it up.
But yes, I'm potentially interested in a patch.
http://github.com/radiant/radiant-extension-registry
--John
On Wed, Aug 11, 2010 at 10:17 AM, Christian Aust
wrote:
> Works, but feels somewhat
Which version of radiant do you have installed?
gem list (and you'll see radiant's version next to its name in parens). I'm
suspecting it's 8, as that seems to be a 9 version diff.
On Wed, Aug 11, 2010 at 2:52 PM, Lindsay Morris wrote:
> Very helpful. Two different install techniques. I had no
Very helpful. Two different install techniques. I had no idea.
So I took the config.gem line away, and ran
[lind...@gator634 ~/rails_apps/radiant]$ rake
radiant:extensions:forms:migrate
(in /home/lindsay/rails_apps/radiant)
rake aborted!
undefined method `tab' for #
What's next?
On Wed, Aug 1
On Wed, Aug 11, 2010 at 5:09 PM, Lindsay Morris wrote:
> Jim, when I added "config.gem ..", the app wouldn't start; complained "gem
> not installed".
> Which makes sense since there's no vendor/extensions/forms directory.
>
You misunderstand. It would say "gem not installed" if the user trying to
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:form
Jim, when I added "config.gem ..", the app wouldn't start; complained "gem
not installed".
Which makes sense since there's no vendor/extensions/forms directory.
Trying Anna's advice:
script/extension install forms
fails: "git was compiled without libcurl support".
I can't be root on this box.
The spanner fork of radiant-sns-sass-filter-extension was helpful so
that I could tell Radiant where to look for my _mixins.sass file.
Also, I learned that you can't mix and match the SCSS/Sass syntax in one
file of a certain type (SCSS or Sass). I was trying to use
@mixin/@include in a Sas
On Wed, Aug 11, 2010 at 2:43 PM, Steven Southard
wrote:
> Is this caused by migrating paperclipped before settings? I read something
> about that but why does that cause a problem? Is there a good way to fix
> the issue if it really is an issue?
>
> Cheers,
>
> Steven
>
> On Aug 10, 2010, at 11:
Works beautifully. Thanks!
On 8/11/10, Jim Gay wrote:
> I've made some updates and I'm not able to recreate this problem.
>
> I've created a new instance from edge
> Used the #4 template (Styled Blog)
> Copied the Styles.css page content into a new stylesheet and saved it.
> Changed the layout fr
Is this caused by migrating paperclipped before settings? I read
something about that but why does that cause a problem? Is there a
good way to fix the issue if it really is an issue?
Cheers,
Steven
On Aug 10, 2010, at 11:51 AM, Steven Southard wrote:
I have the same thing now. Did
Thanks for posting this guys, I was about to come up with a more
complex solution to the same problem.
- Jeff
On Tue, Aug 10, 2010 at 9:41 PM, Bill Heaton wrote:
> editing the gemspec worked for me as well.
>
> s.add_runtime_dependency(%q, [">= 1.0.0","< 1.2.1"])
>
> -Bill
>
>> But with pre-0.9,
No, it's not a general question. I'm using the SNS Sass filter
extension, and I couldn't get my Sass file to see the mixin file.
The change at http://github.com/spanner/radiant-sns-sass-filter-extension
looks like it will help. I just haven't tested it yet.
Wes
On 8/11/10 12:25 PM, Jim Gay
Does hostgator give you command-line, or shell, access to the server? For
extensions to work (last time I looked) you need to run a command-line
series of commands. One simple one is, in the rails-root directory, type
"script/extension install forms"
That will create the forms directory in the ven
I think this was just a general question with Sass, not the SNS Sass filter
extension.
Wes, I don't have an answer for you. But you might try the Haml mailing
list http://groups.google.com/group/haml
On Wed, Aug 11, 2010 at 2:18 AM, William Ross wrote:
> On 10 Aug 2010, at 17:47, Wes Gamble wro
Please reread my previous reply.
You've installed the gem and that's it. There is nothing telling your
application to use it.
On Wed, Aug 11, 2010 at 12:11 PM, Lindsay Morris wrote:
> I used hostgator's cpanel web interface to install it.
> There is no vendor/extensions/forms directory.
>
> So I
I used hostgator's cpanel web interface to install it.
There is no vendor/extensions/forms directory.
So I ran "gem install radiant-forms-extension"; it seemed to work:
[lind...@gator634 ~/rails_apps/radiant]$ gem install radiant-forms-extension
Successfully installed radiant-forms-extension-2.0.1
Great news Jim. Gonna try it out as soon as I get home.
Thanks!
On 8/11/10, Jim Gay wrote:
> I've made some updates and I'm not able to recreate this problem.
>
> I've created a new instance from edge
> Used the #4 template (Styled Blog)
> Copied the Styles.css page content into a new stylesheet
Works, but feels somewhat clumsy. What about using thinking_sphinx for
searching the extensions? I'd volunteer to create a patch.
Am Mittwoch, den 11.08.2010 um 15:42 schrieb john muhl:
> http://www.google.com/search?q=0.9+site:ext.radiantcms.org
>
> On Wed, Aug 11, 2010 at 7:44 AM, Christian Au
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
>
Hi Keith,
Thanks for your reply.
I had the settings in place. I tried your setting, restarted apache and the
path looks still like this:
http://s3.amazonaws.com/com-sichtwerk-imuw-ch/Users/cmyk/Sites/imuw-ch/public/assets/9/grt.jpg
It should look like, no?:
http://s3.amazonaws.com/com-sichtwerk-
On Wed, Aug 11, 2010 at 7:07 AM, Robert Wenc wrote:
> I'm trying to upgrade a old site form Radiant 0.6.9 to 0.9.1. I've
> installed the new gem, and run the rake update task in the project. I
> had some errors with extensions, but managed to get by that by
> disabling them. Everything looked
I've made some updates and I'm not able to recreate this problem.
I've created a new instance from edge
Used the #4 template (Styled Blog)
Copied the Styles.css page content into a new stylesheet and saved it.
Changed the layout from using a direct link to the /styles.css page to
(Using the same
Hi all,
is there a way to serach for all extensions marked as 0.9-compatible on
http://ext.radiantcms.org/? Regards,
Christian
I'm trying to upgrade a old site form Radiant 0.6.9 to 0.9.1. I've
installed the new gem, and run the rake update task in the project. I
had some errors with extensions, but managed to get by that by
disabling them. Everything looked good until I run the db:migrate
task. It runs to completion,
You need to set the path in you Radiant::Config. I use the Settings
extension to make it easier.
Here is mine: :class/:id/:basename:no_original_style.:extension
Hope that helps
keith
On Aug 9, 7:18 pm, cmyk wrote:
> I've got an issue with the paperclipped extension and s3.
> I set it to use S3
Doesn't work like that.
First: While it might be possible to add that helper to the relevant
controllers, there's no need to do so: Radiant tags are used in
layouts and snippets instead of ERB syntax. In fact, helper methods
aren't even accessible directly from radius tags, because a "context"
in
Hi,
I´m planning on creating a helper that can base64 encode images.
i.e. <%= base64_encode(path_to_image) %>
I started by running script/generate extension base64_encoder
Then I created
app/vendor/extension/base64_encoder/app/helpersbase64_encoder_helper.rb:
module Base64EncoderHelper
def b
28 matches
Mail list logo