Problem with member.php rewrite for Admin Log in as User Plugin

I use the Admin Log in as user plugin. The vBSEO rewrite is "chopping off" some code on the end of URL that is needed to log in and out of a user's profile.

PHP Code:

http://www.domain.com/member.php?u=userid&admin_log_in_as_user 


is being re-written as

PHP Code:

http://www.domain.com/members/username/ 


where it should look like:

PHP Code:

http://www.domain.com/members/username/&admin_log_in_as_user 


Why is it stripping out the amprestand during re-write?

Here is what the template looks like:

PHP Code:

<div id="admin_log_in_as_user" class="block">
    <div class="admin_log_in_as_user">
        <div class="blockbody">
            <div class="blockrow">
                <a href="member.php?{vb:raw session.sessionurl}u={vb:raw userinfo.userid}&amp;admin_log_in_as_user={vb:raw userinfo.userid}" rel="nofollow">{vb:rawphrase log_in_as_user}</a>
            </div>
        </div>
    </div>
</div> 


Anyone?

I do not believe this will function correctly with vbseo.

One workaround would be to copy the member.php script to something else, say admember.php, add that script to vbseo's excluded script list in vbseoCP, and then change the plugin to link to that page instead of member.php. You should also robots.txt out the new script so bots don't duoble index the member pages.

I can't do that as it is a custom script. I tried adding this to Excluded Pages in the settings:

HTML Code:

^member\.php\?u=(\d+)&admin_log_in_as_user

Did I type it correctly to exclude this re-write?

you can't block member.php from rewriting like that. it's tied to the rules.

and why can't you copy it?

Oh...now I get it. Sorry I'm so dense. That's a great idea.

hehe No problem.

BTW, this did solve the problem.

great, glad it was an easy fix.

Don't really see why it's a problem to make vbSEO NOT strip custom URL parameters. It works as expected in forumdisplay, allowing custom parameters there. My style chooser links don't work on member.php currently because of this.

Sure, as mentioned, creating a member.php clone for extra actions is a viable work-around, but should not be necessary in the first place.

This CAN be custom coded to be accounted for if you wish to dive into the core vbseo code, however, it is currently not supported (nor do we have a code sample available), so duplicating the script is the simplest fix for customers at this time.