Re: [Radiant] Rails 2.3 Templates WAS: Radiant 0.8.0 Asterism Release
Adam van den hoven wrote: I'm wondering if: 1. anyone else sees value in pursuing templates as a generalized mechanism to more easily bootstrap radiant sites (ala radiant -t http://www.example.com/my_cool_theme.rad NewSite) or installing and uninstalling extensions I think that would be awesome. It would be nice to set up a site template with all the extensions I use on a regular basis. 2. anyone is already working on it... I'm rather busy on other fronts these days, so if someone is already thinking about it, I'd rather collaborate than start from scratch. Likewise, I have little time to breathe, let alone start another project. But if it was started, I would certainly do what I can to help further it along. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Newsletter extension
Mauricio Dulce wrote: you know any extension compatible with 0.7x, which serves to collect email addresses (newsletter) I found only one, but this is not compatible with version 0.5 if not can someone help me Use Mailer for your form and Database_Mailer to collect those submissions. ~N ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Newsletter extension
Mauricio Dulce wrote: I have run mailer _extension, i can't install other extension whit the same name or this is possible You have to have Mailer extension installed first, then Database_Mailer. D_M was made to work with Mailer. ~N ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Problems getting Reorder extension migrated
I tried using Ray to install the reorder extension and it was getting errors on the migration. So I reenabled it, checked out tag 0.7.1, tried to migrate it myself and I am getting this from the trace: http://pastie.org/507927 It can't find a controller because a controller doesn't exist. I have installed reorder a number of times before and never ran into this kind of thing. Anybody have any ideas? ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Problems getting Reorder extension migrated
N. Turnage wrote: I tried using Ray to install the reorder extension and it was getting errors on the migration. So I reenabled it, checked out tag 0.7.1, tried to migrate it myself and I am getting this from the trace: http://pastie.org/507927 It can't find a controller because a controller doesn't exist. I have installed reorder a number of times before and never ran into this kind of thing. Anybody have any ideas? My bad. I had checked out the right tag but then init'ed and updated the submodule. No wonder it didn't work it was reactivating master before I migrated. Nothing more to see here. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Is there an if-else tag in Radiant?
What I would like to do is specify a default part of a page that would have a default banner, but I would like to override that on some of my pages. It would be great if something like this worked: r:if_content part=topBanner r:content part=topBanner / r:else_content img src=/images/banner.jpg / /r:else_content /r:if_content Is there any extension that would work relatively like this? ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Request to all extension writers/maintainers
With the imminent release of 0.8 I would like to request that when anyone is updating their extensions to work with the new version of Radiant that they tag the latest latest version that works with 0.7 as 0.7 and that the first update for 0.8 is tagged 0.8 as well. This will help in deciphering which versions of an extension works with 0.7 and will make it easier to identify which extensions have been updated for 0.8. Thanks, ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Paperclipped extension and new pages
Steven Southard wrote: I think it's just the way it works. If the page doesn't exist yet it could be problematic to associate an asset with it. Save and continue and assets are fully functional. I agree. The page needs an id before attachments can be assigned to it. Press 'Save and Continue' and you're golden. ~N ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Problem installing tags extension
Rafael Souza wrote: I am getting this when do 'rake radiant:extensions:tags:install': ** Invoke radiant:extensions:tags:install (first_time) ** Invoke environment (first_time) ** Execute environment rake aborted! uninitialized constant ApplicationController I have already copied the has_many_polymorphs for plugins dir. Someone knows what is happening? Run the task with '--trace' and paste the output to a pastie (pastie.org). I ran into this before, but it'll take the full trace for my hamsters to get moving on it. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] How can I use Mailer form on every page?
Hey guys, I have built a contact form with Mailer and I would like to use it in my template so that it is at the bottom of every page. It is working on the contact page itself, but on any other page I get the Mailer config is not valid error. The ReadMe for Mailer says that you can use it in a snippet, but doesn't mention the syntax to do that. Right now I have this set up in a snippet that is at the bottom of my template: div id=contact r:find url=/contact/ r:content / /r:find /div The form is defined in the body of the /contact page (obviously). How can I use this in my template on pages other than /contact? Thanks. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How can I use Mailer form on every page?
Mohit Sindhwani wrote: N. Turnage wrote: Hey guys, I have built a contact form with Mailer and I would like to use it in my template so that it is at the bottom of every page. It is working on the contact page itself, but on any other page I get the Mailer config is not valid error. The ReadMe for Mailer says that you can use it in a snippet, but doesn't mention the syntax to do that. Right now I have this set up in a snippet that is at the bottom of my template: div id=contact r:find url=/contact/ r:content / /r:find /div not sure how the extension works, but can't you use it in a snippet and then use the snippet from the layout? I though so, and I'm curious how to make that happen. I just looked at its readme and it says: You configure the recipients and other Mailer settings in a mailer part The form and it's config are set up properly. On the /contact page everything works perfectly. But on other pages it doesn't. Just a suggestion: 1. You may be able to use: from_field: my_form_field_that_contains_the_from_email_address with a snippet that has the mailer form. This won't help. This is just to set the From field to the address of the user submitting the form. 2. It seems that you mailer may be failing because you don't have a mailer part. It may be that with your current code, you also need the mailer part on your pages. Yeah, it's set up properly. This isn't the issue... Wait a minute, does this mean that even if the form is in a snippet, each page (every page for me) needs a mailer and an email part to allow for processing the form? If so, is there a way of creating a page part in my template so that I don't have to add mailer and email parts to every page? So I can do something like this: r:part:new name=mailer r:find url=/contact r:content part=mailer / /r:find /r:part:new Good luck. On a side note, I noticed this: Caveats Relative urls will almost certainly not work if the mailer fails validation. Solution? Only use absolute urls. How would that affect me here? ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How can I use Mailer form on every page?
Cristi Duma wrote: I did this on a site some time ago. It was an older version of radiant and mailer extension but it should work for you. I created a snippet which I used then on every page. The trick is to post the contact form to a page that has mailer part. Like this form class=mailer-form method=post action=/newsletter/ div input type=hidden value=newsletter name=mailer_name/ /div label for=emailEmail:/label input type=text name=mailer[email] class=required validate-email id=email / input type=submit value=Trimitere/ /form The newsletter page has the mailer part and it works just fine. Contact me if id doesn't work, we'll find a solution :) Cristi PS: or did it work allready? I'm too tired right now to read all the posts.. That looks like it's going to work. I am trying this on a side project, so I can't play with it until this evening though. I'll let ya know. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] At my wit's end with Mailer -- (see Mailer.valid_config?)
I have set up Mailer on 3 different websites and the first two worked
right out of the box, but the third is not working even though it's set
up no different than the others. No matter what I push or pull on, I
still get the (see Mailer.valid_config?) error when I try and view
the 'Contact' page. The content for my page parts is this:
Body:
...
r:mailer:form
/r:mailer:form
...
mailer:
...
subject: Thank you
from: he...@goodtastewithtanji.com
redirect_to: /contact/thank-you/
recipients:
- pixeln...@gmail.com
...
email:
...
This is a message from r:mailer:get name=name /
...
This is my ActionMailer settings from the bottom of the
'config.after_initialize' block:
...
# ActionMailer settings for use by the Mailer extension
ActionMailer::Base.smtp_settings = {
:address = mail.goodtastewithtanji.com,
:domain = goodtastewithtanji.com,
:user_name = hello+goodtastewithtanji.com,
:password = myrealpassword,
:authentication = :login
}
...
And yes I have removed action_mailer from 'config.frameworks -= []'.
Is there anything else I can check or do even if it only means that the
error changes? I have been banging my head on this for the last two
days. I have tried reinstalling the extension (3times), moving things
around in my environment, and nothing works. I don't know what else to
do. Any help/pointer/criticism appreciated.
~Nate
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] At my wit's end with Mailer -- (see Mailer.valid_config?) SOLVED: incompatible with Twitter extension
john muhl wrote: maybe trying putting the subject in quotes, the spaces might be choking it up ... subject: Thank You ... I tried a number of space, no space, quotes, no quotes combinations; I pared my layout down to almost nothing; finally I started disabling extensions and found out that if the Twitter extension was installed, then the Mailer config would throw an error. I don't know why it would throw an error, but it would. So my solution is just to remove the Twitter extension and all is well. Many Bothans died to bring us this information. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] At my wit's end with Mailer -- (see Mailer.valid_config?) SOLVED: incompatible with Twitter extension
Charlie Robbins wrote: Nate, You should thinkg about posting that information to the Wiki of either the Mailer or Twitter extension. This is exactly the type of information that we were discussing at the NYC Radiant Meetup last Thursday. Which Twitter extension in particular did it not work with? I know that there are more than one. I had both the Twitter and Twitter_Tags extensions loaded, but it was the Twitter extension that was causing problems. That's a good idea to post it to the wiki. I have two weeks to hit a major deadline (aren't we all), but after that I'll do it. There are some other nuggets to share that I don't think a lot of people have encountered, and would be good for the wiki. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] At my wit's end with Mailer -- (see Mailer.valid_config?) SOLVED: incompatible with Twitter extension
Jim Gay wrote: On May 25, 2009, at 9:05 PM, N. Turnage wrote: I had both the Twitter and Twitter_Tags extensions loaded, but it was the Twitter extension that was causing problems. That's a good idea to post it to the wiki. I have two weeks to hit a major deadline (aren't we all), but after that I'll do it. There are some other nuggets to share that I don't think a lot of people have encountered, and would be good for the wiki. This is likely due to the fact that the Mailer extension uses the name config to refer to the mailer config, and NOT Radiant::Config as the convention goes. Mailer should *not* use config http://github.com/radiant/radiant-mailer-extension/blob/b661842349b8019d98aac9b50a576541d5f01d13/lib/mailer_process.rb#L12 Because the Twitter extension uses config to refer to Radiant::Config and it is loaded after Mailer, the Mailer config is clobbered. I've not tested this, but it is likely the case. I'm sorry I didn't catch this sooner, Nate. I'll let it slide... this time. You are allowed a mistake now and then. ;^) I am just glad that I discovered which extension was keeping Mailer from working, after two days of grumbling at the computer. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Getting NoMethodError with Templates extension
Sean Cribbs wrote: Nate, I suspect those are installed as submodules. Inside the extension, run this: git submodule init git submodule update I believe Andrew was working on switching it over to use Admin::ResourceController, so make_resourceful wouldn't be needed any more. Watch for those changes. That did the trick. I thought I had done that already. Thanks, Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Page Attachments
Mohit Sindhwani wrote:
Next on my list is PageAttachments - so, I installed attachment_fu
and then, I cloned the recent page_attachments from git. I applied
the migration and did the update and restarted the server.
I was able to add an attachment and then another. But the third one
failed. After trying for a bit, it seems that it loads small files
(tried up to 14KB) but larger files (more than 30KB) seem to be not
loading. Any suggestion on what may be wrong?
I found this in page_attachments\app\models\page_attachment.rb:
has_attachment :storage = :file_system,
:thumbnails = defined?(PAGE_ATTACHMENT_SIZES)
PAGE_ATTACHMENT_SIZES || {:icon = '50x50'},
:max_size = 10.megabytes
This tends to suggest that files up to 10MB should be fine? Any idea
what I should look for? (I'm on Windows, running Radiant 0.7.1 on
ruby 1.8.6)
*bump*
I suggest you drop page_attachments in favor of Paperclipped. It's
easier to manage image sizes and mime-types (you can do both with the
settings extension) and page_attachments will prevent you from using the
change_author extension (I got bitten by this one) if you decide to use
it. It's also much easier to use in day-to-day operations with its
bucket that will allow you to upload and attach images from the same place.
~Nate
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Anyone else having trouble with database_mailer not working with 0.7.1?
I am having trouble getting the emails sent with the mailer extension to be logged by the database_mailer extension. The emails get sent out, but they aren't saved. Does anybody have this working in 0.7.1? If so, could you point me to the site where you have it working properly? Thanks, Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Anyone else having trouble with database_mailer not working with 0.7.1?
Cristi Duma wrote: Hi.. I updated the DB_mailer extension to 0.7.1 a few weeks ago, and it works well for me. Do you get any errors? Did you delete the save_to_database: false line in the mailer page part. I never had the save_to_database: false line in my mailer part. Could I somehow force it to save to the database with save_to_database: true? Did you had the extension working on any version lower than 0.7.1? I never tried it before this. I am reinstalling the mailer and database_mailer extensions from scratch now to see if that helps. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Anyone else having trouble with database_mailer not working with 0.7.1?
Cristi Duma wrote: This is the problem.. that save_to_database: false. There's no need to put it on true, it's true by default, so just delete that line in the mailer part for the email forms you don't want to log in DB_mailer. What I said was that line was never in my mailer part. ~N ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Anyone else having trouble with database_mailer not working with 0.7.1?
Cristi Duma wrote:
oh, I got it the other way around...
well, i'm sure that if you follow the instructions on the blog or the
readme on github it will work.
Everything is working except that the submitted information just isn't
getting into the form_datas table. I just don't know what else to do. I
have reinstalled these extensions 3 times now and while the Mailer
works, the information just isn't getting saved. I don't know which part
of the database_mailer extension intercepts that information, but it's
not working for me.
This is the transaction that's taking place when the form is submitted:
Processing SiteController#show_page (for 70.238.72.121 at 2009-05-21
10:43:14) [POST]
Parameters: {action=show_page, url=[contact],
mailer={church= kljh k, name=lklkjshdglkh, subject=test
email, graduation_year=769876, school=kjh h jh,
email=pixeln...@gmail.com}, controller=site}
Sent mail to emailaddr...@domainname.com
Completed in 0.41906 (2 reqs/sec) | DB: 0.00283 (0%) | 302 Found
[http://test.texasfreshmen.com/contact/]
I don't understand where it is breaking. It worked for me once, and I
cannot get it working again.
~Nate
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] How can I uninstall Database_Mailer extension?
When you migrate the extension into existence, it takes fields from the environment for use in migrations. Like others here I had to migrate it twice to get passed the Mysql::Error: BLOB/TEXT column 'message'... error message. For some reason it just stopped working on my production server after working once (even though mailer didn't send anything out) and now I would like to uninstall it to try reinstalling to see if that helps. Well, this is where the real problem begins. This is a trace of the migration to 0 where I get the undefined method 'set_schema_version' error: http://pastie.org/484724 Can anybody tell me how I can migrate this extension back to 0? Thanks. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How can I uninstall Database_Mailer extension?
Charlie Robbins wrote: rake production radiant:extensions:database_mailer:migrate VERSION=0 that should git 'er done for ya. That's when I get the undefined method `set_schema_version' for #Class:0xb7f7fb4 error. I know how extensions normally work, that's why I asked the process for removing the extension. The way I did it, thought I don't know if it's right, is that I just nuked the table form_datas then removed the two entries for Database_Mailer in the schema_migrations table. It seems to have worked. The database_mailer extension is not like other extensions. It creates a migration from a hash you create in your environment. The migrations try and create an index on every column, I am guessing so that you can sort on each column in the view. That also means that the migrations fail when they hit columns set as :text without a length (just FYI). What I don't understand is how it worked the first time I submitted the form, but after I fixed the problem in my mailer part that was preventing the form from sending out mail, the database_mailer part started failing. I am going to try and remove database_mailer entirely then reinstall it now that mailer is working. ~N ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Templates extension - Two things
I have a but report and a suggestion for the Templates extension. Bug report: When you change a template (parts or structure) in any way the pages that are based on the template don't get updated with the changes. For each page that uses that template must be opened and resaved before any of the changes get implemented. I don't know if this was intentional, but I have 250+ pages that rely on one of my templates. Any change in a template means a long morning of opening and resaving pages. Suggestion: It would be really nice to have a Save and continue editing button on templates like on the other pages in the admin. Thanks, Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Templates extension - Two things
Mohit Sindhwani wrote: N. Turnage wrote: I have a but report and a suggestion for the Templates extension. Bug report: When you change a template (parts or structure) in any way the pages that are based on the template don't get updated with the changes. For each page that uses that template must be opened and resaved before any of the changes get implemented. I don't know if this was intentional, but I have 250+ pages that rely on one of my templates. Any change in a template means a long morning of opening and resaving pages. This is not uncommon. In general, the pages should 'eventually' expire. If you haven't made any changes to Radiant, shouldn't it expire within 5 minutes? To fix this, the following options exist (but you'll need to cut in to the code): * Bring back the 'Clear Cache' button (I have requested this in the past, but it's been deemed unimportant) * Get the extension to clear the cache automatically whenever a template is saved (similar to changing layouts/ snippets). I had never thought it could be a caching issue. As long as it's that, I can just resave one page to check that the changes work, and just wait for all the others to get updated when the cache expires. Thanks, Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Problem with Extensions
Emanuel Vinzent wrote: Hello all, i have a problem with installing Extensions, the error-message Could not load extension from file: drag-order_extension. #NameError: wrong constant name Drag-orderExtension rake aborted! You have a nil object when you didn't expect it! You might have expected an instance of Array. The error occurred while evaluating nil.+ the directory drag_ordner is on vendor/drag-order any ideas? First off, which version of Radiant are you using? And second, you'll want to name your directories for your extensions using underscores ( _ ) instead of dashes ( - ). I have never used that extension, but I would check compatibility with the version of Radiant you are using. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Problem with Extensions
Mohit Sindhwani wrote: Emanuel Vinzent wrote: thank's! with the underscores in the directiories will should be work ;-) With the advent of git, we need a FAQ that explains how to rename extension directories after the extension is cloned to vendor/extensions. I guess there's a clean way to guess the directory name by looking at the _extension.rb in the newly created directory? Examples: * when it's blog_tags_extension.rb - the directory should be blog_tags; * similarly, it's page_attachments when the file is called page_attachments_extension.rb * and simply enough, gallery when the file is gallery_extension.rb This should be foolproof, isn't it? Are there any known extensions that tend to use CamelCase (guess not!) or dashed-names (theoretically possible, but I haven't seen any). Or you could just use Ray to install extensions. If you manage your project with git, this is super easy to use. And if it, for some reason, can't install an extension, there is always git submodule add. Ray is now the first extension I add to a project. The only extension that throws me for a loop when I install it is the radiant-extensions-extension. Try searching for that one in github. Searching radiant extension returns all of them. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Templates Extension: Important Update
Andrew vonderLuft wrote: To anyone using Templates extension with Radiant 0.7 or greater: We discovered an issue today which could cause the creation of a child page with a nil parent_id. The scenario is when you create a new child page with a given template, and then change the template before the initial save. In this case the parent_id is lost. We corrected this by updating the switch_templates partial to conform to RESTful routes. So if you are using Template Extension with Radiant 0.7, be sure to pull from master. I am having problems trying to upgrade the templates extension. I upgraded from commit 0f3043d to commit a0b19b2 so I already had migration 009. When I migrated 010 this was the error: http://pastie.org/478375 How can I migrate the db to 010 without having to go back to 008 and migrate up? ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Templates Extension: Important Update
Andrew vonderLuft wrote: I would try this: $ rake radiant:extensions:templates:migrate VERSION=8 $ rake radiant:extensions:templates:migrate This will roll you back to migration 8, and then re-migrate 9 and 10. migration 9 will create the boolean part_type which you appear to be missing. Won't that destroy the data the templates I already have set up? And will the pages based on those templates be affected? ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Is there an extension for rotating or random images?
I could have sworn that I had seen an extension that would either load a random image or rotate images banner-style, but I cannot find it. I need to to be able to set a random background image for a div each time the page is loaded/re-loaded. Does anybody know what I am talking about? I thought I had seen an extension that would do this one time, but with the serious lack of sleep I am experiencing I cannot find it. Thanks, ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Is there an extension for rotating or random images?
Joel Oliveira wrote: I know I'll come off as the guy who turns to the javascript hammer every time he needs a tool to fix a problem -BUT, that'd be a 3 or 4 line implementation with some JS. Or is that out of the question for your purposes? I thought there was something more Radiant specific. Maybe it was the banner rotator that I was thinking of, but I don't think I that will work for what I am trying to do. In an ideal world, what I want to do would be this: The css background-image property of a div would use a random image from a directory of images that have completely random names. The client I am building a site for has a Phanfare feed, and I would like to use their images as backgrounds. I was thinking about setting up a cron job to pull images from their feed into a directory on the web server, then randomly choose an image from that directory. Every javascript solution I have seen requires that the images be named samename_#.jpg and and a random number is chosen and added into the filename. That is probably something I can achieve with the radiant random number generator and a stylesheet. I was looking for a more automated solution. Do you know of any javascripts or jQuery scripts that would allow for non-uniform file names? ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Is there an extension for rotating or random images?
Sean Cribbs wrote: Actually, it sounds like John Muhl's solution will work best for you - you could even keep it tucked away in a snippet. div style=background-image:r:snippet name=banner /.../div That worked like a charm! Thanks, Sean John. I hadn't even thought about using a snippet in an inline style. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Templates Extension: Important Update
Andrew vonderLuft wrote: To anyone using Templates extension with Radiant 0.7 or greater: We discovered an issue today which could cause the creation of a child page with a nil parent_id. The scenario is when you create a new child page with a given template, and then change the template before the initial save. In this case the parent_id is lost. We corrected this by updating the switch_templates partial to conform to RESTful routes. So if you are using Template Extension with Radiant 0.7, be sure to pull from master. Thanks for fixing this. I had run into it a couple of times, but could never figure out how to reproduce the error 'reliably'. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Major error with Google_Maps extension
Wherever I have placed a map on a page, I get this error:
*undefined method `attr' for {name=markerInfo}:Hash*
It doesn't matter what I put in the marker text box on a map marker, it
always gives me this error. This happened when I updated the google_maps
extension. I am guessing the cac6eba commit is what did it.
Pastie with trace:
http://pastie.org/474979
~Nate
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] 500 Internal server errors with Radiant 0.7.1 and SNS
Rafael Souza wrote: I was with the same problem with sns (the main project) and the solution was install the fork of netzpirat. http://github.com/netzpirat/radiant-sns-extension/tree/master The original project (of SwankInnovations) is good only for radiant 6.9. Hope this works to you too. +1 This is the solution. Use the Netzpirat branch. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Big Thanks for Ray
I just want to thank everyone involved in putting Ray together. It really is amazing. I don't have to install my submodules by hand anymore. You guys rock: * John Muhl * Michael Kessler * Arik Jones * Benny Degezelle ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Nasty SystemStackError when going back to admin/pages
I am running into a very annoying stack level too deep error when I try and go back to the admin page list from any other section of the admin site. I looks like it has something to do with the Paperclipped extension's included version of will_paginate, but I am not sure how what to do about that. I do have the mislav_will_paginate gem installed as well. I have also increased my ulimit to 8192 as mentioned elsewhere when a stack too deep error was encountered in Radiant. The full trace: http://pastie.org/471504 ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RailsConf BoF
Keith Bingman wrote: I am definitely interested in a BoF session. I think Eugene ( who is working on the internationalization and doing the Russian translation) is coming too, so the i18n project would be a great topic. Dang, I'm jealous. There is no way I can get to RailsConf. Anybody coming to the Lone Star Ruby Conf? That's just a short jaunt up I-35. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Recreating thumbnails with page_attachments extension: Is it possible?
Hey all, In my environment file I have added a couple of extra sizes for the page_attachments to size my images to when saving and I was wondering if there is a way to recreate thumbnails of my images in the db like paperclipped does. Anyone know of a way to do this without having to re-add the images? ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] filters on layouts
Mohit Sindhwani wrote: Steven Southard wrote: Why aren't filters available on layouts? That I would like! Have you tried using templates? Since I started using them I don't build a site without templates anymore. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How do I get published date fields back on admin pages?
Michael Kessler wrote: Did you mean the page.edit.published_date? Radiant setting that is mentioned here http://wiki.github.com/radiant/radiant/additional-configuration-options I don't know how I missed that. Normally I just google what I need. I forgot about the new wiki on github. Thanks. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Radiant and regexp
Is there any good reference to the way that Radiant uses regular expressions for page links? For example, this kind of thing: r:if_url matches=^/.+ I don't know how deep /.+ will work, etc. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Git questions regarding submodules... and updating them
Sean Cribbs wrote: Assuming your remote is named origin, it's easy to push your local branch up: git push origin radiant07 That was the missing piece of the puzzle. Thanks. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Git questions regarding submodules... and updating them
Brian Gernhardt wrote: It just so happens that I'm one of the guys working on git. So I'll see what I can do to help you. :-D I don't know how extensive your git experience is, so bear with me if I'm saying things you already know. Thanks. Your info was exactly that little bit I needed to grok this. But I still have a few questions for pushing back to the repo on my server. See below. On Apr 9, 2009, at 2:50 PM, N. Turnage wrote: Submodules are useful, but are also a little bit bleeding edge. They are not widely used, and as such, sometimes have odd problems. If you encounter any serious problems, feel free to poke the git mailing list g...@vger.kernel.org. The list is both for development and users and we try to be friendly to everyone. 6906bb369339fa74674d41b638ad134a70980cc2 vendor/extensions/blog (radiant069-5-g6906bb3) 782918fda1c2b3d5a659f1ea507aaa7c5cb2e410 vendor/extensions/comments (0.6.9-1-g782918f) 07015cd85bca4af44a182775e7979e965f1acc94 vendor/extensions/copy_move (heads/master) b7e64f11037ccd0a0d07eb1a70fc90240ab6ec6e vendor/extensions/page_attachments (0.6.9-4-gb7e64f1) e4bd92f52b35222c1316f5b3c275534b5ad3407d vendor/extensions/search (heads/master) 3302f3f7187b7d22924502e5cca3e57496c262be vendor/extensions/share_layouts (heads/master) e4bc04ebe6eb4f6946131f42248f181dea676439 vendor/extensions/sns (radiant0.6.9-10-ge4bc04e) b99e2cbf3689bd5074517c2a17b6e1ed5e6063b9 vendor/extensions/tags (pre-radiant-0.7-5-gb99e2cb) 743a95be0f01696530f558e7f4934cc7e57d3ab8 vendor/plugins/attachment_fu (743a95b) Why is it displaying this way instead of just telling me which commit I am using? The description is either a branch name or something in the following format: tag-#-gSHA. The tag is the most recent tag that _doesn't_ contain the commit. # is the number of commits between the commit in question and the tag. And SHA is the beginning of the full SHA-1 (usually 6 characters). (This is the result of running `git describe HEAD` in each submodule.) I had to read this a couple of times, but this really helped understand that I am using the latest commits regardless of which commit the tag was/is on. It looks like copy/move, page attachments, and share layouts are all on their master branch while blog, comments, page_attachments, sns, and tags are all a commit of their own. This can happen if the origin repo for them moved ahead of where your submodule has them. If you want, you can (usually) update them by going into the submodule and running `git pull`. Then you can `git add` the submodule and `git commit` in the supermodule to update it's records. I actually went to each of the submodules and ran 'git reset --hard master' . I don't know how right or wrong that is, but it worked. I'm not sure what you were expecting to see, since I don't know the details of your setup. But if this description isn't enough, I'll try to help you get where you need to be. Also, because I cloned my repo, instead of pulling it, how can I get the branch on the server? Right now when I try and git push I get the message that everything it up to date. Any info is appreciated. This is where I am really confused. Cloning should have set up the appropriate tracking information, but would not have set up any push information. You might want to run a command like the following, assuming the clone URL is also something you can push to (i.e. not git:// or http://) git config remote.origin.push refs/heads/*:refs/heads/* Note that pushing to a non-bare repository (one that has a working directory attached to it) isn't recommended, as it will change the respository out from under you. You might want to change the push line to something like refs/heads/*:refs/remotes/home/* and then `git merge home/master` on the server instead. Or set up a bare repository that both sides can clone from. (git --bare clone URL site.git) What I would like is for the local branch I created to become a branch on my server so that I can use Capistrano to deploy from my new branch. I don't really want to merge my changes back into master just in case something goes wrong and I have to go back and deploy from the master. My local branch is called: radiant07 My git push/clone url is: g...@pixelnate.gitrepo.com:pixelnate/goodtaste.git What confuses me is the 'refs/heads/*:refs/heads/*' bit. Could you maybe explain that a little bit? Thanks again for your help, Brian. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Something I noticed about Textile in 0.7.1
Jason Garber wrote: Nate, I didn't really follow you. Can you have another go at it? Sure. It was late when I posted. When I upgraded to 0.7.1 I noticed that I was getting extra line breaks (br) between lines, even though the exact same stylesheet was used and nothing else in the conten had changed. Well as it turned out, the pages with the problems had the Textile filter on and the snippets and page parts added on the pages each had textile turned on. In 0.6.9 this didn't create problems, everything went through it's own filtering process and the html rendered correctly. In 0.7.1, every time a page part or snippet was processed on the page, the Textile filter was invoked and I was getting html with extra line breaks as Textile filter was called multiple times on the same page content. I may be the only person experiencing this, but for me, this excellent. This is exactly how I originally imagined the Textile filter to work. With the filter set on a container page, all the page parts and snippets on it are filtered at the same time. Does that make more sense? Radiant 0.6.9 locked you into using RedCloth 3.0.4 for Textile, which was released in September of 2005. 0.7.1 lets you use RedCloth from gems, so you can get the latest RedCloth—4.1.9 which is much better. It handles HTML or already-rendered Textile (i.e. HTML) much better. I find occasionally I still have to wrap some radius tags in notextile blocks, but it's a big improvement over what we had before. Do you have to do anything special to make this happen? I installed the RedCloth 4 extension to avoid using v3.0.4 that it looks like Radiant uses by default. Are you saying that Radiant should automatically use my gem by default? Maybe something within Radiant changed between 0.6.9 and 0.7.1, but I doubt it. Are you saying it's an overall improvement? Do you have suggestions for additional improvements. I would say that if Radiant uses the gem automatically, then it's perfect. If not, then I am getting the behavior that I wanted by using the RedCloth4 extension. That reminds me, I made a pure-Ruby version of RedCloth a couple months ago and I should submit that to Radiant to be bundled in in place of 3.0.4. That would be great. Have a great weekend! I'm probably offline 'til Tuesday. You too, but I am always online. ;^) ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] 500 Internal server errors with Radiant 0.7.1 and SNS
Sean Cribbs wrote: A while back Chris asked me to fork SnS into the radiant account, which I did, but I haven't had time to fix it. Anyone who writes and submits a good patch or set of patches will get commit bits. I really wish I was that person, but sadly I am not. My skillz don't trend toward that direction. I can whip up a bangin' CSS layout for ya tho. ;^) ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Git questions regarding submodules... and updating them
I've cloned (I think I should have pulled it instead) my main project from my repo, created a branch and have been updating that branch to 0.7.1. My extensions are set up as submodules, and work beautifully, but the tag showing which version of the extensions I am using shows the original tag/commit sha - (dash) the new tag/commit sha. Like this: 6906bb369339fa74674d41b638ad134a70980cc2 vendor/extensions/blog (radiant069-5-g6906bb3) 782918fda1c2b3d5a659f1ea507aaa7c5cb2e410 vendor/extensions/comments (0.6.9-1-g782918f) 07015cd85bca4af44a182775e7979e965f1acc94 vendor/extensions/copy_move (heads/master) b7e64f11037ccd0a0d07eb1a70fc90240ab6ec6e vendor/extensions/page_attachments (0.6.9-4-gb7e64f1) e4bd92f52b35222c1316f5b3c275534b5ad3407d vendor/extensions/search (heads/master) 3302f3f7187b7d22924502e5cca3e57496c262be vendor/extensions/share_layouts (heads/master) e4bc04ebe6eb4f6946131f42248f181dea676439 vendor/extensions/sns (radiant0.6.9-10-ge4bc04e) b99e2cbf3689bd5074517c2a17b6e1ed5e6063b9 vendor/extensions/tags (pre-radiant-0.7-5-gb99e2cb) 743a95be0f01696530f558e7f4934cc7e57d3ab8 vendor/plugins/attachment_fu (743a95b) Why is it displaying this way instead of just telling me which commit I am using? Also, because I cloned my repo, instead of pulling it, how can I get the branch on the server? Right now when I try and git push I get the message that everything it up to date. Any info is appreciated. Thanks, ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Which Settings extension is the one to use?
http://github.com/Squeegy/radiant-settings/network Curious about which of the Settings forks is usable for Radiant 0.7.1. Anybody know? ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Volunteers Needed! Radiant Wiki Migration
Ollivier Robert wrote: Why not using Redmine (redmine.org) it is also Rails based, has its own forums/wiki/repository managements and a nice interface? I've been using it for http://dev.keltia.net/ with great success (while www.keltia.net is radiant). It looks like some of the projects they mention as success stories have themselves moved their wikis to git (e.g. Typo). ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Which Settings extension is the one to use?
Brian Gernhardt wrote: I'm using Squeegy's and it seems to be working fine. Thanks. It now works for me as well. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: ActionController::RedirectBackError during redirect_to with Comments extension
N. Turnage wrote: When I try and approve, unapprove or destroy a comment I get the following error: *ActionController::RedirectBackError in Admin/commentsController#destroy* No HTTP_REFERER was set in the request to this action, so redirect_to :back could not be called successfully. If this is a test, make sure to specify request.env[HTTP_REFERER]. Here is a full text of the error: http://pastie.org/442463 Anybody run into this before? I am using Radiant 0.7.1, Mac OSX 10.5.6, Ruby 1.8.6 Just found some more info about this. Apparently FireFox, my browser of choice (and the only anyone should use ;^), has an option to disable referrers. This article suggests another option for handling the redirect. http://blog.edendevelopment.co.uk/2009/04/02/redirect_to-back-not-reliable/ What do you think? ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: ActionController::RedirectBackError during redirect_to with Comments extension
N. Turnage wrote: Just found some more info about this. Apparently FireFox, my browser of choice (and the only anyone should use ;^), has an option to disable referrers. This article suggests another option for handling the redirect. http://blog.edendevelopment.co.uk/2009/04/02/redirect_to-back-not-reliable/ OK, I'm answering my own question again. It turns out that I had the disable referrers set in the Web Developer extension. Now I don't know if FireFox disables referrers by default, but I thought it important to mention why I was having trouble with the Comments extension. So anybody running Firefox and having a problem with the redirect_to :back, check that you are allowing referrers. That is all. Everything else about the Comments extension seems to work perfectly with Radiant 0.7.1. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: ActionController::RedirectBackError during redirect_to with Comments extension
Pat Allan wrote: Nate, not that I want to rain on your parade, but I *think* IE cannot be relied upon to send the referrer back to the server (depending on settings/versions/who-knows-what it may think it's a security risk). It's been a while since I looked into it, though. When I'm handling logins and then redirects-on-success, I track the last-visited-page in the session (excluding POSTs, session-related pages, etc), and redirect to that instead, rather than using HTTP_REFERER. Not sure if that's any help in your situation though. And all that said, it really has been a few years since I hit this problem with IE. I could be wrong. I think you are right. This post touches on that: http://www.ahabman.com/blog/2008/06/rails-redirect_to-back-in-internet-explorer/ Setting a session variable does indeed seem like the best way to make use of the last-visited page, as described here: http://blog.edendevelopment.co.uk/2009/04/02/redirect_to-back-not-reliable/ I should clarify that the Comments extension is only using 'redirect_to :back' in the admin comments_controller after comments are approved, unapproved or destroyed. As long as the admin avoids IE or makes sure that referers are not disabled if using FF then it shouldn't be a problem. I was encountering the error because FF was set up to block referers. Once I changed that, everything wored perfectly. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Something I noticed about Textile in 0.7.1
During the upgrade to 0.7.1 from 0.6.9 (seriously, could we add another couple more decimal places?) is that Textile is handled a bit differently. It used to be that You could pile on the textile'd page parts and snippets on top of one another inside of a page that had Textile set and it would (usually) render the html properly. But in 0.7.1 the Textile processing is much more specific in how the html gets rendered. I found that specifying the Textile filter in the parent snippet/page/page part will sort it out for the parts that are placed within it. Nice. Just something I noticed. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Hosting 0.7.1 site w/ Papperclipped
Brian Gernhardt wrote: I'm working on a website for a client and I'm attempting to find a decent host for them. I'm building the site locally right now, using Radiant 0.7.1, Paperclipped, and Styles 'n' Scripts. I've looked around but it's far too easy to find piles of negative feedback about everyone, and difficult to get an independent review. So I thought I'd ask the people actually using Radiant what they think. I've used Rails Playground (http://railsplayground.net) for two years now, and I've been very happy with them. They have svn and git repository hosting, serve rails apps with fcgi, mogrel and/or Phusion Passenger and they have great prices on their plans. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] uninitialized constant Admin::PageController -- SOLVED
Pat Allan wrote: Hi Nate Looks like the page_attachments extension is the cause (and it's now PagesController - plural, not singular). Has the extension been updated for 0.7.0+? Thanks. After a little more research I figured out that I needed to update my extensions before migrating the app. Worked like a charm. Thanks for looking into it. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] 500 Internal server errors with Radiant 0.7.1 and SNS
I am running into the same problems with SNS that were mentioned here: http://www.ruby-forum.com/topic/176102 And just like the original person having problems, the info here was not the fix for it: http://www.nabble.com/SnS-Extension---500-Error-td21486070.html This is the error: Status: 500 Internal Server Error Content-Type: text/html 500 Internal Server Error Anybody have a fix for it? I have 5 stylesheets that I would really rather not bring into the main admin area. Thanks, ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Anybody tried Disqus?
Hey all, Has anybody here ever tried using Disqus for a Radiant project, or any project for that matter? If so, what were your thoughts about it? Thanks, Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Anyone know if these extensions have been updated for 0.7?
Jeffrey Jones wrote: Hoi all Comments extension definitely works. i am using it on a 0.7.1 site. For the others, check out their github repos. The commit comments usually give a big clue. N. Turnage wrote: comments search share_layouts I had done a cursory examination of the commits for all the extensions I am using. These three didn't have any obvious mention of 0.7x compatibility. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Anyone know if these extensions have been updated for 0.7?
Jason Garber wrote: I just used share_layouts on a 0.7.1 project. I tried using comments at one point but got fed up and just used Disqus. I don't remember if it was compatibility or just too much complexity for me. Awesome, then if search works I'm golden. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Page_attachment image title as attachment:link title
Istvan Hoka wrote: You are getting this because Radius does not expand tags inside tag attributes. To get around this you could use the radiant-extensions extension (not a good name, I know) [http://github.com/Aissac/radiant-extensions-extension] which, among other things, hacks Radius to do what you need. Thank you very much. I ended up doing something a little bit differently, but I'll definitely look into this extension to add to my solution. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Paperclipped Extension improvements
Istvan Hoka wrote: Hi everyone! We have made some changes to Paperclipped we thought you might like: * r:assets:each enhanced with limit, offset, order, by, extension filtering; * r:if_assets and r:unless_assets tags for conditional rendering; * r:assets:width and r:assets:height via imagesize gem; Pure unadulterated awesomeness! * better migration compatibility with PageAttachments extension when they have title and description fields (degrades gracefully). I cannot thank you enough for this. Fork is at: http://github.com/Aissac/paperclipped/tree/master. Pull requests have been sent out. Thanks again. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Page_attachment image title as attachment:link title
Hey all, Trying to get the image title to render as the link title attribute but title=r:title / is rendering out as title=lt;r:title /gt; in the following snippet: notextile r:attachment:each limit=2 offset=1 order=asc div class=galleryThumb r:attachment:link rel=facebox-cap title=r:title / r:attachment:image size=gallery_thumb / /r:attachment:link /div /r:attachment:each /notextile Can anyone tell me why the less-than and greater than symbols are becoming html names instead of the tag being interpreted? Thanks, Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Trouble grepping regex for if_url
Hey guys, I am trying to set up an if_url rule that creates an h1 headline of the page title if the page or the page's parent is /destinations/. What I have is this: r:if_url matches=^/destinations/.+ h1r:title //h1 /r:if_url The problem with this is that, while I get the page title on the /destinations/ page, it draws two h1 headlines on the child pages. How should I modify this to only create a single h1 headline on the child pages. I have unsuccessfully tried: ^/destinations/ /destinations/ /destinations Can anyone shed some light here? Thanks, Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Search extension question
Hey guys, How do I set up a search field in my template that will take one to the search page and return results? My Rails-fu has gotten really rusty since going 100% Radiant and I cannot remember how to do it. Thanks, Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Question about search extension and site caching
I am using the search extension and I have posted my site to my dev server. The project is managed with git. I cap deployed to the server, then dumped my local db and imported it into the online server. Now the search term that I had last tested the search extension with is showing up in the search box at the top of the page. I don't understand how that search term was cached and included in the db. How can I refresh the cache to let go of this term? You can see what I am talking about here: http://stmc.andadv.com It's the top search box that I want to clear. This is the content from the snippet that the search box appears in: div id=aux_navbar spanCareers:/careers | Contact:mailto:i...@southtexasmedicalcenter.com form action=/search method=get id=search_forminput id=q name=q value=baptist size=15 alt=search type=text input value=Search type=submit/form/span /div Anyone have any idea how to fix this? ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Question about search extension and site caching
N. Turnage wrote: I am using the search extension and I have posted my site to my dev server... You know, some days it just isn't worth getting out of bed. I found that I had set a default value for the text field, and that's why it was always showing up. There is nothing more to see here. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Counting pages in an archived month - how?
Hey guys, Is there any way to count how many pages are archived per month for a given parent? What I have is this: r:if_url matches=^/blog-posts/ div id=archives class=sidebar_section h5Posts By Month/h5 ul r:find url=/blog-posts/ r:children:each order=desc r:headerlia href=r:date format=/blog-posts/%Y/%m/ /r:date format=%B %Y //a/li/r:header /r:children:each /r:find /ul /div /r:if_url I would like to show something like this, where (50) is the number of pages posted during February 2009: lia href=/tanjents/2009/02/February 2009 (50)/a/li Any thoughts? Thanks, ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] So what doesn't work with 0.7?
Philip Hallstrom wrote: 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 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] So what doesn't work with 0.7?
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? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Unistall extensions
Chaim Kirby wrote: I am having trouble with the copy_move extension under 0.6.9. I now know that I need to use an older version of the extension. How do I go about uninstalling the extension that I have currently installed so I can switch to the correct version? You don't have to remove the extension, you just need to use an earlier commit. This commit works for me with a site running 0.6.9: 79ee39addf4adabcf28fe77a8cb9cbf2338feda8 The process for using an older commit is different depending how you manage your project. If you are managing your project with git, you can add the extension as a submodule, and checkout the commit you want. If you are using something else to manage your project you can create your own local branch. I don't have the time at the moment to document the process for each right now, but you can find info on adding submodules to a project and on using local branches on the interweb. Also, you could look in the mailing list archives. In late December and early January I went back and forth with Sean (and somebody I cannot remember at the moment) about setting up a project with git and use submodules. If you have any more specific questions I'll do what I can to help out. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Unistall extensions
Chaim Kirby wrote: If I were to phrase the question more generically: How does one remove an extension they are no longer interested in having installed? Is there a process to do it? As a note, I have been using the git clone _extension_ into vendor/extensions, migrate, update extension management paradigm. You would cd to your project then do the following: 1) rake radiant:extensions:name_of_extension:migrate VERSION=0 2) rm -rf vendor/extensions/name_of_extension 3) check your extension_meta table for an entry for the extension and delete that record 4) That's it. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] tags extension - dropdown
Steven Southard wrote: Is there any way to break tags up so It can be made into a dropdown? I imagine it would be something like this: r:find url=/something/ select r:children:each option value=r:slug /r:title //option /r:children:each /select /r:find // Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Unistall extensions
Sean Cribbs wrote: Two things - 1) You can typically use `script/extension uninstall extension_name` to uninstall an extension - although it may need to be on the registry. I have never done it that way, so I didn't want to recommend it. But, thanks for the alternative method. 2) In 0.7, the 'extension_meta' table is no longer used. Once you have migrated any extension, all extension migrations are recorded in the 'schema_migrations' table. That is good news. That should make it easier to track down problems when a migration goes awry. Thanks. // Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] So what doesn't work with 0.7?
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 ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant 0.7.0 Intaglio Release
Sean Cribbs wrote: Looks like it's time for another release of Radiant: http://radiantcms.org/download/ Frickin' sweet! I can't wait to try it. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Templates extension and the schema
Jim Gay wrote: Radiant should update the schema.rb file But it doesn't. This is the content of my schema.rb file: ... # This file is auto-generated from the current state of the database. Instead of editing this file, # please use the migrations feature of ActiveRecord to incrementally modify your database, and # then regenerate this schema definition. # # Note that this schema.rb definition is the authoritative source for your database schema. If you need # to create the application database on another system, you should be using db:schema:load, not running # all the migrations from scratch. The latter is a flawed and unsustainable approach (the more migrations # you'll amass, the slower it'll run and the greater likelihood for issues). # # It's strongly recommended to check this file into your version control system. ActiveRecord::Schema.define(:version = 0) do end ... The file is auto-generated, so how do I get a look at the current state of affairs? ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Templates extension explosion solved, Now I want to reinstall cleanly
Jim Gay wrote: Take a look at what your log says cd log tail -900 producton.log - that will show the last 900 lines. If you need more or less, change the number. Or you can do tail -f production.log - that will display the log as the requests come in, so do that and then hit the admin page in a browser and you'll see the log populated I am curious, does radiant keep track of the schema anywhere in the file system that it would see that I have already migrated the extension before, albeit on my dev machine? Radiant should update the schema.rb file Jim, thanks for you help. That tip for viewing the production log as it's happening is awesome. The really strange thing is that the admin area of the site miraculously started working on its own. Strange. But since I can never leave well enough alone, I am going to try and install the templates extension again. I like the way it works for some of the site parts that I use. So a few more questions related to extensions in general: 1) I have migrated to VERSION=0 the templates extension, removed it from my file system and removed it from my git repo, but I noticed that there is still an entry for the templates extension in the extension_meta table. Will I be creating a problem if I delete that record (the last in the table)? Are there any other hidden db tables where I might find some vestigial parts of that now removed extension? 2) Where in the Radiant space-time continuum is the schema info that would normally be in the schema.rb file kept? The schema.rb file is essentially empty and I cannot find the schema info in the db so I am wondering, where is it? I want to make absolutely sure that my db is free of templates info. BTW, I am using the gem of 0.6.9. Thanks, //Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Templates extension explosion - Please help
I installed the templates extension on my project on my laptop, but when I deployed the updated project and migrated the templates extension things went horribly wrong. First, the rake was aborted on the 4th migration with an error that the position column had already been created (not possible). Second, I cannot get into the admin portion of my site any more, even if I migrate the extension to VERSION=0 and delete it completely. The only thing I could think might be a problem is that I did add the arrow image and the templates javascript files into source control, but neither should affect a migration. I am really at a loss as to what could make this break this way. The project is on 0.6.9. Trace from the migration: rake production radiant:extensions:templates:migrate --trace (in /home/tanji/app/goodtaste_new/releases/20090206034811) ** Invoke production (first_time) ** Execute production ** Invoke environment (first_time) ** Execute environment ** Invoke radiant:extensions:templates:migrate (first_time) ** Invoke environment ** Execute radiant:extensions:templates:migrate == 4 AddPositionToTemplates: migrating -- add_column(:templates, :position, :integer) rake aborted! Mysql::Error: Duplicate column name 'position': ALTER TABLE `templates` ADD `position` int(11) /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:150:in `log' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:281:in `execute' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/schema_statements.rb:124:in `add_column' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/lib/active_record/migration.rb:285:in `send' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/lib/active_record/migration.rb:285:in `method_missing' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/lib/active_record/migration.rb:265:in `say_with_time' /usr/local/lib/ruby/1.8/benchmark.rb:293:in `measure' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/lib/active_record/migration.rb:265:in `say_with_time' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/lib/active_record/migration.rb:281:in `method_missing' /home/tanji/app/goodtaste_new/releases/20090206034811/vendor/extensions/templates/db/migrate/004_add_position_to_templates.rb:3:in `up_without_benchmarks' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/lib/active_record/migration.rb:219:in `send' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/lib/active_record/migration.rb:219:in `migrate' /usr/local/lib/ruby/1.8/benchmark.rb:293:in `measure' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/lib/active_record/migration.rb:219:in `migrate' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/lib/active_record/migration.rb:348:in `migrate_without_extension_support' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/lib/active_record/migration.rb:339:in `each' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/lib/active_record/migration.rb:339:in `migrate_without_extension_support' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.9/lib/radiant/extension_migrator.rb:33:in `migrate' /home/tanji/app/goodtaste_new/releases/20090206034811/vendor/extensions/templates/lib/tasks/templates_extension_tasks.rake:11 /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:617:in `call' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:617:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:612:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:612:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:578:in `invoke_with_call_chain' /usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:571:in `invoke_with_call_chain' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:564:in `invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:2019:in `invoke_task' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:2036:in `standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1991:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1970:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:2036:in `standard_exception_handling'
Re: [Radiant] Templates extension explosion - Please help
Jim Gay wrote: Mysql::Error: Duplicate column name 'position': ALTER TABLE `templates` ADD `position` int(11) It would appear that the templates table already has a position field before the migrations are run. Is it possible that you're working with a database that has some of the structure already setup? That's how it appears to me as well and this happened on a fresh install of the templates extension. The process I have used is as follows: On laptop: - add extension as submodule - cd to extension and git initialize and update extension - cd back to project root - migrate extension - update extension - git add files added by templates extension - git push On server: - cd to project current root - rake production extension Migration dies trying to run 4th migration and now I cannot get into the admin page list. I have tried migrating extension to VERSION=0 and completely removing it, but I still cannot get to the list of pages. It's late and I have no fight left in me tonight. If anybody has any info on what I can do just to get my site working again, I would be very appreciative. I don't know where to start looking to find out why the admin page list isn't showing up. I am curious, does radiant keep track of the schema anywhere in the file system that it would see that I have already migrated the extension before, albeit on my dev machine? ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] if_content not working as expected
Jim Gay wrote: In retrospect, the if_content should be called if_part, since that's what it means. if_content doesn't check for contents in the part (or whether or not the part is blank) it checks if the part exists Ah, I see. Would it make sense if a feature was added to it so that you could do something like r:if_content part=address2 check_text=true Yes, that would be immensely helpful. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] if_content not working as expected
Sean Cribbs wrote: With templates, the part is there even if empty. You probably need a tag that checks whether the contents of the part is blank. Andrew vonderLuft has some tags that he intended to submit to core that do just that - I'll poke him about it. Thanks. Are there any current extensions that might help out with this? ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Additional templates extension strangeness
Thanks for the page status pulldown on the updates though. ;^) ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] if_content not working as expected
Hey all. I am using the templates extension and I have 'address1' and 'address2' fields in a template used to hold information about a number of institutions. When I use r:children:each to iterate over the fields for each institution, some or which do not have any content in the address2 field, the bullet is still rendered using using the following block: r:children:each h5r:title //h5 p r:content part=address1 / r:if_content part=address2 bull; r:content part=address2 / /r:if_content /p /r:children:each I was expecting that because the address2 field is empty that the bullet and address2 content part would not be rendered. Is that not what is supposed to happen? Thanks, Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Customizing Radiant's command line behaviour
Adam van den Hoven wrote: The thread on what standard plugins do people use as well the Oops I deleted the contest2 content thread got me thinking that it would be great if someone wrote a tutorial to the effect of, How to customize your Radiant command. Usually I start 90% of my radiant sites by installing the same extensions; they fit into the way I like to do my work. I am also inherently lazy so I'd rather put a lot of work in now to prevent having to do that work over and over again later (I'm told that's not actually lazy, but I'm not convinced). Things I would like know how to do: 1) add my own default plugins to the created site 2) add my own initial site templates (or force a single initial setup) 3) take production database parameters from the command line (I tend to follow the same pattern since most of my sites are on dreamhost) 4) save the results in Git (either in my own repository on Dreamhost or in GitHub) 5) update my custom radiant with the lastest changes (either plugins or radiant itself) half a year from now. . I like the idea of making the radiant command do things the way I like it but (5) is critical if I don't want to fall behind. I also want to control which versions I see of any of these so that I don't get hosed when version 0.8 comes out and now half my extensions won't work with 0.7.9 Sorry, dude, but that wouldn't work that way because of the nature of open source. Not everybody maintains their extensions with up to the minute changes for Radiant edge, there is no standard way for managing Radiant projects in git, extensions aren't always in git repos and the extensions are rarely tagged for which which commits work with which Radiant versions. Not to mention that some people prefer to use the multi_site extension for their Radiant projects which brings a whole other set of complications. Also, Dreamhost hosting for Radiant projects presents a further set of complications that someone like myself doesn't encounter because I use Rails Playground instead. The only way that it might be possible for your suggestion to work is for RadiantMachine to get up and running and have it become the standard way of building and hosting Radiant apps. It would need to be kind of like Wordpress where they have a large number of sites that are hosted by the mothership, but if people so desire they can build and run a Wordpress site on their own servers. What do you think, Sean, you're not busy, eh? Feel like becoming a millionaire? All you need is some venture capital. Seriously, though, I think Radiant is just fine as it is. Well, it would be nice to have those blogging features alluded to for 7.1 (?). Then it would be perfect. Well, it would be great if... ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Basecamp
Sean Cribbs wrote: Purely coincidence. The tab metaphor is pretty powerful and ubiquitous. Have you seen http://github.com/radiant/radiant-prototype ? I just took a look at this. I cannot wait to start using it. Thanks to everyone working on the updates. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
