TexInWien

Has something changed since this thread?

I played around with this a few weeks ago and wasn’t able to get it to work, but I may have missed something. It’s also possible that something’s changed since then.

From the linked thread:

dashaluna: When 1 or more posts of custom post type exist then any of them can be a parent of another post of the same (!) custom post type.

Ipstenu: Ah, that makes sense, actually, since CPTs are posts/pages and not categories

I don’t want to bug too much, but I also don’t want to waste time re-coding my CPT experiment if it’s not going to work.

My understanding is that that ‘heirarchical’ setting applies only to a single Custom Post Type.

That is, in my examples above, it would not be possible to hierarchically nest Resort posts underneath Destination posts.

Hi Andrea,

Fortunately, I think this block of rules will perform well. I only have one rewrite rule, and I’ve got 5 conditions in front of it. I believe Apache will stop processing the conditions as soon as the first condition returns false, so for every domain other than customer.com, Apache will only look at the first condition, then ignore the rest of the conditions and the rule.

I’ll probably change the order of the conditions to make sure the ones that are most likely to fail are at the front of the list.

We are already running quite a few customer sites on this installation, and haven’t seen any noticeable performance issues related to mod_rewrite. When we do have enough customers and rules to cause a problem, we’ll move them all over to httpd.conf, which should speed things up.

Thanks for the import-html-pages solution – I’d considered that, but this site is old style with lots of tables and inline styling, so I’d prefer to just serve up the static HTML and maintain the current (very outdated) design until we’ve converted everything over.

Thanks for your input and suggestions!

So, here’s the solution I came up with, in case anyone’s interested:

For sake of this example, we’ll assume that the ID of the blog I set up for my customer is 25.

1. I added the customer’s entire site content to a new directory I created in his blog’s blogs.dir directory (/wp-content/blogs.dir/25/old-site/{all html and images here}).

2. I then added the following rewrite rules to .htaccess, in front of all of the other rewrite rules:
RewriteCond %{HTTP_HOST} ^customer.com$ [NC]
RewriteCond %{REQUEST_URI} !^\/wp-content* [NC]
RewriteCond %{REQUEST_URI} !^\/wp-includes* [NC]
RewriteCond %{REQUEST_URI} !^\/blog* [NC]
RewriteCond %{REQUEST_URI} !^\/index.php$ [NC]
RewriteRule (.*) /wp-content/blogs.dir/25/old-site/$1 [L]

And that, my friends, is all that’s required, at least according to my early tests. Will return if I find any problems with this setup.

If anybody sees a potential problem with this setup, I’d love to hear it!

I’d like to get an update here, as well. WPTouch is fantastic, and we’re considering moving all of our customer sites to the Pro version.

We’re also toying with a move to W3 Total Cache, which may make this issue obsolete.

I see now that you have to add the redirection, first, and the box for defining the referrer URL shows up in the next step.

A little weird from a UI perspective, but at least it works.

Tex

I’m pretty sure it’s a joke. A pretty funny one, too. The site is not by Amazon, and the joke is: What good is a write-only storage service?

If you can only upload data to it, but can never download the data, it’s not very useful, is it? Might as well just delete the data and be done with it.

I’m surprised that they seem to have a real PayPal page, though.

Kurt

Hi Frederick,

Thanks for the response. To go one step further, I’d like to suggest the following directory structure. This takes into account one of my other feature requests, which can be found here:
https://www.ads-software.com/support/topic/plugin-w3-total-cache-feature-request-better-directory-structure-for-file-based-caching?replies=2

wp-content/w3tc/000001/
wp-content/w3tc/000002/
wp-content/w3tc/[6 digits – blogid left-padded with 0’s]

I’m not sure on the W3 Total Cache – specific questions, but for the poor man’s CDN, you should point the root domain somewhere that’s not serving cookies.

Anyone who’s visited the top-level domain, assuming GoDaddy’s sending cookies out on it, will pass cookies with every resource that’s pulled from the domain and all of its subdomains (if my understanding of cookies is correct).

Clear your cookies and your cache, then run PageSpeed on your site again – I believe you’ll see the cookies warning go away. I just tried it and there’s no cookies warning for me. Long term, you need to point the TLD at somewhere that’s not serving cookies.

djnfield – You can set up a “fake” CDN that works with W3 Total Cache, as you describe.

Depending on how good your host is, you can set up a cookie less domain and create symlinks to wp-content and wp-includes, meaning all of your images would be in one physical location, but they’d be served by the cookieless domain, while the dynamic stuff comes from your main domain.

We’ve got this set up for our customers who don’t want to spring for the full-on CDN option.

Kurt

I submitted a bug request from the support tab.

By the way, I can’t confirm epschmidt’s report, but what I do see is that the domain rewriting for mirrors was working with subdomains but is not working with tld’s.

On our dev server we have a URL structure like this:
[projid].dev.projects.xioup.com

I installed W3 Total Cache on that server and rewriting worked fine for all sites – media URLs were changed to https://ourmirror.com/path/to/file/.

As soon as I changed these sites use a tld as their primary domain, the URL-rewriting stopped working.

Kurt

I’m running the Domain Mapping plugin on WP 3.01 and would be willing to allow you to debug on one of my development or test installations.

I’ll bet this is due to relying on the domain name for the cache folder name.

I’ll let you debug on my development server if you’d like.

Kurt

Yes, that did it. Any other potential ‘gotchas’ I should know about? WP-Cache? Anything else?

Thanks for the tip ??

+1

I have the problem on wpmu 2.9.2, as well. I have the exact same error as sbressler (directories are different, of course, but line numbers and files are the exact same) and the exact same behavior as masonjames.

Would be nice to find a solution.