Verify and activate the planningcenter plugin in the Settings->Manage Plugins menu.

Installation (MacOS)

Right click on OpenLP in the Applications Folder and select "Show Package Contents"

Unzip the planningcenter.zip file inside of the OpenLP application at Contents/MacOS/plugins, keeping the planningcenter folder intact.

Usage:

Select the File->Import->Planning Center Service menu.

Setup your authentication keys, following the directions in the GUI.

Import Services

Recommended Settings:

Turn off the "Import missing songs from service files" configuration
in the Songs plugin. You will get strange results if you (a) import a
song, (b). change the song lyrics on Planning Center, (c) import the song again, (d)
edit the song. You will display the correct lyrics in the Service
Manager but if you try and "edit" the song from the ServiceManager, then
you will be editing the original lyrics, not the updated ones. You are
better off depending on PCO as your song database if you use this
plugin.

Currently Supported Features:

Importing Lyrics from Planning Center songs that are added to a service (no verse order or other media support currently)

Importing slides as Custom Slides. Note: the V2 API does not have
support for getting the content added to slides on Planning Center.
While PCO is discussing adding this back into the V2 API, they do not
intend to continue to have support for editing these slides in the
Services Web GUI sometime in 2019. So... this plugin just replicates
the titles of any slides onto a single-page custom slide.

Updating Service. This updates the current service in OpenLP with a
new copy from Planning Center Online, keeping any edits you've made
since you Imported it earlier. The use case here is that you are
updating Custom Slides while the band is off working on rehearsals.
After rehearsals, you can use the "update" feature to pull in any lyric
or song-order updates without overwriting your custom slide updates.
Note: if a song or custom slide is removed from Planning Center, it will also be removed from OpenLP, even if you have updated it.

Comments

As also mentioned in a different thread I managed to convince our build system to create a windows test build that should include the PCO plugin. I have not tested it myself since I don't have a windows PC, so feel free to test.
Get it here: https://ci.appveyor.com/project/OpenLP/dev/build/OpenLP-win-ci-b638/artifacts
Note that this is not a supported build!!!

The previous 0.1 release was based off of a standalone
utility that I wrote that reverse engineered the json/xml formats in the
OpenLP saved service files and then mimicked the actions of loading
these into a new service.

This 0.2 release builds upon that code and knowledge but incorporates
OpenLP classes and documentation styles into the classes/methods.

1. Which version of the plugin did you use? The newest is 0.2.1 available from https://github.com/ghjpk/planningcenter/releases (Note: this would not cause the issue you are seeing... just want to make sure you downloaded the newest release.)

2. When you look inside share/openlp/plugins, do you see other OpenLP plugins in that same location, like the following: alerts bibles custom images media presentations remotes songs songusage (this question is to double confirm that this is the correct directory).

3. When you navigate to the share/openlp/plugins/planningcenter directory and do a "ls", what files/directories do you see? You should see at least forms & lib directories and a file: planningcenterplugin.py. If you see a planningcenter directory instead, then you have the planningcenter directories doubled up, meaning you have planningcenter/planningcenter/planningcenterplugin.py, when it should just be planningcenter/planningcenterplugin.py (this is actually my current guess as to what might be occurring).

4. What version of OpenLP are you using? This was developed with and only tested with 2.4.6.

5. What version of Linux are you using? You don't need to match my version, but I am using it with Ubuntu 18.04 LTS. You can see your version/distribution by running "lsb_release -a" on your system.

Hi John. I had wondered why I had to create a plugins directory. Default under Linux/Elementary is eg //home/alistair/.local/share/openlp and all the plugins are within that directory not under a plugins directory

However, when I move yours and another custom plugin to the openlp directory, after reopening openlp, these new plugins are still not visible.

Brilliant, visible now. Will advise later. BTW did you try Olp-yt-master?? I have that now in correct plugin directory but that isnt visible. Pretty sure the Olp-yt needs to be added as a formatting tag, rather than a plugin as it hasnt got plugin structure.

Hi, fkrol,
I used the date format in the code that my planning center sends me. Your date string is different than mine.
To fix this, I’ll either need to use a library that automatically parses arbitrary date strings or find a date string setting in the planning center API.
In which country are you located? I want to see if I can get my planningcenter to behave like yours.
Thanks,
-John

I ended up finding a different date value in the API that is always the same regardless of the user's time/locale configuration. The fix is available in the 0.4 release of the planningcenter plugin at: https://github.com/ghjpk/planningcenter/releases

Perhaps @tgc will create a new Windows build, or you can download the plugin directly and replace the one in your current package.