New answers tagged

0

Hashes are used in web addresses to navigate to anchors on a specific position within a page. The part after the # symbol is never sent to the server. That's probably why WordPress doesn't allow hashes in URLs. If it did, you wouldn't be able to access the page anyway.


0

Based on the info in the comments, here's my preliminary answer, hopefully helping to debug the issue rather than a fix as I can't see enough info for that — not the OP's fault, rewrite debugging is just a pain. The rewrite rule is obviously passing something to WP but WP isn't happy with it. What I'd do is add some debugging code to your theme's 404.php ...


0

First, check for get_current_user_id. Then create a log of visits by adding information to a user's metadata with update_user_meta & get_user_meta. On every page hit that you care about you can run a function to determine rate/limit of usage per user. If they break the rules, you can redirect to a page that doesn't contain that logic with wp_redirect.


0

I figured out my own answer, so am posting it here so if someone else runs into the same problem, they can see what I did. The issue for me was that the base Wordpress redirect code: # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{...


2

The solution to restrict access to author's archives with .htaccess rule does pretty decent job. However, not everyone can edit or have access to .htaccess, especially on shared hosting accounts. The code below require PHP version 5.3+. Here is the solution which deals with the problem on WordPress level. Put this code in your theme's function.php file: &...


0

Hey see the following link. It has information about redirecting from one site to another : Redirecting Your Site With .htaccess


2

It was a server missconfiguration in httpd.conf: <Directory /> AllowOverride None </Directory> had to be changed in AllowOverride All. I should have realized this sooner, but it eluded me since I thought the override was working on the main installation, but it wasn't. I didn't notice it, because it was a one-page website. Once I turned ...


0

What's in your Apache logs? Maybe more info about the error. Set a 755 permission on the the public_html directory Who's your hosting provider? The issue might be permissions that you, as a user, cannot change yourself (contact hosting support).


-1

NO NEED TO HIDE! You will waste energy. it has no secruity. Read this - https://goo.gl/Pkq8Kn


-2

You could try this: RewriteCond %{REQUEST_URI} !^/wp-admin RewriteCond %{REQUEST_URI} !^/wp-login\.php(.*)$ RewriteRule ^blog/(.*)$ /news/$1 [R=301,NC,L]


0

Try this: <IfModule mod_rewrite.c> RewriteCond %{HTTP_HOST} ^www\.mydomain\.com [NC] RewriteRule ^(.*)$ http://mydomain/.cl/c/news/.com/$1 [L,R=301] </IfModule>


0

Try to edit wp-config.php and add this line : define('WP_HOME', 'http://your-domain.com/news');


0

When I create a .htaccess in my root directory to redirect a page in the root to a page in the wordpress directory then it changes the .htaccess of the wordpress. So this is what I have so far. I can fix the 500 by eliminating my .htaccess and rebuilding the .htaccess of my wordpress.


0

Here's the trace results. http://coinauctionshelp.com/United_States_Coin_Mintages_Price_Guides.html HTTP/1.1 500 Internal Server Error Date: Fri, 01 Jul 2016 22:24:27 GMT Server: Apache Last-Modified: Mon, 25 Apr 2016 21:39:43 GMT ETag: "38150-117-5315603b9a5c0" Accept-Ranges: bytes Content-Length: 279 Vary: Accept-Encoding Content-Type: text/html ...


0

I use this bash command to reset WordPress file permissions quickly and easily, just navigate to your root WP folder and run both: directories find . -type d -exec chmod 755 {} \; files find . -type f -exec chmod 644 {} \;



Top 50 recent answers are included