drywallbmb

Thanks for reporting this bug. We’ll look into it!

Should be fixed with 1.0.2. Thanks again for reporting!

Thanks for reporting this bug. We’ll investigate.

Try updating to 1.0.1 and let me know if the problem persists. Thanks!

Hi gabernx,

Please update to 1.0.1 —?hopefully we’ve really got it fixed this time.

Let me know if the problem persists.

Thanks for reporting this! Kind of a terrible bug.

We’ll get a fix done as soon as we can.

DOH!

We’ll take another look.

Just issued a new release, let me know if you still encounter this bug — hopefully we’ve got it squashed.

This should be available now in the new release!

This should be fixed now in the new release, let me know if not.

That’s a notice to you that there’s a post in your Media section that doesn’t seem to have a corresponding file in the filesystem. This can happen if, for example, you used FTP to connect to the files in your uploads folder and manually deleted something.

Hi Jason,

Sorry for the delayed response. Right now, Deduper will simply delete the media file(s), with no accounting for how those files might be appearing in the site —?as featured images, within gallery shortcodes, custom fields, etc. If your images are being deployed in lots of different ways, you can expect some “holes” in places as the media items will have been deleted without any record of where they went, so to speak.

Hopefully next week we’ll have the new version out that’s much smarter about handling Featured Images (for all content types). It won’t resolve issues with sliders, shortcodes, custom fields, and the like, but will at least keep posts from losing their primary thumbnails during deduplication.

Thanks. We haven’t been eyeing PressThis as a use case to dedupe against, but will try to take a look — if there’s an easy way to handle your situation, we’ll try to get it taken care of!

We’ve got behavior like this set for the release we’re hoping to push out next week.

In that release, the system only looks at posts’ “Featured Images,” making sure that if it’s deleted a featured image that a post was pointing to, the post gets updated to point to the preserved version of the image.

It doesn’t, however, go through the body of posts looking for actual URLs, or dig thru shortcodes that have image IDs in them, or anywhere else — just featured images.

I hope that’ll be useful. We’re considering releasing a Pro version that’s more feature-rich, and if we do I would expect that we’ll identify some use-cases like this that it should handle.

Thanks for reporting this. We’ve been able to recreate this bug and have it fixed for the next release, which we anticipate will be available next week.