I have found that the users I have setup and given access permissions with the Toolset Access module are not displaying the correct fonts for sections on the site . See screenshot for admin vs custom user role of same page. The admin is displaying correct.
Hello and thank you for contacting the Toolset support.
In order to exclude any possible conflict with another component of the website, please check if this issue appears when:
- Only Toolset plugins are activated. It will tell us if there is an interaction issue with another plugin.
- The theme is set to a WordPress default like Twenty-Twenty. It will tell us if there is an interaction issue with your theme.
If the problem disappears, start activating one at a time to track where the incompatibility is produced.
If that does not help identify the cause of the issue, we'll need to visit the page as an administrator and as a user with that custom role. Your next reply will be private to let you share credentials safely. ** Make a database backup before sharing credentials. **
Please let us know the page URL and what user or what roles to test against?
Thank you for the credentials. However, I don't know what other roles present different fonts. I checked with an logged-out user and I could not see any differences.
The issue is not reproduced on my side. Wither I logged in as an administrator or HR user, or without logging, I am getting the same fonts. Maybe that's only a browser cache from your side, can you purge the browser cache and try again?
Regarding your last question, I am not sure to understand. Can you share a URL where we can see this file field?
I have purged cache, but still I get different styles with logged in custom roles. See attached browser windows with same page but separate user roles logged in.
Without being able to reproduce the issue, I am afraid, I'll remain helpless. I tested again with 3 different browsers(Chrome, Firefox, Edge), but I am not able to reproduce the issue. The custom user role gets the same fonts as the administrator on your last screenshot(right window). I am using Windows 10.
Maybe the issue comes from a difference of system or browser, what is your operating system and the browser you tested with? I'll ask a team mate that has the same to test from his side.
