Integration for ChurchSuite (AKA CS Integration) allows you to display certain\ndata from ChurchSuite on your Wordpress website without resorting to embedding\niframes. This plugin provides shortcodes that are easy to drop into any page\nor post. Each shortcode will, behind the scenes, request data from your\nChurchSuite feed, and will display the data returned in a similar way to the\nusual ChurchSuite iframes, but natively to your website. Many aspects of the\ndisplay can be modified in your theme to make the display match your website\ntheme. The shortcodes allow you to use a range of query parameters so that you\ncan display just the data you want for each part of your website.<\/p>\n\n
For the technical among you: This shortcode works on the 'server side',\nbuilding the response which is delivered to your browser from churchsuite.<\/p>\n\n
We also provide the If you have a problem or a feature request, please send a message to the author.<\/p>\n\n Currently there is no demo site, but you can view examples on a church website:<\/p>\n\n This plugin relies on information provided by ChurchSuite using their 'embed'\nJSON feed. Details of this JSON feed can be found here:<\/p>\n\n https:\/\/github.com\/ChurchSuite\/churchsuite-api\/blob\/master\/modules\/embed.md<\/p>\n\n For the Event Cards shortcode<\/em>, place the shortcode into a page or post or\ninto a shortcode block. The shortcode will be:<\/p>\n\n where If you want events on a specific day, use the parameters For the Event List shortcode<\/em>, place the shortcode into a page or post\nor into a shortcode block. The shortcode will be:<\/p>\n\n The comments above about parameters also apply to this shortcode. By\ndefault only a maximum of 5 days events are returned, but this can be\noverridden by adding the For the Calendar shortcode<\/em> place the shortcode into a page or post or into a\nshortcode block. The shortcode will look like:<\/p>\n\n (where For the Smallgroups shortcode<\/em>, place the shortcode into a page or post or into\na shortcode block. The shortcode will be:<\/p>\n\n (where See The plugin itself is released under the GNU General Public License. A copy of\nthis license can be found at the license homepage or in the From within Wordpress - In the Wordpress Dashboard use the menu to go to\nPlugins and from there choose 'Add new plugin'. Search for 'churchsuite'\nand then look for this plugin. Select the 'install' button on the plugin\nto install it, and once installed use the 'activate' link to activate the\nplugin.<\/p><\/li>\n If you want to install from github:<\/p>\n\n Once you have used either method to install the plugin, you need to then\nadd a shortcode (see examples below) to your wordpress posts or pages where\nyou need them<\/p><\/li>\n<\/ul>\n\n\n The default behaviour when there is an error is to give no output rather\n than produce error messages all over your website. Check that you have\n supplied the correct churchname, or test it with the churchname 'cambray'\n to see if that is the problem. Check that you can actually get to your\n ChurchSuite JSON api url - try entering the following URL in a browser\n with your church name instead of You must use the shortcode You can use a shortcode parameter for showing a particular number of events:<\/p>\n\n By default the Events List only looks ahead 5 days. If your future events\n are beyond that nothing will show. So just use the days_ahead attribute:<\/p>\n\n The output is formatted via css - just override the defaults in your theme<\/p><\/dd>\n\n<\/dl>\n\n\n 2026-02-26<\/strong>\n* Refactored the Locale code to use the wordpress site locale rather than\n the server locale, and to use the wordpress admin settings for full\n date or time output. This means the time and date output should always\n be sympathetic with the Wordpress site settings. Also moved all the\n time and date string creation to a new module so it can be easily\n modified without having to update many files.\n* Version bump to 1.0.8<\/p>\n\n 2026-02-24<\/strong>\n* Added output of dates which takes account of the current Locale of the server\n* Bumped version number\n* Bumped Wordpress Compatibility testing to 6.9<\/p>\n\n 2025-09-08<\/strong>\n* Added a new attribute 'days_ahead' to cs-event-list so that you can specify\n more than the default 5 days looking ahead for events. Use like this:<\/p>\n\n 2025-09-02<\/strong>\n* Remove FontAwesome and replace with a subset of FontAwesome to reduce the\n size of the plugin. Modify the CSS to reflect this. Correct missing css\n elements to do with cancelled events.<\/p>\n\n 2025-08-26<\/strong>\n* Change to the Calendar display to use DIVs rather than responsive tables\n to be compatible with the JS version of the plugin and enable better styling<\/p>\n\n 2025-03-17<\/strong>\n* Change to the README files to make them more readable on the Wordpress\n Directory and to include install instructions suitable for the directory.<\/p>\n\n 2025-03-13<\/strong>\n* Changes to how the JSON feed is read to remove a security vulnerability. Other\n minor changes to allow for final Wordpress Directory approval.<\/p>\n\n 2025-03-03<\/strong>\n* Added Event Categories to cs_event class, and the inclusion of an event category\n class to the html output by the event calendar so that we can colour the events.\n* Added scrolling to the event description within the pop-up\n* Added an additional control on font-size of paragraph tags within the event\n description to prevent theme definitions of for paragraphs causing large text\n to be displayed within the small calendar cells, unless the user overrides this.<\/p>\n\n 2025-03-03<\/strong>\n* CSS and HTML changes to allow the dates to be better formatted in the small\n responsive calendar display\n* Minor changes to respond to two problems reported by the Wordpress plugin checker\n* Change to the main plugin name to fit with requirements for inclusion on the\n Wordpress Plugin Directory\n* Changes to the README files to reflect the version bump<\/p>\n\n 2025-02-27<\/strong>\n* Added the first of the functionality for the 2025-02-25<\/strong>\n* Changed caching to cache API responses rather than the final HTMl, for security reasons\n* Found that num_results alone causes a 8sec response time, but adding a date_end reduces\n the API response time to 1.5s regardless of the amount of events returned. So defaulted\n the cs-events-list to 5 days just to get reasonable response time. \n* Added basic i18n support\n* Changed all files to reflect 1.0.1 release status<\/p>\n\n 2025-02-20<\/strong>\n* Added caching of responses and displaying cancelled events in the event list correctly<\/p>\n\n 2025-02-18<\/strong>\n* All files changes to ensure all code was according to the Wordpress Style Guide\n* Added the Events List shortcode<\/p>\n\n 2025-02-11<\/strong>\n* Major changes to everything to code in the style required for submission to Wordpress\n - Changed to plugin scaffolding based on WPPB\n - Change from procedural code to Classes and Objects<\/p>\n\n 2025-02-04<\/strong>\n* Initial release - really only a test of what was possible<\/p>","raw_excerpt":"Integration for ChurchSuite is a plugin to enable display of data from ChurchSuite JSON feeds","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/gl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/225003","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/gl.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/gl.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=225003"}],"author":[{"embeddable":true,"href":"https:\/\/gl.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/dramb"}],"wp:attachment":[{"href":"https:\/\/gl.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=225003"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/gl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=225003"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/gl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=225003"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/gl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=225003"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/gl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=225003"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/gl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=225003"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}cs-js-integration<\/code> plugin. That plugin uses the more\nrecent v3 ChurchSuite API which does not permit such flexibility because it\nrequires you to create a ChurchSuite 'embed configuration' to pass in the\nshortcode call. It also does all the work on the 'client side' so that\nthe client browser holds the cached data and the client browser creates all\nthe html for output. That plugin use Javascript to create the response\nwhereas this plugin uses php. This server-side implementation can be faster\nfor many repeated requests, and is less speed dependent on the client\nprovision. However the client-side implementation can be faster for an\nindividual user. The cs-js-integration plugin uses Alpine.js to output the\nHTML, which means an end user could change the output by changing the HTML\nfiles without having to get into the php of the plugin. However, the\nAlpine.js code isn't straightforward and so this is likely to be of little\nadvantage. Really, it's simply 'horses for courses' - you have the choice\nof which to use!<\/p>\n\nSupport<\/h3>\n\n
Demo<\/h3>\n\n
\n
Contributions<\/h3>\n\n
Usage<\/h3>\n\n
\n
[cs-event-cards church_name=\"mychurch\" num_results=\"3\"]\n<\/code><\/pre>\n\nmychurch<\/code> is the name of your church and 3<\/code> is changed to the\nnumber of future featured events you need in a page or post. Use the\nparameter featured=\"1\"<\/code> to obtain only featured events. Because your\ncalendar will have many<\/em> events, make sure you include num_results<\/code>\nto get the number of events you want.<\/p>\n\ndate_start<\/code>\nand date_end<\/code>. If you want events from a particular Calendar category,\nuse category=1<\/code> where 1<\/code> is replaced by the category number for the\nCalendar category you want.<\/p><\/li>\n[cs-event-list church_name=\"mychurch\" num_results=\"10\"]\n<\/code><\/pre>\n\ndate_end<\/code> parameter.<\/p><\/li>\n[cs-calendar church_name=\"mychurch\"]\n<\/code><\/pre>\n\nmychurch<\/code> is the name of your church used to get into your churchsuite).\nThe only parameter that might be used with this apart from church_name<\/code> is\n date_from which will can be any date which will identify the month to be\ndisplayed - so 2025-01-15<\/code> and 2025-01-30<\/code> will both display the month\nJanuary in 2025.<\/p><\/li>\n[cs-smallgroups church_name=\"mychurch\"]\n<\/code><\/pre>\n\nmychurch<\/code> is the name of your church. The more limited set of\nparameters provided by ChurchSuite for small groups can all be used.<\/p><\/li>\n<\/ul>\n\nhttps:\/\/github.com\/ChurchSuite\/churchsuite-api\/blob\/master\/modules\/embed.md=calendar-json-feed<\/code>\nfor a full list of parameters that can be used.<\/p>\n\nLicense<\/h3>\n\n
cs-integration.php<\/code>\nfile in the top comment.<\/p>\n\n\n\n
\n
\n
The shortcode produces no output<\/h3><\/dt>\n
mychurch<\/code>:<\/p>\n\n https:\/\/mychurch.churchsuite.com\/embed\/calendar\/json?num_results=3\n<\/code><\/pre><\/dd>\nHow do I add my church so that I get the JSON feed for my church?<\/h3><\/dt>\n
church_name<\/code> parameter:<\/p>\n\n [cs-event-cards church_name=\"mychurch\" num_results=\"3\"]\n<\/code><\/pre><\/dd>\nI want to limit the number of events in the shortcode<\/h3><\/dt>\n
[cs-events-list church_name=\"mychurch\" num_results=\"6\"]\n<\/code><\/pre><\/dd>\nEvents List is not showing any results<\/h3><\/dt>\n
[cs-events-list church_name=\"mychurch\" num_results=\"6\" days_ahead=\"30\"]\n<\/code><\/pre><\/dd>\nI want to change how the output looks:<\/h3><\/dt>\n
1.0.8<\/h4>\n\n
1.0.7<\/h4>\n\n
1.0.6<\/h4>\n\n
[cs-event-list church_name=\"mychurch\" num_results=\"5\" days_ahead=\"30\"]\n<\/code><\/pre>\n\n1.0.5<\/h4>\n\n
1.0.4<\/h4>\n\n
1.0.3<\/h4>\n\n
1.0.2<\/h4>\n\n
1.0.1<\/h4>\n\n
cs-calendar<\/code> shortcode. Updated\n README.md to reflect these changes.<\/p>\n\n1.0.0<\/h4>\n\n
0.0.1<\/h4>\n\n