Support » Plugin: WP Customer Area » Client can't see squat

  • Seems like it works ok in the backend but when logging in as the client, I can’t see the “private file” or “private page” I created for that client. That makes it totally useless. I set every possible permission for a user/subscriber to be able to view but still nothing.
    Also there’s a fix for bootstrap compatibility regarding menus not having submenu items. Applied the fix but it didn’t change anything.

    The alternative fix is to turn off the css for my theme and allow this plugin’s css to take over. Are you high?

    I’m not going to sit around here all day tweaking things to TRY and get it to work and besides, I’m not a programmer which seems to be what’s required to make it work. However, if I was a programmer, I probably wouldn’t need this plugin.

    Now there’s something a lot of plugin authors need to think about. “We’ve got tons of hooks and actions”. Well whoopdie doo. How about getting the basic plugin to work, then worry about the dev bells and whistles.

    A good permissions plugin, create your own menu, maybe a cpt and you’ve got what this plugin should do.

    SO what is this thing supposed to do? Make some content private. Other than that, this plugin doesn’t save any time.

    The dev needs to fix the bootstrap theme incompatibility issue because a LOT of themes are based on bootstrap. Let the theme’s css be used.

Viewing 1 replies (of 1 total)
  • Seems like it works ok in the backend but when logging in as the client, I can’t see the “private file” or “private page” I created for that client. That makes it totally useless.

    Well, I guess that’s the case with any plugin: if you cannot manage to make them work, they are useless…

    I don’t remember having seen any support request from you on the plugin’s official support forum. Permission issues usually come from:

    – Permissions not set at all
    – Permissions not properly set
    – Content owner not set to the proper user
    – Conflict with another plugin
    – Conflict with the theme

    We usually need 5/10 minutes to diagnose and correct the wrong setup.

    The alternative fix is to turn off the css for my theme and allow this plugin’s css to take over. Are you high?

    I don’t know where you read that, but we advise the following in case of theme conflict:

    – Check what is wrong with the Javascript and fix it in the plugin’s skin
    – Check which CSS rules are not working and remove them from the plugin’s skin (the skin system is flexible, you can create your own by copy/pasting the files)
    – If the problem is very hard to solve, and if the plugin is the only one that fits your requirements, install the plugin on a multi-site sub-domain and use another theme for that sub-site.
    – If the subdomain is not an option and if the plugin is the only one to fit your requirements, change your theme for a compatible one.

    No one forces you to use the plugin, and/or change your theme.

    SO what is this thing supposed to do? Make some content private. Other than that, this plugin doesn’t save any time.

    That’s already a big thing, because WordPress does not allow to publish private content. If you add on top of that a few add-ons, you can allow your client to create private content too, you can publish invoices, you can have private messenging, etc.

    Just ask other users, we have saved plenty of their time.

    I’m not a programmer which seems to be what’s required to make it work. However, if I was a programmer, I probably wouldn’t need this plugin.

    If you were a programmer you would on the contrary value your time and opt for ready made solutions even if you need to tweak them a bit. Basically that’s the reason why I have created that plugin, being a web developer myself and facing the absence of ready-made solutions when a client of mine needed a private area.

    A good permissions plugin, create your own menu, maybe a cpt and you’ve got what this plugin should do.

    No, that’s not what this plugin is supposed to do, but feel free to create your own plugin which does that, no worries.

    The dev needs to fix the bootstrap theme incompatibility issue because a LOT of themes are based on bootstrap. Let the theme’s css be used.

    This should mostly be solved with the 7.0 release which is scheduled for February 2016. However there will never be 100%-guarantee that the plugin works with any theme in the wild, that’s simply not possible.

Viewing 1 replies (of 1 total)
  • The topic ‘Client can't see squat’ is closed to new replies.