All right, thanks for that. So let’s have you make two changes and tell me if it works on your multisite (it works for me on a regular setup).
file-away/lib/cls/class.fileaway_definitions.php on line 13
change this:
self::$s2member = fileaway_utility::active('s2member') ? true : false;
to this:
self::$s2member = fileaway_utility::active('s2member/s2member.php');
then, file-away/lib/cls/class.fileaway_utility.php on line 11, replace the whole active() method with this:
public static function active($plugin)
{
include_once(ABSPATH.'wp-admin/includes/plugin.php');
return is_plugin_active($plugin);
}
Man you’re fast on the support response 🙂
Ok…with these mods in place the s2member-files option now shows up in the Base Directory pull-down menu within the Directory Files shortcode modal.
However…the s2member-files option does not show up in the Base Directory pull-down menu under the File Uploads shortcode modal. Thoughts?
It’s not supposed to. You just have to build a path to it for file uploads. The File Up shortcode doesn’t need to know the directory it’s uploading to is “special,” whereas File Away needs to know it’s triggering a new kind of link, hence the special option in the dropdown.
Fair comment…I take your point.
It’s just that I upload and download from the same S2Member directory, which is a common practice I would expect, so if I add an entry in the plug-in options base directory list for it to show up in the Base Directory pull-down menu under the File Uploads shortcode modal it will then show up twice in the Base Directory pull-down menu within the Directory Files shortcode modal.
I just assumed if s2member-files was being treated as a “virtual 6th base directory” that it would show up everywhere the other 5 base directories show up.
No worries if things stay as they are. Works a treat with the new fix. Thanks again…much appreciated 🙂
Yeah you’re right. Adding s2member support was a process, so it’s kind of a patchwork I guess. It’ll work in [fileaway] now either way (the special option, or a standard base directory. If it finds “s2member-files” anywhere in the base, it’ll treat it as such. When I first added it, I did the special option but that was back before I even allowed you to use sub-directories with s2member files, so whatever. Anyway, I’ll take another look at it.
This fix will be in the next update (plugin active thing). Thanks for the heads up and the nice feedback!
You’re brilliant man…pleasure working with you 🙂
Pleasure working with you too. 🙂
3.6.2 is up. Marking as resolved.
