Translations for Modules in Oxid 4.9

Hey people,

Is there something new to the translations in Oxid 4.9 ?
My backend part isn’t translated anymore.

It shows me for example

ERROR: Translation for SHOP_MODULE_myKey not found!

My file, stored in:

out/admin/de/file_lang.php has the specific keys.

Any ideas?

your path is deprecated and 4.9 doenst support some deprecated functions anymore
use application/ instead of out/

[QUOTE=vanilla thunder;149646]your path is deprecated and 4.9 doenst support some deprecated functions anymore
use application/ instead of out/[/QUOTE]

i’ll give it a shot, hold on

So, i stored my translation-file in:

/modules/application/admin/de/mymod_lang.php

but it is not triggering. I cleaned the cache and reloaded. Still a path-error?

Hi dfu,

have a look at this one:
http://wiki.oxidforge.org/Downloads/4.7.0_5.0.0#Module_handler_changes

The translation files for the admin panel will be moved from modules/modulepath/out/admin/ to modules/modulepath/views/admin/.

Regards

[QUOTE=Marco Steinhaeuser;149652]Hi dfu,

have a look at this one:

Regards[/QUOTE]

Thank you very much :slight_smile:
That did the trick.

Also, is there any source where I can find the developmenet-changes?
It seems like “oxConfig::getParameter” is not supported anymore. Looking in the class-reference, it is still listed and not marked as deprecated.

I was looking here:
http://docu.oxid-esales.com/CE/sourcecodedocumentation/4.3.0.26948/classox_config.html#a1fc86da9374367a5ce322da1c56925bf

Yes. AFAIK, changes are still about to be collected:

Also at OXIDforge, you’ll find a list of deprecated and removed methods etc…

Best!

[QUOTE=Marco Steinhaeuser;149655]Yes. AFAIK, changes are still about to be collected:

Also at OXIDforge, you’ll find a list of deprecated and removed methods etc…

Best![/QUOTE]

I had a look at this page. So oxConfig::getParameter is deprecated and will be removed in the next build. But there is nothing like “see also:” or anything like this. I assume, Oxid implemented a new way to get params, right?

[B]as an example:[/B]

$oSofort->setSuccessUrl( oxregistry::getConfig()->getSslShopUrl().'?cl=order&fnc=continueExecute&transactionid=-TRANSACTION-&orderid='.$oOrder->oxorder__oxid->value.'&force_sid='.oxConfig::getParameter('force_sid'));

// call to undefined method: oxConfig::getParameter () …
But i don’t think i have to use $_GET… right?

Hey,

my translations for the frontend and backend are screwed up. Both with Translations not found-Error.

The translations for the backend were always located under [B]inspirito/MODULENAME/views/admin/de/deposit_lang.php[/B]. Until version [B]4.8.7[/B] everything works fine, but after upgrading to [B]4.9.3[/B] i got errors about missing translations.

Cleaning /tmp folder and reactivating module had no effect.

Anyone an idea?

Kinda regards

Hello again,

after i checked some modules compatible with 4.9.x i found out, you have to put the language files

  • for the backend to vendor/modulename/[B]application/views/admin/de[/B]
  • and for the frontend to vendor/modulename/[B]application/translations/de/[/B]

I moved my translations to this folder, cleared the cache and reactivated the module and got translations in the backend.

:slight_smile:

Additionally, to clear this up because it’s even more confusing:

[ul]
[li]If you actually [B]have [/B]an “application” folder, put module_options.php in application/views/…
[/li][li]If your module [B]does not have [/B]an “application” folder, you can just leave it in /views/…
[/li][/ul]

I think this has to be documented clearly somehow (or remove legacy support completely). Would be glad if someone could put this in the wiki.

  1. Maybe here:
    http://wiki.oxidforge.org/Tutorials/Create_a_backend_module_-_1._Getting_started

Note: This Tutorial is five years old now.
(I tried to register/signup and edit the article, but the SSL certificate seems to be broken.)

  1. Or here:
    http://wiki.oxidforge.org/Features/Extension_metadata_file

Hi,

[QUOTE=dmersiowsky;162312]I think this has to be documented clearly somehow (or remove legacy support completely). Would be glad if someone could put this in the wiki.[/QUOTE]

I am 100% with you. There - at least - shall be a documented “king’s road”.

[QUOTE=dmersiowsky;162312]
(I tried to register/signup and edit the article, but the SSL certificate seems to be broken.)
[/QUOTE]

I will not put any effort into the old wiki. The new OXIDforge can hopefully published as closed alpha soon(ish).

Cheers

i really want it and search for many website to get the right info . Many thanks