Read the statement by Michael Teeuw here.
MagicMirror regions
-
@DanClarkCBET3 only thing you can do is edit the source at
~/MagicMirror/js/utils.js
// return all available module positions getAvailableModulePositions () { return ["top_bar", "top_left", "top_center", "top_right", "upper_third", "middle_center", "lower_third", "bottom_left", "bottom_center", "bottom_right", "bottom_bar> },
note that because you are editing our file, this will block updates
-
@sdetweil thanks for the help. That cleared the error but my modules are still not being displayed.
-
@DanClarkCBET3 i would use the developers window to examine the dom. see if your elements have the right classes on them.
you rechanged index.html, right?
-
there were more changes in the corresponding PR, see https://github.com/MagicMirrorOrg/MagicMirror/pull/3445/files
-
@karsten13 main should call utils to get the list. I thought it was a requested charge in the pr.
actually the code should read index.html to get them. so users dont have to edit our code. I know it’s an edge case…
-
@sdetweil Thanks everyone. It is working perfectly now.
-
@DanClarkCBET3 for the next release I have submitted a pull request to detect the regions used in index.html instead of hard coded…