[jira] [Created] (COUCHDB-2662) Saving view multiple times causes conflict
Garren Smith created COUCHDB-2662: - Summary: Saving view multiple times causes conflict Key: COUCHDB-2662 URL: https://issues.apache.org/jira/browse/COUCHDB-2662 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith Saving view multiple times causes a conflict as the revision is not being updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (COUCHDB-2646) Page displays blank when trying to access broken view index
[ https://issues.apache.org/jira/browse/COUCHDB-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-2646. - Resolution: Fixed > Page displays blank when trying to access broken view index > --- > > Key: COUCHDB-2646 > URL: https://issues.apache.org/jira/browse/COUCHDB-2646 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > When a user tries to access a view via the database menu (see attached > screenshot) and the view is broken and won't index, trying to access it > results in a blank page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-2646) Page displays blank when trying to access broken view index
Garren Smith created COUCHDB-2646: - Summary: Page displays blank when trying to access broken view index Key: COUCHDB-2646 URL: https://issues.apache.org/jira/browse/COUCHDB-2646 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith When a user tries to access a view via the database menu (see attached screenshot) and the view is broken and won't index, trying to access it results in a blank page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (COUCHDB-2152) Views pagination has bad usability
[ https://issues.apache.org/jira/browse/COUCHDB-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2152. --- Resolution: Fixed > Views pagination has bad usability > -- > > Key: COUCHDB-2152 > URL: https://issues.apache.org/jira/browse/COUCHDB-2152 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin >Assignee: Garren Smith > > In Futon I can move to the next page in single click without scrolling much > (only for 100 rows per page). In Fauxton I always have to scroll down to till > page end and only after I can move to the next page. Things are getting worse > if I hadn't collapse the result e.g. disable include_docs option. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2188) Pagination is broken if map fun emits more rows than page size is
[
https://issues.apache.org/jira/browse/COUCHDB-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345170#comment-14345170
]
Garren Smith commented on COUCHDB-2188:
---
[~kxepal] can you check this. But I think this should be fixed now.
> Pagination is broken if map fun emits more rows than page size is
> -
>
> Key: COUCHDB-2188
> URL: https://issues.apache.org/jira/browse/COUCHDB-2188
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Fauxton
>Reporter: Alexander Shorin
>Assignee: Garren Smith
> Labels: advanced
>
> 1. Create new database with single doc - his content doesn't matters
> 2. Create the view that emits multiple rows for single doc, like:
> {code}
> function(doc){
> for(var i=0; i < 20; i++){
> emit(doc._id, i);
> }
> }
> {code}
> Yes, too synthetic, but you got the idea.
> 3. Try to navigate thought results with page size 5 and 10 - you'll always
> browse the same content
> Fauxton @
> [4e60f0b|https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commit;h=4e60f0b]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (COUCHDB-2584) Highlight user management section
[ https://issues.apache.org/jira/browse/COUCHDB-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2584. --- Resolution: Fixed > Highlight user management section > -- > > Key: COUCHDB-2584 > URL: https://issues.apache.org/jira/browse/COUCHDB-2584 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > Highlight user management section when it is active -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-2584) Highlight user management section
Garren Smith created COUCHDB-2584: - Summary: Highlight user management section Key: COUCHDB-2584 URL: https://issues.apache.org/jira/browse/COUCHDB-2584 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith Highlight user management section when it is active -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (COUCHDB-2047) UI for creating show functions
[ https://issues.apache.org/jira/browse/COUCHDB-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith reassigned COUCHDB-2047: - Assignee: Garren Smith (was: Sue Lockwood) > UI for creating show functions > -- > > Key: COUCHDB-2047 > URL: https://issues.apache.org/jira/browse/COUCHDB-2047 > Project: CouchDB > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Sue Lockwood >Assignee: Garren Smith > Labels: advanced > > http://docs.couchdb.org/en/latest/couchapp/ddocs.html#show-functions > Make a UI for adding show functions to the design doc. Similar to the Views > UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (COUCHDB-2582) Index Editor - view name resets
[ https://issues.apache.org/jira/browse/COUCHDB-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2582. --- Resolution: Fixed > Index Editor - view name resets > --- > > Key: COUCHDB-2582 > URL: https://issues.apache.org/jira/browse/COUCHDB-2582 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > Go to new view > Alter the Index name to "foo" > Select _count in the Reduce dropdown. > Note that the Index name has reverted to "new-view" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-2582) Index Editor - view name resets
Garren Smith created COUCHDB-2582: - Summary: Index Editor - view name resets Key: COUCHDB-2582 URL: https://issues.apache.org/jira/browse/COUCHDB-2582 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith Go to new view Alter the Index name to "foo" Select _count in the Reduce dropdown. Note that the Index name has reverted to "new-view" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2573) Problems selecting text in CodeMirror editor
[ https://issues.apache.org/jira/browse/COUCHDB-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314464#comment-14314464 ] Garren Smith commented on COUCHDB-2573: --- Small thing. Its Ace Editor. Not CodeMirror. > Problems selecting text in CodeMirror editor > - > > Key: COUCHDB-2573 > URL: https://issues.apache.org/jira/browse/COUCHDB-2573 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Ben Keen >Assignee: Ben Keen > > Two issues: > 1. The background color isn't that different from the selected row colour, so > it's not clear what's selected. > 2. The selected text background looks like it's being shifted to the left, > rather than behind the actual text you're selecting -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (COUCHDB-2564) New Doc link not working
[ https://issues.apache.org/jira/browse/COUCHDB-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2564. --- Resolution: Fixed > New Doc link not working > > > Key: COUCHDB-2564 > URL: https://issues.apache.org/jira/browse/COUCHDB-2564 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > The '<' is not working for new doc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (COUCHDB-2563) Changes page keeps filtered keyworks in memory
[ https://issues.apache.org/jira/browse/COUCHDB-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2563. --- Resolution: Fixed > Changes page keeps filtered keyworks in memory > -- > > Key: COUCHDB-2563 > URL: https://issues.apache.org/jira/browse/COUCHDB-2563 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith >Assignee: Garren Smith > > A database changes page keeps the filtered keywords in memory across > databases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-2564) New Doc link not working
Garren Smith created COUCHDB-2564: - Summary: New Doc link not working Key: COUCHDB-2564 URL: https://issues.apache.org/jira/browse/COUCHDB-2564 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith The '<' is not working for new doc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-2563) Changes page keeps filtered keyworks in memory
Garren Smith created COUCHDB-2563: - Summary: Changes page keeps filtered keyworks in memory Key: COUCHDB-2563 URL: https://issues.apache.org/jira/browse/COUCHDB-2563 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith A database changes page keeps the filtered keywords in memory across databases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (COUCHDB-2563) Changes page keeps filtered keyworks in memory
[ https://issues.apache.org/jira/browse/COUCHDB-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith reassigned COUCHDB-2563: - Assignee: Garren Smith > Changes page keeps filtered keyworks in memory > -- > > Key: COUCHDB-2563 > URL: https://issues.apache.org/jira/browse/COUCHDB-2563 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith >Assignee: Garren Smith > > A database changes page keeps the filtered keywords in memory across > databases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (COUCHDB-2483) Add CORS to Fauxton
[ https://issues.apache.org/jira/browse/COUCHDB-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2483. --- Resolution: Fixed > Add CORS to Fauxton > --- > > Key: COUCHDB-2483 > URL: https://issues.apache.org/jira/browse/COUCHDB-2483 > Project: CouchDB > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Christian Hogan >Assignee: Garren Smith > > Ticket for adding CORS support / enable options in Fauxton. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (COUCHDB-2483) Add CORS to Fauxton
[ https://issues.apache.org/jira/browse/COUCHDB-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith reassigned COUCHDB-2483: - Assignee: Garren Smith > Add CORS to Fauxton > --- > > Key: COUCHDB-2483 > URL: https://issues.apache.org/jira/browse/COUCHDB-2483 > Project: CouchDB > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Christian Hogan >Assignee: Garren Smith > > Ticket for adding CORS support / enable options in Fauxton. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (COUCHDB-2555) Clicking on React burger no longer triggers EVENTS.BURGER_CLICKED event
[ https://issues.apache.org/jira/browse/COUCHDB-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2555. --- Resolution: Fixed Assignee: Garren Smith (was: Ben Keen) > Clicking on React burger no longer triggers EVENTS.BURGER_CLICKED event > --- > > Key: COUCHDB-2555 > URL: https://issues.apache.org/jira/browse/COUCHDB-2555 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Ben Keen >Assignee: Garren Smith > > A minor bug, but I don't want to forget. This is listened to the full page > doc editor to know when it should repaint. Wasn't sure how to tackle it > without converting the doc editor to a React component, or at least adding a > store. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-2550) Bug in new notifications
Garren Smith created COUCHDB-2550: - Summary: Bug in new notifications Key: COUCHDB-2550 URL: https://issues.apache.org/jira/browse/COUCHDB-2550 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith Steps to reproduce: 1. edit a document 2. Click save 3. When the document saved notification appears click on the 'x' It then redirects the user back to the all databases page. I think you just need to add a 'data-bypass=true' to the 'x' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2507) Update Doc Editor page to make better use of space
[ https://issues.apache.org/jira/browse/COUCHDB-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243923#comment-14243923 ] Garren Smith commented on COUCHDB-2507: --- this looks awesome Ben, looking forward to this landing. > Update Doc Editor page to make better use of space > -- > > Key: COUCHDB-2507 > URL: https://issues.apache.org/jira/browse/COUCHDB-2507 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Ben Keen >Assignee: Ben Keen > Attachments: Screen Shot 2014-12-11 at 11.27.15 AM.png > > > Right now the document editor page doesn't make terribly good use of the page > and the styling's a bit out of date with the rest of the app. > A screenshot first draft of the new page is attached. This will go through a > few revisions, note. > Changes: > - focus placed on editor on first load > - editor now appears full page (no margins) > - buttons now place in a full button row underneath the main header > - header and function button row are now fixed, so large docs will only > scroll the editor region of the page. > - notifications moved to global notifications > - editor re-themed for consistency with other pages in Fauxton > - delete document confirmation prompt moved to bootstrap dialog > - ace editor now automatically scrolls into view when you click up/down and > the available space in the page runs out (right now the cursor just > disappears offscreen) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2404) Make second nav column consistently appear for all Database pages
[ https://issues.apache.org/jira/browse/COUCHDB-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231415#comment-14231415 ] Garren Smith commented on COUCHDB-2404: --- What about extending off the DocumentRoutesObject for the compaction and permissions RouteObject. Then all you have todo is implement the compaction method and the methods in the DocumentsRoutesObject will take care of the rest. They will initialise and setup the sidebar. Then you don't need to move anything around. > Make second nav column consistently appear for all Database pages > - > > Key: COUCHDB-2404 > URL: https://issues.apache.org/jira/browse/COUCHDB-2404 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Ben Keen >Assignee: Ben Keen >Priority: Minor > > Right now when you select a DB and click on the various sub-pages that appear > in the second column, sometimes the column stays there, sometimes it > disappears (Permissions, Compact & Clean). Change this so that the second > column always shows up for all subpages. > This is an interesting one, architecture-wise. Those 2 pages - Permissions, > Compact & Clean - are separate components, and the sidebar content is found > in the Documents addon. Suggestions on how to tackle this very welcome! > btw, I spoke to Sean Barclay about this and got his thumbs up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2390) Fauxton config, admin sections considered dangerous in 2.0
[ https://issues.apache.org/jira/browse/COUCHDB-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224156#comment-14224156 ] Garren Smith commented on COUCHDB-2390: --- [~kxepal] we are working on something that allows fauxton to connect to a different node. But its still in a very early phase and won't solve this problem. > Fauxton config, admin sections considered dangerous in 2.0 > -- > > Key: COUCHDB-2390 > URL: https://issues.apache.org/jira/browse/COUCHDB-2390 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: BigCouch, Fauxton >Reporter: Joan Touzet >Priority: Blocker > > In Fauxton today, there is are 2 sections to edit config-file settings and to > create new admins. Neither of these sections will work as intended in a > clustered setup. > Any Fauxton session will necessarily be speaking to a single machine. The > config APIs and admin user info as exposed will only add that information to > a single node's .ini file. > We should hide these features in Fauxton for now (short-term fix) and correct > the config /admin creation APIs to work correctly in a clustered setup > (medium-term fix). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2390) Fauxton config, admin sections considered dangerous in 2.0
[ https://issues.apache.org/jira/browse/COUCHDB-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14223121#comment-14223121 ] Garren Smith commented on COUCHDB-2390: --- I think the conversation on this ticket has digressed a little. This ticket is what to do with the config section in Fauxton. I would like to keep the config section in Fauxton in for Couchdb 2.0. But we should state in the config section that the changes the user is making is only for a specific node/server. If we could add a dropdown link or something to get them to open up Fauxton to edit another nodes config that could also be useful. If a user has enabled CORS Fauxton could make a config change to any node. This is definitely not the perfect solution, but a workable solution for Couchdb 2.0. Then with later releases once there is a supported api for configure global and local settings we can change the config section accordingly. > Fauxton config, admin sections considered dangerous in 2.0 > -- > > Key: COUCHDB-2390 > URL: https://issues.apache.org/jira/browse/COUCHDB-2390 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: BigCouch, Fauxton >Reporter: Joan Touzet >Priority: Blocker > > In Fauxton today, there is are 2 sections to edit config-file settings and to > create new admins. Neither of these sections will work as intended in a > clustered setup. > Any Fauxton session will necessarily be speaking to a single machine. The > config APIs and admin user info as exposed will only add that information to > a single node's .ini file. > We should hide these features in Fauxton for now (short-term fix) and correct > the config /admin creation APIs to work correctly in a clustered setup > (medium-term fix). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2403) Build Fauxton for a different url paths?
[ https://issues.apache.org/jira/browse/COUCHDB-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182837#comment-14182837 ] Garren Smith commented on COUCHDB-2403: --- Hi @michaelcole, The correct way to do this is by setting the settings.json file. That is what it is there for. You can edit the app.root and app.host parameters to fit your needs. It only works once you rebuild fauxton though. It that doesn't quite fit your needs we might have to look at making the url a little more generic but thats a little tricky for how Fauxton works. > Build Fauxton for a different url paths? > > > Key: COUCHDB-2403 > URL: https://issues.apache.org/jira/browse/COUCHDB-2403 > Project: CouchDB > Issue Type: Question > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Michael Cole > > Hey, I'm trying to use Fauxton in another project: express-pouchdb > We'd like Fauxton to not know it's URL, until it's being served. So someone > could configure a PouchDB server in Express at their [own > URL](https://github.com/MichaelJCole/express-pouchdb#example-usage) like this: > /mydb/ <-- PouchDB server > /mydb/_utils <-- Fauxton > The best I could figure out to do was hard- > code the URL in settings.json and use `grunt release` to build Fauxton for > that specific URL. > Is there a better way? > Thanks! > Mike -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COUCHDB-2369) Adding Nightwatch.js to test Fauxton
[ https://issues.apache.org/jira/browse/COUCHDB-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165183#comment-14165183 ] Garren Smith commented on COUCHDB-2369: --- Some tests I would like to see are: Create database Delete database Create doc Delete doc Create view Query View If we can get those tests going this will help us smoke screen Fauxton nicely. Also if we can get it to integrate with our grunt tasks or if we have a npm command to run it like `npm fixtures` > Adding Nightwatch.js to test Fauxton > > > Key: COUCHDB-2369 > URL: https://issues.apache.org/jira/browse/COUCHDB-2369 > Project: CouchDB > Issue Type: Test > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Michelle Phung >Assignee: Michelle Phung >Priority: Minor > > Browser Automation: > Nightwatch.js is an easy to use Node.js based End-to-End (E2E) testing > solution for browser based apps and websites. > It uses the powerful Selenium WebDriver API to perform commands and > assertions on DOM elements. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (COUCHDB-2351) Docs page should show total record count
[ https://issues.apache.org/jira/browse/COUCHDB-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-2351. - Resolution: Won't Fix we cannot add the "of X rows" part because we support query options for a view query. Futon can do "Showing 1 - 10 of 11 rows" is because it doesn't support different query options. The total_rows returned for a view query stays constant even if a user adds some query options to the query. > Docs page should show total record count > > > Key: COUCHDB-2351 > URL: https://issues.apache.org/jira/browse/COUCHDB-2351 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Ben Keen > > On the document listing page, Futon shows: > "Showing 1-10 of 11 rows" > Fauxton just has "Showing 1-10" so you don't know how many documents are > there. > Unless there was a specific reason to remove it, I suggest adding it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-2342) Document ids are not url encoded correctly
Garren Smith created COUCHDB-2342: - Summary: Document ids are not url encoded correctly Key: COUCHDB-2342 URL: https://issues.apache.org/jira/browse/COUCHDB-2342 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith * Go to databases / my databases / new document * set the _id to "design%20foo" * click save * note that the _id has changed to "design foo". Expectation is that the _id would be preserved as it is round-tripped to Couchdb (e.g. URL encoded to design%2520foo where needed). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-2341) Cannot create "id" field
Garren Smith created COUCHDB-2341: - Summary: Cannot create "id" field Key: COUCHDB-2341 URL: https://issues.apache.org/jira/browse/COUCHDB-2341 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith Fauxton stops a user from creating a "id" field. This was an attempt to be helpful but its not effective and will confuse the user. We need to remove that check and allow a user to create an id field. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (COUCHDB-2332) Missing api bar
Garren Smith created COUCHDB-2332: - Summary: Missing api bar Key: COUCHDB-2332 URL: https://issues.apache.org/jira/browse/COUCHDB-2332 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith There is no api url button when editing a document. This needs to be added back. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (COUCHDB-2332) Missing api bar
[ https://issues.apache.org/jira/browse/COUCHDB-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2332: -- Skill Level: New Contributors Level (Easy) > Missing api bar > --- > > Key: COUCHDB-2332 > URL: https://issues.apache.org/jira/browse/COUCHDB-2332 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > There is no api url button when editing a document. This needs to be added > back. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (COUCHDB-2297) Create Fauxton links functionality
[ https://issues.apache.org/jira/browse/COUCHDB-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith reassigned COUCHDB-2297: - Assignee: Garren Smith > Create Fauxton links functionality > -- > > Key: COUCHDB-2297 > URL: https://issues.apache.org/jira/browse/COUCHDB-2297 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith >Assignee: Garren Smith > > Currently we hard code the urls for the app. So our templates and code is > littered with urls. This is not a great idea. I propose we create a links > object that can generate urls for us. > This would be similar to how Ruby on Rails works with its url functionality. > I think how we should do it is have a Fauxton.links object. We can then ask > it for a url e.g. Fauxton.links.allDocs(databaseName, context); it would > then return the url for the all docs page of the database. > What would also be important is to have the context argument so we can > specify if its for the web or to fetch an object. Like how we use the context > for models. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2297) Create Fauxton links functionality
[ https://issues.apache.org/jira/browse/COUCHDB-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2297: -- Skill Level: Committers Level (Medium to Hard) > Create Fauxton links functionality > -- > > Key: COUCHDB-2297 > URL: https://issues.apache.org/jira/browse/COUCHDB-2297 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > Currently we hard code the urls for the app. So our templates and code is > littered with urls. This is not a great idea. I propose we create a links > object that can generate urls for us. > This would be similar to how Ruby on Rails works with its url functionality. > I think how we should do it is have a Fauxton.links object. We can then ask > it for a url e.g. Fauxton.links.allDocs(databaseName, context); it would > then return the url for the all docs page of the database. > What would also be important is to have the context argument so we can > specify if its for the web or to fetch an object. Like how we use the context > for models. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (COUCHDB-2297) Create Fauxton links functionality
Garren Smith created COUCHDB-2297: - Summary: Create Fauxton links functionality Key: COUCHDB-2297 URL: https://issues.apache.org/jira/browse/COUCHDB-2297 Project: CouchDB Issue Type: Improvement Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith Currently we hard code the urls for the app. So our templates and code is littered with urls. This is not a great idea. I propose we create a links object that can generate urls for us. This would be similar to how Ruby on Rails works with its url functionality. I think how we should do it is have a Fauxton.links object. We can then ask it for a url e.g. Fauxton.links.allDocs(databaseName, context); it would then return the url for the all docs page of the database. What would also be important is to have the context argument so we can specify if its for the web or to fetch an object. Like how we use the context for models. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (COUCHDB-2291) Select All Docs + delete is not working.
Garren Smith created COUCHDB-2291: - Summary: Select All Docs + delete is not working. Key: COUCHDB-2291 URL: https://issues.apache.org/jira/browse/COUCHDB-2291 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith A regression. We need to fix this plus add some tests so that we can hopefully avoid this regression again. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (COUCHDB-2288) Firefox: Icons are broken
[ https://issues.apache.org/jira/browse/COUCHDB-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2288. --- Resolution: Fixed Assignee: Garren Smith > Firefox: Icons are broken > - > > Key: COUCHDB-2288 > URL: https://issues.apache.org/jira/browse/COUCHDB-2288 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Robert Kowalski >Assignee: Garren Smith > > The icons are broken on Firefox, e.g. in the Sidebar -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2285) Improve document sidebar test coverage
[ https://issues.apache.org/jira/browse/COUCHDB-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2285: -- Skill Level: Regular Contributors Level (Easy to Medium) > Improve document sidebar test coverage > -- > > Key: COUCHDB-2285 > URL: https://issues.apache.org/jira/browse/COUCHDB-2285 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > We need to improve the test coverage of the sidebar views. This is a ticket > to track that progress. For reference this is the file > [https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-sidebar.js] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2282) Create tests for Documents changes
[ https://issues.apache.org/jira/browse/COUCHDB-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2282: -- Skill Level: Regular Contributors Level (Easy to Medium) > Create tests for Documents changes > -- > > Key: COUCHDB-2282 > URL: https://issues.apache.org/jira/browse/COUCHDB-2282 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > We need to improve the test coverage of the changes views. This is a ticket > to track that progress. For reference this is the file: > [https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2283) Improve test coverage for documents doc editor
[ https://issues.apache.org/jira/browse/COUCHDB-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2283: -- Skill Level: Regular Contributors Level (Easy to Medium) > Improve test coverage for documents doc editor > -- > > Key: COUCHDB-2283 > URL: https://issues.apache.org/jira/browse/COUCHDB-2283 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > We need to improve the test coverage of the changes views. This is a ticket > to track that progress. For reference this is the file: > [https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-doceditor.js] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2284) Improve test coverage of Document index views
[ https://issues.apache.org/jira/browse/COUCHDB-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2284: -- Skill Level: Regular Contributors Level (Easy to Medium) > Improve test coverage of Document index views > - > > Key: COUCHDB-2284 > URL: https://issues.apache.org/jira/browse/COUCHDB-2284 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > We need to improve the test coverage of the indexes views. This is a ticket > to track that progress. For reference this is the > file:[https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-index.js] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2281) Create tests for Documents Advanced options
[ https://issues.apache.org/jira/browse/COUCHDB-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2281: -- Skill Level: Regular Contributors Level (Easy to Medium) > Create tests for Documents Advanced options > --- > > Key: COUCHDB-2281 > URL: https://issues.apache.org/jira/browse/COUCHDB-2281 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > We need to improve the test coverage of the advanced options views. This is a > ticket to track that progress. For reference this is the file: > [https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-advancedopts.js] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (COUCHDB-2285) Improve document sidebar test coverage
Garren Smith created COUCHDB-2285: - Summary: Improve document sidebar test coverage Key: COUCHDB-2285 URL: https://issues.apache.org/jira/browse/COUCHDB-2285 Project: CouchDB Issue Type: Improvement Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith We need to improve the test coverage of the sidebar views. This is a ticket to track that progress. For reference this is the file [https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-sidebar.js] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (COUCHDB-2284) Improve test coverage of Document index views
Garren Smith created COUCHDB-2284: - Summary: Improve test coverage of Document index views Key: COUCHDB-2284 URL: https://issues.apache.org/jira/browse/COUCHDB-2284 Project: CouchDB Issue Type: Improvement Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith We need to improve the test coverage of the indexes views. This is a ticket to track that progress. For reference this is the file:[https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-index.js] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (COUCHDB-2282) Create tests for Documents changes
Garren Smith created COUCHDB-2282: - Summary: Create tests for Documents changes Key: COUCHDB-2282 URL: https://issues.apache.org/jira/browse/COUCHDB-2282 Project: CouchDB Issue Type: Improvement Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith We need to improve the test coverage of the changes views. This is a ticket to track that progress. For reference this is the file: [https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-changes.js] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (COUCHDB-2283) Improve test coverage for documents doc editor
Garren Smith created COUCHDB-2283: - Summary: Improve test coverage for documents doc editor Key: COUCHDB-2283 URL: https://issues.apache.org/jira/browse/COUCHDB-2283 Project: CouchDB Issue Type: Improvement Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith We need to improve the test coverage of the changes views. This is a ticket to track that progress. For reference this is the file: [https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-doceditor.js] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (COUCHDB-2281) Create tests for Documents Advanced options
Garren Smith created COUCHDB-2281: - Summary: Create tests for Documents Advanced options Key: COUCHDB-2281 URL: https://issues.apache.org/jira/browse/COUCHDB-2281 Project: CouchDB Issue Type: Improvement Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith We need to improve the test coverage of the advanced options views. This is a ticket to track that progress. For reference this is the file: [https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/views-advancedopts.js] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2279) Trash can not aligned correctly
[ https://issues.apache.org/jira/browse/COUCHDB-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074177#comment-14074177 ] Garren Smith commented on COUCHDB-2279: --- The embedded link didn't seem to work so here is an image of whats wrong [https://www.dropbox.com/s/clmzpawsz6w2t2d/Screenshot%202014-07-25%2009.39.40.png] > Trash can not aligned correctly > --- > > Key: COUCHDB-2279 > URL: https://issues.apache.org/jira/browse/COUCHDB-2279 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > The trash can button on the edit document page is not aligned correctly. See > image: > !https://www.dropbox.com/s/clmzpawsz6w2t2d/Screenshot%202014-07-25%2009.39.40.png! -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2279) Trash can not aligned correctly
[ https://issues.apache.org/jira/browse/COUCHDB-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2279: -- Skill Level: New Contributors Level (Easy) > Trash can not aligned correctly > --- > > Key: COUCHDB-2279 > URL: https://issues.apache.org/jira/browse/COUCHDB-2279 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > The trash can button on the edit document page is not aligned correctly. See > image: > !https://www.dropbox.com/s/clmzpawsz6w2t2d/Screenshot%202014-07-25%2009.39.40.png! -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (COUCHDB-2279) Trash can not aligned correctly
Garren Smith created COUCHDB-2279: - Summary: Trash can not aligned correctly Key: COUCHDB-2279 URL: https://issues.apache.org/jira/browse/COUCHDB-2279 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith The trash can button on the edit document page is not aligned correctly. See image: !https://www.dropbox.com/s/clmzpawsz6w2t2d/Screenshot%202014-07-25%2009.39.40.png! -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2275) New document sidebar feedback
[ https://issues.apache.org/jira/browse/COUCHDB-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2275: -- Description: Lena was kind enough to send some feedback on the new sidebar. I really like the generally very clean and tidy design, great work! I know it's hard to make design decisions, especially when there's no widely agreed based for them. Most of it is based on the styles of CouchDB's website, as it's afaik currently the only existing base with a design that has been approved and agreed on. Thus, please just take this as input and thoughts from my side. # Typography #* looks good to me # central area - readability #* current colours are code in red / black on beige background, alternative idea would be to choose a white background in terms of readability # Colours as in https://github.com/apache/couchdb-fauxton/blob/master/assets/less/couchdb.less – #* @linkcolor: is #CA2530 in the CSS, is #ff on the website + in CouchDB's logo #* @red: is #9d261d in the CSS, is #ff on the website + in CouchDB's logo (which then also automatically affects @redButton and @linkColor in https://github.com/apache/couchdb-fauxton/blob/master/assets/less/variables.less ) Colours as in https://github.com/apache/couchdb-fauxton/blob/master/assets/less/variables.less #* @darkred is #AF2D24 here, is #a70012 in the logo # leftmost sidebar / menu with icons #* general note: the contrast of the dark grey icons (#2c2120 in my screenshot) and their background (#443c3b) is pretty low – maybe go for a bit lighter grey for the background here? # left sidebar #* interaction popup box in left sidebar (showing when user clicks "+" icon): the contrast of "add new" text and the dark background is also pretty low – maybe choose a lighter grey (maybe even the one which is currently used for "Secondary View" text in the screenshot)? #* the red of the "plus" icon: ideally, it would also be #ff was: Lena was kind enough to send some feedback on the new sidebar. I really like the generally very clean and tidy design, great work! I know it's hard to make design decisions, especially when there's no widely agreed based for them. Most of it is based on the styles of CouchDB's website, as it's afaik currently the only existing base with a design that has been approved and agreed on. Thus, please just take this as input and thoughts from my side. # Typography - looks good to me # central area - readability - current colours are code in red / black on beige background, alternative idea would be to choose a white background in terms of readability # Colours as in https://github.com/apache/couchdb-fauxton/blob/master/assets/less/couchdb.less – - @linkcolor: is #CA2530 in the CSS, is #ff on the website + in CouchDB's logo - @red: is #9d261d in the CSS, is #ff on the website + in CouchDB's logo (which then also automatically affects @redButton and @linkColor in https://github.com/apache/couchdb-fauxton/blob/master/assets/less/variables.less ) Colours as in https://github.com/apache/couchdb-fauxton/blob/master/assets/less/variables.less - @darkred is #AF2D24 here, is #a70012 in the logo # leftmost sidebar / menu with icons - general note: the contrast of the dark grey icons (#2c2120 in my screenshot) and their background (#443c3b) is pretty low – maybe go for a bit lighter grey for the background here? # left sidebar - interaction popup box in left sidebar (showing when user clicks "+" icon): the contrast of "add new" text and the dark background is also pretty low – maybe choose a lighter grey (maybe even the one which is currently used for "Secondary View" text in the screenshot)? - the red of the "plus" icon: ideally, it would also be #ff > New document sidebar feedback > - > > Key: COUCHDB-2275 > URL: https://issues.apache.org/jira/browse/COUCHDB-2275 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > Lena was kind enough to send some feedback on the new sidebar. > I really like the generally very clean and tidy design, great work! I know > it's hard to make design decisions, especially when there's no widely agreed > based for them. Most of it is based on the styles of CouchDB's website, as > it's afaik currently the only existing base with a design that has been > approved and agreed on. Thus, please just take this as input and thoughts > from my side. > # Typography > #* looks good to me > # central area - readability > #* current colours are code in red / black on beige background, alternative > idea would be to choose a white background in terms of readability > # Colours > as in > https://github.com/apache/couchdb-fauxton/blob/master/assets/less/couchdb.less > – > #* @linkcolor
[jira] [Created] (COUCHDB-2275) New document sidebar feedback
Garren Smith created COUCHDB-2275: - Summary: New document sidebar feedback Key: COUCHDB-2275 URL: https://issues.apache.org/jira/browse/COUCHDB-2275 Project: CouchDB Issue Type: Improvement Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith Lena was kind enough to send some feedback on the new sidebar. I really like the generally very clean and tidy design, great work! I know it's hard to make design decisions, especially when there's no widely agreed based for them. Most of it is based on the styles of CouchDB's website, as it's afaik currently the only existing base with a design that has been approved and agreed on. Thus, please just take this as input and thoughts from my side. # Typography - looks good to me # central area - readability - current colours are code in red / black on beige background, alternative idea would be to choose a white background in terms of readability # Colours as in https://github.com/apache/couchdb-fauxton/blob/master/assets/less/couchdb.less – - @linkcolor: is #CA2530 in the CSS, is #ff on the website + in CouchDB's logo - @red: is #9d261d in the CSS, is #ff on the website + in CouchDB's logo (which then also automatically affects @redButton and @linkColor in https://github.com/apache/couchdb-fauxton/blob/master/assets/less/variables.less ) Colours as in https://github.com/apache/couchdb-fauxton/blob/master/assets/less/variables.less - @darkred is #AF2D24 here, is #a70012 in the logo # leftmost sidebar / menu with icons - general note: the contrast of the dark grey icons (#2c2120 in my screenshot) and their background (#443c3b) is pretty low – maybe go for a bit lighter grey for the background here? # left sidebar - interaction popup box in left sidebar (showing when user clicks "+" icon): the contrast of "add new" text and the dark background is also pretty low – maybe choose a lighter grey (maybe even the one which is currently used for "Secondary View" text in the screenshot)? - the red of the "plus" icon: ideally, it would also be #ff -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2160) Fields-view for documents
[ https://issues.apache.org/jira/browse/COUCHDB-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033779#comment-14033779 ] Garren Smith commented on COUCHDB-2160: --- Hi Sebastian, This is a cool idea. If you are happy to implement, go for it. Cheers Garren > Fields-view for documents > - > > Key: COUCHDB-2160 > URL: https://issues.apache.org/jira/browse/COUCHDB-2160 > Project: CouchDB > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin > Attachments: edittext_screen.png > > > Futon provides two representation of documents: raw JSON and, how I called > it, fields-view where document is represented in nicer k-v table form. This > representation is very user friendly, since you don't have to care about JSON > syntax - you don't even have to know about it. You just double clicks on > value, enters something and Futon guesses right type for the input. No > commas, no quotes, no brackets, just keys and values. > Currently, Fauxton has no such view providing documents representation only > as raw JSON (thought it has very rich editor for it). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (COUCHDB-2210) Update D3.js
[ https://issues.apache.org/jira/browse/COUCHDB-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2210. --- Resolution: Fixed > Update D3.js > > > Key: COUCHDB-2210 > URL: https://issues.apache.org/jira/browse/COUCHDB-2210 > Project: CouchDB > Issue Type: Task > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Sue Lockwood > > Update D3.js so new features can be used in data monitoring work -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (COUCHDB-2036) Redirect logged in user back to access denied page
[ https://issues.apache.org/jira/browse/COUCHDB-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2036. --- Resolution: Fixed > Redirect logged in user back to access denied page > -- > > Key: COUCHDB-2036 > URL: https://issues.apache.org/jira/browse/COUCHDB-2036 > Project: CouchDB > Issue Type: New Feature > Components: Fauxton >Reporter: Garren Smith >Assignee: Garren Smith > > When navigating restricted fauxton pages and a user is not logged in. The > user will get an access denied screen. Once a user has logged in they should > be redirected back to the page so that they can continue working. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2222) Design document name doesn't show on active tasks
[ https://issues.apache.org/jira/browse/COUCHDB-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13970512#comment-13970512 ] Garren Smith commented on COUCHDB-: --- Thanks [~dedalozzo] thats very helpful. We will take a look and fix that. Unless you would be interested in submitting a PR for this. I would be happy to help you through it? Also look for robertkowalski or deathbear on IRC to help you. Otherwise email the dev@ mailing list. > Design document name doesn't show on active tasks > - > > Key: COUCHDB- > URL: https://issues.apache.org/jira/browse/COUCHDB- > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Filippo Fadda > Attachments: couch.jpg > > > On the active tasks list, the name of the design document should appear under > any indexing task in the Objects column, like in Futon. Actually when there > are many simultaneously indexing tasks, you can't figure out which design > document they are related. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2222) Design document name doesn't show on active tasks
[ https://issues.apache.org/jira/browse/COUCHDB-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-: -- Skill Level: New Contributors Level (Easy) Thanks for reporting this Filippo, this is a good idea. Could you submit a screenshot of what you are currently seeing so that anyone who works on this has a good idea what you are suggesting. > Design document name doesn't show on active tasks > - > > Key: COUCHDB- > URL: https://issues.apache.org/jira/browse/COUCHDB- > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Filippo Fadda > > On the active tasks list, the name of the design document should appear under > any indexing task in the Objects column, like in Futon. Actually when there > are many simultaneously indexing tasks, you can't figure out which design > document they are related. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (COUCHDB-2213) Improve stats page
[ https://issues.apache.org/jira/browse/COUCHDB-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-2213. - Resolution: Duplicate Deplicate of COUCHDB-2138 > Improve stats page > -- > > Key: COUCHDB-2213 > URL: https://issues.apache.org/jira/browse/COUCHDB-2213 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > The stats page is very basic. I think we could do a lot more with the stats > we get from couchdb. We could also look at storing the stats for a short set > of time and graphing more time series info. > We also need to remove nv.d3.js. nv.d3.js is a bit tricky to work with > because their documentation is quite poor. It would be better to just build > the graphs using straight d3.js -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (COUCHDB-2213) Improve stats page
Garren Smith created COUCHDB-2213: - Summary: Improve stats page Key: COUCHDB-2213 URL: https://issues.apache.org/jira/browse/COUCHDB-2213 Project: CouchDB Issue Type: Improvement Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith The stats page is very basic. I think we could do a lot more with the stats we get from couchdb. We could also look at storing the stats for a short set of time and graphing more time series info. We also need to remove nv.d3.js. nv.d3.js is a bit tricky to work with because their documentation is quite poor. It would be better to just build the graphs using straight d3.js -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2175) Metadata isn't available for new ddocs
[ https://issues.apache.org/jira/browse/COUCHDB-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949010#comment-13949010 ] Garren Smith commented on COUCHDB-2175: --- I don't actually understand this ticket. Why is it about? > Metadata isn't available for new ddocs > -- > > Key: COUCHDB-2175 > URL: https://issues.apache.org/jira/browse/COUCHDB-2175 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin > Labels: beginners > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (COUCHDB-2209) No Access to return to page
[ https://issues.apache.org/jira/browse/COUCHDB-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2209. --- Resolution: Fixed > No Access to return to page > --- > > Key: COUCHDB-2209 > URL: https://issues.apache.org/jira/browse/COUCHDB-2209 > Project: CouchDB > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith >Assignee: Garren Smith > > If a user tries to access a page and they are not logged in. They are then > required to login and are then navigated to _all_docs. Instead we should > navigate them to the page they originally were on. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2209) No Access to return to page
[ https://issues.apache.org/jira/browse/COUCHDB-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946705#comment-13946705 ] Garren Smith commented on COUCHDB-2209: --- [~kxepal] That is for when someone hasn't logged in. This is for when someone logs in they can then get redirected to the page they were not allowed to view. > No Access to return to page > --- > > Key: COUCHDB-2209 > URL: https://issues.apache.org/jira/browse/COUCHDB-2209 > Project: CouchDB > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith >Assignee: Garren Smith > > If a user tries to access a page and they are not logged in. They are then > required to login and are then navigated to _all_docs. Instead we should > navigate them to the page they originally were on. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (COUCHDB-2209) No Access to return to page
[ https://issues.apache.org/jira/browse/COUCHDB-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith reassigned COUCHDB-2209: - Assignee: Garren Smith > No Access to return to page > --- > > Key: COUCHDB-2209 > URL: https://issues.apache.org/jira/browse/COUCHDB-2209 > Project: CouchDB > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith >Assignee: Garren Smith > > If a user tries to access a page and they are not logged in. They are then > required to login and are then navigated to _all_docs. Instead we should > navigate them to the page they originally were on. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (COUCHDB-2209) No Access to return to page
Garren Smith created COUCHDB-2209: - Summary: No Access to return to page Key: COUCHDB-2209 URL: https://issues.apache.org/jira/browse/COUCHDB-2209 Project: CouchDB Issue Type: New Feature Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith If a user tries to access a page and they are not logged in. They are then required to login and are then navigated to _all_docs. Instead we should navigate them to the page they originally were on. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (COUCHDB-2116) Fauxton cache is too persistent
[ https://issues.apache.org/jira/browse/COUCHDB-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2116. --- Resolution: Fixed > Fauxton cache is too persistent > --- > > Key: COUCHDB-2116 > URL: https://issues.apache.org/jira/browse/COUCHDB-2116 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin >Assignee: Garren Smith > > 1. Have a server with Admin Party > 2. Open two tabs with Futon and Fauxton > 3. Fix admin party in Futon > 4. Navigate thought pages on Fauxton - Admin Party is still there > 5. Try to refresh Fauxton tab - still Admin party > 6. Close Fauxton tab and open it again - finally fixed! > 7. Logout and login on Futon - Fauxton still thinks that you're anonymous > 8. Ok, let's login on Fauxton too. And remove all admins from config > 9. Refresh Futon - Admin Party there! Ok. Refresh Fauxton - you're still > logged in. > Ok, let's try the opposite: logout on Futon, login on Fauxton, refresh Futon > - you're logged in without any issues. > UPDATE. Another case: > 1. Navigate to databases list page > 2. Create new database > 3. Go back (no matter how: via browser history, by click on sidebar link) > 4. You'll miss that database in the list > Same is true if you delete database - nothing changes in the list even if you > change the view page, refresh the tab or open the new one. > However, after ~one minute Fauxton will show the changes. I believe that both > cases are happens because of local state caching which doesn't reacts on > changes that current user made. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (COUCHDB-2110) Highlight graveyards in database list
[ https://issues.apache.org/jira/browse/COUCHDB-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2110. --- Resolution: Fixed > Highlight graveyards in database list > - > > Key: COUCHDB-2110 > URL: https://issues.apache.org/jira/browse/COUCHDB-2110 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin > Labels: intermediate > > Let Fauxton detect graveyards - databases where amount of deleted documents > more than existed ones. Not much useful for small databases, but helpful for > large ones. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (COUCHDB-2201) New View creation errors
[ https://issues.apache.org/jira/browse/COUCHDB-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2201. --- Resolution: Fixed > New View creation errors > > > Key: COUCHDB-2201 > URL: https://issues.apache.org/jira/browse/COUCHDB-2201 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Garren Smith > > Creating a view fails because of of two issues: > * design doc info is created and rendered > * it expects the routeObject to have a list of results -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2116) Fauxton cache is too persistent
[ https://issues.apache.org/jira/browse/COUCHDB-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933391#comment-13933391 ] Garren Smith commented on COUCHDB-2116: --- We are going to remove caching. It looks like it causes more issues then fixes. > Fauxton cache is too persistent > --- > > Key: COUCHDB-2116 > URL: https://issues.apache.org/jira/browse/COUCHDB-2116 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin >Assignee: Garren Smith > > 1. Have a server with Admin Party > 2. Open two tabs with Futon and Fauxton > 3. Fix admin party in Futon > 4. Navigate thought pages on Fauxton - Admin Party is still there > 5. Try to refresh Fauxton tab - still Admin party > 6. Close Fauxton tab and open it again - finally fixed! > 7. Logout and login on Futon - Fauxton still thinks that you're anonymous > 8. Ok, let's login on Fauxton too. And remove all admins from config > 9. Refresh Futon - Admin Party there! Ok. Refresh Fauxton - you're still > logged in. > Ok, let's try the opposite: logout on Futon, login on Fauxton, refresh Futon > - you're logged in without any issues. > UPDATE. Another case: > 1. Navigate to databases list page > 2. Create new database > 3. Go back (no matter how: via browser history, by click on sidebar link) > 4. You'll miss that database in the list > Same is true if you delete database - nothing changes in the list even if you > change the view page, refresh the tab or open the new one. > However, after ~one minute Fauxton will show the changes. I believe that both > cases are happens because of local state caching which doesn't reacts on > changes that current user made. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (COUCHDB-2116) Fauxton cache is too persistent
[ https://issues.apache.org/jira/browse/COUCHDB-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith reassigned COUCHDB-2116: - Assignee: Garren Smith > Fauxton cache is too persistent > --- > > Key: COUCHDB-2116 > URL: https://issues.apache.org/jira/browse/COUCHDB-2116 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin >Assignee: Garren Smith > > 1. Have a server with Admin Party > 2. Open two tabs with Futon and Fauxton > 3. Fix admin party in Futon > 4. Navigate thought pages on Fauxton - Admin Party is still there > 5. Try to refresh Fauxton tab - still Admin party > 6. Close Fauxton tab and open it again - finally fixed! > 7. Logout and login on Futon - Fauxton still thinks that you're anonymous > 8. Ok, let's login on Fauxton too. And remove all admins from config > 9. Refresh Futon - Admin Party there! Ok. Refresh Fauxton - you're still > logged in. > Ok, let's try the opposite: logout on Futon, login on Fauxton, refresh Futon > - you're logged in without any issues. > UPDATE. Another case: > 1. Navigate to databases list page > 2. Create new database > 3. Go back (no matter how: via browser history, by click on sidebar link) > 4. You'll miss that database in the list > Same is true if you delete database - nothing changes in the list even if you > change the view page, refresh the tab or open the new one. > However, after ~one minute Fauxton will show the changes. I believe that both > cases are happens because of local state caching which doesn't reacts on > changes that current user made. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (COUCHDB-2201) New View creation errors
Garren Smith created COUCHDB-2201: - Summary: New View creation errors Key: COUCHDB-2201 URL: https://issues.apache.org/jira/browse/COUCHDB-2201 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith Creating a view fails because of of two issues: * design doc info is created and rendered * it expects the routeObject to have a list of results -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-1879) Interactive UI editor for filters/update handlers/etc
[ https://issues.apache.org/jira/browse/COUCHDB-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930910#comment-13930910 ] Garren Smith commented on COUCHDB-1879: --- We have broken this issue out into smaller ones. > Interactive UI editor for filters/update handlers/etc > - > > Key: COUCHDB-1879 > URL: https://issues.apache.org/jira/browse/COUCHDB-1879 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Russell Branca > Labels: advanced > > As it stands now filter functions and update handlers and other non view > javascript functions are a challenge to debug. > Let's simplify that and build in a client side editor that does an in browser > preview of the functions across a sampling of the database, as we now do with > views. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (COUCHDB-1879) Interactive UI editor for filters/update handlers/etc
[ https://issues.apache.org/jira/browse/COUCHDB-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-1879. - Resolution: Fixed > Interactive UI editor for filters/update handlers/etc > - > > Key: COUCHDB-1879 > URL: https://issues.apache.org/jira/browse/COUCHDB-1879 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Russell Branca > Labels: advanced > > As it stands now filter functions and update handlers and other non view > javascript functions are a challenge to debug. > Let's simplify that and build in a client side editor that does an in browser > preview of the functions across a sampling of the database, as we now do with > views. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-1913) Upload multiple attachments
[ https://issues.apache.org/jira/browse/COUCHDB-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-1913: -- Skill Level: Regular Contributors Level (Easy to Medium) > Upload multiple attachments > --- > > Key: COUCHDB-1913 > URL: https://issues.apache.org/jira/browse/COUCHDB-1913 > Project: CouchDB > Issue Type: Improvement > Components: Fauxton >Reporter: Alexander Shorin > > Currently, it's only possible for Fauxton to upload only one attachment at > once (due to using Attachments API), but CouchDB allows to [upload multiple > attachments| > http://docs.couchdb.org/en/latest/api/document/common.html#creating-multiple-attachments] > with single document update. > For good old Futon, the [next example | > https://gist.github.com/rjsteinert/4074427] shows the solution. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-1919) Database first view load is veeeery long, browser times out
[ https://issues.apache.org/jira/browse/COUCHDB-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-1919: -- Skill Level: Committers Level (Medium to Hard) > Database first view load is vry long, browser times out > --- > > Key: COUCHDB-1919 > URL: https://issues.apache.org/jira/browse/COUCHDB-1919 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Mark Deibert > > When I click my database, the first view Fauxton tries to load takes a very > long time. So long that Chrome shows the frozen/timeout error at least twice. > My guess is because the view it's trying to load is for "Photo" type > documents and each photo document has a fairly large image attachments. > At the moment I have only 15 or so photos with attachments. If there were > hundreds or thousands, this first view would never, ever load! When I choose > another database, that has no attachments, the first view loads just fine. > One last note: "Fauxton" UI is gorgeous! Standing O for the Fauxton designer > :-) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-1920) Fauxton vertical scroll handles covered by UI
[ https://issues.apache.org/jira/browse/COUCHDB-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-1920: -- Skill Level: Regular Contributors Level (Easy to Medium) > Fauxton vertical scroll handles covered by UI > - > > Key: COUCHDB-1920 > URL: https://issues.apache.org/jira/browse/COUCHDB-1920 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Mark Deibert >Priority: Minor > > The vertical scroll bar handles at both the top and bottom of the Fauxton UI > are covered by other UI elements and cannot be grabbed with the mouse. This > happens in the latest versions of both Chrome and Firefox. > Here is a screen cap... > !http://i.imgur.com/KQfQrOt.png! -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (COUCHDB-1937) Fauxton doesn't play nice thru a reverse proxy at a non-root path
[ https://issues.apache.org/jira/browse/COUCHDB-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-1937. --- Resolution: Fixed > Fauxton doesn't play nice thru a reverse proxy at a non-root path > - > > Key: COUCHDB-1937 > URL: https://issues.apache.org/jira/browse/COUCHDB-1937 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Will Perry >Assignee: Garren Smith > > If Fauxton is exposed thru a non-root path by a reverse proxy, it doesn't > work. > For example, we host fauxton at > www.somewhere/admin/futon/10.114.136.18-2/_utils/fauxton/ > ... and it attempts to issue a GET from: > www.somewhere/_session > which in our case results in HTTP 401 (unauthorized) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-1965) docco docs
[ https://issues.apache.org/jira/browse/COUCHDB-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-1965: -- Skill Level: Committers Level (Medium to Hard) > docco docs > -- > > Key: COUCHDB-1965 > URL: https://issues.apache.org/jira/browse/COUCHDB-1965 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Noah Slater > > Taken from the Fauxton TODO file. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-1960) Provide pagination for /_all_dbs
[
https://issues.apache.org/jira/browse/COUCHDB-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garren Smith updated COUCHDB-1960:
--
Skill Level: Regular Contributors Level (Easy to Medium)
> Provide pagination for /_all_dbs
>
>
> Key: COUCHDB-1960
> URL: https://issues.apache.org/jira/browse/COUCHDB-1960
> Project: CouchDB
> Issue Type: Improvement
> Components: Fauxton, HTTP Interface
>Reporter: Benjamin Young
>
> The database-per-user design pattern has increased in popularity and
> consequently causes long lists of databases when one hits {{/_all_dbs}}
> To keep this sane, we need some pagination.
> {{?skip=10&limit=10}} style seems to be the simplest to implement (and there
> should be existing code from Cloudant for this one).
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (COUCHDB-2136) Group log messages by date
[
https://issues.apache.org/jira/browse/COUCHDB-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garren Smith updated COUCHDB-2136:
--
Skill Level: Regular Contributors Level (Easy to Medium)
> Group log messages by date
> --
>
> Key: COUCHDB-2136
> URL: https://issues.apache.org/jira/browse/COUCHDB-2136
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Fauxton
>Reporter: Alexander Shorin
>
> Another idea how to get more free space for log message is grouping by
> datetime. You'll rarely notice changes in date part while be reading the
> logs, so it is possible to extract this common part as group header like:
> {code}
> [2010-02-13]
> ==
> [02:31:30] [<0.6327.1>] httpd 401 error response:
> {"error":"unauthorized","reason":"Name or password is incorrect."}
> [02:31:29] [<0.6258.1>] 'GET' /_log {1,1} from "127.0.0.1"
> Headers:
> [{'Accept',"text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8"},
> {'Accept-Encoding',"gzip, deflate"},
> {'Accept-Language',"en-US,en;q=0.5"},
> {'Connection',"keep-alive"},
> {'Cookie',"AuthSession="},
> {'Host',"localhost:5984"}]
> --
> [02:31:29] [<0.6258.1>] 'GET' /_log {1,1} from "127.0.0.1"
> Headers:
> [{'Accept',"text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8"},
> {'Accept-Encoding',"gzip, deflate"},
> {'Accept-Language',"en-US,en;q=0.5"},
> {'Connection',"keep-alive"},
> {'Cookie',"AuthSession="},
> {'Host',"localhost:5984"}]
> {code}
> More free space for log message!
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (COUCHDB-2009) Issue with Ace Editor losing arrow key functionality
[ https://issues.apache.org/jira/browse/COUCHDB-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2009: -- Skill Level: Dont Know > Issue with Ace Editor losing arrow key functionality > > > Key: COUCHDB-2009 > URL: https://issues.apache.org/jira/browse/COUCHDB-2009 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Sue Lockwood > > reported by cvi__ on IRC > The code-editor ended up in a state where i couldn't use my arrow-keys to > move around the text. > It instead scrolled the code-window. I tried to close down the browser > completely, which didn't help. > Restarting Couch did help however. > Browser: Chrome: Version 31.0.1650.57 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2014) Fauxton requires full admin rights to access secondary indexes
[ https://issues.apache.org/jira/browse/COUCHDB-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2014: -- Skill Level: Committers Level (Medium to Hard) > Fauxton requires full admin rights to access secondary indexes > -- > > Key: COUCHDB-2014 > URL: https://issues.apache.org/jira/browse/COUCHDB-2014 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Hans J Schroeder >Assignee: Benjamin Young > > Fauxton requires full admin rights to access secondary indexes where db admin > right should be enough. > Step to reproduce: > In futon everything works as expected: > 1. As admin create a database "aaa" > 2. Set security to admin: ["usera"] and member: ["usera"] > 3. Create a view "all/by_id" > 4. Log in as "usera" and open the view "all/by_id" > In fauxton: > 1. Login as "usera" > 2. Open the database "aaa" > 3. Click on the secondary index "all/by_id" -> This leads to no access and > opens the login page. > I guess it has something to do with routeroles being to strict. The "no > access" is generated client-side. > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (COUCHDB-2036) Redirect logged in user back to access denied page
[ https://issues.apache.org/jira/browse/COUCHDB-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith reassigned COUCHDB-2036: - Assignee: Garren Smith > Redirect logged in user back to access denied page > -- > > Key: COUCHDB-2036 > URL: https://issues.apache.org/jira/browse/COUCHDB-2036 > Project: CouchDB > Issue Type: New Feature > Components: Fauxton >Reporter: Garren Smith >Assignee: Garren Smith > > When navigating restricted fauxton pages and a user is not logged in. The > user will get an access denied screen. Once a user has logged in they should > be redirected back to the page so that they can continue working. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2046) Add Filter UI to Fauxton
[ https://issues.apache.org/jira/browse/COUCHDB-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2046: -- Skill Level: Committers Level (Medium to Hard) > Add Filter UI to Fauxton > > > Key: COUCHDB-2046 > URL: https://issues.apache.org/jira/browse/COUCHDB-2046 > Project: CouchDB > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Sue Lockwood > > Documentation > http://docs.couchdb.org/en/latest/couchapp/ddocs.html#filter-functions > Like Views, we need a UI around filters -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2048) Create UI for List functions
[ https://issues.apache.org/jira/browse/COUCHDB-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2048: -- Skill Level: Committers Level (Medium to Hard) > Create UI for List functions > > > Key: COUCHDB-2048 > URL: https://issues.apache.org/jira/browse/COUCHDB-2048 > Project: CouchDB > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Sue Lockwood > > Create a UI around adding list functions to a design doc > http://docs.couchdb.org/en/latest/couchapp/ddocs.html#list-functions > similar to Views -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2036) Redirect logged in user back to access denied page
[ https://issues.apache.org/jira/browse/COUCHDB-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2036: -- Skill Level: Regular Contributors Level (Easy to Medium) > Redirect logged in user back to access denied page > -- > > Key: COUCHDB-2036 > URL: https://issues.apache.org/jira/browse/COUCHDB-2036 > Project: CouchDB > Issue Type: New Feature > Components: Fauxton >Reporter: Garren Smith > > When navigating restricted fauxton pages and a user is not logged in. The > user will get an access denied screen. Once a user has logged in they should > be redirected back to the page so that they can continue working. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2062) Write documentation on how to create an addon
[ https://issues.apache.org/jira/browse/COUCHDB-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2062: -- Skill Level: Committers Level (Medium to Hard) > Write documentation on how to create an addon > - > > Key: COUCHDB-2062 > URL: https://issues.apache.org/jira/browse/COUCHDB-2062 > Project: CouchDB > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Documentation, Fauxton >Reporter: Garren Smith >Assignee: Benjamin Young > > Currently we have a very basic introduction to addons and how Fauxton. We > need better documentation on how Fauxton works and how to create an addon, > add styling etc. > We can use > https://github.com/apache/couchdb/blob/master/src/fauxton/writing_addons.md > and the https://github.com/apache/couchdb/blob/master/src/fauxton/readme.md > as starting points. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2044) Plugin to Review and Resolve Conflicts
[ https://issues.apache.org/jira/browse/COUCHDB-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2044: -- Skill Level: Regular Contributors Level (Easy to Medium) > Plugin to Review and Resolve Conflicts > -- > > Key: COUCHDB-2044 > URL: https://issues.apache.org/jira/browse/COUCHDB-2044 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton, Plugins >Reporter: Maximilian Alexander Thayer > > Hey gang! First issue :O > As a developer, I want a way to visually review and by-hand resolve conflicts > as they appear. > I'm plotting to build an app to do that as a Fauxton plugin for reviewing and > resolving document conflicts. > Documenting that intention here, at the behest of Simon Metson. If you've > done any work on anything like this, let me know, yeah? Thanks! -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2130) Search over configuration option names/values
[ https://issues.apache.org/jira/browse/COUCHDB-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2130: -- Assignee: Sue Lockwood > Search over configuration option names/values > - > > Key: COUCHDB-2130 > URL: https://issues.apache.org/jira/browse/COUCHDB-2130 > Project: CouchDB > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin >Assignee: Sue Lockwood > > This would be extremely helpful, especially if you forgot full option name or > looking for some specific value and don't know where it could be. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2131) Provide links to documentation for config options
[ https://issues.apache.org/jira/browse/COUCHDB-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2131: -- Assignee: Sue Lockwood > Provide links to documentation for config options > - > > Key: COUCHDB-2131 > URL: https://issues.apache.org/jira/browse/COUCHDB-2131 > Project: CouchDB > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin >Assignee: Sue Lockwood > > Do you remember what all these options actually does? And which values they > actually accepts? And what options CouchDB can handle? > Like API URL, but for config sections/options. May be make their names > clickable for that? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2129) Edit configuration option name
[ https://issues.apache.org/jira/browse/COUCHDB-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2129: -- Skill Level: Regular Contributors Level (Easy to Medium) > Edit configuration option name > -- > > Key: COUCHDB-2129 > URL: https://issues.apache.org/jira/browse/COUCHDB-2129 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin >Assignee: Sue Lockwood > > Have you ever made a typo there? That's a doubtful feature since there is no > atomic operation for config option rename in CouchDB. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2131) Provide links to documentation for config options
[ https://issues.apache.org/jira/browse/COUCHDB-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2131: -- Skill Level: New Contributors Level (Easy) > Provide links to documentation for config options > - > > Key: COUCHDB-2131 > URL: https://issues.apache.org/jira/browse/COUCHDB-2131 > Project: CouchDB > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin >Assignee: Sue Lockwood > > Do you remember what all these options actually does? And which values they > actually accepts? And what options CouchDB can handle? > Like API URL, but for config sections/options. May be make their names > clickable for that? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2128) Autocomplete section name
[ https://issues.apache.org/jira/browse/COUCHDB-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2128: -- Skill Level: Regular Contributors Level (Easy to Medium) > Autocomplete section name > - > > Key: COUCHDB-2128 > URL: https://issues.apache.org/jira/browse/COUCHDB-2128 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin >Assignee: Sue Lockwood > > Common use case is addition of new options to the existed sections, not > creating new ones. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2132) Optimize configuration options list
[
https://issues.apache.org/jira/browse/COUCHDB-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garren Smith updated COUCHDB-2132:
--
Assignee: Sue Lockwood
> Optimize configuration options list
> ---
>
> Key: COUCHDB-2132
> URL: https://issues.apache.org/jira/browse/COUCHDB-2132
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Fauxton
>Reporter: Alexander Shorin
>Assignee: Sue Lockwood
>
> Config section names are consume a lot of visible space. Instead of having 3
> columns in the list, probably better to make like:
> {code}
> +-+
> | section1|
> +-+---+
> | option1 | value |
> +-+---+
> | option2 | value |
> +-+---+
> | section2|
> +-+---+
> | option3 | value |
> +-+---+
> | option4 | value |
> +-+---+
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (COUCHDB-2130) Search over configuration option names/values
[ https://issues.apache.org/jira/browse/COUCHDB-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2130: -- Skill Level: Regular Contributors Level (Easy to Medium) > Search over configuration option names/values > - > > Key: COUCHDB-2130 > URL: https://issues.apache.org/jira/browse/COUCHDB-2130 > Project: CouchDB > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin >Assignee: Sue Lockwood > > This would be extremely helpful, especially if you forgot full option name or > looking for some specific value and don't know where it could be. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2132) Optimize configuration options list
[
https://issues.apache.org/jira/browse/COUCHDB-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garren Smith updated COUCHDB-2132:
--
Skill Level: New Contributors Level (Easy)
> Optimize configuration options list
> ---
>
> Key: COUCHDB-2132
> URL: https://issues.apache.org/jira/browse/COUCHDB-2132
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Fauxton
>Reporter: Alexander Shorin
>
> Config section names are consume a lot of visible space. Instead of having 3
> columns in the list, probably better to make like:
> {code}
> +-+
> | section1|
> +-+---+
> | option1 | value |
> +-+---+
> | option2 | value |
> +-+---+
> | section2|
> +-+---+
> | option3 | value |
> +-+---+
> | option4 | value |
> +-+---+
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (COUCHDB-2150) More handy view result pagination
[ https://issues.apache.org/jira/browse/COUCHDB-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930855#comment-13930855 ] Garren Smith commented on COUCHDB-2150: --- I don't understand this. In pagination in Fauxton there is a dropdown to select the number of docs per page. > More handy view result pagination > - > > Key: COUCHDB-2150 > URL: https://issues.apache.org/jira/browse/COUCHDB-2150 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin > > Futon provides pagination by 10/25/50/100 rows per page in single click. For > Fauxton you have to do some magic with query options. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2154) Scrollbar is overlapped by action bar in Chrome for views page
[ https://issues.apache.org/jira/browse/COUCHDB-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2154: -- Skill Level: Dont Know > Scrollbar is overlapped by action bar in Chrome for views page > -- > > Key: COUCHDB-2154 > URL: https://issues.apache.org/jira/browse/COUCHDB-2154 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2152) Views pagination has bad usability
[ https://issues.apache.org/jira/browse/COUCHDB-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2152: -- Skill Level: Regular Contributors Level (Easy to Medium) > Views pagination has bad usability > -- > > Key: COUCHDB-2152 > URL: https://issues.apache.org/jira/browse/COUCHDB-2152 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin >Assignee: Garren Smith > > In Futon I can move to the next page in single click without scrolling much > (only for 100 rows per page). In Fauxton I always have to scroll down to till > page end and only after I can move to the next page. Things are getting worse > if I hadn't collapse the result e.g. disable include_docs option. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2151) Show only document _id and _rev for _all_docs index
[ https://issues.apache.org/jira/browse/COUCHDB-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2151: -- Skill Level: Committers Level (Medium to Hard) This will be fixed in the new UI changes. > Show only document _id and _rev for _all_docs index > --- > > Key: COUCHDB-2151 > URL: https://issues.apache.org/jira/browse/COUCHDB-2151 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin > > In good old Futon if documents have some meaningful ID you can easily > navigate though them via pages. It's not possible to do the same with Fauxton > since it shows a lot of useless information for _all_docs index: I don't need > to see any value or key there which are duplicates information from _id and > _rev fields (also, there is no _id or _rev field in views results, only id). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2156) Changes feed page is broken
[ https://issues.apache.org/jira/browse/COUCHDB-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2156: -- Skill Level: Regular Contributors Level (Easy to Medium) > Changes feed page is broken > --- > > Key: COUCHDB-2156 > URL: https://issues.apache.org/jira/browse/COUCHDB-2156 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin > > - Changes column should represent documents in more friendly and readable way > - Document URL should respect the revision > - No scrolling at all (Chrome/Firefox) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (COUCHDB-2155) Optimize database security page
[ https://issues.apache.org/jira/browse/COUCHDB-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith updated COUCHDB-2155: -- Skill Level: Regular Contributors Level (Easy to Medium) > Optimize database security page > --- > > Key: COUCHDB-2155 > URL: https://issues.apache.org/jira/browse/COUCHDB-2155 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Fauxton >Reporter: Alexander Shorin > > - Get rid duplicated user/role inputs > - Form elements are uses too much space leaving almost nothing for the actual > content -- This message was sent by Atlassian JIRA (v6.2#6252)
