fredb86
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Category Display: Invalid foreach()Forum: Fixing WordPress
In reply to: Category Display: Invalid foreach()Ok. I’m pretty sure I figured out why it’s happening. Here’s my setup. If someone could try this an verify, I’d truly appreciate it.
1) I have ten categories
2) I have 20 articles but ALL of them have “Post Status” set to “Private”
That causes the error message in index.php when categories are listed.
3) If I set the “Post Status” of just one of the articles to “Publish”, the error DOES NOT appear. The article is displayed and just the category that the article is in is listed.
So, this appears to be a bug in WordPress where, if all articles have “Post Status” set to “Private”, an attempt to list categories causes that error msg to appear.Forum: Fixing WordPress
In reply to: Category Display: Invalid foreach()It does not work. However,
if I use this code:
<?php list_cats(0, ‘All’, ‘name’, ”, ”, ”, ”, ”, false); ?>
the categories are displayed BUT I STILL GET THE ERROR MESSAGE.Forum: Fixing WordPress
In reply to: Category Display: Invalid foreach()That is not the case here. I did a fresh install of WP 1.2 and changed the site url in the database, and I still get this message when using the default index.php and css file from WP 1.2.
Forum: Fixing WordPress
In reply to: category error FOR EACHI’m also getting this error. I have just upgraded from WP 1.02 -> 1.2. I am calling the category display function using the call in WP 1.2 index.php file:
<?php wp_list_cats(); ?>
I have used phpmyadmin to examine the wp_categories table and it looks fine. I’ve tried creating new categories, and that works fine, but the error persists. I have about 10 categories.
PHP 4.36, MySQL 4.x, FreeBSD
Could this be a problem with MySQL 4.x and maybe not in MySQL 3.x?Forum: Installing WordPress
In reply to: Can’t Login: WP 1.02 -> 1.2Ok, here’s my solution. I created an empty database and installed a fresh install of WP 1.2. Then I took note of the randomly generated password for user “admin”. Then I ran phpmyadmin on the new database and copied the encrypted password string out of the wp_users table for user admin. Then I went back to my hosed database and copied that encrypted password into the password field for user admin. Then I successfully logged in using that randomly generated password. Everything is fine now. Sheesh. ??
Note: I had already tried deleting my WP cookies and it didn’t help.Forum: Installing WordPress
In reply to: tick.png…………………………?After perusing the code, I figured out that those ticks are actually supposed to be the “rating” of the link. Somehow the first link got set to a rating of “9” when it should have been zero. You guys may want to check your “upgrade from .72” procedure to see if it does that accidently.
Forum: Requests and Feedback
In reply to: FEAURE REQUEST: Notify admin/users that direct HTBy the way, the actual code that checks to see if a direct HTTPS connection can be made to wordpress is in the file: b2-include/xmlrpc.inc
if (!function_exists(“curl_init”)) {
$r=new xmlrpcresp(0, $xmlrpcerr[“no_ssl”],
$xmlrpcstr[“no_ssl”]);
return $r;
}Forum: Requests and Feedback
In reply to: FEAURE REQUEST: Notify admin/users that direct HTUh, that title should be: “FEATURE REQUEST: Notify admin/users that direct HTTPS connections are not possible”