cornershop

Thanks for reporting these warnings! We’ll fix this in the next release. We’ll probably switch to using wp_add_inline_script() instead of wp_localize_script() too, since that’s considered best practice now.

Thank you for the heads up. We’ll fix this warning in the next release.

Hi, all – today we released updates to both Media Deduper and Media Deduper Pro that address these deprecation warnings.

Bump. Submitted this as a support case in formassembly.com:

Case #00365952 Forms added on WP through shortcode stopped working had to switch to iframe

[ ref:_00DE0Yukk._500V4CnFtT:ref ]

Hi there! We will address these warnings in a future version of Media Deduper. Until then, they’re harmless, as long as you keep WP_DEBUG_DISPLAY turned off in your wp-config.php file, and display_errors turned off in your php.ini file.

@mantecrod I’m going to mark this as resolved, but if you’re still having issues, please let us know.

Hi, Isa,

Are there any errors visible in your browser’s JavaScript console when you run the indexer?

Hi there! The latest version of this plugin fixes this deprecation warning. Thanks again for the heads up.

Hi there –?so far, we haven’t been able to replicate this issue. NaN most commonly appears in the context of a divide-by-zero operation; but when there are zero attachments available to index, the indexer UI doesn’t try to calculate a percentage of zero. It simply doesn’t display a progress bar.

If you have any further information about your situation that you can share, please let us know.

Hi Isa,

This is Courtney, the support specialist from the Cornershop Creative team.

I will hand this off to our plugin developer to look at. Please be advised it may take 3-5 business days for us to review. In the meantime, here is some documentation from our support articles that might be helpful. You can find more here if you’d like to look: Media Deduper Support Articles

Thank you!
Courtney


If indexing is stuck at 0% or does nothing:
From time to time, users report that they are unable to generate the media index after activating Media Deduper Pro. Most commonly, this is caused by either unusually large media files or password protection.

Large files
When Media Deduper or Media Deduper Pro indexes your files, it calculates a hash of the contents of each file. If your media library contains exceptionally large files (e.g. long audio or video files, or extremely large and/or high-resolution images), this process can be slow or may even cause out-of-memory errors, preventing the indexing process from ever completing.

In these cases, we recommend enabling the “Run partial hashes” setting, which tells Media Deduper Pro to analyze only the first 5 megabytes of each file, rather than each file’s full contents. This setting greatly improves indexer performance on sites with large files and/or low memory, but it also carries the risk that files that are not completely identical will be treated as duplicates, because if two files’ first 5 MB are identical, it isn’t necessarily true that the rest of the two files will be identical. As always, we recommend backing up your files before using Media Deduper.

To enable this setting, from Settings in your WordPress Admin, navigate to Media Deduper Pro, check the box next to Run Partial Hashes, and click Save Changes.

Password protection
Media Deduper and Media Deduper Pro require WP cron to function. If you’re working on a development site that’s password-protected using HTTP basic authentication, special measures are necessary to make WP cron work. We recommend using this plugin, which is easy to configure: https://www.ads-software.com/plugins/wp-cron-http-auth/

Media Deduper Pro will display a warning message on your WordPress admin screen if it detects that WP cron isn’t working correctly.

Other issues
If you see Media Deduper Pro’s “It looks like your site is password-protected” notice on your WordPress dashboard, but your site is not password-protected, then something else is causing so-called “loopback” HTTP requests to fail. Loopback requests are requests made by a website to itself, and they’re used by WP cron and by Media Deduper to perform scheduled work in the background, including building the media index.

When first installed, Media Deduper Pro performs a test loopback request to your site’s wp-cron.php file.

If any of the following conditions are met, the password protection warning will be displayed:

1. The response from your server contains a www-authenticate header
2. The status code for the response is 401 (Unauthorized)
3. Your server fails to respond with a 200 (OK) status code for any other reason (timeout, 5xx or other 4xx error, etc).

The result of the test loopback request is cached for up to 12 hours in a transient named mdd_wp_cron_request, so once you find and fix the issue that initially prevented loopback requests from working, there may be a delay before the password protection warning disappears.

Thank you for letting us know! We’ll fix this in the next release.

Thanks for bringing this to our attention! We’re looking into it; in the meantime, do you see any errors in your browser’s JavaScript console, and if so, could you please share them here?

Closing this thread as the issue was fixed in Media Deduper 1.5.7.

Closing this thread as the issue was fixed in Media Deduper 1.5.7.

I’m closing this thread, but please open another if the plugin isn’t working quite right for you. Thank you!