Hello Clare,
Here are some options that might help in this site’s case or similar situations:
Link Formatting
In all cases where the website was input as?https://www.example.com/, they display?when logged in?in both the backend edit screen and on the public-facing site?https://www.example.com:/?#?linking back to the current page.?
For the Website field, there are formatting options when editing the field under Website options. Does selecting a different Format or No Format, checking/unchecking Allow port in URL, or checking Enable HTML5 Input Field change the behavior?
The first two options change output sanitization. Selecting No Format should leave the field as-is when outputting to your site.
Checking Enable HTML5 Input Field uses a different type of input field. This might change how the field is saved.
Output Method
When logged out, they display and link OK on the public site. But some of the information is private and requires logging in (Subscriber access) to view, so the issue remains.
Is the challenge that the link format differs for users when logged-in versus logged-out?
What is the method by which the website field is being output to your theme? Are there any typos in the HTML around the field, or related logic?
Is the field being output by any third-party page builder or other system which might be filtering the URL in unexpected ways?
Does disabling other plugins or switching to a default theme resolve the issue?
Testing
Creating a new website field with default options, as well as switching on Display as Link output https://www.example.com/ as expected when displaying with shortcode [pods]{@website}[/pods]
