Templates add pseudorandom garbage code at its end on update

[Insidea]

Hi,

we've been developing a large amount of sites using CMSMS here at Insidea and we love the simplicity. However, in the last few months we've discovered a possible bug that's complicating our lives and we'd like to know if we're the first ones to notice or have some kind of unique setup that shows this. Read on, this one gets scary..

Thing is, you have a template anywhere in the system, be it core templates, or module templates. You open it in the admin section, as you normally do, you edit it, you save it, and you expect that the saved output is exactly the same as you've entered. Not this time. At the end of the string you've entered as the content of the template, after the template is saved and you open it again (or you just open and click somewhere else and reopen it again), there is a weird looking mix of smarty and html and php, which seems like buffer overflowing somewhere, or POST not being properly posted and parsed, or we don't have the slightest clue what it could be:-(

Imagine that your CMSMS "talks" to you, by adding this little word "Help" after you save your template. Until this moment it was weird, but now, it got scary.. see the attachment. The word "Help" at the end of form template was added by no human input, it added itself as I opened and closed and reopened the template. The same weird stuff can be observed in content templates as well.

It happens on all versions of CMSMS we've used in the history, but the important thing is it happens on 1.9.4.2 and that's the most-often deployed version we have so far. The PHP behind the machines getting this bug is 5.3.3 (and on some servers it's higher version, but no less than 5.3.3).

If anyone has experienced anything like this, or could point us in the right direction, we'll be happy to try it all, this can get very unpleasant during the devel process as well as with the maintenance of a site.

Kind thanks for any help,
Vaclav

[calguy1000]

CMSMS 1.9.4.2 is no longer supported, so before you respond to this post you should upgrade all of your sites to CMSMS 1.10.3

But... please try using a different browser and see if the issue goes away.

[Insidea]

OK, roger that, I will post back as soon as it appears on our 1.10.2 sites, so far, we have no 1.10.3 in production env

And it happened in Opera and Firefox.

Thank you, calguy.

[Insidea]

OK, before we had time to prepare a customized 1.10.3 that's ready for deployment, the background for this bug had changed:

it seems, that it only happens in Opera. No matter how much I like this browser, we are now only able to replicate the bug in Opera /current version 11.61/.

Thanks for the push in a good direction, Calguy.
Closing for now.