derricksmith01

Thanks, was just updating this thread so anyone who may land here knows that my original question was answered.

Ownership has been transfered and this plugin is now actively maintained.

I forked this on Github and resolved a vulnerability in mv-file-handler.php which allowed authenticated users to access other users files. If you would like to send your changes I can add to the repo.

https://github.com/derricksmith/wordpress-plugin-media-vault

After digging to the code I discovered the function ‘bp_group_hierarchy_allow_anon_access’. Filtering the function to include the public menu item solves the problem. I added the filter prior to calling ‘bp_register_group_extension’ in my plugin.

Would be nice if GH could implement the BP 2.1 ‘access’ and ‘show_tab’ arguments in a future release.

@phil.dziner

Worked for me. Thanks

I had the same problem. Turned out non of the beginning php tags were completed in any of the files. I manually went through them all (maybe 25) and changed ‘<?’ to ‘<?php’. This solved the first problem.

The second problem I ran into was inserting a new database. This problem was caused by how the wp_an_databases table was created. Since phpanalytics stores the database passwords encrypted (good), the password column needs to be a blob instead of a varchar. I changed

$qy_table_databases = ‘
CREATE TABLE IF NOT EXISTS '.$analytics_sql['tname']['databases'].' (
DB_ID int(10) unsigned NOT NULL AUTO_INCREMENT,
DB_NAME varchar(256) NOT NULL,
DB_HOST varchar(256) NOT NULL,
DB_USER varchar(256) NOT NULL,
DB_PASS varchar(256) NOT NULL,
PRIMARY KEY (DB_ID)
) — ENGINE = INNODB DEFAULT CHARACTER SET utf8
‘;

to

$qy_table_databases = ‘
CREATE TABLE IF NOT EXISTS '.$analytics_sql['tname']['databases'].' (
DB_ID int(10) unsigned NOT NULL AUTO_INCREMENT,
DB_NAME varchar(256) NOT NULL,
DB_HOST varchar(256) NOT NULL,
DB_USER varchar(256) NOT NULL,
DB_PASS BLOB NOT NULL,
PRIMARY KEY (DB_ID)
) — ENGINE = INNODB DEFAULT CHARACTER SET utf8
‘;

After the database changes, I had to deactivate the plugin and remove the database tables manually. I then reactivated it and it installed correctly.

Good luck.