Thanks for having taken the time to answer.
Disclaimer: what follows is not directed at you personally, but at the Sitefinity team as a whole (managers in particular).
We hope the fix will really make it in the next release (because I remember times when promised fixes were not included after all
), as this is a show-stopper for us.
Also, thanks for the proposed workaround, which we could use as developers for
now, but that we couldn't seriously propose to our clients,
as you can guess. This means we'll have to delay the launch of the site once more.
By the way, we're hitting this particular bug as we're *already* working around another glaring Sitefinity flaw: the inability to have multilingual documents (PITS #5304
). So this is a workaround for a workaround. We get more and more entangled in hacks and bad designs, as we need to keep developments going despite the limitations of Sitefinity. In these conditions, you can guess why so many SF users are appalled that you have time to spend on an eCommerce module.
"Please use the upload and save as draft option and then Publish from the
grid to make you image live in the non default language until the next
According to Nicolas, this does not work, the bug is triggered on save, whether it's published or not.
This would only work for items that are available in the default language, or both languages, but not items that only exist in the non-default language.