We’ve been putting a ton of work into simplifying Google Maps exports. Phase II should be ready for release within the next two weeks. Besides including a WYSIWYG-esqe editing interface, it will allow users to group, order, and better organize their map data into logical groupings (like colored markers for like-minded data).
Oh - and did we mention that geocoding will be included? You’ll no longer need to include latitude/longitude data in your reports. A geocodable address will be sufficient.
Here’s a preliminary screenshot.
Let us know what you think.
Mockup of Maps 2
Here’s the simplest type of export. We’ll take an RSS feed of our “Open” Tickets from our ticket tracking system, rename two of the data fields to “Title” and “Summary”, then spit out the results in tabular format to the screen.
http://admin.bluyah.com/export/screen/8e9c9f40cd97012b6ee4002241319b39
Feel free to bookmark the report link above if you want to keep track of open tickets. Since all Bluyah exports report in real-time, as soon as we add or remove a ticket from our tracking system the report will reflect the change.
ver 0.4.0 of the Bluyah code has been pushed to production. This releases fixes the following:
- CA-signed SSL certificate has been installed on server - so users will no longer need to manually accept our self-signed certificates when signing up - and again when logging into their custom sub-domain. [Ticket #30]
- Some more prep-work for Google Docs access [Ticket #57]
- Fixed serious flaw in login process where by users who had never activated their account were prevented from resetting their password or retrieving activation code. Additionally, if user’s email address belonged to more than one account and one of those accounts was inactive, server error would result. [Ticket # 78]
- Fixed bug in Atom/RSS connector to account for feeds that may not include the full range of allowable elements [Ticket # 49]
- Fixed template to remove some debug text from the main Connector screen (oops!) [Ticket # 71]
Small patch release to resolve some login problems, primarily associated with Tickets #70 and #73.
Core issue that has been resolved is this:
- Prior to 0.3.6 it awas assumed that there was one user per account, and that the email address for that user was system-unique.
- Post 0.3.6 we allowed the same email address to belong to more than one account.
- Doing this caused all pre-0.3.6 accounts to become inaccessible via login. We’ve resolved this.
Additionally, #70 exposed an issue with running an application across multiple servers that we didn’t consider when laying out the “signup” -> “activate” -> “login” page flow. Basically, if a user clicked on “login” first, then on “signup”, their account would get created on the wrong server, preventing authentication and login on the “correct” server . We’ve resolved this issue as well.
Let us know if there are any other issues you discover.
We’ve set up the email address beta@bluyah.com to handle incoming communications from our beloved Beta Testers.
We’ve just pushed version 0.3.8 of Bluyah out. Bug fixes and new features include:
- Fixing problem where LOGIN was routed to wrong server - resulting in some users never being able to login.
- Fixed misconfiguration of Postfix - was causing some users to not receive their account notification emails.
- Fixed error messages on unsuccessful login so they’d be more helpful (thanks Beta Testers!!)
- Account signup and login are now via SSL (you’ll need to accept our self-signed certificate for the next week)
- Account signup now recognizes selected subscription level if other than “Free” (people want paid accounts, right?)
- Links to our Twitter and Blog are now on the app and homepage.
- Admins now get notified IMMEDIATELY when users submit Feature Requests
- Fixed a bunch of layout issues specific to IE7
New updates will be coming Friday. Checkback then - or subscribe to our Twitter Feed to stay up-to-date.
We’ve just pushed version 0.3.7 of Bluyah out to the servers. This version includes enhancements to Atom/RSS feeds and introduces several new features, including:
- Exporting to Google Maps - includes auto-detecting latitude/longitude values from data source.
- Updated (ie: quicker) charting library
- Forgot “domain” redirect - useful if user belongs to more than one account.
- Combined Atom/RSS feed consumer - user no longer needs to preselect what the feed type is - we auto-detect,.
- Better handling of auto view detection in MySQL databases. We now respond gracefully if views are not found
- You can now drag columns to indicate layout when designing a Report.
- label tags on all forms fixed.
- Color Picker for selecting chart background colors (still an open bug on the application of that choice)
- Upgraded EC2 AMI - DB stored on EBS (ie: data persistence more stable)
- My Account Section exists now - including ability for user to change subscription (feature) levels
- Base framework for Google Docs access implemented (still an open bug about reading spreadsheets)
Let me know if I missed anything.
