Problem with language settings in Version 3...

brezel

I have noticed something. In the versions 3... (for example 3.1.10) more often errors are displayed because German language files are not found. In paths or file names then a "de" for the German language is missing. For example in SimpleGallery and in TinyMCE4. The file names in question are generated within the Extras. Since obviously the "de" is not found, an incorrect file name without "de" is generated. The language output then falls back to the default values (mostly English).
The installation language for me is German and where I can in the backend, I have also set the language to German.
Can I still set something somewhere, or must this be fixed in EVO.

Translated with www.DeepL.com/Translator (free version)

fourroses666

Maybe you can post the error(s)?

Seems a german langfile is there for SG and probably for TinyMCE too
https://github.com/Pathologic/SimpleGallery/tree/master/assets/plugins/simplegallery/js/lang

bigmike

Es sieht so aus, als ob in Version 3.+ bei der Manager-Sprache nicht mehr „german“ benutzt wird, sondern die Abkürzung „de“ . Deshalb funktioniert bei allen bestehenden Extras die Spracheeinstellung nicht mehr, da sie z.B. für Deutsch die Bezeichnung „german“ erwarten.
Es müssen also alle Extras mit Sprachwechsel auf die neuen Sprachkürzel umgeschrieben werden …

English:
It seems that in version 3.+ the setting for manager language is no longer "german" but the abbreviation "de". This is why the language setting no longer works for all existing extras, as they expect the designation "german" for German, for example.
All extras with a language change must therefore be rewritten to the new language abbreviations ...

cimt67

Hello, you should update to Evolution CE 3.1.12 (sooner or later) and update all snippets/plugins via "extras" then there should be no more error messages!!!???

SG is in German...TinyMCE4 stays in English no matter what language you choose!

I haven't updated from 3.1.10 to CE 3.1.12 yet it might be a little tricky.
Maybe fourroses666 has experience with it!?

MattiN

cimt67

The fact that the language in TinyMCE cannot be changed is really not nice.
I currently solve this simply by overwriting the English language file with the desired language (in my case German).
That shouldn't really be the solution, but it helps until the problem is hopefully solved one day.

fourroses666

cimt67 I haven't updated from 3.1.10 to CE 3.1.12 yet it might be a little tricky.
Maybe fourroses666 has experience with it!?

Its really simple. Just edit Updater in Plugins. Configuration tab Version needs to be: evocms-community/evolution
Then clear EVO cache in the manager and refresh the dashboard. You will see the update button.

cimt67

Hi Marc,
Good to hear... 1.4.17 to CE 1.4.20 I had done it that way too 😀

with 3.1.10 ... had only read in the Russian forum (with translator) that it is a bit more complex with composer!

fourroses666

You don't have to use Composer to update EVO. I don't use Composer aswell. Don't think that will ever change.
There is the installer script and the dashboard Update button.

Some new plugins like TinyMCE5 needs to be installed with Composer.
It would be possible to add it to the Extras/Add-ons but then an installer needs to be made of the package.
Some packages seems to need modxAPI and then you need Composer on the server.
I don't think its the way we are heading in the future anymore, not sure. We as non-tech are dependent of developers and their choises.

cimt67

Graffx Design

Hi Marc,
Now I have the answer I didn't want to hear: https://github.com/evocms-community/evolution/issues/147#issuecomment-1199817773

I mostly create small websites on small hosting packages where installing Composer doesn't work. But even if I could install it, i don't see any benefit for me... so back to Modx...
but with a crying eye!

BBloke

I've jumped in on it. I think there is a blank spot in my head in understanding the user models between v1.4 and v3 and why you need the MODxAPI.

So I've asked why it can't be included by default with the core of v3. That way all you would have to do with your FormLister v1.4 call is change the model parameter accordingly (as well as UserHelper plugin).

cimt67

BarnsleyBloke

Hi BBloke, i don't understand "pathologic" either or should 3.x become a CMS for Backend-Developers!?

YES, every PHP-Developer should work with Composer, but not a user who needs a CMS!

"pathologic" writes:

If you cannot use composer with your hosting, then create local copy of your site, run composer commands you need and then upload core/vendor folder to your hosting.

That wouldn't be a good solution for most of the Frontend-Developers and Webdesigners here!?

BBloke

Pathologic has done a great thing with the bridge. It's sadly the separation of versions that has led to FormLister needing it.

Don't forget FormLister is a replacement to WebLoginPE, which it does wonderfully.

It's just the new v3 users which requires the bridge which fundamentally means there's a potential for two versions!