Title: ScreenRes's Replies | WordPress.org --- # ScreenRes [ ](https://wordpress.org/support/users/screenres/) * [Profile](https://wordpress.org/support/users/screenres/) * [Topics Started](https://wordpress.org/support/users/screenres/topics/) * [Replies Created](https://wordpress.org/support/users/screenres/replies/) * [Reviews Written](https://wordpress.org/support/users/screenres/reviews/) * [Topics Replied To](https://wordpress.org/support/users/screenres/replied-to/) * [Engagements](https://wordpress.org/support/users/screenres/engagements/) * [Favorites](https://wordpress.org/support/users/screenres/favorites/) Search replies: ## Forum Replies Created Viewing 7 replies - 1 through 7 (of 7 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Contact Form 7] Bug: wpcf7 JQuery Not Defined Error](https://wordpress.org/support/topic/bug-wpcf7-jquery-not-defined-error/) * [ScreenRes](https://wordpress.org/support/users/screenres/) * (@screenres) * [4 years, 3 months ago](https://wordpress.org/support/topic/bug-wpcf7-jquery-not-defined-error/#post-15472581) * [@thomasjarvisdesign](https://wordpress.org/support/users/thomasjarvisdesign/) 60 sites! Thankfully I haven’t got that many to update. CF7 Condition Fields still worked fine for me with the standard method but suppose I should keep it all neat in one call in one place. Thanks for the updated. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Contact Form 7] Bug: wpcf7 JQuery Not Defined Error](https://wordpress.org/support/topic/bug-wpcf7-jquery-not-defined-error/) * [ScreenRes](https://wordpress.org/support/users/screenres/) * (@screenres) * [4 years, 3 months ago](https://wordpress.org/support/topic/bug-wpcf7-jquery-not-defined-error/#post-15471793) * I was having the same issue, thanks for the fix [@thomasjarvisdesign](https://wordpress.org/support/users/thomasjarvisdesign/) * Forum: [Localhost Installs](https://wordpress.org/support/forum/localhost-installs/) In reply to: [MAMP Viewer: Static homepage causes page load error](https://wordpress.org/support/topic/mamp-viewer-static-homepage-causes-page-load-error/) * [ScreenRes](https://wordpress.org/support/users/screenres/) * (@screenres) * [8 years, 2 months ago](https://wordpress.org/support/topic/mamp-viewer-static-homepage-causes-page-load-error/#post-10239843) * I’ve been chatting with MAMP support over the past week, sending logs, altering settings etc but with no joy. The support person I’ve been dealing with has finally managed to replicate the issue so bug report has been submitted. Apparently if support can’t replicate the issue then they can’t submit a bug report. * Another bit of advice I was give via MAMP support was don’t use .local, .localhost or .dev host names. * If I hear anything else I’ll report back. * Forum: [Localhost Installs](https://wordpress.org/support/forum/localhost-installs/) In reply to: [MAMP Viewer: Static homepage causes page load error](https://wordpress.org/support/topic/mamp-viewer-static-homepage-causes-page-load-error/) * [ScreenRes](https://wordpress.org/support/users/screenres/) * (@screenres) * [8 years, 2 months ago](https://wordpress.org/support/topic/mamp-viewer-static-homepage-causes-page-load-error/#post-10201720) * [@sideshow01](https://wordpress.org/support/users/sideshow01/), Did you ever sort this issue or get a reply from MAMP/Appsolute? Am having exactly the same issue. This happened in MAMP Pro 3 if using XIP to view the site on another device. Asked MAMP about it 2 years ago, got told it’s a WordPress issue. * I’ve contacted MAMP again, awaiting a response. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Fetch Tweets] Item count and returned tweets don’t match](https://wordpress.org/support/topic/item-count-and-returned-tweets-dont-match/) * Thread Starter [ScreenRes](https://wordpress.org/support/users/screenres/) * (@screenres) * [9 years, 6 months ago](https://wordpress.org/support/topic/item-count-and-returned-tweets-dont-match/#post-8544025) * Thanks [@miunosoft](https://wordpress.org/support/users/miunosoft/) Works perfectly. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Fetch Tweets] Item count and returned tweets don’t match](https://wordpress.org/support/topic/item-count-and-returned-tweets-dont-match/) * Thread Starter [ScreenRes](https://wordpress.org/support/users/screenres/) * (@screenres) * [9 years, 7 months ago](https://wordpress.org/support/topic/item-count-and-returned-tweets-dont-match/#post-8523470) * Cheers for the info [@miunosoft](https://wordpress.org/support/users/miunosoft/). * For the time being I’ve rolled back to v2.4.9. Any suggestions on fix via my custom template would be greatly appreciated. * Thanks * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Fetch Tweets] Item count and returned tweets don’t match](https://wordpress.org/support/topic/item-count-and-returned-tweets-dont-match/) * Thread Starter [ScreenRes](https://wordpress.org/support/users/screenres/) * (@screenres) * [9 years, 7 months ago](https://wordpress.org/support/topic/item-count-and-returned-tweets-dont-match/#post-8520716) * Thanks for the response [@miunosoft](https://wordpress.org/support/users/miunosoft/). The feed I was pulling in did have several re-tweets in it. * Not sure if this will help but I’ve been testing a few bits my end. I updated to v2.6.0 from v2.4.9 so went back and downloaded v2.5.0 through to v2.5.3, this issues started in v2.5.0. I had a look at the change log and reverted 1 change from v2.5.0: * > Default value of the operator argument to IN from AND used when fetching tweets > with tags. * include/class/option/FetchTweets_Option_Format.php I changed it back to AND and the issue now isn’t there (returns full item count) in v2.5.0 through to v2.6.0. * I’m not sure if this affects anything else within the plugin (didn’t do a robust test). Would it be feasible to alter it back to AND in v2.6.1 as a temp fix? I understand you must have changed it for a good reasons in v2.5.0. * Thanks Viewing 7 replies - 1 through 7 (of 7 total)