Luke Stephens
Forum Replies Created
-
Forum: Plugins
In reply to: [Contact Form 7] Dynamic form data not populatingHey Jeff, Thanks for the update! I wonder if the emails you are getting are form fills from either links: https://fannysatcrossroads.com/contact or https://fannysatcrossroads.com/contact-1/, rather than https://fannysatcrossroads.com/contact-2/.
Here are two of the issues I encountered troubleshooting our ROI calculator’s CF7 form:
1. Mail Tags Don’t Match Form Fields: If the mail template uses tags like [your-name], [your-email], etc., those exact tags must also exist in the Form tab above. If, for example, the form field is [text* your-name], but the mail template says [name], the email will be blank. I added [hidden calculator-csv class:wpcf7-calculator-result] to the “Form” tab in WP CF7, and the Mail’s Message Body contains [calculator-csv] to display these results which the users submitted.2. Using the Same Email for To/From: Sometimes, if the “To” and “From” addresses are the same (e.g., both are [email protected]), some hosts or spam filters will block or blank out the message. Try using a different “From” address, or use the default CF7 mail tag for the sender. For the project I’m working on, we needed CF7 to send the form results to the user who filled out the form from our customer support address, so I used [your-email] for “To” and [_site_title] for “From” field.
- This reply was modified 1 year ago by Luke Stephens.
Forum: Plugins
In reply to: [Contact Form 7] My email is not sending even after success messgaeYour page is private, so its not possible to diagnose from your link. Are you using [your-email] for “To:” and [_site_title] for “From:”?
Forum: Plugins
In reply to: [Contact Form 7] Changing Contact Form Submit ButtonWe recently worked through this exact issue on our own site and here’s the CSS that worked perfectly for us to style the Contact Form 7 submit button and keep everything on-brand:
/* --- SUBMIT RED BUTTON STYLING --- */
.formbox__btn-calc,
.formbox__btn-mail,
.wpcf7-form-control.wpcf7-submit {
background-color: #e30615 !important;
border-color: #e30615 !important;
color: #ffffff !important;
font-weight: 500;
padding: 10px 20px !important;
border-radius: 4px;
font-size: 16px;
display: inline-block;
min-width: 120px;
width: auto !important;
text-align: center;
}
.formbox__btn-calc:hover,
.formbox__btn-mail:hover,
.wpcf7-form-control.wpcf7-submit:hover {
background-color: #cc0513 !important;
border-color: #cc0513 !important;
}Tips:
- Swap
#e30615and#cc0513for your own brand’s colors if needed. - The
!importantensures your styles override any theme defaults. - This selector will style both the calculator and Contact Form 7 submit buttons for a consistent look.
- This reply was modified 1 year ago by Luke Stephens.
Forum: Plugins
In reply to: [Contact Form 7] Issue with Developer’s Custom Contact Form 7If the code snippet you posted is just a shortcode like [contact-form-7 id=”123″ title=”Contact form 1″] or uses standard Contact Form 7 tags (such as [text your-name], [email your-email], [submit “Send”]), that’s all standard syntax from the official plugin. In that case, you should be able to safely use the official version of Contact Form 7 without any issues.
However, if you see any custom shortcodes (for example, [custom_field] or [my-special-shortcode]) or PHP code that references wpcf7 functions or custom classes, that could indicate your previous developer made custom modifications. These might not be compatible with the official plugin out of the box.
A good way to check is to:
- Look for any non-standard tags in your form templates.
- Search your theme or plugin files for references to wpcf7 or “contact form 7” that aren’t part of the official plugin.
Before making any changes on your live site, it’s always a good idea to:
- Make a full backup of your website (files and database), so you can restore it if anything goes wrong.
- Test the official plugin on a staging or development site first, as you’ve already started doing. Compare the form output, email notifications, and any integrations (like Flamingo or custom mail handlers, SMTP) to make sure everything works as expected.
If everything in your forms uses the standard tags and shortcodes, you can be confident it’s from the official plugin and should work fine after the switch.
Conclusion:
- The form you’re using is a standard Contact Form 7 form.
- The fields (Name, Email, Subject, How Can We Help?, Resume Upload) are all standard CF7 fields.
- The submit button is a standard <button> with some inline styles for color and size.
- The success message (Thank you for your message. It has been sent.) is the default CF7 response.
- The hidden fields at the bottom are for anti-spam and bot detection (also standard for CF7).
- There are no custom shortcodes, custom field types, or custom PHP hooks visible in this form’s markup.
What this means:
- This form is fully compatible with the official Contact Form 7 plugin.
- You can safely update or replace the plugin with the official version without breaking this form.
- Any customizations (if they exist) would be in the theme’s CSS for styling, or possibly in the mail template for email formatting—but not in the form’s structure or functionality.
Recommendation:
- As always, make a full backup before updating or replacing the plugin.
- Test the form on a staging/dev site after switching to the official plugin to confirm that emails, file uploads, and styling all work as expected.
- If you want to further customize the look or email output, you can do so via the CF7 form and mail templates—no custom code is required for the functionality you have here.
Summary: Your form is standard and should work perfectly with the official Contact Form 7 plugin. No custom code or special migration steps are needed based on what’s shown in your screenshot.
Do you need help locating this specific CF7 form in the WordPress admin or editing it?
Forum: Plugins
In reply to: [Contact Form 7] Dynamic form data not populatingHey Jeff,
I have been running into the exact same issue with WP-CF7 and Flamingo—trying to get clean, user-friendly email notifications from a custom ROI calculator (built in Calchub with grad students from WPI.) Instead, I kept getting either a single field or a raw data dump in the emails, which wasn’t ideal.
Noticed you’re working on Fannys at Crossroads. I am in Auburn, small world! I actually grew up on Lake Martin and even worked at Spring House back in high school.
One thing that helped us was creating separate hidden fields in the CF7 form for each result we wanted to email (like the ROI percentage and a detailed summary), then assigning those values in the calculator’s formula. That way, we could reference just those fields in the email template, instead of dumping the whole CSV or raw data.
If you’re still troubleshooting this, I’d be happy to share what’s worked (and what hasn’t) on my end more in-depth. Always fun to connect with someone local who’s working through the same challenges.
Best,
Luke
Forum: Plugins
In reply to: [Ajax Search Lite - Live Search & Filter] Ajax Search Lite UnusableUpdate: I have added WP extended search plugin and it has fixed this issue with the SKUs. It’s so fast, too. It works amazing now, i just have one more need. I really want to see a way to make the secondary sort function work. Maybe an advanced title or content field that would understand publish date? I just know that Ajax Search Lite’s secondary ordering by date descending does pickup. Any insight here is much appreciated!
This is why I need this… Look at our two example products. Product 1) “S10 Toolbox” and product 2) “drawer slide (s10)”. When someone searches ‘s10’ on the website, it shows a couple of dozen products that are considered accessories, like “paper holder grey (S10)”, are being classified as ‘more relevant’ than the product “S10 toolbox, 8 drawers”. I believe the latter is more relevant as the search term is the first word; however, that is not the case.
Forum: Plugins
In reply to: [Ajax Search Lite - Live Search & Filter] Ajax Search Lite UnusableI have now added WP extender, which brings back to big commerce products being searchable by SKU. I really dont know how it does this while ajax couldn’t; however i need any/all advice on using the two in unison. Your plugig is wha we use for the search shortcode in our header, so i dont want to get rid of it. I am trying to figure out the best way to pretty much only use ajax for the shortcode and for the live search on type. Having both causes a bit of lag, similiar to speeds when i originally reached. I just need to get back to instant speeds but while maintaining the accurate search results.
Thank you so much for bearing with me throughout all of these message the last couple of weeks.
Forum: Plugins
In reply to: [Ajax Search Lite - Live Search & Filter] Ajax Search Lite UnusableThanks for the response!
While the search function’s speed got fixed, we have a much more important issue that is causing our search queries to fail to read big commerce’s item_ID’s. I spent like 9 hours in customer support with WP Engine, and the only thing they can think it is is a database issue that has been around for a while (in search.php.) I know I was told the reason we downloaded ajax search lite originally was because our website’s default search function wouldnt work properly. Now, the WP Engine support tried everything as far as trying to restore several backups of the website and the search.php and other theme files that showed php error logs.
I really want to use Ajax Search, with quick results. When you search now, but dont hit enter (and let the Ajax live search qeue…), you can see that your plugin is able to pull the correct items. However, WordPress wont by default. Additionally, the override feature in Ajax Search Lite wont allow me to override the search results page.
Please, any insight here would be so helpful. I am new in this position, and this is the primary ‘task’ I have been given. I really don’t want to disappoint. I need to perform well in this task so that my capabilities shine, so to speak. Any advice or other information needed can be provided within minutes. Just let me know.
One last thing I’ll add is a Stackoverflow link to data I’ve compiled in this issue, as well as the actual PHP error log I see when search queries are running. Here are both stack overflow links, and here is the error log itself:
- PHP Warning: Attempt to read property “slug” on bool in /nas/content/live/sonictools/wp-content/plugins/bigcommerce/templates/admin/query-builder.php on line 68
- PHP Warning: Attempt to read property “term_id” on bool in /nas/content/live/sonictools/wp-content/plugins/bigcommerce/templates/admin/query-builder.php on line 67
Forum: Plugins
In reply to: [Ajax Search Lite - Live Search & Filter] Ajax Search Lite UnusableI hope we can find out if the plugin’s premium version would solve this issue before I get approval to add another plugin (Index WP MySQL For Speed) to our website. Either way, fixing this is one of my top priorities in the role. It is causing us to lose lots of potential sales.
I appreciate your continued help. If there is anything else I can offer you to assist with the troubleshooting, please let me know.
Additionally, I have just seen that you are out of the office until 9/4. I hope you enjoy your family vacation. Look forward to discussing this further! In the mean time, I have emailed this to you incase we cannot discuss it here.
(I have seen some tickets where you mention we cannot discuss paid plugins in these forums.)
- This reply was modified 2 years, 9 months ago by Luke Stephens.
Forum: Plugins
In reply to: [Ajax Search Lite - Live Search & Filter] Ajax Search Lite UnusableI am so sorry for such a late reply. I have been worknig on my 30/60/90 plan recently. However, i now have the login information to our WP back end and can continue these troubleshooting trials. One thing I have come to find out is that our website is using your plugin’s free version. This could very well be the issue. For us and all of our customers, it takes 30 seconds to maybe even 2-3 minutes per search. We do have several thousand products, which makes me think it could just be an issue with that we use the lite version.
Here is our debug data pasted into past.ee for your access: https://paste.ee/p/NbTM4#section0
If there is anything you would suggest to fix this issue, I would greatly appreciate it. I am new in this role and solving this would be a massive weight off my shoulders.
I appreciate your hands-on support as the creator of this plugin.
Thank you,
Luke Stephens