frank tredici

I think the format of the form itself has changed.

Originally and for a few years, I had [text* ic-youremail] for the sender’s email field.

But now I think it needs to be[email* ic-youremail].

That is, I changed [text* to [email* and it works.

To my specific install, correct…I should not run out for a while.

But more to the theoretical aspect of the question, because as WP developer that adds client WP Sites to my WPMSN install from time-to-time, I should never ever resequence AI values or else the WP Core and MultiSite tables will get corrupted.

Is that the best answer to the question?

What does it matter?

Just wondering…that’s all.

My wp_##_options table looks like this:
Rows 3,984
Next autoindex 2,036,971

So I was wanting to rebuild the AI in order to headoff long-term issues with potentially exceeding the upper limit of the AI

• This reply was modified 7 years, 10 months ago by frank tredici.
• This reply was modified 7 years, 10 months ago by frank tredici.

Question. It costs $179 to migrate from standalone to multisite?

Ok. Hope it works. You are missing the naming convention of my tables.

My tables are wp_ID_* … not wp_22_ID_*

“22” in my post is the ID.

I’ll post back on the results.

But how does your plugin know the target table ID=22? (i.e., wp_22_*)

Do I manually provide the ID of the subsite at time of import?

Or does your plugin automatically grab the next ID from the auto incr value? If so, then I would need to manually rename the tables after import to move them from wp_(AI+1)_* to wp_22_* — correct?

• This reply was modified 7 years, 10 months ago by frank tredici.
• This reply was modified 7 years, 10 months ago by frank tredici.
• This reply was modified 7 years, 10 months ago by frank tredici.
• This reply was modified 7 years, 10 months ago by frank tredici.
• This reply was modified 7 years, 10 months ago by frank tredici.

So out of curiosity, how do I map the migration?

The SOURCE standalone DB table names are wp_* while the TARGET multisite database table names are wp_22_*

In certain instances, the source wp_* tables will conflict with the target multistage core tables at wp_* …

• This reply was modified 7 years, 10 months ago by frank tredici.
• This reply was modified 7 years, 10 months ago by frank tredici.

Work around note: you cannot reset your password from a site within Multisite. You can only reset your password from the core install site (Site ID: 1).

Wondering…why is that?

Started for me with the upgrade to WP v4.7

Any wordpress gurus out there?

I am wondering if it has anything to do with the cookie attribute isHttpOnly?

I can see that the cookie gets set on wp_set_auth_cookie(); do_action(); with attribute isHttpOnly = “true”, yet once the wp_redirect(); is executed (which is essentially back to itself) the cookie is destroyed.

BTW, my script was working fine until I upgrade yesterday to WP v4.7.

• This reply was modified 7 years, 11 months ago by frank tredici.

Note:

When I first login to a site in my Multisitre network, the following cookies get set:
wordpress_d6718066b5ad6e44d3470f952222ec16
wordpress_logged_in_d6718066b5ad6e44d3470f952222ec16
wordpress_test_cookie
wp-settings-1
wp-settings-time-1

And I am taking to my Admin panel.

Yet when I switch to another site in the network, I only get the following cookie and the WP login form appears and I cannot get past it.
wordpress_test_cookie

I do not get the other 4 cookies.

Ok, cool. I’ll look into it. Thanks.

Thank you @FrankCorso. Looking forward to it.

Thank you @FrankCorso. Please add it to the wish list, if possible.