ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

[1.7] {exp:member:custom_profile_data}

December 27, 2010 4:54pm

Subscribe [3]
  • #1 / Dec 27, 2010 4:54pm

    mhulse

    329 posts

    Hello,

    We recently upgraded to EE 1.7 and I noticed that {guest-blogger-url} is generating the full href link:

    <a href="http://mysite.com/blog/index.php?URL=http://www.twitter.com/blah">http://www.twitter.com/blah</a>

    Before the upgrade, all I got was the URL.

    Having the URL wrapped in a link is not very helpful. :(

    Is it just our install, or did something change with {exp:member:custom_profile_data}?

    The blog I am using this code in has “turn links into hrefs” turned off.

    Any tips?

    Thanks,
    Micky

  • #2 / Dec 27, 2010 5:02pm

    mhulse

    329 posts

    I should clarify, {guest-blogger-url} is a custom profile field, and formatting is turned off for this custom field.

    I am also noticing that e-mail {encoded} links are not working in profile templates. :(

  • #3 / Dec 27, 2010 5:10pm

    mhulse

    329 posts

    Ah, ok, so it looks like the custom profile info has been modified in 1.7:

    Altered member profile fields to disallow HTML.

    This might explain why my custom profile templates exploded. ;(

    Just curious why the URL would automatically get converted to an href? Maybe it is just me, but having a link that wraps a url is kinda useless if you ask me.

    Still investigating though… Maybe I am doing something wrong here. 😊

    Thanks!
    Micky

  • #4 / Dec 27, 2010 5:17pm

    mhulse

    329 posts

    Argh, this is annoying.

    Looks like {encode} does not work on a profile template?

    Contact {encode="{guest-blogger-email}” title=”{guest-blogger-name}”}

    If I just output {guest-blogger-email} I get the JS encoded e-mail, but it is just a e-mail href wrapping the e-mail address.

    Still kinda wondering why all of this had to change… I am sure it had to do with security, but why would you not allow template authors to use {encode} on the profile template? :(

    Kinda making wish I had stuck with 1.6.8. :D

    Thanks for listening to me complain.

    Cheers,
    Micky

  • #5 / Dec 27, 2010 5:24pm

    mhulse

    329 posts

    One last thing…

    Having e-mails encoded in custom member profile templates by default affects thing like this:

    {exp:gravatar email=

    As you can see, I am using exp:gravatar plugin, but it does not work anymore because the e-mail is obfuscated via built-in EE logic.

    I am hoping I can use some PHP to help me remove some of this cruft.

    Have a nice day, and thanks for letting me vent a little.

    Micky

  • #6 / Dec 27, 2010 5:45pm

    mhulse

    329 posts

    Update:

    It looks like the {exp:html_strip} plugin does not work on email addresses because it is obfuscated by javascript. :(

    I kinda figured this would be the case, but it was worth a shot.

    When I used PHP:

    <?php echo '{email}'; ?>

    ...the template just failed to render. :(

  • #7 / Dec 28, 2010 3:32am

    John Henry Donovan

    12339 posts

    mhulse,

    We recently upgraded to EE 1.7 and I noticed that {guest-blogger-url} is generating the full href link:....but having a link that wraps a url is kinda useless if you ask me.

    This was the case before 1.7 also. What version did you upgrade from?

    Not sure how it would be useless as I’m not aware of your own context but having a clickable link is certainly helpful for my own users.

    Likewise email being encoded was there before EE1.7

  • #8 / Dec 28, 2010 1:46pm

    mhulse

    329 posts

    This was the case before 1.7 also. What version did you upgrade from?

    Oh! Really? Sheesh, I feel stupid then. :D

    We upgraded from 1.6.8.

    Maybe things had been broken for longer than that? I could swear things were working before the upgrade (the blogger that I was using this code for would have let me know a lot sooner if things were borked).

    Not sure how it would be useless as I’m not aware of your own context but having a clickable link is certainly helpful for my own users.

    Definitely. I guess we all use things differently.

    I was just trying to say that having a URI that is linked-up is not as useful as just being able to take the URI and put it in its own link on the template. When the URI is automatically linked, without the ability for the template author to do anything with it (besides spit it out onto the page), it is not as useful as it would be otherwise.

    If you just got the url, then you could create your own link (which, in my case, would be the preferred way to use this custom field).

    IMVHO, I think the same could be said about the e-mail links. Running an e-mail through the {encode} tag (on the template level) is pretty easy… But becsause the e-mail is linked-up, my options are pretty limited. For example:

    Click here to email John: john @ nospam.com

    I would much rather have the “John” text hot, vs. just spit out the e-mail addy.

    Same goes for URIs too. :D

    Check out Billy’s website! http://thisisbillyswebsite.com/folder/file.ext

    In the above case, I would much rather have “Billy’s website” linked rather than show the full URI.

    Likewise email being encoded was there before EE1.7

    I could swear things were working in 1.6.8, and they broke after upgrading to 1.7. It must be our install… Could be some sort of plugin conflict or something. 😊

    Anyway, thanks so much for your reply. I will search around for a plugin that bypasses the EE text formatter (I assume that custom profile fields are run through EEs text formatting system).

    Thanks for the reply, clarification and the help! I really appreciate it.

    Have a nice day!

    Cheers,
    Micky

  • #9 / Dec 28, 2010 8:00pm

    Barry Cogan

    291 posts

    Hi Micky,

    We are always happy to help!  If you have any further questions please do post again!

    Sincerely,

    Barry Cogan

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases