1.1 is the current branch on Nova Press
@daveismyname I have update also the composer.json from the branches of https://github.com/nova-framework/app
Please be kind to check if everything is OK on packagist side for this app.
@daveismyname
HP@DESKTOP-7TPCTSP MINGW64 /c/xampp/htdocs/nova
$ php forge module:migrate
There are no commands defined in the "module" namespace.
Header always set Access-Control-Allow-Origin "*"
Header always set Access-Control-Allow-Headers "Origin, X-Requested-With, Content-Type, Access-Control-Allow-Origin"
Header always set Access-Control-Allow-Methods "PUT, GET, POST, DELETE, OPTIONS”
Hi, guys!
I solved the CORS issues on Nova 4.2 per route, in the following way:
// /app/Middleware/Cors.php
namespace App\Middleware;
use Closure;
class Cors
{
public function handle($request, Closure $next)
{
return call_user_func($next, $request)
->header('Access-Control-Allow-Origin', '*')
->header('Access-Control-Allow-Methods', 'GET, POST, PUT, DELETE, OPTIONS');
}
}// /app/Config/App.php
/**
* The Application's route Middleware.
*/
'routeMiddleware' => array(
'auth' => 'Nova\Auth\Middleware\Authenticate',
'guest' => 'App\Middleware\RedirectIfAuthenticated',
'throttle' => 'Nova\Routing\Middleware\ThrottleRequests',
'cors' => 'App\Middleware\Cors', // <--- Add this line
),// /app/Routes/Api.php
Route::get('cors-works-here', array('middleware' => 'cors', function ()
{
return 'CORS works here!';
}));The example route responds on /api/cors-works-here and I suggest to people to limit their CORS routes to API, because the WEB way on Nova is basically a true fort defending the app against CORS.
Everything there fights against CORS, from sessions to auth system.
// /app/Middleware/Cors.php
namespace App\Middleware;
use Closure;
class Cors
{
public function handle($request, Closure $next)
{
return call_user_func($next, $request)
->header('Access-Control-Allow-Origin', '*')
->header('Access-Control-Allow-Methods', 'GET, POST, PUT, DELETE, OPTIONS')
->header('Access-Control-Allow-Headers', 'X-Requested-With, Content-Type, X-Token-Auth, Authorization');
}
}@ZhaoLin1457 Hmm...
This thing is really nasty: ->header('Access-Control-Allow-Origin', '*')
Maybe it's good enough for tests, but on the wild I will prefer to enforce the acceptance of well known CORS origins, like in something similar with:
class Cors
{
protected $container;
public function __construct(Container $container)
{
$this->container = $container;
}
public function handle($request, Closure $next)
{
$config = $this->container['config'];
// Get the "Origin" header from Request.
$origin = $request->header('Origin', $url = $config->get('app.url'));
// Handle the middleware flow and retrieve the Response.
$response = $next($request);
// Retrieve all accepted CORS origins.
$origins = array_merge((array) $url, $config->get('cors.origins', array()));
if (! in_array($origin, $origins)) {
return $response;
}
return $response->header('Access-Control-Allow-Origin', $origin)
->header('Access-Control-Allow-Methods', 'GET, POST, PUT, DELETE, OPTIONS')
->header('Access-Control-Allow-Headers', 'X-Requested-With, Content-Type, X-Token-Auth, Authorization');
}
}There is supposed that the valid CORS origins are enumerated in an array from a config file app/Config/Cors.php
And regarding the API and Auth System, there's a way to use stateless authenticated requests via API: using the Token Guard.
In theory, you need a special API authentication endpoint, which returns a token on successful logins. Then this token should beused to authorize the following requests.
hey @DonWagner, hope your keeping well.
Did you install /app or /framework repo?
I’ve just installed from app using composer create-project nova-framework/framework novatemp that installed correctly I’ve then connected to a database and ran php forge seed that worked also did php forge db:seed and also tried php forge package:migrate and php forge package:seed all worked without issue
A new Q from the Dane...
Now I have searched and searched, but I have not been able to find an answer I could use. That is why I now ask in here.
How to easily create a list of users without the users mentioned in another table.
Eg: In my database I have the User table with a column called zip code. I also have a table called Cities with a list of zip codes.
Now I would like to make a list of the users from the User table, which does not have the zip codes that are in the Cities table.
How to do it easiest? Or smartest?
I’ve been re-reading this a few times I don’t quite get what you need as you can select all users where the zipcode is empty, but it sounds like that’s not what you need.
To select all users that does not have a zip code but is in the cities table? how does a user relate to the cities table?
Thanks Dave, i will try to explain in another way.
It's only a test setup, to learn from. So there is no logic why i'm using zip codes, that could be anything :laughing:
I have made a table with 100 users, all with a zip code (they don't have the same zip code):
id|name|zip_codeThen i have another table called Cities, where i'm adding some cities and there zip codes:
id|city|zip_code|I then have a list of all the users. Then every time a new city is added to the Cities tabel, the users from the same zip_code, as the newly added city, will be removed from the list.
I hope that made more sens :smil:
Thank you for your patience. I apologize for being poor at explaining.
I try like this:
I would like to make a list of users who come from zip codes that are not in the Cities table.
So the list will look like this:
Martin 8240
Otherwise 8210
Christian 8200
Niels 8000.Then I add Aarhus C | 8200 to theCities table and I add Aarhus V | 8210
Then the list will look like this:
Martin 8240
Niels 8000It's certainly simple, but I can't tell if you need to use whereNotIn. I can't really make it work