Matthias Pabst

Ich konnte das Problem ebenfalls bei einem Strato Shared Host nachvollziehen (Paket “Power Web Plus”). So lange das Backup kleiner als 64 MB ist, l?uft’s. Wenn es gr??er ist, bricht die Erstellung bei 64 MB ab. Sehr Schade.

Solved in version 1.3.9. Thanks!

Thank you for your quick reply. Sounds good! Keep up this great plugin!

I had the same problem and just found the error with the directory name. In file content-progress.php in line 29 change

load_plugin_textdomain( 'content-progress', false, dirname( plugin_basename( __FILE__ ) . '/lang' ) );

to

load_plugin_textdomain( 'content-progress', false, dirname( plugin_basename( __FILE__ )) . '/lang' );

Any news about this?

Same here. Since version 20141123 the plugin doesn’t track anymore. WP 4.0.1 and PHP 5.5.19.

When I try to install the plugin on a new WordPress site, the filters are missing. Maybe that’s the problem. Screenshot: https://cl.ly/image/011R183o1R27

Same problem here since I switched from http to https.

2.3.0 works! Thank you for your great support!

Just tested WP-Bitly 1.0.1 with Jetpack 3.0.1 on a WP 3.9.1 Test Site and it worked fine (link to tweet).

After updating to WP-Bitly 2.2.9 it didn’t work anymore (link to tweet).

Good idea! I will test this next monday and post another update here.

I updated to the latest version (2.2.8) but it didn’t work. Currently I’m still running Jetpack 2.9.3.

Same problem here. When using Jetpack’s Publicize to share posts at Twitter, only the (non-permalink) ID-URL is shared instead of the bit.ly-URL.

Before updating WP bit.ly from 1.0.1 to 2.x it worked fine.

One more vote! Scanning child themes and parent themes would be great. ??

Hi Dale,

I deleted and reinstalled the plugin. Still doesn’t work. The plugin still tries to load all resources from the wrong path (2x wp-content/plugins).

Best,
Matthias

Hi Eric, thanks for your answer.

I found a solution which works for me. Via .htaccess a small script checks, if a user ist logged in when trying to access a file. If not, it redirects him to the login page.
https://www.0to5blog.com/tips/protecting-wordpress-media-uploads-unless-user-is-logged-in/
Maybe it’s possible to integrate this in your plugin.