IainPurdie

Yes, just moved to Krystla over the weekend.

I’ll try tinkering when I get home (much) later tonight. I also suffer from my work filtering things out! Including access to my host’s control panel ??

Again – thank you.

Thanks for getting back to me, Paul – appreciated. I’ve checked each of your points:

1) A mixture! If I create a new post and name it, then click “Save” (e.g. draft) then the post is created and the title saved and the 403 displayed… but that’s it. No content, images, category, etc. If I click Publish, I get the 403, but the post is *not* published. I would say that falls under “failing to update the post”.

2) Did a quick product search (Author name Gibson) and it works fine.

3) PHP 5.6.33

Iain

Checked the logs and nothing sticks out, I’m afraid.

It is weird as we simply copied the filesystem as is from one server to another. Permissions are all the same, plugins the same… It’s definitely not clashing with another plugin as I enabled them only one at a time until I hit the one that was the cause.

Definitely befuddling! I’ll check server logs if I can find them (new system so everything has moved) and see if I can spot anything.

And, yes, plain vanilla plug-in.

Iain

I stripped the plug-in out via file manager on the host’s control panel and simply haven’t re-installed.

Will have a shot in a while. I’m backing the site up at the moment!

I did try renaming the folder, but it didn’t help. Could be it was just cached and I needed a little more patience ??

Hey Amber,

Thanks for the reply. Thing is, as an Editor I can upload files with no issue. If the exact same file is uploaded by a Contributor then the above errors are given. This can’t be down to a server setting, surely, as the server itself doesn’t differentiate between WordPress logins.

Iain

Thanks, Mike – here’s hoping it’s just a coincidence that something else glitched and FSCF just happened to catch it!

Just a follow-up/FYI. I installed Easy Update Manager to prevent auto-updating of this plug-in.

a) connection to WP’s repository timed out so I have to download the file as a ZIP and upload. Couldn’t do it within the “Add New Plugin” section

b) Installation succeeded, but I was stuck in Maintenance Mode again afterwards.

Could be other issues making this a problem. Major difference was that the new app *did* install despite .maintenance not being removed afterwards, whereas the new update to FS Contact Form fails to install and leaves me in the same situation.

Takis,

As always, I appreciate your feedback! A manual change isn’t the end of the world and we’ll see if I can get it working that way – the only annoyance is Adaptive Images “nagging” me within WordPress as it doesn’t think the changes have been made!

We’re looking at moving servers sometime in the near future and when we do it could be an opportunity to do a fresh install rather than just copying over. At that point, I think we’ll be sorted.

Cheers!

Iain

Takis,

Apologies for taking so long to respond – it has been one of those weeks!

Yes, I spotted in the codex when I was looking that my htaccess file script didn’t match. However, this is what’s been in use for years, now.

I changed my script to the “new” version (obviously changing the “mysite” references) at which point the only page which would load became my index/home page. Every other page gave a “The requested document was not found on this server” error.

I can only assume that the way WordPress handles subdirectories has changed over time and we’re still using an updated version which relies on an older system ??

Ah, wait…

Once I do that, the site works fine but every time I go to the dashboard in WP I get a red alert at the top of every screen:

Adaptive Images Error — The .htaccess file is not updated
The Adaptive Images settings are saved, but the .htaccess file was not able to be updated yet.
Please try to save the plugin settings once again in Adaptive Images Settings. If the problem persists, then you should contact your system administrator and inform them about the issue.
The .htaccess file permissions are: /var/www/vhosts/moshville.co.uk/Moshville/.htaccess => -rw-r--r--.

If I then go to the settings and save them, the original Adaptive Images code is added to .htaccess *but doesn’t replace the edited section*. That is, I end up with two copies of the settings in .htaccess and the most recently saved one seems to overrule my edited version and the site breaks again ??

Yes – activated Adaptive Images, edited .htaccess and removed the superfluous “/wordpress” and it works fine ??

Oh – I’m looking at that and thinking I *may* have spotted something:

RewriteRule \.(?:jpe?g|gif|png)$ /wordpress/wordpress/wp-c....

Pretty sure there’s an extra “/wordpress” there.

Takis – no problem, a shame not as many plugin authors are as attentive ??

For giving WP its own directory, I have checked my .htaccess and the appropriate lines I have are similar to those in the Codex document (though not identical). I set the site up several years ago so perhaps things have changed? The ones I have in place are:

# 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

Adaptive Images adds the following:

# BEGIN Adaptive Images
#=======================

<IfModule mod_rewrite.c>

    RewriteEngine On

    # Watched directories
    RewriteCond %{REQUEST_URI} /wordpress/wp-content/uploads [OR]
    RewriteCond %{REQUEST_URI} /wordpress/wp-content/themes

    # Redirect images through the adaptive images script
    RewriteRule \.(?:jpe?g|gif|png)$ /wordpress/wordpress/wp-content/plugins/adaptive-images/adaptive-images-script.php [L]

</IfModule>

# END Adaptive Images