Alignment changed for a restored Website

This topic has 4 replies, 3 voices, and was last updated 3 weeks, 3 days ago ago by Tony Rodriguez

  • Avatar: Eslyn Dsouza
    Eslyn Dsouza
    Participant
    February 16, 2026 at 14:22

    HI Team, I tried restoring my website from an older backup copy on Hostinger and now find that the alignment for images and colletion seem to be elongated or misplaced now. Please advise on how to fix this.

    Files is visible for topic creator and
    support staff only.
    3 Answers
    Avatar: Andrew Mitchell
    Andrew Mitchell
    Support staff
    February 16, 2026 at 16:53

    Hi,

    Thank you for reaching out to us. We understand that after restoring your website from an older backup on Hostinger, the image and collection alignment appears elongated or misplaced.

    Please try the following steps:
    1. Clear your website and browser cache to ensure you are viewing the latest version of your site.
    2. Check if your theme and all related plugins are updated to their latest versions.
    3. If you are using any custom CSS or modifications, temporarily disable them to see if the issue persists.
    4. If the problem continues, please provide us with temporary admin access.

    Best regards,
    The 8Theme Team

    Avatar: Eslyn Dsouza
    Eslyn Dsouza
    Participant
    February 16, 2026 at 19:54

    Thanks for the support! My topic “Alignment changed for a restored Website” has been successfully resolved.

    Avatar: Tony Rodriguez
    Tony Rodriguez
    Support staff
    February 16, 2026 at 19:54

    Dear Eslyn Dsouza,

    Thanks for being part of our WordPress & WooCommerce community!

    We’re happy we could assist you. Your feedback truly matters — it helps us make XStore better, faster, and more reliable with every release.

    Together, we’re shaping a better WooCommerce experience for everyone.

    Topic closed.
    The 8Theme Team

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

The issue related to '‘Alignment changed for a restored Website’' 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.