Perhaps this is an unusual use case, but trying to edit pre-existing tokens that had worked (somewhat) in the previous version, after clicking edit, I get:

Warning: date_timezone_set() expects parameter 1 to be DateTime, boolean given in format_date() (line 2062 of /srv/bindings/8dbba19192124a1c8ddcdfff90761e4b/code/includes/common.inc).
Warning: date_format() expects parameter 1 to be DateTimeInterface, boolean given in format_date() (line 2072 of /srv/bindings/8dbba19192124a1c8ddcdfff90761e4b/code/includes/common.inc).
Warning: date_timezone_set() expects parameter 1 to be DateTime, boolean given in format_date() (line 2062 of /srv/bindings/8dbba19192124a1c8ddcdfff90761e4b/code/includes/common.inc).
Warning: date_format() expects parameter 1 to be DateTimeInterface, boolean given in format_date() (line 2072 of /srv/bindings/8dbba19192124a1c8ddcdfff90761e4b/code/includes/common.inc).
Warning: array_flip(): Can only flip STRING and INTEGER values! in EntityAPIControllerExportable->load() (line 742 of /srv/bindings/8dbba19192124a1c8ddcdfff90761e4b/code/sites/all/modules/entity/includes/entity.controller.inc).
Warning: array_flip(): Can only flip STRING and INTEGER values! in EntityAPIControllerExportable->cacheGetByName() (line 787 of /srv/bindings/8dbba19192124a1c8ddcdfff90761e4b/code/sites/all/modules/entity/includes/entity.controller.inc).
Warning: array_flip(): Can only flip STRING and INTEGER values! in EntityAPIController->load() (line 219 of /srv/bindings/8dbba19192124a1c8ddcdfff90761e4b/code/sites/all/modules/entity/includes/entity.controller.inc).
Warning: array_flip(): Can only flip STRING and INTEGER values! in EntityAPIControllerExportable->cacheGet() (line 773 of /srv/bindings/8dbba19192124a1c8ddcdfff90761e4b/code/sites/all/modules/entity/includes/entity.controller.inc).

After adding the user to the token and clicking update, the date-timezone errors go away, but I still see the array_flip errors.

Thanks.

Comments

jsibley created an issue. See original summary.

thedut’s picture

Status: Active » Closed (cannot reproduce)

Hello,

Yes, you meet this errors because you have upgraded from limesurvey v7.x-2.x to v7.x-3.x
Just install the v7.x-3.x on a new install.