noogrub

I have the same problem KingJeffrey had: WP 2.8.1 Editing Page now shows in one column, with the Attributes and Publish widgets far down the page. If I hit “Screen Options”, select 1 column and then select back to 2 column, the main column narrows and I can drag the widgets to the right sidebar. However, no matter what I try, the page reverts to single column when I refresh, or when I click “Publish”.

Can anyone explain how the “Screen Options” settings work? I have not figured out what js is called when I click “Screen Options”.

Any assistance appreciated.

This upgrade stinks. I wish the WP coders would act like professionals.

I notice that on “Edit Page”, the left sidebar dropdown arrows (for things like Posts, Links, Media, Pages, etc don’t work. Anyone have any ideas there? I also notice that javascript from various plugins works fine in other areas but not on edit-pages.php.

Hope that helps, and I hope someone fesses up what the darn problem is.

Drupal is looking prettier all the time. They actually test their code as they develop it.

OK, everybody, have a good laugh, but then please give me a point in an alternate direction.

I have a client which is a university department. Their webserver IS their ONLY option for hosting, and that webserver only allows db connections to the Uni dbase server, which runs mysql 3.23. Yes, I know. Yes, I know that, too. Uh-huh. Yep. Laugh it up. Those policies are all in the name of “security”, too, which adds to the comedy.

I developed the client’s CMS using WP 2.0.11, and cosntantly have to grab functions, javascripts, etc from WP2.7 and do some occasional custom scripting in order to get things working for them. Sometimes I rip code from XOOPS to do things that WP hadn’t implemented in 2.0. Imagine that for a moment. Needless to say, upgrade notices from WP Grand Central are ignored.

Spare me the glib “get another provider” “advice”. This is not an option for this client. Is a genuine professional-grade technical discussion of why the later version of MySQL is required? Are there specific 4.0+ features involved?

I’m considering switching the entire darn thing to XOOPs, but I really love WP. It’s beginning to seem to be less work to hack the install scripts to run 2.7 on 3.23 rather than continue the constant coding to enable plugin workarounds.

XOOPS I don’t love so much but that option looks sweeter all the time. One reason it’s so popular overseas is precisely b/c folks in less technically-fortunate countries often have to deal with legacy systems, and cannot mess with a system like WP where their decisions are made for them. “Upgrade yer provider, dude” is not an option.

I have other clients running WP 2.7.1 b/c they have modern hosts. But in this one case, the client is shelling out $20k a year, most of which is to pay me to constantly custom-code stuff like lightbox-2/templates/pagemash/etc which don’t want to work on the old WP. (wp_enqueue workarounds, anyone?) There is no way the Uni is going to upgrade their dbase in the forseeable future. I need the account, but I’d rather spend their budget making the site cooler instead of just getting basic stuff to work.

What’s a fella to do? Any suggestions? Anyone else chopping into the install script to work around the Micro$oftesque forced “wisdom” of the WP developers?

Curious to hear the thoughts out there.

We host our WordPress installation using Redhat linux and apache. Our host is a virtual host.

In order to get Permalinks to behave properly, we have to add:
RewriteOptions Inherit

to our .htaccess file, in addition to the items which WordPress wrote. We also made sure that
RewriteEngine On
was there.

Documentation for mod_rewrite mentions the need for the “Inherit” option, which is NOT set by default:
https://httpd.apache.org/docs/2.2/mod/mod_rewrite.html

Note that if you wish, you can add
RewriteEngine On
RewriteOptions Inherit
inside the virtual host block in your httpd.conf

Hope that helps someone!
John