How to use and Not use "Use Friendly Alias Path" In different directories

I use "Use Friendly Alias Path" checked as yes for a website.

I have a blog directory under same website, which also have subdirectories under. I want this directory not use "Use Friendly Alias Path".

Is there an easy way to cancel this setting under a different directory using htaccess, or any other suggestion?

Thank you

"Easy" is a relative term.

One way would be to put the blog resources in a different context and create a context setting: use_alias_path (set to "No").

Maybe there is an easier way, which would be good because a separate context would complicate your site in a number of ways.

Quote from: BobRay at Apr 08, 2011, 11:10 PM

"Easy" is a relative term.

One way would be to put the blog resources in a different context and create a context setting: use_alias_path (set to "No").

Maybe there is an easier way, which would be good because a separate context would complicate your site in a number of ways.

Thanks Bob. I thought of that also but it will make other things little more complex.

I wonder if this is something doable with htaccess.

FWIW, the new features in the upcoming 2.1.0 release include support for manually specifying the complete URI for any Resource you wish. You simply check the Freeze URI checkbox and a URI field is revealed. When this is checked, the URI is never recalculated for that Resource, even if you move it. You can also manually edit this field when the URI is "frozen" to any valid URI string.

Quote from: OpenGeek at Apr 09, 2011, 11:14 AM

FWIW, the new features in the upcoming 2.1.0 release include support for manually specifying the complete URI for any Resource you wish. You simply check the Freeze URI checkbox and a URI field is revealed. When this is checked, the URI is never recalculated for that Resource, even if you move it. You can also manually edit this field when the URI is "frozen" to any valid URI string.

Jason, this is awesome! Can’t wait to try it out, I better get to installing a 2.1.0 RC already...

Quote from: pixelchutes at Apr 09, 2011, 01:27 PM

Jason, this is awesome! Can’t wait to try it out, I better get to installing a 2.1.0 RC already...

FWIW, RC2 is expected on Monday—lot’s of bug fixes from feedback on RC1.

Quote from: OpenGeek at Apr 09, 2011, 11:14 AM

FWIW, the new features in the upcoming 2.1.0 release include support for manually specifying the complete URI for any Resource you wish. You simply check the Freeze URI checkbox and a URI field is revealed. When this is checked, the URI is never recalculated for that Resource, even if you move it. You can also manually edit this field when the URI is "frozen" to any valid URI string.

Thanks a lot Jason. that could be a solution.