drywallbmb

Hi @willkang525,

Thanks for your feedback. We’re working on an update that should facilitate the ability to eliminate all duplicates with a single click. In the past we’ve shied away from this — we generally encourage users to carefully review everything being deleted so that nothing untoward gets removed unexpectely —?but we’ve heard from you and others that this is a desired feature, however dangerous, so we have added it to our roadmap.

Ben

• This reply was modified 4 years, 9 months ago by drywallbmb.

Thank you for your kind words!

Hi @amotherthing,

I’m sorry you had a bad experience with Media Deduper. I realize it’s been 5 months since you left this review, but if you’re willing and able to provide more information to our support team), we’d love to learn more about exactly what went wrong. While some of the things you mention are expected, known behaviors (that we clearly need to document better!), the deletion of non-duplicates is not a behavior we’ve had others report and we’d definitely like to get to the bottom of as that’s absolutely not acceptable and shouldn’t ever happen.

If this is “old news” and you’d rather not take the time, that’s okay, but I figured it wouldn’t hurt to ask. At the very least, if you could reach out with that form to request a refund we’d be happy to provide one.

Apologies for your unfortunate experience.
Ben

• This reply was modified 4 years, 9 months ago by drywallbmb.

Hi @austinhamilton

The first thing I’d recommend doing is confirming on both the Engage side and in the Gravity Forms settings that you’ve got everything configured correctly with regards to permissions, API keys, and the like.

When you say you’re only seeing 24 of the 30 map fields, are you referring to fields to put GF data into on the Salsa side? I assume it’s not just a matter of your Gravity Form on one site having fewer fields in it than the form on the live site…

Is there anything special about the missing six Engage fields —?like are they all custom fields or something like that?

As mentioned above, screenshots or any other documentation you can provide may be helpful for us in troubleshooting this for you.

Thanks!
Ben

Hi @mediazombie!

Unfortunately there are so many potential issues (server timeouts, network issues, etc) that it can be impossible to pinpoint from afar. What I’d recommend doing is going in to Gravity Forms’ “Settings” and enabling logging. Save that change, then on the now-visible “Logging” item on the lefthand of the settings page turn all the logging OFF except the logging from this plugin. Leave the logs from this plugin going for a while, until you get at least a few recurrences of the issue.

Once the issue has been captured in that log, send it over to us as described above and we can take a closer look and try to identify the specific issue.

Best,
Ben

Hi Ian,

Better Section Navigation Widget doesn’t have any hard-coded H1 elements anywhere. You may want to check with how your theme is setup to output widget titles within the sidebar you’ve got the widget appearing —?the “before title” and “after title” properties of register_sidebar are typically where such things are defined.

• This reply was modified 5 years ago by drywallbmb.

@drzraf Agreed. We’ve now made the git repo public at https://bitbucket.org/cornershopcreative/wp-popup/ (though it’s a little bit messy, branch-wise and such)

• This reply was modified 5 years ago by drywallbmb.

@jdiamonte Well, EN support has said the URL value does, in fact, depend on the client, so there’s no “one size fits all” URL endpoint we can use. Due to that, with today’s 2.0.6 release we’ve introduced a gf_en_api_base_url filter to allow for more easily changing the URL. Hope that helps!

@jdiamonte Thanks for this! We’ll make the base filterable for you in the next release, which should be soon. I’ve also put in a request with EN support to see if we can get clarification on which domain is the “right” one to default to using.

@refurl Probably the easiest thing to do would be to use FTP to go into your wp-content/plugins directory and delete the media-deduper directory entirely. Once that’s done, you should be able to load your wp-admin again, in which case you can re-add Media Deduper as a plugin; WordPress should then download the fixed 1.5.1 release for you.

@refurl We’ve just pushed out 1.5.1 which should resolve this issue for you (and everyone else). Sorry for the snafu!

@refurl Yikes! Our bad. We’ll get a new release out that addresses this ASAP.

Ack! I thought I’d replied to this earlier but didn’t. We did release a 0.9.1 per your suggestion.

Deleting the plugin should not cause existing overlays to be deleted.

Apologies!

When we deployed the 0.9.0 release we inadvertently left some files out of the release. The problem was quickly addressed, but if you happened to update during the window in which some files were missing —?and it looks like you did —?the best thing to do is probably delete and then re-install the plugin; 0.9.0 should then work just fine.

• This reply was modified 6 years, 5 months ago by drywallbmb.
• This reply was modified 6 years, 5 months ago by drywallbmb.

Unfortunately, I think it’s a matter of vague documentation. ??

Source Details is populated with the HTML Referrer only when forms are being filled out directly on Salsa-hosted pages — when the API is used for any reason, such as this plugin, it is always “null”. I’d love it if the API worked differently, but this is consistent behavior that I believe is “by design” from Salsa’s perspective.

• This reply was modified 6 years, 6 months ago by drywallbmb.