Amahi 12 Testing with platform 11.7.29
We have updated the f33 repo of Amahi with the latest platform release that should work like Amahi 11.
However, there are a few things that, while probably minor, should be addressed. Let's collect them in this ticket.
Known issues (please add as necessary):
- editing properties of shares (e.g. writeable) appears to work but not when done repeatedly (after refreshing one can make one more change)
- the beach theme works, but the vertical tabs are shrunk
- the news from the blog are not working
installing apps has been tested only sparingly on a handful of apps.
- Status changed from New to Feedback
- Assignee set to cpg
- When installing apps, the amahi-app-installer.log displays:
Rails Error: Unable to access log file. Please ensure that /var/hda/platform/html/log/production.log exists and is writable (ie, make it writable for user and group: chmod 0664 /var/hda/platform/html/log/production.log). The log level has been raised to WARN and the output directed to STDERR until the problem is fixed.
I was able to correct it by changing permissions to 644 and apache:apache. Files was root:root
- Also in he amahai-app-installer.log it displays:
You have selected Sha512 as your authlogic crypto provider. This algorithm does not have any practical known attacks against it. However, there are better choices. Authlogic has no plans yet to deprecate this crypto provider. However, we recommend transitioning to a more secure, adaptive hashing algorithm, like scrypt. Adaptive algorithms are designed to slow down brute force attacks, and over time the iteration count can be increased to make it slower, so it remains resistant to brute-force search attacks even in the face of increasing computation power. Use the transition_from_crypto_providers option to make the transition painless for your users.
- On main screen, when not using DNS the banner displays an odd looking x on the left side of the screen.
More to follow once I have time to test thoroughly. App installs appear to work fine so far.
I believe I have fixed 1).
About 2), it's innocuous, though I may just go ahead and try to do the transition to the recommended crypto (I have done it before and it "should be easy and transparent" ... famous last words ...)
About 3, I see it. It looks like it's meant to be for dismissing the alert, however, it appears that the dismissal is not working. Prolly some JS/JQ missing. It has a funky look too. I will see if I can get to it quickly.
The apps working seemingly right is great to hear, as that area was a little tricky.
Also available in: Atom