Google Calendar

sdetweil

@louise and any messages from where u start mm?

npm start or pm2

if pm2 the pm2 logs --lines=50

sdetweil

@louise said in Google Calendar:

I suppose I should of that of the privacy thing.

i edited the cal url in both posts

sdetweil

@louise also you were missing a close brace after the url definition, which needs quotes

the config.js rules

the thing to the left of : does not need quotes
the thing to the RIGHT of : does NOT need quotes IF it is trye or false, or a number 10, 123.4567… or { or [
otherwise if the thing to the right of contains letter (http://… fred, 124somefile) then it must be enclosed in quotes,
single of double doesn’t matter, long as both ends are the same

louise

@sdetweil pm2
I copied the sample calendar module, it works. Then the ONLY thing I changed is the google link, didn’t touch any of the brackets or commas or quotations etc. Still didn’t work. Don’t get it, it worked yesterday.

The weather current and forecast work as does the clock, just not the calendar.

Yesterday, the clock and weather didn’t work but the calendar did. I copied from my calendar bak file in the config.js file and it doesn’t work.

sdetweil

@louise what does “doesn’t” work mean

cal shows no events?
or MM shows black screen?

also, still waiting for the messages from npm start time
you should see something like this (your url of course)

 Create new calendarfetcher for url: http://www.calendarlabs.com/ical-calendar/ics/76/US_Holidays.ics - Interval: 300000

and

Calendar-Fetcher: Broadcasting 10 events.

louise

@sdetweil
No events showed up. npm start time is the same as it was. No I never saw the message, but I was wasn’t looking.

With the US Holidays, that comes up. When I put in the google calendar info I get the npm run config:check which says the json can’t parse

sdetweil

@louise show the messages,.,

npm start >somefile.txt
wait til no events
ctrl-c

then u can edit somefile.txt to look at the messages emitted by startup

search for ‘fetcher’

sdetweil

@louise
and did you put the quotes around it as i mentioned before, and be careful, the default line has }
way out at the end… don’t delete that…

the npm run will tell you the line where it detect the problem, but the line that CAUSED the problem is usually the line before

on your prior post of the config, I noticed a missing } as well as the quotes around the URL…

see your prior post, which I edited

louise

@sdetweil Yes, I made sure the quotes were there. Also, like I said I was VERY careful not to mess with anything outside the quotes.

Not sure on the pm start >somefile.txt
wait til no events
ctrl-c

is it pm start>somefile.txt in the terminal window?

sdetweil

@louise yes, everything is in the terminal window

all commands are in the terminal window

again, copy paste the { to } of the calendar module config from the failing config.js and the error message from the cconfig:check
(and junk up the actual url text so its not valid)