jeezyo

You should post a link, but its probably your old page just getting read before your wordpress site. Its probably called index.html or index.php. Youre going to want to either, a) delete that and use an under construction plugin, b) develop your wordpress site in its own directory and then move it over when youre done. Those are the simplest ways to go about it.

have you adjusted your permalinks settings? looks like they are wrong. Try going in and changing to one of the defaults and see how it works.

You would still need to publish it, but make it private or password protected. Look at the visibility drop down near the publish button.

its just a css class related to suckerfish, your menu script.

Look in your theme options, and see if there is place for custom css.

If so, add this:
#subpage .content p { clear: none; }

If your theme does not have a place for custom css, you will need to go into the editor, to the file style.css. Look for #subpage .content p, and change clear:both to clear:none.

take a look at #suckerfishnav .sf
change the width to 960px, and add border-right: 1px solid #FFF;

you need to create a new directory in the theme folder, and call it what you want. put in a style.css, with this at the top, but change it to name the theme what you want. https://codex.www.ads-software.com/Child_Themes#Example_of_a_basic_Child_Theme

Basically, the way it works is that if there were php template files that you wanted modified, you would copy those files into the child theme, and then modify those as you wish. wordpress will first look in you child theme folder for the template, before it looks to the parent theme. same thing for the css. just add any style in there that you would like to overwrite or create new, and they will take priority over the parent theme.

No load delay, no need to copy over anything that you dont plan to modify.

Yeah, i *think* events manager extended might have been the culprit, because i know it does something to permalinks, and it was disabling that that created the problem the second time. In fact who knows, it might have been enabling that, and not upgrading, that created the problem the first time. Gonna take your advice, and just update them all manually again, instead of wasting more time looking for an automated way of doing it, and just hope it doesnt happen again ??

hmmm….unless im doing something wrong, its not working. i tried both version of their code. Pasted into a php file. Uploaded to mu-plugins. Logged into dashboard. Oh well, guess ill keep on hunting.

Thanks you so much, thats awesome!

thats exactly the sort of thing im looking for. i looked quite a bit before i posted here, but ill keep on looking now that i know it actually exists. thanks for your help!

Oh, it does work. I did it on a few sites just to check. But with 100+ sites, i was just hoping there was another solution, so that i dont need to do this every time i enable/disable or upgrade. ??

i dont have any caching plugins installed.

There is one difference in my htaccess, that i made to handle a custom signup form, a rewrite rule as you can see below, could that have anything to do with it?

RewriteEngine On
RewriteBase /
RewriteRule ^wp-signup\.php(.*)$ wp-content/themes/hmba/wp-signup.php$1
RewriteRule ^index\.php$ - [L]

# uploaded files
RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule . index.php [L]

I fear turning off all the plugins, because it seems that disabling a plugin may have caused this in the first place. Because i did do the manual permalinks save on each site and had them working.

I could deal with it, if there were a way to update all the permalinks at once.

its using subdomains. its very frustrating because there are so many sites!

a little further info….permalinks are set to use one of the defaults /%year%/%monthnum%/%day%/%postname%/ accross the network, but /%postname%/ on the main site. i just realized if i take the dates out of the url the posts do work. so its defaulting them to postname.