Pat K
Forum Replies Created
-
Forum: Plugins
In reply to: [BulletProof Security] XML-RPC & JetpackIt works! (I am now getting the 403 Forbidden message when visiting xmlrpc.php)
Thanks AITpro! Excellent support & assistance!
Forum: Plugins
In reply to: [BulletProof Security] XML-RPC & JetpackThanks for your very clear instructions. I did all that – and added only the most recent chunk of code for Jetpack (your “Recommended Code for Jetpack”).
The reason for posting my question is that I was EXPECTING a 403 Forbidden error when visiting the xmlrpc.php page on the front end after adding the new custom code (as is the case when adding the “usual” XML-RPC Bonus Code). Instead I got the xmlrpc.php page: “XML-RPC server accepts POST requests only”.
Just wondering if this is expected? (I always check to make sure I get the 403 error page after adding the XML-RPC Bonus Code to ensure it’s working.)
Cheers (and thanks for the modlook tag tip)
Forum: Plugins
In reply to: [BulletProof Security] XML-RPC & JetpackSorry for the typo. I INTENDED to link to this:
http://forum.ait-pro.com/forums/topic/wordpress-xml-rpc-ddos-protection-protect-xmlrpc-php-block-xmlrpc-php-forbid-xmlrpc-php/If someone can clean up the mangled hyperlink in my original message, that would be great.
Forum: Themes and Templates
In reply to: [Storefront] Storefront 2.0 Sass and style.cssIn case you are reading this and need a quick way to unminify the parent stylesheet, try this http://unminify.com/
Forum: Themes and Templates
In reply to: [Storefront] Storefront 2.0 Sass and style.cssHey back,
This developer selected Storefront in part because it DID NOT use minified files.
RE: “What is it that you need the css to be un-minified to do?”
I want to be able to read (as in, with my eyes) the parent stylesheet using a text editor.If you want this to be user-friendly, you could, at the very least provide an unminified version of the file for developers and non-developers who simply want to access the rule-sets in the parent stylesheet without having to jump through hoops to do so.
Some WooCommerce users may like or even love this, but I think you’re going to find many people – like me – REALLY don’t like this approach.
Re: “loads of tools” …that’s actually pretty funny; yes, there ARE loads of tools around the Web.
Version 3.3 fixes the problem on sites I manage as well. In my case, I could run manual backups ONLY if I deactivated Bulletproof Security and reverted to the default .htaccess file.
Manual backups are now running fine again with BPS installed.
Thanks Daniel!
I can verify that BackWPup version 3.2.4 DOES work on sites I manage that DO NOT have Bulletproof Security installed.
Not sure if this is the case for other people reporting this problem.
I am having the same issue on several sites when attempting to run manual backups after updating to BackWPup version 3.2.4 (using WP version 4.4.2).
Rolling back to 3.2.3 allows me to run successful backups.
I also have Bulletproof Security installed on these sites, and came across this which may be helpful to Daniel in identifying the problem:
https://wordpress.org/support/topic/backwpup-missing-or-not-expected-http-response-headers?replies=3(I did not find any errors related to BackWPup in my BPS logs.)
Forum: Plugins
In reply to: [Products Per Page for WooCommerce] Max 3 columns in storefrontHi Jeroen,
Love your plugin (and will give it a rating shortly).
In case this helps someone else with the same issue, it IS possible to increase the number of products per row by using a child theme for Storefront, adding a filter to the functions.php file in the child theme and making a minor modification to the child theme’s style.css file.
The details are provided here:
https://wordpress.org/support/topic/change-number-of-product-columns-on-shop-pageIt might be necessary to add !important after both CSS rules (or increase the specificity of both style rules).
Cheers,
PKForum: Plugins
In reply to: [Limit Login Attempts] Plugin VulnerabilityHello nvispute,
(This is a copy of my reply to your plugin review…)
Thanks for posting your information BUT I’m pretty darn sure the vulnerability you’re referring to applies to “WP Limit Login Attempts” https://wordpress.org/plugins/wp-limit-login-attempts/ NOT this plugin (“Limit Login Attempts”).
You will notice the wpvulndb.com link at the top https://wpvulndb.com/plugins/wp-limit-login-attempts AND reference to a fix in version 2.0.1 …the most recent version of this plugin is 1.7.1
Just wanting to clarify the reported vulnerability doesn’t apply to this plugin….so your sites that were hacked may be related to something else entirely.
Cheers
PKForum: Themes and Templates
In reply to: [Twenty Thirteen] sub-menu always visibleThis is an old post, but maybe this can help someone else. The fix for this isn’t in the media query; in your child theme’s style.css file, look for this (around line 888):
.nav-menu .sub-menu, .nav-menu .children { background-color: #220e10; border: 2px solid #f7f5e7; border-top: 0; padding: 0; position: absolute; left: -2px; z-index: 99999; height: 1px; width: 1px; overflow: hidden; clip: rect(1px, 1px, 1px, 1px); }and replace it with this:
.nav-menu .sub-menu, .nav-menu .children { background-color: #220e10; border: 2px solid #f7f5e7; border-top: 0; padding: 0; position: absolute; left: -2px; z-index: 99999; height: 100%; width: 100%; overflow: visible; clip: rect(1px, 1px, 1px, 1px); }If you want to indent the children in your mobile menu, in your mobile query, use text-indent or margin-left. Something like this:
.toggled-on .nav-menu li > ul { background-color: transparent; display: block; float: none; margin-left: 20px; position: relative; left: auto; top: auto; }Forum: Plugins
In reply to: [Media Vault] Password protectedThanks Jake for sharing your work-around!
Max, please add my vote for password protected pages & posts to your most excellent plugin. It would be GREAT if basic WP password protection for pages & posts could be integrated…
Would it be possible to do a cookie check – and add ‘basic password protection’ as an option to the File Access Permission drop-down on the Attachment Details Screen? From the WP codex:
“WordPress stores this password in a browser cookie so readers don’t have to re-enter passwords if they visit the same page multiple times. Furthermore, if multiple posts use the same password, the reader will only have to enter the password once to access every post”Thanks again for the great plugin!
pkHi Joe,
D’oh! I never thought to run the pages through a markup validator!!
Thanks for letting me know about the email issue as well.
I’ll be sure to send a donation your way to compensate you for your time.
Thanks!
Thanks Joe,
Yeah – I was surprised when I didn’t hear back from you. I checked the server to make sure the messages were sent and could see they were sent successfully. Maybe a spam filter issue? Let me know if you think the email issue is on my end and I’ll take another look.Thanks for the quick fix!
I updated and it’s working fine.
Resolved!