grosshat

Yep. We’re facing the same issue.

Tests we’ve made:

– a change on the default language slug (any change on the string), makes a valid URL

– database values seem to be same as the rest of languages

– it appears apparently randomly

I’ve thought it might be an issue related to flush rewrite actions. But debugging that didn’t give any useful info.

Although it looked resolved, it caused again redirection problems even with priority modified.

At the end, we had to modify qTranslate in order to stop its request management when a language pattern is found on the URL and such pattern matches with an enabled language.

We stop qTranslate URL management when the URL is found on the redirections list, and do a wp_redirect directly.

Done. It was a conflict with qTranslate plugin. I solved it setting a max priority for Redirection plugin (to 0), so it is the first action before any other plugins works.

You should add a param to the shortcode call, deciding if that is a category string or a category id. So the user calls it:

[mpc_recent_posts number="10" category="software"]

That must be referenced on the shortcode_atts.

Then you should fetch the category (from string or id) and pass it to the WP_Query (as category_name for string, or cat for id).

Are you thinking on content? On code? Or on both?

For content, you might use WordPress workflow, marking something as draft until it is getting done for being puslished.

On code, you might use your local installation (with production database, for instance) for developing and deploy when code is ready for production.

If you are thinking on having 2 sites on production, with different domains, you should have an installation with one database but different tables for each version (standard feature on WordPress network).

Do you need that for specific purpose? I guess for getting such feature, you should modify the plugin itself.

From Google Guideline for Sitemaps:

A Sitemap file is independent of the language of the content. To make sure that each language version can be crawled and indexed, use unique URLs. These URLs can all be included in your Sitemap files.

WordPress is based on Hooks, Actions and Filters. You can get the big picture on its API docs:

https://codex.www.ads-software.com/Plugin_API

On this case you might code an action triggered when a site is created, or when the theme for the new site is setup. But you already have examples using filters:

https://wordpress.stackexchange.com/questions/33522/changing-bloginfo-description-from-a-plugin

Stop and think. I asked you what you want to achieve. Which file?

Right now, this page is giving this CSS file:
https://arakataka.rhli.org/wp-content/themes/oxygen/style.css

Explain to us why that is wrong, and what should be. Do no paste more .htaccess or whatever just for pasting, because such noise does not help. :/

How do you config the domain on WordPress network?

BTW, ServerAlias does not need ‘csi.our.company.uk’, since it is the ServerName.

You get that information calling get_bloginfo('description')'. So you might code a custom function to set such data.

API: https://codex.www.ads-software.com/Function_Reference/get_bloginfo

Ups, that is a typical maintenance code error. If you have to maintain manually that info for sites, think to redesign that. :/

So, what file do you think is being missed? Give the name and its path, so it is easier to know what you expect.

I tried that, debugging with Firebug -> Network, and all the resources used on the page (CSS included) don’t give any 404. :/

…the browser either redirects to a 404 page or the basic landing page from my hosting provider (JustHost).

That is quite different. A 404 error means your server receives the request and does not find a route to response. A landing page from your hosting provider means there is no DNS configuration for such domain, so the request does not get your server.

You can debug (and so, modify) that checking how wp-includes/kses.php works when you are importing. That code is the HTML/XHTML filter used by WordPress for allowing some elements and attributes.