• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Site logo alignment doesn't work, when published

JussiK

New Pleskian
PRODUCT, VERSION
Web presence builder STANDALONE 11.5.4.

PROBLEM DESCRIPTION

Changing Site logo alignment, which has been brought from add-on modules has no affect on a published site. It works in preview of the site builder, but not when the site is published.

STEPS TO REPRODUCE

Add a Site logo (from modules)
Change the alignment to center
Publish the site and check the result

ACTUAL RESULT
The site logo alignment changes on site builder, but not on a published site.

EXPECTED RESULT
The site logo alignment should change also on a published website
 
What's the situation on this? Is additional information needed or do I need to make an official ticket about it?
 
Hello,
I see that this bug has already been fixed in the WPB 11.5.6 update.
Release of this update is planned at the next week.

Thanks for your bug report!
 
Back
Top