Use a multi-site installation (see our multisite tag), give each team its own sub-site on /team-name/ and use the master site for the rest. Advantages All users on a multi-site setup are stored in the same database, they don’t need a separate account for the main site. You can give each user a different role … Read more
As this sounds like an existing WordPress setup that ‘was’ working and now ‘is not’ working then check a couple of things: 1. have you recently moved server? or who else has changed anything on your server such as: – file permissions for the WordPress folder – have these change? – php.ini or .htaccess files … Read more
You have to ignore the “otherside” in the htaccess file of your “root” blog. You can try to add something like that above the (root) WordPress’ .htaccess code: # stuff to let through (ignore) RewriteCond %{REQUEST_URI} “/otherside/” RewriteRule (.*) $1 [L] #
Check if the Primary option is selected for the second domain under domain mapping settings. It should say Yes under Primary in Settings->Domains for that domain.
OK Thanks all I found the answer update_option( ‘WPLANG’, ‘ar’ );
Using LiteSpeed with php 5.3 + WordPress 3.5 will require to increase External App >> lsphp5 to these values : Memory Soft Limit = 777M Memory Hard Limit = 800M Amazing values for memory setting, but it works for me.
Install WordPress as a multisite installation. Check Codex! for how to start. You can google for more tutorials on how to setup a multisite installation.
There is no code I know of to automatically partition databases like that based on their size, but if you want to use something to manually split your system across multiple databases, then HyperDB is one way to do that. http://wordpress.org/extend/plugins/hyperdb/
Your user are not inside the user-list of each blog in network active; maybe you are Super-Admin. Go to ‘Sites (All Sites)’ –> Edit a blog in Sites –> Tab ‘Users’ –> Add your user to the list of users and see the dropdown.
prepare has always required two arguments, it just didn’t throw an error when used incorrectly until 3.5. Basically, the use of prepare in this case is not doing anything. Since you’re not passing potentially unsafe data to the query, you can remove it entirely to get rid of the error and just pass your query … Read more