Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
NetSuite has launched SuiteSuccess Wholesale Distribution Edition, in Japan. Please join us the webinar on February 12 that introduces NetSuite solution with demos and case studies for Wholesale Industry.
Register Now
Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.
order of <head> add-ons
Is it just me? Or does anyone else think it's ass-backwards to have a template's "add to <head>" block come first, before the theme's "add to <head>" block when the page is rendered?
I mean... really?
If I want to override a site-wide CSS rule in a particular class of pages, I don't see a way to do it, except by putting the <link> or <style> element in the <body>, which violates the HTML spec.
If I want to include, say, the jQuery lib and use it in a particular way on a particular class of pages, I have to include jQuery in the template. I can put <script> elements in the <body>, I suppose, and in that way keep the jQuery include in the theme's <head>. But that's just kind of messy.