Are you able to send mail from any other rails app?
The mailer extension (as far as I know) does nothing special in
sending mail and your settings in your environment should be the same
as those that you use in any other rails app.
I have another app where I use a gmail account to test my
I'm adding extensions to a new instance of radiant and, when running
"rake db:migrate:extensions", getting the error
undefined method `publish_associations' for class `Page'
Important info:
version 0.6.4
I've set:
config.extensions = [ :shards, :all ]
And I have these extensions from release
you give me a line number on which that occurs? Run the rake task
with --trace.
Sean
Jim Gay wrote:
I'm adding extensions to a new instance of radiant and, when
running "rake db:migrate:extensions", getting the error
undefined method `publish_associations' for class `
I'm trying out using acts_as_taggable_on_steroids (with the plugin in /
vendor/plugins/) and getting an error:
uninitialized constant LibraryResourceSearchPage::Tag
I'm tying in an existing part of the database with radiant tags.
The tag causing the error is this:
tag 'library_search:resour
ote:
Jim,
Radius also has a "Tag" class, so try putting :: in front of the
classname so that it looks in the root namespace.
Sean
Jim Gay wrote:
I'm trying out using acts_as_taggable_on_steroids (with the plugin
in /vendor/plugins/) and getting an error:
On Mar 31, 2008, at 8:56 PM, Benny Degezelle wrote:
I'm a bit late to the party but; I have a working tags extension
extension
here that runs on has_many_polymorphs
you should be able to svn export
svn://zuurstof.openminds.be/home/kaizer/svn/rails_stuff/
radiant_extensions/tags
It's not 10
If you mean on the public content, then use Javascript however you
would with any other system: link to the JS files on your server and go.
If you mean on the admin side, you can install the Shards extension
(read this http://wiki.radiantcms.org/Using_the_Shards_Extension)
On Apr 20, 2008,
I would add that your spec should be more specific. When all of your
specs are generated they should be clear.
it "should validate format of name" gives you no information about
what that format should be. Your spec should describe how the
application functions, so if it were me, I'd write my
Run rake production db:migrate
The keywords and description fields were added
On Apr 30, 2008, at 7:06, nurullah <[EMAIL PROTECTED]> wrote:
Parameters: {"action"=>"edit", "id"=>"37", "controller"=>"admin/page"}
Rendering template within layouts/application
Rendering admin/page/edit
ActionVie
nment (first_time)
** Execute environment
rake aborted!
undefined method `page' for #
/var/www/nginx-default/vendor/extensions/newsletter/
newsletter_extension.rb:22:in
`activate'
On 4/30/08, Jim Gay <[EMAIL PROTECTED]> wrote:
Run rake production db:migrate
The keywords and description
On May 12, 2008, at 6:47 AM, Bartłomiej Frydrych wrote:
hello,
I have 2 questions about radiant:
First:
I have layout with sth like this:
I make a Page and I want to put in body-left for example: Hello word!
and to body-right: Hello Hello?
how do this? becouse if I write sth it appears
On May 12, 2008, at 8:48 AM, Bartłomiej Frydrych wrote:
ok, I will put sth like this to Layout:
and sth like this to Page for example index
h2. Hello word!
h2. Hello Frycu!
and it doesn't work;/ what is wrong? or I don't understan this...
Do those parts exist?
If you are not famil
I haven't been following this thread, but according to my tasks gem
should be plural
rake radiant:freeze:gems
Does that work?
On May 12, 2008, at 10:40 AM, Jared Blitzstein wrote:
I just got this issue again but locally this time when I'm trying to
run mongrel (it's the first time I've tri
I'm curious about why r:meta was implemented. Couldn't you get the
same result by using page parts and dropping them in the appropriate
place in your layout?
I haven't used r:meta yet, so perhaps I'm unaware of some particular
benefit
-Jim
On May 19, 2008, at 11:47 AM, Sean Cribbs wrote:
hat I want the tags. The nice thing is that you can use
the inherit="true" parameter.
On Mon, May 19, 2008 at 11:52 AM, Jim Gay <[EMAIL PROTECTED]>
wrote:
I'm curious about why r:meta was implemented. Couldn't you get the
same
result by using page parts and drop
I haven't had time to work on this myself, but I was thinking about
the interface and I'm curious to hear how the community expects this
to work.
Once a site is up and running, I would expect that people would want
to use drafts in 2 different ways.
1) each page has a draft. Any and all ass
face is the whole page, including its
parts; parts are not edited independently. How do you envision this
working?
Sean
Jim Gay wrote:
I haven't had time to work on this myself, but I was thinking about
the interface and I'm curious to hear how the community expects
this to w
Did you type that correctly?
You're going from 0.7.12 to 0.7.10? (I'm not a user of this extension)
if you've already cloned the git repository for the extension, cd into
that directory:
cd vendor/extensions/gallery
and do 'git pull'
On Jun 9, 2008, at 8:55 PM, Ben Morrow wrote:
I know th
I'm experimenting with an idea for help documentation as an extension.
It obviously shouldn't cover getting up and runnining since you'd only
see it once you are running.
I was going to wait until this was more complete until throwing it out
there to the entire community, but since there's
Try Jing
http://www.jingproject.com/
I'm not sure if it will work for this purpose, but I've used it to
create short demos for various projects.
On Jun 10, 2008, at 11:35 PM, Sean Cribbs wrote:
Mohit,
I liked CamStudio on Windows, but I don't know if it's easily
available anymore.
Sean
I really like the idea of extension writers being able to extend the
help system (Section #1) -- say adding documentation for their tags
or explaining how to use their UI elements, or adding context
sensitive help to their UI elements. Then you could crank out a PDF
and have it be a comple
On Jun 11, 2008, at 8:40 PM, Mohit Sindhwani wrote:
2. radiant internal method for extension developers to be able to
create documentation for their parts [Sean]
I think Sean will clarify too, but radiant-help currently allows you
to create documentation to display in the admin interface abo
I want to add regions into the interface for radiant-help.
Is this possible? If so, can I get some pointers on how to go about
that?
-Jim
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:
ets.
5) Modify your views to provide the regions and default partials.
Looking at the included view templates should help.
Sean
Chris Parrish wrote:
Jim Gay wrote:
I want to add regions into the interface for radiant-help.
Is this possible? If so, can I get some pointers on how to go
On Jun 13, 2008, at 12:06 AM, [EMAIL PROTECTED] wrote:
Hey guys,
I am trying to figure out how to add a sign up page for a newsletter
my
client want to send out. I am not worried about the newsletter part,
yet, but I cannot for the life of me figure out which extension I need
to use to build
What was the fix for SnS?
I saw the same problem with RBAC Base on a clean install (which I must
not have tried when we created it) and haven't had time to look into it.
-Jim
On Jun 15, 2008, at 9:19 AM, Chris Parrish wrote:
For anyone (now or in the future) following this thread, I've
ide
Yes, you can add migrations.
No special Radiant way to do it as far as I know
Yes, it will cause problems. That may change depending on what is done
when Radiant moves to Ralis 2.1 and if it can handle the time-stamped
migrations. I'm no git expert, but you should be able to manage the
probl
You'd need to write a tag that wraps it.
tag 'myext:model:if_something' do |tag|
tag.expand if (your code to check that value)
end
that would expand the tag only if that something is set the way you
want, and your radius/html would look like this:
h1. Some Header
There are probably
.html.haml (not sure how to get this to work)
I'm not quite sure how to get that working. Can this be done or does
my structure need to be flattened?
Thanks
-Jim
On Jun 13, 2008, at 12:06 AM, Jim Gay wrote:
That was a big help Sean. Thanks.
I have the basics started with editable r
On Jun 17, 2008, at 8:16 PM, nn wrote:
Hi Jim,
Thanks for the reply.
On Tue, Jun 17, 2008 at 1:18 PM, Jim Gay <[EMAIL PROTECTED]> wrote:
You'd need to write a tag that wraps it.
tag 'myext:model:if_something' do |tag|
tag.expand if (your code to check that value)
end
+1
On Jun 23, 2008, at 1:29 PM, Alex Wayne wrote:
I sent a pull request to the GitHub "radiant" user, but I'm not sure
that goes anywhere just yet.
I have whipped up a quick and simple patch to allow you set a default
filter for pages. On a freshly bootsrapped intance, you will see a
new
v
What would be the way to fix this for extension developers?
On Jun 25, 2008, at 1:59 PM, Alex Wayne wrote:
You should be able to install it now without a problem. That
extension, apparently, depends on some database table being present
when your radiant instance boots up. Running rake db:b
I'm trying to use the radiant-settings extension and having a problem
in MySQL 5.0.27:
ActiveRecord::StatementInvalid (Mysql::Error: You have an error in
your SQL syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near 'key' at line 1:
SELECT
I don't know enough about the extension loading code to provide
insight, but Radiant.bootstrapped? seems like a good idea to me.
-Jim
On Jun 25, 2008, at 3:12 PM, Sean Cribbs wrote:
With the other recent problem related to bootstrapping, I'm
considering adding a method: Radiant.bootstrapped?
I think it should allow a "group" or "size" option.
would apply to the first 3. Working with more
than just one would be useful.
I would want to have these tags with that option:
if_first / unless_first
if_last / unless_last
I'm not sure about the name of the parameter though. Perhaps
in snippet
"
class="">
I had also implemented a modified tag to make the
first part easier so you could just do:
in page
Ok, so that's a long explanation. I'm happy to resurrect the
extension
I saw an error like this when trying to upgrade an app from rails
1.2.6 to rails 2.0 and it had to do (in my case) with any method that
used url_options_for (if I recall the name of the method correctly).
I don't know if that helps, but do you have some setup where a
different version of rail
On Jun 27, 2008, at 10:26 PM, john muhl wrote:
I've patched the default Markdown extension so it uses RDiscount
instead of BlueCloth. The point was to improve the accuracy of
Radiant's Markdown conversion; for an added bonus it's also really
fast. Although the difference in speed diminishes
On Jun 28, 2008, at 2:35 PM, john muhl wrote:
On 2008/06/27, at 21:02, Jim Gay wrote:
On Jun 27, 2008, at 10:26 PM, john muhl wrote:
I've patched the default Markdown extension
Looks nice. I've been frustrated by strange parsing bugs, but never
looked into it. A mor
On Jul 2, 2008, at 10:27 PM, Tim Gossett wrote:
On Sun, Jun 22, 2008 at 3:06 AM, Alex Wayne <[EMAIL PROTECTED]
>
wrote:
I whipped up a quick extension today that some might find useful. I
searched around a little and didn't come with any solutions that I
was
happy with, form a functional
On Jul 5, 2008, at 11:13 AM, Tim Gossett wrote:
I added a tag to the settings extension so that you can use name="admin.title" /> and in
layouts.
Get it at http://github.com/MrGossett/radiant-settings/tree/master
I added these comments on github, but for the benefit of anyone
intereste
I've been working on ideas for a help system for Radiant and have
tagged version 1 of Help on github:
http://github.com/saturnflyer/radiant-help/commits/v1
You can easily create help information for extensions by providing
files with the appropriate information, or by injecting partials into
On Jul 6, 2008, at 4:31 PM, Tim Gossett wrote:
Sounds interesting, Jim. Have screenshots of help in action?
Nope, but don't be mislead; it provides help information in a separate
tab, not within the Radiant page editing interface (for example) but
that's something I'm thinking about for th
Is there any interest in adding the inherit attribute to the
if_content tag?
In some instances I'll find the need to output something like
But I don't have a way to conditionally render the
bit.
If the parent or current page has an "extras" part, then it will
appear, but if it doesn't
server no useful purpose. I'd love it.
On 7-Jul-08, at 12:56 PM, Jim Gay wrote:
Is there any interest in adding the inherit attribute to the
if_content tag?
In some instances I'll find the need to output something like
But I don't have a way to conditionally render the id
would not
behave as you'd expect:
part="this" inherit="true" />>
Adam
On 7-Jul-08, at 5:29 PM, Jim Gay wrote:
I'm working on this feature, but one of the main reasons I put this
out to the list for feedback is that it can become confusing, so I
wanted to se
Sean, what do you think?
I think either
#this being the default
Or I'm thinking that inclusive="true" might be good since we've got
mostly true/false for extra attributes on r:content
[inclusive="true|false"]>
inclusive="true" being the default (meaning AND)
Would either of those be
On Jul 8, 2008, at 2:11 PM, Tim Gossett wrote:
On Tue, Jul 8, 2008 at 12:16 PM, Jim Gay <[EMAIL PROTECTED]> wrote:
#this being the
default
Or
#this being the default
When I see "collect," I expect an array to be returned. I think
"find" is
the way to go.
On Jul 8, 2008, at 2:27 PM, Sean Cribbs wrote:
Or I'm thinking that inclusive="true" might be good since we've got
mostly true/false for extra attributes on r:content
[contextual="true|false"] />
inclusive="true" being the default (meaning AND)
Would either of those be clear to everyone?
On Jul 8, 2008, at 2:43 PM, Tim Gossett wrote:
On Tue, Jul 8, 2008 at 2:27 PM, Sean Cribbs <[EMAIL PROTECTED]>
wrote:
Or I'm thinking that inclusive="true" might be good since we've
got mostly
true/false for extra attributes on r:content
[inclusive="true|false"]>
inclusive="true" being t
On Jul 8, 2008, at 8:16 PM, Chris Parrish wrote:
Since the all / find / require_all / inclusive attribute is both
required and boolean (yeah I know XOR's been mentioned but I'm not
going there), why not try to include that condition in the rest of
it somehow?
(notice that the name "part
On Jul 8, 2008, at 9:08 PM, Chris Parrish wrote:
Jim Gay wrote:
On Jul 8, 2008, at 8:16 PM, Chris Parrish wrote:
Since the all / find / require_all / inclusive attribute is both
required and boolean (yeah I know XOR's been mentioned but I'm not
going there), why not try to in
On Jul 9, 2008, at 3:54 PM, Chris Parrish wrote:
Actually, I've been working towards it (and the SnS renaming -- kind
of wish you'd told me that you were working on it).
Anybody have any good Windows references for Git. I currently
develop with RadRails and really like the SVN integration
I ended up going with find="any | all" because it just made more sense
when applied to unless_content.
My additions are here:
http://github.com/saturnflyer/radiant/tree
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms
This is a bug in 0.6.7 that occurs when run in development mode. If
you run it in production mode it will go away, or if you freeze to the
edge that should also take care of it.
On Jul 14, 2008, at 7:00 AM, Josh Schairbaum wrote:
I've just installed the Comments Extension into a new Radiant
I was working to move my page based stylesheets into the
styles_n_scripts extension when I ran into a problem.
I'd love to see 2 features of doing stylesheets in pages:
1) support for radius tags from pages
2) page parts (or something like it)
I have one client that is managing the design of t
On Jul 15, 2008, at 12:17 AM, Chris Parrish wrote:
You can solve item #2 using and multiple stylesheet
files. Just like you can use the to reference
multiple libraries and create a one-script-to-rule-them-all master
to just serve up one library file, you can also incorporate many
styl
On Jul 15, 2008, at 12:56 AM, Chris Parrish wrote:
Ok, item #1. Unfortunately, this is hairier than you'd think:
1. Pages have an entirely different context than stylesheets and
their tags don't exactly snap in (what exactly is the parent of a
stylesheet? the slug?) Basically, I'd h
Heads up! Help is moving:
http://github.com/saturnflyer/radiant-help-extension/tree
It was formerly named radiant-help but the convention seems to be to
include '-extension' on github. Help will now fall in line with others
and you can use it with extensions like Ray: http://github.com/johnm
:content tag.
2) allow a list of parts to find such as
3) add a find="any" or find="all" to change the condition when listing
multiple parts
On Jul 10, 2008, at 3:05 PM, Jim Gay wrote:
I ended up going with find="any | all" because it just made more
sense when appli
Awesome. I didn't want to assume that you'd have time, so I thought
some +1s from the list would show support.
Thanks.
On Jul 15, 2008, at 2:03 PM, Sean Cribbs wrote:
Jim,
I'm working on the core this week so I'll pull in those changes.
Sean
Jim Gay wrote:
I'm eag
I've been thinking I'd try to tackle it, but I'm swamped and I'd love
to see it started.
On Jul 16, 2008, at 1:47 PM, Chris Parrish wrote:
Ok, that's twice in one week (Jim Gay just asked for the same
thing). I don't think this tag belongs in SnS since it dep
On Jul 17, 2008, at 7:41 AM, Tim Gossett wrote:
On Thu, Jul 17, 2008 at 1:06 AM, Christopher Dwan <[EMAIL PROTECTED]
>
wrote:
Hi folks,
I see all this excitement about GitHub. It's great that everyone
can throw
in their 2¢. It's like stepping on the gas. Now how about that
steering
whe
On Jul 17, 2008, at 1:32 PM, Oli Studholme wrote:
I’m happy to flesh out the tag documentation and add examples, but
someone else will need to write the script to automatically generate/
update wiki pages using the available tags text. If such a script is
impractical I’ll start doing it manu
I couldn't think of a better title for this message
We're excited about a new site we just released that was built on
Radiant (and Help, Page Attachments, Mailer, Settings, Tags and Styles
n Scripts)
http://www.brightyellowjacket.com/
If you're in the Charlotte area and need a creative
On Jul 17, 2008, at 3:56 PM, Tim Gossett wrote:
On Thu, Jul 17, 2008 at 2:59 PM, Jim Gay <[EMAIL PROTECTED]> wrote:
I couldn't think of a better title for this message
We're excited about a new site we just released that was built on
Radiant
(and Help, Page Att
On Jul 18, 2008, at 4:24 AM, Andrew Neil wrote:
Nice site. I like the design of the navigation.
One (very) small crit: I noticed that the links in the body copy
still have the default :link/:visited blue/purple colour scheme.
e.g. check out:
http://www.brightyellowjacket.com/services/capab
On Jul 21, 2008, at 8:01 AM, John W. Long wrote:
For now I think it is appropriate to drop support for IE6. We can
certainly accept a patch back to add it in latter, but I think it is
more important to get the new interface implemented than to quibble
over the details.
Thanks for being w
On Jul 17, 2008, at 1:52 PM, Jim Gay wrote:
On Jul 17, 2008, at 1:32 PM, Oli Studholme wrote:
Im happy to flesh out the tag documentation and add examples, but
someone else will need to write the script to automatically
generate/update wiki pages using the available tags text. If such a
On Jul 21, 2008, at 10:38 AM, Chris Parrish wrote:
Time permitting, I'll have it up by Wednesday.
Great! Send a message when you do, I'm eager to help.
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-li
I haven't experienced this, but run the same task with --trace
rake development db:migrate:extensions --trace
and see what it tells you
On Jul 18, 2008, at 9:18 PM, Andrew Gehring wrote:
After installing SnS, whenever I try to do a db:migrate (for other
extensions), I get:
rake development d
use the Newsletter extension, but I wasn't sure how to
configure the
server to send mail from our GMail.
Shameless plug: If you are planning to be in Edinburgh this
August, be
sure
to check out the West Port Book Festival. Events are all free!
Cheers,
D
On Jul 22, 2008, at 8:43 AM, Andrew Neil wrote:
I was under the impression that if a page has a publishing date set
in the
future, it would only become visible on the site from that date
onwards. Now
that you mention it, I'm not sure if this is true in Radiant,
although it is
the case with a
Yes. I have seen this, and I'm not sure why it happens (but I haven't
tried to find the cause either)
http://groups.google.com/group/radiantcms-dev/browse_thread/thread/f8b1cb2fd2cf2e68/f72e7fe237db648f?lnk=gst&q=%22not+installed%22#f72e7fe237db648f
I can verify that this happens for me in prod
Jul 23, 2008, at 2:45 PM, Jim Gay wrote:
Yes. I have seen this, and I'm not sure why it happens (but I
haven't tried to find the cause either)
http://groups.google.com/group/radiantcms-dev/browse_thread/thread/f8b1cb2fd2cf2e68/f72e7fe237db648f?lnk=gst&q=%22not+installed%22#f72e7
r/index.jsp) so
continued development will be geared toward that, but I'm happy to add
other features if requested.
Start kicking the tires at
http://github.com/saturnflyer/radiant-header_authorize-extension/tree/master
Jim Gay
http:/
ent?
http://feeds.feedburner.com/~r/RubyInside/~3/342732232/redcloth-4-
released-962.html
Apart from dropping of Markdown support (does radiant use it?), it
could be interesting to update it.
Jim Gay
http://www.saturnflyer.com
___
Radiant mailing list
Post:
There was a minor error in a feature added to 0.6.8
If you had a database with pages that referenced page types that no
longer existed, you would have received errors about undefined
constants. 0.6.8 tried to address this by only loading that class if
the class was defined. This is a great w
On Jul 29, 2008, at 10:29 AM, Dan and Norine Simpson wrote:
As for Dan and Norine Simpson's message about needing to specify the
directory for a new instance, I don't recall ever not needing to do
that.
The rails command has the same requirement. But perhaps I'm
misunderstanding
something
t;More" under the
title), and helps to get rid of that disorienting feeling.
http://github.com/saturnflyer/radiant-admin_breadcrumbs-extension/tree/master
If you're running an older version of Radiant, you'll need Shards
install
** Execute radiant:update:javascripts
** Invoke radiant:update:configs (first_time)
** Execute radiant:update:configs
rake aborted!
undefined local variable or method `app_name' for main:Object
(erb):42
Again, my apologies for the low-level nature of this questio
Oli and Casper,
I would love some assistance getting Radiant on Rails 2.1
Rails edge has some localization and translation features built in, so
moving to 2.1 would get us there faster (I hope).
If you'd like to help, please fork my rails_2_1_0 branch and contribute:
http://github.com/saturnf
Oli,
I believe that some of the features you want can be found here
http://github.com/radiant/radiant-page-attachments-extension/tree/master
or http://github.com/kbingman/paperclipped/tree/master
One could start with either of those and add your missing features,
but I don't know of any extens
On Aug 6, 2008, at 6:35 AM, danny q. wrote:
Hi list,
So I've been trying to upgrade from 0.6.7-svn to the 0.6.9 gem using a
Site5 account, and something's blocking me. I am running gems 1.1.0,
ruby 1.8.7
That might be the problem. Radiant is not yet compatible with ruby 1.8.7
http://radiant
, hopefully this thread will help someone down the road.
--Daniel
Jim Gay wrote:
On Aug 6, 2008, at 6:35 AM, danny q. wrote:
Hi list,
So I've been trying to upgrade from 0.6.7-svn to the 0.6.9 gem
using a
Site5 account, and something's blocking me. I am running gems
1.1.0,
nsion that allow users of Radiant to translate inside the
Radiant admin one way or another. That extension could, and should,
use the standardized i18n interface, but the approach and an
appropriate backend will still be up to the extension developer to
select.
Cheers,
Casper
On 02/08/2008
Yes.
Please join in. http://github.com/saturnflyer/radiant/tree/rails_2_1_0
I'll be updating my github wiki with lists of bugs and todos
-Jim
On Aug 7, 2008, at 10:35 AM, Kresimir Saric wrote:
Are there any plans to upgrade Radiant to run on Rails v2.1?
_
I've been meaning to resurrect our RBAC extension for a while now.
This will probably be the impetus for me to add all the features that
have been bouncing around in my head
http://github.com/saturnflyer/radiant-rbac-base-extension/tree/master
It was originally built to allow extension devel
Tom,
Installing the rails gem will have no effect on radiant.
I edited a page on the wiki to include this information:
http://wiki.radiantcms.org/FAQ
I'm sorry to hear that you've had trouble. I don't know that I've read
any of your previous emails to this list, but I've personally been
tr
I just wanted to send out a note about updating the Wiki.
It's community supported documentation, so please be as helpful as
possible.
I was looking at the FAQ page (http://wiki.radiantcms.org/FAQ) and saw
this question listed:
"What on earth are the “Empty”, “Simple Blog” and a “Styled Bl
and
to display or not display parts of your layout.
-Jim
Jim Gay
http://www.saturnflyer.com
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
On Aug 14, 2008, at 10:26 PM, Mohit Sindhwani wrote:
Jim Gay wrote:
Installing the rails gem will have no effect on radiant.
I edited a page on the wiki to include this information:
http://wiki.radiantcms.org/FAQ
Jim, if you get the chance, can you help me verify that the
Prerequisites
add no_login_required to your controller
Some details about it are here
http://wiki.radiantcms.org/Creating_an_extension_VI
http://github.com/radiant/radiant/tree/master/lib/login_system.rb
http://github.com/radiant/radiant/tree/master/spec/lib/login_system_spec.rb#L17
On Aug 15, 2008, at 10:
On Aug 14, 2008, at 11:08 AM, Tim Gossett wrote:
What would be the best way to have edge and stable versions of a
project at
GitHub? Tags? Branches?
The best I can figure is for the master branch to always be stable
(thanks
schacon!) and have a development branch for the edge. Then, when
failing that, im guessing the way would be to unpack radiant and
create my
own custom tag in 'standard_tags.rb' which outputs only what i want
it to
output?
NO!
Well, you *could* do that but it would be more future proof (if you
want to upgrade to a newer Radiant in the future) to just cre
Do you have any extensions installed that alter the page index?
On Aug 18, 2008, at 6:40 AM, Jeffrey Jones wrote:
Hi all,
I recently upgraded to 0.6.9 gem. Ran the migrations and update
scripts. Everything works except the "page" admin page which
displays the following:
Pages
`index_si
On Aug 18, 2008, at 12:54 PM, Gabrio Serbelloni wrote:
Hello.
When installing the database form extension, I get the following
error: http://pastie.org/255037
Any help will be appreciated in solving it.
I'm using the latest radiant version.
Thanks in advance.
Gabrio
It's complaining that your
as any other Radiant extension. Drop it
into your vendor/extensions directory and:
rake radiant:extensions:vapor:migrate
http://github.com/saturnflyer/radiant-vapor-extension/tree/master
Jim Gay
http://www.saturnflyer.com
___
Radiant mailing
t is nice for organization and
comprehension.
But you are right -- it's all just data. In fact, Radiant could
move the slug, breadcrumb -- any field really -- into a page part
and it would still be workable.
my $.02 (though probably overpriced).
-Chris
On May 19, 2008, at 4:02 PM, Jim
Read this
http://wiki.radiantcms.org/Customizations_II
And try this
http://github.com/Squeegy/radiant-settings/tree/master
or
http://github.com/santry/radiant-default-page-parts-extension/tree/master
On Aug 22, 2008, at 3:53 PM, Jordan Isip wrote:
Hi all,
When you create a custom layout, is i
1 - 100 of 375 matches
Mail list logo
