Ali Khallad
Forum Replies Created
-
Hello, any update on this, or should I mark it as resolved?
Hey @stumur , no there isn’t a way to do this by default in the plugin. This is a specific use case and might be best to use a JavaScript snippet to achieve this and since this is outside the scope of the support forum, I’ll mark this as resolved.
There is an option to control what columns appear by default

Hi Stu,
Not at the moment. The Number field does validate numeric input, but it doesn’t currently have a built-in option to lock typing to numbers only as the user types, remove the browser’s up/down arrows, or show red validation messages live before submit.
If you want stricter input control for something like a postcode, the better option for now would usually be a One Line Text field with a custom input mask instead of the Number field.
Hey @stumur ,
This is outside the scope of what the plugin does and we’re not sure what option could work for you. You might consider custom development to achieve your purpose. We might extend the plugin in the future with Views, but for the time being, this functionality isn’t available.
Hi Stu,
The boxed / centred layout is coming from Mega Forms’ HTML email template, so yes, that part is expected with the HTML template enabled. If you want to remove that wrapper and have the email sit more like a normal plain left-aligned email, switch this here:
Mega Forms > Settings > Emails > Template > Plain Template
Just note that if you use the plain template, Mega Forms will stop wrapping the email in its own HTML layout, so you would need to write the full email HTML yourself inside the email notification if you still want custom formatting.
As for the faint grey text at the bottom, Mega Forms does have a footer text setting here:
Mega Forms > Settings > Emails > Footer Text
so that is the first place to check.
That said, the default Mega Forms footer is just the site title, not a reply address plus website tagline, so if that exact text is appearing, it may be coming from a custom footer value, another mail-related plugin, or the email client itself rather than Mega Forms core.
Hi Stu,
I wouldn’t want to add that globally in the plugin, because it changes the submit UX for every user, not just heavier forms like yours.
But for your site, yes, you can handle it with a small custom snippet instead.
Add this to your theme’s functions.php or a snippets plugin:
add_action('wp_footer', function () {
if (!is_page('new-bands-full-sign-up')) {
return;
}
?>
<style>
#mform_19 {
position: relative;
}
#mform_19 .mf-submit-overlay {
display: none;
position: absolute;
inset: 0;
z-index: 9999;
background: rgba(255, 255, 255, 0.92);
align-items: center;
justify-content: center;
padding: 20px;
text-align: center;
}
#mform_19 .mf-submit-overlay.is-visible {
display: flex;
}
#mform_19 .mf-submit-overlay__box {
max-width: 520px;
padding: 24px 28px;
background: #fff;
border: 1px solid #d9d9d9;
border-radius: 8px;
box-shadow: 0 12px 30px rgba(0, 0, 0, 0.12);
}
#mform_19 .mf-submit-overlay__title {
margin: 0 0 10px;
font-size: 20px;
font-weight: 700;
color: #222;
}
#mform_19 .mf-submit-overlay__text {
margin: 0;
font-size: 15px;
line-height: 1.6;
color: #444;
}
</style>
<script>
document.addEventListener('DOMContentLoaded', function () {
var wrapper = document.getElementById('mform_19');
var form = document.getElementById('mega-form-19');
if (!wrapper || !form) {
return;
}
var overlay = document.createElement('div');
overlay.className = 'mf-submit-overlay';
overlay.innerHTML =
'<div class="mf-submit-overlay__box">' +
'<h3 class="mf-submit-overlay__title">Application submitted</h3>' +
'<p class="mf-submit-overlay__text">Please wait up to 1 minute while your files finish uploading and processing. Do not close this window.</p>' +
'</div>';
wrapper.appendChild(overlay);
function isFinalSubmitProcessing() {
var submitButton = form.querySelector('[name="mform_submit"]');
return !!(
submitButton &&
submitButton.classList.contains('mf-submit-processing') &&
form.classList.contains('mf-mask')
);
}
function syncOverlay() {
overlay.classList.toggle('is-visible', isFinalSubmitProcessing());
}
var observer = new MutationObserver(syncOverlay);
observer.observe(form, {
attributes: true,
subtree: true,
attributeFilter: ['class']
});
syncOverlay();
});
</script>
<?php
});Thanks, I checked and there was a mismatch between the server limits and form limits, I fixed that, so you don’t to use the snippet now for version 1.7.3
This fix was for the characters limit, for the upload size limit, can you share the code you’re using? because it’s not clear what the problem is.
- This reply was modified 1 month, 3 weeks ago by Ali Khallad.
This is a bug, I just fixed it in version 1.7.2 and released an update.
There is a details button on the right side that show you the details from each log item.
Also, debug.log from /wp-content folder might be useful if you’ve already enabled WP_DEBUG and WP_DEBUG_LOG
Good to know you got it sorted.
Feel free to share the details if someone else got into the same problem.
The logs aren’t exportable from the plugin side. You’d probably need to copy them manually.
You can send me via email.
Hello, just checking, has this been solved for you?
AJAX is optional, you can keep it disabled, but if you want to know the root cause, you may enable it and try to replicate the issue, then send me the logs here.
I wouldn’t be able to know what’s happening with those images without logs.