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.

{embed_post:post_title} doesn't work in notifications

  1. conpark
    Member

    Hi,

    i tried to get an e-mail subject like this: "Your question about page-name"

    I used {embed_post:post_title} to display the name of the current page.
    Unfortunately, this doesn't work on pages and custom-post-types.

    Any idea what i am doing wrong?

    Posted 13 years ago on Thursday November 25, 2010 | Permalink
  2. door4
    Member

    I too have this problem....does anyone know the answer? Is it because the form is on a page and not a post?

    Posted 13 years ago on Thursday November 25, 2010 | Permalink
  3. Same issue here. Strangely it used to work for me so something must have changed in either WordPress or the plugin code. A fix is highly appreciated!

    Posted 13 years ago on Friday December 3, 2010 | Permalink
  4. I will take a look at this and see what is going on.

    Posted 13 years ago on Friday December 3, 2010 | Permalink
  5. This ended up being a bug introduced in Gravity forms 1.5 beta1. Email me at alex@rocketgenius.com and I will send you our latest beta with the fix.

    Posted 13 years ago on Monday December 6, 2010 | Permalink
  6. Carson
    Member

    I am using 1.5 RC3.1 and I am having the same issue. Any ideas?

    Posted 13 years ago on Sunday January 30, 2011 | Permalink
  7. Please try our latest version beta release 1.5 RC3.10. I am pretty sure it will solve your problem.

    Posted 13 years ago on Monday January 31, 2011 | Permalink
  8. Carson
    Member

    hmmm. i am using that version

    Posted 13 years ago on Monday January 31, 2011 | Permalink
  9. I thought you were using RC 3.1
    Is your problem specific to using those variables on pages and custom post types, or on posts as well?

    Posted 13 years ago on Monday January 31, 2011 | Permalink
  10. I'm having this problem in v1.4.5. I would love to see it fixed.

    Eivind

    Posted 13 years ago on Monday February 7, 2011 | Permalink
  11. I can confirm the latest build of v1.5 does fix this issue.

    @SigarettDesign This isn't going to be fixed in v1.4.5, it's fixed in the upcoming v1.5 release which is available for Download now on the Downloads page. 1.5 is currently a development release and will be released as a final release within the next week or 2.

    Posted 13 years ago on Monday February 7, 2011 | Permalink