Think I got it worked out for both bugs. Ok...for the RichText selection bug...it was something simple.
In mutate_tmplvars.dynamic.action.php, around line 309:
<option value="richtext" <?php echo ($content['display']=='richtext'||$content['type']=='htmlarea')? "selected='selected'":""; ?>>RichText</option>
I think it needs to be this:
<option value="richtext" <?php echo ($content['type']=='richtext'||$content['type']=='htmlarea')? "selected='selected'":""; ?>>RichText</option>
Looks like the $content variable was mistakenly set to ’display’ instead of ’type’.
Now...for the other bug, open up templvars.inc.php. Go to any line that includes this:
$index_list = ParseIntputOptions(ProcessTVCommand("",$field_elements));
Now, I knew that the TV’s weren’t being display due to a problem with one of these functions. I took a look at the ProcessTVCommand function and noticed something...it only accepts one variable, not two. So it would seem that taking out the first "blank" variable would do the trick:
$index_list = ParseIntputOptions(ProcessTVCommand($field_elements));
As a test, I did this with the listbox-multiple case statement and the problem went away. Hmm...what’s the empty quoted variable being passed used for anyways? What’s odd is that the formatting for the ProcessTVCommand call in the $index_list variable existed in the previous Technology Preview...so I’m not sure what’s different in the TV functions to make the behaviour change like this. At any rate, at least we know now that the ProcessTVCommand only accepts a single input value so changing all instances to reflect this would need to be addressed.
That’s all for now...more to come I’m sure.
MODX Staff
