Church Web Requirements

200 views
Skip to first unread message

Tom Brooke

unread,
Oct 17, 2011, 9:03:02 AM10/17/11
to onebo...@googlegroups.com


I am getting ready to meet with a new Pastor that is starting at our Church in January. I am trying to get together my thoughts on Church Web presence. We are going to start from scratch and redo our web page to start off a new era at our Church. We have also built a huge addition - without a pastor and we are a very active congregation - We use Facebook a lot.  We tried Memberhub and Onebody and neither one caught on We have a worpdess web site now that is in disrepair and on hold till we get revamped

This may be off topic but  I thought it would be interesting to get a discussion started on what Churches need, what they want, what they think they want but don't really want, what works and what doesn't. Also I think this might help Tim as he develops profiles. Following are just random ideas - some are in Profiles

Random thoughts

1. Engagement  tool ??

2. Way to publicize Church to the community and the world

3. Ways to communicate activities and services

4. A CMS for articles and pictures or videos about the Church and Church programs

5. Pastor's Blog - or blog by others than the pastor

6. Sermon podcasts  - best way to handle audio, video or both

7 Facebook integration

8 Internal communication tools - such as a directory, calendar, sign up sheets, birthdays,  profiles

9. Donations and Pledge ? Donortools intgration?

10. Document management for bulletins, newsletters, account and budget reports

11 Committee rosters

12. Governance tools - consistory notes online voting?

13. discussion tools -- will anybody use this?

14. Video for plays - video projects - Youtube integration?

15 Twitter


These are just random items that came to mind - Profiles may address some or most of this - if not what can we develop to compliment Profiles

What will be easy for congregations to adjust to?

Tom Brooke

Justyn

unread,
Oct 18, 2011, 4:40:05 AM10/18/11
to OneBody
Hi

I've been trying out ChurchTechies CMS which is very good and includes
a podcast, events, documents & blog functionality. I'm looking to move
our website to it as the support service has been good, and I think it
is going to be very cost effective. I'm thinking of using DonorTools
for donations and MailChimp for emails, but need to integrate these as
well. When Profiles becomes ready for public use I may well look to
use it as well. I would like them to 'talk together' a bit more
through APIs etc..

Justyn

Tim Morgan

unread,
Oct 19, 2011, 3:23:20 PM10/19/11
to onebo...@googlegroups.com
Thanks guys, for your thoughts.

Profiles is nearing a 0.1 release in the next week. I'd love to get your feedback on if it's useful to you and your congregation -- and where it might fit into the whole picture.

I don't believe (nor want) Profiles to solve many problems; really I'm hoping it will be more of a catalyst for greater community involvement in open source church software.

As always, your thoughts are greatly appreciated!

-Tim

--
You received this message because you are subscribed to the Google Groups "OneBody" group.
To post to this group, send email to onebo...@googlegroups.com.
To unsubscribe from this group, send email to onebodyapp+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/onebodyapp?hl=en.


Tom Brooke

unread,
Oct 19, 2011, 4:57:57 PM10/19/11
to onebo...@googlegroups.com
I will definitely try 0.1 Since it apparently launches on Heroku out of the box I can put it up and let some folks see it  - Tim I had some trouble with the facebook login but it may have been a pretty early version I tried it with - I have had trouble with a lot of software coordinating email/password login and social network login and this may be the same thing - It seems that if you set up the account with email and then go back and try to use facebook login you can't - this may be the way it should be but it should be clearer that you can login one way or the other or both  - Maybe it's an OmniAuth thing or maybe it is just me

I looked at Churchtechies - I thought it was Radiant but it is apparently custom based on shopifie's liquid templating language or perhaps it's a shopify CMS - I like liquid and setup is pretty easy and economical they end beta on Oct 23rd but it is still cheap after that   The author David McWilliams was a Onebody user

You could put something together something quickly and easily with Church Techies but my inclination now is to look for a Rails 3.1 CMS that I can integrate with Profiles. I think a Church needs to have one web address otherwise people get confused

Tim Morgan

unread,
Oct 19, 2011, 6:09:21 PM10/19/11
to onebo...@googlegroups.com
On Wed, Oct 19, 2011 at 3:57 PM, Tom Brooke <tom.b...@gmail.com> wrote:
I will definitely try 0.1 Since it apparently launches on Heroku out of the box I can put it up and let some folks see it  - Tim I had some trouble with the facebook login but it may have been a pretty early version I tried it with - I have had trouble with a lot of software coordinating email/password login and social network login and this may be the same thing - It seems that if you set up the account with email and then go back and try to use facebook login you can't - this may be the way it should be but it should be clearer that you can login one way or the other or both  - Maybe it's an OmniAuth thing or maybe it is just me

You're probably right -- I haven't done enough testing of that workflow yet. I do intend that users can use either/or login method.

-Tim

PCCC

unread,
Nov 13, 2011, 10:02:53 PM11/13/11
to Church.IO
I'm also unable to login using either facebook login or trying to
create a new account gives the error

We're sorry, but something went wrong.

We've been notified about this issue and we'll take a look at it
shortly.

Any thoughts?

On Oct 19, 4:09 pm, Tim Morgan <t...@timmorgan.org> wrote:

Tim Morgan

unread,
Nov 13, 2011, 10:23:32 PM11/13/11
to chur...@googlegroups.com
Try running "heroku logs" (without quotes) and send us the output.

-Tim

--
You received this message because you are subscribed to the Google Groups "Church.IO" group.
To post to this group, send email to chur...@googlegroups.com.
To unsubscribe from this group, send email to churchio+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/churchio?hl=en.


PCCC

unread,
Nov 14, 2011, 10:06:54 AM11/14/11
to Church.IO
D:\profiles>heroku logs2011-11-14T02:58:27+00:00 app[web.1]:
2011-11-14T02:58:27+00:00 app[web.1]: Started GET "/users/sign_up" for
71.37.224.14 at 2011-11-14 02:58:27 +00002011-11-14T02:58:27+00:00
app[web.1]: cache: [GET /users/sign_up] miss2011-11-14T02:58:27+00:00
app[web.1]:   Processing by UsersController#new as
HTML2011-11-14T02:58:27+00:00 app[web.1]: Rendered users/new.html.haml
within layouts/application (8.7ms)2011-11-14T02:58:27+00:00 app[web.
1]: Completed 200 OK in 17ms (Views: 15.5ms |ActiveRecord:
0.0ms)2011-11-14T02:58:27+00:00 heroku[router]: GET pccc.herokuapp.com/
users/sign_up dyno=web.1 queue=0 wait=0ms service=28ms status=200
bytes=27442011-11-14T02:59:04+00:00 app[web.1]:
2011-11-14T02:59:04+00:00 app[web.1]:2011-11-14T02:59:04+00:00 app[web.
1]: Started POST "/users" for 71.37.224.14 at2011-11-14 02:59:04
+00002011-11-14T02:59:04+00:00 app[web.1]: cache: [POST /users]
invalidate, pass2011-11-14T02:59:04+00:00 app[web.1]:   Processing by
UsersController#create asHTML2011-11-14T02:59:04+00:00 app[web.1]:  
Parameters: {"utf8"=>"Γ£ô", "authenticity_token"=>"X
+EOHIf7k5e4tLoqJtwaeoGLNmMh778o1VN552AqQ8c=",
"user"=>{"email"=>"kim...@gmail.com", "password"=>"[FILTERED]",
"password_confirmation"=>"[FILTERED]"}, "commit"=>"Sign Up"}
2011-11-14T02:59:04+00:00 app[web.1]: Redirected to
http://pccc.herokuapp.com/2011-11-14T02:59:04+00:00 app[web.1]:
Completed 302 Found in 157ms2011-11-14T02:59:04+00:00 heroku[router]:
POST pccc.herokuapp.com/users dyno=web.1 queue=0 wait=0ms
service=324ms status=302 bytes=922011-11-14T02:59:04+00:00 app[web.1]:
2011-11-14T02:59:04+00:00 app[web.1]:2011-11-14T02:59:04+00:00 app[web.
1]: Started GET "/" for 71.37.224.14 at 2011-11-14 02:59:04
+00002011-11-14T02:59:05+00:00 app[web.1]: cache: [GET /]
miss2011-11-14T02:59:05+00:00 app[web.1]:   Processing by
HomesController#show as HTML2011-11-14T02:59:05+00:00 app[web.1]:
Redirected to http://pccc.herokuapp.com/profile2011-11-14T02:59:05+00:00
app[web.1]: Completed 302 Found in 9ms2011-11-14T02:59:05+00:00
heroku[router]: GET pccc.herokuapp.com/ dyno=web.1 queue=0 wait=0ms
service=31ms status=302 bytes=992011-11-14T02:59:05+00:00 app[web.1]:
2011-11-14T02:59:05+00:00 app[web.1]:2011-11-14T02:59:05+00:00 app[web.
1]: Started GET "/profile" for 71.37.224.14 at 2011-11-14 02:59:05
+00002011-11-14T02:59:05+00:00 app[web.1]: cache: [GET /profile]
miss2011-11-14T02:59:05+00:00 app[web.1]:   Processing by
ProfilesController#show as HTML2011-11-14T02:59:05+00:00 app[web.1]:
Redirected to http://pccc.herokuapp.com/profiles/new2011-11-14T02:59:05+00:00
app[web.1]: Completed 302 Found in 116ms2011-11-14T02:59:05+00:00
app[web.1]:2011-11-14T02:59:05+00:00 app[web.1]:
2011-11-14T02:59:05+00:00 app[web.1]: Started GET "/profiles/new" for
71.37.224.14 at 2011-11-14 02:59:05 +00002011-11-14T02:59:05+00:00
heroku[router]: GET pccc.herokuapp.com/profiles/new dyno=web.1 queue=0
wait=0ms service=176ms status=200 bytes=101792011-11-14T02:59:05+00:00
app[web.1]:2011-11-14T02:59:05+00:00 app[web.1]:
2011-11-14T02:59:05+00:00 app[web.1]: Started GET "/assets/
jquery.miniColors.css" for 71.37.224.14 at 2011-11-14 02:59:05
+00002011-11-14T02:59:05+00:00 app[web.1]:2011-11-14T02:59:05+00:00
app[web.1]:2011-11-14T02:59:05+00:00 app[web.1]: Started GET "/assets/
jquery.miniColors.js" for 71.37.224.14 at 2011-11-14 02:59:05
+00002011-11-14T02:59:05+00:00 app[web.1]: cache: [GET /assets/
jquery.miniColors.css] miss, store2011-11-14T02:59:05+00:00 app[web.
1]: Compiled jquery.miniColors.css  (0ms)  (pid
1)2011-11-14T02:59:05+00:00 app[web.1]: Served asset /
jquery.miniColors.css - 200OK (64ms)2011-11-14T02:59:05+00:00
heroku[router]: GET pccc.herokuapp.com/assets/jquery.miniColors.css
dyno=web.1 queue=0 wait=0ms service=82ms status=200
bytes=11382011-11-14T02:59:06+00:00 app[web.1]:
2011-11-14T02:59:06+00:00 app[web.1]:2011-11-14T02:59:06+00:00 app[web.
1]: Started GET "/assets/profile_form.js" for71.37.224.14 at
2011-11-14 02:59:06 +00002011-11-14T02:59:06+00:00 app[web.1]: cache:
[GET /assets/jquery.miniColors.js]miss, store2011-11-14T02:59:06+00:00
app[web.1]: Compiled jquery.miniColors.js  (2ms)
 (pid 1)2011-11-14T02:59:06+00:00 app[web.1]: Served asset /
jquery.miniColors.js - 200 OK (283ms)2011-11-14T02:59:06+00:00
heroku[router]: GET pccc.herokuapp.com/assets/jquery.miniColors.js
dyno=web.1 queue=0 wait=0ms service=331ms status=200
bytes=87132011-11-14T02:59:06+00:00 app[web.1]: cache: [GET /assets/
profile_form.js] miss, store2011-11-14T02:59:06+00:00 app[web.1]:
Compiled profile_form.js  (152ms)  (pid 1)
2011-11-14T02:59:06+00:00 heroku[router]: GET pccc.herokuapp.com/
assets/profile_form.js dyno=web.1 queue=0 wait=1ms service=579ms
status=200 bytes=6082011-11-14T02:59:06+00:00 app[web.1]: Served
asset /profile_form.js - 200 OK (284ms)2011-11-14T02:59:49+00:00
app[web.1]:2011-11-14T02:59:49+00:00 app[web.1]:
2011-11-14T02:59:49+00:00 app[web.1]: Started POST "/profiles" for
71.37.224.14at 2011-11-14 02:59:49 +00002011-11-14T02:59:49+00:00
app[web.1]: cache: [POST /profiles] invalidate,
pass2011-11-14T02:59:49+00:00 app[web.1]:   Processing by
ProfilesController#createas HTML2011-11-14T02:59:49+00:00 app[web.1]:
  Parameters: {"utf8"=>"Γ£ô", "authenticity_token"=>"X
+EOHIf7k5e4tLoqJtwaeoGLNmMh778o1VN552AqQ8c=",
"profile"=>{"name"=>"Kimberly", "headline"=>"Wag more, bark less",
"bio"=>"", "gender"=>"f", "birthday(1i)"=>"", "birthday(2i)"=>"2",
"birthday(3i)"=>"28", "location"=>"", "phone"=>""}, "commit"=>"Save"}
2011-11-14T02:59:49+00:00 app[web.1]: Redirected to
http://pccc.herokuapp.com/profiles/12011-11-14T02:59:49+00:00 app[web.
1]: Completed 302 Found in 120ms2011-11-14T02:59:49+00:00
heroku[router]: POST pccc.herokuapp.com/profiles dyno=web.1 queue=0
wait=0ms service=202ms status=302 bytes=1022011-11-14T02:59:49+00:00
app[web.1]:2011-11-14T02:59:49+00:00 app[web.1]:
2011-11-14T02:59:49+00:00 app[web.1]: Started GET "/profiles/1" for
71.37.224.14 at 2011-11-14 02:59:49 +00002011-11-14T02:59:49+00:00
app[web.1]:2011-11-14T02:59:49+00:00 app[web.1]: CanCan::AccessDenied
(You are not authorized to access this page.):
2011-11-14T02:59:49+00:00 app[web.1]:2011-11-14T02:59:49+00:00 app[web.
1]:2011-11-14T02:59:49+00:00 app[web.1]:2011-11-14T02:59:49+00:00
app[web.1]: cache: [GET /profiles/1] miss2011-11-14T02:59:49+00:00
app[web.1]:   Processing by ProfilesController#show
as HTML2011-11-14T02:59:49+00:00 app[web.1]:   Parameters: {"id"=>"1"}
2011-11-14T02:59:49+00:00 app[web.1]: Completed 500 Internal Server
Error in 22ms2011-11-14T04:02:04+00:00 heroku[web.1]:
Idling2011-11-14T04:02:05+00:00 heroku[web.1]: State changed from up
to down2011-11-14T04:02:05+00:00 heroku[web.1]: State changed from
down to created2011-11-14T04:02:05+00:00 heroku[web.1]: State changed
from created to starting2011-11-14T04:02:07+00:00 heroku[web.1]:
Stopping process with SIGTERM2011-11-14T04:02:07+00:00 app[web.1]:
[2011-11-14 04:02:07] ERROR SignalException:
SIGTERM2011-11-14T04:02:07+00:00 app[web.1]:   /usr/local/lib/ruby/
1.9.1/webrick/server.rb:90:in `select'2011-11-14T04:02:14+00:00
heroku[web.1]: Starting process with command `bundle exec rails server
-p 35104`2011-11-14T04:02:17+00:00 heroku[web.1]: Error R12 (Exit
timeout) -> Process failed to exit within 10 seconds of
SIGTERM2011-11-14T04:02:17+00:00 heroku[web.1]: Stopping process with
SIGKILL2011-11-14T04:02:19+00:00 heroku[web.1]: Process
exited2011-11-14T04:02:20+00:00 app[web.1]: /app/vendor/bundle/ruby/
1.9.1/gems/rack-1.3.4/lib/rack/backports/uri/common_192.rb:53:
warning: already initialized constant WFKV_2011-11-14T04:02:33+00:00
app[web.1]: [2011-11-14 04:02:33] INFO  WEBrick
1.3.12011-11-14T04:02:33+00:00 app[web.1]: [2011-11-14 04:02:33] INFO
 ruby 1.9.2 (2011-07-09) [x86_64-linux]2011-11-14T04:02:33+00:00
app[web.1]: [2011-11-14 04:02:33] INFO  WEBrick::HTTPServer#start:
pid=1 port=351042011-11-14T04:02:34+00:00 heroku[web.1]: State changed
from starting to up2011-11-14T05:09:37+00:00 heroku[web.1]:
Idling2011-11-14T05:09:38+00:00 heroku[web.1]: State changed from up
to down2011-11-14T05:09:40+00:00 heroku[web.1]: Stopping process with
SIGTERM2011-11-14T05:09:40+00:00 app[web.1]: [2011-11-14 05:09:40]
ERROR SignalException: SIGTERM2011-11-14T05:09:49+00:00 heroku[web.1]:
Error R12 (Exit timeout) -> Process failed to exit within 10 seconds
of SIGTERM2011-11-14T05:09:49+00:00 heroku[web.1]: Stopping process
with SIGKILL2011-11-14T05:09:51+00:00 heroku[web.1]: Process exited

Tim Morgan

unread,
Nov 14, 2011, 5:50:40 PM11/14/11
to chur...@googlegroups.com
I was able to log in using Facebook on your site. Seems to be working now?

PCCC

unread,
Nov 16, 2011, 7:21:58 PM11/16/11
to Church.IO
Well, sort of. It still won't let me log in with Facebook. I had my
husband try and it let him with no problems. I tried 4 different
browsers and my cell phone still no good. I was finally able to login
using email and password. I was able to go to admin and accept you
but it's not accepting my profile. I just keep getting a "There were
errors" message.

On Nov 14, 4:50 pm, Tim Morgan <t...@timmorgan.org> wrote:
> I was able to log in using Facebook on your site. Seems to be working now?
>
>
>
>
>
>
>
> On Mon, Nov 14, 2011 at 9:06 AM, PCCC <secret...@plymouthcreek.org> wrote:
> > D:\profiles>heroku logs2011-11-14T02:58:27+00:00 app[web.1]:
> > 2011-11-14T02:58:27+00:00 app[web.1]: Started GET "/users/sign_up" for
> > 71.37.224.14 at 2011-11-14 02:58:27 +00002011-11-14T02:58:27+00:00
> > app[web.1]: cache: [GET /users/sign_up] miss2011-11-14T02:58:27+00:00
> > app[web.1]:   Processing by UsersController#new as
> > HTML2011-11-14T02:58:27+00:00 app[web.1]: Rendered users/new.html.haml
> > within layouts/application (8.7ms)2011-11-14T02:58:27+00:00 app[web.
> > 1]: Completed 200 OK in 17ms (Views: 15.5ms |ActiveRecord:
> > 0.0ms)2011-11-14T02:58:27+00:00 heroku[router]: GET pccc.herokuapp.com/
> > users/sign_up <http://pccc.herokuapp.com/%0Ausers/sign_up> dyno=web.1
> > queue=0 wait=0ms service=28ms status=200
> > bytes=27442011-11-14T02:59:04+00:00 app[web.1]:
> > 2011-11-14T02:59:04+00:00 app[web.1]:2011-11-14T02:59:04+00:00 app[web.
> > 1]: Started POST "/users" for 71.37.224.14 at2011-11-14 02:59:04
> > +00002011-11-14T02:59:04+00:00 app[web.1]: cache: [POST /users]
> > invalidate, pass2011-11-14T02:59:04+00:00 app[web.1]:   Processing by
> > UsersController#create asHTML2011-11-14T02:59:04+00:00 app[web.1]:
> > Parameters: {"utf8"=>"Γ£ô", "authenticity_token"=>"X
> > +EOHIf7k5e4tLoqJtwaeoGLNmMh778o1VN552AqQ8c=",
> > "user"=>{"email"=>"kim...@gmail.com", "password"=>"[FILTERED]",
> > "password_confirmation"=>"[FILTERED]"}, "commit"=>"Sign Up"}
> > 2011-11-14T02:59:04+00:00 app[web.1]: Redirected to
> >http://pccc.herokuapp.com/2011-11-14T02:59:04+00:00app[web.1]:
> > Completed 302 Found in 157ms2011-11-14T02:59:04+00:00 heroku[router]:
> > POST pccc.herokuapp.com/users dyno=web.1 queue=0 wait=0ms
> > service=324ms status=302 bytes=922011-11-14T02:59:04+00:00 app[web.1]:
> > 2011-11-14T02:59:04+00:00 app[web.1]:2011-11-14T02:59:04+00:00 app[web.
> > 1]: Started GET "/" for 71.37.224.14 at 2011-11-14 02:59:04
> > +00002011-11-14T02:59:05+00:00 app[web.1]: cache: [GET /]
> > miss2011-11-14T02:59:05+00:00 app[web.1]:   Processing by
> > HomesController#show as HTML2011-11-14T02:59:05+00:00 app[web.1]:
> > Redirected tohttp://pccc.herokuapp.com/profile2011-11-14T02:59:05+00:00
> > dyno=web.1<http://pccc.herokuapp.com/assets/jquery.miniColors.css%0Adyno=web.1>queue=0 wait=0ms service=82ms status=200
> > bytes=11382011-11-14T02:59:06+00:00 app[web.1]:
> > 2011-11-14T02:59:06+00:00 app[web.1]:2011-11-14T02:59:06+00:00 app[web.
> > 1]: Started GET "/assets/profile_form.js" for71.37.224.14 at
> > 2011-11-14 02:59:06 +00002011-11-14T02:59:06+00:00 app[web.1]: cache:
> > [GET /assets/jquery.miniColors.js]miss, store2011-11-14T02:59:06+00:00
> > app[web.1]: Compiled jquery.miniColors.js  (2ms)
> >  (pid 1)2011-11-14T02:59:06+00:00 app[web.1]: Served asset /
> > jquery.miniColors.js - 200 OK (283ms)2011-11-14T02:59:06+00:00
> > heroku[router]: GET pccc.herokuapp.com/assets/jquery.miniColors.js
> > dyno=web.1 queue=0 wait=0ms service=331ms status=200
> > bytes=87132011-11-14T02:59:06+00:00 app[web.1]: cache: [GET /assets/
> > profile_form.js] miss, store2011-11-14T02:59:06+00:00 app[web.1]:
> > Compiled profile_form.js  (152ms)  (pid 1)
> > 2011-11-14T02:59:06+00:00 heroku[router]: GET pccc.herokuapp.com/
> > assets/profile_form.js<http://pccc.herokuapp.com/%0Aassets/profile_form.js>dyno=web.1 queue=0 wait=1ms service=579ms
> > status=200 bytes=6082011-11-14T02:59:06+00:00 app[web.1]: Served
> > asset /profile_form.js - 200 OK (284ms)2011-11-14T02:59:49+00:00
> > app[web.1]:2011-11-14T02:59:49+00:00 app[web.1]:
> > 2011-11-14T02:59:49+00:00 app[web.1]: Started POST "/profiles" for
> > 71.37.224.14at 2011-11-14 02:59:49 +00002011-11-14T02:59:49+00:00
> > app[web.1]: cache: [POST /profiles] invalidate,
> > pass2011-11-14T02:59:49+00:00 app[web.1]:   Processing by
> > ProfilesController#createas HTML2011-11-14T02:59:49+00:00 app[web.1]:
> >   Parameters: {"utf8"=>"Γ£ô", "authenticity_token"=>"X
> > +EOHIf7k5e4tLoqJtwaeoGLNmMh778o1VN552AqQ8c=",
> > "profile"=>{"name"=>"Kimberly", "headline"=>"Wag more, bark less",
> > "bio"=>"", "gender"=>"f", "birthday(1i)"=>"", "birthday(2i)"=>"2",
> > "birthday(3i)"=>"28", "location"=>"", "phone"=>""}, "commit"=>"Save"}
> > 2011-11-14T02:59:49+00:00 app[web.1]: Redirected to
> >http://pccc.herokuapp.com/profiles/12011-11-14T02:59:49+00:00app[web.
> ...
>
> read more »

Tim Morgan

unread,
Nov 16, 2011, 8:45:28 PM11/16/11
to chur...@googlegroups.com
I think I know what the issue is. Gustavo commited a patch to the Facebook UID because it was too short. Some users with longer UIDs are unable to log in, while those of us with shorter UIDs can log in just fine.

The patch will be in the next release, which I'll try to push out very soon. Once you upgrade, it should work fine.

Stay tuned for the update...

-Tim

Tim Morgan

unread,
Nov 18, 2011, 6:17:50 PM11/18/11
to chur...@googlegroups.com
Profiles 0.1.2 is now on GitHub, and instructions for upgrading are now here:

http://church.io/profiles/install.html#upgrade

Please upgrade your app following the instructions linked above, and try again to log in with Facebook.

-Tim

PCCC

unread,
Nov 26, 2011, 6:51:55 PM11/26/11
to Church.IO
It works now thanks.

On Nov 18, 5:17 pm, Tim Morgan <t...@timmorgan.org> wrote:
> Profiles 0.1.2 is now on GitHub, and instructions for upgrading are now
> here:
>
> http://church.io/profiles/install.html#upgrade
>
> Please upgrade your app following the instructions linked above, and try
> again to log in with Facebook.
>
> -Tim
>
>
>
>
>
>
>
> On Wed, Nov 16, 2011 at 7:45 PM, Tim Morgan <t...@timmorgan.org> wrote:
> > I think I know what the issue is. Gustavo commited a patch to the Facebook
> > UID because it was too short. Some users with longer UIDs are unable to log
> > in, while those of us with shorter UIDs can log in just fine.
>
> > The patch will be in the next release, which I'll try to push out very
> > soon. Once you upgrade, it should work fine.
>
> > Stay tuned for the update...
>
> > -Tim
>

> >> > >http://pccc.herokuapp.com/2011-11-14T02:59:04+00:00app[web.1]<http://pccc.herokuapp.com/2011-11-14T02:59:04+00:00app%5Bweb.1%5D>

> >> > >http://pccc.herokuapp.com/profiles/12011-11-14T02:59:49+00:00app[web<http://pccc.herokuapp.com/profiles/12011-11-14T02:59:49+00:00app%5Bweb>

> ...
>
> read more »

Tim Morgan

unread,
Nov 28, 2011, 10:05:27 AM11/28/11
to chur...@googlegroups.com
Awesome. Thanks for letting us know!

> ...
>
> read more »

Reply all
Reply to author
Forward
0 new messages