jsa922

Michael,

That works. There may be another solution that I stumbled on.

After posting the log file data for you I started looking at my PHP references and doing some online searching. For reasons unclear to me, the “value” of a checkbox somehow is being ultimately treated, relative to the variable it’s supposed to be in, as a single entry in a multidimensional array. I tried the following code, therefore:

$chgMod = $formData->posted_data['Mod'][0] ? '–25' : '';
//And...
$flagNew = $formData->posted_data['NewCl'][0] ? 'NEW—' : '';

This also corrected the problem. From a “proper” programming viewpoint, I’m not sure which is best, but the problem now appears to be fixed, one way or the other. Thanks for helping me get there!!

The code is certainly a lot tighter. However, regardless of whether I click the “New Client” or “Modifier” boxes or leave them unchecked, the revised routine appends “–25” to every charge code and prefixes “NEW–” before every Client ID. Is it possible that there is something being passed with the posted data that makes it look like these boxes have been checked. When I go to the “formal” full view of the whole DB on the CFDB admin page, those columns are blank when they should be. Very odd.

I tried edit="$_POST(edstatus)" but it still behaves as if it wereedit=”false”`. Any other thoughts?

OK, that’s encouraging. I’ll try Shortcode Exec PHP, as my coding skills in PHP may not be up to registering the short code via Add Actions And FIlters.

I had an idea that would be the case for each, but wanted to be sure. The Admin access limitation addition as it stands is VERY helpful! Thanks for such a useful plugin!

Thanks! I’ll eagerly await any updates that add even more control to this already great plugin.

I tried the dt_options suggestion: it worked perfectly. Thank you.

One more matter, if I may. You’ve posted about a shortcode to search the DB using a simple form. You had helped me on one use of it earlier. I am trying to implement it on a page that tracks vacations for the partners. I carefully copied the shortcode that works perfectly on the client ID lookup page (where I needed the dt_options code), making the necessary changes to fit the tracking form/CFDB entries, and a new lookup form. This one uses a selection list that contains the preformatted year specifications (we run our vacations on an “academic year” from July to June) that I used to create the DB. It doesn’t work. I can make it work fine if I use a type="text" for the criterion input, but not using <select> coding. Does the latter not pass the value to filter on POST? I didn’t want to try <datalist> owing to its less universal browser implementaion. Here is my code:

<form action="" method="POST">
<span style="font-size:18px;">Select Vacation Year to View</span>
<select name="vysel">
<option value="7-2014 thru 6-2015">7-2014 thru 6-2015</option>
<option value="7-2015 thru 6-2016">7-2015 thru 6-2016</option>
<option value="7-2016 thru 6-2017">7-2016 thru 6-2017</option>
<option value="7-2017 thru 6-2018">7-2017 thru 6-2018</option>
<option value="7-2018 thru 6-2019">7-2018 thru 6-2019</option>
</select>
<input type="submit" value="Go" />
</form>
[cfdb-table form="Vacation Tracking" filter="VacationYear~~/.*$_POST(vysel).*/i" show="VacationYear,Partner,VacClaim"]

When the page loads, all the DB entries appear, but when I select the desired year, nothing changes. If I change to [cfbd_datatable...] the “Search” box works fine, so the DB appears to be OK. Thanks!

Thanks, again! Adding the ‘value=”1″‘ did the trick!

BTW, I installed your Actions and Filters plugin and used the advice from your post on “Preventing Duplicate Entries” to ensure this…it works GREAT! Now I can add other custom actions to secure my pages better.

Thanks for making this all work so easily. Next up is to move up to the editor extension, as it’s clear I will need to provide a way for my partners to change project lists over time, especially not that I’ve achieved success with limiting clients to one DB entry each.

I think this specific thread is now “resolved,” as any further questions will pertain to using the editor extension. Thanks so much for your help!