By ajwwong on

Hi there,

I would like to translate some basic text using the locale.module into a text *plus* a link to a certain place on my website. However, when I try to substitute in something like this:

Original phrase:

Access denied.

Desired substitution:

Access denied.  To register go to <a href="/user/register">the registration page</a>.

The text gets substituted in, but the link is not parsed. That is to say, I get the whole messy link code rather than the nice clean link.

That is to say it looks like this:

Access denied.  To register go to <a href="/user/register" >the registration page </a>.

rather than:

Access denied.  To register go to _the registration page_ [with active link bolded].

Any ideas?

Thx.

Albert
www.ithou.org/For_Natalia

⋅ Categories: Drupal 4.7.x

Comments

logictude’s picture

logictude commented

If you look at the source do you see encoded characters? Instead of

<

you get

&gt;

Also, i'm curious as to why you'd do this instead of route users to a custom 403 page (admin->settings)?

ajwwong’s picture

ajwwong commented

You're exactly right.... :-).

The actual source reads like this, for example:

If you don&#039;t have an account, you can register by  going &lt;a href=&quot;/user/register&quot;&gt;here&lt;/a&gt;  .

You nailed it.... :-)

So.... what's the best way to stop it from doing that? [Or is there a way...?]

PS. As far as the custom 403 page, I am using logintoboggin, which is my 403 page redirect: [toboggan/denied] -- but, I just want it to read a bit differently than it is right now -- including a link to a registration page...

Thanks for your help!

Albert
Esalen Alumni Group

logictude’s picture

logictude commented

I just edited the "Access denied" string and replaced it with

<a href="http://example.com">example.com</a>

It came through as a link, just fine. I altered a few other strings with the same code and they came through as well.

I ran this test with Drupal 4.6, LoginToboggan not installed, fyi.

For fun, try editing text that doesn't exist on a LoginToboggan-generated page. You need to remove variables in order pinpoint the problem.