I’ve tried the steps mentioned by Will.
And then did a quick repair/rebuild.
then tried the step mentioned elsewhere of deleted the jslanguage file and then doing a repair of jslanguage followed by quick repair rebuild.
and still the same problem.
It’s a Linux server, with the files controlled by cPanel file manager. The install is not into root, but rather in a subdomain, though I wouldn’t expect that to be a major problem.
Ah. Does the fact that until we complete implementation we’re hosting it on a temp server have any effect?
[hide]
[error] [client 79.77.155.1] Premature end of script headers: colourSelector.php, referer: http://REDACTED/REDACTED/unifynew/index.php?module=Administration&action=RebuildJSLang
[Fri Dec 04 02:46:40 2015] [error] [client 79.77.155.1] File does not exist: /usr/local/apache/htdocs/unifynew, referer: http://REDACTED/REDACTED/unifynew/index.php?module=Administration&action=Upgrade
[Fri Dec 04 02:46:40 2015] [error] [client 79.77.155.1] File does not exist: /usr/local/apache/htdocs/unifynew, referer: http://REDACTED/REDACTED/unifynew/index.php?module=Administration&action=Upgrade
[Fri Dec 04 02:43:57 2015] [error] [client 79.77.155.1] Premature end of script headers: colourSelector.php, referer: http://REDACTED/REDACTED/unifynew/index.php?action=ajaxui
[Fri Dec 04 02:44:00 2015] [error] [client 79.77.155.1] File does not exist: /usr/local/apache/htdocs/unifynew, referer: http://REDACTED/REDACTED/unifynew/index.php?action=ajaxui
[Fri Dec 04 02:46:08 2015] [error] [client 79.77.155.1] File does not exist: /usr/local/apache/htdocs/unifynew, referer: http://REDACTED/REDACTED/unifynew/index.php?module=Administration&action=index
[Fri Dec 04 02:46:08 2015] [error] [client 79.77.155.1] File does not exist: /usr/local/apache/htdocs/unifynew, referer: http://REDACTED/REDACTED/unifynew/index.php?module=Administration&action=index[/hide]
Hello there,
over the years with this CRM there are basically only 3 possible causes for “undefinied”
in the exact order. If the permissions are correct, then it would be interesting, what PHP version is used. We have no problems with 5.3 and 5.4 - but about already. This is certainly also depends on the age, just when Custom modules are used.
Language File is also a possibility.
The error messages should not affect this behavior.
Regards
Soon as the site was pointed to a real domain, it fixed itself, no extra steps necessary.
So the error messages were the problem, in other words. It was a permissions problem, but not in the expected areas that are most common. It was a problem with apache not letting the scripts run because it didn’t believe that it was a valid file.