Re: [Radiant] Test
Booya! Sean John W. Long wrote: testing 1, 2, 3... -- John Long http://wiseheartdesign.com ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] redmine
There's nothing wrong with Redmine. In fact, I like a lot of things about it. However, simply because it's a Rails application doesn't mean that's a compelling reason to switch. I'd like to hear some opinions from people who use Redmine regularly about its pros and cons. Sean Mark Gallop wrote: Benedikt Eickhoff wrote: Mark Gallop wrote: Benedikt Eickhoff wrote: Hello List, - wouldn't it be great to change over onto REDMINE (redmine.org) (from my perspective one true 'model rails app') with all radiant (extension) development efforts? (typo3 already did...) I suggested the same a few months back - http://dev.radiantcms.org/radiant/ticket/591. Cheers, Mark Why don't 'they' react? What do you think? Oh, and by issue (redmine) I meant ticket (trac). Cheers, Mark ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] redmine
I don't see Rails Engines included anywhere in its source. Am I missing something? Sean Benedikt Eickhoff wrote: Sean Cribbs wrote: There's nothing wrong with Redmine. In fact, I like a lot of things about it. However, simply because it's a Rails application doesn't mean that's a compelling reason to switch. I'd like to hear some opinions from people who use Redmine regularly about its pros and cons. Sean I think centralizing extension development could be much easier managed with redmine - it's a snap to create svn repositories. With Trac comes Apache VHosts or svnserve manual permissions etc etc - not quite fuels for a kickstarter like radiant. But the real killer app would be if you guys would hook into redmine development creating an alternative for the current redmine wiki modul ... adding a radiant plugin - however I'm brainstorming - think of dropping radiants shy small team idea. I think redmine suffers a little from 'rails engines' - deserves a cure which you'd sure have to offer! ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] Radiant 0.6.5 Release Candidate 1
Radiant 0.6.5 has been a long time coming! And just to be sure, we want to release a candidate or two to make sure we have everything solid. There are some really major changes in this release, and here's the two big ones: * Rails 2.0.2 included * RSpec is used in core and supported in extensions You can download the Radiant 0.6.5 RC1 from http://radiantcms.org/downloads/radiant-0.6.5-RC1.gem. This release candidate is intended for developers and is NOT intended for production use. Please report any bugs you find to the development site at http://dev.radiantcms.org/. == Installation To install use the gem command (with 'sudo' as necessary): $ gem install radiant-0.6.5-RC1.gem The gem will install as 'radiant-0.6.5'. === Upgrading an existing project/site 1. Change the RADIANT_GEM_VERSION constant in config/environment.rb to 0.6.5 2. Update the Radiant assets in your project: $ rake radiant:update 3. Copy your customizations back into config/environment.rb, if necessary (see below). 4. Migrate the database if you are running 0.6.2 or earlier: $ rake production db:migrate 5. Restart the server === Creating a new project/site 1. Invoke the 'radiant' command with your desired database driver: $ radiant -d sqlite3 my_project 2. Bootstrap the database: $ cd my_project $ rake db:bootstrap 3. Startup the server and try it out! $ script/server == Internal Changes to config/environment.rb This release has required a lot of changes to the internal API of Radiant. End-users should be unaffected, but as a result of these requirements, we have made significant changes to config/environment.rb and config/boot.rb. When updating your existing projects, config/environment.rb will be copied to config/environment.bak. You will need to manually copy any customizations, especially config.extensions and any other libraries, etc. that you require. *DO NOT* copy config.load_paths, config.plugin_paths, or any of those items to the new file; those settings have been internalized in this release. Thanks again for everyone's contributions! Cheers, Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Render content of specific child
Use the r:find tag to switch to any given page while rendering. Documentation about it is available in the interface. Sean rainer griess wrote: Hi again, is it somehow possible to render the content of a specific child? For example, I would like to put some content on my Homepage coming from the homepage's child named homenews. How can I get access the content of a specific child? Thanks again, rainer ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] too many articles..
Kay, Daniel Sheppard has an extension that organizes pages under an archive page by date. This might help. Sean Kay Joo wrote: Hello! I migrated my blog with 500 articles to radiant. It seems like just a common blog, but there is a problem of administration. Hundreds of article pages are the children of Articles(Archive) page, so when I click on the + button next to 'Articles', it takes too long time. Also the articles are not sorted, so it's difficult to manage them. Can somebody help me to solve this problem? ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] still active?
That said, there are a number of jewels of wisdom on this list and some in the wiki. Unfortunately, the wiki is a bit slow and that's quite a problem. I still want to get around to the idea of the documentation I had proposed, but I can't say much till I get more time. Anyway, the idea is here if anyone else is interested. The core team is working with Andrew Vonderluft to migrate all the Radiant sites (home, demo, dev, wiki) over to a better hosting solution. The wiki will be faster and more reliable after this migration. Getting this stuff off TxD's shared hosting will be a boon! Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] reorder extension stopped working (rainer griess)
Rainer, Install piston: 'gem install piston'. Then go into the vendor directory and run 'piston convert'. This will allow you to modify a local copy of the extensions (and of Radiant), and store that copy in your own repository. Radiant uses this technique to track its bundled libraries: Rails, Radius, Redcloth, etc. Sean rainer griess wrote: Benny, it would be nice to get another tip to my related question: How can I store my whole radiant trunk into my subversion repository, including the now running shards extension? If I only do a svn commit the externals get not saved into the repository. This might be useful. But in my case I want to save the complete and running version of my radiant directory. I am new to this ;-) rainer On 21.02.2008, at 13:25, Benny Degezelle wrote: Hi rainier, Check your vendor/extensions/shards/app/views/admin/page directory. What extension do those files have? If they are .html.erb, instead of .rhtml, you'll have to check out an older version of shards (until the 0.6.5 release, which will have rails 2 included). Because 0.6.4 doesn't detect the .html.erb files as views, shards fails to load properly, which will on it's turn break any extensions depending on shards.. This is the svn:external i'm still succesfully using in 0.6.4; shards -r 674 http://dev.radiantcms.org/svn/radiant/trunk/extensions/shards/ Regards, Benny ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] inconsistent routing
Benny, Try this: define_routes do |map| map.with_options :controller = 'shop', :action = 'index' do |shop| shop.connect en/shop/:action/:id, :language = 'en-US' shop.connect nl/shop/:action/:id, :language = 'nl-BE' end end My guess is that without the default action of 'index', it doesn't match. You can test these in a functional test: def test_shop_routing_with_language assert_recognizes /en/shop, :controller = shop, :action = index, :language = 'en-US' assert_recognizes /nl/shop, :controller = shop, :action = index, :language = 'nl-BE' # etc... end Sean Benny Degezelle wrote: ; define_routes do |map| map.connect en/shop/:action/:id, :controller = 'shop', :language = 'en-US' map.connect nl/shop/:action/:id, :controller = 'shop', :language = 'nl-BE' end Sean Cribbs wrote: Benny, Would you paste us the route definitions? Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] inconsistent routing
Benny,
Ah, sorry. You might try assert_routing, which does both a generation
and a recognition assertion. Now, I don't know if it has anything to do
with your problem, but I have found that it's more reliable to use named
or resource routes in extensions. I'm not sure if this is a Radiant
issue or a Rails issue. Try naming those and see if it becomes more
consistent.
Sean
Benny Degezelle wrote:
Nope, i'm still getting the same results; sometimes works, sometimes
doesn't.
the assert_recognizes didn't seem to work that way, i had to switch the
first part ('/en/shop') and the options to get those to pass
Sean Cribbs wrote:
Benny,
Try this:
define_routes do |map|
map.with_options :controller = 'shop', :action = 'index' do |shop|
shop.connect en/shop/:action/:id, :language = 'en-US'
shop.connect nl/shop/:action/:id, :language = 'nl-BE'
end
end
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] inconsistent routing
Are you using trunk or a previous version? This bug may have been
introduced in the extension-loading refactoring.
Sean
Benny Degezelle wrote:
assert_routing works indeed. The test passes, but i'm still getting the
same results:
app.get('/en/shop')
= 302
app.get('/en/shop')
= 200
app.get('/en/shop')
= 302
app.get('/en/shop')
= 200
app.get('/en/shop')
= 302
app.get('/en/shop')
= 200
app.get('/en/shop')
= 200
app.get('/en/shop')
= 200
This is with a named route.
Daniel; as far as i know i'm not working with multiple mongrel
processes. I'm still working in development mode only, and i haven't
played with setting up mongrel clusters or anything..
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] inconsistent routing
Ah. Try freezing to revision 679: rake radiant:freeze:edge REVISION=679 Sean Benny Degezelle wrote: Sean Cribbs wrote: Are you using trunk or a previous version? This bug may have been introduced in the extension-loading refactoring. Sean I'm on 0.6.4, running from gem ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] still active?
Maarten, Yes, I understand the documentation problem. That is one reason why we have been trying to promote the wiki; documentation is time-consuming to write. Sean Maarten Oelering wrote: Hi Sean, Thanks for your extensive reply. I am happy to hear that Radiant is very active. However others might get the same impression as me, which probably would not be the case if radiantcms.org is updated more frequently. But, as you say, the quality of the code is what counts, and not the packaging. The fact that Radiant, like any other CMS, may not do eveything out- of-the-box is not a problem. That's one of the main reasons why I prefer a Rails based CMS, since it makes developing extensions a lot easier. What made me enthousiastic in the review I mentioned is that Radiant is part of list of well-known CMS's and considered as an interesting new contenter which looks very promising. As a ruby developer, the only lacking feature I have a problem with is the part about the documentation. I will check out the Styled Blog template as you suggested. This might help me creating the layouts and structure of the site. However my less technical colleagues must also be able to edit content or add pages to the site. If the rather conceptual documentation is extended with more concrete examples, it might help a lot. Cheers, Maarten On 20-feb-2008, at 15:46, Sean Cribbs wrote: Maarten, Let me assuage some of your fears. Radiant is VERY active, people are using the CMS all the time to build websites, and I receive at least 15 messages a day on the mailing lists. Your perception of inactivity in the project may be because we release fairly infrequently, for an open-source project. I would say that's a combination of the limited time our core developers can devote, the overall quality of the code (fewer bug fixes) and our commitment to that quality (we try not to release broken code). I would not fear using it for serious business websites. If you want evidence of its usage in a serious business website, look no further than redken.com (USA site) and redkensalon.com. Granted, we made heavy customizations to Radiant for that site, but the team I worked with assured me that all of the sites they have built, most of them with a PHP-based CMS, have required an equivalent customization effort. Regarding templates (layouts, actually), Radiant gets out of your way in that regard. Design whatever template you want, Radiant can serve it. If you want to know how to create a layout, it's best to bootstrap Radiant with the Styled Blog template and read its layout(s). They are actually a lot simpler than you might expect. Let me be clear. Radiant won't do everything for you, but most of your needs will be satisfied by the base installation: designing, creating and publishing pages. For other things, you will need to look into extensions. Sean P.S. Those lacking features made you MORE enthusiastic? Did I understand you correctly? Maarten Oelering wrote: Hello, I'm a ruby developer and very enthousiastic about Radiant. The review on http://www.a3webtech.com/index.php/cms-3.html mentioning the less mature state of the project and the lack of an installer even made me more enthousiastic. However I am still hesitant using it for a serious business websites. I miss some critical documentation on creating templates for a decent website, i.e. how to use the system in the role of webmaster. Reading the documentation on radiantcms.org didn't help me much. Fortunately the article in artofmission.com cleared up some things for me. Overall I get the impression that project is not very active, judging on releases, the blog and the mailing groups. However I can't see what's going on behind the scenes. Is Radiant still alive and kicking? Regards, Maarten Oelering ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Best practices for managing CSS, JavaScript, images?
Tim, Chris Parrish, with whom I've spoken privately, is working on an extension that will allow you to manage CSS and JavaScript separate from the page sitemap and have them be cached in some reasonable place so they can be served by your web server. In the meantime, you can create pages in the sitemap that have special layouts that specify their content type. It means an extra hit to Radiant to get the CSS or JS, but it's a good interim solution. To accomplish this, I would create a child of the homepage called Stylesheets, and create a layout for it like this: Name: CSS Content type: text/css Content: r:content / Then create child pages of Stylesheets that are your individual stylesheets, modifying the slug to end in .css if you desire. You can do the same for JS. Cheers, Sean Timothy Jones wrote: Greetings, I'm just ramping up on Radiant. Apologies if I've missed this in a FAQ somewhere, but I'm looking for some recommendations on managing these types of assets on a Radiant-based site. I found a mailing list thread from 2006, but it didn't seem to have a conclusion. With non-Radiant sites I have Apache serve up these static files, bypassing Rails entirely. What are the recommended best practices with Radiant? I'd like to manage them through the web interface, so that other folks don't have to deal with Subversion, deployment, etc. Do folks generally just embed the CSS and JavaScript in a layout and serve it dynamically? And caching? What about images (icons, backgrounds, etc.)? I'd like a way to upload and delete them from a browser, again to avoid Subversion and deployment hassles. It looks like the Gallery extension might work for this. Any other recommendations? Thanks! Tim Jones Barbary Codes and Data ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] rake db:migrate:extensions
Make sure that the directory containing the extension is named the same as the *_extension.rb file inside it. If it's metadata_extension.rb, name the directory metadata, etc. Sean [EMAIL PROTECTED] wrote: I've just got onto using radiant last week, it's been great to get up to speed fast and be able to slam out some sites that have been languishing. While I've been able to install some extensions like shard fine others won't load when I issue: rake db:dbmigrate:extensions I receive the following error: Could not load extension from file: meta_data_extension. #NameError: uninitialized constant MetaDataExtension Which I'm unsure of how to resolve. thanks in advance Brian Loomis Brian Loomis [EMAIL PROTECTED] (208) 562-3944 ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] reorder extension stopped working
rainer, Did the whole column disappear or just the buttons? If there's still a column header that says Order, run: rake radiant:extensions:reorder:update Sean rainer griess wrote: Hi guys, I was happy to get shards and reorder running using the gems version of radiant and trunk versions of shards and reorder: $ svn propedit svn:externals vendor/extensions shards http://dev.radiantcms.org/svn/radiant/trunk/extensions/shards/ reorder http://dev.radiantcms.org/svn/radiant/trunk/extensions/reorder/ After a svn update of my repository the extensions got an update and the reorder buttons disappeared. Although the extensions show up as enabled in radiant. I got two questions and hopefully they get answered. 1. How can I get reorder up and running again? 2. I use SVN too. As shown above I added the extensions as external resource, following your advice at radiantcms.org. I am relatively new to SVN. How can I freeze a version of my radiant installation with all external recources stored as a local copy? Then it would be possible to simply go back to the version before. Now every time I go back to an old version the externals get downloaded from dev.radiantcms.org and I am where I am. Any help would be really nice. Thanks, rainer ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Ticket #503, Bootstrap with sqlite3 db fails to create admin user
Radianteers, Ticket #503 on the Radiant Trac is about problems with the bootstrap process on sqlite3. I have recently been unable to reproduce this problem. This is a call for help -- please test it on your platform and let me know the results. Here's how to test the problem (on trunk): 0) Make sure you have the SQLite3 library installed for your platform, and the sqlite3-ruby gem. 1) Check out the trunk of the Radiant source: $ svn checkout http://dev.radiantcms.org/svn/radiant/trunk/radiant 2) Generate a new project with the sqlite3 database: $ cd radiant $ script/generate instance -d sqlite3 ../test_sqlite3 3) Freeze edge into the new project: $ cd ../test_sqlite3 $ rake radiant:freeze:edge 3b) Instead of rake radiant:freeze:edge, you can link directly to the source (on Unix-y and Mac systems): $ ln -nfs ../radiant vendor/radiant 4) Bootstrap the database, choosing the defaults and the Empty template when prompted: $ rake db:bootstrap --trace 5) Test that the admin user was created: $ script/runner puts User.count If you get 1 printed from the last command, it worked. If you get 0, you have reproduced the problem. If at any point in step 4, you get an exception or failure, please include the stack trace with your report. *** IMPORTANT *** These platform/library combinations have already been tested, please do not respond with one of these unless it fails: Ubuntu 7.04, sqlite3 3.3.13, sqlite3-ruby 1.2.1 Mac OS/X 10.5.x, sqlite3 3.4.0, sqlite3-ruby 1.2.1 Thank you! Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Difference between development/production environments from extensions point of view
Sounds like your routes are messed up. Does your route definition look like this? map.connect 'admin/posts/:action/:id', :controller = admin/posts Make sure that your namespacing is correct. Sean 13 wrote: Hi, I'm developing a new extension for radiant. I have created a controller which is a subclass of Admin::AbstractModelController like this: class PostsController Admin::AbstractModelController model_class Post # ... end Posts controller is mapped to a new tab in the admin interface. When I click this tab list of items is displayed. In development environment everything is working as I want, but when I try to run the same extension in production environment I get following error: uninitialized constant Admin::PostsController I checked environment specific configuration files, but haven't found anything suspicions. Any help on how to fix this issue will be appreciated. Regards, Martins Grunskis ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Adding Options to my Extension
Chris, I like to use Radiant::Config. So if my extension was named Foo, I might do something like this: Radiant::Config[foo.file_path] = /some/path/to/somewhere Radiant::Config[foo.download_enabled?] = true Sean Chris Parrish wrote: What's the preferred way to add options to an extension. I want to let the developer configure things like path locations so that their choices are loaded at startup (and then used by my extension). -Chris ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] scheduler extension + r:children:each
http://dev.radiantcms.org/radiant/changeset/740 Cheers, Sean Mark Gallop wrote: Wow, top service ;) Thanks, Sean. Mark Sean Cribbs wrote: Mark, It should obviously be doing that for you! My apologies. Let me patch in something real quick. Sean Mark Gallop wrote: Hi all, I have the scheduler extension installed and use the following code in a layout: r:find url=/news-and-events r:children:each limit=5 order=desc by=published_at div class=entry h3r:link //h3 p class=infoPosted r:date format=%b %d, %Y //p /div /r:children:each /r:find Now this is showing links to pages which have expired as r:children:each ignores the expires_on value for the page. I wonder if anyone can advise whether I would need to create my own tag to filter the children, or is it already possible to exclude expired pages using existing tags? Cheers, Mark ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] page_attachment extension problem
Aitor, No, page_attachments just recently moved over to the Radiant repository. It is still available from my personal repository in an older version: http://svn.seancribbs.com/svn/rails/plugins/extensions/page_attachments/ Use that version with 0.6.4. Sean Aitor Garay-Romero wrote: Hi there! @sean cribs: I'm getting a template not found error in the page attachment extension. I took a look to the last change to it: r59 | seancribbs | 2008-02-08 15:20:00 +0100 (Fri, 08 Feb 2008) | 1 line Changed paths: A /plugins/extensions/page_attachments/app/views/admin/page/_attachment.html.erb D /plugins/extensions/page_attachments/app/views/admin/page/_attachment.rhtml A /plugins/extensions/page_attachments/app/views/admin/page/_attachments_box.html.erb D /plugins/extensions/page_attachments/app/views/admin/page/_attachments_box.rhtml M /plugins/extensions/page_attachments/page_attachments_extension.rb M /plugins/extensions/page_attachments/public/javascripts/page_attachments.js M /plugins/extensions/page_attachments/public/stylesheets/page_attachments.css Apply Mislav's patch. And seems that you are making it Rails 2.0 compliant. But the Rails extension packed in Radiant 0.6.4 gem is 1.2.5 so AFAIK it's not recognizing the new template name rules. I switched to the previous revision r58 and it's working correctly again. I'm missing some update to Radiant? Thanks! /AITOR ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] scheduler extension + r:children:each
Mark, It should obviously be doing that for you! My apologies. Let me patch in something real quick. Sean Mark Gallop wrote: Hi all, I have the scheduler extension installed and use the following code in a layout: r:find url=/news-and-events r:children:each limit=5 order=desc by=published_at div class=entry h3r:link //h3 p class=infoPosted r:date format=%b %d, %Y //p /div /r:children:each /r:find Now this is showing links to pages which have expired as r:children:each ignores the expires_on value for the page. I wonder if anyone can advise whether I would need to create my own tag to filter the children, or is it already possible to exclude expired pages using existing tags? Cheers, Mark ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] New Radiant site(s)
Mark, Yes, we have an FCKeditor extension, but it's so customized, I'm not sure how well it will translate to the outside world. Correct me if I'm wrong, but there is an existing FCK extension. I wrote one from scratch, with just a few ideas from an existing WYSIWYG extension (being able to toggle the control on and off). Normally I don't recommend a WYSIWYG editor for Radiant because of the potential smattering of Radius tags that would not be understood by the editor. We got by with this in two ways: 1) Most pages used a template (one of the mentioned extensions) that hid the majority of the Radius code. 2) For the tags that HAD to be in the editable content areas, we made sure they could operate as singletons (they automatically render a snippet) and used FCK to generate placeholders inside them. I believe we had only two kinds of these. Redken is also a very graphic-intensive site, so most pages consisted of several graphics in a row without text. So FCK was mostly used to preview the inserted images. Sean Mark Gallop wrote: Hi Sean, Does the FCKEditor integration comment indicate that you have a working FCKEditor extension for page editing? I have been trying get fckeditor working for page editing but the results have been a bit inconsistent. Cheers, Mark Sean Cribbs wrote: Folks, Here's the moment you have all been waiting for (or at least I'd like to think)! For the past four to five months I have been working with the wonderful team at Digital Pulp to develop the new website for Redken. We are proud to say that it has had its official launch this morning! Check it out: http://redken.com - and - http://redkensalon.com It has been an incredible experience working with them, and the Radiant community has greatly benefited. We have released two new versions of Radiant and numerous extensions during this tenure. The following extensions were a direct result of my work for Digital Pulp: * shards (http://dev.radiantcms.org/svn/radiant/trunk/extensions/shards) * related_content (http://dev.radiantcms.org/svn/radiant/trunk/extensions/related_content) * reorder, the non-Ajax version (http://dev.radiantcms.org/svn/radiant/trunk/extensions/reorder) * scheduler (http://dev.radiantcms.org/svn/radiant/trunk/extensions/scheduler) * share_layouts (http://dev.radiantcms.org/svn/radiant/trunk/extensions/share_layouts) * multi_site (http://dev.radiantcms.org/svn/radiant/trunk/extensions/multi_site) I also intend to release a some more over the next weeks, after they have been cleaned up for public consumption, namely: * file_system - Save/load Radiant models to/from the file system so they can be managed in an SCM * templates - Structure pages externally and provide a customized interface for editing * asset_manager - A full-featured asset manager, with mass upload, asset expiration, usage reports, and FCKEditor integration A big thank you and congratulations to all of the team at Digital Pulp (in no particular order) -- John, Justin, Josh, Michael, Alex, Brian, Sarah, David; and to my good friend Scotty Moon who also helped on the project. Cheers, Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] meta tags for 0.6.4
Use the --trace option with rake to figure out on what file/line the command is failing, then paste the results to us. Sean Chris Parrish wrote: Jasper Kooij wrote: Thanks Chris, ok specific questions about the page_meta extension: I've got it down to install on site5 hosting, I've got the extension installed using svn after the rake production db:migrate:extensions I get: rake production db:migrate:extensions /usr/bin/rake:17:Warning: require_gem is obsolete. Use gem instead. (in /home/jasperko/wisconsindells) rake aborted! uninitialized constant ApplicationController what am i doing wrong? Hmm. Are you using any other extensions (your command migrates *all* extensions)? Other than that, In my local development environment, I have a working Radiant 0.6.4 with the page_meta extension. The only reference to require_gem that I can find is in config/boot.rb on line 28. Can any of your core guys offer any insight here? -Chris ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Problem Loading Shards and Multisite
Keith, The other day, I moved the rails2 branch into trunk (1.2 included acts_as_tree and acts_as_list). I have not yet updated multi_site to include the acts_as_list plugin, but I will as soon as I can. Sean Keith Bingman wrote: I just installed the new multisite extension, which is a nice improvement over the old virtual sites extension. Nice work! But now I have problems... while I was at it, I updated to the edge of Radiant and everything broke. First of all I got an method not found error on the acts_as_list call in the multisite extension. Changing this to acts_as_tree makes it start, but then the shards extension doesn't seem to work. The config statement has no effect, the only way to force shards to load is by renaming it... Still, it doesn't seem to have an effect... Any help appreciated. Keith BIngman ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Problem Loading Shards and Multisite
Ah! It may be that I need to update Shards' file types (.html.erb vs. .rhtml). I'm also going to add some tests later that verify it actually injects partials. Sean Keith Bingman wrote: Sean, Thanks. I figured it was something like that. But for some reason I am still having problems with Shards. It runs, but nothing is injected into the views. It also doesn't honor the load order in the environment.rb files. Keith On Feb 5, 2008, at 3:43 PM, Sean Cribbs wrote: Keith, The other day, I moved the rails2 branch into trunk (1.2 included acts_as_tree and acts_as_list). I have not yet updated multi_site to include the acts_as_list plugin, but I will as soon as I can. Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Problem Loading Shards and Multisite
Keith, We put attachment_fu in vendor/plugins of an extension in the Redken project. However, with the way that 0.6.4 (not edge) loads extension-stored plugins, we had some autoloading issues with it. I imagine it should work better since they are in the normal plugin search path now. Sean Keith Bingman wrote: Of course, the new file endings may be messing it up. By the way, I am really happy to see the use of haml in there. We have been writing all of our extension views in haml lately. As for the new vendor folder, I assume this deals with loading plugins in extesnions. Have you tried moving attachment_fu there yet? Keith On Feb 5, 2008, at 4:21 PM, Sean Cribbs wrote: Ah! It may be that I need to update Shards' file types (.html.erb vs. .rhtml). I'm also going to add some tests later that verify it actually injects partials. Sean Keith Bingman wrote: Sean, Thanks. I figured it was something like that. But for some reason I am still having problems with Shards. It runs, but nothing is injected into the views. It also doesn't honor the load order in the environment.rb files. Keith On Feb 5, 2008, at 3:43 PM, Sean Cribbs wrote: Keith, The other day, I moved the rails2 branch into trunk (1.2 included acts_as_tree and acts_as_list). I have not yet updated multi_site to include the acts_as_list plugin, but I will as soon as I can. Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Weblog Archive
Ryan, Sort of. Radiant provides the hooks to be able to do it, but you need certain code in the page. Here's what that page has (Textile filter): r:children:each order=desc by=published_atr:header h4. r:date format=%B %Y / /r:header* r:link / /r:children:each So, it iterates over all of its children, printing out links in bullets. The r:header section only outputs text when the value of its contents changes (so in this case, when the month or year changes). Sean Ryan Irelan wrote: This has been eluding me, so I thought I'd post here for some direction. Does Radiant CMS do a archive page like this: http://radiantcms.org/blog/archives/ on its own? I'm fine with doing something custom, but want to be sure I'm not overlooking the obvious. -Ryan ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] New Radiant site(s)
Folks, Here's the moment you have all been waiting for (or at least I'd like to think)! For the past four to five months I have been working with the wonderful team at Digital Pulp to develop the new website for Redken. We are proud to say that it has had its official launch this morning! Check it out: http://redken.com - and - http://redkensalon.com It has been an incredible experience working with them, and the Radiant community has greatly benefited. We have released two new versions of Radiant and numerous extensions during this tenure. The following extensions were a direct result of my work for Digital Pulp: * shards (http://dev.radiantcms.org/svn/radiant/trunk/extensions/shards) * related_content (http://dev.radiantcms.org/svn/radiant/trunk/extensions/related_content) * reorder, the non-Ajax version (http://dev.radiantcms.org/svn/radiant/trunk/extensions/reorder) * scheduler (http://dev.radiantcms.org/svn/radiant/trunk/extensions/scheduler) * share_layouts (http://dev.radiantcms.org/svn/radiant/trunk/extensions/share_layouts) * multi_site (http://dev.radiantcms.org/svn/radiant/trunk/extensions/multi_site) I also intend to release a some more over the next weeks, after they have been cleaned up for public consumption, namely: * file_system - Save/load Radiant models to/from the file system so they can be managed in an SCM * templates - Structure pages externally and provide a customized interface for editing * asset_manager - A full-featured asset manager, with mass upload, asset expiration, usage reports, and FCKEditor integration A big thank you and congratulations to all of the team at Digital Pulp (in no particular order) -- John, Justin, Josh, Michael, Alex, Brian, Sarah, David; and to my good friend Scotty Moon who also helped on the project. Cheers, Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Proposal: Radiant Pros Wiki Page
Ryan, I think that's a great idea. Make it so. Sean Ryan Heneise wrote: Is anyone interested in building your Radiant business? A couple of times now I've wanted to refer potential customers to other Radiant professionals, but I don't know of any central place where you can find referrals, other than this list. And it's not feasible to send customers here to dig through a mailing list in search of names. So here's my proposal: Let's create a new page on the Radiant Wiki where we can list the companies or professionals who are working with Radiant. Let's do it in a format that helps customers find out more about our business, something like this: *Name of Radiant Pro* Brief intro or marketing mumbo jumbo, if desired Link to company site Link to portfolio site Contact email List of Radiant sites you've worked on I decided to go ahead and create the page at http://wiki.radiantcms.org/Radiant_Pros. What do you think? Should we keep it? Is there another place where this would be more appropriate? Is there already one that I'm missing? If we decide to keep it, feel free to add to the page. - Ryan ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] New Radiant site(s)
Sorry I didn't explain that! Only the US site(s) are hosted with Radiant. All of the international sites were untouched by this project. Sean Christopher Dwan wrote: This is awesome, what a benefit to all of us. Thanks! I'm really looking forward to the templates and asset_manager. Now on the flip side... can't you tell someone over there that in Canada we don't have zip codes? It's confusing - when I see 'zip code', most of the time it means I have to find the 'Canada' selector or Canadian addresses aren't allowed on that form. On this site, I pre- selected my country, so I should expect not to have to see the dreaded 'zip code' field. e.g. http://www.redken.ca/_en/_ca/salon/index.aspx? On 4-Feb-08, at 11:40 AM, Peter Berkenbosch wrote: Looks very good Sean! Congrats.! On Feb 4, 2008 8:17 PM, Jim Gay [EMAIL PROTECTED] wrote: Nice work! Thanks for releasing your extensions. Can't wait to see the new ones. On 2/4/2008, Sean Cribbs [EMAIL PROTECTED] wrote: Folks, Here's the moment you have all been waiting for (or at least I'd like to think)! For the past four to five months I have been working with the wonderful team at Digital Pulp to develop the new website for Redken. We are proud to say that it has had its official launch this morning! Check it out: http://redken.com - and - http://redkensalon.com It has been an incredible experience working with them, and the Radiant community has greatly benefited. We have released two new versions of Radiant and numerous extensions during this tenure. The following extensions were a direct result of my work for Digital Pulp: * shards (http://dev.radiantcms.org/svn/radiant/trunk/extensions/shards ) * related_content (http://dev.radiantcms.org/svn/radiant/trunk/extensions/related_content ) * reorder, the non-Ajax version (http://dev.radiantcms.org/svn/radiant/trunk/extensions/reorder) * scheduler (http://dev.radiantcms.org/svn/radiant/trunk/extensions/scheduler) * share_layouts (http://dev.radiantcms.org/svn/radiant/trunk/extensions/share_layouts ) * multi_site (http://dev.radiantcms.org/svn/radiant/trunk/extensions/multi_site) I also intend to release a some more over the next weeks, after they have been cleaned up for public consumption, namely: * file_system - Save/load Radiant models to/from the file system so they can be managed in an SCM * templates - Structure pages externally and provide a customized interface for editing * asset_manager - A full-featured asset manager, with mass upload, asset expiration, usage reports, and FCKEditor integration A big thank you and congratulations to all of the team at Digital Pulp (in no particular order) -- John, Justin, Josh, Michael, Alex, Brian, Sarah, David; and to my good friend Scotty Moon who also helped on the project. Cheers, Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- met vriendelijke groet, Peter Berkenbosch ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] multi_site extension
Not currently, but it shouldn't be very hard to do. Sean Arik Jones wrote: Haven't had a chance to try the extension out yet, but it would sure come in handy. I do have a few questions. Can you add users to a specific multi-site? And if so, are the secure measures in place that disallow users from editing sites they're not added to? ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] multi_site + search extensions, any suggestions for limiting results
No, you'll probably have to change the search extension to accommodate this, or write some tags of your own in a separate extension. Although the core of the multi_site functionality is in the extension, we also used it to restrict controllers to specific domains and invoked the Site model in other areas of the code. It is also not always a trivial matter to add a tag around some other tag to achieve the effect you want. Anyway, I will look into what would be required to make them compatible. Sean john muhl wrote: I had three 0.6.4 gem installs that merged into one this afternoon (put two on top of one). Thanks for the work that obviously into this and the shards extensions; I'm by no means a guru in these matters and the setup took less than an hour. I'm just looking for a little help trying to limit the search extension to the current domain. As it stands a search from domain X returns pages from the other two domains. I looked in the available tags and didn't see any way to use the radius tags to accomplish this. Are there any new radius tags added with the multi_site extension that just don't show up in the available tags interface that might be useful? Or some clever way to use the existing tags that I've just overlooked? thanks john ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Problem with virtual page(s) and find_by_url
It seems it might be appropriate for your PersonPage to be virtual and
the PeoplePage to override find_by_url as well.
Sean
nn wrote:
I have the following setup:
Home Page
|
-- People (PeoplePage)
|
-- Person (PersonPage)
|
-- Bio (BioPage)
-- Contact (ContactInfoPage)
I made an extension with some Page Types (in parentheses) wich are used to
display the list of people in the company and the data about a particular
person, respectively (the latter being a virtual page).
Since a person object carries plenty of data I need to split the data into
several pages, like:
/people/18 # 18 is an ID of a existing object (Person)
/people/18/bio
/people/18/contact
...
It seems I have a problem with find_by_url in PersonPage:
def virtual?
true
end
def find_by_url(url, live = true, clean = true)
url = clean_url(url) if clean
if url =~ %r{#{parent.url}/\d+/bio/?$}
children.find_by_class_name 'BioPage'
else
super
end
end
This looks fine to my untrained eye, but:
$ script/console
Loading development environment.
p = Page.find_by_url('/people/18/bio/')
= #FileNotFoundPage:0xb709db54 @attributes={virtual=1,
class_name=FileNotFoundPage, slug=file-not-found,
updated_at=2008-01-24 00:47:14, title=File Not Found,
created_by=1, breadcrumb=File Not Found, lock_version=2,
updated_by=1, id=3, published_at=2008-01-20 23:51:27,
status_id=100, layout_id=nil, parent_id=2,
created_at=2008-01-20 22:51:27}
Then, this works in the same console:
p = Page.find_by_url('/people/18/')
p.children.find_by_class_name 'BioPage'
Regexp looks fine too, as far as I can tell. I know this is a cockpit
problem, but I need someone to point a finger at it, since I must be (code)
blind or something. BioPage is declared virtual, too (if it matters). Can
anyone suggest what could be wrong?
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Problem with virtual page(s) and find_by_url
In this find_by_url method, you return the PersonPage if the URL is
/people/18, but you don't call its find_by_url if the URL is
/people/18/bio. Remove the $ from the regexp and then instead of
returning children.find_by_class_name('PersonPage'), return
children.find_by_class_name('PersonPage').find_by_url(url, live,
clean). Then in your PersonPage, have several tests -- one that matches
for itself (use the one below and substitute parent.url for self.url),
and then any special cases (/bio, /contact, etc) that return the
appropriate sub-page, then super.
If this is unclear, write me back and I'll give more detail.
Sean
nn wrote:
On Jan 29, 2008 9:42 PM, Sean Cribbs [EMAIL PROTECTED] wrote:
It seems it might be appropriate for your PersonPage to be virtual and
the PeoplePage to override find_by_url as well.
Hi Sean,
Thanks for the reply. Both of the PersonPage and the BioPage are virtual,
and in PeoplePage I have:
def find_by_url(url, live = true, clean = false)
url = clean_url(url) if clean
if url =~ %r{#{self.url}/?\d+/?$}
children.find_by_class_name 'PersonPage'
else
super
end
end
def child_url(child)
clean_url #{url}/#{child.id}
end
I can get the pages by Page.find_by_url for the
/people/
/people/18
but it doesn't work for
/people/18/bio
Its a wildest guess, but does it have anything to do with the fact that I'm
redefining find_by_url in a virtual page (per se)? I'd say no, but just to
be on the safe side...
nn wrote:
I have the following setup:
Home Page
|
-- People (PeoplePage)
|
-- Person (PersonPage)
|
-- Bio (BioPage)
-- Contact (ContactInfoPage)
I made an extension with some Page Types (in parentheses) wich are used to
display the list of people in the company and the data about a particular
person, respectively (the latter being a virtual page).
Since a person object carries plenty of data I need to split the data into
several pages, like:
/people/18 # 18 is an ID of a existing object
(Person)
/people/18/bio
/people/18/contact
...
It seems I have a problem with find_by_url in PersonPage:
def virtual?
true
end
def find_by_url(url, live = true, clean = true)
url = clean_url(url) if clean
if url =~ %r{#{parent.url}/\d+/bio/?$}
children.find_by_class_name 'BioPage'
else
super
end
end
This looks fine to my untrained eye, but:
$ script/console
Loading development environment.
p = Page.find_by_url('/people/18/bio/')
= #FileNotFoundPage:0xb709db54 @attributes={virtual=1,
class_name=FileNotFoundPage, slug=file-not-found,
updated_at=2008-01-24 00:47:14, title=File Not Found,
created_by=1, breadcrumb=File Not Found, lock_version=2,
updated_by=1, id=3, published_at=2008-01-20 23:51:27,
status_id=100, layout_id=nil, parent_id=2,
created_at=2008-01-20 22:51:27}
Then, this works in the same console:
p = Page.find_by_url('/people/18/')
p.children.find_by_class_name 'BioPage'
Regexp looks fine too, as far as I can tell. I know this is a cockpit
problem, but I need someone to point a finger at it, since I must be
(code)
blind or something. BioPage is declared virtual, too (if it matters). Can
anyone suggest what could be wrong?
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] share_layouts extension 0.3
I have committed a few changes to the share_layouts extension which bring it to version 0.3. * ShareLayouts::RailsPage is now just RailsPage * You can create RailsPage models (which show up as Application) in the page tree, which has these advantages: o You can create a dummy representation of a custom controller in the tree o You can use the page in generation of navigation, etc. o Any controller that uses a Radiant layout will search for a RailsPage that matches the current request URL to use as context for the layout, i.e. you can generate content with tags, snippets, etc. This is not really a change, but I realized while working on this version that it is possible to output Radius from your ERb templates, which will then be rendered within the layout and is nice if you need to use snippets or other built-in features of Radiant. Here's to tighter integration! Cheers, Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] multi_site extension
This email is to announce the release of the multi_site extension, available from the Radiant repository: http://dev.radiantcms.org/svn/radiant/trunk/extensions/multi_site multi_site is a solution for hosting sites with multiple domain names on a single Radiant installation and is in use on an upcoming production site. Rather than having sub-trees which represent individual sites with the configuration in the root page (a la virtual_site), each site has its own tree with a single root page. multi_site requires the shards extension and the trunk version of Radiant (use rake radiant:freeze:edge). Cheers, Sean P.S. I will be filling out the README more fully later, sorry about that! ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] nested layouts?
That's an interesting solution, in principle similar to the solution I
had for the same problem. However, there are some very un-Rails-ish
statements in your tag implementation that make your intentions
unclear. For example, you find PageParts by their page_id, when really
you should use the existing association:
ancestor_part_names = ancestor.parts.map(:name)
Next, you use Array.detect where include? will suffice:
if ancestor_part_names.include?(layout_name)
Radiant's page model offers a shortcut method to getting a part by name,
so your next detect call is also unneeded. In fact this whole block of
statements can be replaced by one line:
tag.locals.page = ancestor if ancestor.part(layout_name)
Page#part will return nil if no matching part is found. Better yet, use
find/detect instead of each:
tag.locals.page = page.ancestors.find {|p| p.part(layout_name) }
There are several other things in your tag definitions that could use
attention, I'll probably make a pass at them later.
Sean
Witter Cheng wrote:
I have revived this post in order to get comments on my implementation
of nested layouts. I created custom tags to allow for this. Here is my
solution to the scenario given above.
First, in /, create a page part called layout to be used as the
nested layout. It will look like this:
r:layout_part name=left
div class=left
r:content part=left /
/div
/r:layout_part
r:layout_part name=main
div class=main
r:content part=main /
/div
/r:layout_part
Then edit the body page part of page1 and page2 to look like this:
r:layout /
The code behind r:layout and r:layout_part follows:
-
# the layout is actually a page part
# if the named page part is not a part of the current page
# ancestors are searched until the named page part is found
tag 'layout' do |tag|
ret_val =
layout_name = tag.attr['layout_name'] || layout
page = tag.locals.page
page_part_names =
page.instance_variable_get(:@parts).collect(:name)
parts_for_layout = tag.attr['parts'] ||
page_part_names.delete_if{|part| part == body || part == layout_name }
found = nil
og_page_id = page.id
if !page_part_names.include? layout_name
page.ancestors.each do |ancestor|
pp =
PagePart.find_all_by_page_id(ancestor.instance_variable_get(:@attributes)[id],
:include = [:page])
ancestor_part_names = pp.collect(:name)
if ancestor_part_names.detect{|part| part == layout_name
} !found
tag.locals.page = pp.detect{|p| p.name ==
layout_name}.page
found = 1
end
end
tag.render('content', {part = layout_name,
parts_page_id = og_page_id})
else
tag.render('content', {part = layout_name})
end
end
tag 'layout_part' do |tag|
part_to_render = tag.attr['name']
# this mess is necessary; trying to get tag_binding_stack
directly from the context returns a different array
page = tag.locals.page
response = page.instance_variable_get(:@response)
template = response.instance_variable_get(:@template)
controller = template.instance_variable_get(:@controller)
pagee = controller.instance_variable_get(:@page)
context = pagee.instance_variable_get(:@context)
tbs = context.instance_variable_get(:@tag_binding_stack)
parts_page_id = tbs.last.attributes[parts_page_id]
# if the layout is in the same page as the parts being laid out
# the parts_page_id will not have been specified, so do not
reset the tag page
unless parts_page_id.blank?
parts_page = Page.find(parts_page_id)
tag.locals.page = parts_page
end
# e.g. name of part is specified in the tag as 'blah'
# but the page calling the layout tag which wraps this tag does
not have a 'blah' part
# in such a case don't display this tag
# NOTE: there is likely a more efficient way to do this check
than a db query
pp = PagePart.find_by_name_and_page_id(part_to_render,
parts_page_id || tag.locals.page.id)
tag.expand unless pp.blank?
end
-
Thank you in advance for any criticism/comments.
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant on Merb
Radiant is tightly coupled to Rails at the moment, but it would be an interesting academic exercise. Someone at Boulder.rb suggested that we might use gem plugins as an alternative to extensions, which IIRC is the Merb Way. Sean Stephane B. wrote: Has anybody though, tried or made a use of Radiant on Merb[http://merbivore.com/] framework yet? -- Stephane ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radius tag from rails helper?
The only case where you would want to do that is if you wanted to generate the links inside a page (not a regular view). Is that what you're trying to do? If not, just use the helper as-is in your views. Sean Mariano Viola wrote: Hi all, I've created an extension that use the rails paginating find plugin http://cardboardrocket.com/pages/paginating_find; and it work well on the controller side. But at this point can I create a radius tag that wrap the paginating_links() method exposed from the helper (already activated in my extension) that generate automatically the pagination? Thanks, Mariano ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to make a virtual page like '/page/:id'
You're on the right track. The /people page should be of a custom type that you create so that all child URLs are routed to a single virtual child page. I did this for the Syllabi at KCKCC over a year ago. Here's a link to the code: http://kck.esumm.com/www/html/vendor/extensions/syllabi/app/models/ Look specifically at the Syllabi Courses Page and the Syllabi Prefixes Page. The prefixes page was used as the parent, the courses page as the virtual child. You can see these in action at: http://www.kckcc.edu/academics/course-descriptions/ Cheers, Sean nn wrote: While developing my first Radiant site I encountered a problem which overwhelms me. Also, I'm not a programmer, so its only worse. Please bear with me. First, I tried to make a page /people which lists all the people in the organization. So, I wrote People extension (my first), wrote some tags, and now I can enter a person into the database through the admin interface, and list every person in the database on the /people page. A small victory. Unfortunately, it doesn't end here. Now I need to display everything there is about a person, but I don't want to make a separate child page for each person. I think one page should be sufficient for that, so a virtual page is in order, right? Well, I tried that, and failed miserably. It getting frustrating, since I've been hanging with Google for more then two days now. Either the examples I found are too complex, or my skull is too thick. At the moment, I'm betting on the latter. So, hopefully, someone has already been there and can show in a simple way how to achieve what I need to. Thanks. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to make a virtual page like '/page/:id'
Thanks Sean. To my surprise, somehow I managed to make it work not long after clicking on the send button. I also found your extension which helped somehow, together with the archive extension. Who would say that simply stearing long enough at the code you don't really understand could get you somewhere. :) My head is spinning, but its fun. Now I need to make use of model associations. I see the syllabi is associated with courses etc, but haven't found yet how you use it in the tags. Look in lib/syllabi_tags.rb for how the majority of the tags are defined. Basically, there's r:prefix, r:courses, r:syllabi tags and various others below it. All they do is assist in looping over the associations and emitting attributes, really. Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Processing unrelated nested Radius tags
David Piehler wrote: John Long wrote: On 1/16/08, David Piehler [EMAIL PROTECTED] wrote: r:attachment:image name=r:photor:photo:name //r:photo alt=photograph / This fails because Radius can't parse tags that are within attributes. Why are you trying to do this? Is there a way to accomplish what you want without using tags within attributes. My goal was to have a person's name in the DB generate a filename that I could pass to the page_attachments tag to grab. Example: David Piehler - david_piehler.jpg - r:attachment:image name=david_piehler.jpg / As you've said though, something like this is not possible due to the way Radius tags are parsed. Thanks for clarifying this. I've since taken a more heavy-handed approach to solve it. David, The way I've found to do this is to use nested Radius tags that pass information back up to the parent. However, the page_attachments tags are currently not structured to support this. If they were, it might look like this: r:attachment:imager:namedavid_piehler.jpg/r:name/r:attachment:image Obviously, you would use some of your own tags to generate the name. Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Javascript on the admin page
Oleg Shelomov wrote: Javascript on the admin page doesn't work. 'More', 'Filter', 'Available Tags' don't render required fields and pop windows. (Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.2) Gecko/20070721 Firefox/2.0.0.2). In the error console I have got the message: 'Element.toggle is not a function' for .../admin/pages/edit/1. I have tried to do the same in konqueror and in IE (in WMWare). I get the same javascript behavior. Can somebody give me an advice what should I do? Oleg, If this is an existing Radiant project, make sure to run rake radiant:update when you install a new gem. The Radiant admin JS has been refactored by Mislav in 0.6.4 to be compatible with Prototype 1.6. Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Reorder extension - buggy?
Ideally, when you run the included migration, it should put all pages in a default order based on the title. Unfortunately, there are serious weaknesses to acts_as_list that cause it to break when any records get inserted inconsistently. I'd appreciate any tests/patches that could identify and resolve this issue. Sean Naohiro Yoshida wrote: Mario T. Lanza wrote: When I try to move a page, it has unpredictable results. They don't seem to properly relocate. I encountered the same phenomenon before, having data incorrect. position has to be unique in a certain parent_id. If you get no empty result executing following SQL(when you use MySQL), you should modify position data first. select * from `pages` group by parent_id,position having count(*) 1; ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Partial Caching - Extension Idea
Mario, You might look into RevolutionOnRails' Edge-side includes plugin, which essentially uses directives like server-side includes to move fragment caching into the server layer rather than the application layer. However, if your pages are taking a long time to render, it's probably worth profiling them with ruby-prof before you consider adding infrastructure. In optimizing some of my past Rails apps, I found inefficient algorithms more often than I found the need to add caching. Sean Mario T. Lanza wrote: In the Radiant-based application I'm developing, it is necessary to dynamically generate pages rather than allow for caching. The frustrating part of this is that for most pages the majority of the page is static content. Only bits of the page are dynamic. Nevertheless, this requirement necessitates that caching be turned off. I hate having to take one benefit and throw it out the window because of a separate need which takes precedence. This got me thinking about a hybrid solution, a way of allowing the majority of the page to be cached while also allowing the dynamic bits to be generated on every page rendering--the best of both worlds, no sacrifices. The way I devised for handing this in an extension which extends Radius to accept a cache attribute (which defaults to 'yes' when not supplied) on all tags: r:snippet name='current_user' cache='no' / Such tags when encountered, would be written as is to the cache file without expanding them. Later, in response to a page request the page is rendered from the cache and such tags are dynamically expanded at that moment. IMPLEMENTATION NOTE Nested tags... r:special_tag cache='yes' r:inner_tag / /r:special_tag r:some_tag cache='no' r:inner_tag cache='yes' / /r:some_tag ...become on the cached page... SPECIAL OUTPUT FROM TAGS r:some_tag cache='no' r:inner_tag cache='yes' / /r:some_tag ...whereby inner tags regardless of their cached attribute are left alone. TAKING IT FURTHER Though I don't see this as necessity, a slightly more advanced version would accept a time period in the cache attribute. r:uber_impressive_tag cache=5 minutes / Then when generated to the cache (at 5pm) we save the tag as: r:uber_impressive_tag cached_until=2008-01-10 5:05 PM / Other than timezone issues, the final details of implementation are obvious. TAKING IT STILL FURTHER Snippets would include a never cache checkbox so that you wouldn't need to remember which ones required the cache='no' setting every time you made use of them. I'm sorry that numerous responsibilities prevent me from focusing on this anytime soon. Furthermore, it might take me far longer to learn to do what another experienced Radiant developer could accomplish in several hours. Does this seem useful? Is it a good approach? Thanks for any feedback. Mario PS: Orginally I had added this to the documentation wiki Extension Ideas page, but somehow it got lost. I am sure it was there at one point because I viewed it after saving the edit. I checked the revision history, no sign of it. Frustrating. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Standard Rake Install/Uninstall Tasks for Extensions
I've kind of kept out of this discussion so far, but there does exist an
'update' task that is generated for new extensions since 0.6.3 (I
believe). It copies files from the extension's public folder to the
project/instance public folder. However, there is no reverse operation
for it currently. I imagine the tasks might look something like this
(cleanup would be the reverse of update):
task :install = [:migrate, :update]
task :uninstall = :cleanup do
ENV['VERSION'] = 0
migrate
end
Sean
Todd Willey wrote:
On Jan 10, 2008 8:01 PM, John Long [EMAIL PROTECTED] wrote:
On 1/10/08, Mario T. Lanza [EMAIL PROTECTED] wrote:
Added a tiny section called Standard Rake Tasks to:
http://wiki.radiantcms.org/Creating_Radiant_Extensions
Why not put those tasks in the generated Rakefile and just have them
do nothing by default?
We could also make assets/{javascripts,stylesheets,images} directories
and have the install task copy files from those directories to their
counterparts in public by default (but should not overwrite something
already there, probably).
-todd[1]
Perhaps that should be put at the bottom in an Additional Notes
section? Or even better truly work it into the tutorial by adding an
code examples and screenshots.
--
John Long
http://wiseheartdesign.com
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Standard Rake Install/Uninstall Tasks for Extensions
If you (anyone in this thread) want this, please implement it, test it and submit a patch. Sean Andrea Franz wrote: Maybe we can use a standard way to organize files for each extension.Something like: public/images/extensions/newsletter/ (here all images added by the newsletter extension) public/stylesheets/extensions/newsletter/ (here all css added by the newsletter extension) public/javascripts/extensions/newsletter/ (here all js added by the newsletter extension) It could be easier to remove files. What do you think about it? On Jan 11, 2008 6:46 PM, Chris Parrish [EMAIL PROTECTED] wrote: Sean Cribbs wrote: I've kind of kept out of this discussion so far, but there does exist an 'update' task that is generated for new extensions since 0.6.3 (I believe). It copies files from the extension's public folder to the project/instance public folder. However, there is no reverse operation for it currently. I imagine the tasks might look something like this (cleanup would be the reverse of update): task :install = [:migrate, :update] task :uninstall = :cleanup do ENV['VERSION'] = 0 migrate end I've used the built-in rake 'update' task and was wondering how it was different from the 'install' being proposed here. You're right Sean, they're really asking for both: rake production radiant:extensions:my_extension_name:update and, rake production radiant:extensions:lmy_extension_name:migrate However, what is also being asked here but can get sticky is an 'un-update' task which, at this point, doesn't exist. IMHO, it should do the following: * Take an inventory of all the files in the extension's public folders that would be copied by the 'update' task. * Look for those files in the application's public folders and: o If they exist and are an exact (binary) match, delete them o If they are exist but are different (same name, different file), leave them alone o If they don't exist, do nothing. * Spit out a report showing which files were deleted, which weren't and why, and which were expected but missing. That way people could update a css file or change a jpeg that came with their extension and not have to worry that uninstalling would erase their work. But I'm not sure what ruby offers to aid in performing a diff-check against two files, though. Ideas anyone? -Chris ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Woes of read-the-code documentation
Theoretically, one could modify the ResponseCache class to use memcached. I wonder what the performance increases would be like. However, you are right in suspecting that the directory change is the problem... the default environment.rb sets the ActionController cache directory to RAILS_ROOT/cache IIRC. Sean Andrew O'Brien wrote: Hi Mario, Sorry to hear about your problems -- that sounds like it could have seriously sucked without source control! I was wondering though: what kind of safe-guards you'd want to incorporate in the caching mechanism? I agree that clearing a directory is dangerous, but IIRC, default Rails caching does something similar (maybe with options for more fine-grained control). Out of curiosity, why did you change the cache directory if you had turned off caching? (That was the problem here, right? That Rails page caching goes to the public dir?) -Andrew On Jan 5, 2008 11:03 AM, Mario T. Lanza [EMAIL PROTECTED] wrote: I apologize for coming across a little harsh. No disrespect intended to anyone. :) -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] newsletter extension 0.1.0
Nice work, Andrea! Nice use of shards, too. I'm glad to see I'm not the only one using it successfully. Sean Peter Berkenbosch wrote: Yiha ! This really rocks. (I still have to check it out) I was planning in writing a newsletter extension. I will check it out and will try to help/test/patch there were needed. Peter. On Jan 4, 2008 4:29 PM, Andrea Franz [EMAIL PROTECTED] wrote: Hi there!! I'm working on a new extension that allows to manage newsletters. Basically a page can be a newsletter (NewsletterPage type) and it has its own subscribers. Each one of its children is an email to send. If you want to try it you can check it out with: svn co http://dev.gravityblast.com/svn/projects/radiant/extensions/newsletter/ It's a super beta version but it should work. Let me know what you think! thank you very much...and an happy new year! :) -- Andrea Franz http://gravityblast.com - http://nimboo.net ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] writing extensions - custom (non-scaffold) views
Jan, First, if your controller is public-facing (and not an admin tool), put this line at the top to disable the login requirement: no_login_required Second, your views should correspond to the _controller name_, not the extension name, unless of course they happened to be named the same thing. So if your controller is Admin::FooController, your view path should be app/views/admin/foo. Third, in most cases, you should be passing objects as instance variables to views, not locals, although there should be nothing to stop you from explicitly rendering the view with locals. Sean Jan Rietema wrote: I'm currently writing my first proper extension and am having problems with custom views for the admin tab. I'm not using scaffold since the extension isn't model-based. I noticed a few things that struck me as awkward but that I could work around, including: - not being able to use filters in my controllers (they are ignored) - having to place my views in /app/views/admin/(extension_name) rather than just /app/views/admin Something I'm not getting to work is passing locals to the view or using references to instance variables. In all cases, I have a nil object rather than a reference to the objects the controller sees / instantiates. Is this a known problem? Regards, Jan ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] PageMeta Extension
It goes back to 0.6.0 so you should be safe ;). Sean Chris Parrish wrote: Made some updates over the weekend. It doesn't need Shards now (actually didn't really before) so this should work for older versions of Radiant too (as long as the PageController and page/edit.rhtml work with the @meta array which I think goes back pretty far). Here's the latest svn version: https://secure.svnrepository.com/s_swanki/open/radiant/extensions/page_meta/tags/v0.1.5/ -Chris ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Hiding Extensions
You could duplicate and override the main view layout, application.rhtml, and remove the Extensions link. Sean Chris Parrish wrote: I'm working on some extensions that I'd like to keep the user from turning off. Is there some way to keep users from disabling (or, better yet, even seeing) extensions in the admin ui? It seems like Shards would be a candidate for this too (I'm not sure I want a user to be able to turn Shards off while leaving my dependent extensions live). -Chris ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Hiding Extensions
Almost forgot... plain users don't have access to Extensions, IIRC. Don't give them the admin or developer role and you should be fine. Sean Chris Parrish wrote: I'm working on some extensions that I'd like to keep the user from turning off. Is there some way to keep users from disabling (or, better yet, even seeing) extensions in the admin ui? It seems like Shards would be a candidate for this too (I'm not sure I want a user to be able to turn Shards off while leaving my dependent extensions live). -Chris ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Snippets
Changing a snippet should cause the entire cache to be cleared. We will write some specs to verify this. Barring that, you can always click Clear page cache on the Pages tab. Sean Chris Barnes wrote: Does anyone know why whenever I edit a snippet it doesn't show up on the site until I open the layout its used in and save that file again? ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Redirecting from index page
Why not make the blog page your root page? Your other alternative is to use the content of the blog page as the content of your homepage, like so: r:find url=/blogr:content //r:find There are ways to make a page render a redirect, and I'm working on one right now, but you might not want that for the root of your site, people will get annoyed and you might get downgraded by search engines. Sean Matias Pelenur wrote: Hi there, I've just started using Radiant for a new site (fortgreene.org) and like it a lot so far. I'd like to add a rudimentary blog to the site using Radiant. I saw that there's the Archive page type, and my plan was to create a new child of the Home page using a different layout, and then add one child for each blog post to that page. Is there an easy way to redirect from the Home page to this blog archive page? I couldn't find anything other than the language redirect extension. I was going to write a really simple custom tag to do so, but perhaps I'm missing something obvious. Thanks, matias ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Snippets
Inside your Radiant project, run `rake radiant:freeze:edge`. Sean Chris Barnes wrote: Cool, Do you run any production sites on the trunk and have you had any headaches doing so? How would you go about upgrading from the gem to the trunk? On Dec 28, 2007 6:36 PM, Thomas Bell [EMAIL PROTECTED] wrote: Yep, this is fixed in with the latest trunk release for me. --Tom On Dec 28, 2007 3:09 PM, Chris Barnes [EMAIL PROTECTED] wrote: I'm using 0.6.4 the gem version. On Dec 28, 2007 4:39 PM, Thomas Bell [EMAIL PROTECTED] wrote: What version are you at. I had to upgrade to trunk to fix this. --Tom On Dec 28, 2007 8:54 AM, Chris Barnes [EMAIL PROTECTED] wrote: I have just confirmed that clicking Clear page cache does not cause the snippet to be updated on the site. The only thing I can do to get the snippet updated is to re-save the layout that the snippet is included in. I'm not sure if it matters but I'm running in development mode using mongrel on OSX 10.5. If I can help out at all with this issue, I would be happy to, just point me in the right direction. On Dec 28, 2007 10:23 AM, Sean Cribbs [EMAIL PROTECTED] wrote: Changing a snippet should cause the entire cache to be cleared. We will write some specs to verify this. Barring that, you can always click Clear page cache on the Pages tab. Sean Chris Barnes wrote: Does anyone know why whenever I edit a snippet it doesn't show up on the site until I open the layout its used in and save that file again? ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] etra quote in cached filename
This question is more appropriate for the rails-talk list. Please direct your question there. Sean Noha Mostafa wrote: Hi all, m having a problem when caching pages with parameters, although static pages went fine and I had an x.html in the folder /public/controllername/x.html. Now if this X accepts any parameters, let's say 1, i was expecting to find : /public/controllername/x/1.html but instead i found : /public/controllername/x/1'.html Can anyone explain this extra single quote, I've searched a lot, but couldn't find any1 w a similar problem :( Thanks, Noha ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Uninstalling an extension and go live with sqlite3
Christian, Simply delete the vendor/extensions/reorder directory and you'll be good to go. Sean Christian Billen wrote: Hi everyone, I was wondering if there was a way to remove an extension from radiant. I have both the copy/move and the reorder installed and only the reorder appears in the admin console. Until there is a way for those to co-exist, I would like to get rid of the reorder *without* having to destroy and recreate the content of my database. Any help on this would be appreciated. Also we are going live with our new radiant site on new year, i'm getting a little nervous and wonder if using sqlite3 as the database back end is a wise choice and will cause performance degradation. Once live the site will rarely be modified. Thank you all and merry christmas. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Uninstalling an extension and go live with sqlite3
Yes, but it's not absolutely necessary. Reorder adds the 'position' column, but it can safely be ignored if he doesn't want to migrate down. Reorder doesn't touch the stock JS/CSS files, however, it does dynamically modify the interface using Shards. Sean Andrew O'Brien wrote: Sean: what about any database changes? If he wants to clean up, won't he have to migrate down? Also, I seem to remember those extensions modifying the Admin JS or CSS files (although this was awhile ago)? Will he have to restore those too? -Andrew On Dec 21, 2007 10:25 AM, Sean Cribbs [EMAIL PROTECTED] wrote: Christian, Simply delete the vendor/extensions/reorder directory and you'll be good to go. Sean Christian Billen wrote: Hi everyone, I was wondering if there was a way to remove an extension from radiant. I have both the copy/move and the reorder installed and only the reorder appears in the admin console. Until there is a way for those to co-exist, I would like to get rid of the reorder *without* having to destroy and recreate the content of my database. Any help on this would be appreciated. Also we are going live with our new radiant site on new year, i'm getting a little nervous and wonder if using sqlite3 as the database back end is a wise choice and will cause performance degradation. Once live the site will rarely be modified. Thank you all and merry christmas. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] limiting children from r:aggregate
r:aggregate is not able to do this currently, but I'd appreciate a well-tested patch (hint, hint). Sean Jim Gay wrote: I'm trying to aggregate several pages and then limit their children. r:aggregate ... for 10 urls r:children limit=1 r:children limit=3 offset=1 ... What I want is to display 1 + 3 children. What I'm getting is 1 + 20. I think that what is happening is that the offset is applying to each url, and not being applied to the aggregated results. Is the aggregate tag able to do this? -Jim ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] File uploads in comments
This would be best as a separate extension. I just suggested that some of the same ideas could be employed in it. Sean Sean Cribbs wrote: You might be able to rip some of the ideas from page_attachments. It has good examples of how to handle an associated model with upload. Sean In fact, it would be best to have an extension that's something like page_attachments with comments - I guess that may be an often required thing. Sean, would it be fair to say that all that should be required are 4 things: 1. An additional migration to extend the page_attachments table 2. A UI to capture the comment - I think that it is a partial that needs modifying 3. Something to save it to the table, probably where page_attachments saves its image path 4. A tag to retrieve the comment I imagine it could be bolted onto page_attachments but I don't know how much trouble it will be to keep it updated as page_attachments changes... Cheers, Mohit. 12/20/2007 | 12:24 AM. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Custom CSS File
' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/mongrel- 1.0.1-mswin32/lib/mongrel.rb:736:in `run' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/mongrel- 1.0.1-mswin32/lib/mongrel.rb:736:in `initialize' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/mongrel- 1.0.1-mswin32/lib/mongrel.rb:736:in `new' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/mongrel- 1.0.1-mswin32/lib/mongrel.rb:736:in `run' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/mongrel- 1.0.1-mswin32/lib/mongrel.rb:720:in `initialize' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/mongrel- 1.0.1-mswin32/lib/mongrel.rb:720:in `new' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/mongrel- 1.0.1-mswin32/lib/mongrel.rb:720:in `run' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/mongrel- 1.0.1-mswin32/lib/mongrel/configurator.rb:271:in `run' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/mongrel- 1.0.1-mswin32/lib/mongrel/configurator.rb:270:in `each' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/mongrel- 1.0.1-mswin32/lib/mongrel/configurator.rb:270:in `run' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/mongrel- 1.0.1-mswin32/bin/mongrel_rails:127:in `run' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/mongrel- 1.0.1-mswin32/lib/mongrel/command.rb:211:in `run' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/mongrel- 1.0.1-mswin32/bin/mongrel_rails:243 C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/radiant- 0.6.4/vendor/rails/activesupport/lib/active_support/dependencies.rb:488:in `load' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/radiant- 0.6.4/vendor/rails/activesupport/lib/active_support/dependencies.rb:488:in `load' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/radiant- 0.6.4/vendor/rails/activesupport/lib/active_support/dependencies.rb:342:in `new_constants_in' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/radiant- 0.6.4/vendor/rails/activesupport/lib/active_support/dependencies.rb:488:in `load' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/radiant- 0.6.4/vendor/rails/railties/lib/commands/servers/mongrel.rb:60 C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/radiant- 0.6.4/vendor/rails/activesupport/lib/active_support/dependencies.rb:495:in `require' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/radiant- 0.6.4/vendor/rails/activesupport/lib/active_support/dependencies.rb:342:in `new_constants_in' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/radiant- 0.6.4/vendor/rails/activesupport/lib/active_support/dependencies.rb:495:in `require' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/gems/1.8/gems/radiant- 0.6.4/vendor/rails/railties/lib/commands/server.rb:39 C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' C:/a_Systems/InstantRails-1.7-win/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' script/server:3 On Dec 2, 2007 2:02 PM, Sean Cribbs [EMAIL PROTECTED] wrote: Richard, This is rather trivial to do with an extension. Write your desired CSS, put it in your extension public/stylesheets directory. Then put something like this in your extension's activate method: SiteController.class_eval do before_filter :customize_admin_css def customize_admin_css include_stylesheet 'my_stylesheet' end end Obviously you'd want to name your stylesheet something else. Hope this is helpful! Sean Richard Hurt wrote: Putting the controls on a sidebar is OK with me. I would even be fine with a smaller text for the page title and various controls. I'm screen height challenged, not blind. :) Hmmm...what about a way to customize the CSS of the Admin pages for each install? Would that work? It wouldn't even have to be anything fancy like a table in the DB, just a static file on the server would work for me. We could then change the look feel of the pages pretty easily and to fit within our own guidelines. Later... Richard On Dec 2, 2007 3:08 PM, Ryan Heneise [EMAIL PROTECTED] wrote: I think I prefer having the buttons underneath the form, because it is more standard and fits the open-edit-save workflow. Moving the buttons to the top breaks with convention. What about a 2-column layout (similar
Re: [Radiant] Securing the Admin page
Richard, I would use your webserver's capabilities to restrict requests to that path to be over SSL. I believe this is fairly easy to do with Apache, and I have a vague idea of how to do it with nginx. Unfortunately, I don't do it that often and so I can't provide you any snippets. Sean Richard Hurt wrote: Now that I have my Radiant powered site up and running (thank you very much!) I am getting a bit anxious about the /admin page being exposed to the world. Not that I'm a big target or anything, but I really don't want to have to depend on my password skills to make sure my site stays the way it is. What I would like to do is two fold. First I want to for the /admin page to be SSL only. What's the best way to go about this? I am going to have a self signed certificate for now as it's only me doing the editing, but I would like to keep the editing sessions private. At the very least I have to secure the initial logon page, even if I don't secure the entire /admin/... route. Second I would like to change the admin route from /admin to something else, maybe /edit, or /blahblah. What's the best|easiest way to do this? I know security by obscurity is no security at all, but I would like to at least give the script kiddies something to chew on. :) Thanx! Richard P.S. I apologize if this is in the Wiki - I searched but couldn't find anything on it. I'll update the Wiki if I get it working. How's that? :) ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] wiki down
$ nslookup georgia.textdrive.com Server:10.0.1.1 Address:10.0.1.1#53 Non-authoritative answer: Name:georgia.textdrive.com Address: 207.7.107.246 $ nslookup wiki.radiantcms.org Server:10.0.1.1 Address:10.0.1.1#53 Non-authoritative answer: Name:wiki.radiantcms.org Address: 207.7.107.246 Adam Williams wrote: I'm 99% certain that it is, actually. On Dec 14, 2007, at 10:36 AM, Sean Cribbs wrote: It's possible the wiki is on Georgia: http://help.joyent.com/index.php?pg=forums.postsid=689pc=8 Sean Aitor Garay-Romero wrote: Yesterday and today ? /AITOR ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] wiki down
Thank you, I will restart it. Sean Aitor Garay-Romero wrote: Yesterday and today ? /AITOR ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] wiki down
My apologies. I tried, but it seems the wiki is on a different host than the other sites. I imagine it's on the same host as John's personal site, which has been down since yesterday too, ironically the day he left town and will be without internet access. Sean Aitor Garay-Romero wrote: Yesterday and today ? /AITOR ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] File uploads in comments
You might be able to rip some of the ideas from page_attachments. It has good examples of how to handle an associated model with upload. Sean Ryan Heneise wrote: Does anyone have an extension that would allow site visitors to upload pictures with their comments? ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant w/ Multiple Sites: How does it actually work?
The way the virtual domain extension works is to read the hostname from the incoming request, then use that to decide which immediate child of the root page should be accessed. The root page of the Radiant installation is given a Virtual Page type and a config part (tab) that contains the configuration. Sean Travis Robertson wrote: I want to use Radiant to host multiple sites. I've read the article on how to configure the directory structure, etc. My question pertains to how it actually works. I looked at the database, and I don't see anything that designates which site pages or their snippets belong to. If I have mysite1.com and mysite2.com both residing under the same installation, how does radiant know which page in the database is the default page for mysite1.com and which page is the default page for mysite2.com ? I didn't see anything in that article that even referred to database configuration modifications. So any help you can provide to a rails newbie is appreciated. Cheers, Travis ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Sitecontroller instance variable in custom tag
Dave, You probably need to explicitly set the instance variable on the page by overriding process_page. Here's a sample (untested): Page.send :attr_accessor, :my_instance_variable SiteController.class_eval do def process_page_with_instance_var(page) page.my_instance_variable = @my_instance_variable process_page_without_instance_var(page) end alias_method_chain :process_page, :instance_var end From that, your instance variable would be defined on the global page (tag.globals.page). I've been looking through the Rails source, but I don't see anywhere where the request is given a link back to the controller it's created for. You may be out of luck there. Cheers, Sean Dave Bryand wrote: Hi, I'm trying to figure out how to access the value of an instance variable that gets setup on SiteController when my extension is activated. I'd like to use this value in a tag, but I can' figure out how to access that variable from the tag. If I setup a tag that just dumps the page.inspect, like the tag below, I can see the instance variable in the output, but I just can't figure out how to grab it. tag 'inspect_page' do |tag| tag.globals.page.inspect end I'd like to be able to do something like tag 'my_instance_variable' do |tag| # @my_instance_variable is defined in SiteController on extension activation tag.globals.page.my_instance_variable end Anyone know how to do this? Thanks! ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Structured Content
Tristan, I would recommend something else entirely. If your data is very field-oriented (not lots of plain text), create an extension with a model or set of models that more properly map to the problem, create controllers to administer them, and then create Radius tags to output their information into a page. While I have created an extension that does something similar to TYPO3's FCE (although Radiant is not a page builder-style CMS like TYPO3), it's not ready for public consumption yet. The extension essentially allows you to define a 'template' for any given page and use the template to constrain both the output and the structure of the UI that is presented to the content editor. I hate to tease all of you with these vapor-ware extensions, but I promise I will release them in early January when I have a few days to clean them up. Sean Tristan Koch wrote: Hi, I was wondering: what is the recommended way to model structured content in Radiant? Say, I want to have a list of contact items: Department #1 Image of Department #1 Name Adress E-Mail Picture Name Adress E-Mail Picture (…) Department #2 Image of Department #2 Name Adress E-Mail Picture Name Adress E-Mail Picture (…) I can think of two possible solutions: #1 a page for each box with subpages, where each subpage has tabs with the fields (e.g. description, image). #2 an extension that overrides the normal body and instead displays a form for each set, with the ability to add a new set by clicking on a + button. In this example, there would be two pages with a specific type (=contact). [somewhat similar to Typo3 XML based Flexible Content Elements, aka FCE] Maybe I'm wrong, but to me #1 doesn't appear very user-friendly, especially if there are many fields. Is there an extension that offers features similiar to #2? Thanks Tristan ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Structured Content
You can add tabs to the Radiant interface in your extension that point to the url of your custom controller that handles manages your structured data. Rather than replacing the interface, you would create Radius tags that expose the data to a regular page. All of this is explained extensively in the extensions tutorial on wiki.radiantcms.org. Have a look! Sean Tristan Koch wrote: Hi Sean, Creating an extension with a specific model seems to be a good option, although I'm very curious about your template extension! Still, I'm not sure where to put the UI of the controller. It handles content, so I should be in the Page Tab. But then, I would need to replace the body from the Page editing UI. Does Shards support this? Or would you recommend to put the UI in a seperate Tab (like Gallery). Tristan Sean Cribbs schrieb: Tristan, I would recommend something else entirely. If your data is very field-oriented (not lots of plain text), create an extension with a model or set of models that more properly map to the problem, create controllers to administer them, and then create Radius tags to output their information into a page. While I have created an extension that does something similar to TYPO3's FCE (although Radiant is not a page builder-style CMS like TYPO3), it's not ready for public consumption yet. The extension essentially allows you to define a 'template' for any given page and use the template to constrain both the output and the structure of the UI that is presented to the content editor. I hate to tease all of you with these vapor-ware extensions, but I promise I will release them in early January when I have a few days to clean them up. Sean Tristan Koch wrote: Hi, I was wondering: what is the recommended way to model structured content in Radiant? Say, I want to have a list of contact items: Department #1 Image of Department #1 Name Adress E-Mail Picture Name Adress E-Mail Picture (…) Department #2 Image of Department #2 Name Adress E-Mail Picture Name Adress E-Mail Picture (…) I can think of two possible solutions: #1 a page for each box with subpages, where each subpage has tabs with the fields (e.g. description, image). #2 an extension that overrides the normal body and instead displays a form for each set, with the ability to add a new set by clicking on a + button. In this example, there would be two pages with a specific type (=contact). [somewhat similar to Typo3 XML based Flexible Content Elements, aka FCE] Maybe I'm wrong, but to me #1 doesn't appear very user-friendly, especially if there are many fields. Is there an extension that offers features similiar to #2? Thanks Tristan ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] page_attachments does not save anything
Ulf,
Check the permissions on the public/ directory of your Radiant project
and make sure that the user your app server (Mongrel or FCGI) runs as
has write access to that directory. It's possible that the file
wouldn't save.
Sean
Ulf Moehring wrote:
Hi all,
I just installed the page_attachments extension according to the
instructions on the wiki page. Everything seems to work on the UI
side since the attachment menu shows up and I can upload files. It
seems, however, that none of the files are actually saved even though
I don't any error message. Here's what my log says:
--
Processing PageController#edit (for 69.181.155.144 at 2007-12-07
07:29:13) [POST]
Session ID: 30150eb9e9fea7af5e53b4b2d516d832
Parameters: {continue=Save and Continue Editing, part=
{0={name=body, filter_id=, content=}, 1=
{name=extended, filter_id=, content=r:snippet name=
\BeginWidgetHeader\ /\r\n img alt=\About us\ border=0 src=\/
images/about_us.png\\r\nr:snippet name=\EndWidgetHeader\ /\r\n\r
\nr:snippet name=\BeginWidget\ /\r\n Want all the information in
one, printable document? Download all travel information as PDF.\r
\nr:snippet name=\EndWidget\ /}}, action=edit, id=3,
controller=admin/page, page={slug=travelinfo,
class_name=DynamicPage, title=Travel Info,
breadcrumb=Travel Info, lock_version=34,
enable_comments=0, add_attachments=[#File:/tmp/CGI9097-14],
status_id=100, layout_id=4}}
Redirected to http://ges.projecttray.com/admin/pages/edit/3
Completed in 0.06352 (15 reqs/sec) | DB: 0.01669 (26%) | 302 Found
[http://ges.projecttray.com/admin/pages/edit/3]
--
The log shows the tempfile created but it seems that it doesn't get
processed further. The page_attachments table remains empty. Maybe
validation failed even though I can't see why. Do I need to create a
files directory somewhere? Is there anything else I should try?
I'm using Radiant 0.6.4 and page_attachments 0.2
Thanks,
Ulf
EMAIL: [EMAIL PROTECTED] | SKYPE: ULF.MOEHRING | AIM:
[EMAIL PROTECTED]
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to include classes in extensions?
[EMAIL PROTECTED] wrote:
Hi,
I would like to access this snippet of code from within my extension
tags:
class Numeric
def ordinal
cardinal = self.to_i.abs
if (10...20).include?(cardinal) then
cardinal.to_s 'th'
else
cardinal.to_s %w{th st nd rd th th th th th th}[cardinal % 10]
end
end
end
This by itself in a file should be fine. However, if you want to make
sure you're using the existing Numeric class and not creating a new one,
change class Numeric ... end to Numeric.class_eval do ... end.
As the tags get called on the page I have tried adding the above to:
module StartDate::PageExtensions
class Numeric Page
def ordinal
cardinal = self.to_i.abs
if (10...20).include?(cardinal) then
cardinal.to_s 'th'
else
cardinal.to_s %w{th st nd rd th th th th th th}[cardinal %
10]
end
end
end
end
Here you've made a class StartDate::PageExtensions::Numeric which
inherits from Page. I don't think this is what you want to do. You
want to override the existing Ruby Numeric class.
I would take your first snippet, put it in a file
lib/numeric_extensions.rb, then explicitly require it from your
extension's activate method.
Hope this helps!
Sean
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] page_attachments does not save anything
Michael, Make sure to use the included rake task to copy the included javascript and stylesheets to your public directory. Sean Michael Nikitochkin wrote: I have other problem, when I add this extension in Edit page below body I see a green plus which and label with (0) in the end. But when I click on plus nothing action begins. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] (no subject)
Matias, Congratulations on your site! The easiest way to do that navigation would be to roll your own. There are many tags available that can be put together to do what you like. Also, Radius tags are fairly straightforward to write if you're into that. Sean Matias Quaglia wrote: Hi everyone! First of all i World like to show my first huge page made on Radiant: http://www.connaxis.com/ Any tip, critic or comment will be very welcome. And last, but not least, I would like to ask about navigation tag, is there any way to make sub menu navigation? What I mean is illustrated in the following mock ups: Case1 (Main Menu 1) - - Main Menu 1 (ul li) - Here (blue) - Sub Menu 1 (ul li ul li) (gray) - Sub Menu 2 (ul li ul li) (gray) - Sub Menu 3 (ul li ul li) (gray) - Main Menu 2 (ul li) (gray) - Main Menu 3 (ul li) (gray) - Main Menu 4 (ul li) (gray) Case2 (Sub Menu 1) - - Main Menu 1 (ul li) (blue) - Sub Menu 1 (ul li ul li) - Here (blue) - Sub Menu 2 (ul li ul li) (gray) - Sub Menu 3 (ul li ul li) (gray) - Main Menu 2 (ul li) (gray) - Main Menu 3 (ul li) (gray) - Main Menu 4 (ul li) (gray) Case3 (Sub Menu 2) - - Main Menu 1 (ul li) (blue) - Sub Menu 1 (ul li ul li) (gray) - Sub Menu 2 (ul li ul li) - Here (blue) - Sub Menu 3 (ul li ul li) (gray) - Main Menu 2 (ul li) (gray) - Main Menu 3 (ul li) (gray) - Main Menu 4 (ul li) (gray) Case3 (Main Menu 2) - - Main Menu 1 (ul li) (gray) - Main Menu 2 (ul li) - Here (blue) - Main Menu 3 (ul li) (gray) - Main Menu 4 (ul li) (gray) I don't know if something like that is possible to do using standard tags. I was reading previous posts, and I have a stupid question (where is page page_context.rb) Greetings, MQ ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Difficulties with a navigation menu and selectively showing children
Lou, Here's a tag definition you can drop into your project's extension that might help. tag 'if_self' do |tag| tag.expand if tag.locals.page == tag.globals.page end Since we have better support for detecting the globally rendering page now, we should probably add it to the core. Sean On Dec 5, 2007 8:31 AM, Lou Brothers [EMAIL PROTECTED] wrote: On Tue Dec 04 16:14:06 UTC 2007, Mohit Sindhwani [EMAIL PROTECTED] wrote: Lou Brothers wrote: I want to display all of the children of the parent page, and then display the children of the current page only. In this example, Child Page 2 has children, but I am not showing them. I haven't tried it but this might work (or something like this): r:parent-- switch the context to the parent of this page r:children:each -- for each child (of the page's parent) r:if_this_is_the_current_page -- sorry, I can't remember how to match this r:children:each --- for each child of this page r:link / -- or whatever you want to do /r:children:each /r:if_this_is_the_current_page /r:children:each /r:parent Maybe, these will help: 1. http://lists.radiantcms.org/pipermail/radiant/2006-July/000888.html 2. http://www.ruby-forum.com/topic/125811 Based on #1 above, you may need to match using:r:page:if_url because that works at the level of the current page, not the level of the current context (which in a nested scheme will be the child/ parent page). Hope this helps. Cheers, Mohit. 12/5/2007 | 12:14 AM. I can't seem to find a reference to an example of determining if a url is the url of the current page. My attempts at using r:if_url matches... have not been successful. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] page_attachments with page type not set to normal.
Dave,
That sounds kind of hack-ish. The better solution is make sure
page_attachments loads before anything else. Uncomment/put this line in
config/environment.rb:
config.extensions = [:page_attachments, :all]
Although I haven't heard of changes to a superclass not propagating to
subclasses like this, it may have to do with associations.
Sean
Dave Bryand wrote:
I think I've got part of the solution figured out. After digging into
the code a little and poking around console, I think I understanding
what's going on.
page_attachments is literally attached to a page with class Page. In
page_attachments_extension.rb, the PageAttachment stuff gets
class_eval'ed onto Page.
--
Page.class_eval {
include PageAttachmentAssociations
include PageAttachmentTags
}
--
Also, I see in the PageAttachment class definition:
class PageAttachment ActiveRecord::Base
...
belongs_to :page
end
From looking at a page with page type Archive in console:
#ArchivePage:0x25cdc48 @attributes={slug=/,
class_name=ArchivePage,
This is no longer a page with class Page, it is an ArchivePage and
ArchivePage hasn't received the PageAttachment extensions.
As an experiment, I tried just duplicating the include code above and
eval'ing it on ArchivePage:
--
ArchivePage.class_eval {
include PageAttachmentAssociations
include PageAttachmentTags
}
--
I restarted my server and tried to edit the page, but got stopped with
an error:
SQLite3::SQLException: no such column: page_attachments.archive_page_id:
SELECT count(*) AS count_all FROM page_attachments WHERE
(page_attachments.archive_page_id = 1)
What I noticed after that was that PageAttachmentAssociations evals the
following when it gets included into a class:
has_many :attachments, :class_name = PageAttachment, :dependent =
:destroy
Adding :foreign_key = page_id should clear up the error that just
stopped us:
has_many :attachments, :class_name = PageAttachment, :dependent =
:destroy, :foreign_key = page_id
I restarted my server and tried to attach an image to the Archive page
and it worked. So now, the main issue is just figuring out a way to
include PageAttachments gracefully into all of the page types when the
extension gets activated. Anyone have any ideas?
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Standard rails plugins not supported in Radiant?
It should be loaded. Are you storing it in RAILS_ROOT/vendor/plugins? Have you modified the config.plugin_paths in config/environment.rb? Sean Christopher Zimmermann wrote: Hello, Forgive me if this is a stupid or already covered question - i did search on the radiant site and mailing list, but did not see any conclusive answers. In a nutshell: I see that the path to the plugins lib directory is properly added to load_paths by railties/initializer.rb load_plugins(). But then the path is completely overwritten in radiant/extension_loader.rb discover_extensions() Context: I am trying use a regular rails plugin acts_as_taggable_on_steroids, and would like to use several others. I dont need to use it as an extension in Radiant - it will be used elsewhere in the same application. (My app mixes Radiant with a rails app through the lovely radiant_on_rails, share_layouts, and record_tags extensions.) It is probably possible to create an extension that wraps it - but I would prefer not too. It's nicest (and easiest) if I can just load existing rails plugins and also keep them up to date as people release new versions. The problem that I am having is that this plugin has several modules in it's lib directory that cannot be discovered by rails Dependencies.load_missing_constant because the path has been removed from the Dependencies.load_paths array by Radiant. So when I try to use this Plugin I get a NameError in TesterController#tagtest Uninitialized constant ActiveRecord::Acts::Taggable::InstanceMethods::TagList Questions: So, are plugins basically not supported in Radiant? Is there a reason for that... and is there a reason for totally overwritting the Dependencies.load_paths array? Or is this something that could be changed, for example that radiant/extension_loader.rb discover_extensions() appends the paths to load_paths instead of overwriting it? Thanks for any insight into this!!! cheers, topher ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Standard rails plugins not supported in Radiant?
The original reason is so that Radiant can be run from the gem or
vendor/radiant. Notice line 17-22 of config/environment.rb. However,
that should not affect plugin paths which are set later on in the file.
However, you may be onto something here.
Sean
Andrew O'Brien wrote:
IIRC correctly, what Chris is describing is the reason I had to
explicitly load the rspec and rspec_on_rails plugins in
config/environments/test.rb. Somewhere along the line (and Chris may
have identified it), the plugin load paths are getting blown away.
Chris: try adding something like
config.load_paths #{RADIANT_ROOT}/vendor/plugins/rspec/lib
(but the path for your plugin) to config/environment.rb in the
Radiant::Initializer block.
What was the original reason for clearing out the load_paths? Is it
something that should be re-examined?
-Andrew
On Dec 4, 2007 4:48 PM, Sean Cribbs [EMAIL PROTECTED] wrote:
It should be loaded. Are you storing it in RAILS_ROOT/vendor/plugins?
Have you modified the config.plugin_paths in config/environment.rb?
Sean
Christopher Zimmermann wrote:
Hello,
Forgive me if this is a stupid or already covered question - i did search on
the radiant site and mailing list, but did not see any conclusive answers.
In a nutshell:
I see that the path to the plugins lib directory is properly added to
load_paths by railties/initializer.rb load_plugins().
But then the path is completely overwritten in radiant/extension_loader.rb
discover_extensions()
Context:
I am trying use a regular rails plugin acts_as_taggable_on_steroids, and
would like to use several others.
I dont need to use it as an extension in Radiant - it will be used elsewhere
in the same application. (My app mixes Radiant with a rails app through the
lovely radiant_on_rails, share_layouts, and record_tags extensions.)
It is probably possible to create an extension that wraps it - but I would
prefer not too. It's nicest (and easiest) if I can just load existing rails
plugins and also keep them up to date as people release new versions.
The problem that I am having is that this plugin has several modules in it's
lib directory that cannot be discovered by rails
Dependencies.load_missing_constant because the path has been removed from
the Dependencies.load_paths array by Radiant.
So when I try to use this Plugin I get a
NameError in TesterController#tagtest
Uninitialized constant
ActiveRecord::Acts::Taggable::InstanceMethods::TagList
Questions:
So, are plugins basically not supported in Radiant?
Is there a reason for that... and is there a reason for totally overwritting
the Dependencies.load_paths array? Or is this something that could be
changed, for example that radiant/extension_loader.rb discover_extensions()
appends the paths to load_paths instead of overwriting it?
Thanks for any insight into this!!!
cheers, topher
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant + ACL + Portlets + 1.0
Erik, Radiant may not necessarily be a good fit for your needs. Radiant is very focused on textual content that is essentially static (i.e. not customized-per-visitor) and has a very simple administration scheme. Take into consideration whether your content editors are familiar with HTML, CSS, etc, as Radiant exposes this almost directly to the editor. Also consider the size of the editing team and whether they will often step on each others' toes when working, as Radiant has no versioning yet (optimistic locking prevents basic overwrites, but doesn't save older versions). If you're still considering Radiant, let's look at your needs. ACL - There are two groups/permissions/roles in Radiant, developer and admin. Only admins can view/edit which extensions are installed and active. Your extension controllers can easily specify who can access what actions and who can see what tabs. Users may also be plain users, or rather, have neither of the above roles. Extensions - Please describe in more detail what you mean by portlets. When I read that word, I think of content components that can be selected and arranged in a page by the visitor. If this is what you're looking for, Radiant is NOT portal software, and I suggest you look at other available options. If you just need to integrate with some proprietary data services, Radiant extensions can handle the job, but won't deliver the portlet idea necessarily. You cannot have multiple versions of an extension installed at the same time. Why would you want this? Please describe what you mean by Maintenance, Disabled, etc. Does this refer to portlets? i18n - There are already some efforts at internationalizing Radiant. Search the mailing list for discussions of the Language Redirect extension and other strategies for serving content in multiple languages. Regarding translating the administration interface, there is some work done in the jargon branch that you may find useful. Web Service - You could easily create or consume a SOAP API using ActionWebService. However, the design and implementation of this is out of my scope of knowledge. Version 1.0 - We have a rough schedule, yes. However, Radiant is already successfully being used on many sites (see the RadiantUsers wiki page), and the core is relatively stable. There is no stigma to using it pre-1.0. And honestly, I don't see 1.0 arriving in less than a year. We have many more hurdles to overcome before then. If you want 1.0 to arrive faster, I suggest you consider contributing well-tested improvements to the core. While the core team contributes their own fixes and enhancements, much of the code has also come from the community. We cannot predict the architectural impact of 1.0 because it's not even on the radar. I can assure you there will be many changes between now and then, but we will likely have near-complete backward compatibility or at least a sensible upgrade path. Hope this helps! Sean Cribbs (Radiant core team) Erik Nijkamp wrote: Hello Developers, We are planning to use Radiant as groundwork for a commercial project and decided to ditch j2ee + jsr portlets in favor of rails + radiant. Would you please inform us about the current status of: * ACL - User/Group/Role management - Authentication - Assigning roles to extensions * Extensions - Portlets: Using extensions as Portlet replacement e.g. associating extensions with roles - Versioning: Using different versions of an extension at the time - State: Maintainence, Disabled, ... * i18n - Localized content - Detecting the currently used language (browser) * Web-Services - Replacing the rails model with a web-service - e.g. extension - controller - soap/rest web-service - backend * Version 1.0 - Do you have a schedule? - Architectural impact? Thanks for your time and help! Best regards Erik Nijkamp ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant Factory
Richard, This is rather trivial to do with an extension. Write your desired CSS, put it in your extension public/stylesheets directory. Then put something like this in your extension's activate method: SiteController.class_eval do before_filter :customize_admin_css def customize_admin_css include_stylesheet 'my_stylesheet' end end Obviously you'd want to name your stylesheet something else. Hope this is helpful! Sean Richard Hurt wrote: Putting the controls on a sidebar is OK with me. I would even be fine with a smaller text for the page title and various controls. I'm screen height challenged, not blind. :) Hmmm...what about a way to customize the CSS of the Admin pages for each install? Would that work? It wouldn't even have to be anything fancy like a table in the DB, just a static file on the server would work for me. We could then change the look feel of the pages pretty easily and to fit within our own guidelines. Later... Richard On Dec 2, 2007 3:08 PM, Ryan Heneise [EMAIL PROTECTED] wrote: I think I prefer having the buttons underneath the form, because it is more standard and fits the open-edit-save workflow. Moving the buttons to the top breaks with convention. What about a 2-column layout (similar to this: http://www.madebyfrog.com/news/preview_layout_for_version_1) , moving the meta-data form inputs to the second column? If some of the metadata were moved out of the way horizontally, then the body of the form could be shorter. On Dec 2, 2007, at 6:30 AM, Andrew Neil wrote: 5. Can we make the edit page a little more friendly for those of us without 1700x2400 displays? :) I feel your pain. A couple of thoughts: * Save Changes and Save and continue buttons could go at the top, perhaps level with the Edit Page heading, but floated to the right. * The same two buttons could be given access keys, e.g. S and C, so that you can trigger them with a key command, rather than pushing them with your cursor. A ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Rails Versions
Radiant ties itself to Rails by inclusion (look in vendor/radiant/vendor/rails, or gems/radiant-0.6.x/vendor/rails). Both frozen and gem Radiant ignores any Rails gems you have installed. As far as moving to a newer version of Rails for security fixes, the core team tries to keep on top of that. 0.6.5 will include Rails 1.2.6, which came out after the Radiant 0.6.4 release. Since Rails 2 will be out soon, 0.6.6 will probably include Rails 2.x. Sean James Coleman wrote: Do I need to freeze my radiant site on a shared host. I have read that Radiant ties itself to a certain version of rails. How does this work, and how will it be affected when the host deletes that gem and installs a newer version? Also, what if I need to move to a newer version of rails to get security fixes? ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant Factory
Mohit, Every one of your requests have been one way or another addressed by some extensions I have written for Digital Pulp. I'll see what I can do to release the pertinent bits. Sean Mohit Sindhwani wrote: Ryan Heneise wrote: The radiant administrative interface is still a bit daunting for some of our scientists I've run into this before - I guess I just take it for granted that the admin interface is easy to use, because _I_ like it. But that's not the case for everyone. I'm curious, what about the Admin interface is daunting to your scientists, and how might it be improved? OK, I'm not a scientist and it's not daunting for me to use the admin interface. But a couple of things would be nice to have (perhaps): 1. A way to search for a page without having to go through the tree hierarchy. A nice neat auto-complete field that narrows down the list of pages based on the text you type would be great. After a few levels of hierarchy and a lot of pages, I imagine the current navigation will start to get a bit tedious. 2. A way to change the published status of multiple pages from the index page directly, rather than going to each page itself. 3. On the page editing interface, a small link to View this page - it's fine if it appears only after the page has been saved once (so that Radiant can render that link). It's a bit annoying to create a new page, but then from the index page (View Site), there's no way to get to the page since the parent page that may be connecting to it is still in cache... and you must either expire cache or type in the full URL or something. 4. The View Site link to open up in a separate window. I think I do really like the minimalist look of the admin page, but some of the above ideas will hopefully not clutter it too much. Cheers, Mohit. 12/2/2007 | 10:11 AM. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RESTful Radiant
Chris, 0.6.6 will be RESTful. John and the core team decided switching over to RSpec first was more important. Plus, Rails 2's release date was no more certain than soon when we made the decision. Sean Chris Parrish wrote: With Rails 2.0 coming soon, are there any near-term plans for Radiant's admin tools to move towards a more RESTful design? I've been working on an extension that inherits quite a bit from Radiant's AbstractController and have found several places where the going would be easier were it REST-oriented (it would probably simplify things like PageController too). I guess I'm saying that it would be nice to bite the bullet sooner rather than later -- before too many extensions get built that would have to be reworked. -Chris ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant Factory
Saji, I concur with Richard. Your design is very clean and probably only needs a few finishing touches to integrate and re-balance certain sections. Sean Saji Njarackalazhikam Hameed wrote: Hi Richard, Thanks for the compliments. I forgot to start the server. It is up now :) saji ... * Richard Hurt [EMAIL PROTECTED] [2007-11-29 21:07:38 -0500]: I don't know, I kind of like the clean look of you existing page. Not too much info to confuse the visitor, yet it explains everything. :) The page you are looking for is temporarily unavailable. Please try again later. Later... Richard On Nov 29, 2007 8:39 PM, Saji Njarackalazhikam Hameed [EMAIL PROTECTED] wrote: I have the same question here. Am looking for a designer to improve the looks of (http://210.98.49.34:3000). We already use Radiant anyway. saji * Richard Hurt [EMAIL PROTECTED] [2007-11-29 20:48:22 -0500]: Do you provide design services or just take existing designs and work them over for Radiant? I can't design my way out of a wet paper bag. I know what I like and what I would like my website to look like I just can't make it happen. sniff :) Later... Richard On Nov 29, 2007 4:30 PM, Ryan Heneise [EMAIL PROTECTED] wrote: Hi Folks, I'm launching a new service called Radiant Factory ( http://www.radiantfactory.com/ ) - basically a theming service for Radiant. Let me know what you think! - Ryan Heneise ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- Saji N. Hameed APEC Climate Center +82 51 668 7470 National Pension Corporation Busan Building 12F Yeonsan 2-dong, Yeonje-gu, BUSAN 611705 [EMAIL PROTECTED] KOREA ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] radiantcms down?
Dominic wrote: Site seems to be down again... ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant We overfilled our disk quota with log files. It'll be back up shortly. Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Problem with date on Mailer Behaviour
Yes, that is in the latest version. However, I have realized there is a breaking change in 0.6.4 for those who are upgrading from 0.5.x, which is that the Archive pages/behaviors have been moved to an extension. When you are upgrading, extensions are not available, so the ArchivePage model (and its brethren) cannot be found. If you have any pages with the Archive or the Year/Month/Day Archive Index behaviors, I suggest you change them to no behavior before upgrading, then move them back after upgrading. Alternatively, you could upgrade to 0.6.3, then upgrade to 0.6.4. Sean Thanks Sean - Will update my code and see if it works. I'm currently running version 0.5.2 of Radiant CMS - is this an update in the latest edition? If so, how do I go about upgrading to the latest version?? I have read the documentation here - http://wiki.radiantcms.org/How_to_Upgrade_05x_to_06 but to be honest it is a little confusing for me... I use a programme called Putty for SSH access to my hosting account with A Small Orange. Any help would be greatly appreciated! Oliver ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] radiantcms down?
Should be back up! Sean Dominic wrote: Site seems to be down again... ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Problem with date on Mailer Behaviour
Oliver, r:date / refers to the published date of the page by default. Use r:date for=now / instead. Sean Oliver Coningham wrote: Hello all - On my website - http://www.spongenewmedia.co.uk/ - I have created a form that uses the mailer behaviour. It is only basic and captures name, message, email address etc. The code for my email message is as follows: Hello! r:mailer:get name=name/ has sent you a message on r:date format=%A, %B %d, %Y / from the web site! Sent: r:date format=%A, %B %d, %Y / Name: r:mailer:get name=name/ Email: r:mailer:get name=email/ Message: r:mailer:get name=message/ The problem with it is that the date seems to be stuck at May 7th 2007 whenever I get a new message. Can anyone help me? I want the date to be the date that the message was actually sent. Many thanks in advance, Oliver Coningham _ The next generation of MSN Hotmail has arrived - Windows Live Hotmail http://www.newhotmail.co.uk ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SASS Filter Extension
Matias, It hasn't been updated in a long time. Can you run script/server and get us a full stack trace of the error? (or check the log) Sean Matias Quaglia wrote: Hi everybody I’m kind-of new at Radiant. I’m very excited using HAML and SASS on my Rails working, and I would like to try SASS in Radiant, so I installed the SASS Filter extension in a Radiant 0.6.4 (gem). When I tried to access to front or back I got the 500 message (like when one mess up things with a ruby syntax error on a .rb file). When I deleted the extension, Radiant worked again. Am I missing something, could anybody give me some enlightment about this extension? Regards, Matías Q ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Does the virtual host extension work with 0.6.4?
I tried it briefly on 0.6.3 before I decided to write my own alternative. It seemed to work fine, but that was only testing locally. Sean On Nov 20, 2007 11:47 PM, Travis Bell [EMAIL PROTECTED] wrote: Hey guys, I tried adding the vhost extension today on a new Radiant 0.6.4 install that I was setting up and kept getting some errors. If it's supposed to work, I can post the errors and hope someone can help but if it's a known problem than I'll hold off. Thanks, -- Travis Bell Not sent from my iPhone. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Simpler reorder extension
That generally occurs when you don't have the loading order set in config/environment.rb of your project. It should look like this: config.extensions = [:shards, :all] Alternatively, you can rename the vendor/extensions/shards directory to vendor/extensions/00_shards. Sean On Nov 21, 2007 1:50 PM, Travis Bell [EMAIL PROTECTED] wrote: Hey Sean, Upon trying to run rake production db:migrate:extensions I am getting the following error: ## undefined method `page' for #Radiant::AdminUI:0x40804734 Any idea why? This is a gem install of version 0.6.4 with the Shards extension from the trunk installed. Thanks, -- Travis Bell Not sent from my iPhone. On 19-Nov-07, at 8:56 AM, Sean Cribbs wrote: With Adam's permission, I have replaced the reorder extension in the Radiant repository with the simpler one I developed recently. Instead of adding a separate view with drag-and-drop, it adds up/down/top/ bottom buttons to the sitemap. You can use Subversion to download it from: http://dev.radiantcms.org/svn/radiant/trunk/extensions/reorder Enjoy! Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] Simpler reorder extension
With Adam's permission, I have replaced the reorder extension in the Radiant repository with the simpler one I developed recently. Instead of adding a separate view with drag-and-drop, it adds up/down/top/bottom buttons to the sitemap. You can use Subversion to download it from: http://dev.radiantcms.org/svn/radiant/trunk/extensions/reorder Enjoy! Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Problem with Shards!
Will, Use the trunk version of shards. It fixes that error. Sean Will Green wrote: The old reorder extension broke with Radiant 0.6.4, so I installed Shards (tags/rel_0.6.4) and the new Reorder extension. Now, when I access the Admin interface, this is what I get: Showing vendor/extensions/shards/app/views/admin/page/_node.rhtml where line #2 raised: wrong number of arguments (0 for 1) Extracted source (around line #2): 1: tr id=page-%= page.id % class=node level-%= level %%= children_class %%= virtual_class % 2: td class=page style=padding-left: %= padding_left %px 3: span class=w1 4: % if simple -% 5: %= icon % Help! ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] radiant extension and rails method
Marc, By default, Radius tags are rendered within a Page that is called from the SiteController, which has the session turned off. You might be better off using cookies, but you would only be able to read them unless you can come up with some scheme that decides what cookies to send based on the page. Including that module doesn't accomplish what you want. Could you give us a little more detail about what you want to do? Sean Marc des Garets wrote: Hi all, I'm pretty new in radiant and in ruby on rails but I'm making an extension for radiant and I have some questions I'm pretty sure you'll be able to answer: I'm creating my tags for my extension in app/models/solr_tags.rb I'm using the method session of the ActionController::SessionManagement::ClassMethods class of rails but to use this session method I had to add this in my solr_tags.rb file: include ActionController::SessionManagement::ClassMethods After that I can call the method session in my lib/flare/controller_extensions.rb that is in a function I'm calling from my solr_tags.rb file. But now, I have this error: undefined method `write_inheritable_array' that I could solve doing an other include of a rails class but I was wondering if there is an other way to get all these rails method without adding an include each time I need one rails method. Furthermore, it's the method session that is using write_inheritable_array so it should be fine. I think I have some misconfiguration somewhere. Can you help? Hope I was clear enough, tell me if not and thank you in advance for your help. Marc ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Performance
If you guys are concerned about performance, please search the mailing list for Daniel's most recent benchmarks. He's done a great job making sure Radiant's cache performance is stellar. Sean Peter Berkenbosch wrote: I think I run 4 mongrels, so that should be brought back to two. I also use Apache which has to be replaced with nginx or something else. Thanks for the headsup! Peter On Nov 14, 2007 5:22 PM, David Piehler [EMAIL PROTECTED] wrote: Sean Cribbs wrote: Are you using mongrel_cluster? If so, I would make sure you don't run more than 2 mongrel processes. On an app I worked on this summer that was hosted on a 256 slice, we would have major problems if we ran more than two, our app would screech to a halt after about an hour of hitting various actions. FYI, seancribbs.com runs Radiant on a 256 slice with only one mongrel. I have yet to have a problem with it. Cheers, Sean Thanks for the info on Slicehost + Mongrel performance. I'm slowly moving all my Radiant apps over there and this is good knowledge to have. -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] tag.globals.actual_page returning null
David, When Daniel cleaned up cruft in the Page model, he made snippets render on the global page, i.e. tag.globals.page. In r601, I changed r:content to be rendered by the global page too. What this does is maintains tag.globals.page as the currently rendering page. It's a pretty ingenious and subtle change -- we don't create a new context and parser, so all rendering context is retained. Sorry, this is a roundabout way of saying, use tag.globals.page instead of tag.globals.actual_page. Cheers, Sean On Nov 15, 2007 12:48 PM, David Piehler [EMAIL PROTECTED] wrote: Using Radiant 0.6.4 gem. The following is false because tag.globals.actual_page is being returned NULL... tag if_page_is_self do |tag| tag.expand if tag.locals.page == tag.globals.actual_page end I'm using my tag like... r:find url=about a href=r:url /r:if_page_is_self class=selected/r:if_page_is_selfr:breadcrumb //a /r:find Any ideas on why tag.globals.actual_page is returning NULL? -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] Another Shards update
Today I'm going to commit a few changes to the Shards extension that I want to warn you about. The primary change is that the SiteMap table is finally better parameterized. This will mean that, finally, you can add arbitrary columns and column headers. Basically, all th and td tags in the original source are separate. Here are the new region and partial names: page.index.sitemap_headers title_column_header status_column_header modify_column_header (spans 2 columns) page.index.node title_column status_column add_child_column remove_child_column If I wanted to insert a column between the title and status, I would do something like this: page.index.add :sitemap_headers, 'foo_column_header', :before = 'status_column_header' page.index.add :node, 'foo_column', :before = 'status_column' Note that all your partials within the node region will receive the locals of page, level, and simple. I will also bump the version number up to 0.2, heh. I'm hoping these changes will make the sitemap easier to manipulate. Cheers, Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Page admin interface bug
I'm actually debating releasing the reorder extension I developed for my current client. It doesn't have the sexy drag-and-drop, but it works well. Would there be interest in it? Sean On Nov 15, 2007 4:44 PM, Travis Bell [EMAIL PROTECTED] wrote: Seems to me Sean said they did a bunch of re-factoring with 0.6.4 and that the re-order extension needs to be tweaked. Cheers, -- Travis Bell Not sent from my iPhone. On 15-Nov-07, at 3:35 PM, David Piehler wrote: Andrew O'Brien wrote: I noticed that if I click the minus button on a page with children, it hides the children as expected but the button doesn't change back to a plus and clicking again it won't re-expand. I figured I'd ask if anyone else had this problem before investigating further. Using Radiant 0.6.4 gem, testing in Firefox. These REORDER extension-based issues seem to have cropped back up for me. Anyone else experiencing this? -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
