gsgltd

Hi again,
The problem on my site has been resolved. I deactivated Akismet, an anti-spam plug-in that addresses spam via the Discussion settings, and no longer get the 403 message. When I re-activated it, the Discussion settings still worked.
I can’t say for sure that this was the problem, but it seems likely, since no other changes were made to the plug-ins, except updates.

My host offered to disable the ModSec too, and I declined. They seem sure that this is the cause of the 403 error.

There are no errors showing in the cPanel error log.

Which files would have to be have ModSec turned off in order for the discussion settings to work?

All my WP files seem to have 0644 permission, except for config, which is 0600.

I discovered that ALL the WP sites I administer, which are on this same host, now have this problem, although they were fine on the install. One site had WP installed just two weeks ago, and the discussion settings worked fine then.

The host has no solution except to remove the security that protects the sites from malicious attacks.

Could Akismet be the problem, since it does monitor comments? All my sites are using it. However, it is not currently activated on one site, because I removed the multi-site option and had to manually re-activate all the plug-ins. The 403 error is still there. I will try deactivating it on the other sites.

I am having this problem also. I have the latest WP and this was a fresh install into /wp directory. I have never had this problem with any other sites, all using the same host. I do have this site on network admin, unlike other sites.

My 403 error is server-generated, not WP, but my host cannot locate the problem and says that the discussion settings work for them.

This is the message:

403 Forbidden
The page you are looking for might have been removed, had its name changed, or is temporarily unavailable.

Any help would be much appreciated.

I just realized what the problem my be. I changed the WordPress URL as well as the site address. I can’t login, but I do have access to mySQL.

Sorry – now marked as resolved. Not sure what you mean by “mark on the front”. Please explain.

Thanks.

Yes, thanks. The new WP update resolved all outstanding issues.

Thanks.

Yes, I will fix any errors. Haven’t spotted any others.

I’ll try deactivating, but reverting to a generic theme is not an option because of the complexity of our site.

I checked the support forums under “error” and it seems as if a lot of plug-ins are having this issue, and others are having the custom fields problem as well.

Looks to me like a problem in how html manifests. Could it be a theme problem?

Thanks for your reply.

I noticed that the ” was missing after gallery, but since this code and page hasn’t been edited in years – and worked fine until very recently, the error could not have been there before.

As to the order – this dictates how the images are shown, in this case, last posted at top of gallery. This has not changed in years either. I checked other galleries on the site, and none are working. Most just use a short category code, now visible.

I tried different configurations of the code, as suggested, but that hasn’t fixed the problem.

It appears that custom field inserts are also malfunctioning. The only thing showing is [HTML1] etc.

This would seem to be a WP problem, rather than a plug-in issue.

Any suggestions?

I did read your tutorial first, but misunderstood. So I can’t make either dimension larger than the default slider – is that correct?

Thanks so much, Josh! That fixed it. I’ll remember that in future!
Sorry for posting the question incorrectly too.

I have a similar problem, except that my slider was working fine until very recently. Now I’ve lost the bottom of some of the images. Could this be a problem resulting from a WP update? We’re using Magazine Premium, but I don’t think there’s been an update for the it recently. There has been a couple of WP updates lately.
I’ve tried adjusting the Meteor slide height and then deleting and uploading the image again, as suggested, but it’s still cut off.
I find the revamped WP Media Library a bit confusing – but did try to re-scale the images, but that didn’t make any difference either.

Further to the menu editor problem, the .htaccess file(s) do not seem to be causing the 403 error. I disabled them both (in root and /wordpress) and the menu error still occurred, so I enabled them again because they’re needed for internal site links.
Unfortunately, I don’t know how long this error has existed. Menus have not been changed recently. Categories are also not working properly and items posted are not appearing where they should.
Our site is https://www.tidechange.ca and we’re using the Magazine Premium theme. We haven’t upgraded yet to WP 3.4.2.
Anyone have any suggestions?

I’m having a similar 403 problem with my menu editor – i.e. I can’t save it and get this:

“HTTP 403 The Default index.html file could not be found
The page you are looking for might have been removed,
had its name changed, or is temporarily unavailable.”

The site is https://www.tidechange.ca. We have WP installed in /wordpress, but originally had it in the root on another host a few months ago. Haven’t needed to revise the menu until now.

Is this a server issue or a .htaccess code problem? The other editors for both WP and the theme (Magazine Premium) seem to be working properly. I don’t want to attempt a revision of the .htaccess as haven’t seen this exact problem anywhere, so if anyone can help, I’d much appreciate it.

Our current .htaccess file in /wordpress looks like this:

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

# END WordPress>

The one in the root directory seems to be identical:

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

# END WordPress

Here is the error message we’re getting …

**HTTP 403 – The Default index.html file could not be found
The page you are looking for might have been removed,
had its name changed, or is temporarily unavailable.**

I’ve narrowed the problem down to the .htaccess file, but since I’m not very versed in code, would appreciate it if someone could tell me what line(s) to add to eliminate this problem. Our current .htaccess doesn’t mention the index.html file.

Thanks