Are you guys sure you’re running a stable Zammad version?
Are there any modifications on the Zammad source code…?
Reason I’m asking:
I can’t reproduce this on the most current package installation
I can’t reproduce this on a fresh pulled hosted instance
Is there anything between your Zammad hosts and you?
For exmaple a CDN or a proxy (except Zammads) that might rewrite stuff?
Technical antivirus software could do too (if it would, that be odd, but you can never know).
All my clients are having the same problem so it can’t be a browser or antivirus problem (I use Mac and Windows, one with antivirus the other one doesn’t)
I use the typical configuration for zammad install, nginx and installed from deb package.
There’s no modification to the code, and it would be rare that all of us made the same modifications to have the same problem, I will try to update the version, even though I install the package 5 days ago, so it seems to be the last version.
I think we are good on my end. I think what was causing it for us was not updating fully the data base. I didn’t noticed that we were getting ruby errors but once I cleaned the errors up, then reinstalled zammad I was able to get the button working.
I fix it this way, but I detect another error related with “linking account” instead login, I get the same error, and the same<a href=""> is being generated, even tough the main login problem is fixed after clean installation.
if you find this in your file, but not in the source code of the webapp being delivered, recompile the app with: zammad run rake assets:precompile
this step does not apply to docker containers, as they should do this on every start
If you still have issues, just to be sure, you can do the following things
ensure this is not a caching issue (by proxy, browser)
run /op/zammad/contrib/packager.io/postinstall.sh to ensure all migrations have run
Hopefully this will help you.
Please note: The above only applies for the login buttons within the login page.
There’s a bug hitting the profile section (e.g. when you try to link any third party account (I totally ignored that in my pasts posts, sorry!)), that currently makes it impossible to link third party accounts:
We’re working on fixing this bug at the minute I’m writing.