View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002686||OXID eShop (all versions)||4.07. Source code, Test||public||2011-04-04 10:48||2012-12-10 13:44|
|Product Version||4.4.8 revision 34028|
|Target Version||Fixed in Version||4.7.0_5.0.0_beta1|
|Summary||0002686: Manufacturer product number OXMPN too short|
|Description||varchar(16) is too short for a third of our products.|
Since we have many extraordinary products (and manufactures), the mpn is often of descriptive nature.
For example those two versions of an article:
I suggest varchar(100) to be on the safe side.
(Our most extreme products mpn is actually that long...)
|Additional Information||oxmpn is required from 3. May 2011 on (if you dont have eans)|
|Tags||No tags attached.|
Reminder sent to: tjungcl
This is more feature request, not a bug. So it's moved to the feature request list:
Thank you for report.
I again forgot to modify this field after installation and loaded thousands of mpns, that were then cut of after 16 chars.
The feature request user-voice-suggestion list is kind of a joke.
I reopen this by quoting the only user-reaction in a whole year (my own):
Moved to feature request for something so trivial?
Making this field 16 chars long in the first place was just a design-flaw. There is no need to restrict this field to so few chars. Even Oxids own artikelnumbers OXARTNUM is varchar(255)!
Of course everybody can change the type to varchar(100) on his own (has i have done of course), but you could include that in your next update, so other users just dont have to bother.
||changed to 100|