orionis23

We are not using the Pro version, we are using the free version. (The client would like to move to the Pro version if we can get the free version working.)

Yes, this plugin unfortunately appears abandoned. Had excellent support in the past. Would be nice to have an official announcement though, perhaps someone else would like to adopt the project.

You rock @ravanh!

Thanks so much.

I opted for a third workaround: the Google Analyticator plugin has a “Method to prevent tracking” option which I had set to “Remove”, giving us the above situation. I have changed that setting to “Use ‘admin’ variable” which prevents tracking while keeping analyticsEventTracking defined… and all is once again right with the world.

Thanks again for the great support!

Upon further testing, it appears to only effect logged in Administrators.

I’m sending you login info for a temp admin account now, thanks for taking a look!

Found both options in the settings, missed them the first time.

Excellent!

The above changes worked like a charm! Thank you for your prompt and efficient support!

Further testing reveals that the actual page in question where I am encountering this error (mysite/wp-admin/users.php) gets as far as line 335:

$wp_list_table->prepare_items();

When the myCred plugin is active, the users page parses up to that line then everything grinds to a halt with the aforementioned undefined method error.

Filter feed by hashtags??

Say someone tweets about many things but only wants to show their photography related tweets on their photo blog…

Until a working update is issued, this topic should remain unresolved shouldn’t it?

Success!! The Apply Bulk Watermark phase now correctly follows the uploads directory path and applies the watermark to images selected. Unfortunately it is not recognizing all images in the directory, specifically those with the extension .jpeg as opposed to .jpg (and this is almost half of all the images!)

This should be an fix in the allowed file types, I’ll move it to a new thread though so that this one can remain resolved as it indeed is!

Enabling allow_url_fopen in the wp-admin directory has successfully allowed the Plugin Diagnostics Check to pass, as well as allowing a successful Watermark Preview image to be created!

Unfortunately, advancing to the Apply Bulk Watermark phase and selecting a directory from within the uploads directory has resulted in the original error (using version 1.6.1):

Fatal error: Uncaught exception ‘UnexpectedValueException’ with message ‘RecursiveDirectoryIterator::__construct(/kunden/homepages/14/d424857031/htdocs/my_sites/tspb/homepages/14/d424857031/htdocs/my_sites/tspb/wp-content/uploads/2012/08) [recursivedirectoryiterator.–construct]: failed to open dir: No such file or directory’ in /homepages/14/d424857031/htdocs/my_sites/tspb/wp-content/plugins/bulk-watermark/bulk-watermark-tools.php:430 Stack trace: #0 /homepages/14/d424857031/htdocs/my_sites/tspb/wp-content/plugins/bulk-watermark/bulk-watermark-tools.php(430): RecursiveDirectoryIterator->__construct(‘/kunden/homepag…’) #1 /homepages/14/d424857031/htdocs/my_sites/tspb/wp-content/plugins/bulk-watermark/bulk-watermark-plugin.php(792): Bulk_Watermark_Tools->list_files(‘/kunden/homepag…’) #2 [internal function]: Bulk_Watermark_Plugin->bulk_watermark_manager(Array) #3 /homepages/14/d424857031/htdocs/my_sites/tspb/wp-content/plugins/bulk-watermark/bulk-watermark-settings-p in /homepages/14/d424857031/htdocs/my_sites/tspb/wp-content/plugins/bulk-watermark/bulk-watermark-tools.php on line 430

Clients hosting provider confirmed that allow_url_fopen is enabled in the directories in question and suggested we contact the plugin developers (as expected… it’s not my first day at work!) They also suggest we confirm in which directories it should be enabled (again, since enabling it is not recursive). So, in which directory is the plugin checking for allow_url_fopen when creating the output of the “Plugin Diagnostics Check” meta-box?

I appreciate the attempts to help, but the confusion seems to be in the assumption that to simply “enable the ‘allow_url_fopen’ with php.ini” will solve the problem, because in my case thus far it is not doing so.

I have enabled allow_url_fopen on the site’s root directory, and in several other directories for good measure, including the uploads directory… below are links to phpinfo pages in each of the directories where you can see confirmation that the function is successfully enabled, yet the plugin in still does not recognize this and is not working.

https://www.truccosemipermanentebologna.com/phpinfo.php

https://www.truccosemipermanentebologna.com/wp-content/phpinfo.php

https://www.truccosemipermanentebologna.com/wp-content/uploads/phpinfo.php

https://www.truccosemipermanentebologna.com/wp-content/plugins/bulk-watermark/phpinfo.php

P.S. To mark this thread as resolved, either:

1) the plugin must be working for me, or
2) we come to the conclusion that the plugin will only work in some instances (not all)

I appreciate your understanding and help! ??

Hosting company will tell me to contact the plug-in developer as this is a PHP5 vs. the plugin issue seeing as how the directory I am enabling allow_url_fopen in has successfully done so.

PHP5 has allow_url_fopen off by default, and php.ini in my site’s root folder is successfully activating it, but this is not a recursive action… if the plugin requires a PHP5 installation with allow_url_fopen activated in a specific directory, then this should be part of the plugin documentation but I’m not seeing anything in the F.A.Q.

Contacting you directly will defeat the purpose of these support forums! ??

Here are the contents of the “Plugin Diagnostics Check” meta box:

Plugin Version: 1.6.0

Server OS: Linux (32 bit)

Required PHP Version: 5.0+
Current PHP Version: 5.2.17

GD Support Enabled!
FreeType Support Enabled!

PHP Safe Mode: is disabled!

PHP allow_url_fopen: is disabled!
Enable allow_url_fopen in php.ini!

Disabled PHP Functions: None Found!

Memory Use: 24.8 / 256M

Peak Memory Use: 24.9 / 256M

Server Load Average: 7.54, 6.86, 6.34

Updated to the newest version and got as far as the watermark preview, which is a broken image so I wasn’t comfortable advancing to the bulk application.

The “Plugin Diagnostics Check” meta box shows:

PHP allow_url_fopen: is disabled!
Enable allow_url_fopen in php.ini!

Yet allow_url_fopen is indeed enabled via a php.ini file as is confirmed via a phpinfo file which shows under PHP Core:

Directive: allow_url_fopen
Local Value: On
Master Valure: On