Language file overrides not working

-- HikaShop version -- : 2.3.4
-- Joomla version -- : 3.3.6
-- PHP version -- : 5.4.31
-- Browser(s) name and version -- : 33.1
-- Error-message(debug-mod must be tuned on) -- : Various messages when debug mode is turned on but none seems to refer to the problem I am experiencing with the language overrides.

I have written a number of overrides in the language overrides file (Eng GB). Until recently it worked perfectly, but now the normal wording is appearing on the front end of the website, not the override wording. I have checked the code in my overrides (for example checking that all " are closed) - there doesn't appear to be any problem there.

Can you think of anything else that might be causing this problem and suggest a way to fix it?

Thanks

Hello,
The solution will probably be to active the Joomla debug mode ("Administration->Global configuration->System->Debug System/Language").
You should then see the debug data at the bottom of each page and on that page, you should get a debug of the translation file of HikaShop and the override file and it will tell you if there is a problem with them and if so, on which line is the problem.

Thanks. I switched debug language to 'yes' but then only got blank screens at the front end of the website - no debug messages or error messages.

Then activate as well the "error reporting" option of the joomla configuration and you should get the error messages.

I have not got this error message:
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 130968 bytes) in /home/myname/public_html/libraries/joomla/language/text.php on line 896.

Seems strange - surely not much memory will be taken up by the language file itself... so it must be something else.

Any suggestions?

Hi,

This seems to be more a Joomla issue than an HikaShop one.
I tried to see the line of the error in the indicated file on my local but I don't have 896 lines in that file.

In all cases, you can increase the memory size allocation in order to no more have this problem.

I think this fatal error is related to debug plugin, which is very resource hungry.