Padlocks are missing from the enter a record pages... again!

Few days Back I also face same problem. Let's explain how I solve this problem. It sounds like the option to lock specific fields is inconsistently available on the desktop site. This could be due to a few reasons:

1. Browser Compatibility – While Firefox generally supports most web functionalities, some sites optimize their features for Chrome or Edge. Try using another browser to see if the issue persists.

2. Cached Data & Extensions – Corrupt cache or conflicting extensions might cause erratic behavior. Try clearing your cache or running Firefox in Safe Mode (without extensions) to check if that resolves the problem.

3. Site or Account Permissions – Some features may depend on specific user roles or settings. If you're using a corporate or team account, check if any permissions affect field locking.

4. Website Bug or Update – If this behavior is inconsistent, the platform might be experiencing a bug. Check if there are any ongoing issues reported by the service provider, or try using the feature in an incognito window to rule out session-related problems.

If the issue continues, consider reaching out to the platform’s support team with details like when it works vs. when it doesn’t, and whether you notice the same problem in other browsers.

Regarding browsers, I like to segregate my browsing. I use Vivaldi for general browsing and Firefox for anything requiring a login. I'm reluctant to login to any of my accounts in anything but Firefox but I suppose it's always an option to create a throwaway account just for testing.

The only extension which could have been causing a problem was an ad-blocker which I temporarily disabled. It made no difference.

It always seemed much more likely that it was a problem with the site than the browser. When I looked in the browser console there were always a shedload of errors but I've just opened the "enter a casual record page" and looked in the console and it's very clean so it looks like they've fixed whatever the issue was.

The team for this site seem generally reluctant to acknowledge any problems with the site, especially the desktop one, and will usually only reply to an issue raised in the forum after they've fixed it. They seem to prefer to keep us in the dark... I really don't know why.

Thanks for your thoughts @Mesh. I'm glad that this has been resolved.

Regarding responses on this Forum, the main issue is that we lack resources to respond to all comments across this Forum, our GitHub and the iRecord email. There is no wish to keep anyone in the dark. Ultimately we are offering a free resource to the recording community, and we do our best to support that community with the resources that are available to us.

Thanks for the reply @OliP_CEH, I'd guessed that it was probably a small team administering the site and I had no idea you had a GitHub account so that's good to know.

Since you say that you don't have the resources to monitor the forum properly can I take this opportunity to flag-up that several people are complaining about not being able to dismiss notifications once they've been read. It's been raised here Notifications that can't be acknowledged but it's been raised by other users too; are you aware of this issue? It only seems to impact those of use who only use the desktop site.

Thanks @Mesh. I have replied in that thread; basically it is known about and awaits prioritisation.