Full Calendar tab is blank in every version after the 0.8

[pat-div-kb]

Please check that this issue hasn't been reported before.

• I searched previous Bug Reports and didn't find any similar reports.

Expected Behavior

Visualize and use the Full Calendar tab

Current behaviour

The Full Calendar tab is blank. I realized that the problem occurs in all the versions that follows the 0.8

JavaScript console output

This comes in the last version installed:

Steps to reproduce

Lunching Obsidian Full Calendar

Calendar information

I have 4 remote Google Calendar and 1 local calendar. Everything works in the version 0.8.0

Which Operating Systems are you using?

• macOS
• Windows
• Linux
• Android
• iOS

Obsidian Version

1.3.5 (and some previous one... I have this problems since few months)

Full Calendar Plugin Version

all the versions that follows the 0.8

Checks

• I have tried it with all other plugins disabled and the error still occurs.

Possible solution

Downgrading to the version 0.8.0

Comments

No response

[alexbevi]

Confirmed on Windows as well

[Grant837]

I am not sure this is the same problem, but I have one (secondary) Windows PC that suddenly does not show any of my full note events... on my android, ipad, and another windows PC, all is OK. I use Sync, so replication should not be the problem, should it?

[pat-div-kb]

I am not sure this is the same problem, but I have one (secondary) Windows PC that suddenly does not show any of my full note events... on my android, ipad, and another windows PC, all is OK. I use Sync, so replication should not be the problem, should it?

As long as I can tell I would say the problem is the same. I confirm that also in my case Full Calendar works properly in the Android app.

[inefg]

关闭所有插件，依次启动 Full Calendar 和其它插件，确保先启动 Full Calendar 。之后就能加载出来的了

[Phil-T1]

Same for me in android, entirely blank after successfully linking five Google calendars.

Thanks,

Phil.

[berlincount]

This bug actually seems to actually be #233 ...

[pat-div-kb]

This bug actually seems to actually be #233 ...

Yes, I can confirm... I solved the problem removing the plugin "Itinerary"! However now I got the issue #481