Override plugin's lan files

[rica-carv]

Is there anyway i can override a plugin's lan files without really overwritng the own plugin lan files?

For instance, like it's donne for templates inside a theme, but for language files?

[tgtje]

@rica-carv : i read it, but unable to get (in my mind) what your question is, eg. the idea behind the goal.
templates or layouts ?
I understand that a problem or idea in your own mind (in your native lang) is sometimes hard to describe in another.
Since i experimented a lot with things related to/with language, can/will you explain more in detail (also related to the new language use).
Like is it creating a template but call for lang define or...?

[tgtje]

@ok think i got it,
Now suppose you have a template.
You know from earlier you can add templates for override in theme folder. (copy plugin with new template/s)
Now keep the original ones (in any which way).
Yes you would need to alter some lan/calls (eg to new ones), but the trick is to (iff original has to be 100% untouched)
to re'style' the template either change define call (needs new lan defined).
Now because you have ONLY the changed template you ONLY need to ADD the 'newer'calls+define text in your language folder
What is not there is not displayed..ea new template asks for new defines. read path stays same. Original active, not realy touched).
It all just out of my head. Think it will work. (Just try with 1 define + call, and you would need enough)

For the newer lang coding in templates with (brackets) { ... } the language files become special (front/admin/global)
Want to take a closer view on that go to my repos try Vstore ( master and second branch > compare and see what i mean

[rica-carv]

@tgtje It could work, if there was a "rule" for shortcodes so that lans should not be harcoded inside them, but even a lot of core shortcodes have lans harcoded inside them, making the templatization or customization of lans for those shortcodes a real hard job, and only possible by rewriting the shortcode via the theme_shortcode file....
And again, that would be a overhead just for changing a couple of lan's...

Why is not a lan overriding file inside theme, just like is for templates?

It's really hard to pick a way to go, because you can have lan's everywhere right now. In templates, in shortcodes, or even in the php code itself, harcoded in output....
And if you can sometimes workaround with shortcodes, in php code is really hard to customize without rewriting the whole code....

[tgtje]

That i understand, easiest way is/would be; because you need another text on a few 'lines' you have to add those anyway, why not use standard lan define with that text and add number 600 or so to it (old style) define("MY_MENU_600", "Anúncios,"); and replace lan call with MY_MENU_600 (example); (org plugin has to be present for path) and new defines stored there.

yep.. and the > you can have lan's everywhere right now is still evolving> base / start was all hardcoded and then translation happened..

Alternative way i used such trick around 5-6 years ago with gallery plugin. I wanted 2 gallery systems to work alongside ( with same name one big mess), so i used notepad++ etc. and search all names 'gallery/alike' and changed those into portfolio. throughout the entire gallery plugin (pluging folder/files ...all).
ehh voila had a working Gallery and a working Portfolio with own mediamanager etc.. next aside each other.
Think took me about an 1.5 hour, some bugs (typo or forgotten word) after testing, fixed and done.
Of course an update ...work ;-)

[rica-carv]

@tgtje We're walking in circles here.

Just to clarifiy, you can use own defined lan's in themes, like you stated, ie: define("MY_MENU_600", "Anúncios,");
But now i have a shortcode in the plugin like this:

	public function sc_news_comment_label($parm=null)
	{
		return ($this->news_item['news_comment_total'] == 1) ? COMLAN_8 : LAN_COMMENTS;
	}

The only way to customize this LAN's output is to rewrite & override the shortcode inside my theme like this:

	public function sc_news_comment_label($parm=null)
	{
		return ($this->news_item['news_comment_total'] == 1) ? MYLAN_1 : MYLAN_2;
	}

Now imagine the overhead for doing this for several shortcodes, when it could be donne just by overriding that LAN's....

And anyway,, i already refered your alternative of copying the plugin to another new plugin, it's also overhead just because a few lan's changes....

[tgtje]

Thought about it, (also took a look at competitors that seem to use such like Joo..., they have coded stuff= work), and iff e107 override function will work, on lan ? do not think.
The only downfall i see is without too much investment and when NO other shortcode in plugin or relationships!! (eg ONLY used HERE) is an altered language file.
You only change the visual outcome, no coding (comment the original text out).
Else see no way to get fast results without extra coding. But that's my believe, maybe others will join the discussion.

[Jimmi08]

Hi, guys...
If I need this - and I needed it, I put those LANs to preferences (with multilan option ON). One pref with type json could be needed for all translations. or one LAN, one prefs (easier coding without custom method)

Advantages:

• the code is plugin independent
• you can customize translation in admin area if you dislike it
• prefs can be cached by default, so it can be really quickly. You can use them as static variable for classes with key similar to LAN constants (it is similar to newest array approach - you just get array from json in prefs).
• you can put default translation in xml/install.xml file
• or you can load default values from real LAN files in plugin_setup file
• you can create your own shortcode like {MYPLUGIN_LAN} working similar way as core {LAN} shortcode for using in templates
• not mention all advantages of admin UI for editing, searching etc

If you still need LAN files, you can generate them easily from admin area (similar way like lan packs are created)

Override functionality looks awesome but there were changes during time and there was no reaction on me reporting issue with overriding handlers.