Forum Replies Created

Viewing 15 replies - 76 through 90 (of 349 total)
  • @

    The next step would be to turn on WordPress debugging and see what errors show up. That can help identify possible problem. You can read more here:
    https://codex.wordpress.org/Debugging_in_WordPress

    Basically, you’ll need to add the following code to your wp-config.php and make sure you remove define( 'WP_DEBUG', false ); that’s already in there.

    // Enable Debug logging to the /wp-content/debug.log file
    define( 'WP_DEBUG_LOG', true );
    
    // Disable display of errors and warnings 
    define( 'WP_DEBUG_DISPLAY', false );
    @ini_set( 'display_errors', 0 );
    
    // Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
    define( 'SCRIPT_DEBUG', true );

    This should create debug.log file inside /wp-content directory. If it’s not generating debug.log file, either plugin or theme is causing an issue that prevents it from generating log file. That’s an issue we can deal with if it happens. For now, see if you can get debug.log file to generate and show errors.

    Try modifying search query:

    add_filter( 'pre_get_posts', 'cpt_search' );
    
    function cpt_search( $query ) {
    	
        if ( $query->is_search ) {
    	$query->set( 'post_type', array( 'post', 'page', 'cpt1', 'cpt2' ) );
        }
        
        return $query;
        
    }

    Just update array with your custom post types.

    I did notice that issue on your website, but it wasn’t limited to visiting homepage from Google. When I tried running performance test on it, it timed out. You can try doing it yourself, using https://tools.pingdom.com/

    I would recommend disabling Wordfence temporarily, and testing to see if this issue goes away.

    I noticed your server is LiteSpeed, which is known to have issues with Wordfence. This may be the result of that. You can get some info and possible fixes here:
    https://www.wordfence.com/help/advanced/system-requirements/litespeed/

    But, as I said before, try turning WordFence off and see if this issue goes away.

    You can just force login for everyone. We use it for company’s intranet, so no one can see what’s inside but logged in users. And the feed should still work just fine. I have not tested it for podcasting purposes, but give it a try and see if that works for you.

    https://en-ca.wordpress.org/plugins/wp-force-login/

    ^V

    Glad I could help.

    ^V

    Happy to help. Glad to hear you were able to fix it on your own. I wouldn’t worry about the error, it’s a “notice” which is for informational purposes. It doesn’t break anything, or nothing is broken.

    Make sure to turn off debugging in wp-config.php file. If you leave it on, it will quickly inflate debug.log. It should be turned off unless necessary for troubleshooting.

    Make sure to mark this thread as “resolved”.

    ^V

    You might want to re-install all core files. We’ve seen this happen with some GoDaddy customers. After most recent update, they started getting this error.

    You’ll need to delete core directories/files and re-upload a fresh set via FTP/SFTP.

    Do you know how to do this? How to use FTP/SFP? I can try to walk you through this.

    ^V

    Hey @travisburch,

    WPEngine’s preview URL needs to be updated throughout database. General settings is only one place where it’s used.

    First, make sure you read through WPEngine’s help article:
    https://wpengine.com/support/going-live/

    Second, I would also contact WPEngine support. They should be able to help you fix this.

    Third, if you plan on doing this yourself. Make sure you backup your database before doing anything. Then, install and activate Velvet Blues Update URLs plugin.

    You will want to enter the following:

    OLD URL: travisburch.wpengine.com
    NEW URL: travisburch.com

    If you’re copying and pasting URLs from above, make sure there’s no spaces at the end of each URL. Sometimes you might copy empty space selecting text.

    Lastly, check all boxes for Step 2. And click Update URLs.

    That should do the trick. Please make sure you backup your database before updating URLs. If something goes wrong, you can easily recover database.

    ^V

    Plugin Contributor ProjectArmy

    (@supporthero)

    Thanks for letting us know. We’ll review it and will get the bug fixed. Thanks.

    • This reply was modified 8 years, 2 months ago by ProjectArmy.
    Thread Starter ProjectArmy

    (@supporthero)

    I believe I got to the bottom of this. It’s the multi-step functionality that’s breaking your spam detection. “Next” button in each step triggers submit(), so your submit() is being triggered too early and it never appends your input at the end.

    The way to fix this is to use on(), so the the input is appended on the last submit:

    $(document).on('submit', gforms ,function(){

    This would replace the following line:

    $( gforms ).submit(function() {

    I hope you can test it and implement the fix. Thanks.

    It doesn’t disable compression in reality, it sets the quality to 100 which means it still performs compression. With jpegs, the more you use them the more quality they lose over time. They lose quality every time they go through optimization or saving (source). If you open jpeg in Photoshop, and save it without any edits, it will lose quality. With WordPress compression it’s the same. Every time you regenerate images in WP, they lose quality. It’s just the way jpegs are made.

    Uploading images via FTP would be the best option to preserve quality.

    Forum: Fixing WordPress
    In reply to: Login problem!

    It looks like your site had an error establishing connection to the database now.

    Did anything happen before you began having issues logging in? Like new plugin activated, or updated plugins, WP core, etc. Or did it just start happening out of nowhere?

    Try to login to your site using Chrome Incognito mode, or Firefox Private browsing mode. Just to make sure it’s not a browser setting issue or some rogue cookies/cache that wasn’t cleared/deleted.

    Thanks.

    What payload does Sucuri still see? They usually tell you the name of the payload from their database.

    ^V

    If all the sites load slowly, and they use different themes/plugins then the common denominator is hosting. Bluehost is crappy to begin with, and support is unhelpful as you’ve found out.

    But, we can test it and see what the issue is.

    Install this plugin, it runs tests on your hosting so we can see what they are:
    https://en-ca.wordpress.org/plugins/mywebtonet-performancestats/

    If you could either copy/paste the results, or take a screenshot so we could take a look that would be great. I’m pretty sure your MySQL response time will be very high.

    ^V

    Hi Lindsay,

    I have a feeling you may have a security plugin active, like iThemes Security. One of the options there is to hide error messages, that’s why it’s empty.

    I would try clearing your cache first, sometimes cookies can prevent successful login. If that doesn’t work, you would need to disable security plugin via FTP. Some security rule may be triggered, blocking your access. It may be not your location, but rather wifi/network that triggered some security rule.

    FYI, your website is showing 503 error.

    ^V

    • This reply was modified 8 years, 3 months ago by ProjectArmy.
Viewing 15 replies - 76 through 90 (of 349 total)