Databases
StackOverflow2013
Postsdbo
PORails route helpers are inexplicably prepending "postinstall" to requests
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails route helpers are inexplicably prepending "postinstall" to requests
    primarykey
    data
    text
    <pre><code>* Listening on tcp://0.0.0.0:3000 Started GET "postinstall/" for 127.0.0.1 at 2013-10-27 07:26:15 +0000 ActiveRecord::SchemaMigration Load (1.8ms) SELECT "schema_migrations".* FROM "schema_migrations" </code></pre> <p>This is basically it, all my buttons linked to helpers like:</p> <pre><code>new_user_registration GET /users/sign_up(.:format) registrations#new edit_user_registration GET /users/edit(.:format) registrations#edit </code></pre> <p>Only all the links are like this:</p> <pre><code>http://localhost:3000/postinstall/users/sign_in </code></pre> <p>I've been through my log and at one point requests just start being effectively poisoned by this "postinstall" business.</p> <p>I've grepped for 'postinstall' because surely this word can't be coming from nowhere. I decided to sleep on it because I thought it must be a stupid mistake, but now I need help and unlike 99.9% of my previous questions - it doesn't seem this one has been answered whatsoever.</p> <p>Searching for even the query "postinstall" on Google yields terrible results.</p> <p>I <strong>THINK</strong> my problem lies in a path helper, everywhere the 'postinstall' is getting prepended to requests/urls - the path is referred to like so: </p> <pre><code>&lt;a href="/users/sign_in" class="btn btn-success"&gt;Test&lt;/a&gt; &lt;%= link_to "Sign In", new_user_session_path, :class =&gt; "btn btn-success" %&gt; </code></pre> <p>Where the first link would work route OK, but then the buttons to Submit the login form are trying the POST to /postinstall/users/sign_in etc... The second button would be a link to /postinstall/users etc.</p> <p>I have absolutely no idea how this started, I've been over my git log and even going back 3 or 4 days (this issue started last night) the error still persists. </p> <p>Is it seemingly specific to my Mac too, deployed to a dev site (Ubuntu) with no issues. I have restarted my mac etc. Any help is very obviously appreciated...</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USWilll
    1. USWilll
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORails route helpers are inexplicably prepending "postinstall" to requests
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORails route helpers are inexplicably prepending "postinstall" to requests
      1. USWilll
      1. VTFavorite
    3. VO
      singulars
      1. PORails route helpers are inexplicably prepending "postinstall" to requests
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAnd I restarted again... and now it's working again... Does anyone know why it was happening, I have no idea what solved it. I added :sessions => "users/sessions" then restarted my computer, and it worked. I then removed that line of code and restarted the server and it still works..
      singulars
      1. PORails route helpers are inexplicably prepending "postinstall" to requests
      1. USWilll
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload