tdjcbe

Not in a position to code this today (I;m on my laptop on battery and it;s already half drained) but you (or someone else) could code up a quick mu plugin that looks to see what theme is being used. If it’s the theme that you want to get rid of, go ahead and change both the options for the theme and the stylesheet to the new theme.

I would think that would work. You would also have to look at what widgets are being used and make sure they get changed over.

Please give this a looksee:

https://plugins.paidtoblog.com/wpmu-power-tools/

I don;t believe it’ll do inactive blogs but it’s a start. It’s setup to delete spam blogs and users. Should be same principle.

There’s an outside script as well but I can;t find it right off.

Please give this a looksee:

https://www.ads-software.com/extend/plugins/limit-blogs-per-user/

I know it might seem trivial but not using the “/” keeps redirecting to the root.

Usually that’s a sign that you’ve installed wp/wpmu into a subdirectory or as an addon domain on a CPanel box. Is that what you’ve done? If so, that’s not recommended as you’re now seeing.

More specific details about what your current server environment would be a plus.

I don’t think this is the cause but just to mention, the site in question fails validation:

https://validator.w3.org/check?uri=http%3A%2F%2Finlightus.com%2Fpureinsight%2F&charset=%28detect+automatically%29&doctype=Inline&group=0&ss=1

In this case it’s three rather minor things but that is something to check if search engine bots aren;t picking you up. I’ve seen sites previously with hundreds of problems and they don;t get indexed.

Why not throw a blogroll link to the secondary site up on the primary site?

Are you wanting to do this as an upgrade or manually setting these or how?

Give the “Welcome to the multisite” sticky and look for the link about creating a network. I have a feeling that you forgor the steps about setting up your required dns wildcard. Forgive me for not copying and pasting the direct link. Not feeling too good tonight.

edit: Just noticed that the subdomain is a Google landing 404 page. Please give the specific as to your setup. If you;re on Google (oh I forget the name of the program) you need to make sure that whatever you;re using supports mod_rewrite as well as the wildcard dns. I don;t think that they do.

Do you have any object and/or file caching in place?

That’ll only work on tiny sites as you’ve compiling all of the content from all of the blogs for each and every search at the time that search is made.

I’d go one of two different routes.

– Either install a sitewide indexer like either Donncha’s or the WPMuDev one. Both of those keep a running total of what’s on the site and it;s easier and quicker to do searches against that.

– Get a Google Mini. (I actually host a 45k blog site that has one of these. Bright yellow. Looks weird against the other gray servers) ??

The one that you reference is not the way to go. Old timers from back in the old pre 2.x WPMu days will remember ITDamage;s sitewide feed plugin and how slow that was. It took the latest 100 posts from each blog, compiled them and then skimmed the latest Posts to create a sitewide feed.

You can cache the compiled Post data but if you;pre going to do that, you mind as well go with one of the other preexisting solutions. Be a waste of time just to redo everything.

I will also point out that Lars just complains about the preexisting solutions. He doesn;t really say what the problem is. We use all three of the solutions I;ve suggested and all of them work on 3.0.x without issue.

Someone else is going to have to give links though. I;m not feeling good tonight. No copy and paste I;m afraid.

I’d just create the sites myself and use them later on if you wanted to or reassign them to someone if they needed them. Less overhead with database queries.

lighttpd 1.4.6

Last I knew, and I’ll be the first to admit that I haven;t checked recently, you had to be running at least 1.5 of lighttpd. 1.4.x has an issue with the uploader. I seem to recall a hardcoded error within the uploader that produced an error.

Haven;t used lighttpd in quite a while though so not sure what the status on this is.

https://codex.www.ads-software.com/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F

It may be help if you check your webserver’s error logs as noted in the error that you copied and pasted:

More information about this error may be available in the server error log.

Give them the https://altafc.futsal.se/ link and tell your webhotel to check it because it’s not working.

https://blahblahblah.futsal.se/ (Which I doubt you would have) also redirects to their home page. It should redirect to your registration page. it doesn’t. The problem is with the wildcard.

Do realize that if you use the Akismet plugin sitewide, you may come under their Commerical Usage clause:

https://akismet.com/commercial/

Discussed here as well:

https://mu.www.ads-software.com/forums/topic/16257