[Radiant] Re: Search patch (global tags)
David Piehler wrote:
Jan frederik Poulsen wrote:
Any help? I'm getting a bit desperate? :-(
The newest Search Extension code is in GitHub:
http://github.com/radiant/radiant-search-extension/tree/master
However, it removes the live search functionality. You might want to use
the download link and try it out anyways, because it should accomplish
your other goals.
- Dave
Also, here are my notes on using an older version of the Search
Extension. This might be helpful to you.
$ cd PATH/TO/PROJECT
$ svn export
http://svn.radiantcms.org/radiant/tags/rel_0-6-6/extensions/search
vendor/extensions/search
Add a new tag to
/PATH/TO/PROJECT/vendor/extensions/search/app/models/search_page.rb
### 2008-05-21 DP added new tag to check if a search has been submitted
desc %{Checks if a query was passed to the browser.}
tag 'search:if_submitted' do |tag|
unless @query ==
tag.expand
end
end
Be sure to set the Page Type to Search or else loading the page will
fail with an error about a missing tag.
The following is a good default Search page…
r:search:form label=Search for:/
div id=search_results
r:search:if_submitted
r:search:empty
h2Searching 'r:search:query/' returned no results./h2
/r:search:empty
r:search:results
h2Searching 'r:search:query/' returned:/h2
r:search:results:each
r:unless_content part=no-search
p
r:link/br /
r:truncate_and_strip
length=210r:content//r:truncate_and_strip
/p
/r:unless_content
/r:search:results:each
/r:search:results
/r:search:if_submitted
/div
You can prevent pages from being returned by adding a 'no-search'
page-part to them.
The above tag r:unless_content part=no-search is used to hide all
pages with a page-part of ‘no-search’ in the search results. This can
result in searches that return “Your search for ‘X’ returned the
following pages:” with no results below, but its better than showing
hidden pages.
- Dave
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Summer Reboot Update
Mohit Sindhwani wrote: Just a brief update on the Summer Reboot Documentation project. I just spent a couple of hours copying and moving stuff to the site from a couple of places to pull things into the project :) My schedule hasn't gone according to plan so far this summer, but I hope to attack this after I return home from vacation starting Friday the 25th. - Dave -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Has anyone added WMD to the admin interface?
Oli Studholme wrote: Has anyone added the WMD markdown editor to the admin interface yet? Or any WYSIWIG editor? I$B!G(Bm looking for some advice on the recommended way to do so. I've used WYMeditor. I like the interface a lot, and my clients like it too. It was a real pain to figure out what files to edit in order to widen/lengthen the textarea and remove unneeded buttons (all these WYSIWYGs are code-bloated), but I finally figured it out. I plan to add this info to the summer reboot documentation. - Dave -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Sitewide Assets
I've been thinking I'd try to tackle it, but I'm swamped and I'd love to see it started. On Jul 16, 2008, at 1:47 PM, Chris Parrish wrote: Ok, that's twice in one week (Jim Gay just asked for the same thing). I don't think this tag belongs in SnS since it depends on Page Attachments too but a new extension for it might be nice. Anyone willing to whip up a mini-extension that simply adds the necessary image tags to the Stylesheet object? I don't imagine there'd be much there to do -- I'm just not familiar enough with Page Attachments to know its tags? Otherwise I'll look into it in a couple of days. -Chris Josh Schairbaum wrote: Sean, That seems easy enough, I assume then that you are not using the Scripts N Styles extension then? Maybe that's the extension that needs to be written, making page_attachments work with scripts/n/ styles. I know SNS has a more 'pluggable' interface now. Josh On Jul 16, 2008, at 1:26 PM, Sean Cribbs wrote: Josh, Since things like background images are generally applied with CSS, I like to store my CSS in a Radiant page and then attach the images to that CSS page. Sean Josh Schairbaum wrote: How do people handle site-wide assets like background images? I'd like to keep everything about the site able to be uploaded/ changed. I've got the page_attachments extension, but that seems like it's only applicable to individual pages. I've looked at something like the paperclipped, but that seems to overwrite some of the page attachments functionality. http://github.com/kbingman/paperclipped/tree/master I'd like to use page_attachments, so what work-arounds are possible for sitewide stuff, outside of having to deploy them in public/images/*? Regards, Josh ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Developing Radiant site
On Tue, Jul 15, 2008 at 9:07 PM, Chris Parrish [EMAIL PROTECTED] wrote: Joe Van Dyk wrote: Hi, I'm new to Radiant, but not Rails. So, I'm seeing that stuff like the layout and CSS is entered through forms and saved to the database, and aren't contained in version controlled files. So, how does that work? I mean, how do you deploy changes? Just by copy/pasting the updated snippets and css stuff to the live site and enter it into the form? How do you version control it? Seems a little weird to me, perhaps I'm missing something? snip * And finally there's version tracking. Part of the problem here is are you just handling drafts while another live version is actively published, or are you trying to track every save that was ever made. The other issue is working it into Radiant's elegant UI. All the other approaches are more admin tools. This one would involve the user and versioning can really affect usability and workflow. To my knowledge, there isn't anything existing to tackle the third item yet (though it's mentioned as being on the development timeline). There'd be some happy campers if you want to roll out a first-class solution here (all the free beer and pizza you want at the big Radiant gatherings). Hope this helps (though I kind of wrote all this to document everything for me too). And if I've missed anyone's great extensions, please chime in. Well, here's what I'm doing: I've got some non-technical users that need to add content. They are just going to be editing the text, creating new pages, using the pages/behaviors/snippets that we set up for them. We are going to be doing the work on the layouts, behaviors, snippets, etc. There will be some extensions written as well. I don't necessarily have to version control the work we're doing (would be nice though), but just curious about the deploying/updating process. Could do hourly backups of the database, that would probably be good enough. Would another CMS work better for us? Thanks, Joe ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Preview functionality
On Wed, Jul 16, 2008 at 2:35 PM, Joe Van Dyk [EMAIL PROTECTED] wrote: On Tue, Jul 15, 2008 at 9:22 PM, Jamey Cribbs [EMAIL PROTECTED] wrote: I've created a Staging extension. You create a staging instance of the radiant app that can either reside on the same server as the production instance or another server. The extension gives you a Staging tab, where you can click a button to migrate the staging db to the production db. The extension also disables the admin functions on the production instance. So, the idea is that you make all your changes on the staging instance and once you like the way staging looks, you stage the db to production. There is also the ability to easily revert to a previous stage by simply clicking on a previous stage. There are some caveats. In order to make sure that all the foreign keys between tables don't get out of whack, I am doing bulk exports and and imports, completely outside of ActiveRecord. Because my client uses MySQL for their radiant app, I have coded it using the mysqldump and mysql source commands. So, right now, the extension only works for MySQL databases. My client just started using this extension this week. So far so good. I have started discussions with them about letting me open-source the extension, and so far, their response has been positive. There are a few technical issues I need to clean up before I could release the extension, but I hope to get these resolved and get permission from them to release it within the next two weeks. This is definitely not the ultimate answer for the whole preview/versioning thing needed in radiant. Its what I came up with to meet a specific client request in a minimum amount of time. If this sounds like something others could use/improve/build-on then I would love to get it open sourced. Interesting approach. A potential issue with that (at least for me) is that if I'm using extensions that need to store data, the data that's in the production database would be overwritten with the data from the staging db, especially if the entire database is dropped and recreated. I could get around that by just dropping and copying certain tables over, I suppose. Joe ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant The extension already handles that use case. In the config file for the extension, you can specify which tables, including extension tables, that you want to have staged to production. Then when you do a staging, only the tables you specified actually get exported from staging and imported into production. Likewise, you can also specify which admin tabs you want to be accessible from production. So, lets say you write an extension that logs stuff in a table on the production database and lets you view the log from an admin tab. It wouldn't make sense to only allow admin access to that tab on staging, cause the only data is in the production table of that extension. You can specify that that extension is accessible from the production admin screen, even though all of the other admin tabs are disabled on production. Jamey ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Sitewide Assets
Josh Schairbaum [EMAIL PROTECTED] writes: How do people handle site-wide assets like background images? I'd like to keep everything about the site able to be uploaded/changed. I've got the page_attachments extension, but that seems like it's only applicable to individual pages. I started created a generic Assets extension for this purpose but ended up just using the Gallery extension. I'd still prefer a simple Assets extension though. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Sitewide Assets
Paperclipped is intended to replace page_attachments, I wouldn't use both at the same time. I wanted to use something other than attachment_fu, so I wrote with different functionality than either gallery or page_attachments. I hope that it offers something that these do extensions do not. I actually use all three. There are several ways you could use page_attachments with site wide images. Sean's suggestion would be the easiest. Paperclipped uses the same file structure as paperclipped (as I had started using attachment_fu), so it is easy to switch if you wish. You could also add a tab to page_attachments, gaining acces to all the uploaded images images... Regards, Keith On Jul 16, 2008, at 7:14 PM, Josh Schairbaum wrote: How do people handle site-wide assets like background images? I'd like to keep everything about the site able to be uploaded/changed. I've got the page_attachments extension, but that seems like it's only applicable to individual pages. I've looked at something like the paperclipped, but that seems to overwrite some of the page attachments functionality. http://github.com/kbingman/paperclipped/tree/master I'd like to use page_attachments, so what work-arounds are possible for sitewide stuff, outside of having to deploy them in public/ images/*? Regards, Josh ___ 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] How does one keep track of GitHub?
Hi folks, I see all this excitement about GitHub. It's great that everyone can throw in their 2¢. It's like stepping on the gas. Now how about that steering wheel? What I don't get is how anyone can keep track of it. Before GitHub, it was hard enough to track all the extensions and which one went with which version of code base. Now it seems like an impossible task. Unfortunately I haven't been able to read the whole 'Summer Reboot Documentation' thread, so I don't know if anyone has addressed this in there. It seems to me that two things are needed to try to get this under control for new people coming on the scene, or those who can't keep up with the changes: 1) Some kind of news feed 2) Someone to take the news feed and compile it into the current 'state of the world' - weekly maybe? ... or am I out in left field? What I'm thinking of as a news feed would be something like this... July 16 - John started on the uber_fu extension July 16 - Tony released the fork of the uber_mailer extension July 15 - Jenna released the google_maps extension July 13 - Tony started a fork of the uber_mailer extension July 10 - Jenna started the google_maps extension How to make that happen? beats me. Tag blog entries with 'radiantcmsnewsfeed' and somehow find them and aggregate them into a single RSS feed? -Chris___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
