| 1 | | "the most prominent ones" - are there any others in WP core at all? I can't think of any. If there's a separate cron check, then for 99.9% + of users, they're being untroubled unnecessarily. Rather than tweaking the wording, I'd suggesting having this check off by default, and providing a filter so that plugins that need loopback to work can turn the check back on. Then "features relying on them are not currently working as expected" would be known to actually mean "actual features" rather than "features you're not using". As-is, it's most useful function would be to strong-arm hosting companies to not prevent loopback. If that's the intended purpose, I wouldn't personally object. But if that's not the intended purpose, then I don't think it currently really has one. |
| | 1 | "the most prominent ones" - are there any others in WP core at all? I can't think of any. If there's a separate cron check, then for 99.9% + of users, they're being untroubled unnecessarily; they're going to believe their site lacks health, when it doesn't. |
| | 2 | |
| | 3 | Rather than tweaking the wording, I'd suggesting having this check off by default, and providing a default-false filter so that plugins that need loopback to work can turn the check back on easily (rather than re-inventing the wheel themselves). Then "features relying on them are not currently working as expected" would be known to actually mean "actual features" rather than "features you're not using". As-is, it's most useful function would be to strong-arm hosting companies to not prevent loopback. If that's the intended purpose, I wouldn't personally object. But if that's not the intended purpose, then I don't think it currently really has one. |