hello dear DenisChenu, jelo, holch
first of all - many many thanks for the reply and all the ideas that you share
- the server it is pretty slow and old: - it will be replaced in winter-season..
- i can install limesurvey in an other setting - no problem here: i will take your ideas and advices into account - thanks for all your thoughts that you share.
- @holch and jelo:
your ideas were very interesting:
I would probably focus on other aspects first, as it works fine with me for quite some time now. Of course, as Jelo says, any update in one of the two applications could start causing problems.
good idea: i updated some wordpress-plugins and added another plugin on Wordpress. Maybe this caused the issues.
To minimize work and trouble, install wordpress and limesurvey side by side. You then need to redirect from YourDomain.TLD/ -> YourDomain.TLD/wordpress/, but you have clean folders and don't cause delays and loops when it comes to URL accessing.
Just use /w/ for wordpress and /s/ for limesurvey will keep the URL short.
i will try to do so. Many thanks for these ideas.
by the way: holch you are right: with FF i can get to the login site - but not any furhter...
as for the GDPR: many thanks for these hints:
note: this is a beta-beta-beta site: but i am willing to fulfill all the GDPR-things.
however I can say that I can't imagine there are many users that would willingly enter any account credentials on an unencrypted page at this point in time. To be honest all of the modern browsers visiting a site will either block the connection or throw up some sort of warning when being forced to use http anyway. But as mentioned above: the site is in Beta, the server itself will be changed - and all the site-concepts will change soon.
btw: as for some fixes in that sort of thing: can we fix the https (there are free certificates one can use like
zerossl.com/free-ssl/
for example) and furthermore - what about to look into a simple free gdpr/cookie consent script like eg here
www.freeprivacypolicy.com/cookie-consent/
above all: i will make sure that the GDBR authorities will be able to go even on my small website that for any reason - if they are interested in GDBR-Things. like logging user data (like requiring visitors to login, or any kind of cookie tracking).