[Radiant] Trailing slash for URLs
Hi all, search engines consider URLs /some-page and /some-page/ to be two different pages (well, at least Google analytics does). I'd like to get rid of that. Would you expect Radiant to redirect clients to the trailing-slash-form of an URL, or should that be the duty of the web server above? Any comments are appreciated. Regards, Christian ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] is Radiant the right platform for our project?
Hi Fima, what I love most about radiant is actually its extensibility plus the clean programming model that comes with Ruby on rails apps in general. Extending existing classes, adding your own models? Adding functionality to the lifecycle of entities? Custom rake tasks? It's all just some lines of code, clean and maintainable. Add specs and scripted deployment using Capistrano, and you're ready to go. Having said that, radiant itself seems to be targeted at projects involving small teams of dozens of users (with less administrative overhead) and rather low numbers of pages. Having thousands of users with hundreds of roles creating 10.000 pages isn't something that the standard radiant code base of radiant will handle too well. (This is my very personal opinion, I'd like to hear otherwise) [What I'm thinking about is the instantiation of Page objects, for example. Traversing very large trees of pages could lead to an increasing number of database queries quickly.] Plus, one of the strongest parts of radiant is the concept of radius tags, AFAIAC. Could you actually make use of them in such a scenario? Would users create blogs using radius tags? Or would you use them during development only? If so, you'd sooner or later recognize that implementations of radius tags are somewhat separated from the standard rails concept of controllers and helpers, let alone request and response data. This is perfectly fine for what they've been designed to do (give access to functionality of your data model within the view), but needs tweaks and workarounds when developers need some more low-level capabilities. Reading your list of requirements, I assume that most if not all has at least some opensource component to start from. Regarding radiant, it feels like you'd disable or ignore most of it's standard features and capabilities, basically building your own app around it. Maybe you're better off starting with a general-purpose rails template and adding stuff from the radiant code base that fits your requirements well. Regards, Christian Am 23.03.2010 um 07:21 schrieb Fima Leshinsky: Additionally, (very high-level) requirements are: * premium features + paypal integration (think premium themes, analytics, etc.) * social technologies (member profiles, messaging, etc.) * strong photo publishing experience * mobile support * private/public sites and blogs ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Tags for Last edited?
Am 02.03.2010 um 07:17 schrieb John Long: If you only need to deal with the children of a page you can do what you want with the children:each tag. There is no way to do this for pages on the whole site. That would be a useful extension though. Started a new repo on github, which is still quite uncommon to me. However, code is available: http://github.com/datenimperator/radiant-any-page http://ext.radiantcms.org/extensions/203-any-page Thanks for Radiant! Regards, Christian ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
[Radiant] Double routes
Hi all, running rake routes prints every route in my instance of radiant-0.8.1 twice. That is, it prints the set of routes completely, and prints it again. Any idea what could be causing this? I've disabled all extensions to see if I accidentally messed something up, but it didn't help. Regards, Christian ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
[Radiant] RBAC and admin tabs
Hi all, I found that it's actually fairly easy to restrict access to standard tabs to some RBAC roles. But there's a catch: My extension defines a new entity which is no page. Users with the role 'editor' will log in to edit its contents, and those users aren't allowed to do anything else. No Pages, Snippets or else. Unfortunately, the Pages tab is hardcoded in the welcome controller, disabling it leads to infinite redirects. (index of the welcome controller redirects to admin_pages_url) Maybe it would be better to have welcome:index redirect to the first accessible tab, whatever that might be? But how? Regards, Christian ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Radiant Digest, Vol 47, Issue 11
Bill,
that's what I thought. My model is called 'City', the controller is 'class
Admin::CitiesController Admin::ResourceController'
What I want to create is a class City which has content parts just like Page,
with filters and tag reference and everything. I assumed that it would be just
like with Page and PagePart, so I created City and CityPart.
The model itself works as expected, but I'm fighting with the controller, esp.
with the render_region method which is implemented in regions_helper.rb. When I
call it for whatever region in a template of my custom controller, it gives me:
undefined method `cities' for #Radiant::AdminUI:0x102036cd8
Extracted source (around line #5):
2:
3: h1Cities/h1
4:
5: %= render_region :top %
6:
7: pSome description/p
8:
Maybe I've got some naming wrong here, but according to the source code of
pages_controller.rb and page_parts_controller.rb I'm all set. I'm rather
clueless as to where to search for a solution next, so any help is greatly
appreciated. Regards,
Christian
Am 06.02.2010 um 21:29 schrieb Bill:
Christian,
Admin::ResourceController gives you CRUD methods so you don't have to define
them yourself. Methods like :index, :edit, :update, :new, :create, :delete
are built in.
So on a plugin I am working on I only define the show method (controller for
a podcast's Shows) to get a single 'Show' in my podcast...
class Admin::ShowsController Admin::ResourceController
model_class Show
before_filter :find_model, :only = [ :show ]
def show
respond_to do |format|
format.html # show.html.erb
format.xml { render :xml = @show }
end
end
private
def find_model
@show = Show.find(params[:id]) if params[:id]
end
end
Regards,
-Bill
pixelhandler
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org
Re: [Radiant] What does Admin::ResourceController do?
Hi banane, my code is packaged as an extension, however I stepped through the code of radiant to see how things worked there. Eventually, I followed this tutorial: http://wiki.github.com/radiant/radiant/creating-a-link-roll-extension http://wiki.github.com/radiant/radiant/removing-the-scaffold-from-the-link-roll-extension I created a new database entity that doesn't depend on radiants Page class, but is similar to it in some regards. There's a new UI in the admin section to work with that entity, plus a number of radius tags that make it available to Radiant pages. Regards, Christian ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
[Radiant] Virtual children pf pages
Hi all, A client needs kind of a directory website, like an employee directory, with pages for each employee. I'd like to propose a solution using Radiant. However, due to the amount of employees and the repetetive structure of those pages, it would be uncomfortable and hard to handle to create an individual page for each of them. The final directory URL structure should look like this: website root - employees - emp1 - Documents - Photos - emp2 - Documents - Photos - [employee n] - Documents - Photos Pages in Radiant would be: - employees (Type: Employee archive) - Documents for %1 (Type: Normal page) - Photos for %1 (Type: Normal page) I was wondering if the employees would be some kind of an archive extension, getting the list of employees from the database. A request for /employees/emp1/ would be handled by the archive, selecting the data for emp1 and getting the layout from the content of employees, effectively producing emp1's personal page. A request for /employees/emp1/documents/ would be handled by the archive, too, checking if there's a page below with a slug documents and getting it's content from there. I've done some RoR stuff but I'm rather new to Radiant (although I've dug through the code) It'd be most appreciated if you could spare some time to help me with these questions: (1) Is there something like this already? Are you aware of anything that's similar so I could start from something? (2) How would I make my list of employees behave like pages (and play nicely with the sitemap extension and others) - without them showing up on the pages tab? (3) What's best practice to expand variables in a document title (like Documents for %1 which should become Documents for John Doe) I'd love to use Radiant for this, so any help is welcome. Regards, Christian ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Wordpress migration
Hi, Am 20.01.2010 um 13:24 schrieb Dmitry Belitsky: Hello there, is there any tool for wordpress posts migration to radiant? none that I'm aware of. However, Wordpress has a XMLRPC interface, it should be pretty easy to get your WP posts converted into Radiant pages. Regards, Christian ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Rack 1.1.0
Sorry for replying to my own post, but is actually is easily fixable: Line 34 of lib/action_controller.rb of the packed actionpack lib inside radiant pins rack to versions up to 1.0.0. I've commented it out, no probs so far. Which leads me to another issue: What would it take to provide a version of radiant without pre-included rails? Is the radiant-provided version of rails different than the official release? I'd really like to have an option to install radiant as a single gem, with dependencies to standard rails and stuff. Any comments? Regards, Christian Am 07.01.2010 um 20:06 schrieb Christian Aust: my rack gem would like to update to something newer than the 1.0.0 that is required from somewhere inside Radiant 0.8.1 Unfortunately, Radiant doesn't start with a never version. Is that easy fixable? Is it just a pinned version somewhere, or is it a real dependency? Regards, ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] link on front-end to edit this_page if logged in
Hi all, Am 07.01.2010 um 20:01 schrieb Steven Southard: No I don't think so. Just a link to the admin page. It would just make it fast because you won't have to go to the admin and find the page you want to edit. If you have a lot of pages that can be a hassle. full ACK. That as well as previous/next page links on the admin screen, which would help tremendously. Regards, Christian ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Rack 1.1.0
Hi all, my rack gem would like to update to something newer than the 1.0.0 that is required from somewhere inside Radiant 0.8.1 Unfortunately, Radiant doesn't start with a never version. Is that easy fixable? Is it just a pinned version somewhere, or is it a real dependency? Regards, Christian ___ 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 performance
Hi Stefan, wonderful hint, I found that both the NavigationTags and the Feedreader extensions were wasting time. After optimization, rendering time went down from 2500-3000ms to 200-600ms per page. Not too bad... Regards, Christian Am 04.01.2010 um 10:19 schrieb qutic development: You might check out Rack::Bug to get an idea why the rendering time is that high: http://github.com/brynary/rack-bug Best regards Stefan ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Thinking Sphinx
Hi John, I've run into that issue, too. It's currently being discussed on the thinking-sphinx GoogleGroup http://groups.google.com/group/thinking-sphinx/browse_thread/thread/4ce0b8ebd94cfcb9?fwc=1 Removing the define_index method basically means disabling the indexing part of the extension, since define_index tells thinking-sphinx what parts of your AR model should go into the sphinx configuration. Since you already had a working configuration and index, it may very well be that the rest of the search actually works. Maybe you have a chance to head over to googlegroups and leave a quick me too to show your interest in that issue. Regards, Christian Am 06.01.2010 um 07:46 schrieb John Polling: Hi, I've recently upgraded to the 1.3.14 gem version of Thinking Sphinx and I know get this error when both running a search and running rake ts:index You have a nil object when you didn't expect it! You might have expected an instance of Array. The error occurred while evaluating nil. I've managed to pinpoint the problem to the define_index method in the SphinxSearch PageExtensions module. As soon as I remove this method all works fine. I'm not certain what the exact problem is in this method though. If anyone can quickly enlighten me it would be much appreciated. Thanks John ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Radiant performance
Hi all,
I've set up my new website http://software-consultant.net/ using Radiant 0.8.1
and a bunch of extensions. In particular, I use
* Archive
* Feed-Reader
* Markdown
* Blog
* Nested layouts
* Paperclipped attachments
* Reorder
* Tags
* Thinking-Sphinx search
* Navigation tags
* Sitemap
* Filesystem Import/Export
For production, the site is running on a dual-core AMD server, 6GB RAM with a
hardware RAID-1 under 64bit Ubuntu 8.0.4 LTS - pretty decent hosting for what
is basically a low-profile site. However, it takes Apache2/Passenger several
seconds (~2 seconds, sometimes up to 3) to fully render a page, and from the
rails logs I assume that it's not Apache being responsible for the delay. From
the current log:
Processing SiteController#show_page (for 109.90.135.63 at 2010-01-04
08:58:57) [GET]
Parameters: {action=show_page, url=[projekte,
redesign-webdynpro-java], controller=site}
Completed in 1792ms (DB: 40) | 200
[http://software-consultant.net/projekte/redesign-webdynpro-java/]
My layout consists of a master template, a page template for most of the
stuff and a project template inside page for URLs like the one mentioned
above. No recursion involved. I've got ~50 pages and 8 snippets.
I suspect feedreader to connect to the RSS source for every request, which I
will look into next. Removing the feedreader snippet from the layout doesn't
show much improvement though, so what's taking Radiant so long?
I've got other rails applications on the very same setup that act quickly, so I
guess it's not a general problem with my installation. Any comments? Your help
is appreciated very much. Kind regards,
Christian
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
