☆ A M B ☆
set the TV value to an @SELECT binding
☆ A M B ☆
The @SELECT binding returns the result set of a SELECT SQL query. Simply enter the query as a normal sql SELECT query. Placeholders can be used for variable values. Two placeholders are already set, [+DBASE+] and [+PREFIX+], which are set to your MODx database name and table prefix. Other placeholders can be set in snippets and @EVAL TVs. Just make sure the snippet or @EVAL TV is called before the @SELECT TV.
This binding will return the raw result set of the SELECT query. You can process this either with your own snippet or configure the @SELECT TV to use the dataset output widget.
Let’s say you have a listing of restaurants, and you want to display a list of restaurants in a given zip code. First you would set a placeholder with the zip code; how you get this is irrelevant to this discussion.
$modx->setPlaceholder('restaurantzip', $zip);
This code could be in a snippet processing a user-submitted form, or in an @EVAL TV.
Then you would query your restaurant table (or whatever table you have the zip code of your restaurants in) using the placeholder you’ve set. Make sure to add the single-quotes around the placeholder if the value will be a string.
@SELECT * FROM [+PREFIX+]restuarants WHERE zip='[+restaurantzip+]'
This will give you a result set that you can process as you would normally process the result set of any SELECT query.
☆ A M B ☆
You could also look a the ManagerManager tagging widget for the multi-categories thing which works quite nicely.
mm_widget_tags(($fields, $delimiter, $source, $display_count, $roles, $templates)
Changes the manager widget for this text field to tag-friendly format - e.g. it will display a clickable list of all other tags which have been used for this field.
$fields: The name(s) of the template variables this should apply to. Can accept multiple field separated by a comma. [Required]
$delimiter: Which character separates individual tags within this field [Optional - default is comma)
$source: The names(s) of the template variables the list of tags should come from. This allows the list of tags to come from a different field that the widget. By default it uses all the TVs listed in $fields [Optional - default is same as $fields]
$display_count: Display the number of documents using each tag (in brackets after it) [Optional - boolean - default is false]
$roles: comma separated list of role IDs this should be applied to. Leave empty (or omit) for all roles [Optional - default is all]
$templates: comma separated list of template IDs this should be applied to. Leave empty (or omit) for all templates [Optional - default is all]
mm_widget_tags(’docTags’); // Adds the tag editing widget to the docTags template variable wherever it appearsmm_widget_tags(’docTags,blogTags’); // Adds the tag editing widget to the docTags and blogTags template variables wherever they appear - making all previous values from both template variables available in both tagsmm_widget_tags(’docTags’, ’,’, ’’, ’1’, ’’, ’2’); // Adds the tag editing widget to the docTags template variables in template 2, and shows the number of times each tag has been used
Note: TV(s) must be a text input field
☆ A M B ☆
I’m going to go ahead and move forward with FoxyCart integration.
I wouldn’t bother (at all) with creating a new table. Just use MODx documents with TVs for your products. WAY easier. The only reason to create a separate table would be if you had a massive number of products.
Okay, off to examine the tables in MODx, not sure if I want to make a separate product table yet.
☆ A M B ☆
<form class="foxycart" action="https://smokymtguitars.foxycart.com/cart" method="post" accept-charset="utf-8">
<table width="100%" border="0">
<tr class="gallery">
<td class="feature"><p><a href="#" >
<img src="assets/images/sampleproductdetail.jpg" alt="Starter" ></a></p></td>
<td>
<p class="thumbnails"><a href="assets/images/313s.jpg" ><img src="assets/images/more-thumbs.jpg" alt="number one" width="100" height="128"></a></a></p>
<p class="thumbnails"><a href="assets/images/sampleproductdetail.jpg"><img src="assets/images/more-thumbs.jpg" alt="Two" width="100" height="128"></a></p>
<p class="thumbnails"><a href="assets/images/sampleproductdetail.jpg"><img src="assets/images/more-thumbs.jpg" alt="Three" width="100" height="128"></a></p>
</td></tr>
<tr>
<td width="71%" height="333"><p class="detailscopy">[*content*] </p></td>
<td width="29%"><p class="email"><a href="#">Email this to a Friend! </a></p>
<p class="price">Price: [*listPrice*] </p>
<p class="sale">Sale Price: [*salePrice*] </p>
<p class="yousave">You Save: <br>
<input type="hidden" name="name" value="[*prodName*]" />
<input type="hidden" name="price" value="[*salePrice*]" />
<br>
<input name="add_to_cart" type="image" src="assets/images/addtocart.gif" alt="Add to Cart " class="submit" align="top">
</tr>
</table>
</form>
☆ A M B ☆
I meant use a @SELECT binding to allow the TV selections (checkboxes) to be populated from MODx document
☆ A M B ☆
☆ A M B ☆
mm_widget_tags('docTags');