[Radiant] Search extension question
Hey guys, How do I set up a search field in my template that will take one to the search page and return results? My Rails-fu has gotten really rusty since going 100% Radiant and I cannot remember how to do it. Thanks, Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Odd behavior with copy_move and default_page_parts
It is actually not a bug with copy_move I don't think. Rather it is a byproduct of how default_page_parts is implemented. I don't know the exact terminology, but the dpp extension modifies the add_child template for and pages it is defined in. Unfortunately it is naive so even if the tabs already exist in the child they get created again. I assume the function gets triggered because copy_move just automagically fires add_child calls. Chaim Kirby chaim.ki...@childrens.harvard.edu Andrea Franz wrote: I'll try to fixit asap, maybe rewriting tests with rspec to be up to date with radiant. -- Andrea Franz http://gravityblast.com On 23/feb/09, at 21:42, Chaim Kirby chaim.ki...@childrens.harvard.edu wrote: 1.9.1, Git rev. 79ee39addf4adabcf28fe77a8cb9cbf2338feda8 (The one that works correctly with 0.6.9) Chaim chaim.ki...@childrens.harvard.edu Andrea Franz wrote: Hi Chaim, which version of copy_move are you using? On Mon, Feb 23, 2009 at 8:23 PM, Chaim Kirby chaim.ki...@childrens.harvard.edu wrote: Has anyone else run into this issue? I copied a tree of pages using the copy_move extension. Some of the pages use the default_page_parts extension to define page parts of children. Some of the children ended up with duplicate page parts, where only one had content. example: page_part_config --- - name: main - name: highlight Expected child page in copied hierarchy: Main(with content), Highlight(with content) Actual child page in copied hierarchy: Main, Highlight, Main(with content), Highlight(with content) Thanks, Chaim chaim.ki...@childrens.harvard.edu ___ 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 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] Question about search extension and site caching
I am using the search extension and I have posted my site to my dev server. The project is managed with git. I cap deployed to the server, then dumped my local db and imported it into the online server. Now the search term that I had last tested the search extension with is showing up in the search box at the top of the page. I don't understand how that search term was cached and included in the db. How can I refresh the cache to let go of this term? You can see what I am talking about here: http://stmc.andadv.com It's the top search box that I want to clear. This is the content from the snippet that the search box appears in: div id=aux_navbar spanCareers:/careers | Contact:mailto:i...@southtexasmedicalcenter.com form action=/search method=get id=search_forminput id=q name=q value=baptist size=15 alt=search type=text input value=Search type=submit/form/span /div Anyone have any idea how to fix this? ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Question about search extension and site caching
N. Turnage wrote: I am using the search extension and I have posted my site to my dev server... You know, some days it just isn't worth getting out of bed. I found that I had set a default value for the text field, and that's why it was always showing up. There is nothing more to see here. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Freezing non-Radiant gems?
Sean Cribbs wrote: You can generally unpack gems to vendor/plugins. As long as they have a 'lib' directory, they'll get added to the load path. Thanks Sean. I think this works. Off the top of your head, what would be the #1 reason for PageAttachments to result in my site showing 'Rails app failed to start'? It worked on my machine but fails on the server. All the other extensions work fine. Include PageAttachment and you get the error - remove it, and all's fine again. I do have the PageAttachments extension, attachment_fu and the server has rmagick. This is on Radiant 0.6.9 and Ruby 1.8.6 - the PageAttachments is the version tagged for 0.6.9. (I'm investigating further!) Cheers, Mohit. 2/25/2009 | 2:05 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Problems with templates_extension
I'm trying to us this with a 0.6.9 base implementation and get lots of errors like `type_column_header' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found!`type_column' default partial not found! I suspect I have a 0.7 version of templates. Either ... where can I get a 0.6.9 one or what do I have to do to get it to act like one suitable for a 0.6.9 site? Thanks -- I will not attack your doctrines nor your creeds if they accord liberty to me. If they hold thought to be dangerous - if they aver that doubt is a crime, then I attack them one and all, because they enslave the minds of men. --Robert Ingersoll (The Ghosts) ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Question about search extension and site caching
Nate, I can't check it out at the moment ( out of the office) but the query should not be in the db anywhere. The tag will list the last query, so if your page is cached it might just be in the page cache. I'll take a look and see if I can recreate your problem. -Jim On Feb 24, 2009, at 12:47, N. Turnage pixeln...@gmail.com wrote: I am using the search extension and I have posted my site to my dev server. The project is managed with git. I cap deployed to the server, then dumped my local db and imported it into the online server. Now the search term that I had last tested the search extension with is showing up in the search box at the top of the page. I don't understand how that search term was cached and included in the db. How can I refresh the cache to let go of this term? You can see what I am talking about here: http://stmc.andadv.com It's the top search box that I want to clear. This is the content from the snippet that the search box appears in: div id=aux_navbar spanCareers:/careers | Contact:mailto:i...@southtexasmedicalcenter.com form action=/search method=get id=search_forminput id=q name=q value=baptist size=15 alt=search type=text input value=Search type=submit/form/span /div Anyone have any idea how to fix this? ~Nate ___ 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
