Help for Aimeos

Reading https://github.com/aimeos/aimeos-laravel/issues/267 it seems I might have to add db-customer and do migration again or anew so the main Laravel database user table gets updated. That should avoid any group issues. And you really did hint at that in last post already. Thanks for that ...

We use a different database name / connection for Aimeos. Will have to ask what settings he used for the connection

'stmt' => config('database.default', 'mysql') === 'mysql' ? ["SET SESSION sort_buffer_size=2097144; SET NAMES 'utf8mb4'; SET SESSION sql_mode='ANSI'"] : [],


Guess he will need to ...

Team mate installing Aimeos / doing migrations is getting this error

Migrated: vendor/aimeos/aimeos-core/setup/Product.php (4.34ms)
Migrating: vendor/aimeos/ai-laravel/setup/CustomerClearPropertyKeyLaravel.php
Migrated: vendor/aimeos/ai-laravel/setup/CustomerClearPropertyKeyLaravel.php (14.06ms ...

I commented out db-customer in shop.php. Reason I removed db-customer data domain is that customer group will then also get loaded from main database and that caused other issues. I also used:
'roles' => ['admin', 'smart-administrator', 'administrator'], // user groups allowed to access the admin ...

Updated app/Providers/AuthServiceProvider.php with

...
Gate::define('admin', function (User $user) {
$role = data_get($user->role, 'name');
return in_array($role, [UserRole::EDITOR, UserRole::SUPER_ADMIN, 'admin']);
});
...


based on config/shop.php
```
...
'roles' => ['admin'], // user ...

I see. Thanks for the replies so far. Learning a lot. Now I have this for `config/shop.php`:

<?php

return [

'apc_enabled' => false, // enable for maximum performance if APCu is available
'apc_prefix' => 'laravel:', // prefix for caching config and translation in APCu
'num_formatter ...

I did not adjust db-customer in shop configuration . I have

<?php

return [

'apc_enabled' => false, // enable for maximum performance if APCu is available
'apc_prefix' => 'laravel:', // prefix for caching config and translation in APCu
'num_formatter' => 'Locale', // locale based number ...

I think the main issue is that the roles the user I am logged into the Laravel application do not work on Aimeos shop yet. Aimeos users are in another database and to Aimeos I am not logged in yet so that is why I get sent to login on trying the load the main shop. So I need to have at least an ...

I think the issue is the catch all. And that gets me back to earlier post wondering if I cannot just move the shop routes to web.php where I can add them all to the Dashboard routes with auth middleware check. Probably can and am trying but routes like

// Aimeos Routes
Route::prefix('store-admin ...

I now have a new admin route in `config/shop.php`:

'admin' => ['prefix' => 'store-admin', 'middleware' => ['web']]


and that route works as I can see listing all routes and filtering by store. Also adding some more with the same prefix:

php artisan route:list --path=store
....
GET|HEAD store ...