dherren

Well, no responses, but I’ve found a fix by modifying the core code.

In /wp-includes/category-template.php I found the code for the wp_dropdown_categories. By modifying line 396:

$output = "<select name='$name' id='$name' class='$class' $tab_index_attribute>\n";

to this:

$output = "<select name='$name' class='$class' $tab_index_attribute>\n";

I can now use wp_dropdown_categories more than once in my sidebar and my pages once again validate xhtml 1.0 transitional.

I can’t even begin to imagine what the wider ramifications might be to this, but given that I validate now and before I didn’t, and the dropdown categories are being selected correctly, I think it’s ok.

This doesn’t fix the problem, but at least it will publish the post without having to manually edit the DB…

If you try to _edit_ the posts which have missed schedule, there’s no UI to actually publish them. However, if you do a “Quick Edit” instead, there _is_ UI for publishing the posts.

This is what I’m having to do until a fix is found. cUrl is enabled on my server, but the posts still show up as “missed schedule”.

This doesn’t fix the problem, but at least it will publish the post without having to manually edit the DB…

If you try to _edit_ the post which have missed schedule, there’s no UI to actually publish them. However, if you do a “Quick Edit” instead, there _is_ UI for publishing the posts.

This is what I’m having to do until a fix is found. cUrl is enabled on my server, but the posts still show up as “missed schedule”.

I believe curl support is enabled on my server and I’m still seeing Missed Schedule issues.

When I call phpinfo() I see this in the output:

curl

cURL support enabled
cURL Information libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3

Anyone? Bueler?

Is there any way to simply get rid of the visual editor altogether–permanently for ALL users in a way that prevents it from ever being turned back on? I hate the damn thing–I don’t want it changing what I write. If I want 3 spaces I want three spaces and I don’t want some javascript crap mucking with my data…

I like that idea as well–it might force a solution to the problem I posted yesterday:

<https://www.ads-software.com/support/topic/152948&gt;

namely, that they cookie format from the 2.0.x tree to the 2.3.x tree has changed the delimiter of the cookie array from a comma (2.0.x) to the vertical bar in the 2.3.x tree. As near as I can tell, the cookies are otherwise identical, but this delimiter change causes problems when one has to administer multiple blogs in the same domain with different versions…

I’d like to be able to do this as well… any suggestions? I’m not finding anything in the codex…

Running on OSX, we are experiencing a VERY high number of these messages:

“Fatal error: out of dynamic memory in yy_create_buffer() in /Library/WebServer/Documents/index.php on line 4”

I have experimented with changing the amount of memory scripts can use in the php.ini file, but changing the default 8M to 12M, 16M, or 32M hasn’t had any effect.

We have absolutely standard index.php files in all the blogs, so line four is:

require(‘./wp-blog-header.php’);

I’m beginning to get lots of user complaints. Running an apachectl graceful will temporarily restore service.

Any suggestions?

Just change the table prefix in the wp-config.php file of the second installation.

For example, I do this for student club blogs at a school site I run. Each club uses the database ‘wp-clubs’ but each club’s blog uses a different database prefix. Eg: ‘astro_’, ‘nature_’, ‘writing_’, ‘chess_’, etc. Everything in the wp-config.php file is the same for each except for these prefixes.

I am suddenly having inline uploading problems as well. Two days ago when I uploaded some images, everything worked just fine. Yesterday, nothing. When I click upload, nothing happens and eventually it times out with this message:

Cannot Load Address

Stopped loading <https://myaddresswashere/wp-admin/inline-uploading.php&gt;: lost network connection

I have restarted browsers, used different browsers, restarted the client machine, restarted apache, and restarted the web server itself. Still no joy.

No changes whatsoever. I’m in Mexico, server is in Vermont. Routers are unchanged on both sides of the connection. I can upload to the server directly via sftp, but the inline function refuses to work.

anyone?

Is $post_status no longer a global in the 2.x versions of WP?

Follow up:

After doing some testing by inserting some die(“message”) lines in various places, it would appear that the variable $post_status is not being returned to Jerome’s plug-in though it is declared as global.

Is this a 2.x change that $post_status is not available?

I have bbclone running in both the 1.5.2 tree and 2.02 tree of WP. The only place I was 100% successful in getting it to work (and now it works very well) is by inserting the bbclone code IMMEDIATELY before the content div in the page.php, home.php and index.php of whatever theme you’re using.

Denis de Benardy’s solution is still MUCH MUCH easier with no editing of any files required:

Step One: Install and activate Static Front

<https://semiologic.com/software/static-front/&gt;

Step Two: Name ANY page you want to become your home page ‘home’

The beauty is that you don’t have to modify any files at all, WP will still use your home.php file automatically, you can have a bunch of pages that don’t get displayed with alternate content and then make them the home page at will and change back, all within the admin interface of WP. No access to files is needed.

I use this on some 20+ WP driven sites I run for high schools.