includes/languages/english/custom override not working

[Bostitch]

Thanks for your response.

I know where that line of text is coming from in the default file. However, the fact that the default file text is appearing, instead of MY text, is why I believe the override is not working correctly.

I realize that I can go into the default file and edit the core file to make it say what I want, but I thought the override was suppose to avoid altering the core files.

[TShooters]

Okay....you've changed that in your override shopping_cart.php file.
(That was what I meant... your custom/shopping_cart.php file.)
Then it goes in your includes/languages/english/custom folder. And you've
uploaded it and have it there? And your custom folders are named the same
as includes/templates/(your) custom folder?

[Bostitch]

All of my names are ok. I have checked and double checked, and then went back and checked again.

But I think I figured it out. I somehow lost my
define('TEXT_INFORMATION', ''); from my custom file.

So I guess it was taking the
define('TEXT_INFORMATION', 'You may want to add some instructions for using the shopping cart here. (defined in includes/languages/english/shopping_cart.php)');
from the default file.

So putting the define statement in my custom file seems to have fixed things.

Does that sound right? It would take a single define from the default file, but still use the custom file for any new defines that are listed there?

[DrByte]

Yes ... it was programmed that way because folks figured that deleting entire definitions would somehow magically remove the text.
They also often failed to upgrade their customized language files properly, thus things were getting missed.
Thus, the catchall offers some protection.

[Paraiba]

I was having exactly the same problem although my TEXT define was there. Still haven't worked out what's going on. My question though is, why on earth is that line in the php files rather than in the admin to make it easy for clients to change?

[Merlinpa1969]

the simple answer is that if things like this were stored inth eDB it would soon bloat the DB and would then add more queries on each page load, and that is one thing ZC DOSNT need is more queries per page.

[Paraiba]

OK, understand but it's inconsistent. Some things can be changed in admin others can't. If it's a sensible message that somebody just doesn't like then great, it's down to them to hack the code but when it's a message saying "you might like to change this" then surely it should be easily accessible via admin.