Re: [Radiant] page_attachments
On 7/17/07, Sean Cribbs <[EMAIL PROTECTED]> wrote: > Michael, > > 1) page_attachments assumes you want a particular file accessible from a > particular page or its children. It also assumes you know the name of > the file and makes no assumptions about the format of the file, be it > text, image or some other binary format. There is no way to iterate > through the attachments of any given page. Mmm, I disagree... What If want to attach a few files and show them inside a table? Just the name and the size, which will allow me later replace those files with updated ones without thinking on the name of the file :-) > 2) This again falls out of the scope of page_attachments. I wouldn't > want random visitors uploading files into my page, so I didn't add that > functionality. > But I agree on this... file uploads from front-end is way beyond the scope of page_attachments.. also, i see a lot of attempts to convert those sites to a pr0n web storage :P -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Spam
On 4/13/07, Gabriel Lamounier <[EMAIL PROTECTED]> wrote: > Hi there, > > Is there any way of stopping the recent spams? > It came from ruby-forum, maybe maintainer of ruby-forum could solve that? (only allow logged ppl to post). > > Be Radiant! :-D -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: [EMAIL PROTECTED] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Installing 0.6.0rc1
On 3/7/07, Sharon Clift <[EMAIL PROTECTED]> wrote: > I am new to Ruby/Rails & RubyGem and am trying to install a copy of > radiant 0.6.0rc1 for testing. > > I have downloaded the gem from > http://johnwlong.com/downloads/radiant-0.6.0rc1.gem to > c:/ruby/lib/ruby/gems/ however when I use the command > > Gem install radiant-0.6.0rc1 > If you manually downloaded the gem, you must supply the extension (.gem) in the command line. gem install radiant-0.6.0rc1.gem I'll suggest read the instructions from Radiant weblog: http://radiantcms.org/blog/2007/02/04/radiant-0-6-release-candidate/ Regards, -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] radiant-0.6.0rc1.gem
On 3/4/07, Marshal Linfoot <[EMAIL PROTECTED]> wrote: > I don't know if this is a bug or just my misunderstanding of how > things should work, but I thought it might be useful to share. > > I installed the radiant-0.6.0rc1.gem on my Ubuntu system in the usual > way. Everything seems to go into /usr/lib/ruby/gems/1.8/gems/. Here's > a list of what's currently installed: > > BlueCloth-1.0.0/activerecord-1.15.2/radiant-0.5.2/ > RedCloth-3.0.4/ activesupport-1.3.1/radiant-0.6.0/ > actionmailer-1.2.5/ activesupport-1.4.1/radius-0.5.1/ > actionmailer-1.3.2/ cgi_multipart_eof_fix-2.1/rails-1.1.6/ > actionpack-1.12.5/ daemons-1.0.4/ rails-1.2.2/ > actionpack-1.13.2/ fastthread-0.6.4.1/ rake-0.7.1/ > actionwebservice-1.1.6/ gem_plugin-0.2.2/ > rubygems-update-0.9.2/ > actionwebservice-1.2.2/ mongrel-1.0.1/sources-0.0.1/ > activerecord-1.14.4/ mysql-2.7/ > > The Radiant binary went into /usr/bin: > > [EMAIL PROTECTED]> which radiant > radiant is /usr/bin/radiant > radiant is /usr/X11R6/bin/radiant > > [EMAIL PROTECTED]> radiant --version > Radiant 0.6.0 > > Looks okay, so next I ran "radiant web/radiantsite" to setup my > working directories and followed the rest of the installation > instructions, ending up with a functioning radiant site. > Yeah, that s the idea with "instance mode", you could start running with a stock Radiant version using the gem. > Days later, when I tried to run "ruby script/generate extensions > myextension" from web/radiantsite, I discovered there wasn't any > generate script. My workaround was to copy everything from > /usr/lib/ruby/gems/1.8/gems/radiant-0.6.0 into web/radiantsite. > Thats because gem mode is aimed to "not extension developers", but users of Radiant. In that case you should use 'gem unpack' or svn checkout to keep in sync with radiant development branch. Maybe someone could add this to the Wiki? -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant 0.6 RC1
On 2/19/07, Oliver Barnes <[EMAIL PROTECTED]> wrote: > hello again, > so followed the suggestion to install my own rubygems and then install > the radiant gem. > got everything going, on webrick the admin came up fine. but when I > tried to use dreamhost's standard apache/fcgi, the application didn't > start, getting the application error "Rails application failed to > start properly" and nothing on the logs. > > i then tried running it on cgi, but got the same problem. what could > be causing this? > Check that public/dispatch.cgi or .fcgi uses the correct shebang! line for dreamhost: http://wiki.dreamhost.com/index.php/Ruby_on_Rails Also check the .htaccess rewrite rules (that point to fcgi instead of .cgi). -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Need someone to confirm a bug with sqlite3 and mental
On 2/9/07, Sean Cribbs <[EMAIL PROTECTED]> wrote: > > We will probably re-freeze the mental branch to 1.2.2 if this issue > persists. > Sean, Its confirmed, will persist... AFAIK, 1.2.x prior 1.2.2 will show this, didn't test with 1.1.x branch, but the sqlite adapter inside AR changed just in the 1.2.x branch (and will not be backported). > > Luis Lavena wrote: > On 2/8/07, Ben Johnson <[EMAIL PROTECTED]> wrote: > > > I've been trying to get this working for two days now. If I get myself > a copy of mental (both from the Gem and from SVN) and try to use > sqlite3 as my database, the rake db:bootstrap script doesn't seem to > create a user. > > It doesn't report any errors, or problems, it just says it's complete > and then won't log in. A look at the database contents reveals that > the admin user simply wasn't created. This happens when I accept the > default settings and when I specify a username and password. > > When using MySQL, the user is in the database and I can log in without > error. > > Can anyone reproduce this? > > > Ben, any version of sqlite3 over 3.3.7 will show this issue, until you > update sqlite3-ruby to 1.2.1 and re-freeze rails to 1.2.2 (the bundled > rails into Radiant shows the bug as listed in the Riding Rails blog: > > http://weblog.rubyonrails.org/2007/2/6/rails-1-2-2-sqlite3-gems-singular-resources > > This is shown on Win32 and Linux as well, after update, you could use > sqlite3 3.3.12 if you want without these issues. > > HTH, > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: > http://lists.radiantcms.org/mailman/listinfo/radiant > -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Need someone to confirm a bug with sqlite3 and mental
On 2/8/07, Ben Johnson <[EMAIL PROTECTED]> wrote: > I've been trying to get this working for two days now. If I get myself > a copy of mental (both from the Gem and from SVN) and try to use > sqlite3 as my database, the rake db:bootstrap script doesn't seem to > create a user. > > It doesn't report any errors, or problems, it just says it's complete > and then won't log in. A look at the database contents reveals that > the admin user simply wasn't created. This happens when I accept the > default settings and when I specify a username and password. > > When using MySQL, the user is in the database and I can log in without error. > > Can anyone reproduce this? > Ben, any version of sqlite3 over 3.3.7 will show this issue, until you update sqlite3-ruby to 1.2.1 and re-freeze rails to 1.2.2 (the bundled rails into Radiant shows the bug as listed in the Riding Rails blog: http://weblog.rubyonrails.org/2007/2/6/rails-1-2-2-sqlite3-gems-singular-resources This is shown on Win32 and Linux as well, after update, you could use sqlite3 3.3.12 if you want without these issues. HTH, -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant 0.6 RC1
On 2/8/07, Oliver Barnes <[EMAIL PROTECTED]> wrote: > how do I install it on a shared host that doesn't have the gem > installed? is there a way to freeze the gem to /vendor? > You could ssh to your host, set GEM_PATH to some folder in your home directory (~/.gems) and the install radiant gem. Later just unpack it into the folder you want (prior chdir into that folder). $ gem unpack radiant HTH, > 2007/2/6, John W. Long <[EMAIL PROTECTED]>: > > Adam Salter wrote: > > > Question: > > > Is there any difference in init/run time with a Rails app running > > > Rails from vendor/rails? I'd hope it was the same, but surely the > > > full gem install could cache more stuff? > > > > It's probably a little slower with RubyGems, but I haven't run any > > performance metrics on it. > > > > -- > > John Long > > http://wiseheartdesign.com > > ___ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant 0.6 RC1
On 2/4/07, John W. Long <[EMAIL PROTECTED]> wrote: > After a hard day's work the core team is pleased to announce the > immediate release of Radiant 0.6 RC1! Lots of changes have gone into > this release—too many to enumerate them all at this time of night. > Suffice it to say that the focus of this release has been the new > extension system. We'll make sure there is a complete list of new > features when this becomes the official release, but for now we want to > submit it to you for feedback and testing. > > To give it a whirl: > > 1. Download the gem: > http://johnwlong.com/downloads/radiant-0.6.0rc1.gem > > 2. Install it using: > $ gem install radiant-0.6.0rc1.gem > John, the gem must be renamed to 0.6.0 because "rc1" is not a valid versioning of rubygems. Also, reverting from custom copy/upgrade script to generator based for instance mode is the best solution (for finding identical files). > 3. Use the Radiant command to create a fresh project: > $ radiant -d sqlite3 path/to/your/project > > 4. Edit config/database.yml to taste. > > 5. Run the new bootstrap rake task: > $ cd path/to/your/project > $ rake production db:bootstrap > > 6. Configure and start it up on your favorite Web server: > $ script/server -e production > > One aspect of this new release that we would especially like feedback on > is that the new Radiant gem now contains it's own copy of Rails. Since > we have been binding each release of Radiant to a specific Rails version > we thought it prudent to go ahead and package Rails with Radiant. This > has the side benefits of simplifying dependencies and making booting easier. > I agree on this, this simplifies deployment on servers, as long you run multiple instances, if you start unpacking (gem unpack), vendor/rails code duplication will stress your disks. Great news Radiant Team! Excellent work on the Extension system! :-) -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Memory Usage
On 2/5/07, Paul Hoehne <[EMAIL PROTECTED]> wrote: > Thanks, Luis, I'll check out the links you sent. Here's the rest of > the information: > > I'm running the process using mongrel. Radiant is configured as a > windows service. I'll suggest you make sure the params used by the service (Check the Path to Executable shown on Services in Administrative Tools). Mostly because running Radiant in development mode don't activate the caching engine and make rails reload all the clases on each request, something that will rise memory leaking issues. > The proxy is a combination of the rewriter from > Helicon - ISAPI_Rewrite and IIS. It just proxies the request to the > windows service, running on a local only network connection. (So you > have to go directly to radiant). It's not a large site with pages is > the dozens - not hundreds. > Ok, good to know you're on mongrel ;-) If none of the suggestions I droped previously work, please post this case at mongrel-users mailing list: mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users > On Feb 5, 2007, at 1:44 PM, Luis Lavena wrote: > > > On 2/5/07, Paul Hoehne <[EMAIL PROTECTED]> wrote: > >> I have a radiant instance whose memory footprint grows to 200+ megs > >> of RAM. At which time I have to restart the service. Does anybody > >> have any information about how to size memory requirements for > >> Radiant? (For example, a lot of J2EE servers require 512 Megs to do > >> anything useful, but can live quite well within a Gig.) > >> > >> If it makes a difference, I'm running Radiant 0.5.2 on windows with > >> Rails 1.1.6, backed by SQL Server, running in Production mode.. It's > >> behind an IIS server proxy. Part of the memory headache seems to be > >> Windows related, as the memory tops out and "interesting" behaviors > >> begin to occur. > >> > > > > Hello Paul, > > > > How are you running your ruby process? Using Webrick and a ISAPI > > proxy? > > > > Which version of ruby are you suing? 1.8.4 or 1.8.5? > > > > In .5 exist a method to control the memory use of your process: > > > > http://www.rubyinside.com/control-your-rails-process-sizes-with- > > ruby-185-246.html > > > > Also, I'll suggest you look into Mongrel and mongrel_service > > > > http://mongrel.rubyforge.org > > > > A complex, big radiant website (400 pages) will not use more than > > 100MB of RAM per process (in case you're running a cluster). > > > > Also, current Ruby implementation show memory leaks in long-running > > process that use threads, mutexes and synchronization mechanism. > > > > I'll suggest install and use FastThread from MenTaLGuY (gem install > > fastthread) and require it early in your config/environment.rb script. > > > > Hope these tips help you, > > > > Regards, > > > > -- > > Luis Lavena > > Multimedia systems > > - > > Leaders are made, they are not born. They are made by hard effort, > > which is the price which all of us must pay to achieve any goal that > > is worthwhile. > > Vince Lombardi > > _______ > > Radiant mailing list > > Post: Radiant@lists.radiantcms.org > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Memory Usage
On 2/5/07, Paul Hoehne <[EMAIL PROTECTED]> wrote: > I have a radiant instance whose memory footprint grows to 200+ megs > of RAM. At which time I have to restart the service. Does anybody > have any information about how to size memory requirements for > Radiant? (For example, a lot of J2EE servers require 512 Megs to do > anything useful, but can live quite well within a Gig.) > > If it makes a difference, I'm running Radiant 0.5.2 on windows with > Rails 1.1.6, backed by SQL Server, running in Production mode.. It's > behind an IIS server proxy. Part of the memory headache seems to be > Windows related, as the memory tops out and "interesting" behaviors > begin to occur. > Hello Paul, How are you running your ruby process? Using Webrick and a ISAPI proxy? Which version of ruby are you suing? 1.8.4 or 1.8.5? In .5 exist a method to control the memory use of your process: http://www.rubyinside.com/control-your-rails-process-sizes-with-ruby-185-246.html Also, I'll suggest you look into Mongrel and mongrel_service http://mongrel.rubyforge.org A complex, big radiant website (400 pages) will not use more than 100MB of RAM per process (in case you're running a cluster). Also, current Ruby implementation show memory leaks in long-running process that use threads, mutexes and synchronization mechanism. I'll suggest install and use FastThread from MenTaLGuY (gem install fastthread) and require it early in your config/environment.rb script. Hope these tips help you, Regards, -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Extensions are for...?
On 2/2/07, Daniel Waite <[EMAIL PROTECTED]> wrote: > Luis Lavena wrote: > > Err... this was discussed previously on the list, also you should > > check the wiki and the weblog of Radiant site: > > > > http://radiantcms.org/blog/2007/01/23/how-to-getting-mental/ > > I read that page, and while it's true the four bullet points answer my > question, I don't _see_ those concerns being addressed when actually > trying to use extensions. I don't see how a broken tab next Layouts > helps me administer the rest of my web site. I don't see how having my > own set of models and views helps me clean up my tags any better. > The rest of your web site? Extension are a way to "extend" radiant main functionality adding things that address _your_ particular needs, all using the same UI (so end-users, ala, *your users* will use). Clean up your tags? that's another story. A Extension could add tags, global tags or anything, expose or not an administrative tab, all depends on _what your extensions need to do_ and most important, what it is for. > What I do see is a disconnect between what's being said about extensions > and the things I'm presented with when trying to utilize them. > Could you rephrase? I'm not a native english speaker so couldn't understand it clearly. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Extensions are for...?
On 2/2/07, Daniel Waite <[EMAIL PROTECTED]> wrote: > Hi again. I checked out Mental from the repo, and I'm totally lost. I'm > interested in these extensions, but... > > Someone called them a "vertical slice" (which means nothing to me, btw) > of a Rails app. I see that calling script/generate extension xxx gives > me an app directory inside vendors/extensions/xxx. I even see that > uncommenting a few lines in my xxx_extension.rb file creates a tab > inside the Radiant admin. (Clicking on that tab yields uninitialized > constant Admin::AssetController). > > As interesting as all that is, what's the point? Do extensions merely > change the administrative interface, or do they modify the way pages can > be handled? What kinds of actions would I put into a controller inside > this new app directory? Do I need to add routes? (My current app has a > heavily modified admin area that visually encompasses Radiant, and every > time I add an action I have to add another route -- very annoying.) > > I'd love to help, and I'd especially love to know what's going on, but > there's little documentation anywhere. > > I guess my primary question is, do extensions extend the admin interface > only, or are they also a way to handle tags? > Err... this was discussed previously on the list, also you should check the wiki and the weblog of Radiant site: http://radiantcms.org/blog/2007/01/23/how-to-getting-mental/ -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RAILS_DEFAULT_LOGGER on Mental
On 1/16/07, Michael Jones <[EMAIL PROTECTED]> wrote: > > To be on the save side check out revision #227. Please let me know if > > this does or doesn't fix the error you got... > > I ran: "rake rails:freeze:edge REVISION=227" sucessfully. > Oh no, you shouldn't do that! You're sticking to revision 227 of Rails, and Alexander say stick to revision 227 of Radiant SVN repo! Use the command I post on previous email: $ rake rails:edge:freeze TAG=rel_1-2-0_RC2 Inside your checkout Radiant Mental branch (or checkout Radiant specific revision 227 as Alexander said). -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RAILS_DEFAULT_LOGGER on Mental
On 1/16/07, Michael Jones <[EMAIL PROTECTED]> wrote: > Hi- > > I just updated my mental branch, when I tried to start the server I got: I guess is something related with Rails Edge and a broken revision? http://groups.google.com/group/dallasrb/browse_thread/thread/93490a637d018833/9c5faa5d2bead4e6?lnk=st&q=Deprecation+NameError+RAILS_DEFAULT_LOGGER&rnum=2&hl=en#9c5faa5d2bead4e6 Try sticking to a safe known-as-good revision or RC2 TAG maybe? $ rake rails:edge:freeze TAG=rel_1-2-0_RC2 > => Booting WEBrick... > > This looks like a Rails issue and not Radiant but I was wondering if > anyone else dealt with this? > > Thanks- > Michael > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Release of how to set up on DreamHost the proper way coming
On 1/16/07, Andrew Klein <[EMAIL PROTECTED]> wrote: > Okay. Got the fix started. Here's the problem (Again) -- It nags that > bluecloth does not exist. I've dropped bluecloth.rb in RAILS_ROOT, no > avail. vendor/, nope. vendor/plugins/, nope again. GEM_PATH, nope again. > Can't access GEM_HOME. I've ran out of ideas. radiant and radius is > seen, as is everything else. Just not seeing bluecloth. My previous fix > by tossing bluecloth into RAILS_ROOT isn't working now. Ideas? > This could sound stupid: tried RAILS_ROOT/lib ? They are added at the beginning of environment loading... > Just as an FYI, I've tossed the following two lines into my dispatch.cgi > and dispatch.fcgi. No luck: > > ENV['GEM_HOME']='/usr/lib/ruby/gems/1.8' > ENV['GEM_PATH']='/usr/lib/ruby/gems/1.8:/home/bladedthoth/.gems' > Maybe adjusting your .htaccess file instead? SetEnv GEM_HOME /usr/lib/ruby/gems/1.8 SetEnv GEM_PATH /usr/lib/ruby/gems/1.8:/home/bladedthoth/.gems Maybe this wiki page could help you on your quest: http://wiki.rubyonrails.com/rails/pages/HowToUseMultipleGemRepositories -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] POLL: Upgrading Unpacked Radiant Applications
On 1/15/07, John W. Long <[EMAIL PROTECTED]> wrote: > The core team is looking to revamp the bin/radiant script in the next > release and we are thinking of dropping support for the --unpack flag. > If user want to unpack a specific gem, he could use gem unpack 'gem name' instead. > The unpack flag extracts the entire source tree from the Radiant gem and > allows you to run the gem in "application" mode rather than "instance" > mode. Presently, it is becoming a pain to create an upgrade script > unpacked Radiant applications, thus we are considering dropping support > for them from the Radiant command. If we did this, you could still > extract Radiant from a tar file to run it in unpacked "application" > mode, but you would be on your own when it comes to upgrading it. > Upgrading would still be supported for applications running in instance > mode. > > The pole: > > 1. Did you install Radiant from source or use the gem? > To create extensions: from source (svn checkout) To deploy: gem mode > 2. If you installed Radiant using the gem, did you use the --unpack flag > with the radiant command? > Even I added that command to the original script, never used it. > 3. Would you mind if we dropped support for upgrading unpacked Radiant > applications (apps installed using the --unpack flag) if it > means that Radiant releases can occur more frequently? > I'm not a Radiant Core developer, but guess maintain the upgrade logic between version is a real pain. > The more people who respond the better. > Hope my comments on this worth something :-) -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] agregar extensiones a radiantcms
On 12/7/06, javier barcena <[EMAIL PROTECTED]> wrote: > Hola a todos.! > Una vez creada la extension en radiant con ruby script/generate extension > mi_extension > como hago para agregarle mi aplicacion. > Creando una aplicacion rails y despues copiar el contenido dentro de la > extension? > o se hace de otra manera. > Javier, la extensión es para Radiant, no para cualquier aplicación rails. Fíjate este link del wiki: http://dev.radiantcms.org/radiant/wiki/RPS2 Y el código de algunas extensiones: http://dev.radiantcms.org/svn/radiant/branches/mental/extensions/ Un comentario: si deseas tener mejor respuesta de ahora en adelante a tus preguntas, intenta enviarlas en inglés, ya que la mayoría de los desarrolladores y usuarios de Radiant manejan ese idioma Yo simplemente te contesto, no trabajo activamente con Radiant ni lo uso. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] quiero extender radiant
On 12/6/06, javier barcena <[EMAIL PROTECTED]> wrote: > Hoal gracais si todo eso lo estudie ya .. > ahora necesito y quiero extender radiantcms .. > y segun sean cribbs me dijo que ... use script/generator extension > mi_extension > pero m iradiant n otiene la misma extructura que la del site de branch > que radiant descargo.? > tengo el 5.2.2 > [snip] > Lo que tenes es el zip o tgz del ultimo release (0.5.2) Lo que necesitas es bajar con svn el "mental" branch: svn co http://dev.radiantcms.org/svn/radiant/branches/mental/radiant radiant-mental De ahí tendrás disponibles el extension generator, para poder crear tus extensiones. Saludos -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Presentation PDF
On 9/30/06, Erik van Oosten <[EMAIL PROTECTED]> wrote: > Hi, > > I blogged about it. And I have also put the presentation on my home > server. In only have a small uplink so I'll remove it when there is a > more solid download location. > > http://day-to-day-stuff.blogspot.com/2006/09/back-to-radiant.html > Hi Erik, you could replace your link with my copy: http://www.mmediasys.com/downloads/radiant/radiant_cms.pdf I'll host it until it exceed my 15GB of traffic ;-) (I don't use the site, so will have spare bandwidth). Regards everyone, > Regards, > Erik. > > > > Yes, I'd like an URL too to put on my website and advertise it to > > people. > > -- > > Ollivier Robert - > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Presentation PDF
On 9/29/06, Nathan Wright <[EMAIL PROTECTED]> wrote: > I gave a presentation to our local Ruby/Rails meeting the other night, > so I thought I'd post the slides here in case anyone is interested. > It's pretty basic stuff, but it might help some who are new to > Radiant. That was excellent Nathan!, The best Radiant introduction someone could imagine. (Even if Radiant is simple, a fresh start is always a bit difficult). I could host the PDF on my site (just a link, no official website to post more info). If that's good with you, will post the link here (already uploaded it, waiting you approval). Good weekend everyone. > > -- > Nathan > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Asset Manager Mephisto Style => Plugin system
On 9/1/06, dror tirosh <[EMAIL PROTECTED]> wrote: > Hey Nicholas, > Look at the page_part_type in the trac system for an implementation of > something similar to what you are talking about. > The only thing is that this doesn't come instead of behaviors, it is a > compliment, and they work together very well. For example an event page_part > allows you to choose a date ( instead of the text box ) and then an event > behavior uses those dates to create tags for coming and past events. > I'm using it in a project were my writers can hardly use word, I have > created a rich text page_part based on fckeditor, an event page_part, an > attachment page_part and a multiple uploads page part (this one loads images > in the background, ajax like) that also shows a gallery. > There is an attachment page_part in the works, but there is some problem > with act_as_taggable not working in development environment, which makes it > realy hard to debug anything else. > Dror > Its just me or Radiant Trac is choked? http://dev.radiantcms.org/radiant/ticket/147 Oops... Trac detected an internal error: 'utf8' codec can't decode bytes in position 36-37: invalid data Anyway, page parts aren't the only thing that should be "pluggable". Assets manager (ala Mephisto), Comment manager, ANY manager (you named) should expose an admin tab, even if no offer a behaviour/filter to manage We created something similar for our applications using similar concept of Behavior registration mechanism and later collected the "tabs" to render them on the admin interface. > > On 9/1/06, Nicholas Mulder [Mulder Consulting] <[EMAIL PROTECTED]> > wrote: > > > Once we have a robust plugin system going I would love to see someone > > > create an asset management solution similar to Mephisto's. I'm not sure > > > if buckets trump the idea for attachments, but it is definitely causing > > > me to rethink my previous ideas about assets. > > > > > That would probably be up the the plugin authors (and the Mephisto > > > people). But I do think it would be great if code could be shared. > > > > > > Ya, their asset management is really good. So simple. So simple we all > > could have thought of it. But we didnt Rick and Justin did. Now we > > should ask them if they will play nice with us... > > > > About the plugins. I know it is on the road map to make a really cool > > plugin system. I dropped a message about this a week or so ago, and got > > no answer. > > > > Is there room in the plugin system for some hooks into the admin > > interface?? What would be really sweet is to be able to define a page > > part as a behavior and have its interface change a bit. Think about a > > gallery part where instead of a great big text box, the user could add > > descriptions to their sub-folders/albums of photo's. Or in a menu part > > where you could define and reorder menu items and such. Hooking into > > those page parts in the admin interface might not be too 'evil'... Would > > need to be able to define a form in radius tags, then parse the result > > of that form(s) in the behavior. > > > > Thoughts? > > > > Nicholas Mulder > > > > Mulder Consulting > > 905 658 5641 > > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > > > > > > > ___ > > Radiant mailing list > > Radiant@lists.radiantcms.org > > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > ___ > Radiant mailing list > Radiant@lists.radiantcms.org > http://lists.radiantcms.org/mailman/listinfo/radiant > > > -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Radiant@lists.radiantcms.org http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Asset Manager Mephisto Style
On 9/1/06, Nathan Wright <[EMAIL PROTECTED]> wrote: > I believe that Mephisto uses the acts_as_attachment plugin (which > works *great* by the way), and you can set this plugin to store > attachments in either the file system or in the database. While > waiting for a real solution for the images issue in Radiant, I hacked > together a rich text version of Radiant using this plugin. My client > has been using it for 2 months now without a single problem. > Glad to hear that, haven't checked the guts of mephisto yet. What really amazed me about it is that broke webrick! (yeah, you need mongrel to run it, even for testing). Anyway, A few things are needed in the Radiant roadmap (as John said, plugin capability) and then everything will follow, blogging, assets, you name it! > On 9/1/06, Luis Lavena <[EMAIL PROTECTED]> wrote: > > On 9/1/06, John W. Long <[EMAIL PROTECTED]> wrote: > > > Nicholas Mulder [Mulder Consulting] wrote: > > > > For fun I installed Mephisto yesterday. Wow is it cool for a blogging > > > > app. (http://mephistoblog.com/) > > > > > > > > Mephisto's Asset management systems is as they claim it is, 'probably > > > > the best you'll find in any CMS/Bloggin application'. All I can say is > > > > wow, they have Buckets! > > > > > > Once we have a robust plugin system going I would love to see someone > > > create an asset management solution similar to Mephisto's. I'm not sure > > > if buckets trump the idea for attachments, but it is definitely causing > > > me to rethink my previous ideas about assets. > > > > > > > Looking at both Radiant and Mephisto I can see two very similar apps > > > > heading in two different directions. Just wondering if for some of the > > > > 'lower level' stuff like comments, asset management, etc. is it worth > > > > 'sharing'? I would just hate to see a competition to see who's is > > > > better when working together could potentially make both better. > > > > > > That would probably be up the the plugin authors (and the Mephisto > > > people). But I do think it would be great if code could be shared. > > > > > > > John, > > > > The Mephisto style for assets sounds good, but plain or direct use of > > their code could be difficult. > > > > They store the assets on the file system, on contrary that your desire > > to leverage only on DB to distribute everything for Radiant. > > > > Maybe the way they choose to use it could change your mind. > > > > -- > > Luis Lavena > > Multimedia systems > > - > > Leaders are made, they are not born. They are made by hard effort, > > which is the price which all of us must pay to achieve any goal that > > is worthwhile. > > Vince Lombardi > > ___ > > Radiant mailing list > > Radiant@lists.radiantcms.org > > http://lists.radiantcms.org/mailman/listinfo/radiant > > > > > -- > Nathan > ___ > Radiant mailing list > Radiant@lists.radiantcms.org > http://lists.radiantcms.org/mailman/listinfo/radiant > -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Radiant@lists.radiantcms.org http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Asset Manager Mephisto Style
On 9/1/06, John W. Long <[EMAIL PROTECTED]> wrote: > Nicholas Mulder [Mulder Consulting] wrote: > > For fun I installed Mephisto yesterday. Wow is it cool for a blogging > > app. (http://mephistoblog.com/) > > > > Mephisto's Asset management systems is as they claim it is, 'probably > > the best you'll find in any CMS/Bloggin application'. All I can say is > > wow, they have Buckets! > > Once we have a robust plugin system going I would love to see someone > create an asset management solution similar to Mephisto's. I'm not sure > if buckets trump the idea for attachments, but it is definitely causing > me to rethink my previous ideas about assets. > > > Looking at both Radiant and Mephisto I can see two very similar apps > > heading in two different directions. Just wondering if for some of the > > 'lower level' stuff like comments, asset management, etc. is it worth > > 'sharing'? I would just hate to see a competition to see who's is > > better when working together could potentially make both better. > > That would probably be up the the plugin authors (and the Mephisto > people). But I do think it would be great if code could be shared. > John, The Mephisto style for assets sounds good, but plain or direct use of their code could be difficult. They store the assets on the file system, on contrary that your desire to leverage only on DB to distribute everything for Radiant. Maybe the way they choose to use it could change your mind. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Radiant@lists.radiantcms.org http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Deployment without SSH?
On 8/3/06, John W. Long <[EMAIL PROTECTED]> wrote: > Cory D wrote: [snip] > > What Web host are you using? Perhaps something like > http://www.hostingrails.com/ would work for you? Hey John, never heard of them, how serious are those guys? We should start creating a "opinion" webapp to qualify different hosting and options ;-) -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Radiant@lists.radiantcms.org http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radrails Install Plugin
On 8/3/06, John Butler <[EMAIL PROTECTED]> wrote: > Hi, > > I'm having a problem installing plugins in the latest version of > radrails. > Have you tried installing them manually? I suggest use scrip/plugin. $ruby script/plugin source http://svn.kylemaxwell.com/upload_reference_app/vendor/plugins/ $ruby script/plugin install remote_upload > I used the Plugin window in radrails to select file_column to install > file_column and everything worked ok. I cannot run radrails to install other plugins not on their listing, don't know why either. > Now i want to install remote_upload plugin which isnt in the plugins > list contained in radrails. So i select plugin from the generators tab > and type remote_upload and hit return. This instals the correct folder > in the vendors folder but all of the files contain just comments like > below. > > # Http:Sean.treadway.info::Svn::Plugins::RespondsToParent > > Can anyone tell me how to install the plugin with all the files. The > link is below and i have tried putting the url in the plugin field to > install without success. I'm having the same problem for > responds_to_parent. Is their a specific way to install 3rd party > plugins? > > http://svn.kylemaxwell.com/upload_reference_app/vendor/plugins/remote... > HTH, -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Radiant@lists.radiantcms.org http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] radiant gem (beta 2): database setup issue
On 6/26/06, Maurizio Balestrieri <[EMAIL PROTECTED]> wrote:
> On 6/27/06, Luis Lavena <[EMAIL PROTECTED]> wrote:
> > A bit more intelligence should be into radiant command to determine
> > previous existance of a instance and blah blah blah... (hard work on
> > doing this).
>
> Thank you for your clarification. I think the two methods you suggest
> are both simple enough to be useful. So if I've understood correctly,
> one way to proceed to align all radiant-based sites someone has on a
> server with the latest radiant version, would then be:
> - update the gem ("gem update radiant")
> - issue a "radiant ." command for each site (radiant instance)
Exactly, please excuse my bad english ;-)
radiant command is still a bit dumb to determine identical and updated
files into the instances to know what to do (it will ask you about
overwrite always, instead of skip the identical ones).
Will look into that later, but so far, "radiant" command proven to be
useful, at least for a few users (me included ;-)
Regards,
> ___
> Radiant mailing list
> Radiant@lists.radiantcms.org
> http://lists.radiantcms.org/mailman/listinfo/radiant
>
--
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi
___
Radiant mailing list
Radiant@lists.radiantcms.org
http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] radiant gem (beta 2): database setup issue
On 6/26/06, Maurizio Balestrieri <[EMAIL PROTECTED]> wrote: > On 6/27/06, Luis Lavena <[EMAIL PROTECTED]> wrote: > > Actually, each instance works separately, even its "bound" to a > > specific gem version, like rails. So a site running against radiant > > 0.5.0 will co-exist with radiant 0.6.1 as long both gems are still > > installed. > > Luis, can you shed some light for me on this? For example, I've > created an instance with the beta-2 gen, which installs radiant 0.50. > At a later time I'll update the gem (radiant version 0.61) and create > a second instance (for a new site). This new instance will use radiant > 0.61. As far as I understand from your sentence above, will the > previously installed instance will continue to run on radiant 0.50? If > this is the case (a sort of "freeze" of the instance-specific radiant > version at installation time), is there a way to update (unfreeze) all > the installed instances? Check into your 0.5.0 instance for config/instance.yml There is coded the gem version of radiant that will be used. If no database changes are introduced between versions, changing this and saving will make your instance work with the new version. The other way is using 'radiant' command in the instance, which will extract the file needed for the new version into the already existing instance. A bit more intelligence should be into radiant command to determine previous existance of a instance and blah blah blah... (hard work on doing this). I'll post osme suggestions to John when have spare time for this, always to enhance functionality. > ___ > Radiant mailing list > Radiant@lists.radiantcms.org > http://lists.radiantcms.org/mailman/listinfo/radiant > -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Radiant@lists.radiantcms.org http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] radiant gem (beta 2): database setup issue
Hi Ryan, On 6/26/06, Ryan Platte <[EMAIL PROTECTED]> wrote: > On Jun 26, 2006, at 4:52 PM, Maurizio Balestrieri wrote: > > > On 6/26/06, John W. Long <[EMAIL PROTECTED]> wrote: > >> Oh, right. Create the db directory. > > > > :) It is working OK now. Thank you. > > > > P.S. I think the gem-based distribution of radiant is a very good > > idea, because you install radiant just once (as a gem), keep it > > updated easily (gem update radiant), and if you have multiple > > radiant-based sites you don't have to install the app again and again, > > besides keeping it updated and in synch everywhere. > > Note that the downside is that with a unified installation, you have > to verify each of your sites all at the same time, instead of > separately. What if there's a subtle change that affects some > assumption you've made in the code of one of your sites? Major source > of potential gotchas. > Actually, each instance works separately, even its "bound" to a specific gem version, like rails. So a site running against radiant 0.5.0 will co-exist with radiant 0.6.1 as long both gems are still installed. In case you don't want it work as gem, svn checkout the radiant truck and create a radiant instance that is bound to that source folder. Both approaches works in similar ways. > I'm not disagreeing that it's a good idea, just mentioning that it's > not necessarily all flowers and radiant sunshine. > > -- > Ryan Platte > Senior Developer, SubscriberMail, LLC > > Warrenville Rd. > Suite 530 > Lisle, IL 60532 > (630) 303-5072 > > Not Just Email...SubscriberMail > http://www.subscribermail.com/ > > This message (including attachments) contains proprietary information > which may not be disclosed or used beyond the purposes of this > message without the written consent of SubscriberMail, LLC. If you > receive this message in error, notify the sender and destroy this > message and all attachments immediately. Thank you. > > SubscriberMail is covered under US PATENT 6,769,002 > > > > ___ > Radiant mailing list > Radiant@lists.radiantcms.org > http://lists.radiantcms.org/mailman/listinfo/radiant > -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Radiant@lists.radiantcms.org http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] db/setup.rb
On 6/23/06, Bryan Liles <[EMAIL PROTECTED]> wrote: > What happened to db/setup.rb? It was removed in r71. It was moved to script/setup_database, for better handling of radiant as a gem. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Radiant@lists.radiantcms.org http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Commenting
On 6/7/06, Rodney Ramdas <[EMAIL PROTECTED]> wrote: > hi, i'm looking at railsmail tnx ! > > so you want a Mail tab in Radiant an basically build a behavior > that works with RailsMail ? > > not sure how this relates to commenting/forum behavior though :-) > With that I was suggesting how to provide a "extension" or plugin to be laoded by raisl and that extend radiant. RailMail was a example, inside it you could see how it "extend" the paths to include the models, controllers and views inside the plugin. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Radiant@lists.radiantcms.org http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] webrick problem
On 6/7/06, J. Ryan Sobol <[EMAIL PROTECTED]> wrote: > I'm having a little trouble getting the current svn revision running > under webrick. After starting radiant's webrick servlet, I'm getting > the following error, sent to stdout, as soon as I access the app > through a browser. > > Bus error (core dumped) > > My other personal rails apps work fine when running their respective > copies of webrick. Perhaps I need to have rails 1.1? I don't think > I've upgraded since 1.0. At the very least, it would be nice of > someone could confirm whether or not radiant under webrick works for > them. > Hello Ryan: Radiant have Rails in vendor/rails directory, so no need of rails gem installed in your system. Please provide information about your os, version, libs, etc. Regards, -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Radiant@lists.radiantcms.org http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Commenting
On 6/7/06, Rodney Ramdas <[EMAIL PROTECTED]> wrote: > Hi Bruce, > > I've started work on a forum behavior , not commenting per see > but the two ideas could be merged. > > It's pretty simple, I'm using Tobias' Opinion as an example. I was > actually distracted by how to package it up. At the moment there's > a bunch of models, a controller etc. I've set it up plugin style like > the gallery behavior. > Hi Rodney, I'll suggest take a look at RailMail http://agilewebdevelopment.com/plugins/rail_mail That actually hook controller and models to the load path. For the admin side, we will need some sort of register (like Behaviors) on the controllers that will be available as tabs for the admins... what do you think? Regards, -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi ___ Radiant mailing list Radiant@lists.radiantcms.org http://lists.radiantcms.org/mailman/listinfo/radiant
