t_l_3

I’m thinking maybe if I can disable pre_get_blogs_of_user & update_meta_cache or something.

The database query that returns from update_meta_cache is 950+ records long and appears to be a user settings for every site it’s a member of. Considering it’s the Super User account, it loads them all.

Was able to get it working by clearing cookies almost obsessively. Also, had to re-register via the link from the Plugin (rather than previously done).

I did notice the following error during install of the plugin from the WordPress admin’s Plugin section:
Warning: Invalid argument supplied for foreach() in /home/tl3/zac/wp-content/plugins/tumblr-crosspostr/tumblr-crosspostr.php on line 67

I’m having the same issue, with the same environment (Chrome 34.0.1847.116) using WP 3.9 & version 0.7.12 of your plugin. I’ve cleared the WP cookies. I’ve logged out of both Tumblr & WP and closed the browser. Using the default theme (TwentyFourteen). It’s practically a clean install of WP and your plugin. That’s it.

I’ve double & triple checked the OAuth keys and yet when I click on “Click Here to connect to Tumblr”, nothing happens. No redirection; just a reloading of the same Tumblr Crosspostr Settings page (same similar URL as fondalashay mentioned).

Any fix yet?

I was able to put a band-aid on it by copying the non-numbered tables (having to do with content) over to a _1_ table.

Now, is there a way to reinstall without disrupting the existing sites? The primary site (that that subdomains are hosted on) isn’t used, so that can be messed with. But the subsequent subdomain sites that the domains are pointed to are the important ones.

Sorry, WPMU was just easier/quicker to type than Multisite.

All the tables are MyISAM.

Alright I figured part of it out.

The install of WPMU’s site, in short, isn’t table-prefix_1_table-name, it’s just table_name. The SITE_ID_CURRENT_SITE & BLOG_ID_CURRENT_SITE is set to 1, while there is a blog in table_prefix_blogs with that ID, there the tables for that site are table-prefix_table-name.

(more to come as I figure out how to fix it)

And for the life of me, I can’t figure out why “Network Setup” shows up in the Network Admin->Settings while my working install doesn’t have that.

After my copying, it changed nothing, but while adapting the working site’s wp-config.php to be identical to wp-config.php of the broken site (with obvious minor changes [MySQL, FTP, etc.]), I’m encountering some odd errors as well. Mainly database connection issues. Only the wp-config.php holds these settings, correct? I have to do some trial & error, but something is causing an db connection error despite the DB_* definitions are identical.

I noticed the only change (that can be related) is that in the “Must-Use” plugins page on the broken WPMU, there’s an “index.php” with “WordPress MU Domain Mapping” listed in the plugins. Whereas my other-yet-working WPMU install on another server only have “WordPress MU Domain Mapping”. Odd, considering the “mu-plugins” directory contents are identical.

I’m in the process of copying the exact core files that the working install has, to the broken install.

I’ve look thru the schema file. It sends out the email but somehow those tables aren’t getting created.

Does WPMU use the 1st site as a template when it come to plugins, when creating a new site?

I previously bypassed this issue by using a site I created, but stopped using a site we cancelled & replaced it with the new site I had to build. Now that site was finished, I went to map the full domain to that site in Domains->Domain Mapping and that wouldn’t add either.

Did you deactivate it or did you have to completely remove the plugin?

Anyone know where (which file) the SQL queries are sent when the sites are added?

Problem with C is, I am the host (my server). :\ I’ll keep looking. It’d be easier if I was getting some sort of logged or displayed error message.