Happy to help you with that! I know it is a bit tricky to change those without any reference, as you cannot view this page while being logged in.

Well, actually even that is possible now, you just need to know the right urls. Since we have dedicated login and registration pages, you can actually visit them while logged in and activate the phrases mode too. Here the urls you are looking for:

https://forum.ovoenergy.com/member/login

https://forum.ovoenergy.com/member/register

Note: This only works for communities that use our login and not the company (SSO) login.

In case you are searching for the specific phrases regardless these pages, we also have them listed in this topic:

Thanks @Julian super helpful. 

I’m not having much luck editing the URL of the T&Cs we link to from this page https://forum.ovoenergy.com/member/register - would using the ‘Phrases’ tool be the right approach for this?

Hmm yeah I remember this is a tricky one, I also mentioned it in the documentation:

 I accept the terms & conditions*
Module: Common
Key: loginBox.terms
*Will automatically be replaced by the system with your platform terms url

I think that there is also a specific phrase only for the url, I will try to dig that out!

Yeah so the default translation actually is:

I accept the {termslink}

{termslink} automatically adds the url for the terms & conditions page.

You should be just fine by adding a hyperlink via HTML, something like this:

I accept the <a href="URL GOES HERE">terms & conditions</a>

Simply add a new phrase with these:

Module: Common
Key: loginBox.terms

Thanks @Julian I feel like I’m so close to getting this done. 

I’m not sure where I add in this HTML, I don’t think it’s via the edit function. If it was, this ‘edit’ function for both the registration.detail.loginLink and the loginbox.terms won’t do anything when selected:

Sorry to hear that you are struggling here! If you want, you can shoot me the code & text in a mail and I can try to add it myself.

I think you have to add the HTML via the phrases tool in Control, could be that the frontend does not accept that.