Welcome back to CCB Tutorials! Today’s tutorial is one that many folks have likely pondered but may or may not have desired or been too intimidated by to dive into the details.
From weekend services to special events to classes to seminars to workshops and the list continues, managing events in CCB is likely one of the top three actions used by most churches.
While CCB serves small to medium-sized congregations well in regards to event management, larger congregations often require self-managed event functionality, especially multi-site or multi-campus church organizations.
I’ve recently fielded inquiries from churches pertaining to the integration of 3rd-party event management software with CCB.
While most of the event management will occur in the 3rd-party system, there is also a need to create and track event and registration data upon close of event.
While an event with 100-150 registrants/attendees is roughly easy to manually manage, reconciling event and registration data for hundreds or thousands of persons is simply not possibly without a team of volunteers or staff.
Nevertheless, I’ll share how to create events in CCB using PHP and CCB’s API in today’s tutorial. Of course, your respective 3rd-party event management software will need to have an available API.
In addition, I’ve also written a few tutorials pertaining to accessing event attendance data that you’ll likely want to combine with today’s tutorial. But without further ado, let’s get started!Read This Tutorial
Over the last few weeks, there’s been a bit of excitement in the world of Church Community Builder, also affectionately known as CCB.
I use “excitement” loosely as many churches using CCB’s API were informed about CCB implementing a new per-minute rate limiting policy in addition to its per-day allotment of 10,000 calls per day — which they hope to retire sooner rather than later, yet it’ll remain in place for now.
As of August 20th, this new rate limiting strategy aims to restrict how many times per minute an API user can access an individual API Service — noted in New API Rate Limiting documentation.
So, what does this truly mean to you, and more importantly, how does this new strategy impact developed applications and environments using CCB’s API? 🤔 Read This Tutorial
Welcome to another CCB Tutorial.
Picking up from where we left off last, it was brought to my attention that last week’s tutorial may have another option as it pertains to creating a simplified login page using the CCB API.
Last week’s tutorial focused on validating a user’s credentials simply using the Individual Profile from Login and Password CCB API service.
Again, last week’s tutorial and today’s tutorial are not a secure or fool-proof login system, and should not be depicted or interpreted as such.
In addition to using the Individual Profile from Login and Password CCB API service, I would like to introduce you to another CCB API service that can be interchanged as well: Community Login. Read This Tutorial
Welcome back! Today’s tutorial will focus on creating a simple and functioning login page that validates a user’s credentials.
I use the term validate instead of authenticate because this is truly not a secure or fool-proof login system using CCB’s API.
The API service we’ll use, Individual Profile from Login and Password, simply states that using this service returns an individual profile for the login and password provided.
However, with a bit of elbow grease, we’re going to use this service to create a simple login page.
In today’s tutorial, I’m sharing with you how to access and display group profiles by id.
Not to be confused with the group_profiles API service — which allows you to pass in a given date and have all groups created or modified since that date returned to you, today’s tutorial will access group_profiles_from_id API service.
So instead of focusing on returning ALL group profiles, we’ll focus on accessing and displaying a specific group by its group id (as shown below).
That stated, let’s get started with today’s tutorial. Read This Tutorial