Tag Info

New answers tagged

0

Try replacing your line with this RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^([^\.]+)$ $1.php [NC,L]


0

Fixed this by changing permission on .htaccess to 444 from CPanel's file manager. For some reason my FTP client - even though logged in as the same CPanel user - could not make the change and the file would always revert back to 644. Cpanel had no such problem at all.


0

Normally WordPress does only affect rules between # BEGIN WordPress and # END WordPress, rules before or after this section should be left alone. Basic example from the codex htaccess entry: ### custom rules # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f ...


0

Placing the htaccess file in the wp-admin directory did not work for me so I went a different route and it seems to be working very well. Below is what I have in my main htaccess file: <files wp-login.php> # set up rule order order deny,allow # default deny deny from all allow from x.x.x.x allow from y.y.y.y allow from z.z.z.z </files> ...


2

The warning is regarding the following part of your code: __( ). In WP __ is actually a function for translation purposes. From a short look in the manual, we can see that the __() function usage is: <?php $translated_text = __( $text, $domain ); ?> And that the $text parameter is required. $text (string) (required) Text to translate. ...


0

Go to Settings -> Permalink and type in Custom structure. /blog/%postname%


1

You can not do that viw .htaccess because .htacces rules can not control how the permalinks are generated by WordPress. Instead, go to WordPress settings->permalink. Select custom structure and enter: blog/%category%/%postname%


0

broad lines of what you need to do change the .htaccess to let wordpress have priority over the directory handle wordpress url parsing You have two good options for handling the parsing hook on the init action and check if the url is of a file that exists in the directory do the file check in your theme's 404.php file before outputting any html. ...


1

Not using WordPress. With that directory in place, your web server doesn't even touch WordPress when it handles the request. I would: Move as much of your stuff as possible away from using that folder Rename the rewrite rule so that it's not just /episodes/ so that it doesn't clash You could try moving the folder and adding redirects, but at that level ...



Top 50 recent answers are included