These are the bugs and enhancements which are currently logged;
| Bug | Component | Summary | Description | Date Submitted | Found In Version | Current Status | Target Version |
| #114 | Website | My Bee: Allow users to manage their toolbar registrations etc | My Bee: Allow users to manage their toolbar registrations etc | 11-Mar-09 | New | ||
| #115 | Website | My Bee: Work out the "nearest neighbours" | Work out the "nearest neighbours" (in terms of overlap of properties viewed) which then allows people to become a "swarm", a group of local people that could share information/comments etc about the area they are interest in | 11-Mar-09 | New | ||
| #117 | Website | Help: Authoring of content | Help pages need a lot of padding out! | 11-Mar-09 | New | ||
| #122 | Backend | When a new version of toolbar is release the backend scripts need updating to allow the version access to the db | I've forgotten to do this twice in a row, so the solution is to automate the process, ie the backend queries which releases are available from Mantis? | 11-Mar-09 | New | ||
| #139 | TooLbar | Add support for aspc.co.uk | Add support for aspc.co.uk | 11-Apr-09 | 2.0.5.0 | New | |
| #157 | Backend | Some properties marked with a little man don't show any changes when viewed | From http://www.property-bee.com/forum/viewtopic.php?f=15&t=771&start=45#p3471 ClareMac; Having cleared all my little men from the Sidebar yesterday I noticed I had quite a few back today, about 20. When I checked them though, about a third of them show a price reduction etc. on 25th October as expected but the rest show nothing new e.g. the last date showing any change being April. BH reply; Just had a look (again) and think I've found something, not sure it explains every rouge little man - but it may explain some of them! One of the properties you viewed was at "2009-10-25 20:33:28" (user_properties.last_viewed in the server db) however the change you found when viewing is logged at "2009-10-25 20:33:29" (rightmove_samples_recent.sampled_on in the server db), ie a second later. Overnight the cron job runs, and generates notifications for all properties where user_properties.last_viewed is before rightmove_samples_recent.sampled_on .. which is true in this case even tho you found the change, and when you click on the property, no new change is seen. Not 100% sure of the reason, it maybe * comparing up the date/time generated by the toolbar with date/times generated by the server * that the server time is being used but ticks over from 28 seconds to 29 seconds between updating the 2 tables |
27-Oct-09 | New | ||
| #159 | TooLbar | Primelocation: Unlisted properties not marked as 'Not listed' | From speakers: I've just started using PB with prime location, after a couple of days a few of the properties on the sidebar had been removed from prime location yet were still showing as available on the sidebar. From BH: When a property listing is no longer available, the generic page http://primelocation.com/property-not-available/ [^] is displayed, which doesn't include a reference number. This causes us a problem, as we are unable to mark the relevent property as "Not listed". The only way I can see is * tracking which page is being requested (by clicking the sidebar row) and trying to associated with the actual page loaded - this is something the current design doesn't do, plus it won't work if the user browsed the property from a bookmark. * try and get the location of the page before the redirect, maybe its in the window.history? |
30-Oct-09 | 2.0.6.0 | New | 2.0.15.0 |
| #160 | TooLbar | Daft: Unlisted properties not marked as 'Not listed' | This is similar to bug #159 but for daft.ie. "When you click on what will become an unlisted property in the sidebar, daft shows a box at the top of the page and suggests similar properties. The problem for PB is that page there's no reference number in the html to identify the unlisted property, and so Pb doesn't pickup that you have tried to look at that property, so it doesn't clear the litlle man." |
30-Oct-09 | 2.0.6.0 | New | 2.0.15.0 |
| #163 | TooLbar | Formalise and improve the interface between the user interface / XPCOM component | At the moment the interface between the user interface and XPCOM component is a little haphazard/incomplete, eg * duplicate methods providing property info to the sidebar/history table * incomplete use of observer or signals&slots to keep the user interface up to date with the latest informations (whether property info or toolbar config) Formalising/improving the interface will * allow the user interface to be extended without need to constantly update the XPCom component * lead to better understanding/requirements of what the XPCOM component needs to do internally (for a future release) |
4-Nov-09 | 2.0.6.0 | New | |
| #169 | Backend | A new user registering using an existing username displays a load of html rather then "username is already in use" | If a new user tries to register with someone elses username, for some unknonw reason the error message being displayed is the html about an insert failing, rather than "Sorry the username is in use by someone else" I'd expect to see. | 14-Mar-10 | 2.0.6.1 | New | |
| #193 | TooLbar | Unable to signal slot imp_shutdown([object Event]) / TypeError: _propertyBeeService is null | Callstack; ([object Event])@chrome://property-bee/content/pb_toolbar.js:766 ([object Event])@chrome://property-bee/content/pb/signals_and_slots.js:47 ([object Event])@chrome://property-bee/content/pb/function.js:16 Seems to occur on wide range of platforms/versions; * Firefox 3.0/3.5 and 3.6 * Windows 5/6/6.1 * PPC Mac OS X 10.5 Believe the error occurrs either on exit of Firefox and/or closing a Firefox window. Unable to reproduce, so any additional information would be helpful. |
25-Feb-11 | 2.0.9.0 | Feedback | |
| #197 | TooLbar | Enhancement to export csv wizard | Enhancement to export csv wizard to a) split it into 3 layers; * a user interface * a generic task independent of user interface / storage * a storage loayer which knows how to access the local database b) export the data in a more useable format, eg one row per property with the following information; * reference / site * discovered date / price * sold price / date * withdrawn price / date * number of price changes * number of false starts (eg gone from sold back to available) * latest agents details / descriptions / price / status * location (postcode and/or latitude/longitude) The wizard will still export all properties for the time being, but in the refactoring take into consideration how only select properties could be exported. |
3-Mar-11 | 2.0.9.0 | New | 2.0.15.0 |
| #213 | TooLbar | Enhancement to check that PB's rules match the website layout so we can identify issues earlier | Not sure what form this could take, options include; 1) adding unit tests for each website rule. 2) getting the toolbar to report xpaths that are not found / regexp that failed to the server |
27-Nov-11 | 2.0.12.0 | New | 2.0.15.0 |
| #224 | TooLbar | Firefox 10 | Firefox 10 is due for release 31st January 2012 | 29-Dec-11 | 2.0.13.0 | Resolved | 2.0.15.0 |
| #225 | TooLbar | Add-on running very slow for some users | After 2.0.14.0 release, some users finding that PB is taking upto 12 seconds per page (of 10 properties). | 5-Jan-12 | 2.0.14.0 | Resolved | 2.0.15.0 |
| #226 | TooLbar | Convert "powered by property-bee.com" into a link to the site | Convert "powered by property-bee.com" into a link to the site | 5-Jan-12 | 2.0.14.0 | Resolved | 2.0.15.0 |
| #227 | TooLbar | History missing for a few daft properties | Possibiliy due to either the migration of daft ids in 2.0.14.0 or the triming of the database between christmas and new year. | 6-Jan-12 | 2.0.14.0 | New | |
| #228 | TooLbar | Display updated history before committing changes to local database | Displaying updated history before committing changes to local database may result is a very slight speed improvement in certain case (possibly only a few 100mS) | 8-Jan-12 | 2.0.14.0 | Resolved | 2.0.15.0 |
| #229 | TooLbar | Firefox 11 compatibility | Changes have been made in Firefox 11 which impact Property Bee. Mozilla have decided that all nsiHttpRequest usage must be asynchronous, which is correct if your reading a resource across a network. However this appears to be a blanket ban, which means if your reading from the local cache synchronously (as Property Bee does) your forced to change a heck of a lot of code for absolutely no gain :-( |
5-Feb-12 | 2.0.14.0 | New | |
| #230 | TooLbar | Make "Work in a bee" always on for registered users. | The "Work in a bee" option orginally existed so that users could switch off the sharing feature if the server was down for any period of time (and not get an error message on every page view). Now that the add-on has a checkbox for "Don't show this error again", I believe we can removed the "Work in a bee" option, and have the featured turned on all the time (assuming the user is registered) This also simplifies using the toolbar as; * users won't need to worry if it is "on or off" * less support questions |
6-Feb-12 | 2.0.14.0 | New | |
| #231 | TooLbar | Move "Show timings" from Options to Development menu | In most cases users aren't interested in the exact timings of the toolbar, therefore it is proposed that the feature be moved to the development menu. This will simplify the options, and stop support questions about the timing pop up appearing. In the rare cases that users are directed to measure the timings, we shall allow access to the the development menu by setting a user preference via about:config. |
6-Feb-12 | 2.0.14.0 | New |
Allows users to swap between history/price graph/related properties easily; fix for duplicate...
We think everything is working normally.