Re: [Radiant] Can't delete page parts
Hi Shaolo, Rails 2.3.5 with 0.8.1? Is that what you get from running ./script/server? I'm pretty sure 0.8.1 needs rails 2.3.4. Check that, otherwise I'm not sure. -Arthur ___ 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] Copy and Move extension
Shaolo, If you haven't look at the drag_order extension. It allows copying, moving and also reordering and does them all through the same less invasive dragging interface. -Arthur ___ 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] how do I add git submodule for reader extension
Pasting into terminal and running? The syntax is right, what's your problem? Perhaps you're just wondering how submodules work? -Arthur ___ 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] how do I add git submodule for reader extension
You aren't using git to track your main application then. You should probably look into sometime because it's a fantastic tool. For now though, just do: git clone git://github.com/spanner/radiant-reader-extension.git vendor/extensions/reader And possibly this if you don't want to worry about git: rm -rf vendor/extensions/reader/.git -Arthur ___ 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] how do I add git submodule for reader extension
In order to use git submodules, your main app must itself be a git repository. Just do the git clone like I showed. Using git submodules is just another way of managing code the author clearly likes. The reader extension does not require it. -Arthur ___ 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] wiki vandalism
Hi, Why not just revert it? Verison 111 looks relatively clean. Perhaps so as to not wipe out valid ones written since? Being rubyists though, the idea of doing computer work manually does not appeal much. Following on from Michael's idea of checking for /admin, I have written a spam-link-checker: http://gist.github.com/305466 It's been reliable for every link I've checked. Just paste the contents of the wiki page into the links_block string and run. It will go through each of the links and divide them into clean and suspicious, for the suspicious ones, it will give a reason. -Arthur ___ 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 CMS right for me?
Hi Cody, Radiant doesn't care what DB you're using, rails takes care of that. In order for you to interact with arbitrary tables, you will want to write your own extensions. Extensions add normal rails controllers, models, views etc. so if you have good rails experience you should pick it up just fine. With regards to CAS authentication, I have no idea. -Arthur ___ 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] Rails app to Radiant extension: problem - app already has User model
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. -Arthur ___ 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
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
Re: [Radiant] How to improve site performance?
Rob, Looking at http://www.snaplogic.com/ the first and biggest thing I would suggest would be to combine your 7 (not including ga_tracker) .js files into one. You could also look into using the google hosted versions of jquery and mootools. -Arthur ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Is it possible to exclude certain pages from being indexed by sphinx_search?
Hi Rob, I believe that on each page, clicking the more link under the title will reveal an option to not have that page searchable. -Arthur ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Best extension for Authorization / Role-Control
Hi Jeff, That depends, whether you're wanting to restrict end-users browsing the front end: http://github.com/spanner/radiant-reader_group-extension .or site editors in the backend: http://github.com/avonderluft/radiant-page-group-permissions-extension/network -Arthur ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Password-protecting radiant content
Hi Newbie, Have a look at: http://github.com/spanner/radiant-reader_group-extension It allows you to grant users access to sub-trees of your sites content, and have them log-in via the front-end interface. Perhaps useful for you too, it has a mechanism for creating users from csv input. -Arthur ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Copy_Move Extension still compatible with 0.8?
Hey Jeff, No insights into copy_move functionality, you could of course checkout a previous version, but I wonder why not use: http://github.com/bright4/radiant-drag-order Ajax copy, move and reorder all in one. -Arthur ___ 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 Distribution
Hi Edmund, Probably an excellent idea! I've been using many similar extensions, relevant here are: spanner/radiant-multi-site-extension spanner/radiant-reader-extension spanner/radiant-reader_group-extension spanner/radiant-reader_group-extension They're working mostly fine alongside: jgarber/radiant-chronicle-extension bright4/radiant-drag-order # beats reorder and copy_move! This would seem to be a very useful stack for someone providing an edit your own site service to multiple users. Another extension I find useful for this purpose is: p8/radiant-rbac_base-extension Which allows you to give users custom roles. I use this for more fine- grained control - a moderately advanced user is an asset_user, but not a layout_user which means they can see and access the former tab but not the latter. I wonder which of Aissac's extensions you had in mind? -Arthur ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant 0.9.0 RC1
Perhaps, then, you can suggest a source of How To for GIT for non-developers. There are no end of resources out there, my personal recommendation though: http://www-cs-students.stanford.edu/~blynn/gitmagic/ -Arthur ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SEO question
I already use this tags. But on a recent project it came to my mind, that as a starting point, it would be great if default values could be calculated from the content of the page. This would enhance the out-of-box SEO experience :-) Search engines themselves are designed to find the most significant words in a page. Writing out the keywords yourself you can have an insight that a computer can't, but it's hard to imagine an automatic feature that could outperform google in their field of expertise. -Arthur ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SEO question
if that would be true: why bother with meta tags?
Well, I would think because you can have insights into what's relevant
about a page that a search engine couldn't.
Like others have pointed out however, it seems the search engines are
unlikely to trust you anyway.
If you did want to go ahead though, this should be a good start:
tag 'meta_keywords' do |tag|
length = tag.attr[:length] || 15
blacklisted = %w[words that are too common or not relevant]
min_word_size = 3
words_from_body = tag.locals.page.part(body).content.gsub(/.*?
/, ).split(/[^a-zA-Z]/).uniq
allowed_words = words_from_body.delete_if { |word| word.size =
min_word_size } - blacklisted
keywords = allowed_words.first(length)
%{meta name='keywords' content='#{keywords.join(' ')}' /}
end
Hope it's easy enough to follow. Description could be done similarly,
but rules for picking what substring to pick for it are likely to be
site-specific.
-Arthur
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
