Here’s what Grok had to say about it. Maybe there is a nugget in there. The problem with Grok and other AIs is that they speak like experts, but aren’t. So huge grain of salt. But it’s more than I could have given you.
Grok: It’s a classic v10 upgrade symptom tied directly to the big Kendo UI library update in Aware IM v10 (the same change that prompted the “best release since moving to Kendo in V8” comments on the official forum).
Your symptoms (left panel completely missing in DOM/inspector, right panel dropping below instead of side-by-side, works fine in v8/v9, new VP from scratch behaves the same, Bootstrap-3 CSS suspected) are almost exactly what other users hit when their old themes/custom CSS (especially Blue Opal) clash with the newer Kendo renderer.
Root Cause
v10 ships a newer Kendo version.
Older themes like Blue Opal (and any Bootstrap-3 references they carry) no longer play nicely with the new Kendo grid/panel rendering.
The VP grid (your left_form size 6 + right panel size 6) relies on Bootstrap/Kendo column classes that now render differently (or get overridden/hidden).
The left panel HTML isn’t even generated (or is hidden at CSS level), which is why Chrome inspector shows “nothing from Aware”.
Bootstrap-3 isn’t “forced” by v10 itself — it’s coming from your copied v9 Blue Opal files or custom CSS.
Immediate Fixes (in Order of Speed)
Switch to a stock v10 theme first (do this before anything else)
In the Config Tool → Presentation → Themes (or wherever you select the app theme), drop Blue Opal and pick the default v10 theme (or “Classic Silver” as a close alternative).
Restart the server and test the VP cold.
Most people find the side-by-side layout instantly returns because the new Kendo theme doesn’t pull in the old Bootstrap-3 baggage.
Restore the old Blue Opal theme properly (if you really want to keep the look)
The forum has an exact method that works in v10:
Go to: https://kendo.cdn.telerik.com/2020.3.1021/styles/kendo.blueopal.min.css
Copy the entire content.
Paste it into a new file here:
C:\AwareIM\Tomcat\webapps\AwareIM\aware_kendo\resources\css\aware_classic-opal.css (create the file if missing).
Restart server.
This bypasses the broken v9 copy you brought over and loads the compatible legacy Kendo style.
Add targeted custom CSS overrides (the official v10 way)
Create this exact folder (it is auto-loaded by Aware IM):
C:\AwareIM\Tomcat\webapps\AwareIM\Custom\CSS[YourAppName]
Inside it, make custom.css (or add to your existing one) with something like:CSS/* Force the VP grid to behave like old Bootstrap/Kendo /
.k-panel, .row, .form-horizontal {
display: flex !important;
flex-wrap: wrap !important;
}
.col-md-6, [class=“size-6”], .left_form, .panel {
flex: 0 0 50% !important;
max-width: 50% !important;
}
/* Restore left panel visibility if it’s being hidden */
fieldset, .k-fieldset, .group-box {
border: 1px solid #ccc !important;
padding: 10px !important;
display: block !important;
visibility: visible !important;
}This is the exact pattern users are using in v10 for group-box/panel rendering fixes (see the forum thread “Fixing Group Box rendering in V10 Kendo library”).
Kill the unwanted Bootstrap-3 once and for all
Open your old Blue Opal CSS files (in the Custom folder or aware_kendo) and search for bootstrap-3.
Comment out or delete the @import or <link> for bootstrap-3.min.css.
Or simply delete any old bootstrap-3 files you copied over — v10 doesn’t need them.
After changes, clear browser cache + restart Aware IM server.
Quick diagnostic steps while testing
Open the VP in Chrome → Dev Tools → Elements tab and search for your left_form panel name or “size-6”. If the <div> isn’t there at all, the process/query that populates the left panel is failing silently in v10 (check process logs).
Console tab: look for Kendo or Bootstrap errors on load.
Try the VP with zero queries first (just empty panels) to isolate whether it’s data-related or pure layout.
Extra Tips
Restart the Aware IM server after every CSS/theme change — it’s required for the Custom folder to pick up.
If you have “Execute JavaScript” in the VP, you can force a layout refresh with a tiny snippet after the queries run (some users do this as a band-aid).
The same Custom\CSS[AppName] trick also fixes the group-box border issues that lots of v10 upgraders are hitting.
This should get your main data screen back to side-by-side with the left panel showing, just like in v8/v9. The v10 Kendo update is the culprit, but the custom CSS folder + legacy theme restore (or stock theme) is the official workaround the community is using.
If you try steps 1–3 and still get stuck, drop the exact classes you see in Chrome inspector for the panels (or a screenshot of the DOM) and I can give you more precise CSS. Also check the threads “Fixing Group Box rendering in V10 Kendo library” and “Can I use a legacy Kendo style?” on the Aware IM forum — they’re basically the same problem you’re describing.
END Grok
