orcasdev

orcas - Mario Gleichmann

<p><em>orcas Responsive Wiki</em> is currently the once wiki with <em><a href="/plugins/buddypress/" rel="nofollow ugc">buddypress</a> support</em> ( <a href="https://www.orcas.de/wordpress-plugin/wiki/" rel="nofollow ugc">pro version needed</a> ) to get every buddypress group its own wiki.</p>
<p>At default our plugin allows registered users to edit wiki documents in the frontend. In addition, it is possible to set which users or roles can create or modify wiki documents. With the WYSIWYG editor you can insert and manage tables and you can insert images per drag and drop. As highlight can you input <code>wiki:</code> to get an auto complete list to insert links to other wiki pages.</p>
<p>You can it also use to build term overviews, dictionaries, encyclopedias, glossaries, knowledge bases and lexicons.</p>
<p>With <em>orcas Responsive Wiki Pro</em> you get additionally a revisions history.</p>
<h3>Features</h3>
<ul>
<li>Optimized for mobile devices.</li>
<li>Editing in frontend possible.</li>
<li>Unlimited wiki pages.</li>
<li>Restrict your wiki, who can create/update wiki pages.</li>
<li>WYSIWYG editor (What You See Is What You Get), write wiki pages like a word document.</li>
<li>Insert images in your wiki with drag and drop.</li>
<li>Create and modify tables in your wiki.</li>
<li>With auto complete function after keyword <code>wiki:</code> you can insert links to other wiki pages.</li>
<li>“pinterest”-style overview.</li>
</ul>
<p><strong>orcas Responsive Wiki Pro Features</strong></p>
<ul>
<li>Buddypress group support.</li>
<li>Revisions view.</li>
</ul>
<h3>Shortcodes</h3>
<ul>
<li>[wiki_add_create_button] – Add a external button to open the create form.</li>
<li>[wiki_add_create_link] – Add a external link to open the create form.</li>
</ul>


orcas Responsive Wiki

Buddypress wiki where registered users in the frontend can edit the same document after each other.

Chris Dennis

<p>‘Private’ uploaded files (PDFs, images, etc.) will normally be only included in private posts and pages.  But the files themselves can still be accessed by anyone if they know the corresponding URLs.</p>
<p>For example, a PDF file’s URL might be</p>
<pre><code>http://example.com/wp-content/uploads/minutes-20160924.pdf
</code></pre>
<p>and anyone could download that file because WordPress does not get a chance to check their authorisation.</p>
<p>The solution that the Private Uploads plugin uses involves moving any private files to a separate folder, and then configuring the web server to ask WordPress to authenticate access to files in that folder.</p>
<p>So the file’s URL might now be</p>
<pre><code>http://example.com/wp-content/uploads/private/minutes-20160924.pdf
</code></pre>
<p>and an HTTP server rewrite rule will convert this to</p>
<pre><code>http://example.com/?pucd-folder=private&pucd-file=minutes-20160924.pdf
</code></pre>
<p>The Private Uploads plugin will intercept that URL and reject it with a 403 status code.</p>
<p>This plugin is more efficient than some similar ones because it only has to run when serving files in the private folder(s): the web server handles other uploaded files (ones not in the private folders) directly.</p>
<h3>Requirements</h3>
<ul>
<li>Sufficient access to the web server to allow the required configuration.</li>
</ul>
<h3>Acknowledgements</h3>
<ul>
<li>This plugin was inspired by a discussion on <a href="https://wordpress.stackexchange.com/questions/37144/how-to-protect-uploads-if-user-is-not-logged-in" rel="nofollow ugc">StackExchange</a>.</li>
</ul>
<h3>Future Plans</h3>
<ul>
<li>Currently, access to private files just depends on the <code>is_user_logged_in()</code> function.  This plugin could be developed to give more fine-grained control, such as having a folder for each user.</li>
</ul>


Private Uploads

Simple, works well, just perfect for me.
Some tips:
With the Plugin User Role Editor you can add a role like view_private_file and choose which user roles can access it. You can also redirect to a access denied page. Just modify in the Plugin file the function send_private_file like this:

    // Only return files to logged-in users
    if (!is_user_logged_in() || !current_user_can('view_private_file')) {
        header("Location: https://www.yoursite.com/access-denied");
        die();
    }


Perfect

Protects sensitive uploaded files so that only logged-in users can access them. The plugin depends on corresponding web server (e.g.

orcas Responsive Wiki vs Private Uploads