Daniel Matthews
Daniel Matthews
@cris1198 Can you confirm whether or not updating `app.frontend.api_base_url` fixed your issue?
> I too have this problem, and modifing the app.frontend.api_base_url config parameter made no difference. @ns0r If you open up the developer console on your CALDERA login page and attempt...
> I too have this problem, and modifing the app.frontend.api_base_url config parameter made no difference. @ns0r Did you modify the configuration file while CALDERA was still running? If so, any...
> I was able to fix my problem by changing the VITE_CALDERA_URL from http://0.0.0.0:8888 to http://myipaddress:8888 in the /plugins/magma/.env file, and doing a --fresh --build. This fixed the login problem....
just for my awareness, what issue is this fixing? The current atomic tests seem to work for me locally
@jbaptperez Makes sense, good catch!
@elegantmoose approved and ready for merge
Here's an idea that wouldn't require refactoring: - Have a setting specific to the atomic plugin that enables/disables legacy IDs. - If enabled (default setting), the atomic plugin will generate...
Alright I have an alternative idea based on @leba-atr 's suggestion that will require some adjustments to core code and ability format, but will actually provide users with more flexibility...
As much as I'd like to introduce a secondary ID(s) field, doing so would require quite significant updates to the core code in order to accommodate looking up and referencing...