Forum Replies Created

Viewing 15 replies - 16 through 30 (of 216 total)
  • Thread Starter wpress2010

    (@wpress2010)

    Divi’s Code module has no problem rendering Pods shortcodes. I found that my problem was that somehow I had checked the box on the template that said “Show to admins only”. Once I unchecked it, the template displayed the correct contents within the Divi Code module. Oddly enough, I also found a reference on the Web for inserting some code into the wp-config and functions.php files that allegedly make Pods work with Divi, but even though that reference was fairly recent, I found that it did not work anyhow.

    Thread Starter wpress2010

    (@wpress2010)

    Hmm. I did not notice that – thank you! I deactivated that plug and activated the WooCommerce PayPal Checkout Gateway: by WooCommerce – 2.1.3 – we’ll see if that solves the problem. I am not sure how the extra plug got in there. The site in question doesn’t do much in the way of actual e-commerce.

    Thread Starter wpress2010

    (@wpress2010)

    Thanks. Here it is:

    
    ### WordPress Environment ###
    
    WordPress address (URL): 
    Site address (URL): 
    WC Version: 6.9.4
    REST API Version: ? 6.9.4
    WC Blocks Version: ? 8.3.3
    Action Scheduler Version: ? 3.4.0
    Log Directory Writable: ?
    WP Version: 6.0.2
    WP Multisite: –
    WP Memory Limit: 495 MB
    WP Debug Mode: –
    WP Cron: ?
    Language: en_US
    External object cache: –
    
    ### Server Environment ###
    
    Server Info: Apache
    PHP Version: 7.4.29
    PHP Post Max Size: 20 MB
    PHP Time Limit: 120
    PHP Max Input Vars: 1000
    cURL Version: 7.64.0
    OpenSSL/1.1.1n
    
    SUHOSIN Installed: –
    MySQL Version: 5.7.36-39-log
    Max Upload Size: 20 MB
    Default Timezone is UTC: ?
    fsockopen/cURL: ?
    SoapClient: ?
    DOMDocument: ?
    GZip: ?
    Multibyte String: ?
    Remote Post: ?
    Remote Get: ?
    
    ### Database ###
    
    WC Database Version: 6.9.4
    WC Database Prefix: wp_
    Total Database Size: 360.80MB
    Database Data Size: 352.35MB
    Database Index Size: 8.45MB
    wp_woocommerce_sessions: Data: 17.06MB + Index: 0.23MB + Engine MyISAM
    wp_woocommerce_api_keys: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_attribute_taxonomies: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_downloadable_product_permissions: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_order_items: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_order_itemmeta: Data: 0.01MB + Index: 0.01MB + Engine MyISAM
    wp_woocommerce_tax_rates: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_tax_rate_locations: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_shipping_zones: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_shipping_zone_locations: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_shipping_zone_methods: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_payment_tokens: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_payment_tokenmeta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_log: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    smackuci_events: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    smackuci_history: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_actionscheduler_actions: Data: 0.03MB + Index: 0.03MB + Engine MyISAM
    wp_actionscheduler_claims: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_actionscheduler_groups: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
    wp_actionscheduler_logs: Data: 0.02MB + Index: 0.02MB + Engine MyISAM
    wp_commentmeta: Data: 0.04MB + Index: 0.02MB + Engine MyISAM
    wp_comments: Data: 0.02MB + Index: 0.02MB + Engine MyISAM
    wp_create_map: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_csp3_subscribers: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_group_map: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_links: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_map_locations: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_nextend2_image_storage: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_nextend2_section_storage: Data: 0.03MB + Index: 0.01MB + Engine MyISAM
    wp_nextend2_smartslider3_generators: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_nextend2_smartslider3_sliders: Data: 0.01MB + Index: 0.00MB + Engine MyISAM
    wp_nextend2_smartslider3_sliders_xref: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_nextend2_smartslider3_slides: Data: 0.03MB + Index: 0.00MB + Engine MyISAM
    wp_options: Data: 94.19MB + Index: 0.95MB + Engine MyISAM
    wp_pmxi_files: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_pmxi_hash: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_pmxi_history: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_pmxi_images: Data: 0.02MB + Index: 0.01MB + Engine MyISAM
    wp_pmxi_imports: Data: 0.09MB + Index: 0.00MB + Engine MyISAM
    wp_pmxi_posts: Data: 0.28MB + Index: 0.33MB + Engine MyISAM
    wp_pmxi_templates: Data: 0.02MB + Index: 0.00MB + Engine MyISAM
    wp_postmeta: Data: 99.53MB + Index: 3.32MB + Engine MyISAM
    wp_posts: Data: 51.95MB + Index: 1.29MB + Engine MyISAM
    wp_redirection_404: Data: 0.37MB + Index: 0.07MB + Engine MyISAM
    wp_redirection_groups: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_redirection_items: Data: 0.00MB + Index: 0.02MB + Engine MyISAM
    wp_redirection_logs: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_relevanssi: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_relevanssi_log: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_relevanssi_stopwords: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_termmeta: Data: 0.02MB + Index: 0.02MB + Engine MyISAM
    wp_terms: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
    wp_term_relationships: Data: 0.20MB + Index: 0.54MB + Engine MyISAM
    wp_term_taxonomy: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
    wp_usermeta: Data: 0.03MB + Index: 0.02MB + Engine MyISAM
    wp_users: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
    wp_vtprd_purchase_log: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_vtprd_purchase_log_product: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_vtprd_purchase_log_product_rule: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wc_admin_notes: Data: 0.04MB + Index: 0.00MB + Engine MyISAM
    wp_wc_admin_note_actions: Data: 0.02MB + Index: 0.01MB + Engine MyISAM
    wp_wc_category_lookup: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wc_customer_lookup: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
    wp_wc_download_log: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wc_order_coupon_lookup: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wc_order_product_lookup: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
    wp_wc_order_stats: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
    wp_wc_order_tax_lookup: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wc_product_attributes_lookup: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wc_product_download_directories: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
    wp_wc_product_meta_lookup: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
    wp_wc_rate_limits: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wc_reserved_stock: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wc_tax_rate_classes: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
    wp_wc_webhooks: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wdp_orders: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wdp_order_items: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
    wp_wdp_persistent_rules_cache: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wdp_rules: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wfblockediplog: Data: 0.10MB + Index: 0.07MB + Engine MyISAM
    wp_wfblocks7: Data: 0.11MB + Index: 0.07MB + Engine MyISAM
    wp_wfconfig: Data: 73.98MB + Index: 0.02MB + Engine MyISAM
    wp_wfcrawlers: Data: 0.01MB + Index: 0.01MB + Engine MyISAM
    wp_wffilechanges: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wffilemods: Data: 5.25MB + Index: 0.67MB + Engine MyISAM
    wp_wfhits: Data: 4.47MB + Index: 0.18MB + Engine MyISAM
    wp_wfhoover: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wfissues: Data: 0.01MB + Index: 0.01MB + Engine MyISAM
    wp_wfknownfilelist: Data: 3.76MB + Index: 0.20MB + Engine MyISAM
    wp_wflivetraffichuman: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wflocs: Data: 0.01MB + Index: 0.00MB + Engine MyISAM
    wp_wflogins: Data: 0.34MB + Index: 0.08MB + Engine MyISAM
    wp_wfls_2fa_secrets: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_wfls_settings: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_wfnotifications: Data: 0.10MB + Index: 0.01MB + Engine MyISAM
    wp_wfpendingissues: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wfreversecache: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wfsnipcache: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wfstatus: Data: 0.14MB + Index: 0.06MB + Engine MyISAM
    wp_wftrafficrates: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wpgmza: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wpgmza_circles: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wpgmza_maps: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wpgmza_polygon: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wpgmza_polylines: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wpgmza_rectangles: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_xsg_sitemap_meta: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    
    ### Post Type Counts ###
    
    _pods_field: 5
    _pods_pod: 1
    _pods_template: 2
    acf-field: 10
    acf-field-group: 1
    attachment: 871
    custom_css: 4
    customize_changeset: 1
    et_body_layout: 2
    et_footer_layout: 1
    et_header_layout: 1
    et_pb_layout: 35
    et_template: 10
    et_theme_builder: 1
    is_search_form: 2
    jetpack_migration: 2
    jp_img_sitemap: 1
    jp_sitemap: 4
    jp_sitemap_index: 1
    jp_sitemap_master: 1
    nav_menu_item: 76
    new: 294
    page: 54
    post: 7957
    product: 15
    revision: 3217
    seedprod: 1
    shop_order: 13
    tablepress_table: 2
    wpautoterms_page: 1
    wpcf7_contact_form: 3
    wpsc_cart_orders: 77
    
    ### Security ###
    
    Secure connection (HTTPS): ?
    Hide errors from visitors: ?
    
    ### Active Plugins (29) ###
    
    404page - your smart custom 404 error page: by Peter Raschendorfer – 11.3.1
    Advanced Custom Fields: by WP Engine – 6.0.1
    Advanced Dynamic Pricing for WooCommerce: by AlgolPlus – 4.1.5
    WP AutoTerms: by WP AutoTerms – 2.4.9
    BackupBuddy: by iThemes – 8.8.0
    Better Search Replace: by Delicious Brains – 1.4.1
    Classic Editor: by WordPress Contributors – 1.6.2
    Classic Widgets: by WordPress Contributors – 0.3
    Coming Soon Page, Maintenance Mode, Landing Pages & WordPress Website Builder by SeedProd: by SeedProd – 6.15.4
    Contact Form 7: by Takayuki Miyoshi – 5.6.3
    Custom Sidebars: by WebFactory Ltd – 3.35
    Yoast Duplicate Post: by Enrico Battocchi & Team Yoast – 4.5
    Google XML Sitemaps: by Auctollo – 4.1.5
    PayPal for WooCommerce: by Angell EYE – 2.1.11
    Redirection: by John Godley – 5.3.4
    Regenerate Thumbnails: by Alex Mills (Viper007Bond) – 3.1.5
    Advanced Editor Tools (previously TinyMCE Advanced): by Automattic – 5.6.0
    Transients Manager: by WPBeginner – 2.0.3
    W3 Total Cache: by BoldGrid – 2.2.4
    Extra product options For WooCommerce | Custom Product Addons and Fields: by ThemeHigh – 3.1.7
    WooCommerce Shipping & Tax: by WooCommerce – 1.26.3
    WooCommerce: by Automattic – 6.9.4
    Wordfence Security: by Wordfence – 7.6.2
    WP Simple Shopping cart: by Tips and Tricks HQ
    Ruhul Amin
    mra13 – 4.5.9
    
    WP All Import: by Soflyy – 3.6.8
    WP Maps: by flippercode – 4.3.6
    WP Meta and Date Remover: by Prasad Kirpekar – 1.9.7
    WPSSO Core (Premium): by JS Morisset – 12.1.1
    WPSSO Update Manager: by JS Morisset – 4.12.3
    
    ### Inactive Plugins (5) ###
    
    Ivory Search: by Ivory Search – 5.4.8
    Relevanssi: by Mikko Saari – 4.17.1
    WebToffee PayPal Express Checkout Payment Gateway for WooCommerce ( Free ): by WebToffee – 1.7.5
    WooCommerce PayPal Checkout Gateway: by WooCommerce – 2.1.3
    WP Extended Search: by 5um17 – 2.1.1
    
    ### Dropin Plugins (1) ###
    
    advanced-cache.php: advanced-cache.php
    
    ### Settings ###
    
    API Enabled: –
    Force SSL: –
    Currency: USD ($)
    Currency Position: left
    Thousand Separator: ,
    Decimal Separator: .
    Number of Decimals: 2
    Taxonomies: Product Types: external (external)
    grouped (grouped)
    simple (simple)
    variable (variable)
    
    Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
    exclude-from-search (exclude-from-search)
    featured (featured)
    outofstock (outofstock)
    rated-1 (rated-1)
    rated-2 (rated-2)
    rated-3 (rated-3)
    rated-4 (rated-4)
    rated-5 (rated-5)
    
    Connected to WooCommerce.com: –
    Enforce Approved Product Download Directories: –
    
    ### WC Pages ###
    
    Shop base: #12447 - /books-publications/
    Cart: #11597 - /cart/
    Checkout: #11480 - /checkout/
    My account: #11481 - /my-account/
    Terms and conditions: ? Page not set
    
    ### Theme ###
    
    Name: Divi Child Theme
    Version: 1.0.0
    Author URL: 
    Child Theme: ?
    Parent Theme Name: Divi
    Parent Theme Version: 4.18.0
    Parent Theme Author URL: https://www.elegantthemes.com
    WooCommerce Support: ?
    
    ### Templates ###
    
    Overrides: Divi-child/woocommerce/single-product.php
    
    ### Admin ###
    
    Enabled Features: activity-panels
    analytics
    coupons
    customer-effort-score-tracks
    experimental-products-task
    experimental-import-products-task
    experimental-fashion-sample-products
    experimental-product-tour
    shipping-smart-defaults
    shipping-setting-tour
    homescreen
    marketing
    mobile-app-banner
    navigation
    onboarding
    onboarding-tasks
    remote-inbox-notifications
    remote-free-extensions
    payment-gateway-suggestions
    shipping-label-banner
    subscriptions
    store-alerts
    transient-notices
    wc-pay-promotion
    wc-pay-welcome-page
    
    Disabled Features: minified-js
    new-product-management-experience
    settings
    
    Daily Cron: ? Next scheduled: 2022-09-28 21:58:27 -05:00
    Options: ?
    Notes: 102
    Onboarding: completed
    
    ### Action Scheduler ###
    
    Complete: 90
    Oldest: 2022-08-29 19:56:10 +0000
    Newest: 2022-09-28 15:53:08 +0000
    
    Failed: 1
    Oldest: 2022-03-18 21:48:27 +0000
    Newest: 2022-03-18 21:48:27 +0000
    
    Pending: 3
    Oldest: 2022-09-28 20:42:34 +0000
    Newest: 2022-09-30 00:17:09 +0000
    
    ### Status report information ###
    
    Generated at: 2022-09-28 15:18:58 -05:00
    
    Thread Starter wpress2010

    (@wpress2010)

    I don.t see any way to insert a graphic here to illustrate. But maybe this will help to explain. Here is a virtual product with 2 variables for the user to select from, “Membership type” and “Matching Gift”.

    [wp_cart_button name=”Individual Membership” price=”25.00″ var1=”Membership type|Renewal|New” var2=”Matching Gift?**|No|Yes”]

    I want to allow the user to select a quantity as well, like this:

    var3=”Quantity|1|2|3|4″

    But I don’t think the plug will recognize the quantity chosen and calculate the total for the quantity ordered from that – although it will display the dropdown just fine.

    Thread Starter wpress2010

    (@wpress2010)

    Solved: without too much extra work, I just decided to use the home page class to style the link, avoiding the whole “active” issue:

    body.home li#menu-item-231 a {
    color:red !important

    It’s difficult sometimes when taking over a site that hasn’t been touched in a long time, to make a few significant changes without having to essentially rewrite the whole thing. It would be nice to be able to add a custom class or id to a Custom Link menu item in the WP menu system.

    • This reply was modified 2 years, 8 months ago by wpress2010. Reason: typo
    Thread Starter wpress2010

    (@wpress2010)

    Yes, but here is what caused the red color:

    Originally, the conditional was intended to show one

    • element if a field existed, a different one if it didn’t, and then end the list:

      [if mlsid]

    • MLSID: {@mlsid}
    • [else]<li style=”list-style-type:none; padding:0; line-height:.5″> 
      [/if]

      While this worked, it threw the error. I changed it to this, and the red color went away:

      [if mlsid]

    • MLSID: {@mlsid}
    • [else]<li style=”list-style-type:none; padding:0; line-height:.5″> 
      [/if]

      So, the closing tag of the

      needed to be outside the conditional statements. I am not sure why the first version did not work, as the if/else just presents one bunch of code instead of another, depending on whether the condition is met. Either way, the
      is properly closed by

    .

    Thread Starter wpress2010

    (@wpress2010)

    Thanks, I guess it was no surprise that the Divi team didn’t know much about this. Divi does have some conditional module ability, but none of it relates to anything like the Pods coding. I was able to accomplish what I needed with Pods and CSS. I just used an [if] [else] statement to render different content if the returns were null.

    I had not noticed when Pods apparently added the [else] feature.

    It works perfectly, but the coding automatically turns some unrelated elements further down in the template a red color as if there were an HTML error, but there is not.

    Thread Starter wpress2010

    (@wpress2010)

    Thanks, I realize that. I am just trying to figure out the logic when the Pods conditionals return “nothing”.

    Thread Starter wpress2010

    (@wpress2010)

    Yes, this is very simple to do. I found that the best way to implement EDD within my Divi theme is like this:

    1.) Use Divi code module, put in code for sample mp3 file – which also calls the audio player. Good built-in support for styling author/title/album.

    2.) Use a separate Divi code module to put in the code for the “Purchase” (i.e., add to cart button) file – i.e., the complete mp3 file.

    Bu using separate Divi code modules, position of both Purchase button and player can be tweaked for all mobile platforms as well. Basic idea is to have a row <div> with 2 columns: one of about 80% width for audio player, second one of about 20% width for Purchase button.

    Thread Starter wpress2010

    (@wpress2010)

    Thanks. This works perfectly! I think that the Purchase buttons could be (1) made smaller – simple via CSS, and (2) for space-saving concerns, these buttons should be floated to the right of the audio player. Basically, there are 8 tracks to be offered, so moving the buttons to the same line as the player would help. Still working on that…

    Thread Starter wpress2010

    (@wpress2010)

    Thanks, I get it now. The UI does allow me to drag/drop cells within rows.

    Thread Starter wpress2010

    (@wpress2010)

    Thank you! I came up with this code and it works perfectly (the proxy code is set to “tomato”):

    function custom_proxy_validation($result,$tag){
            $type = $tag['type'];
            $name = $tag['name'];
            if($name == 'proxynumber'){
               $proxyNumber = isset( $_POST['proxynumber'] ) ? trim( $_POST['proxynumber'] ) : '';
    										
                $the_value = preg_match("/tomato/",$_POST[$name]);
                if($proxyNumber == "" || $the_value == false ){ 
                    $result->invalidate( $tag, "please enter valid proxy number" );
                }
            }
            return $result;
        }
        add_filter('wpcf7_validate_text','custom_proxy_validation', 10, 2);
        add_filter('wpcf7_validate_text*', 'custom_proxy_validation', 10, 2);
    Thread Starter wpress2010

    (@wpress2010)

    Thanks, Jory. I checked it again, and it indeed is working as I described.
    In my particular test, there are 8 Properties that have the Catgeory of ‘HB’ and of those 8, only 3 also have the Category of ‘For Sale’ The code returns just the 3.

    I did have a look at WP Query, and it seems pretty straightforward.

    Thread Starter wpress2010

    (@wpress2010)

    After a bit more experimentation, I find that the following code works for my exact purposes:

    [pods name=”property” where=”category.name= ‘HB’ AND where=”category.name= ‘For Sale’ ” template=”HB For Sale” orderby=”post_date DESC”]

    I don’t think that this is in any way an unusual or complicated query. Still thinking about why this strategy works – where others that seemed pretty much the same thing – don’t.

    Thread Starter wpress2010

    (@wpress2010)

    Thank you. I think that there is perhaps some kind of problem with my thinking here. If this were an ordinary SQL query, it would be expressed something like this:

    SELECT *
    FROM property
    WHERE (category = ‘HB’ AND category <> ‘Sold’)

    I haven’t gone into the db to look at the tables. It seems as though the basic problem is that a Pod can have more than one category assigned to it.

Viewing 15 replies - 16 through 30 (of 216 total)