Skip to content
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

Site health improvements #254

Closed
markkap opened this issue May 6, 2019 · 1 comment
Closed

Site health improvements #254

markkap opened this issue May 6, 2019 · 1 comment
Labels
Milestone

Comments

@markkap
Copy link

@markkap markkap commented May 6, 2019

List of things that need to be done

  • remove/improve php check. It is hard to say what is an acceptable PHP version since some linux distributions are very slow in updating it. The only valid error indication that can be given here is that the PHP version is less then the minimal one, but if it is so, the code is not likely to work at all...
  • Check connectivity to calmpress.org
  • User count is worthless info.
  • Media handling should probably focus on the ability to add new images, not about techno blabla that says very little even to me.
  • .htaccess rules needs to be worded differently to be more explicit that there are (no) rules added "by hand" to the file. It will be nice to test if the file is even being used.
  • "WordPress constants" some of those being displayed do nothing in calmPress
  • "Filesystem Permission" the current wording makes it sound like those directories need to be writable while some of them should not. Either need some different wording or show just what needs to be writable.

For the status tab need to make sure all tests make sence, and probably remove their "categoring". Tests should be either mandatory, highly recommended, or optional. Need to remove the test, or invert the logic, of the auto update test.

@markkap markkap added the UX label May 6, 2019
@markkap markkap added this to the 1.0.0 milestone May 6, 2019
markkap added a commit that referenced this issue May 11, 2019
…ing what seems like random numbers to the user #254
markkap added a commit that referenced this issue May 11, 2019
markkap added a commit that referenced this issue May 11, 2019
…ld not run into the issue in the first place, and users on shared hosting has very little to do about it. As long as calmPress keeps working in that setup there is no point to stress the user. #254
markkap added a commit that referenced this issue May 11, 2019
…tical mismatch the user should not be able to access the site at all #254
markkap added a commit that referenced this issue Aug 30, 2021
…nyting else unless it is local enviroment which is hard to use https with #254
markkap added a commit that referenced this issue Aug 30, 2021
…use a plugin is not up to date do not mean it is bad in any way. Instead check for inactive plugins #254
markkap added a commit that referenced this issue Aug 30, 2021
…se a theme is not up to date do not mean it is bad in any way. Instead check for inactive themes #254
markkap added a commit that referenced this issue Aug 31, 2021
markkap added a commit that referenced this issue Aug 31, 2021
…st useless way to do it. The fact that site health works at all is a more usefull test #254
markkap added a commit that referenced this issue Aug 31, 2021
…e set. The connectivity test to wordpress.org is a much better test for being able to send messages and get replies #254
markkap added a commit that referenced this issue Aug 31, 2021
markkap added a commit that referenced this issue Aug 31, 2021
@markkap
Copy link
Author

@markkap markkap commented Aug 31, 2021

There is probably more that can be done here, but this should be enough for version 1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant