bamajr

I volunteered to purchase a premium add-on and you told me it wasn’t enough. So how big of a customer do I have to be, before there is value, to fix the base plugin, which is needed to use the premium add-on?

Kind of a mute point, now that someone has given you a license for Genesis. However, you should know, I don’t simply dine and dash. If the issues are fixed, I will simply change my review!

I get it. Your development of this theme and the premium add-ons doesn’t earn you any money, for one reason or another, so the $100 price tag, for Genesis, is out of reach. I’m not sure that speaks volumes about your plugin or the premium add-on options, but Y’all act as if this is just an issue with my website, when we all know it is an issue, which will affect EVERY Single Genesis user.

I’m also being asked how, as a “FREE” plugin developer, buying a premium theme, in order to fix your free plugin, is a good business model. Seems like simple economics to me. Your “FREE” plugin actually has a number of premium add ons, right? So how is it a good business model, to eliminate the 101,000 plus websites, using Genesis, as potential customers? – that is just the Genesis customers.

I’m to understand this plugin may not work with other theming frameworks, either – for the same reasons. So how many websites, are you effectively eliminating, by not supporting premium theming frameworks/themes? We know at least 101,000 Genesis websites. What about Catalyst and Thesis users? Have you checked your plugin on them? How about checking compatibility with other plugins, which need access to the TITLE tag, to function properly, like all the SEO Plugins. Did you check your plugin’s compatibility with them?

It’s only in the logs… which, I know, as a general rule, aren’t a huge issue, but these warnings started showing up when the website started crashing. The website is returning a 500 error, about 50 times per day (or more). Naturally, I’m going through all the logs, to figure this out, because, other than plugin updates, I haven’t added or removed any plugins, nor have I modified the theme/design.

I started out by scanning the website, with Sucuri, and it gets a clean report!

@moderator…

Sorry… thought I did!

### Begin System Info ###

## Please include this information when posting support requests ##

Multisite:                No

SITE_URL:                 https://bamajr.com
HOME_URL:                 https://bamajr.com

EDD Version:              1.9.4
Upgraded From:            None
WordPress Version:        3.8.1
Permalink Structure:      /%year%/%monthnum%/%day%/%postname%/
Active Theme:             Genesis 2.0.2

Test Mode Enabled:        Yes
Ajax Enabled:             Yes
Guest Checkout Enabled:   Yes
Symlinks Enabled:         No

Checkout is:              Valid
Checkout Page:            https://bamajr.com/checkout/
Success Page:             https://bamajr.com/checkout/purchase-confirmation/
Failure Page:             https://bamajr.com/checkout/transaction-failed/
Downloads slug:           /downloads

Taxes Enabled:            No
Taxes After Discounts:    No
Tax Rate:                 0%
Country / State Rates:    Country: *, State: , Rate:  |
Registered Post Stati:    publish, future, draft, pending, private, trash, auto-draft, inherit, closed, spam, orphan, hidden, refunded, failed, revoked, abandoned, active, inactive, preapproval, cancelled

Platform:                 Apple
Browser Name:             Safari
Browser Version:          7.0.1
User Agent String:        Mozilla/5.0 (Macintosh; Intel Ma
			  c OS X 10_9_1) AppleWebKit/537.7
                          3.11 (KHTML, like Gecko) Version
                          /7.0.1 Safari/537.73.11

PHP Version:              5.3.10-1ubuntu3.7
MySQL Version:            5.1.73-0ubuntu0.10.04.1
Web Server Info:          nginx/0.7.65

PHP Safe Mode:            No
PHP Memory Limit:         256M
WordPress Memory Limit:   40MB
PHP Upload Max Size:      8M
PHP Post Max Size:        12M
PHP Upload Max Filesize:  8M
PHP Time Limit:           300
PHP Max Input Vars:       1000

WP_DEBUG:                 Disabled

WP Table Prefix:          Length: 3 Status: Acceptable

Show On Front:            posts
Page On Front:             (#0)
Page For Posts:            (#0)

WP Remote Post:           wp_remote_post() works

Session:                  Enabled
Session Name:             PHPSESSID
Cookie Path:              /
Save Path:                /var/lib/php5
Use Cookies:              On
Use Only Cookies:         On

DISPLAY ERRORS:           N/A
FSOCKOPEN:                Your server supports fsockopen.
cURL:                     Your server supports cURL.
SOAP Client:              Your server has the SOAP Client enabled.
SUHOSIN:                  Your server does not have SUHOSIN installed.

TEMPLATES:

ACTIVE PLUGINS:

Akismet: 2.5.9
bbPress: 2.5.3
bbPress Genesis Extend: 1.0.2
Clicky for WordPress: 1.4.2.3
Conditional CAPTCHA for WordPress: 3.6
Easy Digital Downloads: 1.9.4
Easy Digital Downloads - Auto Register: 1.1
Easy Digital Downloads - Downloads As Services: 1.0.4
Easy Digital Downloads - Purchase Gravatars: 1.0
Easy Digital Downloads - Stripe Payment Gateway: 1.6.7
Genesis eNews Extended: 1.4.0
Genesis Latest Tweets: 1.2.2
Genesis Simple Edits: 1.7.1
Genesis Simple Hooks: 2.0.1
Google Analytics for WordPress: 4.3.4
Google Authenticator: 0.47
Gravity Forms: 1.8.3
Gravity Forms PayPal Add-On: 1.9
Gravity Forms Picatcha Add-On: 2.0
Gravity Forms Polls Add-On: 1.5
Gravity Forms Quiz Add-On: 1.1
Gravity Forms Survey Add-On: 1.0.1
Gravity Forms User Registration Add-On: 1.7
Landing Pages: 1.4.6
NextScripts: SNAP Pro Upgrade Helper: 1.1.8
NextScripts: Social Networks Auto-Poster: 3.2.1
Polldaddy Polls & Ratings: 2.0.21
SendPress: Email Marketing and Newsletters: 0.9.8.1
SendPress Pro: 0.8.1
SensorPress: 1.0
Simple Social Icons: 1.0.5
Simple URLs: 0.9.4
Stop Spammer Registrations Plugin: 5.5
Stop Spammer Widget: 5.5
Sucuri Security - SiteCheck Malware Scanner: 1.5.4
SyntaxHighlighter Evolved: 3.1.7
W3 Total Cache: 0.9.3
WordPress HTTPS: 3.3.6
WordPress SEO: 1.4.24
WordPress SEO News: 1.1.1
WP SlimStat: 3.5.3
### End System Info ###

[Moderator Note: Please post log files between backticks or use the code button.]

Yeah Authy does the same thing, again with no compatibility issues between Google Authenticator and the Stop Spammers plugins. I’m being told these options interfere with the credentialcheck, but I’ve not verified how/if it does.

I’m pretty sure it can be done. I’ve looked at the icon set they use, to make the glyphs for this plugin and I think App.net already exists. Its probably more a matter of who has time to do it.

Look, I’m not trying to be an @$$ here. I prefer the Google Authentication app, personally, but I despise the authentication occurring on the same screen as the username/password. It simply isn’t the most effective way to use the 2-Step Authentication model.

The Authy Two Factor Authentication plugin has obviously found a way, which isn’t as disruptive as you want to think. It also seems to me, when their authentication is occurring outside of the WordPress login (username/password) area, it stands to reason other plugins, which perform credential verification tasks, from the same area, would have less problems, not more.

It just seems to me your plugin could play a bigger role, in self-hosted WordPress websites, by aiding in the User Experience, not taking away from it. Tool-tip or not, people are confused by your plugin’s workflow, especially those not using 2-Step Authentication. And, while I’m completely aware, we are way outside of the issue, I first reported and deep into a feature request, it seems to me, making your plugin more useful, less confusing and providing a better over all user experience, would be pretty high on the to do list.

So, I’ll ask this a different way: How is the Authy Two Factor Authentication plugin able to do it and your plugin can’t?

Also, isn’t the method I suggest already being used by the Authy Two Factor Authentication plugin (See screenshot here: https://www.ads-software.com/plugins/authy-two-factor-authentication/screenshots/) While, the Google Authentication plugin has a lot more downloads, the Authy plugin seems to work very similar to yours, but adding the additional authentication screen.

So, my curiosity would be how does the Stop Spammer Registration Plugin interact with the Authy Two Factor Authentication plugin? Does it fail their users’ login attempts?

Henrik & kpgraham, Doesn’t the Stop Spammer Registration Plugin credential check, happen from WordPress’ traditional login process? If so, couldn’t all that occur, prior to being handed off to the next screen, being used for the 2-Step Authentication Code?

Also, isn’t WordPress themselves, offering a 2-Step Authentication model, which already works the way I’m suggesting? If they are developing around the model I suggest, I don’t see it being an issue for the Google Authentication plugin, in the future.

Henrik… You’re awesome. I know this issue bugged you last evening and I’m very happy to see your commitment to making your plugin work.

Awesome question kpgraham! I’d love to see the the two plugins, come together for a better, more seamless integration. While Kenrik has suggested an idea, I don’t think it is the best option.

I just updated my Review, for Henrik’s Google Authenticator plugin, with an idea, but I’ll add it here, with a slightly different description so, possibly, the two of you, could incorporate this functionality together.

Just about all applications and websites, I’m aware of, offering 2-Step Authentication, DO NOT ask for it in the same part of the login process as the username/password. As a matter of fact, I use 2-Step Authentication on several popular apps and websites (I.E. App.net, Dropbox, Evernote, Facebook, GitHub, Google and others). Not one of them utilizes 2-Step Authentication, on the same screen as the username/password.

It would be better if the username/password portion of the login, occurred as it normally does. So a user would be presented with the traditional login screen. After entering their username/password and if the user has this Google Authentication plugin enabled, they are then presented with a second screen, asking for the 2-Step Authentication code.

Maybe I’m wrong, but would this incompatibly issue, between your two plugins, even exist, if the 2-Step Authentication process was more consistent with the generally adopted use, as I’ve described above?

YES… This did fix the issue on all the affect websites.

I’ve been using your Google Authenticator plugin with the Stop Spammers plugin, together, for quite a while. I haven’t changed any settings, nor otherwise altered either plugin, except for applying updates. Both plugins have had fairly recent updates, though this issue didn’t surface until applying the most recent update to your Google Authenticator.

I’m curious: Can you explain, why, this issue started with the most recent update, while working for so long, prior?

YES… This does seem to be the issue!!! I’m now able to use your Google Authenticator on my website. Now I’ll verify this with the other two websites and report back.