TwitterControl | Nette Framework Control for rendering tweets | Frontend Framework library

I managed to solve this by setting the Router context. I already loaded in the RequestStack to access the user's IP, so I used it to set the context of the Route and then the router worked as expected. I ran into problems trying to use the RequestStack in the constructor, so I ended up refactoring it so that it used the RequestStack as late as possible.

i think you forgot to copy your web.config connection string to that app.config.This might be the issue.

Edit:

i mean the project in which your DataContext class resides

I assume you are using the Route::post('twitterlogin','TwitterController@posttwitterlogin') route to perform your login operation - please ensure that you're logging the user in with Laravel's Auth correctly and redirecting the user to the appropriate route in the posttwitterlogin method

I feel you also may also be using a different table to store user data - in which case, kindly ensure that you have your auth.php config file setup appropriately

In case you're using a custom authentication mechanism for some reason, you'll need to replace $this->auth->guest() in your middleware with the appropriate alternative check for the user not being logged-in

For eg: if you're setting a Session variable called is_authenticated to true with \Session::put('is_authenticated', true) upon successfully logging in, you'll check for it with if(\Session::get('is_authenticated') === true) in your Middleware instead of relying on the Laravel Auth method if ($this->auth->guest())

The only real way reduce response time for the user here is to make the API calls asynchronously from the browser, rather than having your server make them.

Consider building your view so that when it loads it shows "loading feedback" to the user and then makes the API calls via AJAX with each section showing content as each API call completes.