rblout

Not sure what is going on. I removed the new install from my DocumentRoot, downloaded the 3.5 release again and pushed it to my DocumentRoot without any files from my saved off DocumentRoot. I loaded a webbrowser with: https://www.mywebsite.com/wp-admin/upgrade.php.
It said I need to upgrade the database so I did. I tried to load my website and got a blank page like the previous efforts. I then tried: https://www.mywebsite.com/wp-admin/install.php. This gave me a login screen to the new webpress 3.5. I loged in and went to the dashboard which had an error message to the effect that the theme directory did not exist or had wrong permissions. It did exist and have correct permissions. I then went to themes in the admin window and chose the default theme for 3.5. After doing this the website was functional. I then copied over the plugins. I got the “feeling” that there was something incompatible with the old them that I was using. Anyway it is now working but it was a bit annoying and I really don’t understand what/where the problem was.

https://www.usefulramblings.org/?page_id=360

Hope this helps.

This response is for those who manage their own Linux server. If you do not, then your services’ admin would have to make the changes since you most likely would not have the authority. On a Linux box determine what php.ini file your php is using. Do this with a file called junk.php for example. It should look like:

<?
phpinfo() ;
?>

In your browser of choice enter: “https://www.yoursite.com/junk.php&#8221;

This will output a lot if data if your php environment is functioning properly. Look for the following:

Configuration file path – your php.ini file
upload_max_filesize 2M

vi your php.ini file (noted in the above output) looking for “upload_max_filesize” and change it to what you think you need, i.e., 33M. Restart apache
(service httpd restart) to pick up the new value. Look at “https://www.yoursite.com/junk.php&#8221; (may need to force a refresh) to see your new “upload_max_filesize” value. This should correct your 2M limitation.

I have seen a lot of posts where many have changed this value in their php.ini file and “nothing happens”. I am assuming that this is because the apache server (or whatever they are using) is not being restarted to acquire these new values.

Hope this helps.

The problem described herein is a known issue brought about by WP 2.6. The plugin author is aware of this issue and is working it. The podpress website offers some “tweaks” which may or maynot work for you. They did not work for me so I am patiently awaiting a resolution.

Found “Advanced Category Excluder” on this site in the plugins directory. It accomplishes what I talk about in this thread. Also of interest – I downloaded and installed “Expression Engine” only to note that it behaved the same way as WordPress as I have described in this thread. Apparently the behavior I questioned is “normal”. Anyway the good news is I get to stay with WordPress.

I was hoping for some sort of response/solution to this problem. Is anyone else experiencing this issue???

Today I blew away WordPress. Downloaded 2.3.2. Dropped my database. Created a new database. Installed WordPress (NOT an upgrade). Created a new category without a parent. Posted to the new category. Published. The post appears both in this new category and the “default category”. This at least proves that the old database was not causing this problem. It appears to me that there is a bug within WordPress. I will now revert back to my old database and consequently my “old” blog.

What you describe is the way I thought it should work. Unfortunately it is posting the way I described it. None of my three categories have parent catgories. I am running release 2.3.2 and have inactivated all plugins. The problem persists. My theme is the standard WP theme. Any thoughts or suggestions?

https://www.usefulramblings.org

I believe that disabling java script is not a solution. I have since “checked” “Enable java script”. I can add categories now but posts to a new category posts to it AND to the default category. Not sure why. Looking into it.

regarding my earlier post about being able to add a category after “disabling java script” in the browser: now that I can add a category a post to this category also is placed in the default category even though this new category is not defined as having a “parent”

followed “condi4prez”‘s suggestion and now I can also add categories.

Took some effort to find this solution and now I forgot why I wanted to add a category. :>)

When I first installed WordPress I had “Forbidden” errors also. These errors were due to Apache being improperly configured. I could explain here what I did to fix it but the explanation is rather long. If you go to https://www.usefulramblings.org and look at the sidebar you will note that there are readme files for installing WordPress. If you go the bottom of the readme you will see the problem I experienced with an explanation on how to fix it. I hope this helps.

Ottomd is correct in his post. I too was having a problem with changing the upper and lower colors. I recompiled php like:
./configure –prefix=/usr/local/php5 –with-apxs2=/usr/sbin/apxs -with-libxml-dir=/usr/lib –with-zlib –with-zlib-dir=/usr/lib –with-mysql=/usr –with-gd –with-png-dir=/usr –with-jpeg-dir=/usr –with-freetype-dir=/usr

and the upper and lower colors now change. Be careful with the apxs2 entry. It is for apache2. If you are not using apache2 the use apxs. Also the dir entries could vary based upon your distro.