Calendar import from google calendar

Documentation
1

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).

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

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

2

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 which discusses importing calendar data. The “calendar data” it’s referring to is the data created with the original “Calendar add-on” which was later folded into the core.

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. You might get some ideas from that.

1 Like