But this seems not to be CORS conflict but a Charset Conflict:
We Germans got it with our ö, ü, ä etc

Read here: https://kriesi.at/support/topic/german-umlauts-and-icons-arent-shown-correctly/

Login with ftp and look for wp-config.php

If there is in it:

define('DB_CHARSET', 'utf8');
define('DB_COLLATE', '');

– replace it with:

define('DB_CHARSET', '');
define('DB_COLLATE', '');

if it is not in the wp-config.php
just try first with

define('DB_CHARSET', 'utf8');
define('DB_COLLATE', '');

https://kriesi.at/support/topic/german-umlauts-and-icons-arent-shown-correctly/#post-864457

try first this above – only if it does not work go on reading
__________-

so you have ftp access to your root directory?
Login. Some ftp clients do not show hidden files on default it must be activated sometimes.
if the charset can not solve it maybe you try the CORS thing:
Filezilla f.e. under Menu – Server – list hidden files.
the htaccess file is a hidden file and has a dot infront of it and no extension.
you can download it – rename it to a file without dot and with extension txt so that there is htaccess.txt.
Open it with a good text editor: sublime text on mac or notepad++ for windows.
Add this code above to it if your provider server is on apache:

<FilesMatch "\.(eot|otf|svg|ttf|woff|woff2)$">
<IfModule mod_headers.c>
Header set Access-Control-Allow-Origin "*"
</IfModule>
</FilesMatch>

upload that file again to your root. rename the existing .htaccess to htaccess.bak ( or something you can remind well) – rename the newly uploaded file to :
.htaccess (without extension)

can you make a screenshot of what you think is not correct. When i look to your site with chrome or firefox or safari – all browsers are with no major differences

It sounds a bit as if CORS is the reason why – but i can not see such “glyphs” on your page.
if it is a CORS Problem ( Cross-Origin Resource Sharing ) you can solve it by adding this to your htaccess file on root directory of your installation ( if you are running on an Apache Server)

<FilesMatch "\.(eot|otf|svg|ttf|woff|woff2)$">
<IfModule mod_headers.c>
Header set Access-Control-Allow-Origin "*"
</IfModule>
</FilesMatch>

on IIS Server Installations it comes to web.config file:

<system.webServer>
  <httpProtocol>
    <customHeaders>
      <add name="access-control-allow-origin" value="*" />
      <add name="access-control-allow-headers" value="content-type" />
    </customHeaders>
  </httpProtocol>
</system.webServer>

ok – then i’m out here – sorry – you have to wait for mods now to solve the issue

this is better – and comes to quick css:

@media only screen and (max-width:767px) {
  .responsive #top.woocommerce-page #main .sidebar {
    display: block;
    border-color: transparent;
  }

  .responsive #top.woocommerce-page #main .sidebar .inner_sidebar {
    margin-left: 0;
  }

  .responsive #top.woocommerce-page #wrap_all .container_wrap_first .container {
    display: flex;
    flex-direction: column-reverse;
  }
}

i do not see how your enfold contact form looks like!
If you are familiar with using the developer tools of a browser you can see the IDs and classes the form element and the input fields got from CF7.
Here you have a few hints: https://contactform7.com/styling-contact-form/
And there are some addons to CF7 for styling it. – But i think you will not need that.

sorry wrong place – i like to answer to a different posting.

The child is always the same. And does not need to update. That is just the trick – to keep all the changes you have made to the theme.
So now you have on your themes folder an enfold , enfold-old and enfold-child-old folder but no enfold-child folder ?
What was the last theme you have activated before the wsod ?

Do please a complete new upload. Not overwriting an existing enfold folder.
That is what that plugin “Update Theme and Plugins from Zip File” does if you mark to “Enable saving a backup copy of old version… “

All my CF7 installs do send ( even with upload ) E-Mails.
It is usually a user error and not an application error.
Very rarely the sent e-mails end up in the Junk E-Mail folder. However, this has more to do with the fact that the recipient’s e-mail does not match the domain url.

genau – und was ich beschreibe, hilft dir diese Zeichen zu verwenden, ohne dass Sie dir das Layout zerschießen.

ich denke du hast das gleiche Problem wie hier: https://kriesi.at/support/topic/in-content-crash-page/
du benutzt größer gleich oder kleiner gleich Zeichen in deinen Texten, das wird aber als anfang bzw ende eines Tags interpretiert.

Bei manchen ALB Elementen wird es reichen ein Entity zu benutzen: http://unicode.e-workers.de/entities.php
die besagten Zeichen oben aber bedürfen der extra Fürsorge

Well, that really seems to be a German problem, that you try to comply with the law.
I don’t think it’s actually eaten as hot as it’s cooked.
But – you are right – for me as a German it is probably also too important to correspond to that.

so i started here my thoughts on how to fullfill all aspects of the GDPR (DSGVO)
Maps: https://kriesi.at/support/topic/google-maps-gdpr-dsgvo/

Same thing with youtube films : https://kriesi.at/support/topic/checkbox-to-show-lightbox-or-not/#post-1011241

See how it works: https://webers-testseite.de/weber/youtube-links/

On Google Font load – i do it localy : the copyright is clear on googel fonts – they allow to download and do a selfhost.

i had only reduced the amount of # because i had no desire to always insert 3 before 3 after.
Of course you can customize this list in the plugin for your purposes.

'#singlequot#'      => "'",
is taking place:
'#34#'      => "'",

but also add new ones etc.

by the way – is this solved for you: https://kriesi.at/support/topic/tag-archive/

Where did you get the shortcode from? – so why don’t you insert the link first to that source and then copy/paste the shortcode?