home

download

demo

documentation

bug report

forums

Bug Report
Submitting a Bug Report

Before submitting a bug report, read the Known Issues section below to see if a bug you've encountered is already listed. Also, check to see if the Bug Report Forum also has your bug. If it is, you may wish to add your own clarifications or opinions to the matter, if it hasn't already been said; or if it's not there, then please post your bug there.

You are not required to register on the Bug Report Forum if you wish to post, so don't worry about signing up! We are more concerned that users find and notify us with bugs than we are with padding our memberlist. By using the forums, it is a handy place for us to store reports as well as allow other users to discuss them with each other.

Thanks!

  • Users with PHP installations that have register_globals set to off encounter many errors.
  • If there are two or more address types with the same name in one entry, and one of those addresses is marked as the primary address, this causes all other addresses with the same type to also act as a primary address.
  • It is possible to delete all the users in the user-management script and therefore completely lock yourself out of the address book installation (because there are no more valid usernames). If you delete all the administrator users (especially your own administrator account) be sure to create another one before you log out. The script permits you to turn off the login system completely, but doing so also turns off the user management page. If you find yourself in a situation where you need to add a user but cannot get to the user management script, you will have to add it manually through MySQL.
Known Issues in v1.01c
  • Users with PHP installations that have register_globals set to off encounter many errors.
  • If there are multiple admin users, entries added at or around the same time might overwrite each other.
  • A user-management script, users.php, is included but does not work. Users may be added or changed only by manually adding them to the MySQL table. Note that passwords must be stored with the MD5() command.
  • A group-management script is still unavailable.
  • A new category in the group drop-down, called "ungrouped entries", does not work.
  • Countries are added in the installation but are not yet available in the script.
  • There is currently no way to upgrade an installation.
Known Issues in v1.01b
  • While adding entries, blank lines in textareas *between* lines (not before or after) causes errors during the update. This is because the blank line is treated as a new row to be added, but because it is blank, it kills the script.
  • Certain fields added in textareas are required, but this is not checked. The "|" delimiter is always required even if fields are optional, which is not obvious to the user.
    • Email - Address is required if a Type is set; Type is optional
    • OtherPhone - Both fields are required
    • Messaging - Both fields are required
    • Websites - URL is required if Name is set; Name is optional
    • AdditionalData - Both fields are required
  • stripslashes() needs to be done before displaying any data.
  • Birthday update variable should be checked for legal values.
  • previous/next functionality should be improved to work in alphabetical order, not by ID order. Current implementation will result in blank entries being displayed if entries have been deleted.
  • Use the VARCHAR length of fields to determine max length of edit.php fields.
  • ID checking does not account for non-whole numbers such as decimals. This results in address.php displaying an empty page since no entry has a decimal number ID. This MAY cause trouble with edit.php if it thinks that a decimal ID is an attempt to create a new entry.
  • Birthday list issues:
    • Birthdates will not wrap around the end of a year -- in other words on December 29 it will not show birthdays in January even though the next thirty days include January.
    • Because DAYOFYEAR is used to find dates, birthdays on leap years (After Feb. 29) will appear a day later than it should.
  • Goto box issues:
    • Really bad at searching more than one part of a name (i.e. first and last name) because of the way the variables are concatenated.
  • Netscape 4.x issues:
    • most problems come from buggy CSS implementation in the browser.
    • padding-top and padding-bottom CSS properties seem to be adding extra white space in list.php. Removing these from the CSS file corrects the problem.
    • Adding an extra table row with the "add new entry", "manage groups" and "export" links causes table to not be centered.
  • When adding an entry that does not have an address the script returns a warning that the address table has already been optimized -- most likely due to code that should not be executed unlss the address table is modified in the first place.
  • Sometimes clicking the "Save" button at the bottom (in Opera 6) scrolls back to the address box. Seems to happen only when most of the address boxes are filled in. May be a browser malfunction.
  • Sometimes in edit.php the pre-existing values in a textarea (usually for e-mail but not always) is actually printed *outside* the box, requiring the user to rewrite it in the box in order to keep the data. May be a browser (Opera 6) malfunction.

The Address Book
© 2001-2004 Infinity Plus One Productions. All Rights Reserved.