Support » Plugin: User Access Manager » Essential tool

  • Hi,

    The evolution since version is really very important.

    The support become more reactive.

    A great product but which is built on a complex object-model which is too implicit (see remark about documentation).


    Notes about others points noted by others users :
    1- Documentation :
    yes it is too light because the complexity of the object-model is not described.
    Which complexity ? : I think that “UAM” defines for the selection a lot more “objects” that are “groups of objects” than objects “groups of users” (objects here means : all post type, terms that are used in selection query of UAM), but both are true. The UAM-user-user-groups are bridges between objects and users.

    There are two points of view : the first, for me, is the association of objects to a “UAM group” (when editing them) which builds “objects groups”.
    But the other view comes when you define association of a “UAM group” to the WP-users-groups and associated rights : the “group of users” who have accesses rights to objects, when you have done you have done the first step of the creation of the group. But, by the way you have defined by the text the purpose of the groups and the rules of usage. Here the easier words to use to define the group define it as a “group of objects” with users accessibility as attributes rather than “a group of users”.

    In my opinion when you associate an object to an “UAM group” in fact you declare that this object instance is an element of the “group of objects” which has accesses rights by some groups of users more than indirect rights of accesses from the WP-users-groups.
    Note that this complexity is enhanced by the capabilities of the wp-users-groups.

    There is behind this what we named commonly an “object-model”, it is complex.

    The main UAM purpose is to simplify the structure of the links between objects and users.

    You can imagine that if you had to define manually for each object the wp-groups of users allowed to view and modify the object you will get an awful spider web (native WP).

    In fact you have purposes of management like “to define that a post belongs to a ‘groups of posts which are quite ready to be publishes and need to be read once again'”. Then this group of objects must be accessible by admin, author, contents manager, moderator (of contents), in fact this is further more complex because you can limit the rights of modification for any other user than author himself.
    UAM offers a good and efficient answer to this type of problem.
    But to build the right groups structure is complex and difficult.

    Note : For this I uses graphical tools designed to build objects-models. I build (have built) first conceptual model and after the instances of the model (each case of use) and later at the end I define the UAM-groups instances.

    • This topic was modified 1 year, 10 months ago by Trebly. Reason: large add-ons
  • The topic ‘Essential tool’ is closed to new replies.