iceman42

The Carrington Build looks pretty cool but I was thinking more along the lines of a tool within those early js wysiwyg textarea toolbars where you could define a preconfigured table that when the user clicked a button would popup, they then could add the elements into the various boxes.

It also doesnt look like you can do https://www.domain1.com and https://www.domain2.com. Mostly looking at this for content sharing and single administration area.

I went digging and digging and then digging somemore, and I ran into an issue that I had seen before. I made some changes to the httpd.conf and had to restart apache, and for several minutes my issue went away. So I went into my php.ini file and disabled mmcache, and presto it worked.

If you have mmcache or some other extensions loaded with php you might want to check and disable them and see if it changes. You can do this in one of three ways.

Directory directive in httpd.conf,
<Directory ‘/some/path/to/wordpress’>
php_admin_value mmcache_enable 0
php_admin_value mmcache_optimizer 0
</Directory>

PHP.ini file just comment out or turn mmcache.enable=’0′ and mmcache.optimizer=’0′

Also do something similar with .htaccess
php_admin_value mmcache_enable 0
php_admin_value mmcache_optimizer 0

You might say but I dont have mmcache installed or whatever, but this should show some of those struggling that there might be something other then WP to blame for the issue, and it might be something that you have to play with in Apache or PHP.ini.

HTH

I went digging and digging and then digging somemore, and I ran into an issue that I had seen before. I made some changes to the httpd.conf and had to restart apache, and for several minutes my issue went away. So I went into my php.ini file and disabled mmcache, and presto it worked.

If you have mmcache or some other extensions loaded with php you might want to check and disable them and see if it changes. You can do this in one of three ways.

Directory directive in httpd.conf,
<Directory ‘/some/path/to/wordpress’>
php_admin_value mmcache_enable 0
php_admin_value mmcache_optimizer 0
</Directory>

PHP.ini file just comment out or turn mmcache.enable=’0′ and mmcache.optimizer=’0′

Also do something similar with .htaccess
php_admin_value mmcache_enable 0
php_admin_value mmcache_optimizer 0

You might say but I dont have mmcache installed or whatever, but this should show some of those struggling that there might be something other then WP to blame for the issue, and it might be something that you have to play with in Apache or PHP.ini.

HTH

I went digging and digging and then digging somemore, and I ran into an issue that I had seen before. I made some changes to the httpd.conf and had to restart apache, and for several minutes my issue went away. So I went into my php.ini file and disabled mmcache, and presto it worked.

If you have mmcache or some other extensions loaded with php you might want to check and disable them and see if it changes. You can do this in one of three ways.

Directory directive in httpd.conf,
<Directory ‘/some/path/to/wordpress’>
php_admin_value mmcache_enable 0
php_admin_value mmcache_optimizer 0
</Directory>

PHP.ini file just comment out or turn mmcache.enable=’0′ and mmcache.optimizer=’0′

Also do something similar with .htaccess
php_admin_value mmcache_enable 0
php_admin_value mmcache_optimizer 0

You might say but I dont have mmcache installed or whatever, but this should show some of those struggling that there might be something other then WP to blame for the issue, and it might be something that you have to play with in Apache or PHP.ini.

HTH

I went digging and digging and then digging somemore, and I ran into an issue that I had seen before. I made some changes to the httpd.conf and had to restart apache, and for several minutes my issue went away. So I went into my php.ini file and disabled mmcache, and presto it worked.

If you have mmcache or some other extensions loaded with php you might want to check and disable them and see if it changes. You can do this in one of three ways.

Directory directive in httpd.conf,
<Directory ‘/some/path/to/wordpress’>
php_admin_value mmcache_enable 0
php_admin_value mmcache_optimizer 0
</Directory>

PHP.ini file just comment out or turn mmcache.enable=’0′ and mmcache.optimizer=’0′

Also do something similar with .htaccess
php_admin_value mmcache_enable 0
php_admin_value mmcache_optimizer 0

You might say but I dont have mmcache installed or whatever, but this should show some of those struggling that there might be something other then WP to blame for the issue, and it might be something that you have to play with in Apache or PHP.ini.

HTH

kennemore and candv I echo your comments, I have three new WP sites waiting and 2 to upgrade and I am sitting here with a permissions issue and its been this was for a while.

The force upgrade script didnt work for me. Anyone know where i can get an old copy of 1.5. IMO the newer version isnt worth it.

I have the same problem only it occurs on a new install. I have successfully installed WP 1.5, this was my first install using the newer version, and its a new site so no upgrade. I’ve been going through and doing each of the hacks and none seem to work. I have redownloaded and reinstalled at least 3 times.

Any other thoughts.

Thanks ??

class-IXR.php will cause issues as well in the 1.5.2 version of WP, go grab the svn release of class-IXR.php and replace the class-IXR.php in you wp-includes directory.

No I’m sorry, there is a class-IXR.php in wordpress/wp-includes, replace the older version (1.6) class-IXR.php file with the newer version (1.7) class-IXR.php. Not sure this will work for everyone but it seemed to do the trick for me.

Some of your problems will be cleared up by grabbing the latest version of the class-IXR.php from the SVN trunk of WP, just grab and replace.