Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter jeremie

    (@jeremie)

    Too quick with the post message.
    So, I guess I shall use the ‘custom fields’ so ‘index.php’ (or whatever handling that) know how to handle this, but where I start ? I’m lost ??

    Unfortunately, the encoder tool is wrong, for compatibility reasons the decimal entity should be used.
    And it doesn’t solve the problem, even with an entity the letter is supressed from the url-path.

    BTW, is there a way to specify an URL for a category ?
    If the name of the category contain non-url letters, lets say something like ?????§?¨?? and the like, the letter is suppressed from the url-path.
    I would like to change that, by specifying an URL-path myself for each category, or if WP would transform the letter to an ascii one (?′ into o for example) that would be fine too.

    Drupal seems very good, but doesn’t work (yet ?) on my target environnement.
    Too bad if WP would stay single user…

    That would be a step in the right direction. But I really fail to see the flexibility in level at all (as in lower/upper level).
    Can’t we simply have some flags (one flag by function in WP), and the admin assign these flag user by user… ?
    In this scenario, it’s even easier to handle post|categories rights (as in acess/view/edit) management, we simply assign a custom flag for each protected post and/or categories (and the posts within) and give it to the users we want.
    So it would be something like: for the category “PrivateClub”, I give the access flag (can read posts/news/comments) to users #4, #62 and #98; and only these three users (and the admins) can read posts in that category even in the backend. And I may give the write flag (can edit the posts in that category) to user #62, so only him can write posts in that category, and so on.
    Very much like unix rights in fact….
    That would be very, _VERY_ useful.

    Forum: Plugins
    In reply to: ViewLevel plugin

    Would it be possible to include in a next release an option to separate the rights of access ?
    I don’t need a hierarchical system, I would rather prefer something like: each level (0 to 9) is a separate usergroup, and you can “attach” a post to one or several usergroup.
    Let’s say you wrote the post “MySpecialPost” and attach it to usergroups 2, 4 and 6.
    Users at the level 2, 4 and 6 (and the admin) can access the post, but users at level 0,1,3,5,7,8,9 can’t.
    ‘know what I mean ?

    Forum: Plugins
    In reply to: ViewLevel 1.1 Release

    https://www.furbona.org/ is down, can anyone post a mirror somewhere ? Pleeeeaaase ? ??

    Thread Starter jeremie

    (@jeremie)

    Seems that Viewlevel may be the right tool to do something close, but https://www.furbona.org/ is down for now ??

    Thread Starter jeremie

    (@jeremie)

    I’ve overlooked the ViewLever plugin, but I don’t know is it’s able to do this.
    Nope, no ban or not public ?? It’s for a CMS usage: a community site, maybe 20 users (to start with), all of them have to write post from time to time. One or two of them are admin, able to do whatever they want; but the others have to be able to read (from the frontend or the backend) only specific posts and/or categories, and not be able to read others specifics posts|categories.
    How do I put that…ok let’s take a company intra/extra-net/webiste for example: you have the customers, who just read public posts. But you have ancient, or “advanced” customers who can wrote posts to help others so they have backend access, but they can’t be allowed to access in any way specific posts/categories even in the backend. And you have company employees… you don’t want a C++ intern developper newbie to have access to internal marketing posts, or accounting posts…and so on.
    See what I mean ?
    Sorry for the laborious explanation, I’m not english speaking native.
    Si, what I need is a way to say:
    – this post (and/or category) can’t be read by the users x, y and z; even in the backend.
    and even better:
    – this post can’t be access at all, except for the users a, b and c.
    and so on, and so on, and so on.
    Really alike any modern right management… like in unix, or MySQL, and the like.
    Can I do that with WP ? Or a plugin ? Or a hack ?

    Thread Starter jeremie

    (@jeremie)

    I’ve seen that, and it work in the backend too. But when you have several users/usergroups to deal with, and several posts each of them with differents accessibility policies, it’s starting to be a nightmare to handle dozens of passwords.
    Is there a way to tell WP, post by post, and/or categories by categories:
    – this post/categorie is (or is not) readable by default
    – these users override the default, and thus can (or can not) access this post (or the posts within the categorie) even in the backend
    ?

Viewing 10 replies - 1 through 10 (of 10 total)