Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #938634

    Hello,
    I was following your instructions on this thread – https://kriesi.at/support/topic/polylang-copyright-footer/
    In order to have the footer language-sensitive.

    I was working for text, but my current footer looks like this:
    © Maratone Soundsystem • <a href="http://originalreggae.de/impressum/">Impressum</a>[nolink] • <a href="http://originalreggae.de/kontakt/">Kontakt</a> • Website design by <a href="http://www.gilingo.de">Gilingo</a>

    With that footer I got an error:
    Your PHP code changes were rolled back due to an error on line 582 of file wp-content/themes/enfold/functions.php. Please fix and try saving again.
    syntax error, unexpected ‘http’ (T_STRING)

    Any way around it?

    Thank you in advance,
    Elad.

    #938636

    What do you mean by language sensitive footer.
    Your are working with polylang to have different languages on your page.

    You can activate shortcode support of polylang via your functions.php of your child theme

    function polylang_shortcode($atts, $content = null)
    {
    	if (empty($content))
    		return '';
    	extract( shortcode_atts( array('lang' => ''), $atts ) );
    	if (empty($lang))
    		return "<h3>You must specify 'lang' using shortcode: polylang</h3>";
    
    	return ($lang == pll_current_language()) ? $content : '';
    }
    add_shortcode('polylang', 'polylang_shortcode');

    from that time on you can edit different languages in Enfold input text fields like:
    [polylang lang="en"]Whatever you like here[/polylang][polylang lang="de"]what ever in german[/polylang]

    the[nolink] is a different shortcode which disable footer notice to kriesi source of the theme.
    you see here what i mean –

    [polylang lang="de"]
    © Maratone Soundsystem • <a href="http://originalreggae.de/impressum/">Impressum</a> • <a href="http://originalreggae.de/kontakt/">Kontakt</a> • Webseiten Design durch <a href="http://www.gilingo.de">Gilingo</a>
    [/polylang]
    [polylang lang="en"]
    © Maratone Soundsystem • <a href="http://originalreggae.de/imprint/">Imprint</a> • <a href="http://originalreggae.de/contact/">Contact</a> • Website design by <a href="http://www.gilingo.de">Gilingo</a>
    [/polylang]
    [nolink]

    or all the things which are the same can stay the differences have to be in that shortcodes:

    
    © Maratone Soundsystem • [polylang lang="de"] <a href="http://originalreggae.de/impressum/">Impressum</a> • <a href="http://originalreggae.de/kontakt/">Kontakt</a> • Webseiten Design durch[/polylang][polylang lang="en"]<a href="http://maratone-soundsystem.net/imprint/">Imprint</a> • <a href="http://maratone-soundsystem.net/contact/">Contact</a> • Website design by[/polylang] <a href="http://www.gilingo.de">Gilingo</a>[nolink]
    

    you now better your links – you see now how it works

    #938637

    Ach – du solltest dich beeilen mit dem umsetzen der DSGVO – auch auf der Gilingo Seite selbst – obwohl da schon ein Zertifikat installiert ist, ist noch vieles in den Datenbanken – wahrscheinlich inklusive webseiten url und wordpress url noch auf http eingestellt.
    Kontaktformulare nur noch mittels TLS (https) und so weiter …
    Cookie Notice ist ein nettes Tool um Cookie Hinweise zu setzen.

    #938638

    Hey,
    Your code works perfectly! thank you so much.

    I don’t understand the 2nd part though, German is not my native language.
    What is DSGVO?

    Do you mean that I should force https on everything?
    One plugin I use – iThemes Security has that feature.

    Thanks,
    Elad.

    • This reply was modified 3 years, 1 month ago by  VJLoops-GT.
    #938640

    sorry – i thought you are concerning to that golingo.
    If you have certs installed it would be nice to have all on secure handling via port 443 TLS. So force https would be best to have.
    thats the new data protection law for europe – with a lot of privacy policy notes etc. pp.

    #938647

    I am actually behind gilingo – you are right.
    But my husband wrote all the text :) I am in charge of the backend, so it definitely concerns me… I hope I got it right.

    So you say if I force https over everything, that fits the new law?
    What about the contact form? is there a way to secure the Enfold contact form?
    Is there another solution to enforce this law?

    Sorry for troubling you with this,
    Every time new laws pop up and I miss them :) like the law with the Impressum that can get you in trouble if you don’t have one.

    Thanks again in advance for the kind advice,
    Elad.

    #938746

    All websites with a contact form needs to be updated to TLS (former SSL) to enshure crypted sending.
    Some of the german lawyers say that it is mandatory to have a checkmark on contact form that the sender had read the privacy policy statement.
    There had to be a lot of new references on Imprint to Data Handling.
    You can see that on my Homepage ( sorry it is german) on Kontakt and Imprint. (https://guenterweber.com)
    Because DSGVO is a very complex thing – and as a showcase for my customers how it could be look alike – but don’t had to look alike i set this :
    https://guenterweber.com/datenschutz/

    you see the link on the bottom : https://dsgvo-muster-datenschutzerklaerung.dg-datenschutz.de/?lang=en

    where you can generate Your GDPR-Compliant Privacy Policy

    #938805

    Wow such a massive request overall for every simple website, I’m sure 50%+ of Germany’s websites don’t even know what that is :D

    but thank you so much for letting me know.
    I’ll add the Datenschutz section.

    I bet some lawyers just look for websites without it and get easy money..

    #939028

    Hi VJLoops-GT,

    Glad you got it working for you with the help of Guenni007! :)

    If you need further assistance please let us know.

    Best regards,
    Victoria

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.