Hi Hartley,
You’ve already ruled out the usual causes (App ID, visibility, module role). Since the widget shows in Design mode but not at runtime, the problem is most likely on the client side. Check these in order:
Check the browser console first. Open the app, press F12, go to Console, and reload. A JavaScript or Content Security Policy error from the Feedback widget usually points straight to the cause.
Remove the old widget package. After an upgrade, the old file can stay in your app’s /widgets folder and conflict with the new one. Look for SprintrFeedbackWidget.mpk, delete it, and keep only the v5 package. Then right-click the widget in Studio Pro → Update all widgets, and run App → Clean deployment directory before running again.
Check the Target container selector. The side tab attaches to the element set in the widget’s advanced settings, which defaults to .mx-scrollcontainer-center. If your layout doesn’t contain that class, the tab has nowhere to render. This is common with custom layouts or after an Atlas update. Open Configuration → Show advanced settings = Yes and set the selector to a container that exists in your layout. You can find one with the browser’s element inspector.
Update Atlas Core. The side tab’s styling comes from Atlas Core. If Atlas Core is outdated, the tab can end up hidden behind other content or positioned off-screen.
Check the Content Security Policy. If your environment sets a CSP header, make sure it doesn’t block the widget’s scripts or images, for example img-src 'self' data: blob:.
A quick way to narrow it down: temporarily set Feedback Button Styling to Button instead of Side tab and place the widget directly on a page.
If the button appears, the problem is the side tab’s container or styling (steps 3 and 4).
If it doesn’t appear, look at the widget package or the console errors (steps 1 and 2).
Hope this helps! If this solution works for you, kindly mark it as the accepted answer so it can help others facing the same issue.
Hi Hartley,
One additional thing to check is whether the Feedback widget is actually loading but being hidden by custom styling.
After upgrading to v5.0.0, inspect the page using your browser's developer tools (F12) and look for the Feedback widget elements in the DOM. I've seen cases where:
Custom theme CSS overrides the widget's z-index and places it behind other page elements.
A fixed sidebar, navigation menu, or floating action button overlaps the Feedback side tab.
Custom styling on containers uses overflow: hidden, preventing the side tab from being displayed.
As a quick test:
Open a simple page with the Feedback widget as the only custom component.
Temporarily switch the render mode from Side tab to Button.
Disable any custom theme changes introduced recently.
Check whether the widget appears in a newly created responsive page using the default Atlas layout.
If it works on a clean page but not on your existing layout, the issue is likely related to layout CSS rather than the widget configuration itself.
Hope this helps!
Hi Hartley,
Since the Feedback widget stopped appearing immediately after upgrading to version 5.0.0, I would first check the module compatibility and widget initialization rather than the App ID or user permissions, which you have already verified.
1. Verify Studio Pro compatibility
Feedback Module 5.0.0 requires Mendix Studio Pro 10.24.0 or later.
If your application uses an earlier Studio Pro version, use a compatible Feedback Module version or upgrade Studio Pro.
2. Check the React Client configuration
If your application uses the React Client, Mendix documents the following configuration:
Install the compatible Mendix Feedback Module.
Add or replace the Feedback widget in your main layout with FeedbackModule.FeedbackWidget.
Open the widget properties inside the snippet.
Set Modal pop-up type to Custom.
Configure On click to Show a page.
Select FeedbackModule.ShareFeedback.
Also ensure that the layout containing this snippet is actually used by the affected pages.
3. Verify the target container selector
In the widget properties, enable Show advanced settings.
Check the Target container selector.
The default is:
.mx-scrollcontainer-centerThe Feedback widget uses this selector to determine where its button is rendered.
If your application uses a customized layout, inspect the browser DOM and verify that this element exists. If it does not, configure the selector to target an appropriate existing container in your layout.
This is particularly relevant when using the Side Tab rendering mode.
4. Test Button rendering mode
Temporarily change Feedback Button Styling from Side Tab to Button.
If the button appears in its normal page position, the problem is likely related to the Side Tab placement or target container rather than the entire widget failing to initialize.
5. Check the browser console
Open Developer Tools and inspect the Console for JavaScript errors when the page loads.
Also check whether the Feedback widget is present in the DOM but hidden by CSS or whether it is not being rendered at all.
6. Re-add the widget in a test branch
If the configuration is correct, remove and re-add the Feedback widget to the affected layout or snippet in a separate branch.
Mendix has previously documented widget re-adding as necessary for certain Feedback Module upgrades, although this is not listed as a specific requirement for version 5.0.0.
My recommendation:
First confirm the Studio Pro version and React Client configuration. Then test Button rendering mode and verify the target container selector.
These checks should help distinguish a widget compatibility problem from a Side Tab rendering issue.
Official references:
Hope this helps! If you find this answer helpful, please mark it as the accepted answer.
Hello,
Follow the below steps to show the Feedback button :
For Windows users, find the Feedback widget in the Structure mode. For Mac users (who do not have the Structure mode), go to the Page Explorer and find the Feedback widget.
Double-click the widget to open the Edit Feedback dialog box.
Go to the Customize button tab.
Set Show in Design mode to Yes.
Click OK to save the change.