Closed (fixed)
Project:
SMS Framework
Version:
8.x-1.x-dev
Component:
Core Framework
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
29 Feb 2016 at 08:32 UTC
Updated:
19 May 2016 at 11:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
dpiComment #3
dpiWorking on this tomorrow
Comment #4
dpiComment #5
dpi#2677676: Automated Messages & Sleep is a prerequisite.
Comment #6
dpiThis will resolve #2650656: Rename sms_user_delete()
Comment #7
dpiI'm going to continue this issue by gutting functions out of core and sms_user once #2677676: Automated Messages & Sleep is in.
Comment #8
dpiSeeing what testbot thinks. Will post a PR and some related issue shortly
Comment #12
dpiComment #13
dpiIssue blocked on #2707697: Update sendtophone to use phone number provider
Comment #14
dpiIssue blocked on #2707723: Update register via SMS feature to use phone number provider
Comment #15
dpiUpdating for HEAD to help me develop #2707723: Update register via SMS feature to use phone number provider. No need to review.
Comment #19
dpiJust running tests
Comment #23
dpiWrong file
Comment #27
dpiAs of 023ce24
Comment #31
dpiOld test snuck back in
Comment #35
almaudoh commentedI'm still reviewing this patch
Comment #36
dpiYuck I just posted the wrong patch again.
PR is here: https://github.com/dpi/smsframework/pull/15/files
Should be easy review. Make a list of any features that need replacements (if any)
Edit: no problems, PR above for easy reading
Edit2: test failure is random, see #2712613: Account creation fails when the regex delimiter is included in the incoming message
Comment #38
almaudoh commentedAre we losing this view completely? We should move it elsewhere...
Other key functionality I've not yet seen in other patches which are being removed here include: user registration form integration; user login form integration; rules integration; etc. Unfortunately, we didn't originally have test coverage for these.
Let me have some time to look at this patch in more detail.
Comment #39
dpiIs this useful? A view to see the phone numbers of entities? Hmm
Since phone number is a regular field, admins can expose the phone number field for registration forms. (/admin/config/people/accounts/form-display)
We need Rules before we can have Rules integration ;) They are still in alpha / unstable API. I am also tracking this for RNG.
Comment #40
almaudoh commentedThen we should have an issue for that I guess :)
Good point. Should we have that as part of this patch (or a new issue)? Or do we let site builders (who may not be aware that that feature exists) decide that for themselves?
Comment #41
dpiI go with let the site builders do it on their own. Its like 3 clicks for them.
We already make admins choose whether they want to create a phone number field on the (user) entity. So they should be able to make the conclusion that if its a regular field, they can expose it on the registration form.
At best, its a "how to" article on stack exchange or a Drupal tutorial/tips site.
Comment #42
dpiDone! #2712599: [meta] Rules integration
Comment #43
almaudoh commentedThanks!!
Comment #44
dpiWhere do we stand with this one? I want to be sure, since this PR removes 2500 lines.
Comment #45
dpiComment #49
dpioops, reintroduced old test from merge.
Comment #51
dpiComment #61
dpi