Obat Maag Kronis
informasinya bermanfaat sekali gan, wah jangan lupa kunjungi balik lapak ane nih
useful information gan, oh do not forget to visit the stall behind ane nih
Obat maag kronis
Less is more!
Switched to the Pantheon cloud service last week and discoverd they dont work with .htaccess. I Found the Global redirect module and it worked like a charm. Sure I would love to see a ton of extra features. And can think of a milion more. But the fact that alle you have is 2 input boxes, makes it so powerfull. Im switching to this module for all my drupal sites now and dumping my old habits of 301 redirecting in the .htaccess file.
I considered this a required module for SEO
I install this module by default on every Drupal installation I create.
The 6.x branch has a sort-of-major bug that causes redirect loops when used with other modules related to URL aliases, but a patch to fix it is available in the issue queue.
Just what I was looking for
This module works exactly how it's supposed to. I noticed in a Google search of my site that the site.com/node/1234 links were the ones showing, so I installed this module and now that problem is fixed!
Great for SEO and Affiliate links
The Global Redirect module helps you eliminate duplicate URLs and also makes it much easier to migrate a website to Drupal and 301 redirect all the pages without losing all your link juice and PageRank.
We also use the module to make our Affiliate links look nice and pretty (eg mysite.com/servicename rather than theirsite.com/index.php?affiliate=123).
It just works
I just installed it on my server and it works. No modifications necessary. Using it to eliminate duplicate pages such as the frontpage with views
Helps eliminate duplicate URLs
This module provides a simple way to automatically redirect links such as 'node/123' to their proper aliases. Most of the other features can be taken care of with proper .htaccess rules, but the node-to-alias forwarding is hard to beat.
Unfortunately, as of this writing, this module can cause infinite loops when using i18n. If you're running a non-english site, be sure to check the issue queue, it looks like this problem may be solved soon.