Hot answers tagged apache
7
Survey said! Wolf Fence in Alaska.
The basic idea is that you divide your problem space in half by inserting a print "Hi, Mom!\n"; exit; (insert your favorite phrase) somewhere near the "middle" of your code. If you get the message, then the bug is beyond where you put the print, so move it farther along in the execution. If you don't get there, move the ...
5
The most common thing to try is a content caching plugin like W3 Total Cache or WP Super Cache. Both will cache entire pages to disk, and will allow the Apache web server to completely bypass PHP processing for many page views. With W3 Total Cache, you can also cache system objects and the results of database queries, as well as using a CDN (Content ...
5
Souljacker,
I would first take a look at your plugins. Star Ratings for Reviews hasn't been updated for over 3 years and looks like its real heavy on the db. I saw some raw sql with some INNER JOINS that look troublesome.
On the server side you should implement some object caching. APC is the defacto standard and will give you the best results.
Once ...
4
In short yes...
'External' Rewrite Rules
If in add_rewrite_rule the rule is isn't directed to index.php then the rule is treated as an 'external' rule (i.e. not to be processed by WordPress' internal handing of rewrites) and instead written to the .htaccess file. I.e. if:
add_rewrite_rule('^nutrition/([^/]*)/([^/]*)/?','somethingelse.php?p=12&food=$1 ...
4
Just to break cycle of "doesn't belong here".
WordPress basically has no specific requirements for web server itself (which doesn't even have to be Apache), aside from permalinks.
The message you are getting seems to be performance-related and may or may not be connected to you using WordPress. For starters check if your traffic had recently increased and ...
4
Number 1 is not wordPress, but PHP. $_GET['type'] is undefined. Use an isset( $_GET['type'] ) conditional.
Number 2 the error message tells you exactly what to do. Instead of calling:
add_custom_background();
...call:
add_theme_support( 'custom-background' );
Number 3 the error message tells you exactly what to do. Instead of calling:
...
4
Without looking at your box to see exactly what's going on, here are some potential avenues of slowness:
Potential Causes
Apache
Apache is usually configured in such a way that a single httpd process is always running in the background. When a request comes in over the wire, it spins up a new httpd process to handle the request. Once the request closes, ...
3
Many of the examples assume you're not the only person running stuff on the server, or that suPHP or some other utility is running to make PHP run as a user other than the web server.
With a basic Debian LAMP install, where PHP runs as the www-data user, it's safe and normal to set ownership of everything under the web server document root directory as ...
3
You're looking at the problem the wrong way. The error you're seeing isn't an error coming from WordPress, it's a PHP error.
Somehow, somewhere, something is limiting the memory limit to 96M, and it ain't WordPress that's doing it.
Here's the thing: WordPress can't actually limit the memory on most servers. I know that it attempts to increase the limit ...
3
This really isn't a Wordpress issue. That said, the key error is "open_basedir restriction in effect." If you're running your own VPS, you need to learn to configure it.
open_basedir restrictions keep scripts in one directory from being able to affect scripts in another directory, which is an important security feature. If one accounts gets hacked, ...
2
Take a look here: Performance tips for a large user base - it's a useful set of things to look at that go beyond just Apache.
When looking to optimise performance, it's pretty important to look at the entire infrastructure to see where you might have issues - for example one of of my sites I eventually traced an issue that initially looked like an Apache ...
2
Both servers are listening to the same port. You have Nginx set to listen to 80 and nothing is set for Apache unless it's in your ports.conf.
Your also proxy passing to Apache port 80 in your Nginx conf.
In the Nginx conf change
proxy_pass http://127.0.0.1:80;
to
proxy_pass http://127.0.0.1:9000;
change listen XXX.XXX.XXX.XXX:80; to listen 80;
In ...
2
Depending on your server configuration, you can change the setting for MaxClients in /usr/local/apache/conf/httpd.conf.
[edit: Since I've only been given a line or two about it myself from my server admin, here is a better explanation as to what MaxClient is...
ServerLimit controls the maximum
configured value for MaxClients.
Reducing MaxClients on ...
2
Anchor will setup apache or nginx for me - but which should I choose?!
Based on your concerns, I'd recommend Nginx -> Apache stack.
Please let me explain. By default, Nginx can only process static content, such as images, CSS and JS files. Nginx passes PHP requests to PHP-FPM or to other servers such as Apache. Nginx can still cache dynamic content ...
1
For now, this is unsolvable according to Mark Jaquith, as noted here.
Q: Does this support WordPress in multisite mode?
A: No. Not until
WordPress supports WordPress-in-a-subdirectory installation for
multisite. If you're a WordPress hacker who wants to help with that
feature, drop me a line
1
Not sure if this is exactly relevant, but Before You Create A Network: WordPress_Settings_Requirements says
Giving WordPress its own directory will not work in WordPress 3.0 with multisite enabled. If you wish to install WordPress in a folder AND have that folder name it will work. Domain mapping, however, will not work.
I'm not sure what AND have that ...
1
Generally speaking your apc.shm_size should be double your highest seen used amount. You want to try and prevent your cache full count from being higher than 0. You might want to also lower some of your ttls. I'm working with someone on AWS EC2 with 5 vhosts and we had to raise apc.shm_size to 512M to prevent 100% fragmentation. I also have better results ...
1
Ok, thanks to @Wyck, I found a sollution to what I wanted to do. I'll try to explain here. The problem was that I needed to change two values found under Dashboard -> Settings -> General Configuration. These values were "WordPress Address (URL)" and "Site Address (URL)" I changed them (I got a no-ip domain so I can test easier) and I managed to access my ...
1
You should be able to just add your port 8888 under general settings wordpress/site url, or directly in your config.php. In your case that would be http://localhost:8888 . I don't know how or what browseling is but a quick glance also shows they support ssh reverse tunnel proxy for localhost, which is another option.
1
After banging my head on this for a few days, I found a solution that works.
Just add the following to wp-config.php:
if ( isset( $_SERVER['HTTP_X_FORWARDED_HOST'] ) ) {
$_SERVER['HTTP_HOST'] = $_SERVER['HTTP_X_FORWARDED_HOST'];
}
This will force WordPress to use the requested domain, instead of the proxy domain.
1
The usual approach to optimising a Wordpress website is using a plugin like W3 Total Cache, but what a lot of people fail to realise and you've discovered is that such plugins have a slew of compatibility issues with other plugins as well as various hosts. The plugin W3 Total Cache does a good job at working with a whole heap of different server ...
1
The best option is to use a cache plugin. I also recommend W3 Total Cache, but before installing it, make sure you backup your database and files and update wordpress to the latest version.
Wordpress is causing the highest load on the database. The processor will have to work hard to retreive the data if there are many queries at the same time. Caching ...
1
The answer to this is rather complicated.
On a shared server (running more than one website), using an setuid process for PHP (via whatever means) provides extra intra-user security. If two people have access to a server, and their scripts run as them instead of as a single "apache" user, then somebody breaking into one site via the web only gains the privs ...
1
The short answer is to enable suPHP on your server, so that WordPress can run as its own user, rather than as apache.
Otto explains more here.
1
Remove the other .htaccess from the sub-directory and try putting this in the .htaccess in your root directory:
<Directory /scripts>
Order allow,deny
<Files hello.php>
Deny from all
</Files>
</Directory>
1
When you register your taxonomy you can create the rewrite rule for the slug
register_taxonomy('investment_country',array('investment'), array( 'hierarchical' => true, 'labels' => $labels, 'show_ui' => true, ...
1
Basically you have three parameters here:
Current server time
Schedule start time
Schedule end time
Then your task boils down to using custom field parameters in query to request posts with two conditions:
schedule start hour is smaller than current hour
schedule end hour is larger than current hour
1
If you are still looking for a solution, your nginx configuration should look like this in order to achieve what you described...
server {
listen 80;
server_name yourdomain.com
root /path/to/yourdomain.com;
index index.php index.html;
location / {
# directives to handle static site
}
location /sub {
# directives to handle WordPress
...
1
Easiest way: Use mod_suphp instead of mod_php. This should just be a matter of using whatever ubuntu's package manager is to remove mod_php and install mod_suphp instead.
mod_suphp is a slightly modified version of mod_php. It does the same thing, but it sets the user of the apache process to be the same as the owner of the PHP files when the PHP executes. ...
1
Are you sure /wp-includes/load.php made it to the server? If you were installing manually, there's a chance it got lost during the transfer. Happens to me occasionally using FileZilla.
The error messages are basically telling you that the server can't find the file, so make sure the file is there.
Only top voted, non community-wiki answers of a minimum length are eligible
