etadmin
Forum Replies Created
-
Forum: Plugins
In reply to: [All-In-One Security (AIOS) – Security and Firewall] Failed loginWoooow. That was it! I saw that option but had no idea what it even was! Dang. That was a new one to me. Thank you!!
Forum: Plugins
In reply to: [All-In-One Security (AIOS) – Security and Firewall] Failed LoginsI still have an issue, but I’m gonna open a separate ticket. It’s a different issue.
Forum: Plugins
In reply to: [All-In-One Security (AIOS) – Security and Firewall] Failed LoginsI just enabled the IP restrictions for the login. Thankfully, we have a VPN. It just got crazy. Darn hackers. Go away.
Forum: Fixing WordPress
In reply to: Disabling forced FTP credentials for any updatesHey! I tried doing that. That was actually one of the first things I tried but it didn’t work either (should have said that), but the only way was with the proper permissions. 🙁 Thanks though!
Thanks @fpcorso! You totally pinpointed the issue. I think that plugin also has an update. The error went away when I updated the plugin.
Forum: Fixing WordPress
In reply to: Disabling forced FTP credentials for any updatesWoooow. I apologize. You’re right. I didn’t have the correct user setup across. So PHP does run as
www-data, but I didn’t put it across the project. Once I changed it, it worked like a champ. Really sorry about this guys! I appreciate the input! Closing this ticket.Forum: Fixing WordPress
In reply to: Disabling forced FTP credentials for any updatesWe are using Debian. We were using Gitlab for version control and I thought that was helping lock down the plugin updates with permissions. Even completely opening the plugin folder using 777 didn’t work.
Forum: Fixing WordPress
In reply to: Disabling forced FTP credentials for any updatesHey Steve, thanks for your reply!
I did confirm that www-data had permissions to that folder and all along until the project root. Wouldn’t changing 777 on the plugins take care of any permissions issues?
Ahhh that would make sense. I think we had some funky permission issues too. It’s fixed. That’s all I cared about. Thanks for the feedback though!
Changing some random folder permissions and re-creating the theme worked. -_-
After looking into this more, the inline CSS doesn’t get applied to mine. I don’t know if it’s a permissions thing. I’m still digging into it.
We are having the same exact problem. We have updated to the latest plugin and still can’t get it to look at the customed theme. We even reset the default one too. Help!