Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • The beta’s working well. It’s still throwing an error because of the isset() on lines 476 of mediatags_settings.php. switching to !empty() would get rid of the error.

    Might be worth adding to the FAQ that if you have SSL enabled only for admin pages or per-content (when using a plugin like Better WordPress Security, for instance) the “Media-tags” in the Media Library’s “Bulk actions” pull-down may not have any obvious effect. This can be fixed by configuring the browser to allow “mixed content” – loading scripts via http even though the rest of the session is https (google “mixed content” and your browser version to get appropriate instructions).

    Thanks very much for the plugin, and for letting us try out the beta !

    thanks, will def. try it !

    You can manually fix this problem by editing media-tags/mediatags_settings.php and replacing the calls to isset() on lines 365 and 357 with !empty(). !empty() only returns TRUE if the variable exists AND has a value, whereas isset() returns TRUE if the variable exists but has no value.

    I’m having the same problem. Two sites running WP3.8.1 and both have v. 3.1.2.1 of Media-Tags. Identical user role configurations on both sites. Bulk edit options work as expected in one site, but in the other result in the behavior described by jusgriff above. Tested with FF25 through 28 and Google Chrome.

Viewing 4 replies - 1 through 4 (of 4 total)