Does your server set the Content-Security-Policy header? If so, you need to add at least script-src 'unsafe-eval'. As other places also need inline, it probably should be script-src 'self' 'unsafe-inline' 'unsafe-eval' at the end.

It's either in the Apache httpd.conf, or for Nginx a server{} block, or an .htaccess file. But if you don't know that then you probably also didn't add the header there ;-)

Anyway, you can find out whether the header is sent or not and what it contains using
curl -sviI https://YourDomain

Note that the output is different between http and https and the last character of the options is a capital I (i) not l (L).

Last edited by erAck (2019-02-13 10:53:37)

Well, try the curl command I gave or continue to poke about in a fog. If the curl output contains the Content-Security-Policy header and that does not list the mentioned script-src then that's very likely the cause. If there is no Content-Security-Policy header then it's something different. At least you'd know then.

https://piwigo.org/forum/viewtopic.php? … 67#p170467

I'm also seeing this message in history

Notice: Undefined index: day in /var/www/vetiraq/admin/stats.php on line 294

I hate to ask, but does it make any difference that I have another Piwigo site on this same server working fine and I have changed nothing since the two were installed

I have attached the Curl results advised to do earlier

ourlifeinpixs site has no problems
vetiraq has the viewing user profiles issue

both hosted on same server installed same day
vetiraq worked fine until about two weeks ago now, maybe longer

Thanks for any help