I found the time to package the decorator pattern into a gem:
http://rubygems.org/gems/rails_engine_decorators
https://github.com/atd/rails_engine_decorators
Hope it is helpful.
El 22/07/12 23:31, Weston Platter escribió:
Added 2 strategies for extending Engine Models. Feedback is welcome.
ht
### App
Rewrite the User Subscriptions module not the class itself.
Maybe the example is not the best, but what do you think of this
approach of having all the behaviour you want to expose in mixins and
seeing changing the models or controllers as a bad smell. Does it make
sense?
On Oct 1, 2012, at
A patch for supporting i18n in Engines:
http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2325-i18n-support-for-engines
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To
Hello all,
I've been working for more than a year in a Rails Engine for Content
Management System
http://github.com/atd/cmsplugin/tree/master
This means authentication, authorization, resource import/export, categories,
tags, etc...
These are common features in web applications not currently c
ne (http://github.com/vigetlabs/
> sandstone/tree/master).
>
> How is this different from other cms plugins available for rails? What
> does your solution provide that others do not?
>
> On Mar 31, 9:23 am, Antonio Tapiador del Dujo
>
> wrote:
> > Hello all,
> >
El Domingo, 30 de Agosto de 2009 20:24:16 Sven Fuchs escribió:
> On 30.08.2009, at 20:00, Michael Koziarski wrote:
> >> I'll have a look at a patch. I assume this can go into 2.3.x?
> >
> > Let's start with master and look at backporting if it's simple and
> > 'purely additive'.
>
> I guess it is
Hi jesusOmar,
first of all, let me tell you that this question should go to rubyonrails-talk
group (http://groups.google.com/group/rubyonrails-talk). This one (rails-core)
is intended to other topics, related with the development of Rails itself.
As for your question, you have to write "task" in
BTW, is there any way to get the docs for 3.0.0.beta3?
El Martes, 25 de Mayo de 2010 17:35:31 Xavier Noria escribió:
> On Tue, May 25, 2010 at 4:01 PM, Michael Breen wrote:
> > I wasn't exactly sure where this should go but I figured this would be a
> > good place start.
>
> Thanks for the heads
I suffered this. I was very annoyed because Rails was rendering nothing. Then I
realized I was passing an empty array and I remembered this issue!
+1
El Sábado, 23 de Octubre de 2010 23:05:06 Eugene M. Magdel escribió:
> Had the same problem! Thanks for reporting!
>
> On Sep 30, 1:28 pm, James
ok on it.
>
> Thank you :)
>
> On 28 ต.ค. 2553, at 21:08, Antonio Tapiador del Dujo wrote:
> > I suffered this. I was very annoyed because Rails was rendering nothing.
> > Then I realized I was passing an empty array and I remembered this
> > issue!
> >
> > +1
Hi Markus,
can associated records be created, using accepts_nested_attributes_for ?
That would be awesome!
El Lunes, 28 de Febrero de 2011 17:16:07 markusschwed escribió:
> Hello everyone,
>
> I'm new in contributing and i saw in the contributing-guides, that i
> have to write an email at this
El Miércoles, 6 de Abril de 2011 17:07:48 Samuel Kadolph escribió:
> For the longest time PartialRenderer#partial_path has prefixed the
> prefix of the current controller when it is nested in a module. This
> hasn't been a problem (because nesting controllers wasn't that common)
> but with 3.1 stri
According to RFC 3986, '[' and ']' are reserved characters. However, Rails
3.0.7 is not escaping them.
This is fixed in master by this commit:
https://github.com/rails/rails/commit/52b71c01fd3c8a87152f55129a8cb3234190734a
Can this fix be included in 3.0.x ?
--
You received this message because
Requesting /attachments/1.all does not work in Rails 3. It was changed here:
https://github.com/rails/rails/commit/7e280c3bff8ac25f1c1938aeaeb1d0b4c0fbb726
The use case is a show action such as:
def show
@attachment = Attachment.find(params[:id])
respond_to do |format|
format.html
f
On Viernes 17 Febrero 2012 06:25:47 Ilya Grigorik escribió:
> Right, so with that in mind.. Is anyone on Rails core looking at this
> currently?
>
> FWIW, if there are any questions about the process, etc, I'm willing to
> help and see if I can get help from inside Google. I'd love to see Rails as
On Domingo 04 Marzo 2012 20:36:12 Michael Schuerig escribió:
> On Thursday 01 March 2012, Consu wrote:
> > What will it cost in real money, to upgrade a bigger Rails App?
>
> For the past few weeks I've been working on Rails app that has grown
> over about 3 years to around 25kloc. The app was stu
It seems pretty useful for other engines as well! Any chances to be
included in Rails?
On 13/07/12 06:00, Ryan Bigg wrote:
We're currently discussing the best way to do this on Forem's issue
#260 (https://github.com/radar/forem/pull/260). Kunal there wants to
add methods to or modify the Forem
El Wednesday 27 February 2008 18:39:08 wildchild escribió:
> http://dev.rubyonrails.org/ticket/11031
>
> This patch adds a new option to map.resources named :polymorphic,
> which will attach a :type requirement to the generated route. It keeps
> URLs absolutely clean.
Useful for me!
I'm already u
El Thursday 06 March 2008 14:09:16 Chris Cruft escribió:
> Wildchild,
> Your patch takes an approach that differs from the one taken by the
> ResourcesController plugin. I like the RESULT of your patch (:*_type
> key in the params) but, as shown by the RC plugin, I'm not sure the
> specification
Hi,
I posted a message to rails talk about a problem with requirements option in
routes, without answers:
http://groups.google.com/group/rubyonrails-talk/browse_thread/thread/9f0dafe1a975de17/96dd4f2fa96ebc75#96dd4f2fa96ebc75
Could anybody please give a hint about where does Rails process :requi
Rails 2.1 Request Forgery Protection is incompatible with AtomPub
implementations
New 'verifiable_request_format?' function
(action_controller/request_forgery_protection.rb:101) is banning DELETE
requests, where request.content_type is nil
It also forbids posting any type of media, like imag
El Friday 20 June 2008 19:04:04 Manfred Stienstra escribió:
> On Jun 20, 2008, at 6:49 PM, Antonio Tapiador del Dujo wrote:
> > Rails 2.1 Request Forgery Protection is incompatible with
> > implementations
> >
> > New 'verifiable_request_format?&
El Sunday 29 June 2008 23:02:58 Rick Olson escribió:
> On 6/20/08, Antonio Tapiador del Dujo <[EMAIL PROTECTED]> wrote:
> > Rails 2.1 Request Forgery Protection is incompatible with AtomPub
> > implementations
> >
> > New 'verifiable_request_for
With single resources:
map.resource :profile
polymorphic_path(@profile) generates profile_path but fails because of the
remaining @profile object, I guess:
NoMethodError: You have a nil object when you didn't expect it!
The error occurred while evaluating nil.to_sym
from
/usr/lib/ruby
24 matches
Mail list logo
