Title: Raspberryade's Replies | WordPress.org --- # Raspberryade [ ](https://wordpress.org/support/users/raspberryade/) * [Profile](https://wordpress.org/support/users/raspberryade/) * [Topics Started](https://wordpress.org/support/users/raspberryade/topics/) * [Replies Created](https://wordpress.org/support/users/raspberryade/replies/) * [Reviews Written](https://wordpress.org/support/users/raspberryade/reviews/) * [Topics Replied To](https://wordpress.org/support/users/raspberryade/replied-to/) * [Engagements](https://wordpress.org/support/users/raspberryade/engagements/) * [Favorites](https://wordpress.org/support/users/raspberryade/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 19 total) 1 [2](https://wordpress.org/support/users/raspberryade/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/raspberryade/replies/page/2/?output_format=md) * Forum: [Networking WordPress](https://wordpress.org/support/forum/multisite/) In reply to: [Images problem after upgrade multisite to 6.8 all over network except root site](https://wordpress.org/support/topic/images-problem-after-upgrade-to-6-8-all-over-network-except-root-site/) * [Raspberryade](https://wordpress.org/support/users/raspberryade/) * (@raspberryade) * [1 year, 1 month ago](https://wordpress.org/support/topic/images-problem-after-upgrade-to-6-8-all-over-network-except-root-site/#post-18422327) * This appears to be the same problem I later described in [this post](https://wordpress.org/support/topic/wp-6-8-upgrade-breaks-images-on-older-multisite-avoid-until-fixed/).( Sorry for the duplicate, I missed this thread when I was originally checking to see if it had already been raised). * From the same dev thread above, it’s claimed [here](https://core.trac.wordpress.org/ticket/63285#comment:7) that the problem “_only [affects] older multisites or multisites that have manually converted to use ms-files_” and [here](https://core.trac.wordpress.org/ticket/63285#comment:4) that “_looks like it will fatal on anything still using ms-files for media, so any WP multisite created before 3.5 and not manually converted after_“. * According to [this StackExchange comment](https://wordpress.stackexchange.com/questions/77270/turn-off-ms-files-php-after-network-setup),“ _in WordPress 3.5, ms-files.php was [disbanded completely](http://core.trac.wordpress.org/ticket/19235) for new installs_“, so presumably ms-files.php is legacy code which was never replaced for multisites that were first created before then? * 3.5 came out on December 11, 2012, and we were using multisite before then, which is presumably why we were affected. * Also note that “_I think we don’t need to rush 6.8.1 out the door_” so hopefully(!) this means there aren’t many users affected and waiting for a solution, but if you’re in that boat I’d hold off on the upgrade until it’s out regardless. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [WP 6.8 upgrade breaks images on “older” multisite- avoid until fixed?](https://wordpress.org/support/topic/wp-6-8-upgrade-breaks-images-on-older-multisite-avoid-until-fixed/) * Thread Starter [Raspberryade](https://wordpress.org/support/users/raspberryade/) * (@raspberryade) * [1 year, 1 month ago](https://wordpress.org/support/topic/wp-6-8-upgrade-breaks-images-on-older-multisite-avoid-until-fixed/#post-18422286) * My apologies for missing this before opening this thread, but the same issue appears to have been already raised on the forum here:- * [https://wordpress.org/support/topic/images-problem-after-upgrade-to-6-8-all-over-network-except-root-site/](https://wordpress.org/support/topic/images-problem-after-upgrade-to-6-8-all-over-network-except-root-site/) * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [WP 6.8 upgrade breaks images on “older” multisite- avoid until fixed?](https://wordpress.org/support/topic/wp-6-8-upgrade-breaks-images-on-older-multisite-avoid-until-fixed/) * Thread Starter [Raspberryade](https://wordpress.org/support/users/raspberryade/) * (@raspberryade) * [1 year, 1 month ago](https://wordpress.org/support/topic/wp-6-8-upgrade-breaks-images-on-older-multisite-avoid-until-fixed/#post-18422174) * Yes, 3.5 apparently came out on **December 11, 2012**, and checking confirms that we already had more than one WordPress site running on that same installation on or prior to mid-2012. * I’d have thought there were quite a few people in the same boat. I mean, yes, the original installation was a long time ago now, but the site has changed significantly, been migrated several times and- importantly- been kept mostly up-to-date since then. It’s just that it’s never been rebuilt *from scratch* at any point because there was no obvious need to do so. - This reply was modified 1 year, 1 month ago by [Raspberryade](https://wordpress.org/support/users/raspberryade/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Site Kit by Google - Analytics, Search Console, AdSense, Speed] Site Kit automatically updated without being asked to do so?](https://wordpress.org/support/topic/site-kit-automatically-updated-without-being-asked-to-do-so/) * Thread Starter [Raspberryade](https://wordpress.org/support/users/raspberryade/) * (@raspberryade) * [1 year, 4 months ago](https://wordpress.org/support/topic/site-kit-automatically-updated-without-being-asked-to-do-so/#post-18248185) * [@adamdunnage](https://wordpress.org/support/users/adamdunnage/) * > Is there any particular reason you didn’t want to update the Site Kit plugin > for your site? * I never said that. * Frankly, the update itself in this case appears to have been no big deal and I’d have been happy to apply it manually. * However, I’d rather have been able to review and make such choices myself, which is why auto-updates were turned off in the first place (amongst other reasons). * And even that wasn’t my only concern- as I said, we administer this site and server ourselves, so when I see something doing something it shouldn’t be like this, it’s something I want to check out if nothing else. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Site Kit by Google - Analytics, Search Console, AdSense, Speed] Site Kit automatically updated without being asked to do so?](https://wordpress.org/support/topic/site-kit-automatically-updated-without-being-asked-to-do-so/) * Thread Starter [Raspberryade](https://wordpress.org/support/users/raspberryade/) * (@raspberryade) * [1 year, 4 months ago](https://wordpress.org/support/topic/site-kit-automatically-updated-without-being-asked-to-do-so/#post-18248100) * [@adamdunnage](https://wordpress.org/support/users/adamdunnage/) ; Thank you for your response. * > “If you already have the auto-updates disabled from the plugins section, it’s > possible that auto-updates are enabled on your hosting platform” * This is unlikely; we both installed and administer WordPress ourselves and it runs via Apache- which we also installed and administer ourselves- on a standard Ubuntu Server-based VPS, again, self-administered. * Also, we’ve never had this happen before, not even from the Site Kit plugin itself. * We have WordPress itself set to auto-update, but not any of the plugins. * All that Site Health tells us that’s relevant here is that some plugins require updating, mainly because they’re not set to do so themselves. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Enable jQuery Migrate Helper] Interference with error handling and console logging?](https://wordpress.org/support/topic/interference-with-error-handling-and-console-logging/) * Thread Starter [Raspberryade](https://wordpress.org/support/users/raspberryade/) * (@raspberryade) * [2 years, 11 months ago](https://wordpress.org/support/topic/interference-with-error-handling-and-console-logging/#post-16797893) * [@clorith](https://wordpress.org/support/users/clorith/); That at least confirms my original suspicion that it had something to do with interception of errors. * Thanks for the feedback and taking the time to take this on board (and thank you for your work on the plugin as well!) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Enable jQuery Migrate Helper] Interference with error handling and console logging?](https://wordpress.org/support/topic/interference-with-error-handling-and-console-logging/) * Thread Starter [Raspberryade](https://wordpress.org/support/users/raspberryade/) * (@raspberryade) * [2 years, 11 months ago](https://wordpress.org/support/topic/interference-with-error-handling-and-console-logging/#post-16794265) * [@mrfoxtalbot](https://wordpress.org/support/users/mrfoxtalbot/); Much appreciated. * I should make clear that this isn’t a showstopper for me so much as a minor nuisance that *can* be worked round (though I’d rather not have to if it was trivially fixable(!)) and enough of an apparent oddity that I thought it was worth raising. * If no-one else was able to reproduce the issue with the code snippet above, I’d assume the problem was with my installation and not worry about it. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Enable jQuery Migrate Helper] Interference with error handling and console logging?](https://wordpress.org/support/topic/interference-with-error-handling-and-console-logging/) * Thread Starter [Raspberryade](https://wordpress.org/support/users/raspberryade/) * (@raspberryade) * [2 years, 11 months ago](https://wordpress.org/support/topic/interference-with-error-handling-and-console-logging/#post-16788712) * Thanks for your response [@thelmachido](https://wordpress.org/support/users/thelmachido/). You should be able to repeat it by pasting the following into the main text of an empty article page (I use the classic editor “text” tab to ensure it appears as-is within the page HTML). * ```wp-block-code ``` * Then simply preview the article. * I’ve tried it with two different themes, the result is the same with both. * If the plugin isn’t enabled, I get “_Uncaught ReferenceError: undefined\_variable is not defined_” on the console (as expected). If it’s enabled, I don’t. * I’m just wondering if this is a known issue. - This reply was modified 2 years, 11 months ago by [Raspberryade](https://wordpress.org/support/users/raspberryade/). - This reply was modified 2 years, 11 months ago by [Raspberryade](https://wordpress.org/support/users/raspberryade/). * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Why do we want the *first* page of a category indexed?](https://wordpress.org/support/topic/why-do-we-want-the-first-page-of-a-category-indexed/) * Thread Starter [Raspberryade](https://wordpress.org/support/users/raspberryade/) * (@raspberryade) * [7 years, 9 months ago](https://wordpress.org/support/topic/why-do-we-want-the-first-page-of-a-category-indexed/#post-10572009) * [@joyously](https://wordpress.org/support/users/joyously/) ; Okay, thanks for your response! * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Why do we want the *first* page of a category indexed?](https://wordpress.org/support/topic/why-do-we-want-the-first-page-of-a-category-indexed/) * Thread Starter [Raspberryade](https://wordpress.org/support/users/raspberryade/) * (@raspberryade) * [7 years, 9 months ago](https://wordpress.org/support/topic/why-do-we-want-the-first-page-of-a-category-indexed/#post-10563060) * [@joyously](https://wordpress.org/support/users/joyously/) ; Thanks, but I’m not certain whether noindexing tag pages would make a difference. * Category pages are already going to have duplicate content anyway (from the first pre- section of the article pages themselves) and if an article appears in more than one category, that intro content is (additionally) going to appear on more than one category page. * #2- I think you’re saying that *you* don’t get their logic either? * I still don’t get their reasoning for allowing indexing of the first cat page only(!) * – Raspberryade * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [wp_is_stream Crashing the server](https://wordpress.org/support/topic/wp_is_stream-crashing-the-server/) * [Raspberryade](https://wordpress.org/support/users/raspberryade/) * (@raspberryade) * [7 years, 9 months ago](https://wordpress.org/support/topic/wp_is_stream-crashing-the-server/#post-10540238) * [@otto42](https://wordpress.org/support/users/otto42/); “The various reports are all on Windows based hosting.” * It’s not just Windows. According to [this comment](https://wordpress.org/support/topic/fatal-error-allowed-memory-size-of-11/#post-10469835) and the one which follows it, it’s also happening on some Linux installations. * (I appreciate that this doesn’t ultimately change the fact that- as you note- it’s apparently a bug in PHP itself, rather than WordPress.) * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Fatal error: Allowed memory size of….](https://wordpress.org/support/topic/fatal-error-allowed-memory-size-of-11/) * [Raspberryade](https://wordpress.org/support/users/raspberryade/) * (@raspberryade) * [7 years, 9 months ago](https://wordpress.org/support/topic/fatal-error-allowed-memory-size-of-11/#post-10536154) * [@te_taipo](https://wordpress.org/support/users/te_taipo/) ; That’s great, thank you for bringing it to my attention. * So, from what I can tell, this *is* a PHP bug (in 7.0 and 7.1 and possibly fixed in 7.2, though I can’t switch to that…) * I ended up using bezpeka.com’s short-term solution here (one of the other methods didn’t work for me):- * [https://wordpress.org/support/topic/wp_is_stream-crashing-the-server/#post-10470012](https://wordpress.org/support/topic/wp_is_stream-crashing-the-server/#post-10470012) * That’ll probably do it until 4.9.8 gets officially released. * Thanks again! * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [wp_is_stream Crashing the server](https://wordpress.org/support/topic/wp_is_stream-crashing-the-server/) * [Raspberryade](https://wordpress.org/support/users/raspberryade/) * (@raspberryade) * [7 years, 9 months ago](https://wordpress.org/support/topic/wp_is_stream-crashing-the-server/#post-10536145) * [@bezpekacom](https://wordpress.org/support/users/bezpekacom/) ; Thank you from me as well. * Yes, I appreciate it’s a somewhat hacky short-term fix that isn’t ideal from a maintenance point of view, but it seems to be working for me just now, unlike some of the other solutions! * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Fatal error: Allowed memory size of….](https://wordpress.org/support/topic/fatal-error-allowed-memory-size-of-11/) * [Raspberryade](https://wordpress.org/support/users/raspberryade/) * (@raspberryade) * [7 years, 9 months ago](https://wordpress.org/support/topic/fatal-error-allowed-memory-size-of-11/#post-10534239) * I’ve been having this problem as well. It only seems to appear under heavy load. * I initially put the problem down to having switched from PHP 7.2 to 7.1 (for reasons unrelated to WordPress) and possibly having a corrupt installation, but it seems to do it under 7.0 as well and now I think I just didn’t spot it under 7.2 and the problem is with PHP 7.x in general. (It wasn’t a problem with 5.x running under IIS). * I’m currently running PHP 7.0 running as a module under Apache 2.4 on Windows. Here’s one of the numerous entries I’m getting:- * [27-Jul-2018 16:17:23 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 7234872724905026747 bytes) in C:[OUR WORDPRESS FOLDER]\wp-includes\functions.php on line 5237 * You can see that the amount of memory it tried to allocate is beyond ludicrous. * I too thought that the problem was with stream_get_wrappers() since that’s where the problem was occurring, but that bit appears to work, and the contents of the array was something like * (php|file|glob|data|http|ftp|zip|compress.zlib|https|ftps|phar) * IIRC the problem appears to occur when it gets to the line * $wrappers_re = ‘(‘ . join(‘|’, $wrappers) . ‘)’; * (Sorry, I did this quick-and-dirty debug check before I saw your post, and I didn’t keep all the details). - This reply was modified 7 years, 9 months ago by [Raspberryade](https://wordpress.org/support/users/raspberryade/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[BruteProtect] The Future](https://wordpress.org/support/topic/the-future-1/) * [Raspberryade](https://wordpress.org/support/users/raspberryade/) * (@raspberryade) * [11 years ago](https://wordpress.org/support/topic/the-future-1/#post-5249301) * [@sam](https://wordpress.org/support/users/sam/) Hotchkiss; Just to clarify- it sounds like you’re implying that the existing standalone plugin (or any forks of it) won’t be permitted to access or interoperate with the backend infrastructure? * That is- as you say- you and Automattic’s proprietary service, and you’re of course entitled to force the use of Jetpack onto those wishing to access it. * But given that BruteForce *is* that (proprietary, non-replicable) infrastructure, if the answer to my first question was “no”, then it’s meaningless that the plugin is forkable- or perhaps that was exactly the point being made? Viewing 15 replies - 1 through 15 (of 19 total) 1 [2](https://wordpress.org/support/users/raspberryade/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/raspberryade/replies/page/2/?output_format=md)