Rename Tabs causes fatal error

[mclemmens]

When attempting to rename tabs (under Admin) I get an error that says

Parse error: syntax error, unexpected $end in .......SugarCE-Full-5.0.0RC/custom/include/language/en_us.lang.php on line 1

When I surf to custom/include/language/en_us.lang.php on line 1 the file is only

<?php

And that's it. 5 bytes of data. Naturally, this causes everything to crash. (The entire site goes down until that file is deleted. )

I'm going to make a few assumptions about what I think is going on here. I think that the Rename Tabs function (part of the studio module) has a little wizard that's creating the en_us.lang.php file. It crashes halfway through and doesn't completely finish making the file because something goes wrong in the script and it chokes.

I believe what's wrong has something to do with three tabs that are listed of modules that were built in the module builder but uninstalled. For some reason, they're still alive as far as the rename tabs utility is concerned. (A bug I suspect) I wonder if they're hunting for info on those custom labels and then they choke out.

Any ideas?

Thanks!

[franklin_sugar]

Hi mclemmens,

I couldn't reproduce this problem on both CE and Ent RC builds in Windows/MySQL environment. I tested the following two use cases.

1) Rename a built-in tab
2) Create and deploy a new module, rename the tab, uninstall the module

Both cases worked for me without crashes.

Can you share your environment? OS, database, and PHP version? Also, can you give the detailed steps to reproduce this problem?

Thanks,
Franklin

[srose]

Hi mclemmens,

I couldn't reproduce this problem on both CE and Ent RC builds in Windows/MySQL environment. I tested the following two use cases.

1) Rename a built-in tab
2) Create and deploy a new module, rename the tab, uninstall the module

Both cases worked for me without crashes.

Can you share your environment? OS, database, and PHP version? Also, can you give the detailed steps to reproduce this problem?

Thanks,
Franklin

I am having exact same issue, on Debian server (media temple), PHP 5, MySQL 4.1.7 renaming tabs has caused exact same error.

Just thought I'd report it, in case it helps to solve. I wonder if this issue could be due to server running out of memory for MySQL "container"? I need to test on other servers...

[moonvn]

When attempting to rename tabs (under Admin) I get an error that says

Parse error: syntax error, unexpected $end in .......SugarCE-Full-5.0.0RC/custom/include/language/en_us.lang.php on line 1

When I surf to custom/include/language/en_us.lang.php on line 1 the file is only

<?php

And that's it. 5 bytes of data. Naturally, this causes everything to crash. (The entire site goes down until that file is deleted. )

I'm going to make a few assumptions about what I think is going on here. I think that the Rename Tabs function (part of the studio module) has a little wizard that's creating the en_us.lang.php file. It crashes halfway through and doesn't completely finish making the file because something goes wrong in the script and it chokes.

I believe what's wrong has something to do with three tabs that are listed of modules that were built in the module builder but uninstalled. For some reason, they're still alive as far as the rename tabs utility is concerned. (A bug I suspect) I wonder if they're hunting for info on those custom labels and then they choke out.

Any ideas?

Thanks!

Hi,

I got exactly the same error. Neither I can delete that file. My site is down. Please help !

[kuske]

Close the opening php-brackets by adding a line with "?>"

So your file should look like

<?php
?>

or delete the file.

Both will help.

hk

[moonvn]

Close the opening php-brackets by adding a line with "?>"

So your file should look like

<?php
?>

or delete the file.

Both will help.

hk

I edit the file with closing php-brackets. It helps. I can access my site now. Thank you kuske !

[swichman]

Hi all. FYI: I was also looking through/evaluating a sandbox version of SugarCRM 5.2.0. I also went in to rename a tab and I got the same error. Just wanted to post an update here indicating it hasn't been fixed. If someone can tell me what file creates this custom php script, then I can look into it because it seems to be a handy feature. STEVE