@sdetweil I am using the default setup that comes with a clean install of MM. That is, NY Times.

So I can go back and forth between “localhost” and “0.0.0.0” and see the immediate difference. Seems odd that it would be affected, but clearly is so.

This problem is caused by changing a single line in config.js:

address: "localhost",

to

address: "0.0.0.0",

Full articles are sometimes displayed, and sometimes not. When set to “localhost” the full articles are always displayed. I replicated this several times with a completely fresh install of MM.

@sdetweil My dumb error which I corrected. Sorry to bother you.

@bhepler Yes, the trailing comma is present. The config.js file is syntactically correct, it just produces unexpected results. In this case a string instead of an array.

How does one declare an array in config.js within the config object? Just using [] does not work. For instance, declaring the following within a module’s config object:

biff: ['muffy','sport','spam']

does NOT create an array. Instead, what is created is the comma separated string: “muffy,sport,spam”.

I see the iframe get created with a z-index=1, but it is not displayed. I the Detweiler script and the only thing reported changed, besides the couple json files, is the config.js in order to add the touch module and comment virtually all the other modules.

I could set up again from scratch to see if the issue disappears, but if there really is some bug, it gets hidden for someone later to stumble upon.

Sorry, posted it a second time because I did not see the original post show up for some reason.

Installed the current release v2.11.0 plus MM-Touch module.
Added some newsfeed-specific gestures to see more details.
Worked fine, as the brief description was first displayed, then the full article version.
Tried it today and full article no longer works. The more details part shows correctly when ARTICLE_MORE_DETAILS is sent, but the second time the notification is sent the article title and brief description disappear from the bottom bar, then very briefly flash at the top of the display, then disappears. Touch gestures do not work anywhere except the left side, which would normally be left open by the full article display. It is as if the full article is hidden behind. Since TAP_! is set to restore the normal newsfeed display, tapping on that left side resumes normal display.

Any ideas for a newbie?

First time user.

Used the detweiler script to install the latest version of MM (v2.11.0) on a fresh installation of Raspian (NOOBS v3.2.1). Ran “npm run config:check” which reports that eslint is missing. Running “npm install eslint” fixes this issue.

Is this a MM issue or Detweiler script issue?

First time user.

Used the detweiler script to install the latest version of MM (v2.11.0) on a fresh installation of Raspian (NOOBS v3.2.1). Ran “npm run config:check” which reports that eslint is missing. Running “npm install eslint” fixes this issue.

Is this a MM issue or Detweiler script issue?