Custom1 interfering with Custom10? [dvdpedia]

[sitenoise]

Is there a chance that Custom1 can some how be interfering with Custom10 in the infoview template?

If I have things tweaked to show Custom1 AND there is something in it, and if I code for show Custom10 and there is NOTHING in it, it displays "0 ENDcustom10-->" in the infoview.

But

If I have things set to show Custom1 and there is NOTHING in it, and if I use Custom10 and there is nothing in it, it displays nothing.
If I have things set to show Custom1 and there is NOTHING in it, and if I use Custom10 and there is something in it, it displays the something.

This is driving me crazy. I don't know where to begin. Help?

[Conor]

It's a bug that has been there since we introduced the custom10 field. It's the reason none of our info templates include custom10. We were hoping nobody would notice it, that people would be happy with the first 9 fields. Since you have decided that you really want to use custom10 try out the beta and it should work like a charm, since the fix was complicated we wanted to leave it until we could no longer pretend the bug did not exist.

The bug was that <--IFcustom1 matches the beginning of <--IFcustom10. So if you have a custom one it removes the beginning comment for custom10 but not the ending one. If you have both it leaves an orphaned "0" if in the file custom1 comes before custom10, as it usually does.

[sitenoise]

I just had to open my big mouth, didn't I? Kind of a funny story.

The beta appears to have fixed it. I'm not actually using all 10 custom fields, just picked number 10 for the heck of it. Sorry ...
Thanks again for outstanding customer care.