Skip to content

Reference Error Codes

James K edited this page Apr 19, 2022 · 17 revisions

General Configuration

170001 - Invalid or incomplete API Settings

The connection to TouchPoint can't be made because the plugin has not been fully configured in WordPress. This is probably because a username or password haven't been set for connecting to TouchPoint. The WordPress admin will need to go to the WordPress dashboard, then Settings > TouchPoint-WP to configure the settings.

170002 - Host appears to be missing from TouchPoint-WP configuration.

The connection to TouchPoint can't be made because the plugin has not been fully configured in WordPress. This is probably because the TouchPoint hostname (e.g. mychurch.tpsdb.com) hasn't been configured. The WordPress admin will need to go to the WordPress dashboard, then Settings > TouchPoint-WP to configure the settings.

170003 - Cleanup Error

One of the background processes that cleans up stale data encountered an issue. The specific issue will depend on the message.

Geolocation Services

178001 - IP Geolocation Error

An error was reported by the IP geolocation service. The error and its conditions may vary by situation.

178002 - Geolocation error

An error was reported by a geolocation service. The error and its conditions may vary by situation.

178003 - Geolocation Data Not Provided

The services could not geolocate the user. This is noteworthy because of where the failure occurred in the process.

178004 - Geolocation Object is Invalid

The geolocation services returned an invalid response.

TouchPoint API

179001 - Script Error

Something went wrong with TouchPoint's execution of the API script. This is consistently a TouchPoint server problem and should be reported to TouchPoint support.

179002 - Script Error

Something went wrong in calling the API. This should be reported to the TouchPoint-WP developers.

179003 - Script Error

Something went wrong in calling the API. This is most likely from data changing unexpectedly within TouchPoint.

179004 - People Query Failed

A Person query in the API failed.

Clone this wiki locally