Re: [Radiant] Quick way to randomize links?
Hi Prism. I'm not a radiant expert, but I think I might be able to help. r:children:each can be used to gather information about each of the child pages of a given parent page. The results are not necessarily random -- the order of the child pages can be specified in attributes of the r:children:each tag. However, you could generate a list of links like this: r:find url=parent_page ul r:children:each lir:link other_attributes... //li /r:children:each /ul /r:find The r:random tag, on the other hand, randomly selects 1 item from a collection of items specified by r:option tags. Here's a simple example of how I used it to have a random banner image displayed on a Christmas event page: r:random r:optionpr:assets:image title=christmas-1 size=original //p/r:option r:optionpr:assets:image title=christmas-2 size=original //p/r:option r:optionpr:assets:image title=christmas-3 size=original //p/r:option r:optionpr:assets:image title=christmas-4 size=original //p/r:option /r:random When someone visits the page, they will see one of the christmas-x images. The next time, it might be a different one. Hope this helps. -- marshal On Tue, Dec 11, 2012 at 11:32 PM, prism ctang.1...@gmail.com wrote: Hi, I want to generate a list of links pointing to articles that are randomly generated from r:children:each. I looked at the link-roll extension. I don't think that's the right extension. If there's no extension for this, I'm assuming I would use the r: random tag? I don't know goes in between r:option/r:option. Thanks if anyone can clarify how I'm suppose to be utilizing these two tags to generate the random URLs.
Re: [Radiant] Radiant Mailer Extension - Clarification on what needs to go into the SMTP settings
Hi Prism.
Here's the configuration I use on my Radiant site. I use Google for
sending/receiving email from the site, the Gmail account is gmail_user
and the password for signing into that account to read email is
gmail_pass.
ActionMailer::Base.delivery_method = :smtp
ActionMailer::Base.raise_delivery_errors = true
ActionMailer::Base.smtp_settings = {
:enable_starttls_auto = true,
:address = smtp.gmail.com,
:port = 587,
:domain = smtp.gmail.com,
:authentication = :plain,
:user_name= gmail_u...@gmail.com,
:password = gmail_pass
}
So, :address, :port, and :domain all refer to your website's smtp server.
:username and :password refer to the email user account you wish to use for
sending/receiving messages.
Hope this helps.
--
marshal
On Sun, Dec 23, 2012 at 1:39 AM, prism ctang.1...@gmail.com wrote:
Sorry this is really daft but I am confused as to what goes into the
bolded fields:
* :address = mail.domain.com,
:domain = domain.com,*
:port = 25,
* :user_name = xx,
:password = xx,*
:authentication = :plain
I've tried various things for the address (mail.domain.com VS.
smtp.domain.com), user_name, and pass and nothing happens when I hit send
on the actual form. Would the username and password be what I use to log
into my webhosting account?
Also for the config, I took off the # for the config.frameworks -= []. Is
that correct? or should the line read #config.frameworks -= []?
For this example from another thread:
ActionMailer::Base.smtp_settings = {
:address = mail.x.com,
:domain = allanmacgregor.com,
:port = 25,
:user_name = x,
:password = x,
:authentication = :plain
}
Why is the mail.x.com blocked out? Wouldn't it be
mail.allanmacgregor.com?
Thank you for anyone to can provide some assistance. I'm sorry if this
seems ridiculously simple to set up but I honestly don't understand where I
am going wrong because nothing is happening when I click send.
Re: [Radiant] Mailer extension
Hi Benny. Turns out the problem was me :( I was evaluating another mailer extension (forms/forms_mailer) and although I had run the migrations to revert the database, I neglected to remove the code from ../vendor/extensions. Duh! Apologies for using this mailing list for something so trivial. -- marshal On Tue, Oct 23, 2012 at 4:23 PM, Benny Degezelle be...@gorilla-webdesign.be wrote: Hi Marshal, You're welcome! Be sure to let us know what caused the issue when you find out. Cheers, Benny
Re: [Radiant] Mailer extension
Mandeep and Jim, thanks for responding. Jim, I don't see anything in the radiant log or the webserver (nginx, in this case) logs. The error message only appears in the browser window when I visit the mailer form page. Is there some way to get more verbose logging from radiant? Mandeep, I think the link you sent would be an excellent reference for someone programming/developing an actionmailer application, but all I'm trying to do is use one that someone else has written. I'm not a Ruby programmer, just someone hoping to use the radiant-mailer-extension on a radiant site. -- marshal
Re: [Radiant] Mailer extension
Thanks again, Benny. environment.rb has config.frameworks -= [ ] so that's not it. I'll keep looking for the conflicting Mail class and also try running in development mode. Thanks for all your help. -- marshal
Re: [Radiant] Scheduler extension
Thanks, guys. John, I will check out the 2 github links. Jim, I need the expiry feature of the scheduler extension. Never had a need to schedule a publish-on date. -- marshal
Re: [Radiant] Re: Scheduler extension
Thanks for the pointers, John. I forked the repo, committed/pushed my changes, and initiated a pull request. I get the feeling though that Sean Cribbs isn't watching the original repo anymore -- I didn't see any notifications for the pull request. What's next? Assuming my changes are incorporated into the original repo, would someone (Sean or some other Radiant guru) build the gem and publish it on RubyGems? Hope this helps... -- marshal On Thu, Mar 29, 2012 at 9:36 AM, john johnm...@gmail.com wrote: check out http://help.github.com/fork-a-repo/ and http://help.github.com/send-pull-requests/
Re: [Radiant] Re: [ANN] Radiant CMS 1.0
Congrats to everyone involved in the development and release of Radiant 1.0.0. It's looking very polished. Appreciate all the hard work that went into this and can hardly wait to migrate and start taking advantage of all the new features! John, your script worked like a charm on my Ubuntu 11.10 system. I think this is going to be a HUGE benefit for newcomers and veterans alike. Thank You! -- marshal On Wed, Feb 29, 2012 at 8:24 PM, john johnm...@gmail.com wrote: http://git.io/radiant-simple-install has been updated to use 1.0.0 now.
Re: [Radiant] Upgrading from 0.9.1 to 1.0.0-rc4
John and Will -- thanks, getting a bit closer to getting the assets working. I had to manually run the radiant:extensions:clipped:initialize task to create the config/initializers/clipped_config.rb file. It wasn't created automatically by the upgrade. The portion that relates to filesystem assets looks like: # The default settings # config[paperclip.url] = /system/:attachment/:id/:style/:basename:no_original_style.:extension # config[paperclip.path] = :rails_root/public/system/:attachment/:id/:style/:basename:no_original_style.:extension # config[paperclip.storage] = filesystem # config[paperclip.skip_filetype_validation] = true # config[assets.max_asset_size] = 5 # megabytes # config[assets.display_size] = normal # config[assets.insertion_size] = normal # config[assets.create_image_thumbnails?] = true # config[assets.create_video_thumbnails?] = true # config[assets.create_pdf_thumbnails?] = true # Check http://www.imagemagick.org/script/command-line-processing.php#geometry # for more details on ImageMagick settings for thumbnail generation # config[assets.thumbnails.image] = normal:size=640x640|small:size=320x320 # config[assets.thumbnails.video] = normal:size=640x640,format=jpg|small:size=320x320,format=jpg # config[assets.thumbnails.pdf] = normal:size=640x640,format=jpg|small:size=320x320,format=jpg My assets are in radiant root/public/assets and the one that I'm focussing on is radiant_root/public/assets/14/Banner_1.jpg. I've tried pretty much every combination I can think of with paperclip.url and paperclip.path and the closest I've come is this: config[paperclip.url] = /public/assets/:id/:basename:no_original_style.:extension config[paperclip.path] = :rails_root/public/assets/:id/:basename:no_original_style.:extension which produces this: 404 [http://localhost/public/assets/14/Banner_1.jpg] Because I'm running script/server and using port 3000, I think the url should be http://localhost:3000/public/assets/14/Banner_1.jpg but shouldn't the extension take care of that somehow? Thanks again for the help. Looks like some small tweak and we're done. -- marshal
[Radiant] Upgrading from 0.9.1 to 1.0.0-rc4
I'm having trouble with an upgrade to rc4 and wondering if anyone else has run into similar problems. Starting with a cloned copy of 0.9.1 instance, I've followed the guide from Jim Gay, https://gist.github.com/1540782, and can successfully start up an rc4 version of the site. But none of the former paperclipped assets are accessible and same thing for migrated sns styleshhets and javascripts. There are no error messages during the process, only a few warnings about deprecated items. The only thing that is obviously amiss, is although I have r:stylesheet slug=screen as=link / in the head of the raw document, when I look at the source of the generated page I see link rel=stylesheet href=screenhttp://octopusgardenyoga.com/css/screen type=text/css / instead of the expected link rel=stylesheet href=/css/screenhttp://octopusgardenyoga.com/css/screen type=text/css / and 404 File not found errors in the server log. If there's anyone willing to help debug this, please let me know what information you need about my setup. Thanks in advance. PS, Fresh install of rc4 (and coffe roasters, for example) looks great! Can hardly wait for the 1.0.0 release. Kudos to everyone involved! -- marshal
Re: [Radiant] Upgrading from 0.9.1 to 1.0.0-rc4
Hi Jim and thanks for the quick reply. I did run the rake radiant:extensions:sheets:import:sns (it's in the gist). I also looked at the resulting sqlite database and can see the StyleSheetPage in the 'pages' table and the corresponding content in the 'page-parts' table. Running ruby 1.8.7 (2011-06-30 patchlevel 352) [i686-linux]. Also tried 1.9.3 (via RVM) with the same results. By the way, in case you don't already know, ruby 1.9.2 breaks the script/server code (see: http://stackoverflow.com/questions/3865515/strange-inability-to-require-config-boot-after-upgrading-to-ruby-1-9-2 ). Hope this helps. -- marshal
Re: [Radiant] Upgrading from 0.9.1 to 1.0.0-rc4
Thanks so much! -- marshal On Thu, Jan 12, 2012 at 10:54 PM, Jim Gay j...@saturnflyer.com wrote: Ok. so this must be my method/local variable problem. I'll try to recreate this and fix it tomorrow with a new sheets gem. It should only require that you bundle update
Re: [Radiant] Re: migrating radiant installation from one server to another
You might want to take a look at taps for your database migration: http://adam.heroku.com/past/2009/2/11/taps_for_easy_database_transfers/ I use it to transfer the mysql database from my production server to an sqlite database on my development laptop. Works very reliably. -- marshal On Mon, Aug 29, 2011 at 4:01 PM, Bob Sleys bsl...@gmail.com wrote: I'd just export the DB from the old server and import it into the new server. Then copy the radiant install dir over to the new server. You might need to make a few tweaks to some of the settings but it really shouldn't be any more difficult that setting up radiant the first time on the old server. IE setup radiant, using the existing code base to keep things simple, and export/import the database.
Re: [Radiant] Third-party hosting for Radiant 0.9.1
If you, or someone you know, has modest Linux system admin skills, Slicehost (http://www.slicehost.com/) gives you complete freedom to install whatever you need, is fast and reliable, and very affordable. On Thu, Jul 14, 2011 at 11:58 AM, JT webmas...@webproductionsinc.comwrote: Hello all, Can anyone offer suggestions for third party hosts that would support Radiant? I saw mention of Dreamhost in an unrelated post, and have also looked into Network Solutions (client is interested in hosting their site with their domain name registrar). Dumb question: In both hosts' list of installed gems, I don't see Radiant mentioned. Presumably I should install it myself? Also, what about ImageMagick for the paperclipped extension? List of installed gems on Dreamhost: http://rails.dreamhosters.com/ List of installed gems on Network Solutions: http://www.networksolutions.com/support/what-ruby-gems-are-available-for-use/ Thanks for your feedback, JT -- marshal
Re: [Radiant] Radiant 1.0 Release Candidate 1
Same thing happening to me. Ruby 1.8.7 (2010-08-16 patchlevel 302), so not a 1.9.2 problem. On Thu, May 26, 2011 at 7:00 PM, Wes Gamble we...@att.net wrote: Are we supposed to be able to install a Radiant app. with Radiant as a gem with 1.0.0.rc1? Here's what happens when I try: $ radiant -d sqlite3 konditioning NOTE: SourceIndex.new(hash) is deprecated; From /Users/weyus/.rvm/gems/ruby-1.9.2-p180/gems/radiant-1.0.0.rc1/vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100:in `new'. create create CHANGELOG create CONTRIBUTORS create INSTALL create LICENSE create README create config create config/environments create config/environments/cucumber.rb create config/environments/development.rb create config/environments/production.rb create config/environments/test.rb create config/initializers create db create log No such file or directory - /Users/weyus/.rvm/gems/ruby-1.9.2-p180/gems/radiant-1.0.0.rc1/bin/../lib/generators/instance/templates/../../../../log I think this is a problem with the RC1 generator, not 1.9.2. Happy to be corrected, however. Wes -- marshal
Re: [Radiant] Re: Forms and Forms-Mailer
Apologies, I should have been clearer. I'm using: -- *radiant-forms-extension* https://github.com/squaretalent/radiant-forms-extension -- *radiant-forms_mailer-extension* http://github.com/squaretalent/radiant-forms_mail-extension I haven't checked for updates on these extensions since installing them, and when I checked today, radiant-forms-extension has moved to http://github.com/dirkkelly/radiant-forms-extension and radiant-forms_mailer-extension has apparently been merged into it. Does anyone know if Dirk Kelley's (latest) radiant-forms-extension supports sending email attachments? Thanks for your help. On Sun, May 15, 2011 at 9:19 AM, Shanison lxsh...@gmail.com wrote: If you are referring to this extension https://github.com/Aissac/radiant-mailer-extension. I don't think it support sending email attachments. You have to extend it. -- marshal
[Radiant] Forms Extension
Greetings. I'm using the forms and forms-mailer extensions to create a form to be emailed. Most of it is working well except for attachments. I've used the r:file tag to get a file chooser button/dialog and that appears to work. In the content page of the form, what gets emailed, I've used r:read to get the uploaded file, but when the form is submitted, a 500 application error is given for exceptions thrown outside of an action. What am I missing? Thanks for any suggestions. -- marshal
Re: [Radiant] Forms Extension
Thanks Jim. Here's the pastie: http://pastie.org/1279841 Is the Yajl::ParseError caused by the FormsController trying to parse the file that was uploaded? If so, what to do about it? I'm totally lost here, so any suggestions for troubleshooting would be much appreciated. -- marshal
Re: [Radiant] how to view (render) a draft page ?
You'll want to install the page_preview extension: http://ext.radiantcms.org/extensions/58-page-preview On Sun, Aug 15, 2010 at 8:33 AM, nruth nick.rutherf...@gmail.com wrote: Is there a way for admins to view a page before publishing it? I can't find mention of this in the docs 'view site' just loads the live page's root. Radiant 0.9.1 Cheers, Nick -- marshal
[Radiant] Re: feed_reader extension
Figured this out, mostly. The Wordpress RSS feed doesn't have an author tag so a nil value is returned. Not important, I'll leave it out. Changed the format attribute to %A, %B %d, G and got a nicely formatted date string. Working fine for anyone else interested in using it. On Sat, Aug 14, 2010 at 2:53 PM, Marshal Linfoot mlinf...@gmail.com wrote: I'm trying to add recent postings from a Wordpress blog onto a page in my Radiant site using the feed_reader extension. Everything installs without error (Paul Dix's feedzirra gem and dependencies + the feed_reader extension), and it displays some of the feed results correctly, but r:author / is empty and r:date / produces undefined method `strftime' for nil:NilClass. I don't see any errors in the production log. Testing this on Radiant 0.9.1 with the following code in the page: r:feed:entries:each url=http://blog.octopusgardenyoga.com/rss; limit=5 div class=feed-entry h2r:link //h2 div class=metaby r:author / on r:date format=%Y-%m-%d//div div class=summaryr:summary //div /div /r:feed:entries:each The docs for feed_reader say it has been tested on 0.7.1 (old!!) but there aren't any special db/assets requirements, other than the feedzirra gem (and dependencies), so I figure it should work on 0.9.1 as well. Any thoughts/ideas for getting this to work? -- marshal -- marshal
Re: [Radiant] New feature: manage CSS and Javascripts from the Admin UI
Great news Jim. Gonna try it out as soon as I get home. Thanks! On 8/11/10, Jim Gay j...@saturnflyer.com wrote: I've made some updates and I'm not able to recreate this problem. I've created a new instance from edge Used the #4 template (Styled Blog) Copied the Styles.css page content into a new stylesheet and saved it. Changed the layout from using a direct link to the /styles.css page to r:stylesheet slug=styles.css as=link / (Using the same slug as the existing page) Reload the public view and see everything as it should be. On Tue, Aug 10, 2010 at 4:58 PM, kbingman kbing...@gmail.com wrote: Marshal, there are a couple of pages set up in the database for CSS, one for CSS in general, then child pages for each actual CSS. When I took a look, the status was set to 90, which is pending. Hopefully Jim will have this sorted out soon (or already). Keith On Aug 5, 6:18 pm, Marshal Linfoot mlinf...@gmail.com wrote: Keith, how did you determine that the stylesheet was in draft status? I browsed my sqlite database looking for that and couldn't find the styesheet page anywhere. On Thu, Aug 5, 2010 at 5:23 AM, kbingman kbing...@gmail.com wrote: Jim, looks like there is a little bug here... the stylesheet is set to draft after it is created. At least is was for me, which is probably was Marshal is not getting it in his layout. Keith -- marshal -- Jim Gay Saturn Flyer LLC http://www.saturnflyer.com 571-403-0338 -- Sent from my mobile device marshal
Re: [Radiant] Drag order extension with Radiant 0.9.1
Anna, thank you. I'll be happy to test your changes. On Mon, Aug 9, 2010 at 10:12 PM, banane ban...@gmail.com wrote: I'll try to rework mine. I got a pull request a few weeks ago from someone who'd merged branches. anna -- marshal
Re: [Radiant] Re: New feature: manage CSS and Javascripts from the Admin UI
Keith, how did you determine that the stylesheet was in draft status? I browsed my sqlite database looking for that and couldn't find the styesheet page anywhere. On Thu, Aug 5, 2010 at 5:23 AM, kbingman kbing...@gmail.com wrote: Jim, looks like there is a little bug here... the stylesheet is set to draft after it is created. At least is was for me, which is probably was Marshal is not getting it in his layout. Keith -- marshal
Re: [Radiant] New feature: manage CSS and Javascripts from the Admin UI
Jim, I've used the sns extensions for some time now and, from a non-developer perspective, am happy to see the functionality moved into core. I'm sure developers will find it easier to work with, too. I gave it a try on a test server that had sns, sns_page_hooks, sns_minifier, sns_sass_filter already installed. Here are the steps I took: 1. rake radiant:freeze:edge 2. rake radiant:update 3. rake production db:migrate 4. removed all the sns* extensions with script/extensions uninstall sns (for each extension) 5. rake radiant:update 6. rake production db:migrate:extensions 7. started the server and uploaded my css to the new stylesheets page 8. changed the stylesheet tag to read r:stylesheet slug=main as=link media=screen / in the layout 9. and for good measure, restarted the server When I open the home page of the test site, the css is not applied. Viewing the page source I see: link rel=stylesheet type=text/css href=/css/main?1280848729 media=screen / Typing either localhost:3000/css/main?1280848729 or localhost:3000/css/main in the browser URL field produces the same Page Not Found result. Have I missed some important step? Any ideas? I haven't tried it on a clean, new radiant instance without any other extensions yet. Lastly, will you be adding the ability to minify the css/javascript like sns_minifier? -- marshal
Re: [Radiant] New feature: manage CSS and Javascripts from the Admin UI
Thanks very much for testing this out, Marshal. Happy to help in any small way. The part you missed is that there was no conversion of content from the SNS records in the database to StylesheetPages and JavascriptPages. I wasn't expecting the old sns content to be moved. Instead, I let the uninstall remove it (at least I thought that's what would happen) and then I created a new Sheets/stylesheet page and copied the css into it from a local text file. SNS stores content in a text_asset table, but none of the steps you did moved that content. Did the uninstall remove it? I haven't yet created the necessary migrations, but judging from your experience here it looks like you'd assume that a migration would do the trick. So I'll probably just add migrations to move the content from within the Sheets extension. This would be great! And if you are moving from SNS, I've also allowed for the name attribute to work. So your r:stylesheet name=main / will still work, no need to update to be a slug attribute instead. I had the name attribute at first, but when the css wasn't applied I changed it to slug thinking that might be the problem. -- Jim Gay Saturn Flyer LLC http://www.saturnflyer.com 571-403-0338 PS. Minify? -- marshal
Re: [Radiant] New feature: manage CSS and Javascripts from the Admin UI
Jim, I just now tried this on a fresh Radiant instance. I installed the Styled Blog so I would have some content and css to work with. Cut and pasted the css from Styles/css into Design/Stylesheets/main and then deleted the Styles page (original css gone, copy of the original css in /css/main). Updated the layout to use Sheets, ie r:stylesheet name=main as=link /. The radius tag renders as expected link rel=stylesheet type=text/css href=/css/main?1280863253 /, but the page is not styled. Can't see that I've missed anything. Could it be a caching issue, that something is pointing to the old, non-existent css? -- marshal
Re: [Radiant] New Feature: Add Child Menu
John and Josh. It just keeps getting better... I tried out the latest edge version and really like the changes. The drop-down selection of page types is very nice, and familiar to those of us using Josh's excellent PageFactory extension. I was curious to see if PageFactory would still work with these changes and, as I guessed, it did not. It installs fine but the custom page type I defined is not included in the drop-down selection of page types. So, understanding that this is early development, I was wondering if you are planning to integrate Josh's PageFactory and PageParts extensions into the Radiant core? If so, this would be awesome. On Mon, Jul 19, 2010 at 12:11 PM, John W. Long m...@johnwlong.com wrote: Josh French and I have just committed a series of changes to Radiant that will change the way page children are created (you must be running on edge to see the changes). Instead of creating a child page immediately, the “Add Child” button will now present you with a list of page types. The goal of this change is to move the selection of page type to page creation. This change is essential for a number of other ideas that we are considering. Read the full story here: http://wiseheartdesign.com/articles/2010/07/19/radiant-cms-add-child-menu/ -- John Long http://wiseheartdesign.com http://recursivecreative.com -- marshal
Re: [Radiant] New Feature: Add Child Menu
Hi Josh. I hope I didn't imply that I was keen to run edge and PageFactory. That's not the case. My production site is running the 0.9 gem plus your extensions (and others) and all is good. When I saw John's announcement about the add-child menu, I installed a radiant edge instance on my laptop to see what it looked like. Nice, very much like PageFactory and hence my curiosity to see if the two played well together. Then the question: wondering if you and John will merge/integrate PageFactory and the add-child menu feature, essentially eliminating the need for a PageFactory extension. I agree with you that PageParts should probably remain an extension. From an end-user perspective, that is, one who uses Radiant and various extensions to manage a web site, extensions have always been somewhat problematic. They don't always install cleanly, the install process varies, some don't work together (eg. install extension A and extension B breaks), and they often lag behind upgrades to new Radiant releases. This is not a criticism; I think I understand some of the difficulties and I appreciate all the hard work that goes into a project of this scope and complexity. However, extensions remain the most difficult part of getting a Radiant site up and running, as most of the discussions on this list will attest. So from where I sit, PageFactory functionality in core would be one less extension to deal with. I know there have been a number of ideas discussed about bundling extensions so one could do things like radiant -basic target dir or radiant extension-bundle target dir to install radiant with a predefined or custom set of extensions. Sounds great, but I would be happy to have a repository of approved/tested (sorry, can't think of a better label) extensions that are all know to work together, can be installed with the same command which would automatically install any/all dependencies and adjust config/environments.rb, if necessary, and would clearly show which versions of Radiant they are known to work with. Hope this is helpful and constructive. -- marshal
Re: [Radiant] [ANN] SNS Page Hook Extension
Jim, this is a really useful addition to the sns extension, something I've
wished was there from the start. Which leads me to ask, why another
extension instead of working it into the main sns extension?
Thanks very much for this. Going to start using it right away.
On Wed, Jun 30, 2010 at 12:48 PM, Jim Gay j...@saturnflyer.com wrote:
I recently solved a problem when using the SNS extension.
With SNS, you can edit stylesheets and javascripts, but you can't use
typical radius tags that you have available in pages, snippets, and layouts.
Now with the SNS Page Hook extension, you can
http://ext.radiantcms.org/extensions/232-sns-page-hook
A typical use case is doing something like this in your stylesheets:
#my_item {
background-image: url('r:assets:url title=my_image /');
}
If you only have SNS, you can't do that. But with SNS Page Hook, you can.
I wrote more details about it here
http://www.saturnflyer.com/blog/jim/2010/06/29/ruby-metaprogramming-is-awesome
I mentioned this in another thread, but thought some subscribers might not
have seen it and the feature addition for SNS is helpful. I'd love to have
your feedback.
Jim Gay
Saturn Flyer LLC
www.saturnflyer.com
571 - 403 - 0338
--
marshal
Re: [Radiant] which gallery extension to use on 0.9.1?
On Tue, Jun 29, 2010 at 5:50 PM, decafranky fra...@decawebservices.bewrote: tested a few gallery extensions but none is working which one do you prefere to install on 0.9.1 ? This one is working fine on my 0.9 site: http://wiki.github.com/radiant/radiant/gallery-extension -- marshal
Re: [Radiant] which gallery extension to use on 0.9.1?
H... I went through the steps again to make sure and all is well. Here's what I did: 1. create a new radiant instance in folder test radiant test -d sqlite3 cd test rake production db:bootstrap [and chose 4. styled blog] 2. install gallery extension git clone git://github.com/technoweenie/attachment_fu.gitvendor/plugins/attachment_fu [prerequisite] git clone git://github.com/hairballopolis/radiant-gallery.gitvendor/extensions/gallery rake RAILS_ENV=production radiant:extensions:gallery:install No errors, ready to use. Lots more info here: http://github.com/hairballopolis/radiant-gallery On Tue, Jun 29, 2010 at 6:07 PM, Franky De Schampheleer fra...@decawebservices.be wrote: i have error with that one: rake production radiant:extensions:gallery:install (in /home/admin/radiant) rake aborted! Object is not missing constant GalleryItem! -- marshal
Re: [Radiant] which gallery extension to use on 0.9.1?
After all the help I've received from the Radiant community, I'm glad I could help someone else. Enjoy! On Tue, Jun 29, 2010 at 6:35 PM, Franky De Schampheleer fra...@decawebservices.be wrote: great, that works fine ! i used another radiant-gallery (same extension name, other author) many thanks ! franky -- marshal
Re: [Radiant] Super Import/Export
Thanks John. Taps looks great! I hacked a workaround by changing object:DatePagePart to object:DatePart in all the yml files and they loaded without error -- database is fine. Will definitely check out taps gem -- much simpler. if you can't get that working check out the taps gem. it can serialize data into and out of any database supported by sequel. -- marshal
