Title: Innervates's Replies | WordPress.org --- # Innervates [ ](https://wordpress.org/support/users/innervates/) * [Profile](https://wordpress.org/support/users/innervates/) * [Topics Started](https://wordpress.org/support/users/innervates/topics/) * [Replies Created](https://wordpress.org/support/users/innervates/replies/) * [Reviews Written](https://wordpress.org/support/users/innervates/reviews/) * [Topics Replied To](https://wordpress.org/support/users/innervates/replied-to/) * [Engagements](https://wordpress.org/support/users/innervates/engagements/) * [Favorites](https://wordpress.org/support/users/innervates/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 17 total) 1 [2](https://wordpress.org/support/users/innervates/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/innervates/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] Fatal error: Class 'WPSEO_Options'](https://wordpress.org/support/topic/fatal-error-class-wpseo_options/) * [Innervates](https://wordpress.org/support/users/innervates/) * (@innervates) * [11 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-class-wpseo_options/page/3/#post-5824130) * So best way for you to fix this – since you can’t access your dashboard. * FTP to your site – or use Cpanel – or some other method to view your folders. * Go to your plugins directory usually something like * public_html/site.com/wp-content/plugins * fine the folder named “wordpress-seo” * Rename that folder to “wordpress-seo2” (or whatever you want) * Now you’ll be able to get into your dashboard. Then go to your updates section– and you’ll see that you’ll have an update for WordPress-Seo * Download that update – install it – right through wordpress. Then go back to your plugins list on WordPress, and activate the plugin. The update will rewrite the folder back to the correct name, so you don’t have to rename it again. * Hope this helps. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Kadence Security – Password, Two Factor Authentication, and Brute Force Protection] iThemes Security Throwing Semi-Random Internal Server 500 Error](https://wordpress.org/support/topic/ithemes-security-throwing-semi-random-internal-server-500-error/) * Thread Starter [Innervates](https://wordpress.org/support/users/innervates/) * (@innervates) * [12 years ago](https://wordpress.org/support/topic/ithemes-security-throwing-semi-random-internal-server-500-error/#post-5232153) * I have a caching plugin – but I’ve had Browser Cache disabled for 3 weeks now– and the error just happened again today. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Kadence Security – Password, Two Factor Authentication, and Brute Force Protection] iThemes Security Throwing Semi-Random Internal Server 500 Error](https://wordpress.org/support/topic/ithemes-security-throwing-semi-random-internal-server-500-error/) * Thread Starter [Innervates](https://wordpress.org/support/users/innervates/) * (@innervates) * [12 years ago](https://wordpress.org/support/topic/ithemes-security-throwing-semi-random-internal-server-500-error/#post-5232152) * Seems really weird that file change detection would throw an internal server 500 error. It happened again today – so you’re telling me that every time I update iThemes, ALLLL of my visitors have to delete their browser history? * Doesn’t this seem like a really big flaw? * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Kadence Security – Password, Two Factor Authentication, and Brute Force Protection] iThemes Security Throwing Semi-Random Internal Server 500 Error](https://wordpress.org/support/topic/ithemes-security-throwing-semi-random-internal-server-500-error/) * Thread Starter [Innervates](https://wordpress.org/support/users/innervates/) * (@innervates) * [12 years ago](https://wordpress.org/support/topic/ithemes-security-throwing-semi-random-internal-server-500-error/#post-5232017) * Okay – I think I’ve narrowed it down to a Cookie problem with iThemes. * What in iThemes creates cookies – what file – someone give me something here, and I can dig and troubleshoot the rest. * I’m able to fix the problem on the browser by deleting the Cookies – clearing cache had no effect. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Kadence Security – Password, Two Factor Authentication, and Brute Force Protection] iThemes Security Throwing Semi-Random Internal Server 500 Error](https://wordpress.org/support/topic/ithemes-security-throwing-semi-random-internal-server-500-error/) * Thread Starter [Innervates](https://wordpress.org/support/users/innervates/) * (@innervates) * [12 years ago](https://wordpress.org/support/topic/ithemes-security-throwing-semi-random-internal-server-500-error/#post-5231922) * I’m also pretty sure it’s not a .htaccess problem, because I went in an commented out each section one at a time, and didn’t resolve it. * So what does ithemes change when it’s activated? If I know that, I can probably figure this out – because it only happens when it’s activated, and when deactivated, problem is fixed instantly. Reactivate, problem returns instantly. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Kadence Security – Password, Two Factor Authentication, and Brute Force Protection] iThemes Security Throwing Semi-Random Internal Server 500 Error](https://wordpress.org/support/topic/ithemes-security-throwing-semi-random-internal-server-500-error/) * Thread Starter [Innervates](https://wordpress.org/support/users/innervates/) * (@innervates) * [12 years ago](https://wordpress.org/support/topic/ithemes-security-throwing-semi-random-internal-server-500-error/#post-5231896) * additionally – I checked our apache server logs… this was the only thing that stood out to me * Premature end of script headers: admin-ajax.php, referrer: … * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Smooth Scroll Up] Uncaught TypeError: Cannot read property 'top' of undefined](https://wordpress.org/support/topic/uncaught-typeerror-cannot-read-property-top-of-undefined-3/) * Thread Starter [Innervates](https://wordpress.org/support/users/innervates/) * (@innervates) * [12 years, 2 months ago](https://wordpress.org/support/topic/uncaught-typeerror-cannot-read-property-top-of-undefined-3/#post-4993574) * Hi there, I did check into this – I thought it was your plugin due to a coincidence when I disabled the plugin. * This has nothing to do with your’s, thank you! * R.J. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce Poor Guys Swiss Knife] Cart Maximum not Working](https://wordpress.org/support/topic/cart-maximum-not-working/) * Thread Starter [Innervates](https://wordpress.org/support/users/innervates/) * (@innervates) * [12 years, 3 months ago](https://wordpress.org/support/topic/cart-maximum-not-working/#post-5022264) * so far it looks like it works great, I do have a plugin conflict with WooCommerce Thumbnail Input Quantities – this plugin allows customers to add items directly from the product archive page, it doesn’t throw a warning or anything, and adds the quantity to the cart – however, this isn’t a big deal, nor your problem. * I tested the new addition, and it seems to work – it gives a warning message. I’m going to edit the plugin so I can change what the warning message says – I’ll just have to find where that’s at. * Thank you! * R.J. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce Poor Guys Swiss Knife] Cart Maximum not Working](https://wordpress.org/support/topic/cart-maximum-not-working/) * Thread Starter [Innervates](https://wordpress.org/support/users/innervates/) * (@innervates) * [12 years, 3 months ago](https://wordpress.org/support/topic/cart-maximum-not-working/#post-5022251) * Well this is great news! This will save me some work on Monday. Thank you! * R.J. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce Poor Guys Swiss Knife] Cart Maximum not Working](https://wordpress.org/support/topic/cart-maximum-not-working/) * Thread Starter [Innervates](https://wordpress.org/support/users/innervates/) * (@innervates) * [12 years, 3 months ago](https://wordpress.org/support/topic/cart-maximum-not-working/#post-5022245) * thanks – usually a Product means an individual item. If I buy 5 Cell phones, I have purchased 5 products – even if they’re all the same TYPE of product 🙂 * Thanks though! I think I’m going to try and write this myself. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce Poor Guys Swiss Knife] Cart Maximum not Working](https://wordpress.org/support/topic/cart-maximum-not-working/) * Thread Starter [Innervates](https://wordpress.org/support/users/innervates/) * (@innervates) * [12 years, 3 months ago](https://wordpress.org/support/topic/cart-maximum-not-working/#post-5022243) * Okay – so that’s weird then. * So the way it’s worded is weird – you might want to change it so it reads “Maximum Number of Different Product Types” – because “Maximum Cart Items” and the comment of “Maximum of items allowed” sounds like Total maximum number. See, we’re trying to find a way so that our clients can ONLY purchase 10 products total – regardless of what TYPE of products they are. Either they can buy 1 of each 10 different products, or they can buy 10 of 1 product – but only 10 maximum total. * In your example – the customer would have 30 items in the cart, that has a maximum of 2 items… so that’s confusing. * Okay – well I guess there isn’t any way for your plugin to do what I need 🙁 * On to the next one I guess. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce Poor Guys Swiss Knife] Cart Maximum not Working](https://wordpress.org/support/topic/cart-maximum-not-working/) * Thread Starter [Innervates](https://wordpress.org/support/users/innervates/) * (@innervates) * [12 years, 3 months ago](https://wordpress.org/support/topic/cart-maximum-not-working/#post-5022145) * Okay – just wondering if maybe anyone else was experiencing this problem. * Thanks for the help! * R.J. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Smooth Scroll Up] Uncaught TypeError: Cannot read property 'top' of undefined](https://wordpress.org/support/topic/uncaught-typeerror-cannot-read-property-top-of-undefined-3/) * Thread Starter [Innervates](https://wordpress.org/support/users/innervates/) * (@innervates) * [12 years, 3 months ago](https://wordpress.org/support/topic/uncaught-typeerror-cannot-read-property-top-of-undefined-3/#post-4993279) * did some searching around – and came up with this… as the solution for a similar problem using a sticky menu… * var nav = $(‘.content-nav’); if (nav.length) { var contentNav = nav.offset(). top; …continue to set up the menu } * (this was the solution for someone else, so you might have to adjust the code to work for you, like whatever “contentNav” should be for your code) * Thanks! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WordPress Calls to Action] Parse error: syntax error](https://wordpress.org/support/topic/parse-error-syntax-error-87/) * [Innervates](https://wordpress.org/support/users/innervates/) * (@innervates) * [12 years, 3 months ago](https://wordpress.org/support/topic/parse-error-syntax-error-87/#post-4951799) * getting this same error as well – and we’re running php 5.3. * Thanks * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[GaugePress] thousands separator](https://wordpress.org/support/topic/thousands-separator/) * [Innervates](https://wordpress.org/support/users/innervates/) * (@innervates) * [12 years, 4 months ago](https://wordpress.org/support/topic/thousands-separator/#post-4850074) * This function actually is currently supported. * It will require you to make one minor change to a javascript file, and then reupload that file replacing the one on your server. * Go to your plugins folder wp-content/plugins/ * and navigate to the gaugepress folder * wp-content/plugins/gaugepress * open up the js folder * so you should now be in * wp-content/plugins/gaugepress/js * open up justgage.js with a javascript editor (dreamweaver works) * scroll down to line 292 you should see this * ``` // formatNumber: boolean // formats numbers with commas where appropriate formatNumber : obj.kvLookup('formatNumber', config, dataset, false) }; ``` * Change that false to true so it should now read like this * ``` // formatNumber: boolean // formats numbers with commas where appropriate formatNumber : obj.kvLookup('formatNumber', config, dataset, true) }; ``` * All of your numbers will now have appropriate comma separators. * The plugin developer should be able to make this change, or add in an option to change this in the shortcodes. Viewing 15 replies - 1 through 15 (of 17 total) 1 [2](https://wordpress.org/support/users/innervates/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/innervates/replies/page/2/?output_format=md)