Error: Unexpected character in input: ''' (ASCII=39) state=1

[mipapage]

Hey all,

We had this error creep up last week when we upgraded to 5.0.0c, so we rolled back to 5.0.0b for the time being.

Now though, it seems we're having it with 5.0.0b. Any ideas what it could be?


Warning: Unexpected character in input: ''' (ASCII=39) state=1 in
/sugar/cache/modules/Opportunities/Opportunityvardefs.php on line 1177

Parse error: syntax error, unexpected $end, expecting ')' in
/sugar/cache/modules/Opportunities/Opportunityvardefs.php on line 1177


It happens with various modules, always the cache files. I'd guess that the cache files aren't building and being saved in an incomplete state, could this be it?

[ptemplin7]

Sounds like a file corruption.
Have you gone to the Admin-> Repair and cleared the cache and rebuilt the connections? If not try that first.

If this error shows in the same file or files. Then I would try editing them and looking for something weird like a control character.

Hope this helps,

Paris

[mipapage]

Thanks for the reply, Paris.

I have cleared the cache and done repairs, unfortunately that didn't help.

I have also downloaded the files in question after seeing one of these errors reported and not found any issues. Quite strange, really.

[fjhuerte]

i have experienced this error too.
after rebuilding the codes, this unexpected character input error occurs
why is this writing garbage files? what is causing these?

fjhuerte

[fjhuerte]

I have solved my prob..
it was caused by permissions and the vss files included in the folders.


fjhuerte

[SpacemanSpiff]

OK, I admit, I might be being a bit stupid here... but what are VSS files?????

[chad.hutchins]

I am having the same problems and they pop up in multiple modules. They occur in the Accounts and Contacts most often for us.

Fortunately, we can just tell our users to refresh the the page and it usually resolves it temporarily, but it is starting to annoy our users.

Just wanted to give this a bump...

[chad.hutchins]

Does anyone know what triggers Sugar to regenerate the cached vardef pages?

Is it possible that one user is on Sugar and somehow they trigger Sugar to regenerate a cached vardef file, then when another user tries to access that a page that requires that cached vardef file the cached vardef file hasn't completed regenerating itself, so it appears to have syntax errors. Is this even possible? I'm just trying to throw out anything I can think of.

Anyone else?

[chad.hutchins]

I can now repeat the problem. I am sure there are multiple ways, but here is the way I found to repeat it:

Have two browser tabs or windows open. Point one to the Reports module and the other to any given account page. Create a custom report that looks at the Accounts module. Run the report then select 'Export'. (I do this because it is a function that takes several seconds to run) While the report is still running, open up /custom/modules/accounts/tpls/DetailViewHeader.php and make any sort of change in the code and save it. While the report is still running, refresh the tab/window that is showing the account. Immediately after refreshing that page, the report will break with our infamous error.

Like I said, there are multiple ways to cause the bug: anything that causes the cache file of a module to be rebuilt at the same time another user is trying to access a page that involves the same module will cause the bug to occur. It seems that the user is allowed access to an incomplete cache file (one that is caught in the middle of being rebuilt), so it throws the syntax error.

SOLUTIONS: We need to find a way to block (as in pause the process until the cache file is completely rebuilt) a user from accessing a page that requires cache files that are in the middle of being rebuilt.

Can anyone else repeat this?

Sugar, is it possible that this is actually the root cause of the problem?

[chad.hutchins]

Turning off Developer mode has seemed to solve this problem!

Thanks to mipapage.