[Radiant] Re: 1st Extension - Class Call from module newext_tags.rb
Manuel Excellent!!! That worked. Thanks... I am obviously new to ruby/rails etc.. My first name is Bartee. Now on to the next step, I am sure I will have more questions. ...bartee... -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Phantom code when Radiant is deployed
Sounds like it could be a difference in RedCloth versions. Are they the same on both machines? Jeff Jon Hope wrote: I've just prepared a whole site using the Radiant CMS and I'm happy with how it looks etc but when I deploy it to my server there are little bits of code appearing that shouldn't be there! For example there are br / tags appearing in a list of images that are left floated, so they stagger downwards instead of being displayed in a line... And on one page the styled comments look great and on another the 'clearing' tags have been left out so they're mushed up into each other... yet both pages use the same snippet to render the comments and it CONTAINS the clearing tags!!! I tried emptying the cache but it's done nothing. The only thing I can think of is that these are throwbacks to earlier code, like when the images were text links with br / tags after them, that have somehow got resurrected when I deployed... I just can't figure it out though, anyone got ANY suggestions?! Thanks, Jon ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Copy_move extension and 0.6.9
On 29 Dec 2008, at 01:15, Nate Turnage wrote: Can anybody tell me how I can git clone and older version of the copy_move extension for use with Radiant 0.6.9? I am not up with all the ins and outs of git enough to figure out how to use previous revisions. I would suggest checking out an older revision of the extension into a new git branch. That way you can keep the up-to-date version (for 0.7) in its own branch, so that if you upgrade your site to 0.7 in the future, it is still there for you. Here are the steps (note that 'co' is short for 'checkout', and 'br' for 'branch'. I have these set as aliases[1]): # from the home directory of your radiant site: $ git clone git://github.com/pilu/radiant-copy-move.git vendor/ extensions/copy_move $ cd vendor/extensions/copy_move $ git log This gives you a list of all commits, with their commit messages and 'sha' values. Find the commit that you want to revert back to (i.e. the commit prior to the one that breaks in 0.6.7). e.g.: commit b7d93af32fc8fbaa97611d0697ab33f606d2eef1 Author: Andrea Franz and...@gravityblast.com Date: Tue Dec 16 18:37:56 2008 +0100 the new radiant searches for regions under app/views/admin/pages instead of the old app/views/admin/page commit 79ee39addf4adabcf28fe77a8cb9cbf2338feda8 Merge: a904fd3... 9f3dd2a... Author: Andrea Franz and...@gravityblast.com Date: Tue Dec 16 18:33:43 2008 +0100 Merge branch 'master' of git://github.com/avonderluft/radiant- copy-move into avonderluft/master If commit 'b7d93a' introduces changes that break in 0.6.7, you want to use the commit before it: '79ee39'. So check it out: $ git co 79ee39 Note: moving to 79ee39 which isn't a local branch If you want to create a new branch from this checkout, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b new_branch_name HEAD is now at 79ee39a... Merge branch 'master' of git://github.com/ avonderluft/radiant-copy-move into avonderluft/master Now when you list the branches, you should see: $ git br * (no branch) master When you checked out the old revision, you were prompted with instructions on how to turn it into a branch of its own. Something like: $ git co -b pre-0.7 Now, when you list branches: $ git br master * pre-0.7 You can switch between your branches using `git co branch-name`. e.g. $ git co master $ git br * master pre-0.7 $ git co pre-0.7 $ git br master * pre-0.7 I hope that helps. Cheers, Drew [1]: http://git.or.cz/gitwiki/Aliases ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Phantom code when Radiant is deployed
Sounds like it could be caused by a filter. Are you using Markdown or Textile for any of the snippets or page parts? Be aware that whitespace is significant to both (?) of these filters. e.g. in Markdown[1], if you end a line with 2 or more spaces, it is interpreted as a line-break (i.e. br). Drew [1]: http://www.wishingline.com/downloads/documentation/markdown_cheatsheet.pdf On 29 Dec 2008, at 16:01, Jon Hope wrote: I've just prepared a whole site using the Radiant CMS and I'm happy with how it looks etc but when I deploy it to my server there are little bits of code appearing that shouldn't be there! For example there are br / tags appearing in a list of images that are left floated, so they stagger downwards instead of being displayed in a line... And on one page the styled comments look great and on another the 'clearing' tags have been left out so they're mushed up into each other... yet both pages use the same snippet to render the comments and it CONTAINS the clearing tags!!! I tried emptying the cache but it's done nothing. The only thing I can think of is that these are throwbacks to earlier code, like when the images were text links with br / tags after them, that have somehow got resurrected when I deployed... I just can't figure it out though, anyone got ANY suggestions?! Thanks, Jon -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Phantom code when Radiant is deployed
Thanks guys, the RedCloth thing fixed it. I have two versions locally and it was using the older one. I still don't understand WHY this fixed it though, does the newer version add line breaks and remove clearing tags?! lol I was sure that it wasn't a filter thing because I checked that specifically for code pages, but then if it's adding html tags I guess anything's possible :) -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Copy_move extension and 0.6.9
Thank you so much! I looked through the Pragmatic book and could not find any of this info. ~Nate On Mon, Dec 29, 2008 at 10:05 AM, Andrew Neil andrew.jr.n...@googlemail.com wrote: On 29 Dec 2008, at 01:15, Nate Turnage wrote: Can anybody tell me how I can git clone and older version of the copy_move extension for use with Radiant 0.6.9? I am not up with all the ins and outs of git enough to figure out how to use previous revisions. I would suggest checking out an older revision of the extension into a new git branch. That way you can keep the up-to-date version (for 0.7) in its own branch, so that if you upgrade your site to 0.7 in the future, it is still there for you. Here are the steps (note that 'co' is short for 'checkout', and 'br' for 'branch'. I have these set as aliases[1]): # from the home directory of your radiant site: $ git clone git://github.com/pilu/radiant-copy-move.gitvendor/extensions/copy_move $ cd vendor/extensions/copy_move $ git log This gives you a list of all commits, with their commit messages and 'sha' values. Find the commit that you want to revert back to (i.e. the commit prior to the one that breaks in 0.6.7). e.g.: commit b7d93af32fc8fbaa97611d0697ab33f606d2eef1 Author: Andrea Franz and...@gravityblast.com Date: Tue Dec 16 18:37:56 2008 +0100 the new radiant searches for regions under app/views/admin/pages instead of the old app/views/admin/page commit 79ee39addf4adabcf28fe77a8cb9cbf2338feda8 Merge: a904fd3... 9f3dd2a... Author: Andrea Franz and...@gravityblast.com Date: Tue Dec 16 18:33:43 2008 +0100 Merge branch 'master' of git://github.com/avonderluft/radiant-copy-move into avonderluft/master If commit 'b7d93a' introduces changes that break in 0.6.7, you want to use the commit before it: '79ee39'. So check it out: $ git co 79ee39 Note: moving to 79ee39 which isn't a local branch If you want to create a new branch from this checkout, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b new_branch_name HEAD is now at 79ee39a... Merge branch 'master' of git:// github.com/avonderluft/radiant-copy-move into avonderluft/master Now when you list the branches, you should see: $ git br * (no branch) master When you checked out the old revision, you were prompted with instructions on how to turn it into a branch of its own. Something like: $ git co -b pre-0.7 Now, when you list branches: $ git br master * pre-0.7 You can switch between your branches using `git co branch-name`. e.g. $ git co master $ git br * master pre-0.7 $ git co pre-0.7 $ git br master * pre-0.7 I hope that helps. Cheers, Drew [1]: http://git.or.cz/gitwiki/Aliases ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Phantom code when Radiant is deployed
Jon Hope wrote: Thanks guys, the RedCloth thing fixed it. I have two versions locally and it was using the older one. I still don't understand WHY this fixed it though, does the newer version add line breaks and remove clearing tags?! lol Pretty much.. :) RedCloth 3.0.4 was just horribly broken, especially with respect to BR tags, so for a year or so your only alternative was to use slightly different Textile markup or back off to 3.0.3 (which probably had its own bugs). I was sure that it wasn't a filter thing because I checked that specifically for code pages, but then if it's adding html tags I guess anything's possible :) ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Asset manager in 0.7?
With the possible exception of the new UI being merged in, we are feature-frozen for 0.7. John's new asset manager will be added in 0.7.1 at earliest. Sean Nate Turnage wrote: I was searching through the archives and came across a mention of 0.7 (that I can no longer find) having it's own asset manager, ala. page_attachments/paperclipped, and was wondering if in fact it was based on either of those. I could have sworn that page_attachments was the basis for it, and that begs the questions: (1) Will the currently attached files automagically work with the new system? (2) If a site already has paperclipped set up and working, will the new asset manager interfere with its normal operation? The reason I am asking is because I am rebuilding a site based on 0.6.7 that just would not upgrade to 0.6.9 and I am taking this opportunity to try and build it with an eye toward keeping it more current, especially with 0.7 so close to completion. I have already had to trick page_attachments to migrate (using Admin::PageController.send instead of Admin::PagesController.send) because I had already been using page_attachments on the project, but if the 0.7 asset manager is based on paperclipped, now would be the best time for me to make the change. Does anybody have any more info about how assets are going to be handled in 0.7? Thanks, Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Copy_move extension and 0.6.9
Where possible, I have been tagging extensions in 'radiant' github user with 0.6.9 before making updates for 0.7. I suggest developers tag their extension repositories similarly to reduce confusion. Sean Tim Gossett wrote: On Sun, Dec 28, 2008 at 9:31 PM, Nate Turnage pixeln...@gmail.com wrote: With the most current version of the copy_move extension and v. 0.6.9 I get this error for every page in the list of pages: *`copy_move_extra_th' default partial not found! I have used this extension in the past without any problems at all, but in building (rebuilding) a project this weekend I am having this problem. I can only imagine it is because of this comment in three places from the latest commit: used the new admin_pages_url http://github.com/pilu/radiant-copy-move/commit/07015cd85bca4af44a182775e7979e965f1acc94 . Again, I imagine this is to allow for the extension to work with v. 0.7 but it seems to break compatibility with 0.6.9. Am I wrong? Actually, it was the commit before that: http://github.com/pilu/radiant-copy-move/commit/b7d93af32fc8fbaa97611d0697ab33f606d2eef1 pilu updated his extension for Radiant 0.7.0, breaking it for 0.6.9. Just rename RADIANT_ROOT/vendor/extensions/copy_move/app/views/pages to page. -- Tim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] demo admin-login problem
Am just starting w Radiant. Installed per instructions and did db:bootstrap. Am running WinXP Ruby 1.8.7, so I had the 'enumerable' error and successfully applied the patch. Also, FYI, my installed sqlite3 gem is 1.2.2. However, when I try to log in to admin, I always get the '500 Server internal error' message page. Partial details are shown below: | Rendering: 0.04700 (100%) | DB: 0.0 (0%) | 200 OK [http://127.0.0.1/admin/login] ←[4;35;1mSQL (0.00)←[0m ←[0m SELECT name FROM sqlite_master WHERE type = 'table' AND NOT name = 'sqlite_sequence' ←[0m ←[4;36;1mSQL (0.00)←[0m ←[0;1m SELECT name FROM sqlite_master WHERE type = 'table' AND NOT name = 'sqlite_sequence' ←[0m ←[4;35;1mSQL (0.00)←[0m ←[0m SELECT name FROM sqlite_master WHERE type = 'table' AND NOT name = 'sqlite_sequence' ←[0m ←[4;36;1mSQL (0.00)←[0m ←[0;1mSELECT DISTINCT class_name FROM pages WHER E class_name '' AND class_name IS NOT NULL←[0m ass_name IS NOT NULL←[0m /!\ FAILSAFE /!\ Sun Dec 28 23:01:34 -0800 2008 Status: 500 Internal Server Error wrong number of arguments (2 for 1) c:/ruby/lib/ruby/1.8/cgi/session.rb:267:in `respond_to?' [ followed by a lengthy listing which I don't know if relevant) Can't figure out what to do (am using the default login values); would appreciate some assistance. [ could this be related to ticket #503 issue? If so, I'd be glad to help test this! ] Thanks! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Multi site wiki entry
Hi, I've just written up a piece for the wiki on the multi-site extension. Here it is: http://wiki.radiantcms.org/Multi-site_Extension The Summer reboot[1] suggested the title Multi-site Extension (why and how). I've gone into some depth on the 'how', but only dashed out a paragraph on the 'why'. If anyone would like to contribute thoughts on this, please feel free. I've also covered how to access multiple sites through a single app in development mode. I've gone into detail on how to make it work with Mongrel. I'm not so familiar with Passenger, but I've left a placeholder in the article. If anyone would like to flesh it out, it would be appreciated. Cheers, Drew [1]: http://wiki.radiantcms.org/Summer_Reboot ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
