Okay
  Public Ticket #4540467
Bug: Users can create similar store names and it creates similar store URL
Closed

Comments

  • Anthony started the conversation

    Hi,

    We found a bug where users can create stores similar to an existing one and the system fails to check them. This causes a problem since both stores with the same name can end up sharing the same store url.

    Ex.

    User1 -> registers: mystore -> /store/mystore

    User2 -> registers: mystore -> /store/mystore

    Both now uses the same store url

    Is there a way you guys can prevent the Store Settings in the dashboard to check if store or URL already exists so users couldn't end up sharing the same store URL?

    Thanks,

    Anthony

    Attached files:  samestorename.png
      sharingsameurl.jpg

  •  2,725
    WebWizards replied

    Hi Anthony,

    Thanks for reaching out,

    Store URLs are supposed to be unique - MarketKing does check this during account registration and prevents duplicate store URLs from being created. You can see how this works here in our demo: https://www.loom.com/share/6d72b1fc0c2749aca179eec12732f71a

    The store URL cannot be changed by vendors from their dashboard or after registration - only the site admin can modify it after registration.

    However, the store Name (the store "title") is not set as unique, so it's possible for 2 stores to have the same title. But each store URL should still be unique and enforced.

    If the URL enforcement is not working correctly on your site, it would help if you could share a link to your site's registration URL so I can take a look and see what might be causing this.

    Kind regards,
    Stefan

  • Anthony replied

    Hello,

    Is there a way you can add a setting that prohibits same business name? If someone could duplicate an existing store name, it can allow them to disguise themself as that store and fool buyers into thinking that they are buying from the same store.


    Thanks,

    Anthony

  •  2,725
    WebWizards replied

    Hi Anthony,

    Thanks for the update,

    I certainly see your point. Currently, we don't have a simple setting to enforce unique store names, though we are considering adding this as an option in future updates.

     

    As a workaround, I would suggest to let vendors choose the store name during registration, and then prevent them from changing it later.

    To do this, we can disable the ability for vendors to change the store name themselves via the dashboard. If you'd like to go this route, I can help you with a simple code snippet to disable that field.

     

    Kind regards,
    Stefan

  • Anthony replied

    I see. So is this a feature you can add in future updates?

    I guess it's fine for now. I could just add something to their Store name from the registration.

    Also, do you have snippets that could control the validation of store name in the backend? Instead of disabling, I think a validation would be better.


    Thanks,
    Anthony

  •  2,725
    WebWizards replied

    Hi Anthony,

    Thank you for the follow up,

    Yes, I agree this makes sense to have - we should at least have an option for it, so we would like to do it in a future update.

     

    If it helps, right now I believe I can write a code snippet for you that applies the validation when clicking 'Update User' in the backend and it would show an error if another user has the store name. Let me know if that would help.

    It would be a bit basic. For a AJAX automatic validation we would need more time to implement in a proper update.

     

    Kind regards,
    Stefan