davehprohoods

This is a pain because if I want to scroll up to see or edit something at the top I have to scroll all the editor text back up, then I have to scroll the page and all the editor text back down again to get back to what I was editing. It redundantly scrolls both the editor and page when I only want to either scroll the page or the editor.

This is not better, it’s making it more difficult and I need some way to change it back as one install of 3.9.2 has the editor scrollbar while a newer install on another server running the same version doesn’t have the scrollbar and I need to know how to reactivate it.

Well where am I supposed to ask what the best site is to register domains or host WordPress sites? They all do things differently with WordPress.

There’s a huge risk upgrading WordPress when you have plugins that go outdated with later versions (even at their latest version) or there are customizations that are built for the current version. I only upgrade if I know that isn’t the case or they can be fixed in a cost-effective way, and having inherited every WordPress site I work on, upgrading is not necessarily cost-effective.

Do you recommend something for file versioning?

We’re using WordPress 3.5. 3.5.1 is on the drop-down select list when I created the topic, and I didn’t select that.

Your author name shows on the site not your username if it’s different.

How do I stop tracking this? I just got notified through email of the last post even though I didn’t for the other ones.

I see. So since the web user (apache) has full r/w permissions (and I know how to fix it anyways if it doesn’t), is there not a switch I can flip so it falls back on the “easy” cURL way? How is it determining that it can’t do it that way?

I’m having this same problem and I’m not sure how to fix it. Yoast SEO doesn’t let me add or modify a robots.txt file and conflicts with the Multisite Robots plugin, so I’ll contact Yoast (if I can) since I’m surprised they don’t take into account multi-site robots files (which are difficult if they’re an actual file, and should be in the database).

After reading some more about CSS, I think I figured this out, though CSS is not that intuitive to me. I think it is because the two divs inside are floated, which means the encapsulating div has no determined height before the border is drawn, so it is actually at the bottom, but the bottom edge of the div is at the top.

I discovered the custom theme our previous developers built broke it; I didn’t think the theme CSS could do that, but apparently it does to keep it consistent.

OK yes sorry I deal with multiple WordPress installs and I was hoping the solution would apply all around. In some installs we do want any non-recognized sub-domains to redirect to the main domain but on others (like multisites that use sub-domains) we want unrecognized sub-domains to redirect to that main site, not the base site it was installed under if it’s different.

That will work for only one domain; if they reach a non-existent sub-domain on any of the sub-sites, it will go to the main domain, which is not desirable. Any other solutions?

I mentioned multiple times why it’s bad to show the domain as a sub-domain to another site to our users. It confuses them and causes copy-and-pasting to be inaccurate and the recipients to be confused and cause the same questions to be asked over and over; sorry, our bad we have to say.

I don’t understand why there’s no effort to do it properly to begin with, or little desire to do it properly now. WordPress allows multiple sites, it should display them properly in the address bar and in links across all pages. This doesn’t seem like a difficult fix or implementation.

Well, the problem is, he didn’t code it to show the proper URL for our users across the different sites. They are only supposed to see their site, not the base site with their site as a sub-domain. Because it seems possible to program it properly, I don’t trust that there was a good enough reason to do it that way. I’d love to see where there actually will be a problem, because I haven’t seen one yet and this seems to clear up a few problems already.

Yes, that’s what I said when I said “even though we change it and it accepts it, it puts back the -2, and the non-2 link redirects to the -2 URL”… what’s going on?!

If anybody knows a solution to have WordPress show only the proper subdomain.com links instead of subdomain.domain.com, I would really love to see it. In the meantime I will be looking into hacking it or developing a plugin for it, as this can negatively affect our admin users even if they are not “admin” roles.