Support » Plugin: Point of Sale POS for WooCommerce » Name and Surname are not registered when add a new client

  • When I add a new client from the POS frontend, a new user is created without Name and Surname, only invoice and shipment fields are filled. Problem is when you search a client in the POS frontend, you can´t find him using his name or surname, you must search for the user name which was filled with the first part of the registered email address.

    This is not the best practice. Someone should be able to find a client by their name or surname, not only by their email address (user name).

    How can I add client’s name and surname with the same data filled in Invoice Data?

    Thanks

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author bizswoop

    (@bizswoop)

    The POS customer search function, https://ibb.co/NnKnDLK does support finding a customer by the following parameters in the search field:

    First Name
    Last Name
    Username
    Email
    Phone Number
    Billing_company

    And in the POS, we allow you to either edit an existing customer, by clicking the Edit icon https://ibb.co/C8X4YZQ, or clicking the Add New Customers. We allow you to create a customer based upon the standard customer detail fields.

    We hope this helps explains the Customer search supported functionality. If we misunderstood the question, please let us know and if possible, send us a screenshot, so we can better understand the question.

    I have challenges that I can not find customers when I use “search for customers” it loads and does not finish. How can that be? All other features seem to work. I can also create customers.

    Plugin Author bizswoop

    (@bizswoop)

    Our first recommendation is to check the permissions for the user accessing the POS and ‘searching for customers’

    Make sure the permission ‘list_users’ is enabled for the user role, as shown here
    https://ibb.co/b21t8k1

    If this is enabled. Our next recommendation is to perform a conflict plugin test. If you are using any other plugins that modify user roles or user role types, this could be causing a conflict with the POS search functionality. The conflict testing, outlined here: https://www.bizswoop.com/plugin-theme-conflict-test/ is easy to perform. Deactivate all plugins, except WooCommerce and the POS. Now launch the POS and search for customers.

    If even after the conflict testing is performed, the issue continues. Please send us any error logs from WooCommerce > Status > Logs. And any PHP Error logs. We will need to review the logs to better understand why the search functionality is not working for your setup.

    I have been following the guide and I have not made it work. I have removed the plugin and installed it again. I have disabled all plugins, it rather did not work.

    I do not see that the page has any errors.
    We are otherwise really happy with the plugin, and are considering buying the license package. but we would like to test it a little more.

    Can I try to send you a login to the site by e-mail?

    Plugin Author bizswoop

    (@bizswoop)

    Unfortunately, as part of our support policy for users on WordPress.org we won’t login to websites for security and privacy reasons. Sorry we can’t provide this type of support on the forum.

    A few other things you should rule out.

    – Chrome Console Errors. The Chrome console errors, you can check yourself. When performing a customer search. Right click, Click Inspect. Click Console. Are you seeing any errors? Error entires could provide more information on why the request to find customers is not returning results.

    – PHP Logs. Pull the website PHP logs to evaluate any error entries that might be occurring. During a Customer search, the POS is performing an API call. If a result is not returned, or the request is timing out. The PHP logs should provide more information on why.

    A quick final note. If you have used any plugins in the past to modify WordPress user role types, like a membership or wholesale type plugin. The modification to the role permissions could be resulting in this behavior. Simply deactivating this plugin will not revert the behavior in the database. We’d recommend you review any type of user role permission modifications you made as part of your troubleshooting efforts. Hopefully either the Browser Console Logs, PHP Logs or reviewing user role permissions will resolve the issue you for you or provide insights on why it’s occurring on your configuration.

    I found an error. but I can not read the problem from the error. Can you read what the error is based on this:

    Failed to load resource: the server responded with a status of 404 (Not Found)
    index.jsx:96 Error: Request failed with status code 404
    at module.exports (createError.js:16)
    at module.exports (settle.js:17)
    at XMLHttpRequest.request.onreadystatechange (xhr.js:59)
    (anonymous) @ index.jsx:96
    /index.php?rest_route=/wc-pos/customers?search=mal&per_page=50&role=all:1 Failed to load resource: the server responded with a status of 404 (Not Found)
    index.jsx:96 Error: Request failed with status code 404
    at module.exports (createError.js:16)
    at module.exports (settle.js:17)
    at XMLHttpRequest.request.onreadystatechange (xhr.js:59)
    (anonymous) @ index.jsx:96
    tryCatch @ runtime.js:45
    (anonymous) @ runtime.js:271
    forEach.prototype.<computed> @ runtime.js:97
    Select_asyncGeneratorStep @ app.js?e8d17f3b0018755af78c&version=2.2.1&ver=5.6:2
    _throw @ app.js?e8d17f3b0018755af78c&version=2.2.1&ver=5.6:2
    xhr.js:172 GET https://bptogo.dk/index.php?rest_route=/wc-pos/customers?search=mal&per_page=50&role=all 404 (Not Found)
    (anonymous) @ xhr.js:172
    module.exports @ xhr.js:11
    module.exports @ dispatchRequest.js:57
    Promise.then (async)
    Axios.request @ Axios.js:53
    utils.forEach.Axios.<computed> @ Axios.js:68
    (anonymous) @ bind.js:9
    (anonymous) @ index.jsx:85
    tryCatch @ runtime.js:45
    (anonymous) @ runtime.js:271
    forEach.prototype.<computed> @ runtime.js:97
    Select_asyncGeneratorStep @ app.js?e8d17f3b0018755af78c&version=2.2.1&ver=5.6:2
    _next @ app.js?e8d17f3b0018755af78c&version=2.2.1&ver=5.6:2
    (anonymous) @ app.js?e8d17f3b0018755af78c&version=2.2.1&ver=5.6:2
    (anonymous) @ app.js?e8d17f3b0018755af78c&version=2.2.1&ver=5.6:2
    invokeFunc @ debounce.js:95
    trailingEdge @ debounce.js:144
    timerExpired @ debounce.js:132
    setTimeout (async)
    timerExpired @ debounce.js:135
    setTimeout (async)
    leadingEdge @ debounce.js:103
    debounced @ debounce.js:172
    ih @ react-dom.production.min.js:193
    hh @ react-dom.production.min.js:193
    Vh @ react-dom.production.min.js:216
    Zh @ react-dom.production.min.js:220
    (anonymous) @ react-dom.production.min.js:250
    exports.unstable_runWithPriority @ scheduler.production.min.js:18
    Fi @ react-dom.production.min.js:250
    Di @ react-dom.production.min.js:249
    Yh @ react-dom.production.min.js:248
    Ib @ react-dom.production.min.js:262
    Kb @ react-dom.production.min.js:39
    Dd @ react-dom.production.min.js:86
    (anonymous) @ react-dom.production.min.js:251
    exports.unstable_runWithPriority @ scheduler.production.min.js:18
    Ii @ react-dom.production.min.js:251
    Cd @ react-dom.production.min.js:85
    index.jsx:96 Error: Request failed with status code 404
    at module.exports (createError.js:16)
    at module.exports (settle.js:17)
    at XMLHttpRequest.request.onreadystatechange (xhr.js:59)
    (anonymous) @ index.jsx:96
    tryCatch @ runtime.js:45
    (anonymous) @ runtime.js:271
    forEach.prototype.<computed> @ runtime.js:97
    Select_asyncGeneratorStep @ app.js?e8d17f3b0018755af78c&version=2.2.1&ver=5.6:2
    _throw @ app.js?e8d17f3b0018755af78c&version=2.2.1&ver=5.6:2
    Promise.then (async)
    Select_asyncGeneratorStep @ app.js?e8d17f3b0018755af78c&version=2.2.1&ver=5.6:2
    _next @ app.js?e8d17f3b0018755af78c&version=2.2.1&ver=5.6:2
    (anonymous) @ app.js?e8d17f3b0018755af78c&version=2.2.1&ver=5.6:2
    (anonymous) @ app.js?e8d17f3b0018755af78c&version=2.2.1&ver=5.6:2
    invokeFunc @ debounce.js:95
    trailingEdge @ debounce.js:144
    timerExpired @ debounce.js:132
    setTimeout (async)
    timerExpired @ debounce.js:135
    setTimeout (async)
    leadingEdge @ debounce.js:103
    debounced @ debounce.js:172
    ih @ react-dom.production.min.js:193
    hh @ react-dom.production.min.js:193
    Vh @ react-dom.production.min.js:216
    Zh @ react-dom.production.min.js:220
    (anonymous) @ react-dom.production.min.js:250
    exports.unstable_runWithPriority @ scheduler.production.min.js:18
    Fi @ react-dom.production.min.js:250
    Di @ react-dom.production.min.js:249
    Yh @ react-dom.production.min.js:248
    Ib @ react-dom.production.min.js:262
    Kb @ react-dom.production.min.js:39
    Dd @ react-dom.production.min.js:86
    (anonymous) @ react-dom.production.min.js:251
    exports.unstable_runWithPriority @ scheduler.production.min.js:18
    Ii @ react-dom.production.min.js:251
    Cd @ react-dom.production.min.js:85

    We have not set up a pretty links structure. We use default links in permalinks. can it be that?

    I found an error. but I can not read the problem from the error. Can you read what the error is based on this:

    index.jsx:96 Error: Request failed with status code 404
    at module.exports (createError.js:16)
    at module.exports (settle.js:17)
    at XMLHttpRequest.request.onreadystatechange (xhr.js:59)
    (anonymous) @ index.jsx:96

    Plugin Author bizswoop

    (@bizswoop)

    Thanks @mads2021 for all the logging information. This is helpful to understand a bit of the behavior. We do think it’s related to the permalinks behavior. Before we make a final conclusion.

    Can you send us one more log, it’s easy to trigger.

    Launch the POS. Attempt to Search for Customers. Now, click the menu in the upper left. Scroll down to Support. A support window will show. Fill out the support form with you information, make sure the option ‘Send POS system report’ is checked. This will send us one final report we’d like to review. Once that support ticket is generated, we will follow-up with you directly on that ticket.

    Thanks @bizswoop for the support. I hope we can find fault with you. we are still very interested in buying your full checkout system.

    As a thank you for the support help, we have also translated your system into Danish, which we are now sending for approval

    Launch the POS. Attempt to Search for Customers. Now, click the menu in the upper left. Scroll down to Support. A support window will show. Fill out the support form with you information, make sure the option ‘Send POS system report’ is checked. This will send us one final report we’d like to review. Once that support ticket is generated, we will follow-up with you directly on that ticket.

    DONE!

    Plugin Author bizswoop

    (@bizswoop)

    Thank you. We received the log and send a follow-up to you via the provided email on the ticket.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Name and Surname are not registered when add a new client’ is closed to new replies.