public static function print_site_consistency_field()
{
$field_name = 'make_site_consistent';
printf('<select id="%1$s" name="nelioab_settings[%1$s]" %2$s>', $field_name, self::get_basic_details());
?>
<option value='1'><?php
_e('Force Consistency All Along the Site', 'nelioab');
?>
</option>
<option value='0'<?php
if (!NelioABSettings::make_site_consistent()) {
echo ' selected="selected"';
}
?>
><?php
_e('Load Alternative Content for Tested Elements Only', 'nelioab');
?>
</option>
</select>
<div class="the-descr" style="display:none;"><span class="description"><?php
_e('When a page or post experiment is created, alternative titles, contents, featured images, and excerpts may be defined. Where and when is this alternative content loaded?', 'nelioab');
echo '<ul style="list-style-type:disc;margin-left:3em;">';
_e('<li><strong>Force Consistency</strong>. It ensures that your users see the same alternative version all along the site. If enabled, all pages will be loading the alternative information defined in your experiments. Note this setting does <strong>not</strong> consume more quota.</li>', 'nelioab');
_e('<li><strong>Tested Elements Only</strong>. If consistency is not forced, the alternative contents will be loaded when accessing the tested page or post only. Thus, for instance, it is possible that a user sees the original title and featured image of a tested post in a widget, but a different, alternative title and featured image when she accesses that very same post (which may be confusing).</li>', 'nelioab');
echo '</ul>';
?>
</span></div><?php
}