[Radiant] So what doesn't work with 0.7?
N. Turnage
begin to move their sites to v0.7 I thought I would begin the thread.
What extensions are known not to work with v0.7?
_______________________________________________
Radiant mailing list
Post: Rad...@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
john muhl
admin_tree_structure
concurrent_draft
dynamic_grouping
exception_notification
file_based_layout
jargon
legacy_path_handler
link_roll
location
page_attachments_xsendfile
page_event
page_group_rbac_migrator
page_meta
page_review_process
page_versioning
rbac_base
rbac_page_edit
rbac_snippets
reorder
snippet_trees
sns
sns_file_system
sns_minifier
sns_sass_filter
subscriber_lists
tags_multi_site
templates
textile_toolbar
top_level_page
translator
twitter
Mohit Sindhwani
> Since this question is going to be asked a number of times as people
> begin to move their sites to v0.7 I thought I would begin the thread.
> What extensions are known not to work with v0.7?
Could we make this a page on the wiki instead? May I request that
people who have written extensions and have an explicit tag that works
for 0.6.9 and below and a trunk that works on 0.7.0 and later make it
known there?
This will make my job of working through the content for 0.7.0 easier.
If someone needs a template, I can try to create the main page on the
wiki for this.
Thanks
Mohit.
N. Turnage
> N. Turnage wrote:
>> Since this question is going to be asked a number of times as people
>> begin to move their sites to v0.7 I thought I would begin the thread.
>> What extensions are known not to work with v0.7?
> Could we make this a page on the wiki instead? May I request that
> people who have written extensions and have an explicit tag that works
> for 0.6.9 and below and a trunk that works on 0.7.0 and later make it
> known there?
>
> This will make my job of working through the content for 0.7.0
> easier. If someone needs a template, I can try to create the main
> page on the wiki for this.
That's a great idea, Mohit. I would think the following info should be
included:
- name of extension (of course)
- github project url
- latest commit known to be working with 0.6.9 if no tag exists
~Nate
Anton Aylward
> Mohit Sindhwani wrote:
>> N. Turnage wrote:
>>> Since this question is going to be asked a number of times as people
>>> begin to move their sites to v0.7 I thought I would begin the thread.
>>> What extensions are known not to work with v0.7?
>> Could we make this a page on the wiki instead? May I request that
>> people who have written extensions and have an explicit tag that works
>> for 0.6.9 and below and a trunk that works on 0.7.0 and later make it
>> known there?
>>
>> This will make my job of working through the content for 0.7.0
>> easier. If someone needs a template, I can try to create the main
>> page on the wiki for this.
>
> That's a great idea, Mohit. I would think the following info should be
> included:
>
> - name of extension (of course)
> - github project url
> - latest commit known to be working with 0.6.9 if no tag exists
And that Wiki page should have a few lies for those of us who are not
git-gurus on how to use - aka download from - one tag or the other.
Thanks.
A git-diot.
Philip Hallstrom
>> N. Turnage wrote:
>>> Since this question is going to be asked a number of times as
>>> people begin to move their sites to v0.7 I thought I would begin
>>> the thread. What extensions are known not to work with v0.7?
>> Could we make this a page on the wiki instead? May I request that
>> people who have written extensions and have an explicit tag that
>> works for 0.6.9 and below and a trunk that works on 0.7.0 and later
>> make it known there?
>>
>> This will make my job of working through the content for 0.7.0
>> easier. If someone needs a template, I can try to create the main
>> page on the wiki for this.
>
> That's a great idea, Mohit. I would think the following info should
> be included:
>
> - name of extension (of course)
> - github project url
> - latest commit known to be working with 0.6.9 if no tag exists
Why not make the field available on ext.radiantcms.org? When you edit
an extension it asks for the highest version the extension works
with. But I don't see that info displayed on the listing/detail page
itself. Just the edit form. That page already lists the github url...
-philip
N. Turnage
> Why not make the field available on ext.radiantcms.org? When you edit
> an extension it asks for the highest version the extension works
> with. But I don't see that info displayed on the listing/detail page
> itself. Just the edit form. That page already lists the github url...
That's a great idea. Now we just need all the creators of the extensions
on the list to update their extension info. ;^)
~Nate
Philip Hallstrom
>> Why not make the field available on ext.radiantcms.org? When you
>> edit an extension it asks for the highest version the extension
>> works with. But I don't see that info displayed on the listing/
>> detail page itself. Just the edit form. That page already lists
>> the github url...
>
> That's a great idea. Now we just need all the creators of the
> extensions on the list to update their extension info. ;^)
Heh. Good point. Although in this case if a several trusted folks
confirm it works or doesn't work I don't see much difference b/n
publishing a wiki page and sending a data file of name:version pairs
to someone who could update the extension database directly...
Maybe at some point when a new version is released an email should go
out to all the authors listed in ext.radiantcms.org?
-p
Adam Farnsworth
the mailer extension? I'm not understanding at all how this extension
works, and the two tutorials/instructions I found on the subject are
very vague:
I gathered this list by using these two instructions:
http://wiki.radiantcms.org/How_To_Use_The_Mailer_Extension
http://github.com/radiant/radiant-mailer-extension/tree/master
- You start out by git cloning the extension into the extension folder
at /vendor/extensions/
- You either do this step now, or at the end of the tutorial. Which
ever one, you remove code in the environment.rb (located in the config
folder) file to make this:
config.frameworks -= [ :action_mailer ] or this: config.frameworks -=
[ :action_web_service, :action_mailer ]
say this:
config.frameworks -= [] or this: config.frameworks -=
[ :action_web_service ]
depending on whether or not the :action_web_service is being ignored
or not.
- You then possibly, or possibly not, add this code to the
environment.rb file, but after a line that doesn't seem to exist
(require "status"):
ActionMailer::Base.smtp_settings = {
:address => "your.smtp.server",
:port => 25,
:domain => "your.domain"
}
obviously changing the setting to match your own.
- Restart your server.
- You then create two new pages, under whatever previous page you'd
prefer, one named "email" the other "email_html" in that file you put
the following code:
subject: From the website of Whatever
from: nor...@example.com
redirect_to: /contact/thank-you
recipients:
- o...@one.com
- t...@two.com
- You then build your contact form with these tags:
<r:mailer:form name=""> ... </r:mailer:form>
<r:mailer:text name="" />
<r:mailer:checkbox name="" />
<r:mailer:radio name="" />
<r:mailer:radiogroup name=""> ... </r:mailer:radiogroup>
<r:mailer:select name=""> ... </r:mailer:select>
<r:mailer:date_select name=""/>
<r:mailer:textarea name=""> ... </r:mailer:textarea>
<r:mailer:option name="" />
to make something that looks something like this:
<r:mailer:form>
<r:mailer:hidden name="subject" value="Email from my Radiant site!" /
> <br/>
Name:<br/>
<r:mailer:text name="name" /> <br/>
Message:<br/>
<r:mailer:textarea name="message" /> <br/>
<input type="submit" value="Send" />
</r:mailer:form>
If someone who has gotten the extension to work please let me know
where I went wrong, it would be very helpful. By doing everything
above I get the following error in a browser:
Mailer config is not valid (see Mailer.valid_config?)
Thanks,
Adam
Mohit Sindhwani
> And that Wiki page should have a few lies for those of us who are not
> git-gurus on how to use - aka download from - one tag or the other.
>
If you're on Windows, you could take a look at:
http://wiki.radiantcms.org/JustEnoughGitOnWindows
It was compiled by another Git-Idiot (i.e. me)
Cheers,
Mohit.
2/11/2009 | 1:19 PM.
Sean Cribbs
Two things. First of all, put the configuration in the 'mailer' part
(tab) on the page that has the form. Second, make sure your indentation
in the recipients list is two spaces; YAML is picky about that.
Sean
Ollivier Robert
> roughly...
>
> admin_tree_structure
...
> reorder
...
What about the radiant-gallery one?
I use reorder and would have difficulties going back w/o it so I'll
stay at 0.6.9 till it is updated.
--
Ollivier Robert -
Steven Southard
problems. Just replacing the comments files in vendor/extensions and
running rake radiant:extensions:comments:update and rake
radiant:extensions:comments:migrate kind of left me somewhere between
the two versions.
Any suggestions to clean this up?
Steven
Steven Southard
Steven
Steven Southard
uninitialized constant CommentTags::Locale. Has anyone else seen
this or know what causes it?
Steven Southard
and got a version that was six months old. I used git clone and
got the current version.
Mohit Sindhwani
> Problem solved. I had used download here
> http://github.com/jomz/radiant-comments/tree/master and got a version
> that was six months old. I used git clone and got the current version.
Could you do us a favour? Could you see if your experience deviates
from the entry in the wiki about 'blogs' (there's a brief description
about Comments) and could you update it please? I've been meaning to
split that article to separate out the part relating to comments but
have not yet been able to.
The URL is: http://wiki.radiantcms.org/Using_Radiant_as_a_Blog
Thanks
Mohit.