stuck at step 1 'INSTL_INSTALLATION'

[carsten888]

I uploaded 1.6 stable and opened the installer. All language strings show untranslated and the button 'jnext' gives a javascript error.

I wondered if I missed something in the upload so uploaded everything again, with same result.

I installed the same 1.6 package 10-20 times on my WAMP without any problem, but not online until now.

[den Bart]

Same problem with me. The frontend and the backend have the same problem. But I don't know how to solve it ...

[kenmcd]

.
This issue may be caused by your host disabling certain PHP functions required by Joomla 1.6.
In J1.6 the language files now rely on the parse_ini_file function (or parse_ini_string in PHP 5.3+).

You can check to see if the functions are disabled by looking at PHP Information (phpinfo).
In the Core section there is a disable_functions line.
If those functions are listed there, you have an issue which you need to resolve with your host.

There are actually four PHP functions which if disabled can be a problem:
- parse_ini_file
- parse_ini_string
- json_encode
- json_decode

You can see more background information here:
[#20613] Missing parse_ini_file, parse_ini-string, json_encode or json_decode cause show-stopper behaviour
http://joomlacode.org/gf/project/joomla ... m_id=20613

An excerpt from that tracker item:

If the functions parse_ini_file (PHP 5.2) or parse_ini_string (PHP 5.3) are disabled,
the user experiences untranslated screens throughout the whole Joomla! experience, starting with its installation.
Many hosts mistakenly disable them on false pretexts regarding security, probably confusing them with ini_set().
This also accounts for the elusive "untranslated strings during installation" issue reports received by various unofficial channels (e.g. Twitter) from users attempting to install Joomla! 1.6.b1.

.

[carsten888]

Thank you. that is helpfull info.

[den Bart]

Thank you for the help.
The COM_ADMIN_PHP_INFORMATION shows "disable_functions no value no value", so it seems to be an other problem.

[kenmcd]

.
That makes me wonder if this an issue with ModSecurity (mod_security).
Something is blocking access to the language INI files.
There are cases where ModSecurity has been an issue with INI files.

For testing that theory, you could temporarily disable mod_security.
Some website control panels have a setting called "Enhanced Web Security" (or similar).
That setting could be used to toggle ModSecurity on and off.
It also may be possible to disable ModSecurity in the .htaccess file.
Near the top of the .htaccess file add:

Code: Select all

SecFilterEngine Off

Note that turning-off ModSecurity is not the solution and should only be done for testing.
If the issue is actually caused by ModSecurity settings, the long-term fix should be in the configuration.


You could also ask your hosting service about the issue.
They may have already seen this issue before and know the solution.
.

[carsten888]

if this an issue with ModSecurity (mod_security).
Something is blocking access to the language INI files.

I tried this on a server where I got a Jooml 1.5 running without lang problems. In a subdirectory I tried to install Joomla 1.6 with the language problem. So problems with langs in 1.6 and NO problem with langs in 1.5 on the exact same server with the same config.

[kenmcd]

.
It is not just the access of an INI file, it how those files are accessed in J1.6.
That has changed in J1.6.
If the required PHP functions are available, then the "blockage" is coming from somewhere else.
So my next guess is some ModSecurity settings are perhaps too aggressive.

I have seen an issue where a standard ModSecurity rule blocked access to an MP3 file simply because the URL to the player and MP3 was constructed in a particular way.
Disable that one ModSecurity rule and the MP3 played fine.

So that is why my guess is it could be an issue with a ModSecurity setting.

p.s. Have you looked in the log files to see if anything there can shed some light on this?
.