Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter Alex

    (@charityimmos)

    Thank you so much!

    Thread Starter Alex

    (@charityimmos)

    Hat sich erledigt. Es lag am falschen Template. Template gewechselt, Kommentarfeld und Kommentare sowie verlinkte Beitr?ge werden wieder angezeigt.

    Thread Starter Alex

    (@charityimmos)

    Hi @estatik,

    thank’s for asking. Yes, I still have the same issue. Some words can not be translated. Watch here… This is the requiery field of a single page of Estatik. Almost anything within this page is translated properly, except of this chack-box below. “I agree to the Nutzungsbedingungen und Datenschutzerkl?rung” should be translated into “Ich stimme den Nutzungsbedingungen und Datenschutzerkl?rung zu”.

    Furthermore the field “area, m2” should be translated into “Wohnfl?che ca.”. Now it’s translated into “Fl?che, m2” which is not good enough.

    With Loco Translate, I can not translate these examples into my version. It just doesn’t work…

    Thread Starter Alex

    (@charityimmos)

    Nach dem Update wurde zumindest bei den Blog-Beitr?gen die Standard-Einstellung des Templates ge?ndert. Habe nun manuell bei jedem Einzelbeitrag das Template unter Einstellungen im Elementor-Editor von “Standard” auf “Full Width” ge?ndert. Das hat funktioniert.

    Thread Starter Alex

    (@charityimmos)

    Hi,

    I did, but didn’t receive a confirmation mail so far, so here is my issue…

    I try to translate some english words of Estatik into german with the plugins LocoTranslate and Preffered-Languages. It works quite good. I could change some words from automatically translation into my version. But it seems like, not all words can be translated into german. Some from the requiery field for example, like the sentence “I agree to the %s and %s” can not be translated into german language, even not with Loco Translate. Or the Field “area%s” is translated into “Fl?che, m2”, which is not as I want it to be translated. The meaning “Fl?che, m2” is not precise enough in german language and could be a reason to get a warning from a lawyer etc. So both examples need to be translated, otherwise I am sure, I will get an expensive fine from german lawyers…

    I hope to hear from you soon. Thank you so much!

    By the way… great plugin so far. I hope to grow, so I can upgrade it soon. Thx!

    Thread Starter Alex

    (@charityimmos)

    Hi, Estatik!

    Thx for your support! But I think, it’s not an issue with the SG Speed Optimizer. I disabled the plugin, but nothing changed with the layout. It was still on the left site. I even tried the troubleshooting mode / health check, disabled all the plugins and tried to activate them one by one. The Layout changed and filled the full screen, but the complete website is shown in a different style as it should be while the troubleshooting mode is activated. Once I disabled the troubleshooting mode again, the website is shown as it should be, but the layout of the searching list fom Estatik is still on the left then.

    So I swapped the theme from OceanWP child theme, which I am using currently, to twentytwentyfour and even OceanWP mother theme. In both the searching list of Estatik is shown properly. I mean, throurgh the full screen and not like with the child theme on the left.

    So I think, it’s an issue with my OceanWP child theme. But I do not know, what to do. Again… with the mother theme OceanWP the layout of the searching list is through the full screen. And I do not want to change my OceanWP-child theme to another one, if it’s possible.

    Thread Starter Alex

    (@charityimmos)

    @estatik: Sry, of I mean the function: “enable/disable collapsed description”.

    Thread Starter Alex

    (@charityimmos)

    By the way… I turned off the construction mode. My website should be online now. Maybe it’s easier fpr you to check out the issue.

    Thread Starter Alex

    (@charityimmos)

    Thx @estatik. Unfortunatelly it didn’t work. I disabled the function “difault archive templates” but nothing changed… Do you have any othr advice?

    Thread Starter Alex

    (@charityimmos)

    No but next to LocoTranslate, I use the plugin preffered languages, which I prefer. Should be the same as polylang but for me much easier to handle. Would you agree?

    Thread Starter Alex

    (@charityimmos)

    Leute Thema hat sich erledigt. Ich habe versehentlich im Warenkorb statt des offiziellen Woocommerce Shortcodes ein Tamplate von “Essential Addons” verwenden. Da lag der Fehler. EA ist wohl nicht kompatibel mit Germanized, daher kam der Fehler. Nachdem ich den Shortcode [woocommerce_cart] im Warenkorb eingefügt habe, wrude automatisch ein Tamplate generiert, was etwas anders aussieht jedoch ohne Fehler ist. Ich bin mit der Gesamtoptik sehr zufrieden. H?tte ich mal vorher den Systemstatus von Woocommerce gechekt, dann w?r mir eine Menge Arbeit erspart gewesen. Unter: Woocommere>Status einfach Systemreport abrufen. Dort werden alle Fehler mit L?sungsvorschlag angezeigt, sofern welche erkannt werden. Damit schlie?e ich dieses Thema.

Viewing 11 replies - 1 through 11 (of 11 total)