Donate to the B3 fund!

"even a small donation helps!"
Donate with PayPal!
Echelon v2 is not yet officially released! If you cannot get this dev-version installed, revert to version 1 as available in our download section.

Author Topic: Oops. Technical Failure.  (Read 1585 times)

Offline WickedShell

  • Moderator
  • Sr. Member
  • *
  • Posts: 201
    • GitHub - WickedShell
Oops. Technical Failure.
« on: August 01, 2011, 02:56:53 AM »
So I have apparently forked my way into an emty branch on echelon2 development, so for all updates since July 10, I have been pushing updates to no where, and was today promted about this, and I told it to switch to the version 2 branch like it was supposed to be. Well... Turns out that lost all recent changes completely.

I went through and recreated as many as I could rememeber off the top of my head and pushed them back out.

These changes include;

+ an update to the size of entries in ech_logs (not updating the database/field wont break anything, this is simply a preventive fix for people who have massive numbers of clients in they're b3 databases)

+ adding expand/collapse buttons to aliases and echelon logs on the client details page. (This helps with people who have a large number of aliases and echelon actions taken on them, as well as preserves consistency on the page)

+ force comptaability view on IE 8/9. This one works with a version of IE9 I borrowed for a day. Past that I can not vouch for it's effectiveness everywhere. I need reports on this one if it works or not.

+ fixed the reset password option failing badly, in that it works, but if a password didn't match or failed strength requirements it looked like it worked, while not actually doing anything.

Again sorry, I'm pretty sure I lost some other minro bug fixes in the mix up. I didn't expect to lose all the changes when I switched to a branch. That was a technical mix up from me not understanding git well enough.

Offline MordyT

  • Support Hero
  • Hero Member
  • *
  • Posts: 3644
  • Over $300 Donated to B3!
    • MordyT
Re: Oops. Technical Failure.
« Reply #1 on: August 01, 2011, 02:48:00 PM »
Ouch. Sorry to hear about the loss. Will be grabbing the latest beta soon to test...
Help will be given to those with a b3.log

If drop off the map it is due to RL becoming busy :)

System: Python 2.7.3 - Deb 7 - B3 Source Code - 128MB RAM box (rented at $5 a year) - remote MySQL - Remote Web Services


Rate this page +1 at Google Search