Ryan Willis

I actually tried that, but I only went as high as 120 seconds. I’ll try more and let ya know. Thanks for your help ??

Great, thanks ??

It’s the MultiDB plugin from premium.wpmudev.org (paid). In all honesty, I’d rather be using HyperDB and may switch in the near future. All that aside though, this seems more like an nginX specific issue to me. I haven’t been able to narrow down the bottleneck yet (swamped at work), just thought I would ask if anyone else has seen this before. I’d really like to get it figured out.

There is an interesting conversation about this issue here. The extra element is appended by TinyMCE on purpose to defeat an issue with FF/Webkit browsers. In the posts, they mention a couple ways to handle this. One is to just add the following to your stylesheet: br[mce_bogus] {display: none;}. This will hide the bogus line break item. You can also add cleanup: true to the TinyMCE init script, which I don’t see in the initial WordPress configuration.

There is some checking to do on TinyMCE versions and WordPress’ custom integration, as well as Templ33t’s tab switching and how it triggers the content filtering. That said, this seems to be an issue of configuration.

Zac, apologies for the delayed reply, I’ve had my focus elsewhere and most support requests I’ve received came through my blog. In any case, I will look into the issue though it is unclear whether it is Templ33t specific or not. The new version will be released very soon and this concern may already be addressed in the new code. Stay tuned.

Ryan

The issue fixed itself after re-saving the configuration page (with no changes oddly enough).

Right on. For the time being, I’ve added an additional str_replace to OSSDL’s rewriter function. Seems to work, but obviously a solution that doesn’t require modifying plugin files (that will be overwritten after each update) would be better, heh.

Excellent work on this plugin btw ??

Adding “files” to the rewrite matches in the WP Super Cache config did the trick for replacing the hostname. Now I just need to figure out how to add the blog ID to the rewrite. I’ll take a look at the OSSDL CDN Off-linker source, but do you have any ideas?

Creating a separate bucket for each site would cause redundant copies of the wordpress theme and plugin files as well, which would cost more. I’ll probably have to stick with appending the blog id to the path for now.

As for the url rewrite, I’d be happy to send a link but this installation is not currently live. Do I need to add “files” to the rewrite rules on the CDN tab in the WP Super Cache configuration? Or is it handled by the plugin automatically?

Thanks for your help.

@backle Thanks ??

If your plugin is not a “must-use” plugin and is installed to the plugins directory rather than mu-plugins, you’ll need to keep a couple things in mind when creating your global tables.

1. If you create the tables through a register_activation_hook callback, use $wpdb->base_prefix and not $wpdb->prefix to prefix your tables.
2. If you register a deactivation hook to remove your tables, know that it will remove the tables when the plugin is deactivated for any blog, so you will need to add some kind of check to make sure the plugin is not activated elsewhere. I increment a site option whenever the plugin is activated in a blog and decrement it when it is deactivated in a blog. If the option is 0 or less, I remove the tables. I’m not sure this is the most efficient method but it does work.

Hope this helps!

Thanks for the advice. I was signing in and out of the different sections like a mad man to no avail. I walked away for a while then tried again and it seemed to right itself.