kulakaula

Same to you!
Peter

Hi,

this is Siteground’s support answer, perhaps it is useful for you:

”
The issue was caused by the fact that access to the desired files was not allowed. As per your developer’s notes, I added the following code to both sites’ .htaccess files and the arrow is now properly shown:

Code:
<IfModule mod_setenvif.c>
<IfModule mod_headers.c>
# mod_headers, y u no match by Content-Type?!
<FilesMatch “\.(gif|png|jpe?g|svg|svgz|ico|webp)$”>
SetEnvIf Origin “:” IS_CORS
Header set Access-Control-Allow-Origin “*” env=IS_CORS
</FilesMatch>
</IfModule>
</IfModule>
<IfModule mod_headers.c>
<FilesMatch “\.(ttf|ttc|otf|eot|woff|woff2|font.css|css|js)$”>
Header set Access-Control-Allow-Origin “*”
</FilesMatch>
</IfModule>

The applications are not directly linked but the original URL is actually used for the staging copies and is replaced using mod_substitute with “staging*”.
”

Thanks again for all your help, currently the problem is fixed.
What actually might happen if the staging sites are pushed live, would have to be seen.

Regards,
Peter

Hi again, Frank!

The Siteground support guy asked me to check with you whether either of the changes you suggest would cause issues when the staging site is pushed to the live (public) site?

What do you think?

Regards,
Peter

Thanks a lot,
I am going to ask Siteground support as you suggested!

Again, many thanks for your quick response!

Peter

Thank you for your answer,

regarding your question – I don’t do anything special, I would not even know how to!
Would it be helpful if I sent your reply to Siteground’s support?

Peter