When upgrading some packages via the package management tool, the output window gave me some red error messages - usually about directories not be writable and such. However, the package upgrade did get to the end and when i ok’d that, the package reports it has now at the latest version.
Should I be worried about the messages?? Would it be better to uninstall and reinstall, having changed folder permissions?
I havn’t noticed anything not working as it should be, but the errors seem, well, maybe not that serious... after all, I didn’t get a message saying ’upgrade failed’ or anything - so what gives? Its a little unclear to me how much concern I should have about the errors.
Revo 2.0.8
PHP 5.2.11
Apache 2.2
-
MODX Staff
- 10,725 Posts
If the PHP process cannot write to the packages/ directory or the locations where the component installs it’s files (typically core/components/componentname/ and/or assets/components/componentname/) then the installation was not able to update the files on the filesystem. Though without the error messages, I cannot tell you anything more specific.
So I guess my point is: wouldn’t it be better if a broader message was also given, to the effect that ’Your package could not be successfully installed - please check and fix the output errors or your package may not function correctly’. If I can just press OK at the end of the output errors, and the messages go away, and I’m left with a package that says it is installed, then I’m likely to think that I don’t need to worry it.
Which brings up the issue - if the package can’t be installed successfully, for such an error, should it really be marked in the package manager as ’installed’?
This could be pretty misleading for not so technical types, who are trying to install/upgrade packages.
I’m not trying to b*tch here, just thinking what would make it a clearer UX.
What do you think? Has this happened to anyone else and do you think it is ambiguous?
