My favorites | Sign in
Project Home Downloads Wiki Issues Source
Details: Show all Hide all

Older

  • Dec 13, 2010
    r1401 ([No log message]) committed by dor...@donaldorgan.com   -   [No log message]
    [No log message]
  • Sep 15, 2010
    r1400 (Fixed Forgot Email Password ) committed by dor...@donaldorgan.com   -   Fixed Forgot Email Password
    Fixed Forgot Email Password
  • Sep 15, 2010
    r1399 ([No log message]) committed by dor...@donaldorgan.com   -   [No log message]
    [No log message]
  • Sep 01, 2010
    r1398 (Continued cleaning up of explicit setting of error_reporting...) committed by dor...@donaldorgan.com   -   Continued cleaning up of explicit setting of error_reporting()
    Continued cleaning up of explicit setting of error_reporting()
  • Sep 01, 2010
    r1397 (Continued removing of explicit error_reporting() settings ) committed by dor...@donaldorgan.com   -   Continued removing of explicit error_reporting() settings
    Continued removing of explicit error_reporting() settings
  • Sep 01, 2010
    r1396 (More removing of specific error_reporting setting..... ) committed by dor...@donaldorgan.com   -   More removing of specific error_reporting setting.....
    More removing of specific error_reporting setting.....
  • Sep 01, 2010
    r1395 ([No log message]) committed by dor...@donaldorgan.com   -   [No log message]
    [No log message]
  • Aug 25, 2010
    r1394 (Removed error_report() option change as error_report level s...) committed by dor...@donaldorgan.com   -   Removed error_report() option change as error_report level should be dictated by php.ini and not by core framework
    Removed error_report() option change as error_report level should be dictated by php.ini and not by core framework
  • Aug 25, 2010
    r1393 (Andro application should have deprecated config option set t...) committed by dor...@donaldorgan.com   -   Andro application should have deprecated config option set to Y
    Andro application should have deprecated config option set to Y
  • Aug 05, 2010
    issue 9 (Error Reporting: secondary errors) changed by dor...@donaldorgan.com   -  
    Status: WontFix
    Owner: dor...@donaldorgan.com
    Status: WontFix
    Owner: dor...@donaldorgan.com
  • Aug 05, 2010
    issue 3 (Problem pulling updates from SVN) Status changed by dor...@donaldorgan.com   -   We are no longer using sourceforge for SVN hosting.....
    Status: Invalid
    We are no longer using sourceforge for SVN hosting.....
    Status: Invalid
  • Aug 05, 2010
    5 issues changed by dor...@donaldorgan.com   -   Issues 1, 4, 6, 7, 15
    Issues 1, 4, 6, 7, 15
  • Aug 05, 2010
    issue 34 (Documentation of Foreign Keys) changed by dor...@donaldorgan.com   -  
    Status: Fixed
    Owner: dor...@donaldorgan.com
    Status: Fixed
    Owner: dor...@donaldorgan.com
  • Aug 04, 2010
    issue 34 (Documentation of Foreign Keys) reported by j...@freedomcircle.com   -   Description of Bug: On the page http://www.andromeda-project.org/foreignkeys.html, the last line of the second code block describing table 'orders' is incorrect. Instead of saying: table orders: ... foreign_key orders: it should say: table orders: ... foreign_key customers: In addition, the second paragraph after that code block should say "the column(s) that make up the primary key of the CUSTOMERS table." There are also some other inconsistencies. For example, in the end of the fourth code block, foreign_key father_persons: prefix: _father The last line should be "prefix: father_". Finally, in the last code block it's unclear what the foreign key column names will be: persons_mother and persons_father, or person_mother and person_father. Please tell us how to reproduce this bug: N/A
    Description of Bug: On the page http://www.andromeda-project.org/foreignkeys.html, the last line of the second code block describing table 'orders' is incorrect. Instead of saying: table orders: ... foreign_key orders: it should say: table orders: ... foreign_key customers: In addition, the second paragraph after that code block should say "the column(s) that make up the primary key of the CUSTOMERS table." There are also some other inconsistencies. For example, in the end of the fourth code block, foreign_key father_persons: prefix: _father The last line should be "prefix: father_". Finally, in the last code block it's unclear what the foreign key column names will be: persons_mother and persons_father, or person_mother and person_father. Please tell us how to reproduce this bug: N/A
  • Apr 22, 2010
    r1392 (Password Reset email bug fix ) committed by dor...@donaldorgan.com   -   Password Reset email bug fix
    Password Reset email bug fix
  • Apr 22, 2010
    r1391 (fixed a bug that was causing the system username to be sent ...) committed by dor...@donaldorgan.com   -   fixed a bug that was causing the system username to be sent instead of the friendly username(email) during password reset request emails
    fixed a bug that was causing the system username to be sent instead of the friendly username(email) during password reset request emails
  • Nov 21, 2009
    r1390 ([No log message]) committed by dor...@donaldorgan.com   -   [No log message]
    [No log message]
  • Nov 21, 2009
    r1389 (changed name column from length 70 to 100) committed by dor...@donaldorgan.com   -   changed name column from length 70 to 100
    changed name column from length 70 to 100
  • Nov 09, 2009
    r1388 (Initial Creation of 2.0 branch only the builder will be used...) committed by dor...@donaldorgan.com   -   Initial Creation of 2.0 branch only the builder will be used from existing Andromeda
    Initial Creation of 2.0 branch only the builder will be used from existing Andromeda
  • Oct 21, 2009
    andromeda_0.1.0_all.deb (ubuntu 8.04 DEB package) file uploaded by dor...@donaldorgan.com   -  
    Labels: OpSys-Linux
    Labels: OpSys-Linux
  • Jul 08, 2009
    r1387 (fix to builder to look at andro_universal.dd when determinin...) committed by dor...@donaldorgan.com   -   fix to builder to look at andro_universal.dd when determining if a full build should be done.
    fix to builder to look at andro_universal.dd when determining if a full build should be done.
  • Jul 08, 2009
    r1386 (fix to builder to look at andro_universal.dd when determinin...) committed by dor...@donaldorgan.com   -   fix to builder to look at andro_universal.dd when determining if a full build should be done.
    fix to builder to look at andro_universal.dd when determining if a full build should be done.
  • Jul 08, 2009
    r1385 ([No log message]) committed by dor...@donaldorgan.com   -   [No log message]
    [No log message]
  • Jul 08, 2009
    r1384 ([No log message]) committed by dor...@donaldorgan.com   -   [No log message]
    [No log message]
  • Jul 08, 2009
    r1383 ([No log message]) committed by dor...@donaldorgan.com   -   [No log message]
    [No log message]
  • Jul 02, 2009
    issue 33 (Updating of application with no releases) Status changed by dor...@donaldorgan.com   -   This issue was closed by r1382.
    Status: Fixed
    This issue was closed by r1382.
    Status: Fixed
  • Jul 02, 2009
    r1382 (fixes issue 33) committed by dor...@donaldorgan.com   -   fixes issue 33
  • Jul 02, 2009
    issue 33 (Updating of application with no releases) reported by dor...@donaldorgan.com   -   Description of Bug: When you run "Update from SVN" if an application has no releases it thinks there are still releases because it still see ".." and "." and tries to actually download that as a release, which it actually pulls nothing but it should be trying to pull anything at that point.
    Description of Bug: When you run "Update from SVN" if an application has no releases it thinks there are still releases because it still see ".." and "." and tries to actually download that as a release, which it actually pulls nothing but it should be trying to pull anything at that point.
  • Jul 02, 2009
    issue 32 (scriptPath() does not return expected result when accessing ...) Status changed by dor...@donaldorgan.com   -   This issue was closed by r1381.
    Status: Fixed
    This issue was closed by r1381.
    Status: Fixed
  • Jul 02, 2009
    r1381 (fixes issue 32) committed by dor...@donaldorgan.com   -   fixes issue 32
  • Jul 02, 2009
    issue 32 (scriptPath() does not return expected result when accessing ...) reported by dor...@donaldorgan.com   -   Description of Bug: [See summary] Please tell us how to reproduce this bug: scriptPath() includes xxx/pages/xxx in path when called from a page that was accessed via the /pages/ method
    Description of Bug: [See summary] Please tell us how to reproduce this bug: scriptPath() includes xxx/pages/xxx in path when called from a page that was accessed via the /pages/ method
  • Jun 29, 2009
    r1380 (Changed scriptPath() to actually work, when a friendly /page...) committed by dor...@donaldorgan.com   -   Changed scriptPath() to actually work, when a friendly /pages/ URL is used.
    Changed scriptPath() to actually work, when a friendly /pages/ URL is used.
  • Jun 21, 2009
    issue 31 (primary_key allow_empty) reported by dor...@donaldorgan.com   -   allow_empty should be allowed on a multi primary_key table for instance in a CMS application pages would reference subsections, and example of subections could be: Computers, Laptops Computers, Desktops Well if you want to assign a page to just Computers then you should be able to point it to Computers,
    allow_empty should be allowed on a multi primary_key table for instance in a CMS application pages would reference subsections, and example of subections could be: Computers, Laptops Computers, Desktops Well if you want to assign a page to just Computers then you should be able to point it to Computers,
  • Jun 08, 2009
    r1379 ([No log message]) committed by k...@secdat.com   -   [No log message]
    [No log message]
  • Jun 08, 2009
    r1378 (Modified auto-complete fetch to only execute if value change...) committed by k...@secdat.com   -   Modified auto-complete fetch to only execute if value changed. No Google issue #.
    Modified auto-complete fetch to only execute if value changed. No Google issue #.
  • Jun 08, 2009
    r1377 (After saving a new row on conventional profile, child detail...) committed by k...@secdat.com   -   After saving a new row on conventional profile, child detail panes become enabled. No google issue number.
    After saving a new row on conventional profile, child detail panes become enabled. No google issue number.
  • Jun 08, 2009
    issue 30 (Allow php pre-insert/update code to prevent action) Status changed by k...@secdat.com   -   This issue was closed by r1376.
    Status: Fixed
    This issue was closed by r1376.
    Status: Fixed
  • Jun 08, 2009
    r1376 (Allow PHP pre-insert/update JSON code to prevent actions by ...) committed by k...@secdat.com   -   Allow PHP pre-insert/update JSON code to prevent actions by returning false or null. fixes issue 30
    Allow PHP pre-insert/update JSON code to prevent actions by returning false or null. fixes issue 30
  • Jun 08, 2009
    issue 30 (Allow php pre-insert/update code to prevent action) reported by k...@secdat.com   -   In an x6 class you can add methods like <table_name>_Before_insert($row) that are given a row before it is inserted or updated. When this enhancement goes in, if the routines returns false then the action is prevented. To allow the action to proceed you return the row with or without modifications.
    In an x6 class you can add methods like <table_name>_Before_insert($row) that are given a row before it is inserted or updated. When this enhancement goes in, if the routines returns false then the action is prevented. To allow the action to proceed you return the row with or without modifications.
  • Jun 08, 2009
    r1375 (Show Menu text as config setting. Also unrelated fix to bui...) committed by k...@secdat.com   -   Show Menu text as config setting. Also unrelated fix to builder that was causing tmp files to not get built properly.
    Show Menu text as config setting. Also unrelated fix to builder that was causing tmp files to not get built properly.
  • Jun 08, 2009
    issue 29 (Allow pre- and post- delete triggers in PHP code, same as up...) Status changed by k...@secdat.com   -   This issue was closed by r1374.
    Status: Fixed
    This issue was closed by r1374.
    Status: Fixed
  • Jun 08, 2009
    r1374 (Allow PHP level actions before and after an ajax delete. fi...) committed by k...@secdat.com   -   Allow PHP level actions before and after an ajax delete. fixes issue 29
    Allow PHP level actions before and after an ajax delete. fixes issue 29
  • Jun 08, 2009
    issue 29 (Allow pre- and post- delete triggers in PHP code, same as up...) reported by k...@secdat.com   -   See summary, it says it all
    See summary, it says it all
  • Jun 08, 2009
    r1373 (Removed stray "console.log()" call.) committed by k...@secdat.com   -   Removed stray "console.log()" call.
    Removed stray "console.log()" call.
  • Jun 08, 2009
    issue 28 (When user clicks [NEW] go to first control) Status changed by k...@secdat.com   -  
    Status: Verified
    Status: Verified
  • Jun 08, 2009
    issue 28 (When user clicks [NEW] go to first control) Status changed by k...@secdat.com   -   This issue was closed by r1372.
    Status: Fixed
    This issue was closed by r1372.
    Status: Fixed
  • Jun 08, 2009
    r1372 (Always go to first control when user clicks [NEW] Fixes iss...) committed by k...@secdat.com   -   Always go to first control when user clicks [NEW] Fixes issue 28 Status: Verified
    Always go to first control when user clicks [NEW] Fixes issue 28 Status: Verified
  • Jun 08, 2009
    issue 28 (When user clicks [NEW] go to first control) reported by k...@secdat.com   -   Right now when a user clicks [SAVE] and then [NEW], the cursor is on the last control they were editing. This should go to the first control.
    Right now when a user clicks [SAVE] and then [NEW], the cursor is on the last control they were editing. This should go to the first control.
  • Jun 08, 2009
    issue 27 (Skey apparently not available after save new) Status changed by k...@secdat.com   -  
    Status: Verified
    Status: Verified
  • Jun 08, 2009
    issue 26 (Regular Text inputs do not allow ampersand) Status changed by k...@secdat.com   -  
    Status: Verified
    Status: Verified
 
Powered by Google Project Hosting