7
Not with a tag, but with a PHP snippet you can, you have some options:
Using EE's built on function
<?php ee()->functions->redirect('{external_link}'); ?>
You'll need PHP parsing on, if you want to use the {external_link} tag you'll have to set it to run on Output
Location Header redirect.
With the above you may get some screen artifacts as ...
6
I've never used EE before version 2 so not 100% sure this will work, but hopefully it helps.
Inside your weblog entries tag (I am assuming it is a weblog entries tag, if it is not, post what it is here) put the following code:
{if no_results}
{redirect="404"}
{/if}
This also assumes you have a 404 page set up in your configuration. This may not work, ...
4
Use the Structure global variable {structure:page:uri} which is the same as EE's native "page_url" variable.
4
According to the bug reported by Mark Drzycimski, for those who don't have an Ellislab account, the solution is listed as follows:
In /system/expressionengine/libraries/Redirect.php on line 50, change:
"<p><a href='".$_GET['URL']."'>".$_GET['URL']."</a></p>\n</body>\n</html>";
to:
"<p><a href='".$_GET['URL']."'...
3
I've run into similar issues in the past, and honestly I gave up on htaccess in the end as I never could get it to work exactly as I intended.
A much easier solution I found was using an add on to force the redirect instead, doing it this way I gained direct control of pages needed redirecting in templates instead.
I used an addon called Force SSL, http://...
3
Detour Pro is an option for this, especially since it provides you with a bit of reporting on each URL redirect. However, it's meant as an alternative to doing 301 and 302 redirects in htaccess - not sure if it would be the best option for URL shortening. Another option is DM Shortee, which is more strictly a URL shortening service and not a redirect tool (...
3
Problem solved. If you are already logged in and log in again the return does not WORK
3
You need to use %{QUERY_STRING}
RewriteCond %{QUERY_STRING} ^option=com_user&view=reset&Itemid=14$
RewriteRule ^(.*) /contact? [L,R=301]
3
My friend... I'm afraid your syntax is incorrect. Place this rule after your index.php rewrites (at the end of the standard EllisLab htaccess file):
RedirectMatch 301 ^/?$ http://www.example.org/todays-info
This is the magic you seek. The second parameter of a RedirectMatch is a regular expression.
3
Yes!
Use the redirect variable in your template.
From the documentation:
{redirect='news/local' status_code="301"}
2
Per comments: The problem was caused by the .htaccess file, and not ExpressionEngine.
2
If you've actually changed the template_group/template structure in EE and you just want to catch old requests and ensure they go to the new location then I'd always look to keep it top-level with .htaccess for this.
First of all ensure that the mod_rewrite module is enabled and the rewrite engine is enabled:
Options +FollowSymLinks
RewriteEngine on
Then ...
2
If you're not opposed to an add-on, I used Detour Pro on a site with many many URL reroutes and loved it. You can use wildcards with it to save time as well.
2
For SEO purposes, I don't think it's a good idea to return a 301 redirect when you want to return a 404 error.
When you do {redirect="404"} then EE serves the 404 template with a proper HTTP 404 status response.
When you do {redirect="404/index"} then EE responds with a HTTP 301 status redirect header.
Google Analytics and Webmaster Tools track when a URL ...
2
You can't use {if}...{if:else}...{/if} (always executed, output thrown away after conditional check) but have to use switchee or something similiar.
{exp:switchee variable="{segment_2}" parse="inward"}
{case value="{url_title}"}
I should re-direct {url_title} | {entry_id} -- <? echo({entry_id}); ?>
{/case}
{case default="Yes"}
...
2
Okay, I found the error (If anyone's intrested):
I must not write RedirectMatch 301 instead I simply have to write Redirect.
So simple.
2
I think it's probably doable. It may be a process of elimination to work out all the kinks as you go, but no core hack should be needed.
I'd suggest you move the system directory out of the main site's document root first.
You can remove admin.php from the main site. And copy it over to the admin subdomain. And you can rename it whatever you like.
You'll ...
2
Updated:
The issue caused by the trailing slash redirect happening after your EE index.php rewrite. You need to have this redirect happen before rewriting to index.php. (Note: almost always, you want all redirects to happen before the rewrite to index.php.)
So, the simplest way to correctly remove the trailing slash, that shouldn't cause you issues, looks ...
2
See if you were bitten by this bug: http://support.ellislab.com/bugs/detail/19378
2
I know it'd be hacking core, but wouldn't throwing a rel="nofollow" attribute on the anchor negate the effectiveness of this?
2
check out this add-on http://devot-ee.com/add-ons/mo-variables and it's "Page Tracker" variables that you can use!
2
The problem is that the redirectee plugin use the native PHP header function which not support the 404 code. In fact it is a little bit strange to send a 404 with the header. Therefor you have to use a 302 code, the 404 page will send a 404 code on his page.
As for redirecting with the 404 code, you have the think of this QA:
User: Hey, do you have ...
2
According to the docs, you can have a selection option that uses different returns.
(Source: http://www.solspace.com/docs/freeform/form/ ) Here's their example:
<select name="return">
<option value="application_form/thank_you">
I will pay at the door
</option>
<option value="application_form/payment">
I ...
2
Alternative solution: use a jquery validation tool instead of multiple return options. If all fields have valid solutions (i.e. all are "yes"), then you collect the contact info. If not, they get an error message.
There are tons of options if you search for "jquery validation" like this one: http://validval.frebsite.nl/
Define what a "valid" response is, ...
2
When you use template access restrictions, EE doesn't do a browser redirect to your no-access template (sign-in/index)--it just displays that template in-place.
For example, if you browse to /members-only in your browser and that's a template with the access restriction, EE will display the sign-in/index template at the /members-only URL.
So, first of all, ...
2
I'm not sure if this works with the {exp:stash:cache} tag or not, but you can try it:
{exp:stash:cache name="page" unprefix="my_prefix"}
{exp:channel:entries
channel="post"
disable="categories|category_fields|member_data|pagination|trackbacks"
require="yes"
}
{if my_prefix:no_results}{redirect="404"}{/if}
{/exp:...
2
The loop occurs because you're testing again and again and again...
Try this:
{exp:browser_sniff available_languages="en|zh"}
{if browser_sniff_negotiated_language == "zh"}
{if browser_sniff_negotiated_language != "{segment_1}"}
{redirect="zh/{uri_string}"}
{/if}
{/if}
{/exp:browser_sniff}
update
Since Transcribe ...
2
The only thing i see from a security standpoint is EllisLab considers php in template a bad practice. If this where me I would create a small plugin that would render your PHP for you. and pass the segment through a parameter. That would then redirect the user.
To create a plugin you can use my plugin starterkit.
1.) Create a folder with lowercase plugin ...
2
It's a simple matter of adding the robots meta tag to the templates which you don't wish to be indexed.
Then use Google's Webmaster Tools to remove those URLs from its index.
You could create a 'dynamic' robots file that applies only to your subdomain by using an htaccess rule like so: (from http://moz.com/community/q/block-an-entire-subdomain-with-robots-...
2
Why just using either snippet or direct put to template meta-part instead of using PHP in-template if editors put full URL?
Something like:
{exp:channel:entries}
<meta http-equiv="refresh" content="0; url={external_link}">
{/exp:channel:entries}
Only top voted, non community-wiki answers of a minimum length are eligible
