[Radiant] Re: Values of the Radiant community (and Ecommerce solution?)
I'm glad people like the feedback... Paul, do you have anyplace on the web where I can track the development of your extension? I suppose paypal does seem like the easiest solution. Ross On Jun 20, 7:58 am, Paul Noden wrote: > On 20 June 2011 15:28, Steven Southard wrote: > > > Paypal? It's only three items so a full on shopping cart seems overkill. > > Paypal would integrate well into what you have now and seems pretty > > legitimate in this day and age. > > Indeed, I've just implemented an extension which will be public soon which > deals with paypal payments on top of the reader extension. Will cater for > different sized payments within the next week or so. Provides validation > that payment has been processed (automatically via PayPal IPN) but > deliberately isn't designed to be a shopping cart such as > radiant-shop-extension which may otherwise be worth a look. > > Paul
[Radiant] Values of the Radiant community (and Ecommerce solution?)
I am consistently impressed with how helpful and friendly people are to another on this list. It's good to see. And I wonder about the role that geek practices such as the agile methodology play in this kind of friendly behavior. I've been reading more about agile and related practices (I am a writer, not a programmer), and I have been surprised at the emphasis, in those practices, on ethics such as collaboration, authenticity, appropriate conflict resolution, and so on. In Lyssa Adkins' book "Coaching Agile Teams," she emphasizes values such as courage, focus, respect, and openness. As someone with a professional background in counselling, I can't help but notice how much overlap there is between agile values and counselling values. It's very heartening to see such deep, resonant, ancient human values at work in contemporary practices such as software development. And the Radiant community, more than any other software development community that I've encountered, embodies those values in the communications on this forum. Thanks for walking your talk. Now, to my question: I'm looking for an ecommerce solution, to integrate with Radiant, that will allow me to sell my books (three of them) and my consulting services on my website (I'm running Radiant 0.9.1). Is something like Shopify a good option, or is there a simpler (or better) solution for someone like me? Thanks in advance. Ross Laird
[Radiant] Re: Tags and taggable
Thanks for the very helpful feedback. I now have a good sense of how to proceed. On a related note: with the increasing success of rails, and with Radiant as the leading rails cms, I think you're going to find more and more people like me (non-programmer tinkerers) using Radiant to build sites. Many of us will be migrating from Drupal and WordPress (which are very good systems, of course, just a bit different and perhaps a bit less fun...). So, there is definitely an opportunity to grow the Radiant community. Thanks again for the help. Ross On Mar 13, 6:25 pm, Jim Gay wrote: > Ross, > > That's a fine way to learn something. Doing is a better teacher than > anything else. > But i'd just make 2 projects to test out the different extensions. If > they do the same thing and use the same or similar tables then you're > asking for trouble. > It would be like using page_attachments and paperclipped together, > which both use the page_attachments table: you're bound to find > problems with both of them turned on. > And you would never do this in a real site, so it would be better to > compare 2 different projects locally and decide. > > If you want to use 1 project, you can turn them on or off by setting > "config.extensions -= [:tags]" (or taggable) to turn one off at a time > (in config/environment.rb) > Or just move one out of the vendor/extensions directory and restart, > then move it back and move the other out. > > Radiant (or any rails project) will run fine if there are extra and > unused tables in the database. So if one uses tags and the other uses > meta_tags, the presence of one table should not affect the other when > you disable either extension. > > I hope that helps. > > > > > > On Sun, Mar 13, 2011 at 8:47 PM, rosslaird wrote: > > Oops, hang on a sec: meta_tags and taggings are both from tags (as > > indicated above). > > I'm getting mixed up with all the name similarity here. > > So, it's just a matter of that one tags table and what to do with it. > > > Ross > > > On Mar 13, 5:39 pm, rosslaird wrote: > >> Jim, it's not so much that I have a problem I'm trying to solve but > >> rather that I'm just trying to learn Radiant. I like to try out > >> various things, see how they work, and figure out what's best for my > >> setup. I am not a programmer, so I find it very helpful to do things > >> like install an extension, set it up, and see what's possible. I find > >> this much easier than trying to figure out the code from behind the > >> scenes. Over the past few months I've learned most of what I need to > >> know to use and administer Radiant by installing, using, and sometimes > >> breaking various extensions. I find that this learning method -- while > >> far from efficient -- works quite well for me. > > >> Will, with this current situation, it sounds like the "tags" table may > >> not be from the tags extension at all but rather from another > >> extension that I have previously installed (like twitter tags, for > >> example). Thanks to your snippet above, I now know how to find the > >> names of the tables used by extensions. And this brings up the > >> question of whether I should just remove the tags table. I have > >> probably removed the extension that uses the tags table (I have > >> installed and removed various extensions), but it seems that the table > >> is still there (and taggable won't migrate for this reason). > > >> I am no mysql expert, but I can see that I have three tables: > > >> meta_tags > >> taggings > >> tags > > >> When I browse the meta_tags table, I see all the tags that show up on > >> my site with the tags extension. So, that seems to confirm what has > >> previously been said (the tags extension uses the meta_tags table). > >> When I browse the taggings table I see the structure but seemingly no > >> data added by me. Same with the tags table. So, the question is what > >> to do next. > > >> Taggable seems to have been partially installed. The migration seems > >> to have created one table (taggings) but has halted at the tags table > >> (which already exists). Should I remove the taggable extension (I > >> usually use the VERSION=0 method), or should I try to remove the tags > >> table, re-run the migration for taggable, then uninstall it (since I > >> should not be using both extensions at once)? Or does the order of > >> things matter here? > > >> Ross > > >> On Mar 13, 3:15
[Radiant] Re: Tags and taggable
Oops, hang on a sec: meta_tags and taggings are both from tags (as indicated above). I'm getting mixed up with all the name similarity here. So, it's just a matter of that one tags table and what to do with it. Ross On Mar 13, 5:39 pm, rosslaird wrote: > Jim, it's not so much that I have a problem I'm trying to solve but > rather that I'm just trying to learn Radiant. I like to try out > various things, see how they work, and figure out what's best for my > setup. I am not a programmer, so I find it very helpful to do things > like install an extension, set it up, and see what's possible. I find > this much easier than trying to figure out the code from behind the > scenes. Over the past few months I've learned most of what I need to > know to use and administer Radiant by installing, using, and sometimes > breaking various extensions. I find that this learning method -- while > far from efficient -- works quite well for me. > > Will, with this current situation, it sounds like the "tags" table may > not be from the tags extension at all but rather from another > extension that I have previously installed (like twitter tags, for > example). Thanks to your snippet above, I now know how to find the > names of the tables used by extensions. And this brings up the > question of whether I should just remove the tags table. I have > probably removed the extension that uses the tags table (I have > installed and removed various extensions), but it seems that the table > is still there (and taggable won't migrate for this reason). > > I am no mysql expert, but I can see that I have three tables: > > meta_tags > taggings > tags > > When I browse the meta_tags table, I see all the tags that show up on > my site with the tags extension. So, that seems to confirm what has > previously been said (the tags extension uses the meta_tags table). > When I browse the taggings table I see the structure but seemingly no > data added by me. Same with the tags table. So, the question is what > to do next. > > Taggable seems to have been partially installed. The migration seems > to have created one table (taggings) but has halted at the tags table > (which already exists). Should I remove the taggable extension (I > usually use the VERSION=0 method), or should I try to remove the tags > table, re-run the migration for taggable, then uninstall it (since I > should not be using both extensions at once)? Or does the order of > things matter here? > > Ross > > On Mar 13, 3:15 pm, William Ross wrote: > > > > > On 13 Mar 2011, at 20:40, rosslaird wrote: > > > > It seems that tags uses a 'tags' table. I am using the tags extension > > > (version 1.5), created by Benny Degezelle and Jim Gay. The version of > > > taggable that I am trying to run alongside tags is version 1.2.1, > > > created by you (Will). Both of these versions are the most recent > > > available from github. > > > > Maybe the tags extension that I am running is the incorrect one? It's > > > this one: > > > >https://github.com/jomz/radiant-tags-extension > > > Hm. I don't really know, since I use taggable for this kind of thing, but > > all I'm seeing here: > > > > > https://github.com/jomz/radiant-tags-extension/blob/master/db/migrate... > > > is the meta_tags and taggings tables. > > > > There are various other tags extensions listed on github (though all > > > the others seem to be qualified for a special application, such as > > > navigation). > > > > Before I go messing around with the tags extension (which I will > > > surely mess up even more), maybe this is simply a matter of getting > > > the correct tags extension. (Maybe?) > > > I guess that depends what you're aiming to do. Both will do the job of > > tagging pages and then getting at them through tag clouds and other lists. > > Taggable is more general purpose but not so well-prepared out of the box. > > > best, > > > will > > > > Ross > > > > On Mar 13, 6:51 am, William Ross wrote: > > >> On 12 Mar 2011, at 22:18, rosslaird wrote: > > > >>> I have the tags extension installed, and I want to try out taggable. > > >>> But it seems that both use a table called "tags," and this causes the > > >>> migration of taggable to halt. I suppose I will have to remove the > > >>> tags extension to install taggable, but if there is another way to do > > >>> this (so that I preserve both extensions) that would be preferable. >
[Radiant] Re: Tags and taggable
Jim, it's not so much that I have a problem I'm trying to solve but rather that I'm just trying to learn Radiant. I like to try out various things, see how they work, and figure out what's best for my setup. I am not a programmer, so I find it very helpful to do things like install an extension, set it up, and see what's possible. I find this much easier than trying to figure out the code from behind the scenes. Over the past few months I've learned most of what I need to know to use and administer Radiant by installing, using, and sometimes breaking various extensions. I find that this learning method -- while far from efficient -- works quite well for me. Will, with this current situation, it sounds like the "tags" table may not be from the tags extension at all but rather from another extension that I have previously installed (like twitter tags, for example). Thanks to your snippet above, I now know how to find the names of the tables used by extensions. And this brings up the question of whether I should just remove the tags table. I have probably removed the extension that uses the tags table (I have installed and removed various extensions), but it seems that the table is still there (and taggable won't migrate for this reason). I am no mysql expert, but I can see that I have three tables: meta_tags taggings tags When I browse the meta_tags table, I see all the tags that show up on my site with the tags extension. So, that seems to confirm what has previously been said (the tags extension uses the meta_tags table). When I browse the taggings table I see the structure but seemingly no data added by me. Same with the tags table. So, the question is what to do next. Taggable seems to have been partially installed. The migration seems to have created one table (taggings) but has halted at the tags table (which already exists). Should I remove the taggable extension (I usually use the VERSION=0 method), or should I try to remove the tags table, re-run the migration for taggable, then uninstall it (since I should not be using both extensions at once)? Or does the order of things matter here? Ross On Mar 13, 3:15 pm, William Ross wrote: > On 13 Mar 2011, at 20:40, rosslaird wrote: > > > It seems that tags uses a 'tags' table. I am using the tags extension > > (version 1.5), created by Benny Degezelle and Jim Gay. The version of > > taggable that I am trying to run alongside tags is version 1.2.1, > > created by you (Will). Both of these versions are the most recent > > available from github. > > > Maybe the tags extension that I am running is the incorrect one? It's > > this one: > > >https://github.com/jomz/radiant-tags-extension > > Hm. I don't really know, since I use taggable for this kind of thing, but all > I'm seeing here: > > > https://github.com/jomz/radiant-tags-extension/blob/master/db/migrate... > > is the meta_tags and taggings tables. > > > There are various other tags extensions listed on github (though all > > the others seem to be qualified for a special application, such as > > navigation). > > > Before I go messing around with the tags extension (which I will > > surely mess up even more), maybe this is simply a matter of getting > > the correct tags extension. (Maybe?) > > I guess that depends what you're aiming to do. Both will do the job of > tagging pages and then getting at them through tag clouds and other lists. > Taggable is more general purpose but not so well-prepared out of the box. > > best, > > will > > > > > > > Ross > > > On Mar 13, 6:51 am, William Ross wrote: > >> On 12 Mar 2011, at 22:18, rosslaird wrote: > > >>> I have the tags extension installed, and I want to try out taggable. > >>> But it seems that both use a table called "tags," and this causes the > >>> migration of taggable to halt. I suppose I will have to remove the > >>> tags extension to install taggable, but if there is another way to do > >>> this (so that I preserve both extensions) that would be preferable. > >>> Ideas and suggestions most welcome. > > >> I thought the tags extension used a 'meta_tags' table and MetaTag object? > >> They ought to be compatible in the sense that you can install one and then > >> the other without destructive side effects. > > >> You might even be able to run them side by side: taggable takes over the > >> keywords field where tags adds its own text-to-tags process. I wouldn't > >> recommend it, though: there are likely to be odd method-name clashes and > >> some admin UI collisions are likely. It will be hard to evaluate them, > >> even if they work. > > >> best, > > >> will
[Radiant] Re: Tags and taggable
Though, upon reflection, it sounds like what you're really saying is that even if I can run them alongside one another, it's not a good idea to do so. On Mar 13, 1:40 pm, rosslaird wrote: > It seems that tags uses a 'tags' table. I am using the tags extension > (version 1.5), created by Benny Degezelle and Jim Gay. The version of > taggable that I am trying to run alongside tags is version 1.2.1, > created by you (Will). Both of these versions are the most recent > available from github. > > Maybe the tags extension that I am running is the incorrect one? It's > this one: > > https://github.com/jomz/radiant-tags-extension > > There are various other tags extensions listed on github (though all > the others seem to be qualified for a special application, such as > navigation). > > Before I go messing around with the tags extension (which I will > surely mess up even more), maybe this is simply a matter of getting > the correct tags extension. (Maybe?) > > Ross > > On Mar 13, 6:51 am, William Ross wrote: > > > > > On 12 Mar 2011, at 22:18, rosslaird wrote: > > > > I have the tags extension installed, and I want to try out taggable. > > > But it seems that both use a table called "tags," and this causes the > > > migration of taggable to halt. I suppose I will have to remove the > > > tags extension to install taggable, but if there is another way to do > > > this (so that I preserve both extensions) that would be preferable. > > > Ideas and suggestions most welcome. > > > I thought the tags extension used a 'meta_tags' table and MetaTag object? > > They ought to be compatible in the sense that you can install one and then > > the other without destructive side effects. > > > You might even be able to run them side by side: taggable takes over the > > keywords field where tags adds its own text-to-tags process. I wouldn't > > recommend it, though: there are likely to be odd method-name clashes and > > some admin UI collisions are likely. It will be hard to evaluate them, even > > if they work. > > > best, > > > will
[Radiant] Re: Tags and taggable
It seems that tags uses a 'tags' table. I am using the tags extension (version 1.5), created by Benny Degezelle and Jim Gay. The version of taggable that I am trying to run alongside tags is version 1.2.1, created by you (Will). Both of these versions are the most recent available from github. Maybe the tags extension that I am running is the incorrect one? It's this one: https://github.com/jomz/radiant-tags-extension There are various other tags extensions listed on github (though all the others seem to be qualified for a special application, such as navigation). Before I go messing around with the tags extension (which I will surely mess up even more), maybe this is simply a matter of getting the correct tags extension. (Maybe?) Ross On Mar 13, 6:51 am, William Ross wrote: > On 12 Mar 2011, at 22:18, rosslaird wrote: > > > I have the tags extension installed, and I want to try out taggable. > > But it seems that both use a table called "tags," and this causes the > > migration of taggable to halt. I suppose I will have to remove the > > tags extension to install taggable, but if there is another way to do > > this (so that I preserve both extensions) that would be preferable. > > Ideas and suggestions most welcome. > > I thought the tags extension used a 'meta_tags' table and MetaTag object? > They ought to be compatible in the sense that you can install one and then > the other without destructive side effects. > > You might even be able to run them side by side: taggable takes over the > keywords field where tags adds its own text-to-tags process. I wouldn't > recommend it, though: there are likely to be odd method-name clashes and some > admin UI collisions are likely. It will be hard to evaluate them, even if > they work. > > best, > > will
[Radiant] Tags and taggable
I have the tags extension installed, and I want to try out taggable. But it seems that both use a table called "tags," and this causes the migration of taggable to halt. I suppose I will have to remove the tags extension to install taggable, but if there is another way to do this (so that I preserve both extensions) that would be preferable. Ideas and suggestions most welcome. Ross
[Radiant] Re: How to take advantage of server-side caching (Rack cache) without using browser caching
I can find various online postings and tutorials about increasing the cache in rails, but is there a conventional way to do this in Radiant? In other words, how do you do this: > The default cache timeout is only five minutes, though. I normally increase > that to at least a week. Ross
[Radiant] Re: Conditional tags wiki info: typo or user ignorance?
Yes, works! Thanks very much for your help. (I had to change your snippet from /about$ to /about, but after that it worked like a charm.) On Mar 4, 5:05 pm, Jomz wrote: > doesn't make much sense.. It means any url > starting with a /, so ... any url. This will indeed always render. > > means if we are not on the /about > page, so this will also render on every page except the about page. > > I think this is what you're after: > > r:unless_url> > > > > > regards, > Benny > > On Feb 23, 7:52 pm, rosslaird wrote: > > > > > > > > > Thanks for the help, Will. > > > I must be misunderstanding this in a fundamental way. > > Here's what I have in my layout: > > > > > > > > > > > > > > > > > > > > > > > > > > By my reckoning, that should render all the snippets -- including the > > slider, which has the About Me info -- on every page except the /about > > page, for which the above code is intended to remove the slider. But > > what happens in the above scenario is that the snippets are rendered > > twice on every page (This creates such a messy page that I have not > > even looked for the slider snippet to see if it is rendered twice. I > > think I should fix the reproduction first.) > > > What am I missing? > > > On Feb 23, 9:16 am, William Ross wrote: > > > > On 23 Feb 2011, at 17:01, rosslaird wrote: > > > > > In the radiant wiki over on github (I am posting this here because the > > > > wiki on github seems to have very low readership), the conditional > > > > tags page show this example code: > > > > > > > > > > > > > Radiant Handbook > > > > > > > > > > > > - Radiant Handbook > > > > > > > > > > > > > The documentation goes on to say that "the code above would set the > > > > page title as “Radiant Handbook” on the homepage, but for all subpages > > > > it would use the title of the page, then “… – Radiant Handbook”. > > > > > Now, when I look at the url regexp in the first bit (if_url matches), > > > > then I look at the regexp in the second bit (unless_url), these two > > > > expressions look *exactly the same* to me. Each one is "^/$". Am I > > > > blind, or are they the same? And if they are the same, should they be? > > > > And if not, what should they be? > > > > The lack of an else clause in radius makes for rather clumsy notation > > > sometimes: this is really just an if/then/else construction to check for > > > rootpageness. In radius that has to be written as if and then unless with > > > the same condition. In this example the path stays the same so that the > > > same condition is applied first positively then negatively. > > > > > I am trying to show an "About Me" link (in an id that slides in and > > > > out with JS) on my site on every page except the /about page (which > > > > already is about me...). It seems that if_url and unless_url are the > > > > way to go here, but I can't seem to get it to work. And I'm wondering > > > > is the reason for that has to do with the example code I've been > > > > adapting. I just changed the unless_url link to > > > matches="^/about/$">, but no dice. The About Me link still shows on > > > > that page. > > > > Your regex should work for /about/, but it does depend on the url that is > > > requested. It's a rails quirk that /about and /about/ are considered the > > > same path, for example. Partial matches are fine so if the site is simple > > > you might have better results with . > > > Depending on the server, you may also want to set ignore_case="true". > > > > best, > > > > will
[Radiant] Re: Use overrides.css to change the look of the front page?
My approach has been to place all css files in /css (and all javascript in /js). I assume this folder will not be over-written by future updates. These non-standard folders probably violate the principle of convention over configuration, but the fact that the folders are outside of /stylesheets and /javascripts -- and therefore will not be messed with (I hope!) in future upgrades -- makes me more comfortable. On Feb 27, 1:51 am, Mel wrote: > You should make you style changes to admin/overrides.css so that they > do not get written over by future updates. > > On Feb 27, 2:33 pm, BIO wrote: > > > > > > > > > No! I see admin/pages/styles now - this is too easy. > > > On Feb 26, 9:08 pm, BIO wrote: > > > > I'm new to Radiant and I've set up a site using the "styled blog" > > > option (very nice, this Radiant). > > > > I'd like to change various colors and dimensions of the front page and > > > at the top of the public/stylesheets/admin/overrides.css file I see > > > that it says: > > > > "Make your custom overrides here. This file will not be updated by > > > Radiant" > > > > Is this the right way?
[Radiant] Re: Conditional tags wiki info: typo or user ignorance?
Thanks for the help, Will. I must be misunderstanding this in a fundamental way. Here's what I have in my layout: By my reckoning, that should render all the snippets -- including the slider, which has the About Me info -- on every page except the /about page, for which the above code is intended to remove the slider. But what happens in the above scenario is that the snippets are rendered twice on every page (This creates such a messy page that I have not even looked for the slider snippet to see if it is rendered twice. I think I should fix the reproduction first.) What am I missing? On Feb 23, 9:16 am, William Ross wrote: > On 23 Feb 2011, at 17:01, rosslaird wrote: > > > > > > > > > > > In the radiant wiki over on github (I am posting this here because the > > wiki on github seems to have very low readership), the conditional > > tags page show this example code: > > > > > > > Radiant Handbook > > > > > > - Radiant Handbook > > > > > > > The documentation goes on to say that "the code above would set the > > page title as “Radiant Handbook” on the homepage, but for all subpages > > it would use the title of the page, then “… – Radiant Handbook”. > > > Now, when I look at the url regexp in the first bit (if_url matches), > > then I look at the regexp in the second bit (unless_url), these two > > expressions look *exactly the same* to me. Each one is "^/$". Am I > > blind, or are they the same? And if they are the same, should they be? > > And if not, what should they be? > > The lack of an else clause in radius makes for rather clumsy notation > sometimes: this is really just an if/then/else construction to check for > rootpageness. In radius that has to be written as if and then unless with the > same condition. In this example the path stays the same so that the same > condition is applied first positively then negatively. > > > I am trying to show an "About Me" link (in an id that slides in and > > out with JS) on my site on every page except the /about page (which > > already is about me...). It seems that if_url and unless_url are the > > way to go here, but I can't seem to get it to work. And I'm wondering > > is the reason for that has to do with the example code I've been > > adapting. I just changed the unless_url link to > matches="^/about/$">, but no dice. The About Me link still shows on > > that page. > > Your regex should work for /about/, but it does depend on the url that is > requested. It's a rails quirk that /about and /about/ are considered the same > path, for example. Partial matches are fine so if the site is simple you > might have better results with . Depending on > the server, you may also want to set ignore_case="true". > > best, > > will
[Radiant] Conditional tags wiki info: typo or user ignorance?
In the radiant wiki over on github (I am posting this here because the wiki on github seems to have very low readership), the conditional tags page show this example code: Radiant Handbook - Radiant Handbook The documentation goes on to say that "the code above would set the page title as “Radiant Handbook” on the homepage, but for all subpages it would use the title of the page, then “… – Radiant Handbook”. Now, when I look at the url regexp in the first bit (if_url matches), then I look at the regexp in the second bit (unless_url), these two expressions look *exactly the same* to me. Each one is "^/$". Am I blind, or are they the same? And if they are the same, should they be? And if not, what should they be? I am trying to show an "About Me" link (in an id that slides in and out with JS) on my site on every page except the /about page (which already is about me...). It seems that if_url and unless_url are the way to go here, but I can't seem to get it to work. And I'm wondering is the reason for that has to do with the example code I've been adapting. I just changed the unless_url link to , but no dice. The About Me link still shows on that page. So I suppose I have two questions: does the wiki have a typo, and how do I get this if/unless pair to work in my situation?
[Radiant] Re: Problem with 'rake radiant:extensions:tags:install'
I'm a newbie too, so I'm a little worried about misdirecting you due to my own lack of knowledge, but I have run into this type of problem several times. In my case, it has always been due to the fact that rake looks for a different database than the one I want the extension to be installed into. For example, rake seems to look for the development database by default, whereas my setup uses the production database. So, when I run rake, I have to specify that it use the production database. I see in your error listing, right near the top, that it says "SQLite3::SQLException: no such table:". This seems to suggest, to me anyway, that rake is looking for a table that does not exist. Is it possible that you are having the same issue that has happened to me, i.e. that you are running in production mode and rake is looking for the development database? If that is the case, here's what I do. I just specify "production" on the command line (there seem to be several ways to do this): rake production radiant:extensions:tags:install You can also use this type of syntax: rake migrate RAILS_ENV=production ... I hope I have not completely misunderstood the situation. As I said, I'm a newbie also. Ross On Feb 19, 12:38 am, wenp...@mac.com wrote: > Hi, > > I'm new to Radiant and even Ruby on Rails in general. I installed > Radiant on my local machine to try it out. Out of the box, I love it > so far. I tried to install the tags extension and followed the > instructions exactly as prescribed in the README listed on the > extension's page: > > 1. Copy the extension to your vendor/extensions directory as you would > any other extension. > 2. Run 'rake radiant:extensions:tags:install' > > I get an error after step 2 above, and I have no clue what's going on > (probably because I'm a noob). > > Here are my outputs: > > $ >./script/extension install tags > Cloning into tags... > remote: Counting objects: 905, done. > remote: Compressing objects: 100% (483/483), done. > remote: Total 905 (delta 392), reused 836 (delta 359) > Receiving objects: 100% (905/905), 196.77 KiB | 215 KiB/s, done. > Resolving deltas: 100% (392/392), done. > > $>rake radiant:extensions:tags:install --trace > (in /Users/wen/Documents/radiant/wenphan) > ** Invoke radiant:extensions:tags:install (first_time) > ** Invoke environment (first_time) > ** Execute environment > ** Invoke radiant:extensions:tags:migrate (first_time) > ** Invoke environment > ** Execute radiant:extensions:tags:migrate > rake aborted! > SQLite3::SQLException: no such table: extension_meta: SELECT > schema_version FROM extension_meta WHERE name = 'Tags' > /Users/wen/.gem/ruby/1.8/gems/radiant-0.9.1/vendor/rails/activerecord/ > lib/active_record/connection_adapters/abstract_adapter.rb:221:in `log' > /Users/wen/.gem/ruby/1.8/gems/radiant-0.9.1/vendor/rails/activerecord/ > lib/active_record/connection_adapters/sqlite_adapter.rb:172:in > `execute' > /Users/wen/.gem/ruby/1.8/gems/radiant-0.9.1/vendor/rails/activerecord/ > lib/active_record/connection_adapters/sqlite_adapter.rb:417:in > `catch_schema_changes' > /Users/wen/.gem/ruby/1.8/gems/radiant-0.9.1/vendor/rails/activerecord/ > lib/active_record/connection_adapters/sqlite_adapter.rb:172:in > `execute' > /Users/wen/.gem/ruby/1.8/gems/radiant-0.9.1/vendor/rails/activerecord/ > lib/active_record/connection_adapters/sqlite_adapter.rb:320:in > `select' > /Users/wen/.gem/ruby/1.8/gems/radiant-0.9.1/vendor/rails/activerecord/ > lib/active_record/connection_adapters/abstract/database_statements.rb: > 7:in `select_all_without_query_cache' > /Users/wen/.gem/ruby/1.8/gems/radiant-0.9.1/vendor/rails/activerecord/ > lib/active_record/connection_adapters/abstract/query_cache.rb:62:in > `select_all' > /Users/wen/.gem/ruby/1.8/gems/radiant-0.9.1/vendor/rails/activerecord/ > lib/active_record/connection_adapters/abstract/database_statements.rb: > 13:in `select_one' > /Users/wen/.gem/ruby/1.8/gems/radiant-0.9.1/vendor/rails/activerecord/ > lib/active_record/connection_adapters/abstract/database_statements.rb: > 19:in `select_value' > /Users/wen/.gem/ruby/1.8/gems/radiant-0.9.1/lib/radiant/ > extension_migrator.rb:42:in `initialize_extension_schema_migrations' > /Users/wen/.gem/ruby/1.8/gems/radiant-0.9.1/lib/radiant/ > extension_migrator.rb:25:in `initialize' > /Users/wen/.gem/ruby/1.8/gems/radiant-0.9.1/vendor/rails/activerecord/ > lib/active_record/migration.rb:401:in `new' > /Users/wen/.gem/ruby/1.8/gems/radiant-0.9.1/vendor/rails/activerecord/ > lib/active_record/migration.rb:401:in `up' > /Users/wen/.gem/ruby/1.8/gems/radiant-0.9.1/vendor/rails/activerecord/ > lib/active_record/migration.rb:383:in `migrate' > /Users/wen/.gem/ruby/1.8/gems/radiant-0.9.1/lib/radiant/ > extension_migrator.rb:7:in `migrate' > /Users/wen/Documents/radiant/wenphan/vendor/extensions/tags/lib/tasks/ > tags_extension_tasks.rake:14 > /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/ > gems/1.8/gems/rake-0.8.3/lib/rake.rb:617:in `call' > /System/L
[Radiant] Extract the number from the tag list
I am new to Radiant, and not a (real) programmer, but I am persistent and willing to try things. Here's what I'm trying to do with the tags extension: extract the number from the output, style it with css as an em element, remove the parentheses around the number, and move the number to before the tag name in the output. So the output, which currently looks like this: tag_name (1) would look like this: 1 tag_name I can see a couple of places in the tag extension files where it looks like the output is defined, but I don't know enough to feel confident changing that stuff. Suggestions are most welcome.
[Radiant] Re: Contact form debugging as Radiant new user learning opportunity...
I migrated my localhost Radiant setup to Dreamhost (holy smokes was that very easy, compared to Drupal!), and the contact form is now working perfectly. It must have been a behind-the-scenes email delivery issue. Thanks for the help, though. On Dec 8, 9:13 am, rosslaird wrote: > Yes, that's the mailer extension that I am using. I installed it by > (precisely) following the instructions on github and in the manual. > > On Dec 8, 8:08 am, john muhl wrote: > > > > > > > > > On Wed, Dec 8, 2010 at 9:55 AM, rosslaird wrote: > > > I am a new user to Radiant (coming from Drupal), and so far I've found > > > Radiant to be a great application. I have also received excellent help > > > from the community (here and on github), and this is also great. > > > (Actually, a strong and helpful community is the most important thing > > > of all.) I have almost finished rebuilding my website in Radiant, but > > > I just need to get the contact form working properly. I have installed > > > and setup the mailer extension and the contact form. The form seems to > > > work, but does not redirect me to the thanks page. Also I do not > > > receive the email (I'm working from localhost at the moment, on > > > Ubuntu, so the fact that I do not get the email is not overly > > > surprising. It could be caused by a number of things, though the mailq > > > is empty). The log, however, says "Sent mail to em...@address.com," so > > > at least something is working. I am in the process now of debugging > > > this, and I've started to look at various posts that discuss > > > validation, changing environments.rb, and so on. Before I wade too > > > deeply into this process, I thought I'd ask for a bit of help. I don't > > > want to do anything to break the whole system. So: > > > > 1. I've seen in various posts that I should add some email info to > > > environments.rb. There is currently no reference to such things in > > > that file. In the following two tutorials (let's hope the url's don't > > > get scrubbed here), different methods of adding email details are > > > offered: > > > >http://railsforum.com/viewtopic.php?id=404 > > >http://wiki.rubyonrails.org/rails/pages/HowToSendEmailsWithActionMailer > > > > Which of these should I use, or should I do something else? For now, I > > > have simply changed one line in environment.rb, as suggested by the > > > mailer documentation. I changed this: > > > > config.frameworks -= [ :action_mailer ] > > > > To this: > > > > config.frameworks -= [ ] > > > > So, I haven't added mailing details (smtp, user, and so on) anywhere. > > > Perhaps that's the place to start. Suggestions most welcome. > > > doeshttps://github.com/radiant/radiant/wiki/mailer-extensionhelpat all?
[Radiant] Re: Contact form debugging as Radiant new user learning opportunity...
Yes, that's the mailer extension that I am using. I installed it by (precisely) following the instructions on github and in the manual. On Dec 8, 8:08 am, john muhl wrote: > On Wed, Dec 8, 2010 at 9:55 AM, rosslaird wrote: > > I am a new user to Radiant (coming from Drupal), and so far I've found > > Radiant to be a great application. I have also received excellent help > > from the community (here and on github), and this is also great. > > (Actually, a strong and helpful community is the most important thing > > of all.) I have almost finished rebuilding my website in Radiant, but > > I just need to get the contact form working properly. I have installed > > and setup the mailer extension and the contact form. The form seems to > > work, but does not redirect me to the thanks page. Also I do not > > receive the email (I'm working from localhost at the moment, on > > Ubuntu, so the fact that I do not get the email is not overly > > surprising. It could be caused by a number of things, though the mailq > > is empty). The log, however, says "Sent mail to em...@address.com," so > > at least something is working. I am in the process now of debugging > > this, and I've started to look at various posts that discuss > > validation, changing environments.rb, and so on. Before I wade too > > deeply into this process, I thought I'd ask for a bit of help. I don't > > want to do anything to break the whole system. So: > > > 1. I've seen in various posts that I should add some email info to > > environments.rb. There is currently no reference to such things in > > that file. In the following two tutorials (let's hope the url's don't > > get scrubbed here), different methods of adding email details are > > offered: > > >http://railsforum.com/viewtopic.php?id=404 > >http://wiki.rubyonrails.org/rails/pages/HowToSendEmailsWithActionMailer > > > Which of these should I use, or should I do something else? For now, I > > have simply changed one line in environment.rb, as suggested by the > > mailer documentation. I changed this: > > > config.frameworks -= [ :action_mailer ] > > > To this: > > > config.frameworks -= [ ] > > > So, I haven't added mailing details (smtp, user, and so on) anywhere. > > Perhaps that's the place to start. Suggestions most welcome. > > doeshttps://github.com/radiant/radiant/wiki/mailer-extensionhelp at all?
[Radiant] Contact form debugging as Radiant new user learning opportunity...
I am a new user to Radiant (coming from Drupal), and so far I've found Radiant to be a great application. I have also received excellent help from the community (here and on github), and this is also great. (Actually, a strong and helpful community is the most important thing of all.) I have almost finished rebuilding my website in Radiant, but I just need to get the contact form working properly. I have installed and setup the mailer extension and the contact form. The form seems to work, but does not redirect me to the thanks page. Also I do not receive the email (I'm working from localhost at the moment, on Ubuntu, so the fact that I do not get the email is not overly surprising. It could be caused by a number of things, though the mailq is empty). The log, however, says "Sent mail to em...@address.com," so at least something is working. I am in the process now of debugging this, and I've started to look at various posts that discuss validation, changing environments.rb, and so on. Before I wade too deeply into this process, I thought I'd ask for a bit of help. I don't want to do anything to break the whole system. So: 1. I've seen in various posts that I should add some email info to environments.rb. There is currently no reference to such things in that file. In the following two tutorials (let's hope the url's don't get scrubbed here), different methods of adding email details are offered: http://railsforum.com/viewtopic.php?id=404 http://wiki.rubyonrails.org/rails/pages/HowToSendEmailsWithActionMailer Which of these should I use, or should I do something else? For now, I have simply changed one line in environment.rb, as suggested by the mailer documentation. I changed this: config.frameworks -= [ :action_mailer ] To this: config.frameworks -= [ ] So, I haven't added mailing details (smtp, user, and so on) anywhere. Perhaps that's the place to start. Suggestions most welcome. Ross
[Radiant] Re: image 404s
Oh wait, I found it: https://github.com/radiant/radiant/wiki/Uninstalling-Extensions A nice wiki page on how to uninstall extensions. Don't know how I missed that. On Dec 2, 6:08 am, rosslaird wrote: > I started to wonder if this was related to the chronicle extension > after I grep'ed for various of the 404-causing files and found > references to these files: > > ./vendor/extensions/chronicle/app/views/admin/snippets/index.html.haml > ./vendor/extensions/chronicle/public/javascripts/admin/chronicle.js > ./vendor/extensions/chronicle/public/javascripts/admin/HelpBalloon.js > ./vendor/extensions/chronicle/app/helpers/admin/timeline_helper.rb > > Then I saw Will's response. So, although I do like the chronicle > extension, is the solution to remove it (at least for now, until it is > updated)? And, if so, I can't find documentation anywhere on how to do > that. (I have removed extensions from redmine by just deleting their > directories, but this is not best practice I'm sure.) > > On Dec 2, 12:13 am, William Ross wrote: > > > On 2 Dec 2010, at 00:25, rosslaird wrote: > > > > I have just started using Radiant (which is just great, by the way), > > > so apologies in advance for what may be a very simple question: the > > > server log shows various 404s to image files: button.png and new- > > > snippet.png are two examples. My setup is on locahost, for testing, so > > > the 404 refers to (for example) this > > > url:http://localhost/images/admin/button.png. > > > Both of those are files used by older versions of the admin interface. The > > most likely explanation is that one of your extensions is not up to date: > > being contemporary with an older version of radiant it is assuming the > > presence of files that don't exist any more. > > > Radiant's helper methods mean that the author probably didn't need to spell > > out the image path, but something like this (in your radiant instance > > directory) should show you where it's coming from: > > > grep -r 'new-snippet' . > > > I don't get any matches from a normal radiant site except in old log files. > > > best, > > > will > > > > There are quite a few image files in /images/admin, but not > > > button.png. On the other hand, there is a new-snippet.png in the > > > images/admin directory, but I still get a 404 for that file as well. > > > These image files are not ones that I have created, so I'm not sure > > > what's going on. I do have some extensions installed (Chronicle, blog, > > > mailer, paperclipped, settings) and I don't know if these are a > > > factor. I have combed through all the css files I can find, and > > > nothing seems to point to these missing files. > > > > Suggestions? > > > > Thanks in advance. > > > > Ross Laird > >
[Radiant] Re: image 404s
I started to wonder if this was related to the chronicle extension after I grep'ed for various of the 404-causing files and found references to these files: ./vendor/extensions/chronicle/app/views/admin/snippets/index.html.haml ./vendor/extensions/chronicle/public/javascripts/admin/chronicle.js ./vendor/extensions/chronicle/public/javascripts/admin/HelpBalloon.js ./vendor/extensions/chronicle/app/helpers/admin/timeline_helper.rb Then I saw Will's response. So, although I do like the chronicle extension, is the solution to remove it (at least for now, until it is updated)? And, if so, I can't find documentation anywhere on how to do that. (I have removed extensions from redmine by just deleting their directories, but this is not best practice I'm sure.) On Dec 2, 12:13 am, William Ross wrote: > On 2 Dec 2010, at 00:25, rosslaird wrote: > > > I have just started using Radiant (which is just great, by the way), > > so apologies in advance for what may be a very simple question: the > > server log shows various 404s to image files: button.png and new- > > snippet.png are two examples. My setup is on locahost, for testing, so > > the 404 refers to (for example) this > > url:http://localhost/images/admin/button.png. > > Both of those are files used by older versions of the admin interface. The > most likely explanation is that one of your extensions is not up to date: > being contemporary with an older version of radiant it is assuming the > presence of files that don't exist any more. > > Radiant's helper methods mean that the author probably didn't need to spell > out the image path, but something like this (in your radiant instance > directory) should show you where it's coming from: > > grep -r 'new-snippet' . > > I don't get any matches from a normal radiant site except in old log files. > > best, > > will > > > There are quite a few image files in /images/admin, but not > > button.png. On the other hand, there is a new-snippet.png in the > > images/admin directory, but I still get a 404 for that file as well. > > These image files are not ones that I have created, so I'm not sure > > what's going on. I do have some extensions installed (Chronicle, blog, > > mailer, paperclipped, settings) and I don't know if these are a > > factor. I have combed through all the css files I can find, and > > nothing seems to point to these missing files. > > > Suggestions? > > > Thanks in advance. > > > Ross Laird > >
[Radiant] Re: image 404s
Nope. I get 404 for them all. R. On Dec 1, 7:55 pm, Fima Leshinsky wrote: > Can you hit other assets in the /admin dir w/ curl and do u get a 200? > > On Dec 1, 2010, at 6:02 PM, rosslaird wrote: > > > Thanks for the help. > > Unless I've done something incorrectly, this: > > >> select * from page_parts where content like '%button.png%', etc. > > > returns no results (I did this in PHPMyAdmin) for any of the tables > > with a content field. > > >> For the new-snippet.png 404 - that's a tough one. I'd use curl to debug it > >> - > > > Here's what I get from "curl -svo /dev/null localhost/images/admin/new- > > snippet.png": > > > GET /images/admin/new-snippet.png HTTP/1.1 > > User-Agent: curl/7.21.0 (i686-pc-linux-gnu) libcurl/7.21.0 OpenSSL/ > > 0.9.8o zlib/1.2.3.4 libidn/1.18 > > Host: localhost > > Accept: */* > > > HTTP/1.1 404 Not Found > > Date: Thu, 02 Dec 2010 01:51:01 GMT > > Server: Apache/2.2.16 (Ubuntu) > > Vary: Accept-Encoding > > > I'm not sure where to go next with that. > > > So, overall, I am learning things (the upside) but not closer to > > resolving this (the downside). > > Thanks again for the help. > > > Cheers. > > > Ross > >
[Radiant] Re: image 404s
Thanks for the help. Unless I've done something incorrectly, this: > select * from page_parts where content like '%button.png%', etc. returns no results (I did this in PHPMyAdmin) for any of the tables with a content field. > For the new-snippet.png 404 - that's a tough one. I'd use curl to debug it - Here's what I get from "curl -svo /dev/null localhost/images/admin/new- snippet.png": GET /images/admin/new-snippet.png HTTP/1.1 User-Agent: curl/7.21.0 (i686-pc-linux-gnu) libcurl/7.21.0 OpenSSL/ 0.9.8o zlib/1.2.3.4 libidn/1.18 Host: localhost Accept: */* HTTP/1.1 404 Not Found Date: Thu, 02 Dec 2010 01:51:01 GMT Server: Apache/2.2.16 (Ubuntu) Vary: Accept-Encoding I'm not sure where to go next with that. So, overall, I am learning things (the upside) but not closer to resolving this (the downside). Thanks again for the help. Cheers. Ross
[Radiant] image 404s
I have just started using Radiant (which is just great, by the way), so apologies in advance for what may be a very simple question: the server log shows various 404s to image files: button.png and new- snippet.png are two examples. My setup is on locahost, for testing, so the 404 refers to (for example) this url: http://localhost/images/admin/button.png. There are quite a few image files in /images/admin, but not button.png. On the other hand, there is a new-snippet.png in the images/admin directory, but I still get a 404 for that file as well. These image files are not ones that I have created, so I'm not sure what's going on. I do have some extensions installed (Chronicle, blog, mailer, paperclipped, settings) and I don't know if these are a factor. I have combed through all the css files I can find, and nothing seems to point to these missing files. Suggestions? Thanks in advance. Ross Laird
[Radiant] image 404s
I have just started using Radiant (which is just great, by the way), so apologies in advance for what may be a very simple question: the server log shows various 404s to image files: button.png and new- snippet.png are two examples. My setup is on locahost, for testing, so the 404 refers to a (for example) this url: http://localhost/images/admin/button.png. There are quite a few image files in /images/admin, but not
