jc_513

Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter jc_513

    (@jc_513)

    Tried 1.2.1 — no change. Here is the output from the log file showing 1.2.1 version infomation.

    <html>
<head>
<meta name="backwpup_version" content="1.2.1" />
<meta name="php_version" content="5.1.6" />
<meta name="mysql_version" content="5.0.77-log" />
<meta name="backwpup_logtime" content="1279718163" />
<meta name="backwpup_errors" content="0" />
<meta name="backwpup_warnings" content="0" />
<meta name="backwpup_jobid" content="1" />
<meta name="backwpup_jobname" content="Testing" />
<meta name="backwpup_jobtype" content="CHECK" />
<meta name="backwpup_backupfilesize" content="0" />
<meta name="backwpup_jobruntime" content="0" />
<title>BackWPup Log for Testing from July 21, 2010 at 1:16 pm</title>
</head>
<body style="font-family:monospace;font-size:12px;white-space:nowrap;">
    Thread Starter jc_513

    (@jc_513)

    I tried the latest version…1.2.0. Still the same. Yes, my PHP is compiled with ‘–enable-memory-limit’. My hosting provider controls the version of PHP so I cannot upgrade to 5.2.X myself.

    This seems somewhat like or to be the same issue as Bassu’s ” ‘Run Now’ shows a blank page ” thread since he is showing running PHP 5.1.6 as well and showing no data in the Run Now screen.

    1. You are right. It would make no sense. I had description on the brain. I meant AD’s displayname. I have done several tests in my dev environment where I cannot login without using the AD displayname instead of the AD samaccountname. In my test environment I have a samaccount name of aaabbb and a displayname of aaabbb_disp. Using this plugin I cannot locate / login with the samaccount name of aaabbb only the displayname aaabbb_disp. If the AD display name is blank I still cannot login. However, through all this I think my issue is/was around the fact that my dev environment did not have the configuration setting for Account Suffix. It was empty. Setting it made to auth’ing work as expected. Not having it configures makes the auth’ing work against the displayname for some reason. A question does come to mind is if there are multiple @domain.tld options that could be applied, for one example a parent – child domain, how would authentication be affected with a set appended suffix if auth’ing across domain?

    2. This does help tremendously. Thanks for make the addition!! The key though is like item #1. If there is no suffix listed then when creating a user in WordPress all fields don’t get populated correctly.

    3. You have an option to send notification is an account is blocked. Is that AD locked or AD disabled? I’d like to see some type of integration and notification with an AD disabled account and the corresponding WordPress account. Is this possible?

    (is there a better place to discuss support on this product than here?)

    I think this plugin will fit my needs but I have a few snags limiting its use for me.

    Couple of questions that may help in its continued use…

    1. Can you add an option to auth off of AD’s samaccountname instead of AD’s description attribute?

    2. Can you add an option to set WordPress displayname to be them same as AD’s description (if not using the description to auth off of)?

Viewing 4 replies - 1 through 4 (of 4 total)