This topic contains 5 replies, has 2 voices, and was last updated by  Cici 7 months, 1 week ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
  • #54540


    User managed location plugin working fine in local and user logged in to wp-admin but we have conflict with woocommerce in development server , new user always be a sabscriber and in woocommerce subscriber haven’t permission to access wp-admin strictly if we do that and it will redirect to wp-admin but there is also some other permission to add and delete posts ,

    we have also tried to add new store user with different user role like store-user , they also haven’t permission of wp-admin if we will give permission to it there is also same problem of some other permission to view and add posts and other menus in right side admin bar



    Please help me on this,

    Waiting for your reply on it.

    Store Locator Plus:4.8.3
    User Managed Locations:4.5.03

    Site URL:
    credential : admin/ admin
    This Info Cached:1503325252
    Network Active:No

    WordPress Version:4.8.1
    MySQL Version:5.7.17

    PHP Limit:256M
    WordPress General Limit:40M
    WordPress Admin Limit:256M
    PHP Peak RAM:83 MB
    PHP Post Max Size:8M




    What happened to product support? We have an outstanding question and nobody has responded.



    We have reached out to DeBaat who owns the USER Managed Locations plug-in. I have recently sent him another email request. Our Third Party agreements do not allow us to patch those authors plug-ins. Please send an email to customer support so we can forward your email to him.



    Your site appears to be working , have you checked the Woocommerce forums for solutions? Woocommerce is constantly updating and changing their algorithms.

    Here is their debugging info:

    They recommend always update a staging site first and Debugging a White Screen or Error 500
    If you find a white screen or error 500 that usually means something has triggered a PHP error, but errors are hidden on your server. To find out the cause of the error you have two choices:

    Look at your server error logs and find the latest ‘fatal error’
    Enable WP_DEBUG mode and view the page again
    Enabling WP_DEBUG involves editing your wp-config.php file and changing, or adding if its not there:

    define( ‘WP_DEBUG’, true );
    When this is done, a more useful error message should be shown. Most of the time this contains the name of the plugin and the line number causing the issue allowing you to act.

    Debugging Functionality Issues
    If something is not working after an update, a likely cause is an outdated or non compatible plugin or theme. The best thing to do is to narrow down the cause. To do this you can temporarily:

    Switch to a default WordPress theme (Twenty Twelve) and test again
    Disable all other plugins except for WooCommerce itself, retest, and re-activate plugins until the issue occurs. This will help you find the culprit.
    Memory Issues
    If after doing the above steps you find that you are hitting the memory limit, you can increase WordPress’ limit. See here.

    For More Help
    See our self-service guide here.

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.