Home › Forums › Weaver Xtreme Theme › WordPress 7.0
- This topic has 8 replies, 3 voices, and was last updated 3 months, 3 weeks ago by
GR8FL.
-
AuthorPosts
-
May 22, 2026 at 21:05 UTC - Views: 53 #76934
GR8FL
ParticipantI’m testing WordPress 7.0 on a sandbox copy of my site before updating production, and I’m seeing some visual/usability issues in the Weaver Xtreme Admin screens.
The front-end settings appear to be intact, but the Weaver admin interface is rendering differently under WordPress 7.0. The clearest example is in the Wrapper Area settings: the Theme Width value is still 1100px, but the input field is now so narrow that it only visibly shows “110.” The same screen on my production site, before the WordPress 7.0 update, displays the full value normally.
I’m seeing similar changes across other Weaver Xtreme Admin tabs as well. Dropdowns, input fields, color fields, checkboxes, and textareas all appear larger or more widely spaced than they do under the current production version. The screens are still mostly usable, but they are noticeably bulkier, harder to scan, and in at least some cases the fields no longer display their values cleanly.
It looks as though WordPress 7.0 may have changed admin form-control sizing, spacing, or padding, and the Weaver Xtreme options panels may need some compatibility adjustments. Could you take a look at whether the Weaver admin screens need updated styling for WordPress 7.0, especially around input widths, dropdowns, color fields, textareas, and overall field spacing?
I can provide screenshots comparing the sandbox and production versions if helpful.
I’m also finding the overall WordPress 7.0 admin color changes visually jarring. The brighter blue/purple highlights and pale tinted rows make the dashboard feel harsher and less readable to me than the previous admin styling. That may be more of a WordPress core/admin design issue than a Weaver issue, but I wanted to mention it because the combined effect makes the admin area feel much less comfortable to work in.
For context, I use the Classic Editor setup or Disable Gutenberg. I do not use the block editor or site editor on this site, so my main concern is how WordPress 7.0 affects the traditional admin screens and the Weaver Xtreme options panels.
May 23, 2026 at 03:22 UTC - Views: 56 #76935User
ModeratorYes, it seems the WP 7.0 has impacted the Weaver Xtreme default visual settings of the box sizes etc.
The ‘1100’ px data is still there, though it only shows ‘110’ due to the narrower box (probably defauly paddings have changed). If you click on the numbers and move to the right, the whole ‘1100’ is fully displayed.
Also the boxes have increased noticeably in height, so the Xtreme Admin pages are now a tad longer…
I also noticed that the white text and icons in the WP 7.0 Admin bar is now pure white and really contrasts with the black, much more than in the past – kinda garish now as your mentioned.
FYI, the only ‘change’ I am finding after the WP 7.0 update is in the edit process.
Occasionally, when I click ‘Save Draft’, it will return blank textareas in both the Visual and Code tabs. However, there are signs that something is there, but all is white and extends down the whole length of the contents. Refreshing/ reloading the pages solved this issue and nothing was missing, so I guess it is only a glitch in the rendering. This happens on about 30% of initial saves.
I also use Classic editors and totally non-block.
@Weaver FYI:On my WordPress.com site, I now get this notice when I log in to edit my ‘classic’ posts:
“The Classic block is being phased out. Convert this content to blocks for the best editing experience, or move it to a Custom HTML block to preserve the markup as-is.”
Regards!
May 23, 2026 at 13:57 UTC - Views: 45 #76936GR8FL
ParticipantThank you — that confirms what I’m seeing as well.
Just to clarify, my site is self-hosted WordPress.org, not WordPress.com. I use the Classic Editor setup with the Disable Gutenberg plugin and do not use the block editor/site editor on this site.
My main question is whether Weaver Xtreme will be making any admin CSS compatibility adjustments for WordPress 7.0. The issue is not that the values are lost; I understand the 1100px value is still there. The problem is that the Weaver Xtreme Admin interface is now harder to use because the fields, dropdowns, checkboxes, color controls, and textareas are rendering larger/taller, and in some cases values are clipped or not fully visible.
Since this appears across multiple Weaver Xtreme Admin tabs, I’m trying to determine whether this is something Weaver can accommodate in an update, or whether users should simply expect the Weaver admin screens to be bulkier and less readable under WordPress 7.0.
For now, I’m not updating production until I understand whether this will be addressed.
May 23, 2026 at 15:42 UTC - Views: 35 #76937User
ModeratorLast week after the Plus 7.0 update I asked if Weaver Xtreme will be updated soon and got the reply: “This is not a short term goal – maybe by end of the summer.”
Given that the WP 7 issues are mainly visual and for Admin, I would doubt if they will make a Weaver Xtreme update any more urgent, especially given the Accessibility and other issues which must also be addressed too.
I think just need to wait and see what Weaver’s deliberations conclude, as I believe there are a whole lot of serious issues involved here.
May 23, 2026 at 15:49 UTC - Views: 33 #76938GR8FL
ParticipantThanks — that helps. I wasn’t asking for or expecting an immediate fix. I mainly wanted to confirm whether the WordPress 7.0 admin display changes were known and whether @Weaver was aware that they affect the Xtreme Admin screens.
For now, I’ll continue testing only on the sandbox and will hold off on updating production until there’s more clarity about Weaver Xtreme compatibility and any possible admin CSS adjustments.
May 23, 2026 at 16:50 UTC - Views: 29 #76939Weaver
KeymasterWell, I hadn’t noticed the changes myself – been running under WP 7 beta for quite a long time – couple of months at least. The value up/down boxes are now too narrow for larger values – missed that. That will likely be a small tweak. And perhaps the boxes are now too tall adding to the over length of options. I do now notice that some of the titles/labels are wrapping to 2 lines, so perhaps the default font sizes have changed.
I’ll try to fix those – messing with the Customizer UI should not be something done like that. WP does know that there are likely millions of sites still using legacy interfaces – Classic Editor, Classic or even Customizer settings.
I will also make a new post soon about a very interesting (and exciting!) thing I’ve learned about LLM Ais, how WP is planning to use them, how that may not be the best approach, while in fact Weaver Xtreme might actually be a much better way to use an AI. That is where I’ve been focused for the past few weeks.
But I’ll at least chedk out the now too narrow value boxed. I will also post a Weaver Xtreme 7,0 download as soon as I get that fixed for testing. I’ve been using it for some time, but now WP is insisting that themes update to specify WP 7.0 compatibility soon, so there will be an official version soon, as well.
May 23, 2026 at 18:42 UTC - Views: 27 #76943Weaver
KeymasterNot the best of news: WP 7.0 has changed handling of the Customizer, apparently.
It seems they made the whole customizer wider, by default. This has also increased the font size, which I’m guessing why the value setter boxes overflow the font.
There are apparently some non-trivial fixes which I will look into. Not a fast fix, I suspect.
Looks like this new “choice” has affected every single classic theme that uses the customizer. Larger fonts, wider column. But I suspect there will be some override CSS fixes to find. Grumble…
May 23, 2026 at 19:33 UTC - Views: 18 #76944Weaver
KeymasterLooks as if styling the Customizer is NOT trivial. There are methods, but not easy. I suspect someone may write a plugin to fix this stupid decision. They probably worked very hard originally to set the Customizer width, and for some unknown reason changed it without regard the legacy users.
So, I guess we wait for a plugin solution.
May 23, 2026 at 19:52 UTC - Views: 16 #76945 -
AuthorPosts
- You must be logged in to reply to this topic.

