1.7 Alpha SMS generic gateway - queer behaviour

I apologise for the number of screen shots here but it's the only way to document the problem - which is related to the Apply button and the To field.

Shot 1 - this is immediately after the edit screen opens - as you would expect it does not like the To addess because it has no phone and is thus generating just '@onewaysms.asia' as the To address.

Now we enter the phone number and press Apply again, and we get the screen below - it still does't like it because it has not noticed that the phone number has been entered:

Now we go and change the x in the To field to a y and press apply and it's happy

Now all we do is change the phone number and press Apply again - as you can see below, it's still happy but it has not noticed that the phone number has changed.

 

So our problem comes from two places:

  1. the initial screen has no phone number so if (as in this case) the phone number generates the To address, on initial opening, the status will always be 'invalid To address'
  2. changes in the phone number field are not noticed unless you change something in the top half of the screen

I suspect that the mimimum fix is to set the phone to say 12345678 when the edit screen opens. This will mean that the initial status check should be OK.

If its a 2 second job to make it notice changes in the phone number field when nothing else changes, that would also be worth doing.

Regards, Tim G

[and no I have not got this working yet - but the generic gateway is allowing me to set all that I need to]

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: 1.7 Alpha SMS generic gateway - queer behaviour

Fixed in revision 5345. If you change the Phone field, and press Apply, it will now update correctly.

You can workaround this in the meantime by pressing enter in the Phone field. This will force it to propagate its change to the webserver.

Thanks,

Tim

Syndicate content