drywallbmb

@craftee123 — Sorry for the delay. Unfortunately, Salsa does not support having the “Source” or “Source Details” fields populated via the API, so there’s no way for this plugin (or any other tool utilizing the API) to provide values for those fields, which is why you’re seeing what you’re seeing. This is documented at https://help.salsalabs.com/hc/en-us/articles/360005440014-The-supporter-object

(I wish Salsa’s API didn’t work this way…)

@vefusion —?Sorry for the delayed response. Not sure offhand why this would happen, as it hasn’t been reported before. Could you tell me what version of PHP your site is running, and list all your active plugins?

@chadmohr We just released a new version that fixes this issue, which was only present in older versions of PHP like the one you’re running. Sorry for the delay, but you should be all set now!

Hey @chadmohr, would it be possible for you to let us know what version of PHP produced that error?

Thanks!

PR accepted and merged, closing this thread to reflect that it’s being handled. w00t.

@relish1227 We just pushed a new release that fixes this issue. If you update to 1.0.1 you should be able to remove your CSS workaround.

Thanks for reporting this issue!

Ha, disregard my comment, you already thought of it!

I’ll have a go at a PR, this will make my life massively easier. ??

Come to think of it, probably all the return calls in advance of that filter running should be changed to set a variable, then run that variable through the filter… I actually need to filter it when $iaoptions['email_visibility_toggle'] is set to 'no_limit' but the function has already returned by that point.

Hi @relish1227 and @deputydawg,

Sorry for the reeeeeeeally late response on this. Our intention was, I believe, to make this plugin functionally equivalent to the old one, with just some improvements and enhancements added on top. So I’m not sure why you’re seeing a difference, but we’ll look into it!

Hi Jeff,

I’m pretty sure this plugin’s developers are no longer maintaining it in any way. Which is a bummer.

But I have some good news: We’ve forked it and touched it up a bit to make sure it’s compatible with new versions of WordPress. Check out https://www.ads-software.com/plugins/better-section-navigation/

Thanks for writing.

Right now Deduper only knows how to automatically fix references for featured images, but we’re working on a new Pro version that we’re hoping will be able to do something similar for WooCommerce product gallery images as well.

Thanks for your message.

We’re in the process of working on a Pro version that will be more sophisticated in handling image references, going beyond just preserving references for Featured Images.

Finding image references in the actual body of posts is actually quite challenging, so while that’s on our roadmap it will be some time before we’re able to release something we think is reliable even for Pro.

But we’re actively working on at least making it smarter for some other postmeta keys, and hope to have at least a rudimentary in-body solution in the not-too-wildly-distant future.

Hi Wes,

Thanks for your message. We are, in fact, in the process of working on a Pro version that will be more sophisticated in handling image references, going beyond just Featured Images.

Finding image references in the actual body of posts is actually quite challenging, so while that’s on our roadmap it will be some time before we’re able to release something we think is reliable even for Pro. But we’re actively working on at least making it smarter for some other postmeta keys, and hope to have at least a rudimentary in-body solution in the not-too-wildly-distant future.

Thanks for bringing this up. Deduper doesn’t do anything weird during deletions that should require any different permissions from just manually managing your Media Library like normal, so I’m not sure offhand why this would be a problem —?or why looser permissions would solve it.

Thus far we’ve been unable to recreate the issue but will keep experimenting to see if we can. Thanks for you your patience!

Nice workaround! I suspect most hosts can handle most files, but you’re right that we’re not setting any sort of upper bound and it would be nice to control that. I’ll add to to the “potential new features” list!