# Calendar import from google calendar
**URL:** https://forums.concretecms.org/t/calendar-import-from-google-calendar/8030
**Category:** Documentation
**Created:** [August 29, 2024, 11:38am UTC](https://forums.concretecms.org/t/calendar-import-from-google-calendar/8030 "2024-08-29T11:38:47Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@simonchilton](https://forums.concretecms.org/u/simonchilton)
#### Post date: [August 29, 2024, 11:38am UTC](https://forums.concretecms.org/t/calendar-import-from-google-calendar/8030/1 "2024-08-29T11:38:47Z")
The documentation says that there’s an option to import from google calendar ( “External Calendar Integration: Easily import events from external sources like Google Calendar.” on this page: [https://documentation.concretecms.org/9-x/user-guide/system-and-settings/calendar#heading-7](https://documentation.concretecms.org/9-x/user-guide/system-and-settings/calendar#heading-7)).
I can’t see any option to import data from google calendar - am I missing something, or are the doc’s inaccurate?
The site is v9. Env. Info below…
# Concrete Version
Core Version - 9.2.8
Version Installed - 9.2.8
Database Version - 20240122172319
# Hostname
[web116.lhr.stackcp.net](http://web116.lhr.stackcp.net)
# Environment
production
# Database Information
Version: 10.6.18-MariaDB-log
SQL Mode: NO\_AUTO\_CREATE\_USER,NO\_ENGINE\_SUBSTITUTION
Character Set: utf8mb4
Collation: utf8mb4\_unicode\_ci
# Concrete Packages
Community Store (2.6.4), ExchangeCore reCAPTCHA (1.1.1), HTML+PHP Code Block (1.0.2), Package Ptc (1.9.2), Stripe Checkout Payment Method (1.2)
# Concrete Overrides
None
# Concrete Cache Settings
Block Cache - On
Overrides Cache - On
Full Page Caching - Off
Full Page Cache Lifetime - Every 6 hours (default setting).
# Database Entities Settings
Doctrine Development Mode - Off
# Server Software
Apache
# Server API
fpm-fcgi
# PHP Version
7.4.33
# PHP Extensions
bcmath, bz2, calendar, cgi-fcgi, Core, ctype, curl, date, dba, dom, exif, FFI, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, igbinary, imagick, imap, interbase, intl, ionCube Loader, json, ldap, libxml, mbstring, msgpack, mysqli, mysqlnd, OAuth, odbc, openssl, pcntl, pcre, PDO, pdo\_dblib, PDO\_Firebird, pdo\_mysql, PDO\_ODBC, pdo\_pgsql, pdo\_sqlite, pdo\_sqlsrv, pgsql, Phar, posix, pspell, readline, redis, Reflection, session, shmop, SimpleXML, snmp, soap, sockets, sodium, SourceGuardian, SPL, sqlite3, sqlsrv, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend OPcache, zip, zlib
# PHP Settings
max\_execution\_time - 300
log\_errors\_max\_len - 1024
max\_file\_uploads - 16
max\_input\_nesting\_level - 64
max\_input\_time - 60
max\_input\_vars - 2500
memory\_limit - 512M
post\_max\_size - 128M
upload\_max\_filesize - 128M
ibase.max\_links - Unlimited
ibase.max\_persistent - Unlimited
ic24.api.max\_timeout - 7
ldap.max\_links - Unlimited
mbstring.regex\_retry\_limit - 1000000
mbstring.regex\_stack\_limit - 100000
mysqli.max\_links - Unlimited
mysqli.max\_persistent - Unlimited
odbc.max\_links - Unlimited
odbc.max\_persistent - Unlimited
pcre.backtrack\_limit - 1000000
pcre.recursion\_limit - 100000
pdo\_sqlsrv.client\_buffer\_max\_kb\_size - 10240
pgsql.max\_links - Unlimited
pgsql.max\_persistent - Unlimited
redis.pconnect.connection\_limit - 0
session.cache\_limiter - _no value_
session.gc\_maxlifetime - 7200
soap.wsdl\_cache\_limit - 5
unserialize\_max\_depth - 4096
opcache.max\_accelerated\_files - 32531
opcache.max\_file\_size - 0
opcache.max\_wasted\_percentage - 5
---
### Author:  [@Myq](https://forums.concretecms.org/u/Myq)
#### Post date: [September 10, 2024, 7:26am UTC](https://forums.concretecms.org/t/calendar-import-from-google-calendar/8030/2 "2024-09-10T07:26:52Z")
That was a mistake that crept in when rewriting the docs for v9+ (and I’ve removed it). The misunderstanding comes from the [original documentation](https://documentation.concretecms.org/user-guide/editors-reference/dashboard/system-and-maintenance/calendar/import-calendar-data) which discusses importing calendar data. The “calendar data” it’s referring to is the data created with the original “[Calendar add-on](https://web.archive.org/web/20240222172721/https://marketplace.concretecms.com/marketplace/addons/calendar1)” which was later [folded into the core](https://documentation.concretecms.org/developers/introduction/version-history/830-release-notes).
If you had originally used the add-on, you could could import that calendar data created with it into the core version of the calendar using the Import Calendar Data option.
There used to be an [add-on that worked with Google calendar XML data](https://web.archive.org/web/20240416145817/https://marketplace.concretecms.com/marketplace/addons/gcalendar-viewer/). You might get some ideas from that.