Tag Info

New answers tagged

0

It turns out that the problem wasn't WP per say but that mod_rewrite was being forbidden because of some server settings. I didn't realize it until the server guy sent over an error log that was filled with messages containing: Options FollowSymLinks or SymLinksIfOwnerMatch is off which implies that RewriteRule directive is forbidden To make it work, he ...


0

Most of the time this problem gets solved after flushing the permalinks. By that I mean, one just needs to hit 'Save changes' on 'Permalink settings' page on backend. However you said that you tried pretty permalinks and its not working. Under "Settings > General", please confirm that you have updated "WordPress Address (URL)" and "Site Address (URL)" to ...


1

You'll want to add these to your wp-config.php file: define( 'NOBLOGREDIRECT', '' ); define( 'WP_HOME', 'http://dev.domain.com' ); define( 'WP_SITEURL', 'http://dev.domain.com' ); So in its entirety, you'll have: $base = '/'; /** Multisite / Wordpress Network **/ define( 'WP_HOME', 'http://dev.domain.com' ); define( 'WP_SITEURL', ...


0

Just use a fake query parameter on the URL to get around those sort of bad restrictions in other pieces of code. http://example.com/feed/?fakefile=feed.xml


1

It is the way the .htaccess wordpress generatea instructs apache to work on the wordpress directories The relevant parts from the default .htaccess RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] The first line will cause the rewrite engine to bail out if there is a file with the same name as the ...


0

You can do it by moving the index.php to the root open up the index file change the following /** Loads the WordPress Environment and Template */ require( dirname( FILE ) . '/site/wp-blog-header.php' ) Replace site with the folder. Then in the admin under settings - general change the site URL and remove the folder www.website.co.uk/site will be ...


0

The only way I managed to get this to work was with the following in the .htaccess of the /site/ directory. RewriteBase \ RedirectMatch 301 ^/site/$ /$1 RedirectMatch 301 ^/site/(?!wp-admin/|wp-content/|wp-includes/)(.*)$ /$1 Whilst I am aware that RewriteRule ^site/ /$1 [R=301,NC,L] should have worked, and that RewriteRule ^site/(.*)$ /$1 [R=301,NC,L] ...


0

We had the same issue, only the default permalink working with Apache mod-rewrite enabled. Other sources had us tweaking the AllowOverride in the 'Directory "var/www/html"' from 'None' to 'All', this only resulted in a 500 error when anything but the default permalink was chosen. Sometimes giving it rest and coming back to it works -- after sleeping on it ...


0

If you want wordpress to behave nice when asked to serve content from example.com you need to configure it to know that. This is done automatically at the install process for the domain on which wordpress is installed on but can also be controlled from wp-config.php by setting values to the WP_HOME and WP_SITEURL constants. What you need to do is set the ...


0

There's sufficient info on the web about how to get .htaccess files working with Apache2. But specifically with Vagrant, you need to ensure the required settings are implemented in Apache on your guest machine. That might be obvious to everyone else, but I wasted an changing settings on my host and couldn't figure out why it wasn't working.


0

Turned out to be cacheing problem. WP Super Cache had been installed and deleted(uninstalled -perhaps incorrectly) but the advanced-cache.php file remained in wp-content.



Top 50 recent answers are included