Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Thu, 3 Nov 2011 17:55:32 +0000 (UTC)
From: "The Dod (Commented) (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: 
 <1674333728.56616.1320342932339.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1385309347.12830.1318573091841.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (COUCHDB-1307) Error popup when viewing futon on
 a vhost
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143385#comment-13143385 ] 

The Dod commented on COUCHDB-1307:
----------------------------------

I'd like to address the second issue you've raised first, because it's much more critical: You can't disable a user's ability to change own profile, and the current "de facto standard" (i.e. what you get from "couchapp generate" and therefore - 99% of the couchapverse) is that "edit profile" is a link to /_utils/document.html?_users/org.couchdb.user:myusername
Even if in the future a non-futon solution for "edit profile" emerges, we'd still have to leave a clue to users of legacy couchapps there (it's acceptable if they get a warning or two along the way, but we'd still need a "we've moved here" link somewhere).

Now for the issue of "treating *any* error case as a possible vhost": we're taking about a *specific* case. The function that might "fail" here is discovering the server's version. If the error is a result of something more serious than "we're on a vhost", then other alerts would (or at least should) trigger. All we need is to change the *comment* in the code "either it's a vhost, or things are so bad user has already figured out there's a problem and doesn't need yet another popup right now" :)

A more elegant way to solve this would be to use a vhost-agnostic /_version or something instead of / for fetching the version, but my patch works on localhost. The fact that I don't have it at - say - iriscouch (because it's not "official") is frightening my users, so pretty please - either do it properly (/_version) or accept this simple and harmless patch so that they can relax.
                
> Error popup when viewing futon on a vhost
> -----------------------------------------
>
>                 Key: COUCHDB-1307
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1307
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Futon
>            Reporter: The Dod
>            Priority: Minor
>              Labels: javascript, patch
>         Attachments: futon.js.diff
>
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> When accessing futon from a vhost (where "/" doesn't return a json description of the server), you unnecessarily get an "error" popup (containing the entire html of the "/" page).
> Since many CouchApps link into futon as a way for end users to edit their profiles, they get the impression that the app is "broken".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira