dlangendorf

I had this same problem and the answer is here, although it took me a minute to put the pieces together. If your situation is like mine:

the htaccess.txt file was in the /wp-content/plugins/wp-dbmanager folder

i had no folder /backup-db in my /wp-content folder. i created one.

i used my ftp client to move the htaccess.txt file to my desktop, then added it to the new /backup-db folder via ftp

my mistake was this: i changed the file to .htaccess.txt — not realizing that the .txt should be removed. i sort of glossed over it. anyway, by removing .txt and adding a . (period) in front of .htaccess, the warning message disappeared.

when you add the . in front of .htaccess the file will disappear from the folder, but that is expected. the . makes the file hidden, from what i understand.

anyway, it worked. hope it helps.

i am going to set up an install using a “dead” url, one not in use at the moment, and see how it works. i’ll post if i discover anything useful. again, thanks for your help.

moshu,
thanks for the help. this helps a lot. and i’ve been warned. but this confuses me a bit (i’m not great with the direct, redirect thing). my hope was to have my host, godaddy, house not only my website (danlangendorf.com … not up yet) but also the blogs (for now, yesternow.com and blogendorf.com). as noted, these blogs are currently at typepad. i don’t necessarily have to port all content over from typepad, as these are experimental, for play, and such. my hope was to have godaddy host danlangendorf.com (not a problem) AND the blogs, https://www.yesternow.com and https://www.blogendorf and any new ones i add. you’re saying that WP does not like redirects, so the strategy outlined above will not work easily? sorry for the seemingly-simple questions, but it does help to hear from someone who is an “expert” before i invest a ton of time in it.

regards.

dan langendorf.