Change

Thanks for the update!

If you do add options to disable your public CSS, please consider making the inline CSS optional as well. These features are great for new users without development experience, but for professional developers we want our own CSS, and we have to reset the styles using !important. With the public file, the amount of CSS in the public file requires a large number of resets in our theme which will break every time you edit your CSS file.

We might be able to remove the CSS file with a filter.

Sounds great! When you switch it to a span, please do set tabindex=0 on the element so that it’s selectable by the keyboard.

https://developer.mozilla.org/en-US/docs/Web/Accessibility/Keyboard-navigable_JavaScript_widgets

https://dequeuniversity.com/rules/axe/3.2/tabindex

That was the only accessibility issue we found so far.

Thanks for the update Hector! I’ll give the latest dev version a try.

Steve,

That’s great news! I can’t wait to test it.

The nesting is 3 or 4 levels deep. And, everything works as expected on Pantheon. So, I expect this is a resource limit issue with SiteGround. I’ve opened a ticket there.

wrong thread.

I gave this a try and still have the white screen of death on the admin screen.

I also noticed when opening this plugin to preform this edit that the plugin author is in violation of the GPL. The plugin shouldn’t have been accepted by www.ads-software.com:

Copyright 2008 ICTA / Mr Pete (email : WP-Tuner at ICTA dot net)

I have not yet chosen a license for this software.

For now, if you have received specific written permission from me
to use this software, then you are free to use it personally according
to the terms I gave you. You may not redistribute it to others.

I too have this problem on several servers. I am the system administrator and I have root access.

Why are there no guides for system administrators on how to setup web servers to make WordPress run smoothly?

I had trouble with automatic upgrades for a year, until I did a chown -R www-data:www-data /var/www/mysite/html

That gave wordpress permission to do the upgrade, but it broke FTP access for the mysite account because it is no longer the owner of the files.

This chown fix did not resolve the “cannot delete” plugins. Installing plugins automatically works, but upgrading fails.

It would be nice to have a how to guide for setting up apache for wordpress to work, and it would be nicer if WordPress would just Work, or fail gracefully with useful error messages.

The final problem was the autoupdate plugin was installed on the blog, and it was conflicting with the build in auto update. It’s a shame there is no check for the plugin. It should have simply thrown an error message instead of failing so mysterously.

Long story short: To set up wordpress auto updates on your own dedicated server:

1. chown -R www-data:www-data /var/www/html or (chown -R apache:apache /var/www/html)
2. If you receive an unpacking error, disable any and all plugins and try again.

If WordPress asks you for FTP information, it has failed a permissions test and should State that clearly. It however, misleads users by asking for ftp information. If you get the FTP login screen, check permissions and try again until it updates without asking for a login.

Hopefully this feature will become more user friendly in future versions.

I read that WordPress is not supposed to ask me for FTP information. So, I typed chown -R apache:apache /var/www/html/, and it still fails to update at the same point. However, I no longer have to provide FTP information!

I did chown apache:apache /var/www/html on another development server I own and that fixed the auto updates on that server. But, the production server still fails at the unpacking step. So, any clues as to why unpacking might fail? It would be nice if this feature had better error checking and better error messages.

Are there any guides for server administrators and hosting companies to get WordPress auto update feature to work? It obviously fails miserably in a default install of centos or redhat… Surely there must be some documentation on how to configure your server to make this happen?