We were 'losing' our database reference every 12 hours when the ensure-auth timer went off, as we weren't always telling the user of our lib that the database ref had been changed.
Only load the jQuery file upload code when we're in the edit partial, because that's the only time we need it.
While we were updating the nano reference inside of nanoo, when reestablishing our connection and authorization, this reference wasn't being updated in database.js, resulting in authentication failures. Fixed the situation by emitting an event when we establish a new connection, and updating the reference in database.js when this happens.
Graphics Magick needs to be installed for the image resizing (during upload) to work.
Move the inline styles into the main stylesheet.
The names of the controllers used by each tab wanted to be in the main edit.html file, instead of the child files. Starting to look a lot like a route configuration.
Each tab wanted its own contoller, and each controller wanted its own file.
The contents of each tab wanted to be in their own file.
an artifact from debugging the scrollToTop behavior in Safari.
Improve performance by getting our community images and icons from the static-image database.
We were crashing when getting a session for the first time. Introduced when we fixed the session expiration issue.
Use the better-looking image uploader for the background and future sections, put some placeholders in there, and add some save buttons, removing the "real-time" saving stuff.
The list of communities wanted to be in their own tab.
Arrange the name, profile image upload, and main present text in a basic layout that's little cleaner than the ad hoc work we had before.
For the time being, just refresh our connection to Couch with every request.
Add dependency on GraphicsMagick.
Use the GraphicsMagick library to resize the community images and the icons to be the size we want. Change-Id: I62cebcb8a4713fc2b36df0759663d6b2b5246e74
Set a max width on the images uploaded by using GraphicsMagick's resize functionality. This introduces a new dependency, though it is provided by Nodejitsu. Change-Id: I4bbb862b149cddee7711b3b4ecc961ebcdcf9274
Make the UI for the main profile image upload a little cleaner, with a custom upload button and placeholder if no image has been uploaded yet.
Cut out the passions for the time being from the edit UI, as there isn't quite room for them in the current hello design. However, the idea is close to what Copper Heart is about, so do not delete the code entirely at this point.
Our sessions weren't expiring because we weren't taking into account the fact that JSON doesn't store Date objects and instead stores strings. Now we convert the saved string back into a Date when we load the session.
scrollToTop stopped working from the header; probably related to our caching efforts. Moved it to the top-level controller, which is also likely to break over time, but is an ok stop-gap for the time being.
There were extra spaces in the backers list.
Having all the nav links in a single row in the header was a bit much. Put the member-only links next to the username.
Clean up the entrance page, since we moved the template to the server. And cache our http requests.
Add a link to the entrance in the header, after initial usability testing, it was obvious that people could get stuck on the contributions page.
Hit the static database directly to get the profile image, and use httpOptions for the $http.get call.
Internet Explorer requires the size of the profile image in the navbar to be specified via an inline style.
Use Angular's http cache on the hello page. The cache prevents second requests from even hitting our server, for the duration of the user session (i.e. until the page is refreshed).
1.0.4 --> 1.0.7
The freq-choice line (once, monthly, weekly, etc) was wrapping in Mozilla. If we cut the width of each element by 0.2ex, it still looks fine in Chrome, and the line no longer wraps.
Add -moz-box-sizing to the places where we use box-sizing, to layout as desired in Firefox.
We can sometimes avoid a roundtrip to the database at /profile/:username/static-base-url by looking for static ids in the entrance config before looking in the database.
Setting up the static database requires a little bit of manual work at this point in time. Touch on the basics.
Put the name of the static database in our config instead of appending "-static" everywhere.