shacker
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Files | Manage broken after upgradeNope – just temporarily renamed the plugins dir — the error persists. No one else is seeing this?
The installation was unpacked from tarball directly on the server, so no chance of an upload error (and everything else works fine).
Forum: Fixing WordPress
In reply to: Files | Manage broken after upgradeWell, this is interesting – decided to start totally fresh and removed the entire WP installation. Dropped all tables from the database (this is a brand new site so we had nothing to lose), and started from scratch with a virgin WP2 installation. Everything goes well, but the error above persisists. Same exact symptom.
Could this be an incompatibility with a plugin?
Forum: Fixing WordPress
In reply to: File Upload doesn’t work in spite of CHMOD 766> Reason # 2 is a spacialty that have many shared hosting webspaces: the owner of a directory is inspite of this not the webserver user. So it works only with 777.
This is incorrect informatin, and dangerous.
You can give the web server the rights it needs without making the dir world writable.
Let’s say your username is joe and the webserver runs as apache.The ownership on the dir should be: joe:apache (that is, it belongs to user joe and group apache)
The permissions on the dir should be 775, so that the user and the group can do everything, but world can only read and execute.
Don’t ever let anyone tell you something needs to be 777.
Common group names under which web servers run are:
www
nobody
apacheChances are high that yours runs under one of these.
Forum: Installing WordPress
In reply to: “Could not load any data from this location”For what it’s worth, the issue on this server was that Apache was compiled against a different version of MySQL than was installed. Upgrading MySQL and PHP, and recompiling Apache fixed the problem.
Forum: Installing WordPress
In reply to: “Could not load any data from this location”It won’t load in any browser. Again:
“Other browsers do nothing or throw similar errors, but in all cases, it’s not a page returned by the server, it’s a browser-side error.”