Website Slider Fix & Payment Form Strategy — 2026-04-05

Overview

Working session with Diana Henry (Didion) and developer Ishaque to resolve a duplicate slider on the Culinary Collection page and strategize a replacement for the current Square/WP EasyPay payment workflow. The team diagnosed a Divi theme limitation requiring custom code for slider management, and converged on using a single Gravity Form with conditional logic to trigger PayPal payments.

Attendees:
- Diana Henry — Didion (dhenry@didioninc.com)
- Melissa Cusumano — Asymmetric
- Michal Bielerzewski — Asymmetric
- Ishaque Mahmud — Developer

Next call: Wednesday, December 10 at 3:00 PM

Key Decisions

1. Slider edits require direct functions.php changes. The Culinary Collection page slider is custom-coded (Slick Slider) in the theme's functions.php — it cannot be edited through the Divi visual builder. Any future changes (adding/removing items, text edits) must be made in code.

2. Duplicate slider fixed via CSS hide + code. Ishaque resolved the doubled slider by hiding the duplicate with a CSS class targeting the master slider element. A follow-up code fix will prevent recurrence.

3. WP EasyPay cannot connect to PayPal. The existing Square/WP EasyPay payment forms are incompatible with PayPal. Rebuilding in WP Forms Premium was considered but rejected in favor of Gravity Forms, which is already installed.

4. Preferred path: single Gravity Form with conditional logic. One form captures user/company info, then conditional logic routes to the correct PayPal payment based on the partnership selected. This avoids new plugins and centralizes data collection.

5. Corn Masa Flour page to be disabled. The page is a legacy duplicate of the Culinary Collection / Masa Arepa page and is not linked anywhere live.

Action Items

Topic Detail

Culinary Collection Slider — Duplicate & Edit Access

Diana noticed the scrolling product slider on the Culinary Collection page had doubled, and could not find where to edit it from the WordPress backend. Ishaque joined the call and explained:

• The slider is built with Slick Slider via custom PHP in theme/functions.php — it is not a Divi module and cannot be managed through the visual builder.
• To add or remove items, you locate the relevant slider block in functions.php, copy or delete the image/label code block, and update the image URL (uploaded first via Media Library).
• To fix the duplication, Ishaque added a CSS rule targeting the master slider class to hide the duplicate. A permanent code fix will follow.
• Lesson learned: Divi has limitations for custom dynamic content. Future design work on this site should account for the need to write custom code for anything beyond static Divi modules.

"This website is in Divi theme. In Divi theme, some things we cannot handle. For this, we need to write some custom code." — Ishaque

Ishaque will send a standalone recording (separate from this Fathom) demonstrating the edit process so Diana can make future changes independently.

Additional cleanup: The "Nachos" item was also identified for removal from the slider. Text corrections needed on both the Culinary Collection and Masa Arepa pages: "tamale" → "tamales" and "arepa" → "arepas".

Payment Form Strategy — Replacing Square/WP EasyPay with PayPal

Diana had previously attempted to build a standalone PayPal button page to test a simpler payment flow. The button did not redirect to PayPal on click — it returned a "thank you" confirmation without processing payment or capturing any user data.

Current state:
- Partnership purchase pages use WP EasyPay (Square integration).
- Square allows processing fees to be passed to the buyer; PayPal does not — this is a known business constraint with no current solution.
- WP EasyPay does not support PayPal. Connecting them would require custom code, which the team wants to avoid.

Requirements Diana outlined:
- Capture company name, contact person, and partnership selected.
- Support invoice generation (some partners require formal invoices).
- Handle multiple partnership tiers (from ~$75 silent auction items up to $10,000+ sponsorships).
- Ideally collect golfer names at time of purchase, though in practice these are usually provided later.

Proposed solution:
A single Gravity Form with:
- Fields for contact/company info (consistent across all partnerships)
- A dropdown or selection field for partnership type
- Conditional logic that triggers the correct PayPal payment link based on the selection

Ishaque confirmed this is feasible if the required fields are consistent across partnership types. If form fields differ significantly per partnership, separate forms may be needed.

"Could one Gravity Form be created with a selection of partnership and/or silent auction item? And could there be a tree — when you select X, Y happens?" — Diana

The team agreed to avoid adding new form plugins (e.g., WP Forms Premium) and to consolidate around Gravity Forms, which is already in use on the site.

Related

• ^[1]
• ^[2]