Laravel-modules: 404 Errors

[uncodable]

Hi,

v6 is throwing 404 errors on my production env, but localhost works fine.

Downgraded to v5.1 working again?

[nWidart]

Hi,

No idea why that would happen. You would have to debug it.

[kapil-gupta]

I was facing the same error. run php artisan module:v6:migrate after laravel upgrade

[uncodable]

I ran the migrate command, made no difference.

[uncodable]

Same docker environment, local and production, only difference is the I'm going through a proxy on AWS end. Any ideas @nWidart where to start the stack debug back to that?

[uncodable]

836 This could be related to this issue also, Vapor doesn't seem to be the issue.

This is just a standard docker containerised application also.

[ndhan93]

if you upgrade from 5.x, update your config also.
laravel-modules has new config for activator
I got same error before, update config and it's working, remember clean config cache

[50shashwat]

The same issue happens even if i use laravel 5.8

[uncodable]

Checked, nothing to do with the cache/configs. Clean install same issue.

[50shashwat]

Somehow the new installation works fine but it only happens when it is used on another machine with git. Now the same issue keeps happening on all the Laravel versions > 5.6

[uncodable]

@nWidart When a module is created is it cached against the url or anything like that?

[afanazmy]

You can check all module with php artisan module:list
If module disabled you can enable it with php artisan module:enable {module_name}

I think, in version 6 there is a bug when we clone our project because after running composer install all modules are disabled and we have to enable it first to use it.

[nWidart]

This isn't a bug, but a documented breaking change. You need to run php artisan module:v6:migrate

[vladamir]

Hi! I have the same issue, I have run php artisan module:v6:migrate many times, but anyway, with next deploy (composer install) I need to enable my modules again :(

[nWidart]

ah yes, you need to commit the file being generated: storage/app/modules_statuses.json, via the settings you can change its name and location if needed.

[vladamir]

wow, got it! Thank you!

[nWidart]

No problem 😄
I'll try to document this as I understand it can be confusing.

[rmicheldev]

Hi
Same problem (Laravel 6 running on apache).
Locally it works but on my AWS it return 404.

Solution:

php artisan module: list

+ ------- + ---------- + ------- + ---------------------- ------- +
| Nome Status Ordem | Caminho
+ ------- + ---------- + ------- + ---------------------- ------- +
| Admin Desativado | 0 / var / www / dark / Módulos / Admin |
| Blog | Desativado | 0 / var / www / dark / Módulos / Blog |
| Usuário Desativado | 0 / var / www / dark / Módulos / Usuário |
+ ------- + ---------- + ------- + ---------------------- ------- +

And so, I had run the command to enable the module again:

php artisan module: enable administrador

[uncodable]

Is it better we remove the way this file is generated and look through the modules to check if they’re enabled instead? Most people are going to have issues with this as storage is on most people’s gitignore

[nWidart]

@narwy No, the whole point of this feature is to have this file generated.

[nWidart]

The activator file has been moved to the base path, giving it better visibility and not ignored by default in 6.1

[uncodable]

Thanks @nWidart