-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot find API Properties #185
Comments
Was this a clean install from scratch??? |
@olliefreeman - yes, completely clean install on my laptop. Jaimie had the same problem yesterday, but seems to have fixed itself when she updated to the latest release. I went straight for the latest release. |
Odd |
Can you do |
See if that fixes it |
|
Just cleaning up and trying again |
Do you have the .env file ?? That is loaded into docker to define those properties |
Another fresh install. Yes, got the .env file. Not getting the error message about |
K….if you restart the instance now using the down then up command does that resolve it |
No :( |
Can you check the shared_volumes/logs/maurodatamapper/Mauro-data-mapper/mauro-data-mapper.log you’ll need to be root user….see if there’s any errors as to why the AP didn’t save |
This def isn’t an issue on existing instances as Ouh updated fine and I accessed AP to activate the oic plugin |
Not that I can see |
Odd….I genuinely don’t have a clue without playing with it…sorry |
No worries... you're off... I'll keep hunting. |
The database table of api properties is definitely empty after start-up. This isn't the case with MAB |
@aaronforshaw - as mentioned earlier - just wondering if there's anything you might be able to spot, since you were in that bit of the code recently. But as I said, doesn't seem to be replicable on M-A-B on a fresh database. |
Keeping notes after feedback from Aaron... the code appears to fail silently if defaults.properties is not found. I can see it in the mdm-core.jar file for version 4.11.0 - same place, same file size as in 4.10.0 and 4.5.0. |
I can confirm that it's an issue with the asset pipeline not being able to load the defaults.properties file. Going to revert back to the old way of loading it to see if that improves things. Once fixed, the error handling / logging needs imrpoving so that if the file is not found, an error is written to the logs |
Don't generate an empty asset manifest file for mdm-plugin-profile (Solves #185)
On first install, I get the following exception:
The text was updated successfully, but these errors were encountered: