Cambabutonono
Forum Replies Created
-
Yes, this is exactly what I mean – my theme is not loading any extra styles for dropdowns on front-end, like in your example that you posted earlier (however it does in the block editor just fine). Ive tested that on both chrome and safari. Thanks for looking into it.
Hi @fcoveram Thanks for your response. I have attached the screenshot in my original post. So I don’t seem to have the same layout of the dropdown on the front-end as you are showing—just the default browser style for dropdowns. Strange. Perhaps it’s something on my end, since your site is working fine. I have some customizations in my child theme and also Jetpack forms enabled. Not sure why that would break the styles, but…
Forum: Themes and Templates
In reply to: [Twenty Twenty-Five] Reverting Font Changes in Typography PanelThanks for heads-up @poena !
- This reply was modified 1 year, 6 months ago by Cambabutonono.
Forum: Themes and Templates
In reply to: [Twenty Twenty-Five] Reverting Font Changes in Typography PanelCorrection – Seems I’m able to revert fonts in 2024 theme to defaults, but not in 2025. Is 2025 still in beta?
Hi, The below snipped works fine for main menu so far but I haven’t finished the project so not sure what still awats… 😉
// SCSS // adjust the mobile menu breakpoint $breakpoint--global-header: 1300px; @media (max-width: $breakpoint--global-header) { .wp-block-navigation__responsive-container-open:not(.always-shown) { display: flex !important; } .wp-block-navigation__responsive-container:not(.hidden-by-default):not(.is-menu-open) { display: none !important; } } @media (min-width: $breakpoint--global-header) { .wp-block-navigation__responsive-container-open:not(.always-shown) { display: none !important; } .wp-block-navigation__responsive-container:not(.hidden-by-default):not(.is-menu-open) { display: block !important; width: 100%; position: relative; z-index: auto; background-color: inherit; } }Forum: Plugins
In reply to: [WordPress Slider Block Gutenslider] Navigation dots have some strange areaThanks for sorting that out @eedee !
The link to the workaround posted by @doctorrockter worked in my case! Many thanks!
(delete_transient_wp_core_block_css_filesin thewp_optionstable.)Ok, I just create a new post in there and copy-paste Ig 🙂 not sure how to delete it from here tho.
Thanks for your response @macmanx Would you be able to provide an advice on how do I report it there? The topic appears to be closed for replies… cheers!
Forum: Fixing WordPress
In reply to: Remove SVG FIlterThat workaround works! Removes both default inline css and the filters from the footer.
Not sure why all that garbage is included by default anyway, should be added by a theme imho.
I had a similar problem. Hummingbird adds a HTML comment at the beginning of document which I think causes the problems in e. g. Google Console.
For Yoast SEO plugin’s sitemaps I’ve added 2 entries
In Caching > Exclusions > Url strings\/sitemap_index.xml
\/*sitemap.xmlnote the escaped slash at the beginning of each string
Seems to resolve the problem.
Forum: Plugins
In reply to: [Page Builder by SiteOrigin] How to revert to classic editorAfter posting that I’ve downloaded the plugins and realised that this is more complex, so probably the classic editor plugin is the best bet.
- This reply was modified 7 years, 5 months ago by Cambabutonono. Reason: corrected grammar, expanded the post
- This reply was modified 7 years, 5 months ago by Cambabutonono.
- This reply was modified 7 years, 5 months ago by Cambabutonono. Reason: reconsidered the options
Forum: Plugins
In reply to: [Page Builder by SiteOrigin] How to revert to classic editorHi there.
I’m very happy that the WordPress page & post edit screens are getting a new look however the website I am working on utilises a heavily modified classic editor that have been developed over many years. I simply don’t have enough dev power to change all the additional functionality to support a new editor therefore are forced to stick to the WordPress 4.x I guess.
I’ve noticed that the ‘classic’ editor is still used on all custom post types anyway, so I was wondering if there is a trick to bring it back to the post & page editing screens with a simple switch, without any additional plugins.
Many thanks