oznola

i have upgraded to wordpress 3.0 beta 1 from the apt-get 2.0.12 wordpress install as follows…

download and unpack wordpress 3.0 in /usr/share

delete the <wordpress3.0>.zip file
delete old database,
delete /etc/wordpress/config-<yoursite>.com.php
run /usr/share/doc/wordpress/examples/setup-mysql -n example example.com to setup the new database and config file.

proceed as with 5min install.

notes: i keep getting the notice “Notice: You’re using the auto-generated password for your account. Would you like to change it to something you’ll remember easier?
Yes, take me to my profile page | No thanks, do not remind me again” eventhough i tried both ways to get rid of it. i think it has something to do with write permissions in the wordpress tree.

perhaps changing permisions on the wordpress file tree will turn off this message?

i would try this question in the Themes and Templates forum.

ty clayton,

your discourse just about sums up what i have been observing.

i am indeed doing a debian “apt-get install wordpress” install. its the only way i can get the custom permalinks to work so far on this server.

the short comings with a .deb package install are as you articulated.

on the other side of the coin i do feel that the .deb wordpress install is the right way for me on my debian server. having only a sym-link in my www directory with core files that only root can write to seems much more robust if less elegant.

i guess i will have to wait until i deploy my next wordpress site on an ubuntu 9.10 lamp to enjoy the features in the newer releases of wordpress.

in the mean time i just add plugins and themes by hand.

i have read those instructions several times and followed them again this time. it eliminates /wordpress/ from the location bar but breaks the custom permalink /blog/%postname%/.

so i go back to using default permalinks. ??

wordpress is installed in /home/web/wordpress

also try…

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress`

for .htaccess with the original httpd.conf and its permutations.

you have aliased “/usr/local/www/*******-wordpress” to /university but it appears to be unused (no big deal).

then i presume wordpress is installed in /usr/local/www on both machines?

copy httpd.conf to http.conf1 (.conf-one for a backup) and then comment out the second <Directory> directive and add <Directory /university> below it.
now you will be using the alias. ??

then run
#apache2ctl restart (as root).

then try you permalinks again.

i believe what i have suggested it what the original author intended for the wordpress section in httpd.conf.

in the mean-time i will look into what the other options you have in httpd.conf for wordpress are. it appears that the author of your httpd.conf was trying protect your wordpress files like password files.

the wordpress codex recommends a httpd.conf section for wordpress similar to what i have.

if the adjustment suggested do not work then comment out everything in the wordpress section of httpd.conf and try adding a section similar to mine underneath it but with paths relevant to your system. assuming the /university alias is correct you can use /university instead of the literal path.

if you get tired of that sort of tinkering you can copy httpd.conf to httpd.conf2 and then copy the original httpd.conf1 back to httpd.conf.

also, you have to run apache2ctl restart every time you make a change to httpd.conf.

here is where i am getting the info on configuring httpd.conf https://httpd.apache.org/docs/2.2/sections.html

i have this in /etc/apache2/httpd.conf

# For wordpress
<Directory />
Options FollowSymLinks
AllowOverride All
</Directory>

<Directory <path_to_www>/university>
# … other directives…
AllowOverride All
</Directory>

(but i add “university” for your convenience.)

put .htaccess into /university/?

he will likely change the permissions on the files and directories where wordpress resides. there is some debate about what file permissions should be for wordpress but 755 is a good start.

i have only recently begun to use adsense but i found pasting the code into the HTML tab of the post/page editor to be the easiest way to get it working.

you have to pick the right ad unit size to fit in the post.

yes; it appears you have insufficient permissions.

follow the instructions on these links

https://codex.www.ads-software.com/FAQ_My_site_was_hacked

https://smackdown.blogsblogsblogs.com/2008/06/24/how-to-completely-clean-your-hacked-wordpress-installation/

https://ottodestruct.com/blog/2009/hacked-wordpress-backdoors/

if it has write permission to the directory i think it should rewrite .htaccess

its a sort of simple minded question but did you try to reset the password?