Read the statement by Michael Teeuw here.
Google Calendar
-
@louise show the messages,.,
npm start >somefile.txt
wait til no events
ctrl-cthen u can edit somefile.txt to look at the messages emitted by startup
search for ‘fetcher’
-
@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
-
@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-cis it pm start>somefile.txt in the terminal window?
-
@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) -
Maybe it could be another reason;
Confirm whether your calendar is public
Unless you check this, your ical URL won’t be accessed. Try your URL in the browser. If it shows 404 error, this might be the reason. -
@mmrize Yes it is public. It does seem to work now.