hastibe

Like @jarledb was asking, though, is there a way that we can see a log of what logins / login attempts are being scored as, @andrewshu or @missveronicatv?

Thanks for the pointers! Looking forward to talking a look at the resources you linked to and seeing if I can get the template satisfactorily modified.

@gn_themes — thank you so much! ??

I don’t think Astra should be interfering, as that is a general theme and not a job board-specific one that could have CSS modifications to the job dashboard, so, my next thought is that you must have caching that needs to be cleared (result in the old CSS being loaded, without the modification).

After adding and publishing the CSS code snippet in the Additional CSS panel like you mentioned above, make sure to clear any caching via plugin and web hosting, and then check your dashboard when logged-in on an incognito / private mode window, to ensure that browser caching isn’t causing the issue, either.

@dcka — please add my vote, too. I think it’s really important that basic usability be given higher priority versus some of the very niche new features that are being rolled out. I also think it is way past time for there to be a roadmap with a general timeline of where and how quickly (or not) development of WPJM is going.

On this note of basic usability, though, please also make higher priority having the “Duplicate” menu option for jobs on the job dashboard, regardless of the jobs’ status — this was opened as an issue on the WPJM GitHub on June 22, 2023, and was closed this spring, but still hasn’t been implemented.

Hmm, it works for mine! Your job dashboard CSS must be modified. What theme are you using?

Hopefully, someone will be able to offer a better modification, but -if nothing better- you could use the CSS code snippet below (put it in your Additional CSS panel via your WordPress admin panel > Appearance > Customize) to hide on the jobs dashboard whatever the 3rd job listing menu option is (for published jobs, it is “Duplicate” until they reach the “Expires Soon” status, and then it hides the “Renew” option, but it still might be helpful–just make sure to test it thoroughly if you do use this, and note that a savvy user could always use the Inspect tool in their browser to unhide anything hidden via CSS, too).

/* Hides 3rd job post menu option of jobs on job dashboard */
#job-manager-job-dashboard > table > tbody > tr > td.job_title > ul > li:nth-child(3) {display: none;}

Just to clarify, it sounded previously like excluding pages from the cache might be working ( you wrote above that “When they click on ‘account’ they get their own role.”) is / was that ever the case, or -even with caching on for the page- did they still get the correct details when they went to the Account page?

But here is also the option in the first tab: Cache Login Page is on.
Shall I turn this off also?

On the LiteSpeed page I linked to, it says about the option: “This option will cache the login page. Normally, there is no reason to uncheck this option. However, if there is something that may identify a user on the page, this should be off.” Is there something that identifies the user on that page?

Please let us know about the questions above, and hopefully Ultimate Member support or other volunteers here will be able to chime in, as well!

Oh, and I noticed that you said the settings did work for the Account page (which you presumably excluded from caching) — are the pages where users are still seeing others’ usernames on pages not excluded from the cache? If so, you need to also include those pages, of course.

Alternatively, you might try turning off caching of logged-in users, as I suggested previously. See here: docs.litespeedtech.com/lscache/lscwp/cache/#cache-logged-in-users

Hope this helps!

Hmm, I’m only familiar with caching causing this issue. Have you reached out to your website host to see if there is server caching that they are doing? Or, perhaps you are using Cloudflare or a service like it, which also caches websites?

Ah, and, @jacquelinej, see the suggestions here for using Ultimate Member with caching (it even has a section specifically for LiteSpeed!): docs.ultimatemember.com/article/1595-caching-problems

Keep us posted! Cache gets regenerated quickly, so the reason deleting it doesn’t work is because the pages are being re-cached. If there isn’t a setting to not show cached pages to logged-in users, you also could try disabling caching for specific pages (your caching plugin should have a setting field to do that) where the issue is occurring or causes the problem, like your member Account page or Profile page, etc.

Anything that is caching or minifying JavaScript on your production website that maybe needs to be regenerated, which could be causing this, but not causing it on the staging environment?

Usually, it is caching on your website or server that causes that. Are you using a caching plugin or does your website hosting plan include caching? If so, see if you can turn off caching for logged-in visitors. If the plugin or website hosting plan can’t do that, they may have another suggestion / solution, or you may need to move to an alternative plugin or hosting plan of theirs.

In WordPress, all data is stored in the site’s database (usually a MySQL database). Other folks here may be able to provide more details and ideas, too.