Forum Replies Created

Viewing 15 replies - 1 through 15 (of 39 total)
  • I had this problem as well. I went back to v2 so I could login. Hopefully, this is an issue he can address.

    Nope, I Just got the email again.

    from: noreply@wordpress.org

    Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site and notifies you with this automated email.

    In this case, WordPress caught an error with your theme, Divi.

    First, visit your website (https://XXXX.com/) and check for any visible issues. Next, visit the page where the error was caught (https://XXXX.com/wp-login.php) and check for any visible issues.

    Please contact your host for assistance with investigating this issue further.

    If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigates further.

    Got a code snippet I could inject into functions.php or another workaround. To be honest with you I shouldn’t even worry about it. I have a custom login page, so wp-login.php is not needed.

    Thank you,
    Syxguns

    I will update if I get another email from WP

    Thank you Gioni for the answer. I have always used Wordfence in the past, and do like what it provides. However, Cerber has a lot of features that Wordfence does not have. I have not installed Wordfence this go around and am running Cerber and Fail2Ban. From my perspective, and I am not a security expert, I feel that the combination of the two plugins for security and hardening is enough.

    Now I could be wrong but would be adding Wordfence to the mix be overkill? Because nobody can get into my site by conventional methods. wp-login.php and wp-admin are either closed off or you need the new link for admin. The other day I had to let someone get onto my site to investigate an error I was experiencing and they could not get in without me disabling Cerber. I feel confident that Cerber is providing the security that I need, meaning no one should be able to access anything and a brute force attack will get them kicked off so they should give up trying. Would you agree that I should be fully protected running Cerber and Fail2Ban?

    In case you are not familiar with Fail2Ban here is a link: https://wordpress.org/plugins/wp-fail2ban/

    Thank you,
    Syxguns

    Thank you, that seems to have fixed the issue I was having. Everything seems to work great now.

    Syxguns

    I currently running Version 11.2.2 of Front-end PM, on a server running Nginx, Varnish, Apache, and PHP version 7.2.27. I have the following files in the database:

    • wp_fep_attachments
    • wp_fep_messagemeta
    • wp_fep_messages
    • wp_fep_participants

    But for some reason in WordPress I still have a message that says, “Front End PM needs to database update”. When I select to proceed and start the update I am greeted with, “Front End PM update: You cannot update from your current version”.

    The database uses a different prefix than wp, but I don’t see where that would be an issue. The wp_fep tables are for Front End PM correct? I guess I could try removing the plugin, and manually cleaning the database of the above-mentioned tables and try from scratch. That might fix the issue, but I’m not certain.

    Do you have another suggestion or a way for me to manually update the database? I’ll wait back to hear from you before I proceed to investigate further. The site is still in development, but I would love for this plugin to work for me.

    Thank you,
    Syxguns

    BTW- I’m running PHP-FPM but I can change my PHP to an older version if you need me to.

    Yes, there is not a problem with the plugin. It ended up being a server-side issue that I was able to correct. Now the plugin is not causing the 500 error. Thank you for reminding me of this post I made. The plugin is working at 100%.

    Thank you,
    Syxguns

    Syxguns

    (@syxguns)

    It seems that I made the error in this case. The following link I placed was incorrect.

    auto_prepend_file = ā€˜/home/XXXX/public_html/wordfence-waf.phpā€™

    Should have been:

    /home/XXXX/public_html/wordfence-waf.php

    That corrected my issue.
    I wish WordPress would allow me to edit the above post so you didn’t have to read it all.

    Syxguns

    Forum: Reviews
    In reply to: [Elevate SEO] The Best!

    Thanks for using Elevate ā€“ and appreciate you including it in your videos

    Not a problem at all. I’ll probably have the video online in a week depending on work conditions. I’ll post a link to it here if you like.

    Syx

    I have the exact same error after the update to PHP 7.3.0. Searching for a solution as this plugin has not been updated in 3 latest releases.

    • This reply was modified 1 year, 1 month ago by Syxguns.

    @vasyltech
    I’m thrilled that you loved the review. Quick question, I have used the AAM to hide certain things on the Admin Bar (Tool Bar now I guess) but it only works for back-end Admin page? I have a couple of features that are listed on a clients tool bar on the front-end. They do not have access to it, it pulls up a page access denied. That doesn’t look very professional.

    I can create a custom code for each user independently but if I had front-end features on the tool bar in AAM that would be perfect. Maybe that might make the list.

    All the best!
    Syxguns

    wfalla,
    I did not receive an error, just it would freeze and not allow you to crop and save the image. However, every time you would upload again, my media gallery would save another copy of the image.

    I placed the firewall back into learning mode and I was able to update the user background image and the avatar image.

    Thank you for that great little tip! I would think that I should be set now.

    Love Wordfence, I would purchase it if I didn’t have so many sites. If I ever happen to get a site that is making me any money then I will definitely be making a purchase.

    Side note: I build websites for others and always include the free version of Wordfence. I would hope that might drum up a little business for the fantastic security that you offer us.

    Thank you once again!
    Syxguns

    Thank you for getting back with me on this.

    Basically I did manage to figure out what the problem was. It is my Wordfence security that is causing the issue. So it is not a problem with ProfileGrid. I just have to figure out what setting I need to deactivate in Wordfence to allow users to upload images.

    If you happen to know the answer to this that would be great, but I’m going to contact them, or they may have an article about the change that you would need to make.

    Many thanks, Hopefully others may see that security can sometimes be the cause of the problem.

    Syxguns

    Following, would like to see a way to get even the admins user profile info in. Until then I will create a new user for testing.

    @imagely,
    I understand that it might be my theme but I decided to give you a little information with pictures. It might help narrow it down.

    Front-end Customization
    Back-end Customization
    Customization Panel
    Error Code

    In the error code I know that it also mentions WooCommerce ShopDock but that error is not there when I disable NextGen Gallery.

    Here are some other front-end development platforms:
    Beaver Builder
    Elementor
    Divi
    Page Builder by SiteOrigin

    I am not able to test with these other themes as I do not use them. I know a lot of developers that do so I thought I would give you a heads up. If you need a place to run testing with Themify just let me know and I will set up a demo site for you to test with.

    I’m going to hopefully be able to get your plugin to work for me, as I’m doing a list of great plugins on my youtube channel. I will post a link to it in this thread for you.

    I got it figured out. It seems that I had an outdated version of white label branding on my site. I keep certain plugins that I use a lot saved on my computer to save time on new sites. The plugin was not activated, but for some reason the code behind the plugin was causing Wordfence problems.

    I should have remembered that even though a plugin is not activated, the code still resides within your WordPress directory.

Viewing 15 replies - 1 through 15 (of 39 total)