Wilma_Wilma

Works for me too ??
Thanks!

He’s not the only one. I’ve had the same happening ever since I downloaded the plugin for the first time in early April. I mentioned it in a post in the beta testers forum but it got lost in the “noise” about a disappearing permalink page. Tried several other versions since and the problem remains.

WOOOHOOO …. I’m very happy ?? just did everything that you two suggested and it seems to have worked just fine. I need to redo a link or two, but it’s looking good! Thank you so very much for your patience and help! I learned a thing or two and one day I hope to be able to share what I learned with others, just the way you two did.

Reading this again, I think my earlier post on NOT moving the WP .htaccess file is wrong and I should move it. I guess my question should have been … is there anything in the current htaccess file that I should copy to the WP .htaccess file and if yes, WHERE do I put it. Or can I just delete that current htaccess file (with the directory stuff in it). I hope I still make sense! I’m on a learning curve (and thankful for your help! stuff like this is a bit scary when you do it for the first time).

Here’s what’s in the existing .htaccess file (in the public_html directory) if it helps:

DirectoryIndex default.html default.htm index.html index.htm index.php

and this is what’s in the .htaccess file that’s currently in the existing blog directory (after I changed the permalinks – it didn’t give me a problem):

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

# END WordPress

I’m following this here: https://codex.www.ads-software.com/Giving_WordPress_Its_Own_Directory

It mentions moving the .htaccess file to the root, but there already is an .htaccess file in there. If I understand you rightly, I can ignore moving the WP .htaccess file and just move the index.php (from the blog directory) to the root? And then follow the instructions in the above link when I switch to pretty permalinks and get a warning that the .htaccess file cannot be written to?

Thanks again! You are very helpful!

The current blog does not have pretty permalinks and I understand that in this case, there may not be a .htaccess file. I wanted to have pretty permalinks in the new WP structure, but if not having those would avoid possible .htaccess clashes, I’ll do without. I wouldn’t be confident enough to edit such a file or even know what to put in it if there were to be a conflict.
Currently the other things in the root (all in their own subdirectories) are x-Cart, forum (vBulletin), the current blog (WP), image gallery.

Thank you both!

Yes, there is an index.html file in the public_html directory. It is the current landing page of the site (basically a logo with mapped buttons to click through to the main sections of the site: store, forums, blog). The idea to set up a WP site with a static front page was to get rid of this existing landing page, so I guess it can be deleted (together with another couple of .html files like the 404 page – which are also now included in the WP setup.

Not sure whether there is a .htaccess (if it’s there, I guess it’s hidden), but it is a good point to check.

Govpatel: why must that static front page be without sidebars? I’ve set up a static front page like a newspaper page. This works great in my test environment (which has WP in public_html but it’s the only thing installed there).