HTML Logo by World Wide Web Consortium ( Click to learn more about our commitment to accessibility and standards.

Moving forward with Composr

ocPortal has been relaunched as Composr CMS. ocPortal 9 is superseded by Composr 10.

Head over to for our new site, and to our migration roadmap. Existing ocPortal member accounts have been mirrored.

Defining Duplicate Language Strings

Login / Search

 [ Join | More ]
 Add topic 
#96333 (In Topic #19134)

Community saint

To do or not to do?


I was wondering if it makes sense if during development of a new module or block if you have 1 or 2 words that are likely defined in another language file should you just redefine them (with a module specific prefix to avoid conflits) for the benefit of less overhead or should just require up the needed existing language file?

Example: I have new block that I want to add the 2 words comment/comments which i am sure exist somewhere in a language file but these would be the only 2 words I need from that other language file while I am already including a language file for my new module so if I put comment/coments into that language file I would save some overhead from calling up the members (or whatever other language file comment exists in) just for those 2 words.

what do you think would be the preferred method?
Back to the top

ocPortal's smarter than this. Each page has a self-learning language cache. On first load, it loads all require'd language files. It tracks what was used on the page. On second load, the page's self-learned cache likely has all strings, so it only needs to load that. If not (e.g. maybe a string is only sometimes used), it will load the files again, but continue to extend it's self-learned cache – so it will be perfect at some point.

Become a fan of Composr on Facebook or add me as a friend. Add me on on Twitter. Support me on Patreon
Was I helpful?
  • If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
  • If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
  • If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
  • If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Back to the top
There are too many online users to list.
Control functions:

Quick reply   Contract

Your name:
Your message: