Thanks to @jacob peattie for helping me to figure this out. The issue is that I had WP_CONTENT_URL set incorrectly. Removing it fixed the issue. I could have added /wp-content to the url and it would’ve solved the issue as well. To explain why this caused in issue, I turned to the docs. This page … Read more
The best way to deal with issues like this is referring to the manual. http://httpd.apache.org/docs/1.3/mod/mod_expires.html#expiresactive Syntax: ExpiresActive On|Off Context: server config, virtual host, directory, .htaccess Override: Indexes Status: Extension Module: mod_expires Look at the Context and Override syntax rules. It’s OK to use ExpiresActive in an .htaccess file aslong as you AllowOverride Indexes
You can adapt the site url which is stored in the database based on what domain you are viewing the site from. Add the following to wp-config.php: define( ‘WP_HOME’, ‘http://’ . $_SERVER[‘HTTP_HOST’] . ‘/yourwebsitename’ ); define( ‘WP_SITEURL’, WP_HOME ); If you use a subdirectory install (ie: you view the site from http://192.168.0.2/yourwebstename but the WordPress … Read more
Codex has an article on Changing The Site URL, you can edit values in database or override them in config. To have your site work from root you can either relocate WP there altogether or configure it to support root of the site, while still residing in subdirectory. See Giving WordPress Its Own Directory on … Read more
Judging from other threads, here are the two most common causes of this problem on freshly built servers: .htaccess override is disabled by apache2.conf Apache mod_rewrite module isn’t enabled. In the file /etc/apache2/apache2.conf: <Directory /var/www/> AllowOverride All </Directory> “AllowOverride” is the switch that tells Apache whether to listen to .htaccess files or not. WordPress relies … Read more
As far I understand, .htaccess rewrite rules are executed before the request is proccesed by WordPress, or even by PHP engine, so you can not know if a URL will trigger a 404 error in .htaccess, you can not check if a given path will trigger a 404 at that level. You need to do … Read more
Apache only runs the index.php of WordPress, and serves static files (images, css, js etc). WP does all the rest, including parsing the request to find out what content to show the user. Apache does not (and needs not) know that there is communication with a data base in PHP, and doesn’t interact with that … Read more
So I’m not sure why that RewriteRule returned a 404 error for you, because I’ve tested it and it did work as expected — if permalinks are actually enabled, you would be redirected to the actual post permalink. And here’s the content of my .htaccess file: RewriteEngine On RewriteRule ^go/(\d+)$ /?p=$1 [R=302,L] # BEGIN WordPress … Read more
You might have edited your .htaccess file in Windows notepad or text editor. If you did use Windows text editor then it must have added some special chars in .htaccess file and that will lead to 500 internal server error. Never edit in Windows text editor. Use notepad++ for editing .htaccess and .htpasswd files. second … Read more
Even though the 000-default.conf file had… <VirtualHost *:80> ServerAdmin webmaster@localhost DocumentRoot /var/www/html <Directory /var/www/html/> Options FollowSymLinks AllowOverride All Require all granted </Directory> ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined </VirtualHost> I had to place… <Directory /var/www/html/> Options FollowSymLinks AllowOverride All Require all granted </Directory> Into the apache2.conf And use the sudo service apache2 restart command.