Scott McCulloch

Thanks for the links Mika!

Yes, I knew your plugin doesn’t directly mess with wp-activate.php, but I thought since it’s supposed to be doing registration per site rather than whole network, the post-activation links would honor that. 🙁

Anyway, I’ll look at possibly following some of those instructions to make a wp-activate.php ‘replacement’ of sorts.

Thanks,
Scott

So here’s an example:

The site they’re registering on is clientcompany.mycompany.com

The link in the activation email correctly takes them to clientcompany.company.com/wp-activate.php?key=yaddayadda

The problem is the text on that page that says:

Your account is now active!

Username: bobmcc

Password: BsJ0uKltRYdR

Your account is now activated. Log in or go back to the homepage.

The link to “log in” and “homepage” both go to mycompany.com instead of clientcompany.mycompany.com

Thanks,
Scott

PS. As I think about it, I may actually need to figure out how to make a new plugin using “Join My Multisite” and “Register Plus Redux” because I want to use “invite codes” rather than activation by email (only clients may register, and we don’t want to have to manually approve everyone)… unfortunately, Register Plus Redux doesn’t appear to do ‘per-site’ registration.

What’s the danger of placing

kses_remove_filters();

and

kses_init_filters();

on either side of that wp_insert_post() query?

Thank you for the tip re: $_GET variables… I will definitely make that change!

I think I found something in the WP code… /wp-includes/post-template.php

At line 695:

* Displays page links for paginated posts (i.e. includes the <!–nextpage–>.
* Quicktag one or more times). This tag must be within The Loop.

So it appears the problem is indeed that because my content is being rendered via the shortcode it isn’t technically “in the Loop” as it’s rendered. I think I need to followup on my approach of adding the code to my page.php template, and figure out how to get the custom query to take the place of the default query to generate “the_content”

A) In “normal” pages (i.e., where I type the contents in the editor) using <!–nextpage–> results in pagination. I guess it’s not technically a ‘shortcode’? I don’t know what in WordPress does the actual pagination when it comes across <!–nextpage–>, but it “just works” in the normally generated pages.

B) The code is placed into the ‘content’ area of a page via a shortcode (using the PHP Code for Posts and Pages plugin).

I create a ‘snippet’ in the plugin settings, then put the shortcode “[php snippet=3]” into the page content, and it displays the resulting text in the page. (I tried RETURNing the text, but get nothing… PRINTing or ECHOing work – other than the lack of pagination).

If I take the exact same content text, and copy it into an actual page via the content editor, then the <!–nextpage–> tags work and the content is paginated.

Somehow, I think, whatever processes the <!–nextpage–> tags is missing this shortcode generated content… for example, if in a page I do something like this:

Some text here
<!--nextpage-->
more text here
<!--nextpage-->
[php snippet=3]
<!--nextpage-->
last text

The resulting page will be paginated… BUT, it only paginates there the <!–nextpage–> tags are in the editor generated content… any <!–nextpage–> tags in the text from the php snippet are ignored.

Looks like the same issue as discussed here:
http://wordpress.org/support/topic/77282?replies=7

Unfortunately, there’s no final answer there… so I’m still hoping someone will know the secret!