mendixlabs / customstring

This widget adds a string to your page, taking a microflow as datasource.

CustomString

This widget adds a string to your page, taking a microflow as datasource.

Contributing

For more information on contributing to this repository visit [Contributing to a GitHub repository] (https://world.mendix.com/display/howto50/Contributing+to+a+GitHub+repository)

Typical usage scenario

Display a string, composed on the fly by a microflow. Choose whether you want to place the widget in a dataview or not (CustomString (No Context)) Use this widget instead of creating an attribute solely for display purposes. Now an additional attribute to store the string has become superfluous!

Installation

Import the widget to your project. Add either the Custom String or the Custom String (No Context) to a page. Configure the properties to determine how the widget will behave in your application.

Properties

• Render as HTML - Determines if HTML elements in the generated string are escaped.
• Source microflow - A microflow generating the string to display.

customstring's Issues

Nanoflow!

This widget would be perfect nanoflow use case!

Replace mx.ui.action with mx.data.action

With the new Mendix 8.5, the CustomString widget produces a deprecated message in the console:

DEPRECATED: mx.ui.action. Use mx.data.action directly instead. -- will be removed in version: 10.0

Upgrade to 7.23.8 no constructor found

I went from 7.23.5 to 7.23.8 a few weeks ago. I am now seeing that this widget is not loading (see screenshot above). Based on some googling I have tried clearing the cache but this did not work. The other suggestion involves deleting the entire widget folder and/or extracting the .mdk file. But that seems like I could risk damaging some other parts of my project.

I'm getting this is the logs which might be related:
Loading module failed! Check console log for more detailed debug information.

Which might be referring to this:
multipleDefine Error: multipleDefine
at l (http://localhost:8081/mxclientsystem/mxui/mxui.js?637133197653209575:5:426)
at Xe (http://localhost:8081/mxclientsystem/mxui/mxui.js?637133197653209575:5:11422)
at http://localhost:8081/mxclientsystem/mxui/mxui.js?637133197653209575:5:11858
at u (http://localhost:8081/mxclientsystem/mxui/mxui.js?637133197653209575:5:339)
at Je (http://localhost:8081/mxclientsystem/mxui/mxui.js?637133197653209575:5:11836)
at r (http://localhost:8081/mxclientsystem/mxui/mxui.js?637133197653209575:5:10417)
at HTMLScriptElement. (http://localhost:8081/mxclientsystem/mxui/mxui.js?637133197653209575:5:12797)

Fix update method

Same as https://github.com/mendix/FormatString/issues/14

Nice! Can we have a version without context?

Mx 7.11 Issue

Mx 7.11 issue:

CustomString.js?636574041495279473:95

Uncaught (in promise) TypeError: Cannot read property 'indexOf' of null
at N.(anonymous function).E.checkString (http://localhost:8090/widgets/CustomString/widget/CustomString.js?636574041495279473:95:24)
at N.(anonymous function).E._processSourceMFCallback (http://localhost:8090/widgets/CustomString/widget/CustomString.js?636574041495279473:89:46)
at N.(anonymous function).E. (http://localhost:8090/mxclientsystem/mxui/mxui.js?636574041495279473:7:26309)
at http://localhost:8090/mxclientsystem/mxui/mxui.js?636574041495279473:7:1051203
at

Console shows deprecation warning

The widget generates this warning:
[Client] DEPRECATED: logger, use console.debug instead -- will be removed in version: 11.0

Mendix 7.15.1 Loading of a page has been superseded by request

In Mendix 7.15.1 I get the following error when putting the Widget on my page:

Ignoring error for page THIS010/Login.page.xml: Loading of a page has been superseded by request for THIS010/Login.page.xml

Remove deprecated methods

Remove mendix.lang.nullExec from the context version of the widget

Widget does not render in Mx 6.2.0 when Render as HTML is set to No

In Mendix version 6.2.0, if the defaul property Render value as HTML is left as No, the widget does not render on the page. If the property is set to Yes, the widget renders correctly