alloverride, and internal privacy choices (two issues)

  • Resolved songdove

    (@songdove)


    3 years, 11 months ago

    So I searched the support list first, and found this code for the .htaccess file:

    # BEGIN BuddyPress Docs
RewriteEngine On
RewriteBase /
RewriteRule (.+) ?bp-attachment=$1 [R=302,NC]
# END BuddyPress Docs

    It broke my site as it couldn’t find something related to “your plugin” as it put it. I amended the base to state the folder the site is in, as it’s a multi-site installation. Still broke the site. I moved it to the top of all my various other plugin rewrites, and no change so I had to remove it from the .htaccess file. I was editing the main wordpress .htaccess.

    I’ve sent a request to my host asking about this.

    Secondly, Any chance the plugin might allow for greater privacy choices beyond “group, anyone and logged in user”??? I’m hoping for “my friends” being added in there as well. Would there be anything I could throw into bp_custom.php to add that to the document privacy choices?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author David Cavins

    (@dcavins)

    Hi @songdove,

    You are correct, that htaccess rule is not meant to go in the root htaccess file. Those are generated when saving a protected doc, and the .htaccess file pertaining to that doc is created in /wp-content/uploads/bp-attachments/{the_doc_id}

    An example might look like:

    # BEGIN BuddyPress Docs
RewriteEngine On
RewriteBase /docs/{doc_title}/
RewriteRule (.+) ?bp-attachment=$1 [R=302,NC]
# END BuddyPress Docs

    If you navigate to /wp-content/uploads/bp-attachments you should see a number of folders, each labeled with a doc ID, and that’s where those specific htaccess files will be written.

    Regarding “my friends” as a privacy choice, I agree that that would be useful. I have not had time to build that feature, but plan to when time allows.

    Thread Starter songdove

    (@songdove)

    This can’t be done site-wide for whoever creates any document??? I have to throw this into every single document’s folder manually??? That’s a huge flaw! There should be a global way to protect user-created documents.

    Plugin Author David Cavins

    (@dcavins)

    You don’t have to do it at all. BP Docs creates the htaccess files for you when needed, and the special htaccess file is only required for protecting attachments, not the documents themselves.

    Thread Starter songdove

    (@songdove)

    Oh ok, I thought this was necessary in relation to various discussions I read where it appeared this had to be added for allowoverride to do its job. I have my host looking into allowoverride, but based on other redirect statements in my main .htaccess file, I assumed it was already on.

    Thread Starter songdove

    (@songdove)

    Ok I confirmed that overrride is on. Why else would I still be told that my users’ documents may still be open to the public? My webhost confirmed that override is on server-wide (shared server hosting). I had sent them the wiki page linked from the notification in my admin back end.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘alloverride, and internal privacy choices (two issues)’ is closed to new replies.