keepulookin

resolved…didn’t realize it was in the “add hidden images” option

added target=”_parent” attribute to link

bump

I renamed to costa-esmeralda2 and that seemed to do the trick

it’s listed as costa-esmeralda, no capital letters.

trypanama.com

I resolved the issue by changing the subject field with the following additional setting:

flamingo_subject: [dynamictext-493]

I created my own post here:

https://www.ads-software.com/support/topic/addingcustomizing-flamingo-inbound-message-columns?replies=1#post-5436991

I want to do something very similar to the OP with one change. I don’t mind my revised code getting overwritten since I keep multiple backups of my site and can simply re-implement negated functions.

My current setup is Contact Form 7, Contact Form 7 – Dynamic Text Extension, and Flamingo.

I used the Dynamic Text Extension to pull data from posts containing contact forms. I would like Flamingo to pull this field to be visible in a new column of the bank of inbound messages.

Currently, I need to open each form within the inbound messages bank or export Flamingo’s inbound messages (including content) and filter through the content field within Excel in order to find the dynamic data I’m using for reports.

The specific dynamic field I want to pull into it’s own column of the inbound messages bank is [dynamictext-493]

kn00tcn, I followed your lead in your post above by using the code below, but no new column was generated with content from the dynamic text field

flamingo_channel:[dynamictext-493]

I also tried
flamingo_inbound_channel:[dynamictext-493]

One thought I had (but not sure how to accomplish without some direction) is to change the subject field to the dynamic text field. I don’t use the subject field in my forms so the entire subject column displays [your-subject].

Incorrect selector field was chosen from export plugin. When choosing correct field, output displays properly in Excel

It was a conflicting plugin…which has subsequently been deleted

I think there was some conflicting plugins. I deleted a few I no longer needed on the site and am no longer getting the catchable fatal error.

The property IDs are limited to list the first 100 in the PHP function so if you have more than that, you will need to change that accordingly.

here’s my dev site product category page:
https://essentialanew.lazybeaches.com/products-page

here’s my dev site individual product page:
https://essentialanew.lazybeaches.com/products-page/facial-care/advanced-c-serum

here’s the live site of what I want to accomplish on the product category page:
https://timelab.hostedbywebstore.com/Windrose-Aromatics/b/6913434011?ie=UTF8&title=Windrose+Aromatics

here’s the live site of what I want to accomplish on the individual product page:
https://timelab.hostedbywebstore.com/Appetite-Grapefruit-Peppermint-Essential-Combination/dp/B00E4Z6ZDI?field_availability=-1&field_browse=6913434011&id=Appetite+Grapefruit+Peppermint+Essential+Combination&ie=UTF8&refinementHistory=brandtextbin%2Csubjectbin%2Ccolor_map%2Cprice%2Csize_name&searchNodeID=6913434011&searchPage=1&searchRank=title-asc-rank&searchSize=12

Here are the steps I took to add the Property ID numbers to the search widget:
Appearance > Widgets > Primary Sidebar > AgentPress Listing Search > Edit > ticked the box for Property ID > clicked “Save Widget” button.

When I go to the front end of the site, the Property IDs appear as part of the widget. Selecting a Property ID and clicking the “Search Properties” button however returns the catchable fatal error. Also, not all of the Property ID numbers appear in the dropdown menu of the search widget.

The taxonomy for Property ID is propertyid so I don’t think it’s related to the taxonomy itself.

They are just a few digits. Some examples are 317, 318, 319, 320. The titles are not the same as the property numbers though. They are more like: “New 3 Bedroom Fully Furnished Home For Sale in Quintas de Cabuya, Chame, Panama.” This particular one that has that name is property number 0109