Discussions
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Don’t miss your chance to meet our SuiteGurus—NetSuite Support professionals and subject matter experts with extensive experience in select product areas, including OneWorld, Advanced & Basic Accounting, Supply Chain Management, Receivables & Payables, CRM, Account Administration, and the SuiteCloud Platform. Full Conference attendees can prebook exclusive 30-minute one-on-one sessions for your product questions.
Spots are limited! Register through your Agenda Builder and find SuiteGuru under Agenda Enhancements.
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.