Review Section Big Blue box for non-logged in users

This topic has 2 replies, 2 voices, and was last updated 6 months, 1 weeks ago ago by Tony Rodriguez

  • Avatar: Blokey
    Blokey
    Participant
    November 3, 2023 at 11:49

    If a user goes to leave a review on a product page, unless they are logged in, they are faced with a big blue box that says “You have to be logged in to be able to add photos to your review”

    The box is so big that it covers the section where they leave their name and email address, so no one can actually leave a review.

    I’m ok with people having to be logged in to add a photo, but I want non-logged in people to be able to leave a review, and they can’t at the moment.

    1 Answer
    Avatar: Tony Rodriguez
    Tony Rodriguez
    Support staff
    November 3, 2023 at 12:47

    Hello, @Blokey,

    Thank you for contacting us and for using XStore.

    1) To resolve the problem you are experiencing, kindly follow the steps outlined below:

    1. Navigate to XStore.
    2. Select ‘Theme Options’.
    3. Proceed to ‘Theme Custom CSS’.
    4. Choose ‘Global CSS’.
    5. Copy and paste the provided CSS code into the designated area.
    6. Click ‘Publish’ to save the changes.

    .single-product .comment-respond .comment-form-author, .comment-respond .comment-form-email {
        float: none !important;
    }

    We trust this will rectify the issue at hand.

    2) By default, WooCommerce allows only logged-in users to leave reviews to prevent spam and maintain the credibility of reviews. Enabling non-logged-in users to leave reviews without using custom code or plugins is not a built-in feature of WooCommerce.

    You are welcome to utilize any third-party plugin for your needs. However, please be advised that you do so at your own risk.

    Should you require further assistance, please do not hesitate to contact us.

    Best Regards,
    8Theme’s Team.

  • Viewing 2 results - 1 through 2 (of 2 total)

The issue related to '‘Review Section Big Blue box for non-logged in users’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.