similar to: Rails Engine ActionController::UrlGenerationError on functional tests

Hi all, I was hoping someone could please clarify the differences between a full engine and a mountable one. I have noticed the following: ** Full Engine ** - With a full engine, the parent application inherits the routes from the engine. It is not necessary to specify anything in parent_app/ config/routes.rb. Specifying the gem in Gemfile is enough. The engine routes are specified as: #

hello, i have a rails 3 engine scoped dynamically like this: scope "/:locale" do mount MyEngine::Engine => '''', :as => ''my_engine'' end I can''t seem to be able to set my own locale like this: my_engine.page_path(page, :locale => ''de'') the path is generated like this: /en/page/12345?locale=de instead of

(Using Rails 4.1.1 with Ruby 2.1.1 on Mac OSX 10.6 Snow Leopard) I'm doing a Rails tutorial (in case you are interested in: It's http://guides.rubyonrails.org/getting_started.html), and I'm stuck on the following: I create in some erb file a link using <%= link_to 'Add new weird stuff', controller: new_article_path %> and this raises the exception

Working on Rails Engine. I want to make the controllers customizable whereever the Rails Engine is used. Therefore, I was trying to use `extend ActiveSupport::Concern` on the Engine controller class and include it in MyRailsApp. https://gist.github.com/4185823 # code in my rails engine moduel MyEngine class SomeController extend ActiveSupport::Concern def engine_some_method

= Engines Generator = Now part of the Engines plugin, you can generate your very own engines. $ script/plugin install engines $ script/generate engine MyEngine = Howto Extract an Engine = I have also written a little documentation on how to extract an engine out of an existing application: http://rails-engines.rubyforge.org/wiki/wiki.pl?ExtractAnEngine = Changelog =

Currently Makefiles for vignettes are only supported for .tex files. Could the tools package be modified to allow file extensions to be specified for a vignette engine? Having the pandoc pdf conversion in a Makefile rather than through R would be tidier in some cases. If I specify my vignette engine as ``` tools::vignetteEngine( 'myengine', pattern = '\\.[Rr](md|nw)$',

I create a simple engine with a simple controller: class FredController < ApplicationController def hello render :text => ''Hello, world!'' end end and I create a simple functional test within the engine: class FredControllerTest < Test::Unit::TestCase ... def test_hello get :hello assert_response :success end

I like the idea of "instant functionality" Engines can offer, but practical implementation issues make adding and removing more tedious than it should be. The process typically requires: - manual modifications to environment.rb ( e.g., adding engine configuration and "Engine.start :myengine" - manual modification to app/controllers/application_controller.rb This should be

1) Right now this is just testing a successful response. However, since I've gone and created a Post via FactoryGirl... how can I test the @post.id equals one of the id's being returned by the get: index json? describe Api::V1::PostsController do context 'Post' do before(:each) do @post = FactoryGirl.create(:post) end context '#index' do

Hello, Would it be possible to add generic engine support to OpenSSH? One use in particular would be to support TCP forwarding for secure mail server connections and similar applications. This would permit an administrator to configure in an arbitrary external engine to establish a secure RSA-based tunnel. OpenSSH would need no information built into it to accomodate any particular engine. One

Hi, I notice looking at the code for the generate script that there it "recognises" a --destination command line parameter (so I can do ''ruby script/generate model --destination vendor/plugins/my_engine my_model'') but it isn''t processed by the command line handling. I''ve hacked it into my code but I was wondering if this is an up-and-coming thing or

I use Engine. How to get access to url_helpers, such as <name>_path or _<name>_url, in a separate class? In application it simple: Rails.application.routes.url_helpers.<name>_path But how to get access to url_helpers in Engine? When I use Rails.application.routes.url_helpers.root_path, then I get ''/'', root of Application. Other helpers for Engine

In Rails 3, is it possible to have a plugin inside an engine? Adding the lib dir of the plugin to autoload_paths doesn''t seem to work. I can manage to load it by adding that path to $: and requiring the init.rb file, but I''m not sure that''s the correct approach. Thanks! -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: