Re: [Radiant] Revisiting Twitter Extension Conflict?
Hi Anna, Thanks VERY much for your help with this. It took me a couple of extra days to focus back on this. Other clients were clamoring for attention. I finally have updated both and now everything is great! ~ Alexis = Alexis Masters, author http://www.alexismasters.com 510 234-0027 On Mar 15, 2010, at 11:17 PM, banane wrote: Hey Alexis Coupla things- I'd update your database mailer extension with Ehaselwanter's: git://github.com/ehaselwanter/radiant-database-mailer-extension.git You don't need to migrate, just update and restart your server. Also update w/ my twitter extension (also no migrate necessary, just update). That will resolve the config conflict in both directions. In general, you may want to edit your environment.rb to load the extensions in the order that's most important to you- leaving the most important t the end. Then if there' sa conflict, your favorite ones won't be affected. Cheers Anna On Mon, Mar 15, 2010 at 10:54 PM, Alexis Masters alexismast...@gmail.com wrote: Anna, THANKS!!! I just got home and found you had worked on this. So great of you to jump in there! I'll try this out tomorrow and let you know how it goes. One question: Do I need to uninstall and reinstall Database_Mailer, or will installing your Twitter fork work without reinstalling Database_Mailer? ~ Alexis = On Mar 15, 2010, at 12:24 PM, banane wrote: OK I forked branched a twitter-extension that also renames the config() to twitter_config. works with database_mailer. Yay! http://github.com/banane/radiant-twitter-extension On Mon, Mar 15, 2010 at 11:39 AM, banane ban...@gmail.com wrote: Also- Haselwanter, your fix on the database_mailer is great, I'm using it now. thanks for adding the admin UI thing, too, it's small but it's nice to keep the log clean. One tip Alexis: setup your environment.rb to load the extensions that are vital to your site last, so they override less important extensions. It's config.extensions = [ twitter, database_mailer, mailer] etc. one of the first lines of that file. Anna On Mon, Mar 15, 2010 at 1:03 AM, Haselwanter Edmund edm...@haselwanter.com wrote: On 15.03.2010, at 08:14, banane wrote: If it makesyou feel better Alexis, I've replicated the error. I have a feeling it's due to both extensions setting the same constant. I'm hunting it down. This is IMHO because both define a method config I did a fix on my mailer -fork and sent out a pull request http://github.com/ehaselwanter/radiant-mailer-extension/commit/22382ab1f44d4ccc900dc29bb938dcfbfb0bb0f9 And I would like to suggest to all extension developers out there to think twice on naming methods while including them to the core page! E.g. do some name-spacing in the method name to avoid conflicts. cu edi On Sun, Mar 14, 2010 at 6:36 PM, banane ban...@gmail.com wrote: I'm going to try installing both and see if I can see the conflict. Anna On Sun, Mar 14, 2010 at 4:03 PM, Alexis Masters alexismast...@gmail.com wrote: Thanks for the suggestion, Anna. And your blog instructions are VERY clear and helpful. Loved them. Sadly, though, the good old Mailer config is not valid (see Mailer.valid_config?) was back on the form pages after the twitter extension was installed, so out it goes again until I can find a fix. DARN! I really want to use this, but on a site where forms are crucial, they must take precedence. ~ Alexis = Alexis Masters, author http://www.alexismasters.com On Mar 14, 2010, at 3:24 PM, Anna Billstrom wrote: Can you check the log and tell the detailed error message? Basically is it part of the smtp config or another setting. See troubleshooting in my blog post on actionmailee (which database mAiler uses. http://www.banane.com/2009/10/27/radiant-mailer-extension-installation-basics Sent from my iPhone On Mar 14, 2010, at 1:18 PM, Alexis Masters alexismast...@gmail.com wrote: Hi All, A little over a month ago, I inquired about what might be causing the mailer extension to fail when the twitter extension is installed. John Polling answered that he had both extensions running together. Thanks, John! I assumed the conflict might be due to the fact that my site used Radiant 0.8.1 while John's was on Radiant 9.0. I just upgraded a site from 0.8.1 to 9.0 and installed the twitter extension after the mail forms were all working optimally. Once again the dreaded Mailer config is not valid (see Mailer.valid config?) appeared, and the twitter had to come out. Now I'm wondering if the mailer extension is the culprit after all, or if the database_mailer extension is causing the conflict due to the way it is configured. So this time, I ask, does anyone have the Twitter extension running alongside Database_Mailer? ~ Alexis = On Feb 9, 2010, at 11:48 PM, John Polling wrote: Hi Alexis, I've just
[Radiant] Reorder Extension testing issues
This is actually common to several extensions, so I'm fairly sure I screwed up something on my end, but it's just to obvious for me to see it. Starting from a completely fresh installation: 1) radiant radiant -d mysql 2) cd radiant 3) rake radiant:freeze:edge TAG=0.8.1 4) cd vendor/radiant At this point I edit the database.yml file at radiant/vendor/radiant/config/database.yml 5) rake db:bootstrap (Don't know if it matters but the last time I did this I chose the Roasters template) 6) rake spec:models The last line was to verify that the installation into the directory called 'radiant' seemed to go properly, and it does appear to have, since all tests passed with a deprecation warning. So now I proceed with downloading the reorder extension, unzipping it, renaming the resulting directory to reorder and dropping it in radiant/vendor/radiant/vendor/extensions (perhaps I should have chosen a less confusing project name, but I didn't expect to have this issue when I chose it). From that point: 7) rake development radiant:extensions:reorder:migrate 8) rake development radiant:extensions:reorder:update (I'm running apache2 with Passenger, and have set the default RailsEnv to development.) 9) rake spec:models and 66 of the tests that passed the first time fail this time. All of the failures are along the lines of: Mysql::Error: Unknown column 'position' in 'order clause': so it seems as if the migration that has occurred in line 7 above (verified by inspecting the db) never happens during the testing. The extension itself appears to be functioning fine in the application, as the position column is filled in correctly, and it does move the pages up and down, so it looks as if only the testing environment is failing to apply the migration for some reason. This sort of thing is obvious enough that I'm sure I'm just missing something simple, but I'm hanged if I can see it. As for variations, I've tried this with both radiant and radiant-rc, and I've frozen to edge and updated as well as freezing to 0.8.1, with no difference. Highlights from the local gem list are: cucumber (0.6.3, 0.3.104) cucumber-rails (0.3.0) passenger (2.2.11, 2.2.10, 2.2.9) radiant (0.8.1, 0.8.0) rails (2.3.5, 2.2.2, 1.2.6) rake (0.8.7, 0.8.3) rspec (1.3.0, 1.2.6) rspec-rails (1.3.2, 1.2.6) rubygems-update (1.3.6, 1.3.5) webrat (0.7.0, 0.4.4) ZenTest (4.2.1) Didn't want to post the whole list, let me know if there's another one that might be relevant. Ruby is 1.8.7 patchlevel 72, default install on SnowLeopard. (Yes, I know. I keep meaning to upgrade to 1.9.x but since this isn't a public-facing machine the urgency just isn't there, and I don't figure it's worth the hassle to upgrade to anything less than 1.9.x.) Ideas? Have Fun, Arlen -- In God we trust, all others must supply data ___ 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] Reorder Extension testing issues
You have to rake migrate the test env: rake radiant:extensions:reorder:migrate RAILS_ENV=test On Thu, Mar 18, 2010 at 3:17 PM, Arlen Walker arlen.wal...@gmail.com wrote: This is actually common to several extensions, so I'm fairly sure I screwed up something on my end, but it's just to obvious for me to see it. Starting from a completely fresh installation: 1) radiant radiant -d mysql 2) cd radiant 3) rake radiant:freeze:edge TAG=0.8.1 4) cd vendor/radiant At this point I edit the database.yml file at radiant/vendor/radiant/config/database.yml 5) rake db:bootstrap (Don't know if it matters but the last time I did this I chose the Roasters template) 6) rake spec:models The last line was to verify that the installation into the directory called 'radiant' seemed to go properly, and it does appear to have, since all tests passed with a deprecation warning. So now I proceed with downloading the reorder extension, unzipping it, renaming the resulting directory to reorder and dropping it in radiant/vendor/radiant/vendor/extensions (perhaps I should have chosen a less confusing project name, but I didn't expect to have this issue when I chose it). From that point: 7) rake development radiant:extensions:reorder:migrate 8) rake development radiant:extensions:reorder:update (I'm running apache2 with Passenger, and have set the default RailsEnv to development.) 9) rake spec:models and 66 of the tests that passed the first time fail this time. All of the failures are along the lines of: Mysql::Error: Unknown column 'position' in 'order clause': so it seems as if the migration that has occurred in line 7 above (verified by inspecting the db) never happens during the testing. The extension itself appears to be functioning fine in the application, as the position column is filled in correctly, and it does move the pages up and down, so it looks as if only the testing environment is failing to apply the migration for some reason. This sort of thing is obvious enough that I'm sure I'm just missing something simple, but I'm hanged if I can see it. As for variations, I've tried this with both radiant and radiant-rc, and I've frozen to edge and updated as well as freezing to 0.8.1, with no difference. Highlights from the local gem list are: cucumber (0.6.3, 0.3.104) cucumber-rails (0.3.0) passenger (2.2.11, 2.2.10, 2.2.9) radiant (0.8.1, 0.8.0) rails (2.3.5, 2.2.2, 1.2.6) rake (0.8.7, 0.8.3) rspec (1.3.0, 1.2.6) rspec-rails (1.3.2, 1.2.6) rubygems-update (1.3.6, 1.3.5) webrat (0.7.0, 0.4.4) ZenTest (4.2.1) Didn't want to post the whole list, let me know if there's another one that might be relevant. Ruby is 1.8.7 patchlevel 72, default install on SnowLeopard. (Yes, I know. I keep meaning to upgrade to 1.9.x but since this isn't a public-facing machine the urgency just isn't there, and I don't figure it's worth the hassle to upgrade to anything less than 1.9.x.) Ideas? Have Fun, Arlen -- In God we trust, all others must supply data ___ 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 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] Reorder Extension testing issues
Or it might work with just a migration all together: rake db:migrate RAILS_ENV=test On Thu, Mar 18, 2010 at 3:23 PM, banane ban...@gmail.com wrote: You have to rake migrate the test env: rake radiant:extensions:reorder:migrate RAILS_ENV=test On Thu, Mar 18, 2010 at 3:17 PM, Arlen Walker arlen.wal...@gmail.com wrote: This is actually common to several extensions, so I'm fairly sure I screwed up something on my end, but it's just to obvious for me to see it. Starting from a completely fresh installation: 1) radiant radiant -d mysql 2) cd radiant 3) rake radiant:freeze:edge TAG=0.8.1 4) cd vendor/radiant At this point I edit the database.yml file at radiant/vendor/radiant/config/database.yml 5) rake db:bootstrap (Don't know if it matters but the last time I did this I chose the Roasters template) 6) rake spec:models The last line was to verify that the installation into the directory called 'radiant' seemed to go properly, and it does appear to have, since all tests passed with a deprecation warning. So now I proceed with downloading the reorder extension, unzipping it, renaming the resulting directory to reorder and dropping it in radiant/vendor/radiant/vendor/extensions (perhaps I should have chosen a less confusing project name, but I didn't expect to have this issue when I chose it). From that point: 7) rake development radiant:extensions:reorder:migrate 8) rake development radiant:extensions:reorder:update (I'm running apache2 with Passenger, and have set the default RailsEnv to development.) 9) rake spec:models and 66 of the tests that passed the first time fail this time. All of the failures are along the lines of: Mysql::Error: Unknown column 'position' in 'order clause': so it seems as if the migration that has occurred in line 7 above (verified by inspecting the db) never happens during the testing. The extension itself appears to be functioning fine in the application, as the position column is filled in correctly, and it does move the pages up and down, so it looks as if only the testing environment is failing to apply the migration for some reason. This sort of thing is obvious enough that I'm sure I'm just missing something simple, but I'm hanged if I can see it. As for variations, I've tried this with both radiant and radiant-rc, and I've frozen to edge and updated as well as freezing to 0.8.1, with no difference. Highlights from the local gem list are: cucumber (0.6.3, 0.3.104) cucumber-rails (0.3.0) passenger (2.2.11, 2.2.10, 2.2.9) radiant (0.8.1, 0.8.0) rails (2.3.5, 2.2.2, 1.2.6) rake (0.8.7, 0.8.3) rspec (1.3.0, 1.2.6) rspec-rails (1.3.2, 1.2.6) rubygems-update (1.3.6, 1.3.5) webrat (0.7.0, 0.4.4) ZenTest (4.2.1) Didn't want to post the whole list, let me know if there's another one that might be relevant. Ruby is 1.8.7 patchlevel 72, default install on SnowLeopard. (Yes, I know. I keep meaning to upgrade to 1.9.x but since this isn't a public-facing machine the urgency just isn't there, and I don't figure it's worth the hassle to upgrade to anything less than 1.9.x.) Ideas? Have Fun, Arlen -- In God we trust, all others must supply data ___ 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 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] Reorder Extension testing issues
On Mar 18, 2010, at 5:23 PM, banane wrote: You have to rake migrate the test env: rake radiant:extensions:reorder:migrate RAILS_ENV=test Yet when I do that, it says: Missing these required gems: rspec-rails ~ 1.2.6 Yet gem list rspec-rails --local shows it's installed: *** LOCAL GEMS *** rspec-rails (1.3.2, 1.2.6) (The 1.3.x versions of rspec and rspec-rails came along with the cucumber 0.6.3 update I installed.) Even so, when I removed both versions of rspec-rails and reinstalled only the 1.2.6 version, the migrate happened (verified by inspecting the test db for the column, and the 'reorder-1' in the schema migrations table): $ rake radiant:extensions:reorder:migrate RAILS_ENV=test (in /Users/arlenwalker/Sites/radiant/vendor/radiant) == AddPositionToPages: migrating = -- add_column(:pages, :position, :integer) - 0.3256s -- Putting all pages in a default order... - 0.2469s == AddPositionToPages: migrated (0.5728s) However, it made no difference, as after rake spec:models the same 66 tests failed. Interestingly enough, after running the tests, the position column was again dropped, and the extension's migration not applied during testing. I can also supply the info that some other extensions that create tables for their own use do not have the tables created, but I figured if I can figure out what's wrong here, the solution will apply elsewhere. Have Fun, Arlen -- In God we trust, all others must supply data ___ 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] Reorder Extension testing issues
On Mar 18, 2010, at 5:23 PM, banane wrote: Or it might work with just a migration all together: rake db:migrate RAILS_ENV=test Actually, oddly enough, a variation of this changed the results: Instead of being at radiant/vendor/radiant when I did the migration, I dropped back to the project working directory itself (radiant, in this case) did the migration and then rake spec:models and now 20 tests failed, and none of the failures relate to position, and the position column remained in the test table. (moving back to vendor/radiant and rerunning the tests repeated the 66 failures). So doing the full migration gave different results from the extension migrate and I suspect some of them at least come from position overriding expected behavior (such as a couple that complained that using the 'order' attribute didn't change the order. Have Fun, Arlen -- In God we trust, all others must supply data ___ 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] Reorder Extension testing issues
This reminds me I should really go back to TDD (ducks). Ha, these errors you're having are familiar, but I can't remember the silver bullet- if there was any-that solved it. Part of me wants to say, the extension developers wrote their tests with one gem version, whereas radiant wrote theirs with another, hence the discrepancy you're seeing. On Thu, Mar 18, 2010 at 4:33 PM, Arlen Walker arlen.wal...@gmail.com wrote: On Mar 18, 2010, at 5:23 PM, banane wrote: Or it might work with just a migration all together: rake db:migrate RAILS_ENV=test Actually, oddly enough, a variation of this changed the results: Instead of being at radiant/vendor/radiant when I did the migration, I dropped back to the project working directory itself (radiant, in this case) did the migration and then rake spec:models and now 20 tests failed, and none of the failures relate to position, and the position column remained in the test table. (moving back to vendor/radiant and rerunning the tests repeated the 66 failures). So doing the full migration gave different results from the extension migrate and I suspect some of them at least come from position overriding expected behavior (such as a couple that complained that using the 'order' attribute didn't change the order. Have Fun, Arlen -- In God we trust, all others must supply data ___ 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 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] Any newsletter system working with 0.8.1 or 0.9 ?
Hi everybody, I'm working for a web agency, and we got really enthusiastic about Radiant. What we love is how simple is the admin and that it gives complete control to a web designer. Most of our sites are statics pages, so Radiant looks just great for that. Said that, we very often need a contact form. Mailer extension works like a charm. I'm very happy with that. More importantly we need to be a able to collect email adresses trough a one text field form and then be able to send emails to all those people. I'm trying to use the *newsletter extension* on 0.8.1 by Andrea Franz. It won't work. For example : rake RAILS_ENV=production radiant:extensions:newsletter:page:new *There are some errors: * slug already in use for child of parent* Moreover this message is displayed when I try to edit a page in the administration: `*page_edit_main_newsletter' default partial not found!*' So this extension is not working. This is not surprising as it's not maintain for new versions of Radiant. But may be there is a simple trick ? Do you guys know how to make it work, or is there any other solution ? Like something based on mailer + database_mailer ? I'm so sorry I would have to abandon this CMS if I don't find a newsletter solution. I mean it's so basic, a lot of static web site just need this dynamic feature. I thought it was something a lot of people use. I'm barely new at Ruby On Rails, I'd love to contribute in anyway. Thanks for the work done with Radiant and all the extentions ! Hope that someone will be able to help me on this one. * * -- Vincent Brouillet ___ 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] Reorder Extension testing issues
On Mar 18, 2010, at 7:55 PM, banane wrote: This reminds me I should really go back to TDD (ducks). Ha, these errors you're having are familiar, but I can't remember the silver bullet- if there was any-that solved it. Part of me wants to say, the extension developers wrote their tests with one gem version, whereas radiant wrote theirs with another, hence the discrepancy you're seeing. This has been my biggest frustration. It's very much like the Windows DLL Hell phenomenon. I'm really going to have to dig in to why a new version of RSpec (fer cryin out loud) gets in the way of a db migration!! I just get the feeling that if I tweak one little thing, the whole house is going to come down, something I thought testing was supposed to help us get away from. Anyway, enough with the venting. I'm in the process of creating some extensions (one of the reasons for doing this was to figure out how to get started at that -- I've done a little of it but it's more cargo cult stuff than real development and I wanted to take apart a working extension to see how it ticks). The real question is how to go about setting up a development environment that I can use for this. Right now my impression is that edge is better than 0.8.1, so I'm probably going to start moving in that direction, hoping to land on 0.9 when it's ready. But I keep running into dependencies on really old testing gems. ah, well. off to bed. Have Fun, Arlen -- In God we trust, all others must supply data ___ 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
