Linking Search Participants and Search Teams

Options
We are building our TeamRaiser page (modifying the page built for us last year by the Luminate Team but we never used it) and my big hang up is the Search Participants and Search Teams Links.  I found where to change the links in the Page Wrapper Editor, but I don't know where to send the link to.  A little help woould be awesome.

http://nlmed.convio.net/site/TR?fr_id=1050&pg=entry


Brian
Tagged:

Comments

  • Have the Javascript redirect (i.e. through JS window.location) upon the "search" button click for participant search to the following:


    Note: change that "YOURFIRSTNAMEVAL" and "YOURLASTNAMEVAL" with the actual value of what's being inputted on those fields (i.e. jQuery can retrieve those, by targetting the selector id of your inputs)

    site/TR?fr_id=1050&pg=pfind&searchFirstName='+YOURFIRSTNAMEVAL+'&searchLastName='+YOURLASTNAMEVAL+'&fr_search_type=participant&fr_find_search=Search&submit=true';


    and for the team result:  Note: Change that YOURTEAMNAME with the actual input (similar as what being mentioned above)

    ../site/TR?fr_id=1050&pg=pfind&searchTeam='+YOURTEAMNAME+'&fr_search_type=team&fr_find_search=Search&submit=true
  • Hi Brian,


    Just checking in to see if someone helped you with this
    issue.  Please let me know if not and I'll coordinate a
    meeting with my developer or we can send you instructions.



    Thanks,

    Laura


    --












    Laura Higgins

    Strategic Consultant | Cathexis
    Partners

    email: laura@cathexispartners.com
    phone: 410.428.3422






















  • Daniel Hartanto:

    Have the Javascript redirect (i.e. through JS window.location) upon the "search" button click for participant search to the following:


    Note: change that "YOURFIRSTNAMEVAL" and "YOURLASTNAMEVAL" with the actual value of what's being inputted on those fields (i.e. jQuery can retrieve those, by targetting the selector id of your inputs)

    site/TR?fr_id=1050&pg=pfind&searchFirstName='+YOURFIRSTNAMEVAL+'&searchLastName='+YOURLASTNAMEVAL+'&fr_search_type=participant&fr_find_search=Search&submit=true';


    and for the team result:  Note: Change that YOURTEAMNAME with the actual input (similar as what being mentioned above)

    ../site/TR?fr_id=1050&pg=pfind&searchTeam='+YOURTEAMNAME+'&fr_search_type=team&fr_find_search=Search&submit=true

    I added this code:

    ...site/TR?fr_id=1050&pg=pfind&searchFirstName='+part_last_name+'&searchLastName='+part_last_name+'&fr_search_type=participant&fr_find_search=Search&submit=true'


    and I changed the input to be match the input ID, but I still a "This Page is not functioning on our site".  I could scrap the whole search on the entry page and put a link to the standalone search page http://nlmed.convio.net/site/TR?fr_id=1050&pg=pfind

  • I think the problem is the link to your template.js script.


    <script src="secure2.convio.net/nlmed/teamraiser-themes/theme1/js/template.js"></script>


     
  • Brian Mucha:

    I think the problem is the link to your template.js script.


    <script src="secure2.convio.net/nlmed/teamraiser-themes/theme1/js/template.js"></script>


     

    Might be time to have a talk with Luminate Support, since they built it originally...


    I did notice that there is a component TeamRaiser short code that could be entered for a participant search on this page, but it's not as clean looking, but I think that we put in a little coding to help that as well.


    Brian

  • Hi Brian,


    No need to reach out Luminate Support for this.


    What Brian Mucha's mean is that your <script> src path that points to your external Javascript file (template.js) is incorrect need to be rectified a little bit.


    Here -- why not try to modify your current path of that "src" value to the following "Relative URL" path
    <script src="../teamraiser-themes/theme1/js/template.js"></script>



    p.s. I did check your javascript otherwise in regards of how you pass the value and trigger the button click of those search buttons, seems to be ok, and should function when you correct the above pathing


    Pathing issue aside, the passing name values implementation wise that I suggested to you initially should work. As verification, here is the same exact suggestion being put in action on our site: 

    http://stepout.diabetes.org/site/TR/StepOut/StepOutContent?fr_id=11524&pg=entry

    Add On Note:

    With Luminate Online, you are either using the "secure2.convio.net/nlmed" prepend or the public facing' counterpart, which in your case is "nlmed.convio.net"


    If you are using the former, the correct src path should be
    https://secure2.convio.net/nlmed/teamraiser-themes/theme1/js/template.js


    if you are using the latter, src path would be
    http://nlmed.convio.net/teamraiser-themes/theme1/js/template.js


    Ideally we don't really use "Absolute" URL path (including that https:// or http://) because of the https:// vs http:// mixed content browser warning/security issue and should try the "Protocol-Relative" URL with that begins with just //  ; modern browsers nowadays know whether to use https or http calling those assets depending on the context of your current page whether the assets are called from a secure page or non secure / regular page -- but this presents problematic issue with Luminate Online environment since it rarely that the secure and non-secure URL are of the same name  (i.e. secure2.convio.net vs nlmed.convio.net)  -- hence for those external Javascript files that gets hosted on FTP, we just simply use the "Relative" URL



    regards,

    Daniel

     
  • Thanks Daniel, I was grabbed into a meeting so I was too cryptic.
  • No worries Brian, after all we help each other here :)  
  • Hey guys, I kept meaning to come back here and thank you two, but it kept getting pushed back because of everything else.  I was able to go in and make those changes and everything is working beautifully.  Thanks for the help.


    Brian

Categories