Might this be due to the fact that Rails will render a view even if
there’s no corresponding controller action behind it? I.E. even though
you are removing the ‘new’ action, because the ‘new.rhtml’ file is
present and locatable, Rails will presume that you want to render
that.

I’m not sure that I can see a way around this at the moment, since the
idea of Engines is that you don’t need to mess with the internals. As
you say, you can always fake out the action to send the user somewhere
else.

Might this be due to the fact that Rails will render a view even if
there’s no corresponding controller action behind it? I.E. even though
you are removing the ‘new’ action, because the ‘new.rhtml’ file is
present and locatable, Rails will presume that you want to render
that.

Ah! Yes, that’s exactly what it is. I never realized that feature of
Rails (but it’s perfect, as I was just about to create a bunch of
pseudo-actions for some static pages, and now I don’t have to).

So no, I can’t think of a way around it either - if new.rhtml exists in
the
search path, then it exists, and there’s no way to negate that. For my
current case, re-rendering a different page is fine; I guess if it ever
becomes a real problem, I’ll just think harder.