Ash Whitney

Hello Anjali

Thank you for your prompt response and advice. I found some incorrect code in one of the snippets we’d added to the site as you suggested.

Kind Regards, Ash

Thank you to Arnan for support via the ticket system for AdRotate Pro. For anyone with the same issue, it turned out to be a conflict from another plugin named ‘Countdown Timer’ as when disabled the date field and picker worked ok in AdRotate.

Hi @drwpcom

That’s most appreciated thank you.

Regards, Ash`

Hi @drwpcom

Thanks for your reply.

Yes, I have more than 30 variations for the affected products.

Could you please repost the link to the code snippet you mentioned as the original link is pointing to my website rather than the thread you mentioned.

Regards, Ash

I haven’t found a solution yet unfortunately. It seems to be something recently introduced as I’ve not had the issue before on the site.

I’m seeing the same issue as you across different browsers, but also on mobiles.

Thanks for your reply t-p

Unfortunately the last entry in the error log was from 11 July, so no clues relating to the issue I’m seeing over the last couple of days.

Hello Venkat

Thank you for your time and advice.

The login redirect issue does seem to be related to the Easy Updates Manager plugin I’m afraid.

I can access the wp-login page with no issues, enter my username and password, but on clicking the login button there is a delay follwed by the redirect error message from my original post.

I’ve deleted and reinstalled Easy Updates Manager. I’ve also disabled my plugins one by one to try and isolate the issue, but I’m only seeing this issue when Easy Updates Manager is enabled – as soon as I disable it, the login works fine.

Regards

Ash

Hello John.

Thanks for the update and for looking in to this issue.

Regards, Ash

Hello Job.

Thanks for your reply. No, we’re not using Amazon S3, but are hosting the downloadable files on our own hosting account on a different domain to the WooCommerce site we’re running – which we’ve been doing for years without an issue.

Regards, Ash

After upgrading to 4.9.1 the issue still existed on my site (couldn’t save functions.php via the dashboard).

However, I deactivated all my plugins and found that I was then able to edit and save functions.php in my child theme.

Obviously then suspecting a conflict with a plugin, I reactivated them a few at a time, each time checking that I could still edit/save functions.php (which I could).

Upshot is that after doing this I failed to find a conflicting plugin, and ended up with exactly the same plugins activated. I made no configuration or setting changes to any of the plugins – other than having to remake the connection to the Jetpack plugin.

This may be of help to anyone with the same issue.

Hello James

Thank you for your reply and link to the plugin.

Unfortunately the plugin didn’t resolve the issue for me – I tried it uploaded as a plugin and then adding the code directly to functions.php (via FTP).

Screen capture here

Regards, Ash

Will do, thanks @sterndata

Regards, Ash

In addition to my previous post:

The issue also exists using the 2017 theme.

The HealthCheck plugin reports the filesystem permissions as follows:

The main WordPress directory Writable
The wp-content directory Writable
The uploads directory Writable
The plugins directory Writable
The themes directory Writable

What I’ve also seen is that the WordPress dashboard under APPEARANCE > EDITOR doesn’t recognise any new files uploaded to the child theme directory. For example, I uploaded a file named functions-test.txt to the child theme directory, but there’s no reference to it in the dashboard (screen capture here).

Regards

Ash

I have the same issue with two sites on the same server (NGINX environment) unfortunately as receiving the error message below when trying to save files like functions.php from my child theme.

Both are established sites that haven had any issues like this before the upgrade to 4.9

“Something went wrong. Your change may not have been saved. Please try again. There is also a chance that you may need to manually fix and upload the file over https://FTP.”

Understood. Thanks for the information.

Regards, Ash