Hi,
A while ago, there have been an Assets Manager plugin for Radiant,
that enabled the upload of assets, like images.
I want to be able to upload images to my Radiant site and reference
them in the pages using Radius tags. How can I do that today with
Radiant 0.6.1? Is there an equivalent
Hi Sean,
Do you have any documentation on the page attachment extension? I have
run the rake command and now have the plus icon. It looks as though it
is working. However after I save the page and then try to find the
image I've tried to upload it does not seem to have been added anywhere.
Hi,
I have a snippet where I store my navigation bar. It's a bullet list,
and I use CSS to make it looks like a bar, with each link as a button.
Is there a way to have this bar dynamic, where the correct button
while be attached a current CSS class appropriately?
Thank you all.
J.
Loren Johnson wrote:
Available Tags reference link. Also note that if you're NOT using
0.6.1 (you should be :) then you'll find that the url separator
character is a semi-colon (;) not a pipe (|).
Actually, on 0.6.1 it's a pipe not a simi-colon.
--
John Long
http://wiseheartdesign.com
The upload path is set automatically by the PageAttachment model. Do
you have an image processor (RMagick, MiniMagick, ImageScience)
installed on your server, or local machine, or wherever you're testing this?
Sean
Sharon Clift wrote:
Hi Sean,
Do you have any documentation on the page
Ah, yes. I had forgotten! Make sure to use Radiant edge:
rake radiant:freeze:edge
The stock 0.6.1 page-edit interface doesn't allow file uploads, but that
has since been changed in trunk.
Sean
Sharon Clift wrote:
Hi Sean,
Do you have any documentation on the page attachment extension? I
At that point, it should only get nil if the YAML file was not correctly
loaded ( data['records'] is the meat of the template ).
Sean
Jonathan Métillon wrote:
From: Sean Cribbs [EMAIL PROTECTED]
To: radiant@lists.radiantcms.org
Date: Thu, 31 May 2007 11:05:34 -0500
Subject: Re:
rake radiant:freeze:edge
rake radiant:extensions:page_attachments:update
Restart your app server.
Sean
ozon wrote:
hello!
I'm istalled a page_attachment (i migrated database and copy code to
proper directories) in my radiant cms site on mediatemple, and this
plugin didn't works. What i do
i also use TinyMCE extension, maybe this one causes the problem?
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:
here is also result of my rake command:
rake radiant:extensions:page_attachments:update RAILS_ENV=production
(in /home/x/containers/rails/y)
Loaded suite /home/x/data/rubygems/gems/bin/rake
Started
Finished in 0.000179 seconds.
--
Posted via http://www.ruby-forum.com/.
There have been very few changes in trunk since 0.6.1. At RailsConf
John mentioned releasing 0.6.2 quickly if we wanted. So, in short, I
don't know! However, the overwhelming majority of changes we make are
thoroughly tested, and you can choose to freeze to any tag, branch or
revision when
Hey,
I just read this post:
http://www.therailsway.com/2007/6/1/railsconf-recap-skinny-controllers
And it made me think immediately of the old handle_new_or_edit_post in
page_controller
http://dev.radiantcms.org/radiant/browser/trunk/radiant/app/controllers/admin/page_controller.rb?rev=57
But
We would love a patch, of course! This will also help in a future
refactoring toward REST which is on the horizon.
Sean
Jacob Burkhart wrote:
Hey,
I just read this post:
http://www.therailsway.com/2007/6/1/railsconf-recap-skinny-controllers
And it made me think immediately of the old
I don't know whether John has gone out of town yet or not, so I'll do my
best to reply in his stead.
In general, the mailing list is faster because it's more in-your-face.
Too, I think it's a good principle to discuss something thoroughly on
the mailing list, then create a patch or ticket on
On 6/1/07, Sean Cribbs [EMAIL PROTECTED] wrote:
At that point, it should only get nil if the YAML file was not correctly
loaded ( data['records'] is the meat of the template ).
Sean
Well, can be. But I did not mess with the YAML dump file. I passed it
directly from the db:export right to the
On 6/1/07, John W. Long [EMAIL PROTECTED] wrote:
Jonathan Métillon wrote:
Hi,
A while ago, there have been an Assets Manager plugin for Radiant,
that enabled the upload of assets, like images.
I want to be able to upload images to my Radiant site and reference
them in the pages
Jonathan Métillon wrote:
On 6/1/07, Sean Cribbs [EMAIL PROTECTED] wrote:
At that point, it should only get nil if the YAML file was not correctly
loaded ( data['records'] is the meat of the template ).
Sean
Well, can be. But I did not mess with the YAML dump file. I passed it
Thanks for the laugh, ya'll.
On Jun 1, 2007, at 11:09 AM, Loren Johnson wrote:
But that's what I said ;)
On Jun 1, 2007, at 7:04 AM, John W. Long wrote:
Loren Johnson wrote:
Available Tags reference link. Also note that if you're NOT using
0.6.1 (you should be :) then you'll find that
But.. but... the point is to YES USE THE PIPE IN 0.6.1 earlier
versions NO
It's getting funnier all the time ;)
On Jun 1, 2007, at 11:05 AM, Jonathan Métillon wrote:
On 6/1/07, Loren Johnson [EMAIL PROTECTED] wrote:
Jonathan,
Take a look at the documentation for the r:navigation urls='
Jacob,
Your patch adding the level tag in r:navigation is quiet tidy. In
my own Swiss Army tag library extension which I dump into nearly
every Radiant site I put up I have a similar tag r:navigation_level
level=2. Your version is cleaner. My tag gets use in combined with
an r:level /
David Piehler wrote:
I'm running Radiant 0.6.0rc2
Is there any way to disable caching of Radiant generated pages AND
plugin code when running in development mode? Having to clear the page
cache after every plugin code change is slowing me down.
In order to not cache Radiant pages I had
On 6/1/07, Loren Johnson [EMAIL PROTECTED] wrote:
Jonathan,
Take a look at the documentation for the r:navigation urls=' tag.
It should do everything you describe and a little more.
I've copied the docs to this bottom of this message, but if you're on
the current 0.6.0 or 0.6.1 version of
Sean Cribbs wrote:
rake radiant:freeze:edge
rake radiant:extensions:page_attachments:update
Restart your app server.
Sean
And on rake radiant:extensions:page_attachments:update
I have:
C:\radiantrake radiant:extensions:page_attachments:update
(in C:/radiant)
rake aborted!
Don't know how
On Jun 1, 2007, at 1:21 PM, Loren Johnson wrote:
Also note that if you're NOT using
0.6.1 (you should be :) then you'll find that the url separator
character is ... not a pipe (|).
Double negatives are hard outside of code, too, I see.
Ha! adam
No they're not
;)
On Jun 1, 2007, at 11:28 AM, Adam Williams wrote:
On Jun 1, 2007, at 1:21 PM, Loren Johnson wrote:
Also note that if you're NOT using
0.6.1 (you should be :) then you'll find that the url separator
character is ... not a pipe (|).
Double negatives are hard outside
This is actually pretty old and the big thing missing from it is
backwards-compatibility. One thing I personally would like to maintain
about the navigation tag is that it is independent of the site
structure. Anyway, here's the pastie of my original idea:
http://pastie.caboo.se/26340
Sean
Double negatives are hard outside of code, too, I see.
Ha! adam
Yet another reason to stay away from !! in Ruby.
Sean
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:
Sean Cribbs wrote:
In general, the mailing list is faster because it's more in-your-face.
Too, I think it's a good principle to discuss something thoroughly on
the mailing list, then create a patch or ticket on Trac that addresses
the issue.
In our defense I've asked that people talk
Sean Cribbs wrote:
One thing I personally would like to maintain
about the navigation tag is that it is independent of the site
structure.
Agreed. I'm not entirely sure I like the syntax of the new navigation
tag. I wonder if there is a way to simplify it:
r:navigation
r:items
Web
Sean Cribbs wrote:
Yet another reason to stay away from !! in Ruby.
That is so !!true. :) Except that I do like to use it to convert an
expression into either true or false:
def open?
[EMAIL PROTECTED] #if pipe is nil convert it to false
end
--
John Long
http://wiseheartdesing.com
Yeah, there are not many changes to the core since 0.6.1, mostly
extension changes.
Sean
John W. Long wrote:
Sean Cribbs wrote:
There have been very few changes in trunk since 0.6.1. At RailsConf
John mentioned releasing 0.6.2 quickly if we wanted.
It'll be at least a week or
I'm a bit confused about freezing. Here's what I did:
cd ~/Sites/myproject
rake radiant:freeze:edge
This creates ~/Sites/myproject/vendor/radiant which appears to duplicate
all of what is in ~/Sites/myproject and also adds in all the app files,
etc.. I'm just confused by the duplication and
maybe someone post a FULL instruction how to install page_attachment
plugin? please. i'm try to do this from scrathch.
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search:
Loren Johnson wrote:
You're absolutely right, sorry I hadn't looked closely enough.
You could gem install Radiant and generate an instance and then merge
the necessary bits from the environment.rb it generates into your
existing app.
If I get a chance I'll try and determine what those
I'm struggling trying to get radiant-0.6.1 installed in a subdirectory. My
current approach is to use an Apache proxy.
I note there are threads starting:
http://lists.radiantcms.org/pipermail/radiant/2006-September/002022.html
Earl Chew [EMAIL PROTECTED] wrote:The problem is that when Apache forwards
the request using proxypass, it includes the following in the HTML:
--
HTTP_X_FORWARDED_HOST: foo
HTTP_USER_AGENT: Wget/1.10.2 (Red Hat modified)
SCRIPT_NAME: /
SERVER_PROTOCOL: HTTP/1.1
HTTP_HOST:
1) Follow the general instructions (available on the Wiki, weblog, and
mailing list archive) for installing Radiant and creating a new
project, including initializing the database.
2) From the root of your Radiant project/instance, run these commands in
order:
svn export
On 02/06/07 01:00 AM, Earl Chew was heard to say:
Earl Chew [EMAIL PROTECTED] wrote:The problem is that when Apache forwards
the request using proxypass, it includes the following in the HTML:
--
HTTP_X_FORWARDED_HOST: foo
HTTP_USER_AGENT: Wget/1.10.2 (Red Hat
38 matches
Mail list logo
