botman | Botman is here to speed up those witty responses on Facebook

From these lines in their github:

https://github.com/botman/botman/blob/79310f6e6464436aaa2d0522267b2ca00a07fda5/tests/BotManConversationTest.php#L79-L83

https://github.com/botman/botman/blob/4ec6e3f30d620cbcb73a0cf8e1dbf6b34e47f75d/src/Traits/HandlesConversations.php#L47

https://github.com/botman/botman/blob/203e7f5ef68473dd4d71ca7ee31275eae9a92745/src/BotMan.php#L238-L239

It must be like these:

I see your LDAP backend is setting token_num_uses. From this documentation and this discussion, having token_num_uses set to something non-zero will prevent the token from creating child tokens.

The reason it is broken for LDAP and working for AppRole is because the LDAP backend is applying the token_num_uses property, whereas I'm guessing the AppRole backend is not.

I assume that you use the Botman web widget to render the chat box.

You need three routes and three controller functions:

• One that will send back the page that contains the chatbot widget ("homepage" in the following example),
• One that will deal with the Botman logic and return the serialized answers of the bot("message" in the following example),
• One that will send back the chat frame ("chatframe" in the following example).

here is a basic example:

The error message is telling you that somewhere in the code is trying to serialize the object, that is turn it into a string representation. This is probably in the framework you're using, and what you are thinking of as a "global variable" is actually stored between requests in some form of session, e.g. in a file on disk.

Because of the way SimpleXML is implemented, it doesn't allow this operation. The simplest workaround is to instead store the XML by calling ->asXML(), and then re-parse it when you need it with simplexml_load_string().

You'll want to do that round trip as rarely as possible, so it will be worth understanding better about how the "global variables" are actually handled by the framework so you can try to do it once on each request.

This is a 5.7 to 5.8 upgrade issue, as you point out when the problem started. The signature of that method changed:

"The renderHttpException method signature of the Illuminate\Foundation\Exceptions\Handler class has changed. If you are overriding this method in your exception handler, you should update the method signature to match its parent:"

So, after finding some github code examples i have managed to work out the issue. It is to do with the way the botman framework is structured. To achive linked conversations you have to use a function from the botman framework called startConversation() to envoke this you need to reference bot which is from the extended base class Conversation. So you will need an entry point and then the conversation you want to link to like so: *note you will need the default entry point of run() for each conversation.

I quickly checked out the web widget on the botman github.

There is a simple link to the chat.css in the head of chat.html located in the src folder. This points to assets/css/chat.css, which you can edit freely and add a background-color to.

ReactPHP core team member here. There are a few options and things going on here.

First off then will never return the value from a promise, it will return a new promise so you can create a promise chain. As a result of that you do a new async operation in each then that takes in the result from the previous one.

Secondly done never returns result value and works pretty much like then but will throw any uncaught exceptions from the previous promise in the chain.

The thing with both then and done is that they are your resolution methods. A promise a merely represents the result of an operation that isn't done yet. It will call the callable you hand to then/done once the operation is ready and resolves the promise. So ultimately all your operations happen inside a callable one way or the other and in the broadest sense. (Which can also be a __invoke method on a class depending on how you set it up. And also why I'm so excited about short closures coming in PHP 7.4.)

You have two options here:

• Run all your operations inside callable's
• Use RecoilPHP

The former means a lot more mind mapping and learning how async works and how to wrap your mind around that. The latter makes it easier but requires you to run each path in a coroutine (callable with some cool magic).

Everything works fine right now, I overlook on a simple syntax issue... updated my code as below :