ejm

I think you may be mistaken. My colleague was unable to access webmail (he kept getting a message that his password and email were invalid) until I changed Deny from all to Require all denied in the .htaccess file located in the wpcf7_uploads folder. As soon as this was changed, he was finally able to access his email via webmail.

resources:

• https://support.cpanel.net/hc/en-us/articles/360051768554-Troubleshooting-the-client-denied-by-server-configuration-error-
• https://linux.101hacks.com/unix/client-denied-by-server-configuration/

Therefore, please remove the ancient Apache directive. There is strong evidence that the “backwards compatibility” is causing cPanel’s webmail operation to break.

Thank you.

One thing that is important, as you mention security, is that we only officially support the latest major release (that would be version 5.5 at this point) [-Marius]

If there was a security fix in a major release, it would be sent out in a minor for all the other versions (back to 3.7), but that didn’t happen. […]
There’s no way for all of our tests to find the problems […] there’s no way to judge that it’s bug-free unless it’s released.
[-Joy]

In that case, it would be helpful to include a note on the major release that it does NOT contain security fixes. Not everyone is able (or willing) to act as guinea pigs to deal with the inevitable bugs of yet another brand new version.

The WP security plugin I have keeps reporting that it is essential to update to the latest version. I understand that I can (probably) safely ignore that report, and wait for the 5.5.1 fix. But how many less capable WP users know it’s safe to wait?

Again. If it ain’t broke….

Suggestion for all WP developers: Please make it very clear on the announcement of the major release, state the fact that updating to the latest Jazz icon is not required for security reasons and is simply a swishy new design.

Thank you for your reply, Marius;

If this is the case, then it would be a good idea to state something along the lines of “as always, this release includes security updates”.

However, it has been my experience that with the annual scheduled regular releases, there are almost invariably glaring errors that become apparent within a few days. Is it possible that the releases are done prematurely, simply because there is a perception that they must appear like clockwork?

I do appreciate that people have been working hard to improve things. However, judging from content of the 5.5 threads in the forums, it seems that all is not entirely rosy with the 5.5 release dedicated to Billy Ekstine.

Therefore, next August, it would be a pleasant surprise to see a notice stating with regret that the much anticipated annual release dedicated to another Jazz legend has had to be postponed because it’s not quite ready for the public. ie: don’t release something new simply because the calendar tells you it’s on the schedule.

E Morris

Thank you, Jarret.

Yes, I did mean a bicycle ride.

The bike ride was good, but I still don’t understand why   is still giving me grief either. I’ll keep picking away at it. I bet it’s something as simple as a misplaced semi-colon! (I know what you mean about how easy it is to miss those. I’ve learned from experience to check for their absence whenever I see an error message saying something like unexpected }….)