{"id":1551,"date":"2025-06-03T14:00:00","date_gmt":"2025-06-03T12:00:00","guid":{"rendered":"https:\/\/www.panelalpha.com\/blog\/?p=1551"},"modified":"2025-06-03T15:31:17","modified_gmt":"2025-06-03T13:31:17","slug":"panelalpha-v1-4-1-awstats-integration","status":"publish","type":"post","link":"https:\/\/www.panelalpha.com\/blog\/panelalpha-v1-4-1-awstats-integration\/","title":{"rendered":"AWStats integration and smarter UX choices – PanelAlpha v1.4.1"},"content":{"rendered":"

If you’ve been keeping tabs on PanelAlpha, you already know that it’s not the kind of platform that adds features just to fill a changelog. When something gets introduced, it’s because it naturally found its way into many requests shared across our community. Version 1.4.1<\/strong> introduces a new default stats engine, more flexibility in the client area, and a number of refinements based on direct user feedback. All of it reflects what we continue to learn from how PanelAlpha supports actual WordPress hosting scenarios.<\/p>\n

AWStats: A clearer wiew, built right in<\/strong><\/p>\n

Since the beginning, we’ve offered different ways to track website statistics, including Matomo and Google Analytics. Starting with version 1.4.1, AWStats<\/strong><\/a> becomes the default option for all hosting types<\/strong>.<\/p>\n

We made this change for a few simple reasons: AWStats is lightweight, fast, and doesn’t rely on JavaScript or cookies. It runs entirely on the server side, which means no impact on page performance and no need to configure anything extra<\/strong>. From the moment a site is set up, basic traffic and usage data is collected automatically, securely and privately, without requiring any third-party integration.<\/p>\n\n\n

\"AWStats<\/a><\/figure>\n\n\n

Of course, Matomo and Google Analytics are still available for those who need them. But for the majority of everyday use cases, we believe AWStats offers the right balance of simplicity, speed, and privacy. That’s why it’s now built into the core system, via a dedicated container that handles stats collection behind the scenes. This means fewer steps for you, and faster access to meaningful data<\/strong> for your clients.<\/p>\n

Dark Mode: Now it’s personal<\/strong><\/p>\n

Dark Mode<\/strong><\/a> joined the client area in version 1.3.0<\/strong><\/a>, after being quietly at the top of many wish lists. At the time, it was up to the hosting provider to choose how the panel would appear for everyone. We heard clearly from both sides that there’s more to be done.<\/p>\n\n\n

\"Dark<\/a><\/figure>\n\n\n

In version 1.4.1, you can now give clients full control over the theme they prefer. All it takes is enabling one option, and each user can switch between Light and Dark Mode<\/strong> on their own, whenever they like. This is just as much about visual preference, as it is about giving people the ability to work the way they’re most comfortable, whether that’s a bright interface during the day or a darker one late at night. A small shift that adds a lot of personal comfort.<\/p>\n

Progress guided by real conversations<\/strong><\/p>\n

Among 10<\/strong> improvements and 43<\/strong> handled issues in PanelAlpha v1.4.1, many come from the conversations we’ve had through tickets or casual Discord chats. These aren’t abstract ideas, but practical changes that smooth out the small bits of your daily routine. You’ll find the full list in the changelog, but what matters most is that each of these updates is rooted in real-world situations our users have shared with us.<\/p>\n

View full changelog<\/span><\/a><\/p>","protected":false},"excerpt":{"rendered":"

If you’ve been keeping tabs on PanelAlpha, you already know that it’s not the kind of platform that adds features just to fill a changelog. When something gets introduced, it’s because it naturally found its way into many requests shared across our community. Version 1.4.1 introduces a new default stats engine, more flexibility in the […]<\/p>\n","protected":false},"author":3,"featured_media":1572,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/posts\/1551"}],"collection":[{"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/comments?post=1551"}],"version-history":[{"count":21,"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/posts\/1551\/revisions"}],"predecessor-version":[{"id":1584,"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/posts\/1551\/revisions\/1584"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/media\/1572"}],"wp:attachment":[{"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/media?parent=1551"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/categories?post=1551"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.panelalpha.com\/blog\/wp-json\/wp\/v2\/tags?post=1551"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}