Databases
StackOverflow2013
Postsdbo
POPersonalized protected frontend content on a "per User" base in Wordpress
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPersonalized protected frontend content on a "per User" base in Wordpress
    primarykey
    data
    text
    <p>For a current project i need to provide some of the client's clients (you go it? =) some kind of protected frontend content area. This area should hold protected content on a "per User"-base.</p> <p><strong>For example:</strong> Tom from (lets call the company EXCORP) wants to provide <strong>User A</strong> with a document (PDF) and some Text (HTML-Content). But(!) <strong>User B</strong> would get a totally different document and maybe some more Text. <strong>User C</strong> would possibly not get a document at all.</p> <p>This Game goes on for circa another 150 users or so. So going by "default" roles doesn't work here, since i would have to create one user-role per user and that would definitely overkill it. And all the Membership Plugins i've found do not work that way.</p> <p>Just to make that clear: This thing only goes one way. Meaning, Client-Supporter Tom (in example above) needs to provide all the clients some personalised information. Tom would be a Backend-User. Clients do not need to provide eachother some files or information. Just from one Backend-User to all the different Frontend-Users.</p> <p>So my question clearly spoken: <strong>Is there a way to protect frontend content on a "per User"-base using Wordpress?</strong> It doesn't matter to me if I get it to work the "hacky" way, or by a premium/free plugin, as long as it is safe (I will use SSL of course). I just don't want to develop a plugin from scratch, though my client would never speak the budget to pay for it!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJeremy Zahner
    1. USJeremy Zahner
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COhow are you deciding what content to show to which user? on the basis of user id ?
      singulars
      1. POPersonalized protected frontend content on a "per User" base in Wordpress
      1. UScodepixlabs
    2. CO@wordpresser yes, that could be one way. Though i didn't really consider the technical issues yet. I would have to do that if i don't find a already working solution. Fact is: every single user would/should have his/hers completely personalized page(s).
      singulars
      1. POPersonalized protected frontend content on a "per User" base in Wordpress
      1. USJeremy Zahner
    3. COyou mean as per your example User A will have same authority as Tom, i.e to publish some text and docs and decide who gonna see what .. ?
      singulars
      1. POPersonalized protected frontend content on a "per User" base in Wordpress
      1. UScodepixlabs
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload