Your external rule doesn’t work because you’re using a format that only works for internal rules- $matches[1] is essentially nonsense in the context of an .htaccess file. Using the $matches array will only work when rules are parsed by PHP, external rules need to use the standard $1 instead of $matches[1]. Any rule that doesn’t … Read more
In the DNS we have an A record for www pointing to the ip address. You will also need an A record for the domain apex pointing to the same IP address. Or, preferably, an A record for the domain apex pointing to the IP address and a CNAME record for the www subdomain pointing … Read more
https://xxxx.com/informe-calculadora/1/[email protected]&id=610 Redirect 301 /wp-content/plugins/custom-plugin/public/partials/informe.php /informe-calculadora/$1 The $1 “backreference” at the end of the target URL is in error (the Redirect directive does not support regex in which backreferences can be captured). This will likely be seen as literal text, which would explain the erroneous 1 at the end of the target URL (the $ is … Read more
if you are trying to get http://www.myblog.com/currentpage/1 http://www.myblog.com/currentpage/2 then your function should be add_action(‘generate_rewrite_rules’, ‘currentpage_rewrite_rule_222’); function currentpage_rewrite_rule_222($wp_rewrite){ $newrules = array(); $new_rules[‘currentpage/(\d*)$’] = ‘index.php?currentpage=$matches[1]’; $wp_rewrite->rules = $new_rules + $wp_rewrite->rules; } and just keep your query_vars function the way it is. add_filter(‘query_vars’, ‘wpa3537_query_vars’); function wpa3537_query_vars($query_vars) { $query_vars[] = ‘currentpage’; return $query_vars; }
Thanks to @rofflox and @toscho for giving me the link. web.config file was not created as i was working on localhost as WAMP i.e Apache and it required when i shifted to production as it was running IIS. So i created a blank web.config file and added the following content. <rewrite> <rules> <rule name=”Main Rule” … Read more
a colleague fixed it using parse_request. similar to this one: http://willnorris.com/2009/06/wordpress-plugin-pet-peeve-2-direct-calls-to-plugin-files
The redirect has to be a 301, not an internal request. Otherwise WordPress will search dor a page named blog. And you don’t need mod_rewrite. # Apache 1.3 needs a complete URL RedirectMatch Permanent ^/blog$ http://example.com/ # Apache 2.x needs just the path RedirectMatch Permanent ^/blog$ /
Sigh had to add this to the httpd.conf file on the webserver: <Directory /var/www/> Options FollowSymLinks AllowOverride All Order allow,deny Allow from all </Directory> First time I have to add it manually, oh well it works fine now 🙂
Sooo the problem was my brackets around the content in the condition I think. I’m still not so hot on these things, but I use these rules and they work: RewriteCond %{REQUEST_URI} ^/(review|preview|feature).*\-[0-9]+$ RewriteRule ^review/(.*)\-[0-9]+$ /$1 [R=301,L] RewriteRule ^preview/(.*)\-[0-9]+$ /$1 [R=301,L] RewriteRule ^feature/(.*)\-[0-9]+$ /$1 [R=301,L] note: the (review|preview|feature) but is an x OR y OR … Read more
You should use get_query_var rather than $_GET. But you will need to register you custom variables, for instance: add_filter(‘query_vars’, ‘register_my_query_vars’ ); function register_my_query_vars( $qvars ){ //Add these query variables $qvars[] = ‘video_id’; $qvars[] = ‘vide_title’; $qvars[] = ‘venue_src’; return $qvars; } Then you should be able to use get_query_var(‘venue_id’).