Doesnt Seem to be working with Mountable Rails engines about miniprofiler HOT 4 OPEN

Will this break subdirectroy based rails installs though? care to give a full fix a shot, I don't really want to fix this just to break other cases.

from miniprofiler.

This was a major headache for me using a plethora of mountable engines. Thanks for finding a little fix - even if it has caused some more breaks elsewhere? I haven't seen any problems yet.

from miniprofiler.

@SamSaffron looks like rails4 mangles the SCRIPT_NAME based on the engine's mounted location so it's not an accurate method of getting the base.

rails/rails@5b3bb61

Perhaps it would be ideal to append env['SCRIPT_NAME'] to the default base_url_path instead of appending it to all base_url_paths, so that if people need to override it, they can do so without patching miniprofiler?

from miniprofiler.

sure, care to try a PR for it?

On Thu, Sep 12, 2013 at 6:59 AM, Michael J. Cohen
[email protected]:

@SamSaffron https://github.com/SamSaffron looks like rails4 mangles the
SCRIPT_NAME based on the engine's mounted location so it's not an
accurate method of getting the base.

rails/rails@5b3bb61rails/rails@5b3bb61

Perhaps it would be ideal to append env['SCRIPT_NAME'] to the default
base_url_path instead of appending it to all base_url_paths, so that if
people need to override it, they can do so without patching miniprofiler?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/178#issuecomment-24275889
.

from miniprofiler.