SMS Notify v1.0.3 is not sending messages when using it with beta.24. SMS Notify v1.0.3 is generating an error message when accessing Design / SMS Templates when using it with beta.24.1. The content field is required. (1/1) ValidationException The content field is required. in Validation.php line 59 at Template->throwValidationException() in ValidatingObserver.php line 56 at ValidatingObserver->performValidation(object(Template), ‘saving’) in ValidatingObserver.php line 20 at ValidatingObserver->saving(object(Template)) in Dispatcher.php line 389 at Dispatcher->Illuminate\Events{closure}(‘eloquent.saving: IgniterLabs\SmsNotify\Models\Template’, array(object(Template))) in Dispatcher.php line 218 at Dispatcher->dispatch(‘eloquent.saving: IgniterLabs\SmsNotify\Models\Template’, array(object(Template)), true) in Dispatcher.php line 191 at Dispatcher->until(‘eloquent.saving: IgniterLabs\SmsNotify\Models\Template’, object(Template)) in HasEvents.php line 189 at Model->fireModelEvent(‘saving’) in Model.php line 652 at Model->save(array(‘force’ => false)) in Model.php line 1087 at Model->saveInternal(array(‘force’ => false)) in Model.php line 1115 at Model->save() in Template.php line 115 at Template::syncAll() in Templates.php line 58 at Templates->index(‘index’) at call_user_func_array(array(object(Templates), ‘index’), array(‘index’)) in AdminController.php line 206 at AdminController->execPageAction(‘index’, array(‘index’)) in AdminController.php line 172 at AdminController->remap(‘index’, array()) in Controller.php line 111 at Controller->runAdmin(‘igniterlabs/smsnotify/templates’) in Controller.php line 54 at Controller->callAction(‘runAdmin’, array(‘slug’ => ‘igniterlabs/smsnotify/templates’)) in ControllerDispatcher.php line 45 at ControllerDispatcher->dispatch(object(Route), object(Controller), ‘runAdmin’) in Route.php line 219 at Route->runController() in Route.php line 176 at Route->run() in Router.php line 681 at Router->Illuminate\Routing{closure}(object(Request)) in Pipeline.php line 130 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in VerifyCsrfToken.php line 77 at VerifyCsrfToken->handle(object(Request), object(Closure)) in Pipeline.php line 171 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in CurrencyMiddleware.php line 33 at CurrencyMiddleware->handle(object(Request), object(Closure)) in Pipeline.php line 171 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in LogUserLastSeen.php line 26 at LogUserLastSeen->handle(object(Request), object(Closure)) in Pipeline.php line 171 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Localization.php line 40 at Localization->handle(object(Request), object(Closure)) in Pipeline.php line 171 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in SubstituteBindings.php line 41 at SubstituteBindings->handle(object(Request), object(Closure)) in Pipeline.php line 171 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in ShareErrorsFromSession.php line 49 at ShareErrorsFromSession->handle(object(Request), object(Closure)) in Pipeline.php line 171 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in StartSession.php line 56 at StartSession->handle(object(Request), object(Closure)) in Pipeline.php line 171 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in AddQueuedCookiesToResponse.php line 37 at AddQueuedCookiesToResponse->handle(object(Request), object(Closure)) in Pipeline.php line 171 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in EncryptCookies.php line 67 at EncryptCookies->handle(object(Request), object(Closure)) in Pipeline.php line 171 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 105 at Pipeline->then(object(Closure)) in Router.php line 683 at Router->runRouteWithinStack(object(Route), object(Request)) in Router.php line 658 at Router->runRoute(object(Request), object(Route)) in Router.php line 624 at Router->dispatchToRoute(object(Request)) in CoreRouter.php line 20 at CoreRouter->dispatch(object(Request)) in Kernel.php line 170 at Kernel->Illuminate\Foundation\Http{closure}(object(Request)) in Pipeline.php line 130 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in SaveSetting.php line 27 at SaveSetting->handle(object(Request), object(Closure)) in Pipeline.php line 171 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in TrustProxies.php line 57 at TrustProxies->handle(object(Request), object(Closure)) in Pipeline.php line 171 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in TransformsRequest.php line 21 at TransformsRequest->handle(object(Request), object(Closure)) in Pipeline.php line 171 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in ValidatePostSize.php line 27 at ValidatePostSize->handle(object(Request), object(Closure)) in Pipeline.php line 171 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in CheckForMaintenanceMode.php line 63 at CheckForMaintenanceMode->handle(object(Request), object(Closure)) in Pipeline.php line 171 at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 105 at Pipeline->then(object(Closure)) in Kernel.php line 145 at Kernel->sendRequestThroughRouter(object(Request)) in Kernel.php line 110 at Kernel->handle(object(Request)) in index.php line 53

Not sure why, but the v1.0.3 did not create the template records in the database in igniterlabs_smsnotify_templates. To resolve this I found a copy of my db export from 10/13, copied the text that had those records and pasted that into the SQL page of phpmyadmin, clicked Go and now those records exist. With these records and SMS Notify settings set correctly for Twilio I as able to use TI to send a test txt. However, TI still is not sending an SMS message when the status of an order changes. TI is sending email, but not SMS!

@ryanmitchell this is one of those instances where finding and fixing the fault would be incredibly useful to expedite resolution of issues I have. I’m going to message you on slack as well!

@roydeanjr Not sure how this relates to me?!

Relates to you as I saw on another thread your willingness to help setup a “fault finding” development environment. I’d like to set that up as well so I can help debug and offer fixes for extensions or core that is being developed.

Right now I am watching laracasts to learn about phpstorm.

Once you set up your dev environment I’m available to answer questions on Slack and to help give understanding as to what needs fixed on specific bugs and guiding through the pull request process. I’m not available to help with setting up dev environments 🙂

I’m available on Slack for help with setting up dev environments as long as it is not windows (haven’t used windows in years) 😉

SMS Notify not sending messages

roydeanjr

sampoyigi Are you using any GUI on linux or totally text based.

sampoyigi

roydeanjr I’ve tried using Ubuntu a few times but never stuck, I work mostly on mac. My guess is setting up a linux web server remotely wouldn’t be any different than setting up locally 🤷‍♂️

ryanmitchell

I use a dev Linux machine in the cloud - on an Amazon ec2 instance. I then checkout any Git branches I want to work on to it.

roydeanjr

I am trying to set up a local development capability on Windows. While downloading phpStorm I learned about Windows Sub-system for Linux (WSL). I am working toward getting that set up as it alleviates a workaround with running Linux in a VM; access to both Linux drive and Windows drives are seamless and bidirectional! I am watching a lot of videos about getting that set up. Many of the videos highlight VS Code, Docker, Linux (multiple flavors) and php, mysql, etc. So, once I get that going I will reach out and get help resolving any issues I encounter.

Thank you both for you willingness to help get help with this fantastic application!

Oh, and all this while still executing my day job gets really taxing! I am sure you understand that………

eadt

Hi @roydeanjr what exactly did you add the database to get the SMS templates to work? I tried adding a dummy row to the ti_igniterlabs_smsnotify_templates but I am still getting the content field error:

roydeanjr

I copied the records from an earlier version of the extension. On the github repository for smsnotify, look at the releases list and download one of the earlier versions and install that. Then, make sure and copy the records created by that version. Then update the extension and after updating, paste those records back into the db; can be done by exporting the whole database and importing just the sms templates table or by exporting the sms templates table and importing separately.

eadt

@roydeanjr Tried with all versions from v1.0.0 through v1.0.4 and still couldn’t get it to work. Do you mind sharing the SQL of that specific table? Thank you so much!

roydeanjr

SQL statement does not post correctly. I need to post another way. Try getting to the files here: https://ardeeent-my.sharepoint.com/:f:/g/personal/roydean_ardee_com1/EhihgzjVLBhHvw3onixfqPABPVRmkKF2X3qD7HagAvYLMA?e=HDJbHQ

The password is LetMeIn!

roydeanjr

@eadt did that help?

eadt

@roydeanjr Hi!! Thank you so much it did help and I can now access the Design SMS Templates menu. The only issue is that whenever I try to send a test SMS, I get this error:

"[HTTP 400] Unable to create record: Permission to send an SMS has not been enabled for the region indicated by the 'To' number: 8765456789."

Interestingly I don’t know where TI or Nexmo (Voyage, the API I am using) is getting that number from, because this is from the Test button located in the Design SMS Templates menu.

eadt

Okay nevermind, that number was somehow the dummy one that was put as my Location number.

Now I solved that, but I still get this error:

"“Cannot declare class Nexmo\Client, because the name is already in use” on line 159 of /home/customer/www/tastyigniter.fasty.me/public_html/extensions/igniterlabs/smsnotify/vendor/vonage/nexmo-bridge/src/Autoloader.php#0 [internal function]:"

eadt

@roydeanjr just changed to Twilio and it worked right away, thank you so much! Is it me or this SMS are expensive? 0.07 euros per SMS in Spain!

roydeanjr

In US cost is much less! .005-.0075/msg. Glad it is working for you!

BTW, you referenced test in an earlier comment. Is it working when you send a test message, but not working when a status is updated? Or is it working for both situations?

I am not getting any actual messages when the status is updated. The test works fine, but not the live status changes. The log on the automation shows success, but twilio does not show the phone number in its usage log. It does show the test message in the usage log, not the live status change message. @sampoyigi any ideas?

eadt

It is working only on test, but I believe this is because I have Twilio in Trial mode, is that possible?

Best,

roydeanjr

I don’t think so. You should still get msgs when statuses change and notify customer is enabled.