PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Entry_url link not working

  1. I'm using the entry_url tag in my admin notifications. These links were working fine until the last update to 1.6.3.1.1. Now I keep getting "Oops! We couldn't find your lead. Please try again" when I click on the entry links. It seems to be giving an incomplete link. The link in my notification e-mail looks like this...
    http://www.mysite.com/wp-admin/admin.php?page=gf_entries&view=entry&id=8&lid=110

    But navigating to the actual entry has a link like this...
    http://www.mysite.com/wp-admin/admin.php?page=gf_entries&view=entry&id=8&lid=110&filter=&paged=1&pos=0

    I've tried installing the latest version (1.6.3.1.2) and using the meta-recovery tool (since I recently moved the site) but neither of those made any difference. The entry_url links still don't work.

    Posted 13 years ago on Friday March 2, 2012 | Permalink
  2. Nevermind- it's working now. Turns out there was server maintenance I was unaware of causing the issue. So uh... We're fine. We're all fine here now, thank you. How are you?

    Posted 13 years ago on Friday March 2, 2012 | Permalink
  3. I'm getting something very similar to this... I'm using the {entry_url} in the email notification, and it includes something like https://www.domain.com/wp-admin/admin.php?page=gf_entries&view=entry&id=1&lid=708 which actually navigates to entry ID #712

    However, if I go to the wordpress gravity forms entries link (https://www.domain.com/wp-admin/admin.php?page=gf_entries), and click on entry ID #708, then I get this in the URL: https://www.domain.com/wp-admin/admin.php?page=gf_entries&view=entry&id=1&lid=708&filter=&paged=1&pos=4

    It seems like the "pos" parameter is a position parameter that offsets the selection (in my case, by 4 for some reason), but does not do the same thing when using the {entry_url}. What's going on here?

    Posted 13 years ago on Monday April 23, 2012 | Permalink
  4. This should be fixed in the latest Beta, however if you don't want to use that you can wait for the official 1.6.4 release which is getting wrapped up soon.

    Posted 13 years ago on Tuesday April 24, 2012 | Permalink