Re: [Radiant] More 'Rails app to Radiant extension' questions
2010/1/11 banane ban...@gmail.com: Put the routes.rb stuff in [yourapplication]_extension.rb You can extend ActiveRecord, just like in Rails. Rails is embedded in Radiant, so it works pretty much the same. Put the testing stuff in /rspec, test as usual. And what about selenium on rails tests? That is another stickler. Another question: My app currently uses several plugins it needs. If I make my app an extension, where do those plugins go? If I simply move them to the Radiant app, won't that make upgrading difficult? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] More 'Rails app to Radiant extension' questions
2010/1/12 john muhl johnm...@gmail.com: if your rails app has vendor/plugins/xyz then your extension would have vendor/plugins/xyz. for example: /rails_app/vendor/plugins/xyz /radiant_app/vendor/extensions/your_extension/vendor/plugins/xyz Oh, that's beautiful. Thanks. 2010/1/12 Sean Cribbs seancri...@gmail.com: It might be better to use gems where possible, as that's the direction both Rails and Radiant are going. If you can't use your plugins as gems, John's method should work. My plugin is an in-house one that I use to share useful code between my apps. If I pack it up in a gem, I can freeze it in the extension, I assume? Thanks, regards, Asfand ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Rails app to Radiant extension: problem - app already has User model
I will probably have to do something similar to that. On the other hand, I might just namespace all my classes that conflict. But looks like renaming is the way to go. Now just to break the news to the client... 2010/1/11 Arthur Gunn art...@gunn.co.nz: Project-wide find and replace? User — Person users — people etc. Just do it case-sensitively. This worked fine for me. -Arthur ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] More 'Rails app to Radiant extension' questions
Hi, More questions to converting a Rails app to a Radiant extension. Currently, in Rails 2.3.5, it is almost possible to mount a Rails app as a plugin and have all the routes, helpers, etc. just work. If I am going to convert my Rails app to a Radiant extension, I need to have the following issues resolved. - I have all my text used in view, flash messages and emails in the I18n file 'en.yml', containing lots of ActiveRecord and other translations as well. How do I move these to the Radiant app? - I have several routes in my current app (in config/routes.rb). How do I move these to the Radiant app? If I simply move them into the Radiant app, won't upgrading the Radiant app become more difficult? - Will mailers just work? - Things like RSpec specs and Selenium tests are currently run by doing a 'rake spec' or 'rake test:acceptance' , but they rely on the Rails app - if I dismantle the Rails app, how will I cause these to still run? Again, if I simply move them into the Radiant app, won't upgrading the Radiant app become more difficult? Any hints to help me speed up the transition would be appreciated, as I believe I have already under-quoted the client because of guilt that I should have developed the app in a Radiant extension from the beginning since I knew they would eventually want a CMS anyway. Thanks ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Rails app to Radiant extension: problem - app already has User model
Hi, I want to move my Rails app to a radiant extension, as it makes it so much simpler to share layouts and things with my existing controllers. However, there is a problem: the Rails app already has an Authlogic based User model. It would conflict with Radiant's one. Can anyone tell me a solution to how I can make the 2 co-exist easily without going in and rewriting either the app or Radiant to change one of the User model's names? If it isn't possible, I'm just going to have to make them separate apps, and integrate them some other way. Thanks ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Rails app to Radiant extension: problem - app already has User model
2010/1/10 Arthur Gunn art...@gunn.co.nz: Renaming your app's user model would seem like a very clean and easy way of doing things. I don't see any way of doing things without renaming your app's user model. The only alternative would be to drop it and patch radiant's user model with your changes. That's likely to be more trouble than it's worth, and the only potential advantage it brings you is that radiant editors can automatically become app editors and vice versa. Just call your apps user model Person. And then go and rename it in every single location, from models to controllers, specs and selenium tests.. I was hoping for another way, as that is going to take a long, long time, and be potentially very fiddly and error-prone. Shouldn't Radiant be using its own namespace for everything? I suppose I could say the same thing about my app, why didn't I use my own namespace? I think I will just host the two apps separately, and use ActiveResource or something to make them communicate when I have to, and get my app to 'download' the layout from Radiant or vice versa. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Sharing radiant layouts with another Rails _application_ (not controller)
On Tue, Jan 5, 2010 at 12:45 PM, Asfand Yar Qazi ayq...@gmail.com wrote: Hi, I know I can use a plugin to let a controller independant of Radiant to use Radiant's layout. But what if I have 2 applications - one with custom functionality, one as the Radiant CMS - serving the same 'site' on different paths, how I can I share as much of the layout as possible without having to copy/paste? Thanks 2010/1/6 John Long johnwlong2...@gmail.com: commodity and consumer look like they may be what you are looking for: http://ext.radiantcms.org/extensions/124-commodity Ah, thank you. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Sharing radiant layouts with another Rails _application_ (not controller)
Hi, I know I can use a plugin to let a controller independant of Radiant to use Radiant's layout. But what if I have 2 applications - one with custom functionality, one as the Radiant CMS - serving the same 'site' on different paths, how I can I share as much of the layout as possible without having to copy/paste? Thanks ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Develop new project in Radiant 0.8.1, or 0.9?
2009/11/30 Mamed Mamedov mamed.mame...@gmail.com: snip It is only my opinion, thank you for reading it till the end ;) no problem - I'm already starting to develop in 0.8.1, it's just that the 0.9 UI is soo much prettier, and I'm a sucker for aesthetics ;) ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] WYSIWYG editors problem
Hi, I'm having a problem with both the Fckeditor filter and the TinyMCE filter which is the same, so it must not a problem with either of those extensions. Basically, if I scroll the page and type text into one of the editors' boxes, everything works fine. But if I press enter, the browser window scrolls right to the top of the page. Has anyone experienced any issues with either of these? Thanks Asfand Yar Qazi ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant capabilities
2009/11/22 Anton Aylward anton.aylw...@rogers.com: Asfand Yar Qazi said the following on 11/22/2009 10:10 AM: 2009/11/21 Anton Aylward anton.aylw...@rogers.com: I'm a strong believer in simplification, and one of the axioms is Each Thing Does One Thing and Only One Thing. Overloading a single engine to do all you want sounds like a recipe for disaster. Well, I'm not really overloading a single engine. The radiant engine will only manage blogs and articles. That is kind of what it is designed for, I'd assume - dealing with articles and presenting them in some format accessible by a menu hierarchy. The separate forum software (whatever it is) will manage the forums. If the client wants something else added in the future, like a video presenting application, obviously that would be its own app. However I see what you're getting at. [1] See Rick Smiths' book Authentication http://www.amazon.com/gp/product/0201615991?ie=UTF8tag=emergentprope-20linkCode=as2camp=1789creative=390957creativeASIN=0201615991 P122: Indirect Authentication dresses the scalability problem posed by sites with a single user population but multiple points of service. Even a site with just two servers will want to avoid the headache of maintaining consistency between two separate authentication databases. That seems like a good way to implement user access control across several services, thanks. I shall see if I can have it done between the forum and radiant app in an extensible manner (hopefully without the use of something like LDAP, which I loathe too, even though I am proficient in it). Regards, Asfand Yar Qazi ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant capabilities
2009/11/23 Anton Aylward anton.aylw...@rogers.com: And I don't know where you get off slagging the excellent work by the various contributors to Radiant by implying its not as capable of being a forum engine as a blogging engine. And yes, there are plugins to handle video too. Sorry about that, I didn't mean to be insulting. I just thought the forum features weren't as mature as other more established forums. If you feel it is, then I shall surely look into it and present it to my clients as a possible forum solution. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant capabilities
2009/11/23 Anton Aylward anton.aylw...@rogers.com: Its not about maturity. Its about what people have chosen to develop. One reason for Radiant was that it simply headed in a different driection from Joomla ... or Silverlight. But RoR and Radius makes Radiant very easy to alter. I agree. In particular I like the approach of aspect-oriented programming used in Radiant extensions. I think Rails is moving towards that sort of idiom as well, with the recent work on plugins having their own routes and translations as well as the usual M/V/Cs. However you must understand that the Radiant forum extension is competing against vBulletin, which my client is used to. I'm not saying vBulletin is good, it is just what the client is used to. And phpBB is the closest open source alternative. I will offer the radiant forum extension as an alternative, maybe they will prefer the simplicity - I certainly hope so. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Develop new project in Radiant 0.8.1, or 0.9?
Hi, Should any new projects be developed in Radiant 0.8.1 , considering all extensions are written for it? Or can I assume they will be updated fairly quickly to 0.9, and start developing for the 0.9 release? If I were to develop any projects in 0.8, how difficult would it be to port them to 0.9, including any extensions used (assuming 0.9-compatible versions were available)? Thanks ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant capabilities
2009/11/21 Steven Southard ste...@stevensouthard.com: This sounds like standard CMS stuff, doesn't it? The only sticking point seems to be the overall account scheme, where a single user account can do multiple things depending on what permissions it has. Will Radiant easily support these features, or is some hard development work required? From my experience with radiant I think a few of these features seem like you will be doing some development work to achieve. That said the CMS is quite flexible and I'm sure it could be made to do these things. I can't believe I'm saying this but with what your trying to do may I suggest you first look into Drupal before you start this project with Radiant. I don't know Drupal very well but I do know some sites made with it that have similar features. Good luck with what ever you choose. I don't know PHP or Drupal, but I know Ruby on Rails. Hence I will develop this platform using Rails, and since Radiant seems to be the number 1 CMS system on Rails, I will use that. The kind of thing (although simpler) I think my clients are looking for is http://anandtech.com/ 2009/11/21 Bentley, Dain dbent...@nas.edu: For comments have you looked at disqus? You can eve use facebook signon. Thanks I will consider that. 2009/11/21 Anton Aylward anton.aylw...@rogers.com: Asfand Yar Qazi said the following on 11/21/2009 12:05 PM: I'd like to know if Radiant or one of its extensions offers some capabilities I'm looking for for a site I need to write for a client. Site. That's an important term. It means domain? Right? I mean 'site'. I know of several 'sites' where the all the features are rolled up into a single coherent interface (at least from the visitor's point of view), for example, http://www.anandtech.com/ (technology magazine) and http://www.therevival.co.uk (Muslim youth magazine). I wouldn't do this all with just one engine, even if I used Radiant for all the parts. Suppose you have a 'portal' at QizisCompany.com. I've done this with static HTML and embeded IFRAMES for news feeds, but there's no reason that this shouldn't be the front page of the magazine, and yes I believe it can be done with Radiant. But that front page can have a menu item for Blogs that actually takes you to Blogs.QizisCompany.com. Perhaps that'd done with Radiant, perhaps not. Another menu item goes to forums.qizisCompany.com . And so on. If you don't like the forum plugin for Radiant, try another RoR forum engine: Eldorado - http://eldorado.heroku.com/ I'm not going to skimp on forum features just because it has to be in Ruby on Rails - phpBB it is, because the rich feature set is worth it (and it's free compared to vBulletin). The main page has to have snippets of the latest blog entries, the latest forum posts, and a single username/password must be able to access all of these. Using separate apps makes this more difficult, but not impossible - I just have to delve into the database of each one and extract the text myself. Also, using different sub-domains causes search engines to treat each one as a separate site - SEO advice seems to recommend that everything is under the same domain, to increase search engine rankings. So I'm going to have them as 'xyzsite.com/forums' and 'xyzsite.com/blogs' etc. Thanks for the advice. SSO is a very fuzzy concept. Many of the authentication mechanisms give a cookie token back after login and have remember me so that when the user come back after a period (seconds, hours, days...) so long as they haven't deleted the cookie they are authenticated. If you make this happen at the DOMAIN level - see above - then you can make one form of SSO happen. There's a few IFs though. Authentication is not the the same as Authorization. Someone may log in to update their blog but that may not mean they are authorized to read private parts of the forum or submit articles to the journal. I suggest you look at using Role Based Access Control. I believe there is a plugin for it, but I don't know if it addresses this kind of thing. That's why I want to use a single engine for everything - RBAC becomes easier. If I have to use other software, I'll basically be creating accounts and logging people into them on the other software when they log onto my app. But phpBB, for example, has its own RBAC scheme, so that's ok. It means doubling work of administrators when assigning roles (first on the app, then on the forum software), but from the visitor's point of view, it seems consistent, because they only have to create an account once. But again thanks for the tips. Check out the plugins by 'spanner' http://github.com/spanner/radiant-reader-extension http://github.com/spanner/radiant-forum-extension Many thanks. That seems to be the kind of things I'm looking for. The 'Beast'-based forum is not suitable, my client is used to vBulletin's rich feature set, and only another mature forum
[Radiant] Radiant capabilities
Hi, I'd like to know if Radiant or one of its extensions offers some capabilities I'm looking for for a site I need to write for a client. They want a 'magazine' type structure, with forum and blogs, using a single sign on. So someone can open an account, and be given permission to write articles. These are then approved by designated editors and published both to the front page, and to 'category' pages depending on what category the articles belong to. Comments may be left by visitors, who may or may not choose to sign up for an account on the site. All comments are moderated before being published. If they sign on with an account, they may choose to receive notifications via email when the comment is replied to. They may also edit their comments (again, which are moderated) if they sign up with an account before-hand. Visitors may use the forums on the site. I intend this to be something like phpBB, and somehow manipulate the phpBB cookies to make it a single sign on scheme. Visitors with accounts may be selected by moderators to have their own blogs. In addition, blog articles can be 'nominated' to the front page or a category page. In addition, there is a blogs page where the most recent blog articles from all authors are shown. This sounds like standard CMS stuff, doesn't it? The only sticking point seems to be the overall account scheme, where a single user account can do multiple things depending on what permissions it has. Will Radiant easily support these features, or is some hard development work required? Thanks, regards, Asfand Yar Qazi ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Disqus (was Re: Radiant capabilities)
2009/11/21 Sean Cribbs seancri...@gmail.com: One thing I've been meaning to mention, since it came up with my blog and with one of Marty Haught's sites with respect to Disqus: Make sure you manually set the page URL or other identifier, since their software seems to be sensitive to the existence or lack of trailing slashes. On a number of my blog posts, this has caused the creation of multiple threads for a single post. Here's two ways you can prevent that in your embed code: script var disqus_url = http://yoursite.comr:url /; /script or, even more strictly: script var disqus_identifier = r:id /; /script You can find more information here: http://disqus.com/docs/embed/ Cheers, Sean Thanks, will keep that in mind. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
