Read the statement by Michael Teeuw here.
London Bus status
-
@strawberry-3.141 If I get the chance I’ll look at passing an identity to the helper so it knows where to route the response back to.
-
Hm. I tried that. I copied the module and contents to modulename2, changed the .js to 2.js - edited the 2.js to (module.register) to modulename2 .
Then I changed my config file - copied the first module to another instance and changed its name to modulename2. (then i changed the atcocode for a new bus stop). --It’s stuck on loading bus info…
-
@soqueen I’ve just pushed a new version that hopefully allows you to have multiple instances of the module running. It’s been working happily this afternoon running three different bus stops around the area with no complaints.
You’ll need to do a git pull to update, then run the
cd MMM-UKLiveBusStopInfo npm install
to install the new dependencies.
Give it a try and let me know. If it goes pear-shaped I can always roll the old version back and look again later.
-
It works! Thank you SO VERY much! I really appreciate it! Thank you!
-
HI there! One of the newest updates took off the heading for my multiple instances. It only puts a header on the first one. I tried adding a header in the config.js file but it ignors it. Help please?
-
@soqueen mmm weird, didn’t do that for me in testing. I’ll have a look later when I get home.
-
updated and now even the first one is missing. :)
-
@soqueen I’ve just hacked a fix together. Give it a try and let me know.
-
@soqueen I’ve just noticed some weird behaviour this end while trying to fix this. Did you update your Mirror to 2.1.1? If so did you then do a new
npm install
afterwards?I ask because on one box the departures now shows no header at all, while the other now shows both departures AND the bus stop name…
-
I re-ran the npm install just in case I hadn’t done it before, and then pulled your update. Now the headers are back! Thanks!