• Is this compatible with the WP subdomains plugin?

    So I expect that plugin allows me to mark pages as category “site1” to get them showing at
    http://www.site1.mynetwork.com

    and then using the domain mapping to convert it to

    http://www.site1.com

    Will that make the whole thing explode?

    Basically, I want all the domains showing some pages with “shared content” which edition is in one place (and there will be unique pages for each domain too)

    I’ve already modified 70+ websites having the same pages, over and over, when I could doing only one edit. (taking care of duplicate content with canonical links and some variable texts.

    Thanks.

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter Zambrano Sergio

    (@sergiozambrano)

    Or… what about using another plugin to “tag” pages? and then setting permalinks like
    e.g. http://wordpress.org/extend/plugins/tagpages/

    http://mynetwork/tag/post-name

    and then let the plugin do its magic as subfolders?

    Thanks.

    Plugin Author Ron Rennick

    (@wpmuguru)

    It’s for a single WP network not multiple single WP installs.

    Thread Starter Zambrano Sergio

    (@sergiozambrano)

    I MUST have a single WP installation, otherwise I couldn’t edit the pages in a centralized place.

    Is any of those plugins I mentioning intended / outputting / resulting in multiple wp installations?

    If I’m right, what was your answer about?

    Thanks for your time.

    Plugin Author Ron Rennick

    (@wpmuguru)

    what was your answer about?

    I was telling you that domain mapping won’t do what you’re looking for.

    Thread Starter Zambrano Sergio

    (@sergiozambrano)

    Ron: Your short answers will prevent others willing to explain me why and how to respond, because they will think I’ve got my answer. Although technically I did, That answer only works for others to think you offer good support and “you know your plugins/your stuff”, ie. foreseeing the output, knowing all the answers for me… but if you put in my shoes, after my detailed plan and explanation, a single “NO” doesn’t help me at all.

    A single “domain mapping won’t do what you’re looking for”
    Only gives me more questions which wastes my time more than actually testing the installation.

    If you feel healthy and the doctor tells you “go home and write your last will” that DEFINITELY tells you how confident, smart and sure your doctor is but DEFINITELY won’t help you at all.

    I know you hate someone coming in here with a whole project to be build on others knowledge, but I do answer a lot of “if”s (sometimes I didn’t understand correctly, sometimes people ask the wrong question and we can tell) and I like to explain why and how myself when I’m asked in a forum. I feel if I don’t, I’d better don’t reply. I want to help.

    Domain mapping is the tip of the iceberg. Before that plugin maps the domains, I need other plugins for me to prepare the neccessary conditions for the folders/categories/subdomains/etc reflect what domain mapping needs in order to accomplish my goal.

    Now, after investigating for 3 HOURS last night, and I found out a possible answer matching your useless 5 seconds answer. 10 seconds could have shorten my search 2 hours, that’s helping out.

    I found out domain mapping just mapps whole wp sub-installations to domains. I doesn’t “listen” to folder estructures other plugins could make, and also the multisite installation doesn’t provide a “main network” content area (posts). Content only comes from sub-sites, so I couldn’t “add common posts”.

    I will research with a dummy sub-blog that will only provides the posts and common pages for the rest, and htaccess redirects to map the common pages (tagged pages) to new domains.

    2 paragraph and up are welcome. Otherwise, let helpers do it. Even other who never developed a plugin can explain whys and hows.

    I’ll post the answer here to help others.

    Plugin Author Ron Rennick

    (@wpmuguru)

    @sergio – The domain mapping plugin does not work in single sites. At all. The way it does domain mapping cannot be implemented in single sites.

    “you know your plugins/your stuff” – Unfortunately, yes, I do – http://core.trac.wordpress.org/ticket/11644

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Advisor and Activist

    SergioZambrano – I know English isn’t your first language, so I’m cutting you a lot of slack. Ron, Andrea, myself, and many other people with the funny titles on these forums do know what we’re talking about. It would behove you to give us the benefit of the doubt that we do know our stuff πŸ™‚

    Domain Mapping maps MultiSite subsites to domains.

    It does not map TAG pages to domains.

    You probably can (though I would not suggest it) map tags on an individual WP sub-site to a domain, but doing so may cause conflict with any domain mapping you have going on.

    Is this compatible with the WP subdomains plugin?

    There is no WP Subdomain Plugin (that I know of – if there is, please link us to it). It IS compatible with WordPress MultiSite installed with Subdomains.

    So I expect that plugin allows me to mark pages as category “site1” to get them showing at
    http://www.site1.mynetwork.com

    Please don’t use the term ‘category’, as it is incorrect in this instance. You would create a SUBSITE called Site1 on your network as a subdomain and that becomes site1.mynetwork.com

    Ron’s plugin would be then used to MAP site1.com to site1.mynetwork.com

    Basically, I want all the domains showing some pages with “shared content” which edition is in one place (and there will be unique pages for each domain too)

    I’m not sure what you mean by ‘which edition is in one place’ … Do you want all sites to have mostly the same content and only some individual content? Or do you want all your sites to have their own content and sometimes the same? Or do you want one site to collect all posts from all sites?

    There are plugins you can use to do all of these, but it depends which one you mean.

    Thread Starter Zambrano Sergio

    (@sergiozambrano)

    Having all the sites to have “mostly” or “sometimes” the same content is the same. It’s just a matter of quantity/balance of one or another.

    The plugin I mentioned is http://wordpress.org/extend/plugins/wordpress-subdomains/

    but it would only work if yours would “listen” to any subdomain, being simulated by redirects or any means, to map it to another domain. Wich I doubt.

    What I need can be accomplished by server redirects, but I figured out it’ll be better to change the source of the content to be from the main site where I need it right in the php of the template, rather than messing with redirections.

    For other types of networks / websites could probably be useful to have this plugin (or other) managing subdomains not only coming from actual subsites in the same network, but also to map the subdomains generated by other means.
    I think that’s something the other plugin is closer to do than yours, right?

    Thanks for your time.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Advisor and Activist

    That plugin is not compatible with MultiSite (or WordPress 3.1 from the look of it). I’m fairly certain (without testing) that it would conflict with wildcard subdomain settings that we use for MultiSite.

    This bit:

    just remember to point the document root to the same path as your main wordpress document root.

    would 100% conflict with how MULTISITE handles subdomains. So no, don’t use both Multisite AND this plugin.

    WordPress Multisite (via the WPMU Domain Mapping Plugin) CAN map a top level domain to a subdomain. You cannot use that plugin on Single Site WordPress with the Subdomain category plugin you’ve listed, as the domain mapping plugins were written to work with MultiSite only.

    For other types of networks / websites could probably be useful to have this plugin (or other) managing subdomains not only coming from actual subsites in the same network, but also to map the subdomains generated by other means.

    Ron’s plugin does this. I think you’re confusing what Ron’s plugin does and what YOU have to do outside of the plugins.

    Suffice to say, you can’t have both. Either use WordPress MultiSite to handle subdomains as separate sites, and get to use domain mapping via a plugin, or use the subdomain plugin to make them from your categories and build your own solution for domain mapping.

    That’s all we’ve got for you.

    Thread Starter Zambrano Sergio

    (@sergiozambrano)

    Oh, that’s actually good news!

    From the panorama you painted at the beginning, sounded like only sites in the network would be mapped to the domain, regardless of the folder structure they would output.

    If I understand correctly, your plugin will map to http://www.atlanta.com both the following examples:

    http://www.network.com/atlanta -> site called “atlanta” mapped as folder.
    http://www.network.com/atlanta -> page called “atlanta” inside network.com.

    is this correct?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    πŸ³οΈβ€πŸŒˆ Advisor and Activist

    Only SITES in your network can be mapped to a DOMAIN via Ron’s plugin.

    (tl;dr version: You can only map SITES via the domain mapping plugins. You cannot map pages, posts, categories or monkeys.)

    This CAN be mapped to http://www.atlanta.com using Ron’s plugin:
    http://www.network.com/atlanta -> site called “atlanta” configured as subfolder.

    So can:
    http://atlanta.network.com/ -> site called “atlanta” configured as subdomain.

    This CANNOT be mapped to http://www.atlanta.com using Ron’s plugin:
    http://www.network.com/atlanta -> page called “atlanta” inside network.com.

    Notice how I changed your ‘mapped as a folder’ to configured as subfolder? Your use of ‘mapping’ in that instance was incorrect and will confuse people πŸ™‚

    Thread Starter Zambrano Sergio

    (@sergiozambrano)

    SergioZambrano wrote:

    For other types of networks / websites could probably be useful to have this plugin (or other) managing subdomains not only coming from actual subsites in the same network, but also to map the subdomains generated by other means.

    Ipstenu wrote

    Ron’s plugin does this.

    And now you say

    This CANNOT be mapped to http://www.atlanta.com using Ron’s plugin:
    http://www.network.com/atlanta -> page called “atlanta” inside network.com.
    (Which I called “by other means”)

    Now you understand what I meant by “…not only coming from actual subsites in the same network, but also to map the subdomains generated by other means.

    Is there any way to edit the above post so others who doesn’t read my re-question don’t believe the plugin does that?

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘[Plugin: WordPress MU Domain Mapping] Is this compatible with WP subdomains?’ is closed to new replies.