WISECP Form Builder Not Sending Messages? A Datawise Theme Guide with Fixes and Featu...

WISECP Form Builder Not Sending Messages? A Datawise Theme Guide with Fixes and Feature Ideas

Sometimes the real problem on a WISECP website is not a major system failure but a small break in a very important flow. That was exactly the case in this support ticket. The customer had created a form with FonPageBuilder, but messages were not being sent even though the overall mail system was active. On top of that, they had already made custom code changes in the theme and understandably did not want those edits to be broken during troubleshooting.

This kind of ticket is more than a one-time fix. It is the kind of issue that turns into a useful knowledge-base article because it touches both functionality and user experience. In this case, the immediate problem was resolved for the customer, and the related suggestions were also added to future development notes.

The Datawise theme includes FonPageBuilder, and according to the official product information, it provides a drag-and-drop Form Builder that lets users create custom forms on any page. Official product descriptions also highlight the availability of a comparison table component and a custom email template as part of the theme ecosystem. In the installation documentation, email-template.txt is listed as part of the package as well.

Another important detail from this ticket was the customer’s warning not to break existing theme edits. That concern is completely valid. Datawise installation notes explicitly state that if you have modified PHP or CSS files, you should compare your edited files with the update package before applying changes, otherwise your custom work may be lost. The same notes strongly recommend taking a backup first. On the styling side, Datawise also supports a custom.css approach so visual overrides can be handled in a dedicated custom stylesheet instead of directly hacking core theme files, which is, tragically, still a favorite human pastime.

The customer then shared three particularly useful improvement ideas. First, browser autofill should be optionally disabled for forms, because automatic field filling can sometimes create bad input behavior. Second, there should be a separate outgoing email flow for the end user, especially in cases like a demo request form where the user should receive additional product or demo information. That makes practical sense, because the admin notification and the user-facing confirmation email serve different purposes.

The third suggestion was even more commercially relevant: on pricing tables and comparison tables, it should be possible to hide the visible price and replace the purchase button with custom text or a custom link. That matters for quote-based sales, demo requests, consultation pages, or products that are meant to lead visitors into a contact flow instead of an instant checkout. Official WISECP translation resources clearly include fields for an “external purchase link” and a “buy button name.” Datawise update notes also state that handling of the External Purchase Link in FonPageBuilder pricing tables was improved and that External Button Title support was integrated for special product groups. In other words, this need is real, recognized, and already partly reflected in the product direction.

One very practical lesson from this ticket is that using a fake price such as 1 just to force a visual layout is not a stable solution. In the customer’s case, that workaround started to fail when currency changes made the actual pricing logic visible again. That is exactly the kind of shortcut that looks clever for ten minutes and then starts embarrassing the site owner later. A cleaner approach is to use external-link logic and custom button behavior where possible, and to treat user copy emails, autofill behavior, and form notifications as separate design decisions rather than one bundled afterthought.

The broader takeaway is simple: building a form in WISECP is only the beginning. A good implementation also considers how the form is delivered, how browser behavior affects the fields, what confirmation the end user receives, and what call-to-action structure appears in pricing boxes. These details may look minor in the admin panel, but they directly affect conversion quality, support load, and the overall professionalism of the site.