Bugtracker of MarioValdez.net Bugtracker of MarioValdez.netOSCommerce Product Manager: Recently closed tasks http://www.mariovaldez.net/webapps/bugtracker2/ 2010-02-18T15:48:19Z FS#109: Test compatibility with CRE Loaded versions of OSC. 2010-02-18T15:48:19Z 2004-09-07T00:41:44Z
Pending testing.
Mario A. Valdez-Ramirez http://www.mariovaldez.net/webapps/bugtracker2/:109
FS#73: Test compatibility with Windows ME, 98 and 95. 2010-02-18T15:41:38Z 2004-08-21T10:10:15Z
Pending testing with other Windows platforms. Currently, only Windows 2000 (Pro and Server) and Windows XP Pro has been tested.
Mario A. Valdez-Ramirez http://www.mariovaldez.net/webapps/bugtracker2/:73
FS#343: Test compatibility with osCommerce Modificado 2010-02-18T15:39:45Z 2007-05-23T07:49:55Z
osCommerce modificado is a derivative version of osCommerce: http://www.oscommerce-modificado.com/

Pending to test.
Mario A. Valdez-Ramirez http://www.mariovaldez.net/webapps/bugtracker2/:343
FS#123: Test with WINE. 2010-02-18T15:38:42Z 2004-09-21T15:29:53Z
Pending to test compatibility with WINE in Linux.
Mario A. Valdez-Ramirez http://www.mariovaldez.net/webapps/bugtracker2/:123
FS#353: Rounding error when calculating and saving tax and net price 2010-02-18T15:37:30Z 2009-12-18T13:06:09Z
From an email report:

"si yo introduzco 2.50 como precio final impuesto incluido, su programa automáticamente rellena la casilla de precio sin impuesto a 2.1552, y acto seguido al confirmar, redondea esta cantidad a 2.16, con lo que el precio final se guarda con valor 2.5056, 2.51 al redondear."

"If I enter 2.50 as final price with tax, your program automatically fills the net price field with 2.1552, after that when confirming, it rounds up the number to 2.16 and the final price is stored with 2.5056 value; rounded as 2.51."

Pending to review.
Mario A. Valdez-Ramirez http://www.mariovaldez.net/webapps/bugtracker2/:353
FS#356: Wrong product list loaded when category tree is clicked... 2010-02-18T15:36:39Z 2010-02-16T14:59:18Z
In a customized osCommerce store, the OSCPMWin client loads the wrong product list when clicking a given category in the category tree. It seems it load the previous on listed in the tree (for example, Prueba category is listed before Relojes, but clicking Prueba loads the Relojes products).

Pending to check if this is a problem with this store only or a general one.

Mario A. Valdez-Ramirez http://www.mariovaldez.net/webapps/bugtracker2/:356
FS#347: Use JPEG downsampling when resizing the images. 2007-08-11T04:00:21Z 2007-07-22T08:06:12Z
Test the downsampling options in the FreeImage library and test for different downsampling settings to check what options gives better size vs quality. The idea is to create an automatic downsampling selector based on the desired quality level defined in the OSCPMWin configuration.
Mario A. Valdez-Ramirez http://www.mariovaldez.net/webapps/bugtracker2/:347
FS#273: Watermark uploaded images. 2007-07-25T05:37:07Z 2005-09-21T14:15:58Z
Create the option to select a graphic (PNG, GIF, TIFF, etc) to blend with all uploaded images, to watermark all images. Some store users use to add their logo to their images or their URL.
Mario A. Valdez-Ramirez http://www.mariovaldez.net/webapps/bugtracker2/:273
FS#322: Elapsed time checking may give wrong result. 2007-07-21T04:52:51Z 2006-04-04T20:57:44Z
At several places, specialy when waiting for a retry, the application check the current time (with milisec resolution) and it act accordingly. The usual checking is done with a GetTickCount functions.

We are aware of a possible problem if the computer (client-side, not server) is left running more than 49.7 days. The GetTickCount will be restarted.

We usually do this:

LapseTime := GetTickCount;
UNTIL ((GetTickCount - LapseTime) > opmG_HTTPConnWait);

The problem will happen if we start the loop and then the GetTickCount value is wrapped (restarted), the loop would take 49.7 days to complete (unless again it wraps before the cheking, which would extend the wait for 49.7 days).

Even though this would be a very rare occurrence, it should be fixed.
Mario A. Valdez-Ramirez http://www.mariovaldez.net/webapps/bugtracker2/:322
FS#301: Improve password hashing sent to server-side script. 2007-07-15T17:48:34Z 2005-12-04T09:57:22Z
Currently the application send the hashed (password + timestamp). The timestamp is set by the client and is sent in the clear.

We set the salt client-side to avoid a full round-trip asking the server a salt.

We could do this:

MD5 (MD5 (Salt + Password))

and not this:

MD5 (Salt + Password)

If the server could set the salt, we could use:

MD5 (MD5 (Salt + MD5 (Password)))
Mario A. Valdez-Ramirez http://www.mariovaldez.net/webapps/bugtracker2/:301