Incompatibility with custom database prefixes
-
Expected behaviour:
The plugin dynamically uses the $wpdb->prefix variable to create its mysql tables conventionally.Actual behaviour:
The plugin creates its tables using the $wpdb->prefix but partially uses hardcoded query strings to access it.An example of an error message which might be caused by this problem is:
Warning: mysql_fetch_object(): supplied argument is not a valid MySQL result resource in /path-to-your-wp-root-directory/wp-content/plugins/html5-jquery-audio-player/playlist/add_playlist.php on line 50I found occurences of the descripted problem in playlist/add_playlist.php (lines 26, 39, 42).
Nasty workaround (because it alters the plugin code and will be overwritten by updates):
Replace the occurences ofwp_hmp_playlistby$tableso they use an (already existing!!!) variable containing the correct table name.Hope this will be fixed in future releases.
The topic ‘Incompatibility with custom database prefixes’ is closed to new replies.