Jump to content

Module translation


Recommended Posts

Hello,

 

I'm using 1.4.9.0 with a custom theme and I have problems translating the modules. I get an error message like "Your host limits max_input_vars to 1000". Although my hosting provider assured me they raised that limit to 8000 (which should solve the problem) there is no improvement. I can translate FO features but i can't translate modules and BO. There was no problem translating modules until I installed some new ones that came with default PS download (just one module non-default).

 

Any ideas why is this happening?

 

Thanks.

Link to comment
Share on other sites

Hello,

 

I'm using 1.4.9.0 with a custom theme and I have problems translating the modules. I get an error message like "Your host limits max_input_vars to 1000". Although my hosting provider assured me they raised that limit to 8000 (which should solve the problem) there is no improvement. I can translate FO features but i can't translate modules and BO. There was no problem translating modules until I installed some new ones that came with default PS download (just one module non-default).

 

Any ideas why is this happening?

 

Thanks.

 

do you cleared your browser cache ? it's weird but sometimes it helps with changing server configuration.

Btw. are you sure that you provider change max input vars value to 8000?

Link to comment
Share on other sites

I cleared the cache, still the same result.

The hosting provider initially raised the value to 4000, than at my request at 8000. I can't be 100% sure they did that, I can't check. But I trust them to have done that.

 

you can check it, just create a php file with content:

 

<?PHP
phpinfo();
?>

 

and upload file to your server - and open it in your browser

 

you are looking for "suhosin.post.max_vars" on the list. Try it, maybe provider doesn't change the value of max input vars

Edited by vekia (see edit history)
Link to comment
Share on other sites

No, it works the same. Actually I just deleted it from the server. But I don't think there is a direct connection between the installation of this module and the translation error, I just noticed that after a couple of installations (this module included) the error appeared.

I think it has something to do with the theme and the files in it, that override standard theme files. It's kind of weird that I'm the first to experience this error.

Edited by sergiud (see edit history)
Link to comment
Share on other sites

No, it works the same. Actually I just deleted it from the server. But I don't think there is a direct connection between the installation of this module and the translation error, I just noticed that after a couple of installations (this module included) the error appeared.

I think it has something to do with the theme and the files in it, that override standard theme files. It's kind of weird that I'm the first to experience this error.

 

for me translations page works great (with installed nivo slider module). That's weird, you're right. Error which occurs in your shop isn't related to template of front office. This error is related to translation "input" fields, where you can translate some string to other language. if you've got more than 1000 fields on translation page - suhosin will display error about reached "max input fields".

 

Btw. you're sure that you haven't got more than 8000 fields in translation page :P ?

Link to comment
Share on other sites

Finally we got it sorted out.

It was a hosting problem after all. It seems that the increase of max_input_vars wasn't influencing subdirectories too, only directories.

My programmer decided to modify .htacces. Another option was to notify the hosting provider about this.

So if anyone will have this problem in the future they should check this also with their hosting.

Link to comment
Share on other sites

Finally we got it sorted out.

It was a hosting problem after all. It seems that the increase of max_input_vars wasn't influencing subdirectories too, only directories.

My programmer decided to modify .htacces. Another option was to notify the hosting provider about this.

So if anyone will have this problem in the future they should check this also with their hosting.

 

thanks for the information, so the problem is solved as you said. Do you know what you programmer changed in htaccess file?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...