webofcreativity
Forum Replies Created
-
I just came across this issue as well, and the above did not help. Any other fix here?
Thank you.
It was showing up in order history but not sending the email.
I’ve set them up on a new SMTP setup, so hopefully it helps.
Thank you for responding.Forum: Plugins
In reply to: [DIVI Enhancer - DIVI Modules and Options] Not working with latest updateYes, it is working now.
Thank you.Forum: Plugins
In reply to: [DIVI Enhancer - DIVI Modules and Options] Not working with latest updateI’d like to update if it will work.
Forum: Plugins
In reply to: [DIVI Enhancer - DIVI Modules and Options] Not working with latest updateI rolled back. and it works on the rolled back version.
Forum: Fixing WordPress
In reply to: Password Field is disabledDidn’t work for me =\
Forum: Fixing WordPress
In reply to: Password Field is disabledThanks but we are using the most up to date browser.
The main browser my client is using is Chrome 79.0.3945.88, but she tried as well with other browsers on her computer. I should note that on my own computer I was able to log in fine.
As a temporary fix I downgraded wordpress, and she is now able to log on. But I would like to get to the bottom of this, so I can keep wordpress up to date.Forum: Fixing WordPress
In reply to: Password Field is disabledIs there any other solutions people found? I deleted Jetpack, disabled all plugins and went to default theme, and was still having this issue. I should note that it does not happen for everyone – on my own computer it is working fine. On my client’s computer the password field is disabled no matter what browser she uses..
Can anyone help?!Forum: Fixing WordPress
In reply to: Password field disabled on wp-admin (not jetpack)@sumanm I saw that post already, and full deleted Jetpack before writing this post. Jetapck is not on my site, and I don’t have any caching plugins installed. Besides, I had put my site on ‘safe mode’ to see if it was a plugin causing the issue, but the issue persisted. I also switched to a default theme, issue was still there.
So it doesn’t seem to be a conflict…