Join our new community forum for support & discussion

Join Now

Home Support Themes ExpertHive Requests

Requests

  • Author
    Posts
  • Absinthko

    Hallo. I want to clarify something.
    Lets say I am vendor and I add 1 listing using FREE 10 LISTINGS PACKEGE. After I sumbit that 1 listing, I am eligible to send Requests to users and making deals with them. In this situation, vendor doesnt need to create any other lisitng because he is in touch with users (sending them messages in Requests). Therefore vendor never needs to add another listing and is basically using website for free.
    How can I prevent that kind of behaviour?
    Thank you

    ihor developer

    Hi,
    This depends on your business model, if you use listings as separate services then vendors would want to add multiple listings (a listing for each service, so each service can have different details/category to allow users to find it). If this is not the case you can charge a commission on every order made via the website (by using Marketplace), or even block messaging until the order is made (in HivePress/Settings/Messages). Also, you can consider using Memberships extension to charge users for messaging vendors – there are a few different ways of monetization.

    Absinthko

    Thank you for response.
    My business model is:
    – free for users to see listings and contact vendors, make deal with them via massages
    – make payed packages for vendors with listings limit and different expiration periods

    What I want to ask you:
    1. I want to make Requests page visable only for vendors- Is that possible with Membership extesion?
    This way I want to prevent anyone to see requests and contacting customers without being vendor.
    2. Other way of solving my problem woud be to ban users to post contact information (phone number, email etc.) to Request description, so when the Request page remains Public, there will be no way of contatcing this user but only using my website and become a vendor.
    Thank you

    ihor developer

    Thanks for the details.
    1. If you mean just blocking the requests page (not single request pages, blocking these would also block the request author) it may be possible with a simple code snippet, e.g. for redirecting non-vendors to some page (if you have some landing page for becoming a vendor). Please let me know if this works for you.

    2. It would be hard to prevent this, but you can try setting blocked words or word parts in HivePress/Settings/Messages, also you can enable request moderation.

    Absinthko

    Redirecting non vendors after they click to Requests in header to other page where they can Log in or Create account would be perfect. But I am not sure how to create page with Log in form for them. If you can tell me how to do that and also send code snippet I would be grateful. Thank you

    yevhen developer

    Please try this PHP snippet

    add_action(
    	'template_redirect',
    	function() {
    		if(is_post_type_archive('hp_request') && !current_user_can('edit_posts') ){
    			wp_safe_redirect(hivepress()->router->get_url('user_account_page'));
    		}
    	}
    );
    Absinthko

    Hallo, I added this snippet to Code Snippets plugin but Requests are still visable for non signed in users. Any idea what may casue this? Maybe that I use different language on site…? Thank you

    ihor developer

    Please let me know if you mean the Requests page (and the request search page) or a single request page? This snippet should redirect regular users (not vendors) from the Requests page, but the single request pages will still be visible via direct URLs.

    Absinthko

    I mean Request page (which shows after clicking on- Requests in header menu). I visited site without being signed in and was able to click on Requests and see whole request page. I was also able to visit single Requests from main Request page. Maybe I didnt use the snippet correctly, but I am not sure.

    yevhen developer

    Please try this PHP snippet:

    add_action(
    	'template_redirect',
    	function() {
    		if((is_post_type_archive('hp_request') || is_singular('hp_request')) && !current_user_can('edit_posts')){
    			wp_safe_redirect(hivepress()->router->get_url('user_account_page'));
    		}
    	}
    );
    Absinthko

    Thank you. This snippet works, it is able to see the main request page but when you click on one of the requests, it redirects you to Log-in site. Solved my problem, thank you very much.

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

The topic ‘Requests’ is closed to new replies.