Problem with signup.

18 views
Skip to first unread message

Brett Williams

unread,
Jul 13, 2016, 1:51:37 PM7/13/16
to Church.IO
Brand new install on Ubuntu 16.04 using the manual instruction method...

Everything "seems" to be up and functional.  I have started adding a few people to the system and had one of them attempt to create an account, but when verifying via mobile got the following:


I've checked the information in his profile and everything appears to be correct.  What am I missing?
Auto Generated Inline Image 1

Tim Morgan

unread,
Jul 13, 2016, 2:24:28 PM7/13/16
to chur...@googlegroups.com
Is their profile Active? Inactive profiles cannot sign in.

--
https://church.io
https://github.com/churchio
http://chat.church.io
---
You received this message because you are subscribed to the Google Groups "Church.IO" group.
To unsubscribe from this group and stop receiving emails from it, send an email to churchio+u...@googlegroups.com.
To post to this group, send email to chur...@googlegroups.com.
Visit this group at https://groups.google.com/group/churchio.
For more options, visit https://groups.google.com/d/optout.

Brett Williams

unread,
Jul 13, 2016, 2:55:05 PM7/13/16
to Church.IO
Yes, it is showing as active.

Brett Williams

unread,
Jul 13, 2016, 3:55:51 PM7/13/16
to Church.IO
Also took a peek in production.log, nothing there:

I, [2016-07-13T10:19:05.691575 #4996]  INFO -- : Reloading settings for site 1...
I, [2016-07-13T10:19:05.706338 #4996]  INFO -- : Reloading global settings...
I, [2016-07-13T11:19:05.261741 #7208]  INFO -- : Reloading settings for site 1...
I, [2016-07-13T11:19:05.276789 #7208]  INFO -- : Reloading global settings...
I, [2016-07-13T12:19:05.819427 #9363]  INFO -- : Reloading settings for site 1...
I, [2016-07-13T12:19:05.834844 #9363]  INFO -- : Reloading global settings...

Brett Williams

unread,
Jul 13, 2016, 5:18:57 PM7/13/16
to Church.IO
Had another user try and got the same response...

Brett Williams

unread,
Jul 13, 2016, 5:51:35 PM7/13/16
to Church.IO
Here is what I can see in log/apache2/error.log:

App 29413 stderr: Completed 200 OK in 18ms (Views: 11.0ms | ActiveRecord: 0.3ms)
App 29413 stderr: Started POST "/account" for 24.183.195.156 at 2016-07-13 14:16:35 -0700
App 29413 stderr: Processing by AccountsController#create as HTML
App 29413 stderr:   Parameters: {"utf8"=>"✓", "authenticity_token"=>"6AtiIXfVMNfAq2J+hrjK6FBpAEXNBGGL8pKdUh8nQmsD+GSqSXZx5TG+uPtgZhSrX7RNMqhroNjZnwPbzqX1tw==", "phone"=>"true", "verification"=>{"mobile_phone"=>"7311111111", "carrier"=>App 29413 stderr:   Rendered accounts/new_by_mobile.html.haml within layouts/signed_out (5.2ms)
App 29413 stderr:   Rendered layouts/_favicons.haml (0.4ms)
App 29413 stderr:   Rendered layouts/_footer_links.haml (0.7ms)
App 29413 stderr: Completed 200 OK in 27ms (Views: 10.0ms | ActiveRecord: 2.4ms)
App 29413 stderr: Started POST "/account" for 24.183.195.156 at 2016-07-13 14:16:50 -0700
App 29413 stderr: Processing by AccountsController#create as HTML
App 29413 stderr:   Parameters: {"utf8"=>"✓", "authenticity_token"=>"GtMFXGBHM6/thUwH2S+O7S4mgVnpyFAPj0K+DeFMWxfxIAPXXuRynRyQloI/8VCuIfvMLoynkVykTyCEMM7syw==", "phone"=>"true", "verification"=>{"mobile_phone"=>"17311111111", "carrier"=App 29413 stderr:   Rendered accounts/new_by_mobile.html.haml within layouts/signed_out (5.0ms)
App 29413 stderr:   Rendered layouts/_favicons.haml (0.4ms)
App 29413 stderr:   Rendered layouts/_footer_links.haml (0.6ms)
App 29413 stderr: Completed 200 OK in 22ms (Views: 9.6ms | ActiveRecord: 1.6ms)
App 29413 stderr: Started POST "/account" for 24.183.195.156 at 2016-07-13 14:17:03 -0700
App 29413 stderr: Processing by AccountsController#create as HTML
App 29413 stderr:   Parameters: {"utf8"=>"✓", "authenticity_token"=>"kIy+mtBrb8AKemyqhCe8cHzSjpSNAmbMOW3vYAEV6K97f7gR7sgu8vtvti9i+WIzcw/D4+htp58SYHHp0Jdfcw==", "phone"=>"true", "verification"=>{"mobile_phone"=>"7311111111", "carrier"=>"AT&$p 29413 stderr:   Rendered accounts/new_by_mobile.html.haml within layouts/signed_out (5.0ms)
App 29413 stderr:   Rendered layouts/_favicons.haml (0.4ms)
e$p 29413 stderr:   Rendered layouts/_footer_links.haml (0.7ms)     
n$p 29413 stderr: Completed 200 OK in 24ms (Views: 9.7ms | ActiveRecord: 1.7ms)          
App 29413 stderr: Started POST "/account" for 24.183.195.156 at 2016-07-13 14:17:11 -0700
e$p 29413 stderr: Processing by AccountsController#create as HTML
"$p 29413 stderr:   Parameters: {"utf8"=>"✓", "authenticity_token"=>"cHV/JKp64SS2KEczubLXmX/8M3JIKEEBDGbBieEx9QCbhnmvlNmgFkc9nbZfbAnacCF+BS1HgFIna18AMLNC3A==", "phone"=>"true", "verification"=>{"mobile_phone"=>"7311111111", "carrier"=>"$p 29413 stderr:   Rendered accounts/new_by_mobile.html.haml within layouts/signed_out (5.6ms)
App 29413 stderr:   Rendered layouts/_favicons.haml (0.5ms)
App 29413 stderr:   Rendered layouts/_footer_links.haml (0.7ms)                
e$p 29413 stderr: Completed 200 OK in 26ms (Views: 11.2ms | ActiveRecord: 1.4ms)   



Brett Williams

unread,
Jul 14, 2016, 9:00:13 AM7/14/16
to Church.IO
Problem solved!

Wish I could take more credit for this than God's providence, but I can't...  The users that were getting this error did not have e-mail addresses setup.  When I added their email address, thinking I would try having them verify against e-mail. It dawned on me that the only other users that didn't have a problem already had e-mail addresses in the system.  So I had the people with problems try phone verification after adding email addresses for them and everything worked smoothly...

From what I have read, I don't guess this is a bug, rather a limitation of the design.  But, it is something that might be addresses through some kind of documentation or on screen prompting, such as a "nag" that lack of email address will prevent user from creating an account.

I'm liking this software and since I have recently started getting into Ruby, hopefully being able to contribute to this in a more meaningful way as we figure out how we want our church to use it.

Tim Morgan

unread,
Jul 14, 2016, 9:52:30 AM7/14/16
to Church.IO
Yay! I intended to take a look at that today, because I couldn't think of what else would cause that. I agree that we should give better messaging when this occurs!

-Tim

--
Reply all
Reply to author
Forward
0 new messages