-
-
Notifications
You must be signed in to change notification settings - Fork 700
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bot doesn't work with fbmessenger #1251
Comments
Originally lhc bot is not supported by fb messenger just :)
In the future a I’ll add support for lhc bot, but it’s not supported at the
moment :)
On Wed, 15 Aug 2018 at 21:58, FlavioSousa1982 ***@***.***> wrote:
Hello, good afternoon.
I updated version for extension fbmessenger, and i can receive message by
Fbmessenger in my LHC, and can send message (human) to fbmessenger,
correctly.
But, when actived option for bot (in settings|departament|bot
configuration and Modules|Facebook chat|Facebook Pages|Bot disable:False)
the message by bot, is not received in Facebook. Only, i see the answer in
chat for LHC.
The aplication was not been submited in facebook yet. In the above tests,
the option 'Application was verified by facebook' = True. And when updated
to False, the message wrote by human operator, dont't is received by
fbmessenger.
PS.
I had a problem during the activation of the fbmessenger ( Unknown column
'lhc_fbmessenger_page.bot_disabled' ), but, fixed by creating
"bot_disabled" for both tables. Could this bug be the cause?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1251>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABF85ankmDsYuWu_F2a6qnHUQeUlo4G-ks5uRG84gaJpZM4V-oEM>
.
--
Sincerely,
Remigijus Kiminas
|
Ok, thank's Remdex. Then the option for fbmessenger aplicattion 'bot messenger' in developer facebook, will not aprove, ok? Thank you for your attention. Flávio Sousa. |
Yes, I’ll approve. Yes in fb messenger just disable not :)
On Wed, 15 Aug 2018 at 22:33, FlavioSousa1982 ***@***.***> wrote:
Ok, thank's Remdex.
Then the option for fbmessenger aplicattion 'bot messenger' in developer
facebook, will not aprove, ok?
You have prevision for this resource (fbmessenger <> bot lhc) ? There is
also a forecast for whatsapp api (https://www.whatsapp.com/business/api) ?
Please aprove my skype (flavio.zenga), but we are interested in
partnerships in Brazil.
Thank you for your attention.
Flávio Sousa.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1251 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABF85elYnpObxqdxGyGQg7sGVatAIyB8ks5uRHd5gaJpZM4V-oEM>
.
--
Sincerely,
Remigijus Kiminas
|
Complementing, the bot LHC supported on the Telegram ? |
Also not at the moment. Like structure is similar to fb messenges, just
would need transformer and I’m just to busy for free stuff so do what I can
:)
On Wed, 15 Aug 2018 at 22:44, FlavioSousa1982 ***@***.***> wrote:
Complementing, the bot LHC supported on the Telegram ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1251 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABF85S9PKcRULyVuZj_Kt9jFZMm6jWWtks5uRHotgaJpZM4V-oEM>
.
--
Sincerely,
Remigijus Kiminas
|
Hello, good afternoon.
I updated version for extension fbmessenger, and i can receive message by Fbmessenger in my LHC, and can send message (human) to fbmessenger, correctly.
But, when actived option for bot (in settings|departament|bot configuration and Modules|Facebook chat|Facebook Pages|Bot disable:False) the message by bot, is not received in Facebook. Only, i see the answer in chat for LHC.
The aplication was not been submited in facebook yet. In the above tests, the option 'Application was verified by facebook' = True. And when updated to False, the message wrote by human operator, dont't is received by fbmessenger.
PS.
I had a problem during the activation of the fbmessenger ( Unknown column 'lhc_fbmessenger_page.bot_disabled' ), but, fixed by creating "bot_disabled" for both tables. Could this bug be the cause?
The text was updated successfully, but these errors were encountered: