Now then...
RewriteRule ^/?$ "http\:\/\/example\/\?post_type\=pbcezmobsite\&p\=2017 " [P]
Urk. Let's pick that rule apart.
The /? in the pattern isn't needed. In the config file, patterns begin with a directory slash. In htaccess they don't. So a request for the front page, the root, in htaccess really would be expressed as ^? in a RewriteRule. Or, if you want to be different, !. where both forms mean "nothing" or "empty request".
In the target of a RewriteRule-- the stuff on the right-- nothing needs to be escaped, and quotation marks aren't needed. (They are sometimes appropriate in a RewriteCond.) Most non-alphabetics don't need to be escaped at all, ever. Some Apache mods-- and some other languages-- have to escape slashes because they've got syntactic meaning, but not mod_rewrite. Literal question marks theoretically have to be escaped, but they'll never occur except possibly in a UA string.
Your rule as written has a blank space before the closing quotation mark. Was that a typo in the post? I'd expect it to crash the whole rule. So... Request for root in the two named domains yields
RewriteRule ^$ http://www.example.com/?post_type=pbcezmobsite&p=2017 [P]
:: detour to Apache due to chronic mental block on distinction between [P] and [PT], with further detour as I notice a slightly confusing pair of statements in docs for a (different) flag ::
In your previous post, when you say "displays as..." did you mean "I want it to display as... but it currently displays as something else"?
example.com/?post_type=pbcezmobsite&p=2040
Is that the actual form of the link, or did you leave something out? You must have done, because as written, links in that form would lead to a browser request for
http://www.example.com/example.com/?post_type et cetera
where "www.example.com" is whichever domain the browser "thinks" it is in (having been fooled by the [P] flag :))
I have to assume the links really say
/?post_type et cetera
The request is then attached to whichever domain the browser currently thinks it is in, and your question is how to conceal the "?post_type=pbcezmobsite&" part.
Matter of fact-- you didn't ask this, but it's an obvious follow-up-- if you're prettifying the URL, do you even need the "p=" element? Seems like what you really want is something like
RewriteCond {same blahblah involving two domain names}
RewriteRule ^(\d\d\d\d)$ http://www.example.com/?post_type=pbcezmobsite&p=$1 [P]
and then, as with any pretty-to-unpretty rewrite, you need the corresponding Redirect for insurance. This goes before all your simple rewrites (with or without [P] flag):
RewriteCond %{THE_REQUEST} \?
RewriteCond {blahblah about one domain name here}
RewriteCond %{QUERY_STRING} (?:post_type=pbcezmobsite&)?p=(\d\d\d\d)
RewriteRule ^$ http://www.example.com/%1? [R=301,L]
You can only capture from one Condition at a time, so you'll need a separate redirect for each domain. This bit is obviously not cut-and-paste; it's a variation of the redirect-to-rewrite two-step. The redirect half is not essential. It's just insurance in case the "real" URL leaks out and gets into someone else's links or bookmarks.
Psst! Moderators! Is there some arcane historical reason why a closing parenthesis after an ampersand turns into a wink? Wait, n/m, I just figured it out. The ampersand is auto-converted into & ... which creates the ; ) sequence. Since the semicolon in entities is optional, the ampersand carries on happily in its truncated & form. D'oh!
