Customized form blocks were not using "form_row" design resulting fatal error

Skip to first unread message

Alexander Obuhovich

Sep 8, 2010, 1:53:27 PM9/8/10
to In-Portal Bugs
Customized form blocks were not using "form_row" design resulting fatal error on pages, that were having such blocks.


Ready for testing.

This is bug created during other task scheduled to 5.1.1 release. Therefore problem can only be reproduced in 5.1.x branch, since it wasn't released at all.

Best Regards,

Dmitry Andrejev

Sep 10, 2010, 6:42:37 PM9/10/10
Thanks for the patch and task (it's already tested as you know).

There might be another issue that rose from this patch. We are getting blank screens on some of Catalog pages.

We had similar issues before and it was related to some JS processing in the catalog_tabs.tpl, but I wonder if it's related to changed latest.



You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at


Best regards,

Dmitry A.

Alexander Obuhovich

Sep 11, 2010, 2:18:59 PM9/11/10
That is unrelated to form blocks, but is related to task, that was commited in 5.1.1 release (

Tag "IterateGridFields" was a bit changed. As a result, when:
  1. grid was never visited by user
  2. width of at least one column was not set explicitly in unit config
  3. user visits that grid
empty width was returned instead of default width equals to 100px resulting malformed array of grid column widths (GridScroller.MinWidths array) with trailing comma.

Task about this created:

Ready for testing.

Dmitry Andrejev

Sep 11, 2010, 4:31:02 PM9/11/10
New patch tested good (updated task) and can be committed.

Alex, thanks for the fix!!!

Reply all
Reply to author
0 new messages