unklee

I’m still wondering if anyone can help me please.

At this stage I want to keep WordPress in the blog folder, keep post URLs in the form sitename/blog/category/postname, but eliminate the /blog from the page URLs.

It seems I can’t take the /blog out using Permalinks so I’m wondering if I can do it this way: Use PHP or a plugin to remove the /blog from all URLs, then use Permalinks to add /blog back in for blog posts.

Does anyone know, please, (1) if that will work, and (2) either a plugin that changes the base of the URML or the location of the PHP code that controls this?

Thanks.

Hi Angela, I’ve read that reference (and a couple of others it links to) and I must say I find the idea of moving WordPress from my blog subdirectory to the root directory pretty scary. So I think I’m going to keep it in /blog and try to set up the site around that decision.

My process will be something like this:

1. Switch to the new theme and get it all styled and good. This will be straightforward, though for a while the site will have two different looks for blog and for pages.

2. Copy my key HTML pages into WordPress pages and style them. Again, this will be straightforward. Most people will visit the old pages but a few will find the new ones. The trick will be the URLs for these pages (see below).

3. When I’m happy with this, start transferring all pages as quickly as possible. For a time, there’ll be 2 versions of every page.

4. Set up a static/custom home page for the blog and style this. This should be straightforward.

5. Make that page the site home page, not just the blog home page, to replace the exiting HTML home page (I think that means moving a couple of PHP files to the root).

6. Use redirects in the .htaccess file to direct visitors from Google or with bookmarks to the new pages and take down the old HTML pages and folders & style sheets.

To do that, I need to know a couple of things if you can help please:

(i) The blog post URLs will stay sitename/blog/postname but I’m unsure how the pages will come out. It seems to me that they will be sitename/blog/category/pagename whereas I want them to be sitename/category/pagename. You said before this could be done, but I haven’t seen anywhere that tells me how. Can you point me in the right direction please?

(ii) I’m worried that any change I make to permalinks structure will affect the blog posts as well as pages, so if I remove /blog from the pages, it will disappear from blog posts as well. Is there a way to change one but not the other?

(ii) I have to be able to make the static/custom homepage accessible in the root directory. I think your reference show me that fine thanks.

I know this reply has been long, but I want to be sure to get this right, so I thought I’d lay it all out there and hope you had time to read and answer please. Thanks.

Thanks Angela, I will check it out. I would prefer moving to the root, but I am a little scared of it as well. If I decide that is the way to go, I will try it on a test site first!!!

Thanks again, but you can stop worrying. I was able to locate or reload (can’t remember which) a second .htaccess file, change the permissions, and now I can upload.

So once again permissions were the key. Thanks.

Hi kunstwerck and Samuel,

Thanks for your help. Unfortunately I’m still having the same problems.

I tried increasing the permission, eventually trying 777 (!) but it made no difference. So I asked support at my ISP, and got this reply:

upon checking with our L2 engineers you are seems to be having the following error,

Permission denied: /home/freeweb/web/h2bh/public_html/wp-content/cache/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable,

Suggestion for the problem is to make the file readable or create a new file and try.

The file looks OK, and I don’t know what would make it unreadable apart from permissions. And what makes it more weird is that that isn’t the address of the .htaccess file, and in that location (wp-content/cache) there is only one (blank) file, and I wouldn’t expect that location to have anything relevant. I will try to get more info out of them, but does that make sense to either of you?

Thanks.

I used 705 because it was the highest level of permissions I could see for this install. I changed to 644, but still the same. Perhaps it isn’t permissions?

Hi kunstwerck,

Thanks for your interest and help. It may be that I still need to do what you have said, but I asked the support from my ISP, and got this message:

upon checking with our L2 engineers you are seems to be having the following error,

Permission denied: /home/freeweb/web/h2bh/public_html/wp-content/cache/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable,

Suggestion for the problem is to make the file readable or create a new file and try.

I assume from this they think it is not their problem, but a problem with my WordPress install, specifically the .htaccess file. That file had 604 permissions so I changed that to 705, but that made no difference.

Any further ideas from what you said before? Thanks.

Hi, thanks for that. It sounds like it could be the problem. I understand permissions and how to change them for individual files and folders, but I don’t understand how to apply what you have just said. Can you point me to somewhere that explains how to ensure WordPress has access to the necessary folders please? (I can always Google, but if you have a good reference, that would help.) Thanks.

Hey thanks, that’s it.

I have another WordPress blog with quite a few pages, and I thought I had put them all under parent pages, and things were still unstructured, but I had forgotten to do it for many of the pages. When I add the parent, the pages sort fine.

Thanks.

Hello again, yes you were right and I have been wasting people’s time here and wrongly blaming WordPress (I’m sorry WP). An autocorrect feature WAS introduced into Mac OS 10.8, much to my surprise. The good thing is I can turn it off.

Thanks for your trouble.

I don’t understand. How can it be local to me? It’s not happening in any other software, just WordPress.

Is anyone else experiencing what I’m experiencing?

Hi, I don’t think so. I have 9 plugins I don’t think any of them would have autocorrect, I haven’t added any recently, and I don’t recall upgrading any recently. The ones I have activated are:

BackUpWordPress
Content Aware Sidebars
Facebook LIkes You
Google XML Sitemaps
Simple Comment Editing
Subscribe2
Subscribe to Comments
Tako Movable Comments
WP Captcha Free

Further, I notice the autocorrect happening on this forum, where I don’t recall it before. So I assumed it was a new WordPress feature.

The only other thing I can think of is that I recently upgraded my Mac Os from 10.6 to 10.8, which may have allowed a WP feature that was there all along but wouldn’t run under OS 10.6. But I can’t really think that is correct.

Do you or others get this autocorrect happening on this forum? Is it new?

Hi Mizagorn,

I hope toy read this. I changed true to false in line 33, but it made no difference to my problem. Are we talking about the same thing? I want to stop the autocorrect which shows in a small blue box below the text, and more often gets it wrong than right.

Thanks.

I don’t know if anyone will see this, but I have been using WordPress on my own site for several years, and only now has it started to do autocorrect on my posts, in a little blue box which appears below the text. It must have been part of a recent update.

I hate it! It seems to get things wrong more often than right, and I don’t always notice that what is there is not what I typed. I find in word processors as well as WordPress auto correct is a most annoying, inaccurate and persistent problem.

I wish it was an option in the Dashboard, but it appears not to be. Grrrr! ??

I will try this hack. Thanks.

Thanks. Have you had an issue with page speed that led to you not using some features?