FeralReason

Thanks much!

Posted in wrong place re wrong plug-in. My mistake. Please DELETE.

Marking as resolved.

BTW – this problem only exists with 3.5.2. I just installed 3.6 and it had no problems.

I’ve installed 3.5.2 on localhost 4 times now. Same result each time: Can’t add text in the edit window. And text tab and “Add Media” do not work. Is this the problem you are having? My GoDaddy install is working fine though.

Anyone else seeing this ?

Platform : Windows 7 running Xampp, MySQL version 5.5.8, PHP Version 5.3.5.

Thx for the response. I think I’ve solved the problem. Although I haven’t identified the cause, I’ve at least isolated it down to the root directory’s .htaccess. (Recall that I have the Blog located in a subdirectory of the website’s root — so there is a root .htaccess and a /blog/ .htaccess.)

So (for the benefit of posterity) here is what worked:
1) Rename the “.htaccess” in the root directory (to something like “.OLDhtaccess”.
2) Log into the WP admin area and set the Permalinks as desired.
3) Test (everything works appropriately.)
4) Rename the “.OLDhtaccess” back to “.htaccess”.

I haven’t had the time to test the root .htaccess line by line — and it would disrupt the client’s site too much to do so now — I’ll save that for some future opportunity. (The curious thing is that I have two other virtually identical .htaccess files with very similar sites working fine.)

Didn’t get around to deactivating plugins – altho there is only one active plugin – sharebar. So no plugins (such as SEO plugins) that might play with .htaccess.

For now I’m marking this as “resolved” tho not fully understood ??

Thx for all the responses!

kmessinger – Thanks much. Sorry for long delay – I was on vacation.

I just tried your suggestion. As soon as I click on Common Settings -> PostName (radio button) and then click “Save Changes” it puts me back into the login screen (as before) and will not allow me to log in.

No message on proper PermaLink settings appears and the .htaccess file is rewritten, deleting all code as before. At this point I can’t even access the blog online until I restore the .htaccess file back to what I described above (also as before). Going back to the main site and clicking on the link to the blog (or trying to access it through its URL) again results in the message “This webpage has a redirect loop”.

Since this blog is in a subdirectory of the root, I also checked the Root’s .htaccess file. It is identical to my other installations (that work).

My best theory (at this point) is that setting Permalinks attempts to rewrite the .htaccess file but only goes half way — deleting the contents but not adding the necessary code. However, I have no theory as to why this might be happening.

Any other suggestions or theories would be welcome !

Hmmm – so the answer was not that easy. The .htaccess files are directory-level configuration files so the 500 error is probably just an indication that the server doesn’t like the .htaccess configuration (either at the /blog/ level or at the parent level.)

Are you responsible for the entire site or is there another server administrator you can coordinate with? If there is another server administrator, there are logs that might tell you something (see this thread: https://www.ads-software.com/support/topic/internal-error-500-501?replies=11)

Assuming you are okay with temporarily creating problems for the top level site, then 2 other experiments might be worthwhile. 1) Leaving the .htaccess file as you have changed it, rename the higher level .htaccess to .htaccessOLD and try to access the blog URLs. 2) Then (leaving the upper level .htaccess renamed, remove or rename the /blog/ .htaccess and repeat to see what happens. After this, be sure and change the upper level .htaccess back to its original name.

(Just in case you don’t already know this — All this is intended to test the theory that one of the RewriteRule directives in your high level .htaccess is redirecting the URL you are entering to that page we are calling the 404 page.)

No – if you can’t find an .htaccess file in your wordpress directory then the logical test is to create an .htaccess file (for the time being just copy the one I gave you) and then put that into your /blog/ directory.

See if that works (before you try renaming the higher level .htaccess.)

So the general site is running another CMS – and this .htaccess is for that. The directives in this .htaccess affect all subdirectories below it — including your blog folder. But you also have an .htaccess file in your blog folder (with directives that control only what’s in the blog folder). I would check that to make sure it looks reasonable. It should be shorter and should look something like this:

# 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

If your blog’s .htaccess is empty (i.e. just has the # BEGIN WordPress and # END WordPress comments) then try just copying and pasting the code I have above into your blog’s .htaccess to see if that works.

However, if your blog’s .htaccess looks okay, I would probably briefly rename the higher .htaccess file (to something like .htaccessOLD) and, after clearing your cache, again try accessing your blog. If you get the same result, then you can at least rule out the “parent” .htaccess as a cause.(After this experiment be sure and rename the “.htaccessOLD” back to “.htaccess” !)

One more point – the page you go to in all cases is apparently also the default for 404 errors. So, if you haven’t already, make sure you get into FTP and check to see if your blog directory and wp-login.php files are where you think they are.

Postname.

At first I thought actually changing the setting was causing the .htaccess code to be deleted (changing permalinks can cause .htaccess changes) but the puzzle is that the .htaccess file becomes altered before I ever get into the settings. It happens when I click on the “Permalinks” link in the left sidebar. Makes no sense but I ran several trials to confirm it. After each trial I had to go into FTP, edit the .htaccess and put the code back in that was deleted. Correlation at least… whether it’s cause and effect I don’t know ??

Well, when you go to https://www.simicdom.com/blog/wp-login.php, clearly the wp-login.php page is not being displayed (unless it has somehow been overwritten…) Might be worth checking (or posting your .htaccess file.) I’m no .htaccess expert but it seems worth a look.

Yes esmi – using a child theme.

And YES paulwpxp ! You win the brass ring – that’s exactly what I was looking for !

Thank you so much ??

Have any of you come up with a solution for a simple blog subscription solution ? I thought this would be simple !@#$!%&!

Thanx, Glenn