Forum Replies Created

Viewing 15 replies - 1 through 15 (of 56 total)
  • Thread Starter xrun

    (@xrun)

    Solved. For reference:

    <?php	$paged = (get_query_var('paged')) ? get_query_var('paged') : 1;
    	query_posts('cat=3&posts_per_page=3&paged=' . $paged);
    ?>

    Thread Starter xrun

    (@xrun)

    I see. We can start the install over, no problem. There’s just one site so far, the other domains are empty, nothing to tear down on those.

    With a single set of files, how are the users on the various blogs under the three TLD’s (one each for Norway, Sweden and Denmark) given the dashboard and our theme in their own language, depending on which TLD they’re on? I know WP comes in localized versions ofc, but how about several languages and always showing the right language in the right TLD, how is that determined with one set of files?

    Thread Starter xrun

    (@xrun)

    Not quite, and that’s just it. The two options are still just that, we haven’t selected either of them yet.

    I have three domains ready. I’ve installed wordpress on of them so far. The other domains are empty and ready to receive files. I’m wondering if we should install WP again on those and enter the same db info during those installations, or just copy the WP-files there but not run the install script.
    We’ll need a main blog, a blog id 1 so to speak, on each of the three domains, and each of the three domains will eventually be open for users to create their own subdomain blogs.
    The thing is to set it up in such a way that a sitewide search by a user on any of the three main domains subdomain blogs produces results from all three main domains subdomain blogs, and when listing latest sitewide posts, this should also show content from all the subdomain blogs under each of the three main domains.

    I just don’t know what would be the right way to do this, and I belive we need a clear plan before we proceed.
    If there’s another “best way” to do this that would require a fresh start right now, we’ll do that. We’re not comitted yet, but need to find a way to actually do this.

    Thread Starter xrun

    (@xrun)

    Example: dashboard and theme text seen in swedish for the .se TLD.
    Blog pages, posts and comments as written by the swedish bloggers, untouched by us.

    Same goes for Norwegian on the .no and Danish on the .dk TLD’s. Theme and dashboard in their respective languages, but the posted content presented untouched in the original posted language by the blogger.

    To clarify: we don’t copy the posted content to the other TLD’s, they remain where they were posted. They should however be seen in lists on the other TLD main-blogs, and a click on a listed blogpost title from another TLD brings up the post in the blog where it was originally posted.

    I need to get some clarity about the installation process in a setup such as this. We already have wordpress set up at one of the domains, and we have the two other domains ready but they don’t contain files from wordpress just yet.
    Do we upload wordpress to the second and third domain and run through the installation script, or do we just copy the files from the first domain over to the second and third domains?
    If I were to hazard a guess, I’d think we should run through the wordpress installation script on those domains as well, using the same prefixes, but I could be wrong. Can anyone confirm this?

    The point is to make sure all content from each domain is available on all three domains, including subsequent comments and edits of posts and pages. Meaning that when we use a sitewide latest posts or sitewide latest comments plugin, they’ll see everything and offer a link to the posts or comments on the domain where they were originally posted and so on. Also to have for example a blog called toms.domain.no for Norway be a different blog than toms.domain.se for Sweden.

    I’m asking because I’m not entirely sure about the process of adding wordpress to the second and third domains and have them working together like this, allthough I’m clear about entering database information during the WP setup process.

    If I’m not mistaken, it’s the same content read out at different locations. This is rather important, otherwise a post written on the .se domain, and then viewed and commented through the .no domain, would not have the comment when the post is viewed back at the .se domain. That would be a serious problem.

    I agree, if the contents is to be shared between different sites with different brands and userbase and/or customers.
    In my case, it would seem like duplicated content on different domains. The content has not been duplicated though, it’s the same and stored at the same place in the same database. One content available through 3 different domains.
    These domains will share the same brand, the only difference between the domains is the language of the wording in the dashboard and in the theme.
    I hope we’re on the same page here, I just need to be sure this is the way to go in my case and it seems like we concurr.

    Ah, Andrea to the rescue. Thank you. 🙂
    I take it there are other ways to get a similar result though. Would you go for the solution outlined in my previous post? I’ll need to have the contents posted in the other countries available for all three.
    Just double checking before I dig into this.

    As this issue is a very current one for me, I’d like to ask if anyone have tried sharing database between domains. How would this be handled, would it be safe to install WordPress in this way?

    For example, if there are blogs like this:
    tomsblog.domain.no (Norwegian user – Norwegian WP and theme translation)
    tomsblog.domain.se (Swedish user – Swedish WP and theme translation)
    tomsblog.domain.dk (Danish user – Danish WP and theme translation)

    Would these be handled correctly as three separate blogs by WordPress in a single database for all three domains, each with their own posts not interfering with eachother?

    I’ll chime in here as I’m looking to do the same thing. The need in my case is to display the same content in all the scandinavian countries, but having the theme (and thus complete interface) in their own languages. We have .no .se .dk domains allready registered, and for now they all point to our .com domain where the main installation and database is hosted.

    So if there’s a better way to show visitors on the .se domain the swedish translation of the theme, and the visitors on the .dk domain the danish translation of the theme, then that’d be interesting. All the contents (blog posts) needs to be available on all our domains for this setup.

    Thread Starter xrun

    (@xrun)

    Yes, well we already have translations. The thing is to set this up in such a way that the site is displayed in one of the three scandinavian languages depending on wether the site is visited on its .no .se or .dk domain. The language is really not the problem, showing the right one of the three available is the thing.

    As I see it, there are several possibilities. We could install the site in three different localized versions on each of those domains, and let the three installations use the same database. Not sure if that would work well, because having all the content available to each of the sites would mean they all need to use the same table prefixes.

    Or we could use a single installation, and determine the language of the browser or operating system, and give the visitor a localized version based on this. The problem with this is that many people in Scandinavia prefer the English version of both operating systems and browsers, so they would get the site in English instead of Norwegian, Swedish or Danish.

    If it’s possible, we could have a single installation still, and maybe determine the language to be shown on wether the site is visited on its .no .se or .dk domain, but as these all are forwarded to the same installation this would be somewhat tricky and may not work in some browser configurations. The reason for this would be that browsers with high or custom security settings would warn the blogger about being forwarded, and could either jump to the main .com domain where the actual installation is, or cause some other problem that would gum up the work… and the user experience.

    There may be several other workable solutions, though the first alternative I mentioned here seems to be the best one so far, if it is possible. If there are people with experience setting up such a site, please chime in. 🙂

    Thread Starter xrun

    (@xrun)

    Human translation is fine, the point is to set this up so that the theme and dashboard is localized for each of the domains. F.example the comment buttons should be worded in Norwegian, Swedish and Danish, depending on which of our .domains our site is visited through.
    The posted content in the blogs will be left in its original state. If a post is written in Swedish it’s gonna stay Swedish regardless.

    Thread Starter xrun

    (@xrun)

    A codesearch for “ms_posts” in the wp-contents folder turned up this inactive plugin as the only result:
    http://wordpress.org/extend/plugins/multisite-latest-posts-widget/
    Removed the plugin and table, no issues.

    Its functions in our setup was already replaced with another plugin:
    http://wordpress.org/extend/plugins/diamond-multisite-widgets/

    Thread Starter xrun

    (@xrun)

    Ok, I’ll make another backup and then remove the table to see if that clears it up. Thanks 🙂

Viewing 15 replies - 1 through 15 (of 56 total)