Forum Replies Created

Viewing 15 replies - 16 through 30 (of 86 total)
  • Thread Starter mpedersen

    (@mpedersen)

    I can tell you that a) the site has been running for years without issues and b) while interesting, resaving the permalink structure (without changes) did not resolve the problems with the Event Calender plugin.

    Thread Starter mpedersen

    (@mpedersen)

    Gotta be honest here, I’m not interested in posting the full report publicly here; it exposes a lot of information. I’m happy to provide the key info you might need that doesn’t reveal any potentially sensitive info.

    What I can tell you is that nothing is “red” on the status report, all green.

    Searching the woo logs, there are no error logs, fatal error logs, or anything specifically coming up when I search for “error” in the available logs. All I see are various payment logs, and a testlog.log.

    Tell me what info you’d need.

    Thread Starter mpedersen

    (@mpedersen)

    Please note, after posting this, I noticed version 6.0.6 was running, and an update was needed. An update to 6.0.6.1 was applied, but the problem remains.

    E.g.

    https://www.amazonasmagazine.com/events/list/?tribe-bar-date=2023-03-01

    Thread Starter mpedersen

    (@mpedersen)

    So..this problem keeps coming and going. It appeared that clearing transients would restore things when I ran that tool, but today it happened while working on the site, and clearing transients did NOT resolve the issue.

    The problem continues, randomly, and in different parts of Woocommerce at different times. E.g. right now, I can see the main shop page, but when I go into the sub pages, there is “no results”. It also seems to affect OTHER Woocommerce pages as well; for example, earlier this month, it sounds like the order success page was generating this error message, causing people to resubmit their orders!

    Pretty frustrated with this random failure of Woocommerce, particularly since it’s not something I can simply replicate on demand!!!

    Thread Starter mpedersen

    (@mpedersen)

    I believe this problem was resolved through various updates that have been release and applied, so yes, perhaps fixed without any intervention on my part.

    Thread Starter mpedersen

    (@mpedersen)

    Looking at all the unanswered stuff, and the security type problems that seem to plague this formerly good plugin, I’m trying out https://ww.wp.xz.cn/plugins/redirection/ – imports the redirects from this one, so that’s a start.

    Thread Starter mpedersen

    (@mpedersen)

    OK, potentially the conflict was from installing an older copy. I’ve reinstalled from WP on multiple sites and re-scanned, and Wordfence is now happy. Not sure where/what the “hack” came from, but it showed up on all sites it seems.

    Thread Starter mpedersen

    (@mpedersen)

    Thanks for the update Erica. However, the 6.0.2 version actually crashed our site completely earlier, so we had rolled back to 6.0.1.

    (see https://ww.wp.xz.cn/support/topic/site-crashing-3/ )

    I see there is a 6.0.3 version out now; if that fixes the problems that were causing the crashes in 6.0.2, then I should upgrade, but honestly I’m very hesitant at the moment.

    Thread Starter mpedersen

    (@mpedersen)

    And, once the scan completes, the version I uploaded from WordPress is still having the original “hacked” messaging.

    Thread Starter mpedersen

    (@mpedersen)

    Reviewing the “differences”, it appears that the “ad supported network” code is also back! I’m in the process of investigating the copy of the plugin that I downloaded to verify:

    160	   function ppr_notice_hook() { 
     	 	161	       add_filter( 'plugin_row_meta', array( $this, 'ppr_add_notice' ), 10, 2 ); 
     	 	162	       add_action( 'upgrader_process_complete', function ( $upgrader_object, $options ) { 
     	 	163	           $our_plugin = plugin_basename( __FILE__ ); 
     	 	164	 
     	 	165	           if ( $options['action'] == 'update' && $options['type'] == 'plugin' && isset( $options['plugins'] ) ) { 
     	 	166	               foreach ( $options['plugins'] as $plugin ) { 
     	 	167	                   if ( $plugin == $our_plugin ) { 
     	 	168	                       update_option( 'ppr_show_notice', 0 ); 
     	 	169	                   } 
     	 	170	               } 
     	 	171	           } 
     	 	172	       }, 10, 2 ); 
     	 	173	   } 
     	 	174	 
     	 	175	   function ppr_add_notice( $links_array, $plugin_file_name ) { 
     	 	176	       if ( strpos( $plugin_file_name, basename(__FILE__) ) ) { 
     	 	177	           if ( (! $this->ppr_show_notice && current_user_can('administrator')) || (! $this->ppr_first_install && current_user_can('administrator')) ) { 
     	 	178	               $links_array[] = '<div class="notice notice-warning inline">Quick Page/Post Redirect Plugin contains advertising support - by installing and/or using it, the plug-in will become part of an advertising-supported network. <br>The plug-in may be purchased without advertising support at <a href="https://anadnet.com/pro/" target="_blank">anadnet.com/pro/</a>.</div>'; 
     	 	179	 
     	 	180	               update_option( 'ppr_show_notice', 1 ); 
     	 	181	               update_option( 'ppr_first_install', 1 ); 
     	 	182	           } 
     	 	183	       } 
     	 	184	 
     	 	185	       return $links_array; 
     	 	186	   } 
     	 	187
    Thread Starter mpedersen

    (@mpedersen)

    Keep in mind, this is a hosting company support agent & often times they are wrong. The agent simply informed me that wp-cron.php was getting hammered with requests: “It also seems that the wp-cron.php file is the one that is having the most requested on the website.”

    It was to the point that the entire site came crashing down. Ultimately, rolling back the plugin fixed things (although as I reported separately, there are apparently some display problems with 6.0.1 that one of our editors found). I see that 6.0.3 is out, but I’m understandably hesitant to install it, even more so since you tell me this problem hasn’t been replicated (and thus, not addressed).

    If there is something more specific I might be able to obtain, please ask and I’ll try to get it for you.

    Thread Starter mpedersen

    (@mpedersen)

    Rolling back to 6.0.1, the site runs normally, all other plugins are up to date, our theme is held back one version because their most current update creates layout issues in WooCommerce. So…definitely something wrong with 6.0.2.

    Tagging along, as the update to 6.0.2 has caused our site to immediately grind to a halt and crash as well.

    Thread Starter mpedersen

    (@mpedersen)

    Sorry, apparently some “threat mitigation” at the hosting company is causing SOME inbound emails to be blocked, and I wasn’t aware of the follow-up.

    To your earlier questions:

    1. I believe I only had a couple of customers set up as “wholesale”. It turned out that wholesale customers were much more interested in order off an Excel spreadsheet than logging onto a website to navigate and make their purchases.

    2. At this time there are 260 published products in the WooCommerce store. Another 20 or so as drafts.

    • This reply was modified 4 years, 2 months ago by mpedersen.
    Thread Starter mpedersen

    (@mpedersen)

    On the basis of your response, I threw the site’s theme over to 2022 and reactivated the wholesale price plugin. The simple process of activating it took like 10-20 seconds. The site performed OK while 2022 was running, but even deactivating the plugin again took another 10-20 seconds….other plugins only take a second or two for the site to respond.

Viewing 15 replies - 16 through 30 (of 86 total)