Thread

Hi,

I have a strange error after upgrading a system from 2.7.1 => 2.7.2.

When setting up an EE install I always move the system directory out of the public scope of the server (and rename), rename ‘admin.php’ and make the necessary config changes via a bootstrap file (have done this many many times!).

Since upgrading to 2.7.2 I am getting javascript loading issues when accessing the CP via the renamed ‘admin.php’ file causing things like tabs and the template manager to stop working! These seem to be inconsistent issues across the loaded files but one example is as follows:

‘Uncaught SyntaxError: Unexpected end of input ’ on the following code:

...
a("#template_keywords_reset").click(function(){a("#template_keywords").val("");a(".search form").submit()})})(jQuer

As you can see, the last characters of the javascript file are not loaded and it throws and error. When the CP is access directly through the system folder (for example http://xxx.xxx.xxx.xxx/system/index.php) I do not get the errors and the above example code loads fine:

...
a("#template_keywords_reset").click(function(){a("#template_keywords").val("");a(".search form").submit()})})(jQuery);

I have tried everything I can think of:

- Cleared all caches (browser/ee/server)
- performed the upgrade again (from a backed up copy)
- tried different browsers (I use Chrome by default)
- Fresh install of 2.7.2 and the database and manually re-create the channels/setups etc

...and still get the same inconsistent issue.

At the moment I can access the ‘system’ folder to develop the system but, as I move the system directory out of public scope in the production environment, we (or indeed our clients) cannot use the CP when it’s live!

Does anyone have any thoughts what so ever…it’s got to be one of the strangest issues I have had with EE and I am at my wits end with it!

Many Thanks
Dan

As a quick update to this issue. I have deployed the system to a fresh server environment and there doesn’t seem to be a problem!

This has taken some of the urgency out of the problem but doesn’t really explain the problem in my local environment. Just a ‘stab in the dark’ but does anyone know of any particular Apache or PHP modules that may cause JS parsing issues in EE?