Forum Replies Created

Viewing 15 replies - 61 through 75 (of 239 total)
  • Plugin Contributor peterdog

    (@peterdog)

    Donation received. Thanks!

    Plugin Contributor peterdog

    (@peterdog)

    All versions are here: http://wordpress.org/plugins/stealth-login-page/developers/ Just upload that by overwriting your existing SLP folder.

    Plugin Contributor peterdog

    (@peterdog)

    Sorry – this one didn’t get e-mailed to me.

    Thanks for the pro-tip on that field. I didn’t know that was an issue with a text field, but now that it’s a password field in 4.1.0 (in development), you might be able to make it more complex.

    We’re getting pretty advanced here. What I imagine you’re looking for is the account ability like Premise has to register Premise users who aren’t WP users. They might be different than the WP login – do you have a custom login form for your shop or does it take them to the wp-login.php? You might want to see if a custom login page will work for you and then I can see if I can work around this, but it is a somewhat custom request, so big population percentages have to take priority on revisions with my “hobby time.”

    Plugin Contributor peterdog

    (@peterdog)

    That is coming out next week. I’m working on adding both. Look for 4.1.0

    Plugin Contributor peterdog

    (@peterdog)

    .htaccess has nothing to do with the plugin but the plugin until 4.1.0 doesn’t re-locate the WP-login.php page. Did you have that set in .htaccess.

    No one in ~800 4.0.0 downloads has a ticket that they were locked out. How about a support ticket instead of a 3-star rating you would have rated higher before today? This prompted a low rating instead of a ticket.

    Plugin Contributor peterdog

    (@peterdog)

    Please try again to re-visit this rating. V 4.0.0 isn’t known to break any other plugin function and 4.0.1 won’t either.

    Plugin Contributor peterdog

    (@peterdog)

    Yes, I’m considering rolling out 4.0.1 today to fix that bit. 4.1.0 is underway but I have a strict deadline to do a site start to finish by Friday.

    If you have access to FTP, edit the settings-page.php fields by searching for “required” and deleting them. That will kill the complaining of empty fields. Just be sure you have the 3 fields filled in.

    Plugin Contributor peterdog

    (@peterdog)

    Per the installation notes: http://wordpress.org/plugins/stealth-login-page/installation/

    1. Upload contents of the directory to /wp-content/plugins/ (or use the automatic installer)
    2. Activate the plugin through the ‘Plugins’ menu in WordPress
    3. Configure the settings to create the secret authorization code and redirect URL.
    4. Verify it works by going to your login form.

    Those you mentioned are if you are on multi-site, which I doubt you are as a new user. Activate = installed. Follow Step #3.

    Plugin Contributor peterdog

    (@peterdog)

    Noted. It is coming back. ASAP.

    I clearly made an error in judgement in preparing for WP 3.6 (dropped yesterday, so go update after making a backup and see what happens when you sit idle in a post too long.

    I will ensure I have several feature checkboxes, so I’m working out the UI in my head before I begin because I have so many full-site projects in my queue.

    Plugin Contributor peterdog

    (@peterdog)

    Darn, no. I did put that in place so people couldn’t save with blank fields. I forgot about that. You can go into SQL and clear that out of the settings, but stick with 3.0.0 until WP 3.6 comes out and I’ll see how fast I can have 4.1.0 out.

    Plugin Contributor peterdog

    (@peterdog)

    Oh, I didn’t make this multi-site compatible in the way that I did the others. I wonder if that has anything to do with it. I think I’ll have to do some more testing. Please revert to 3.0.0 until I get this sorted out.

    Plugin Contributor peterdog

    (@peterdog)

    That is the error I get all of the time and WP Engine said it can’t be cleared, so there isn’t an actual PHP error in the terms of WSOD (white screen of death). That error doesn’t cause WSOD.

    Warning: include() [function.include]: Failed opening ‘/nas/wp/www/staging/~~~~~/wp-content/advanced-cache.php’ for inclusion (include_path=’.:/usr/share/php:/usr/share/pear’) in /nas/wp/www/staging/~~~~~/wp-settings.php on line 58

    Without knowing your setup, I’d guess that you have another plugin conflicting with it. Is that blank page /wp-admin/ or /wp-login.php?

    Drag all other plugins into another folder (don’t visit the plugins page in the dashboard in any old tab) and refresh the WSOD page. If it’s still blank, it’s not a plugin and then drag them back in. Let me know your findings.

    Plugin Contributor peterdog

    (@peterdog)

    The redirect is based on the auth field. I’ll have to re-work things, it’d appear.

    Please revert to 3.0.0 if this is too bothersome and I do agree that stealth is gone, but it was changed for reasons in the threads that I’ve stickied in the forums.

    I’ll add an option to use either method OR you can simply clear out the auth field in the settings and your old settings should still be in the database unless you deactivated and deleted 3.0.0 before updating.

    I’m slowly adding different methods so people can choose and this method was strictly because of WP 3.6 heartbeat API.

    Plugin Contributor peterdog

    (@peterdog)

    Go to wp-config.php and enable debug and see what those pages say – temporarily. http://codex.wordpress.org/WP_DEBUG

    I had to use it frequently in writing the plugin but all errors in my test environments were all error-free. It may be some cache issue.

    Plugin Contributor peterdog

    (@peterdog)

    I am adding in the option to choose just as soon as I launch things with immediate deadlines. It will be the best of both worlds. To get that option back, just clear out the auth code field and it will revert to previous behavior or add the variables to wp-config.php:
    $slp_redirect = “item”;
    $slp_question = “item”;
    $slp_answer = “item”;

    Hack Repair Guy – I didn’t have time to put the link in the dashboard in case WP 3.6 dropped – the link is here on the repo under my developer name in the sidebar or https://www.petersenmediagroup.com/contribute/

Viewing 15 replies - 61 through 75 (of 239 total)