'Language' question...

Just curious about how ocPortal uses language files.  I was fiddling with my galleries, slowly working on getting the 'look' as I wanted it.   In the list of galleries, for any given user it said "Personal Gallery of username'.  I just wanted it to say 'usernames's Gallery'.

This was a big learning curve.  All the way into a function that pulls the text out of the translate table.  Heck, how did it get there?   The theory/concept behind having language files, AND putting all that into a database to look up, escapes me.  If anyone knows how this works so it is a bit more simple to sort through next time a small text change needs to be made, it would be much appriciated.

In all that, as a bit of side tracking, I learned of the function _get_where_extend (or something like that).  I couldn't figure out how you could pass down to it, a 'WHERE' that would be a non-equal statment.  Seems it's either =NULL or = something.

Paul
Busy exploding my brain with code. 

galleries.ini >> against 'PERSONAL_GALLERY_OF=' change the language file to whatever you want it to read …

 

---

The 'function_get_where_extend' thingy. No idea. Not an area I wander into with my eyes open!

Fletch said

galleries.ini >> against 'PERSONAL_GALLERY_OF=' change the language file to whatever you want it to read …

It would seem that easy.  But it is a bit more than that.  Because that bit of language is used and stored in the translations database.  So if users already have a gallery, it will still use the old form of 'PERSONAL_GALLERY_OF… unless you go into the translations db and edit them.

Yes. Personal galleries get saved and the regular title field is used after that point. But you can go back and edit old ones via the normal edit gallery screen(s) if you wish.

_get_where_extend is used internally (anything starting with an underscore probably isn't useful).
It's used by query_select/query_delete/query_update which are nice functions to avoid you having to write SQL.