How do I find how this link or button on the left side to delete it?
I used a code from Vertical Response, which is their email that they use.
Sue
Printable View
How do I find how this link or button on the left side to delete it?
I used a code from Vertical Response, which is their email that they use.
Sue
Got a link Sue, without it we're just guessing ;)
Old age, I'm afraid...and distractions!
Here you go..https://www.makom.org/join-email-list.htm
I don't see a Sign Up button at the left corner of the page. Here's a screen-grab from Firefox. The Sign-up button is where I'd expect it as it is in Chrome, Opera & Edge. (Don't understand the need for the field below the sign-up button though)
Also tested the form & it appears to work. However I'll decline to subscribe ;)
Egg, the button is in your screen shot! :( See yellow highlight. I don't know why it's there and where that came from...
Attachment 124701
Good to know it works...and it's fine you decline...thank you for testing it.
Sorry, missed that one. Without looking at your .web/.xar file I can't say exactly what the cause is but looking at your page source you have two:
scripts on your page ;)Quote:
<!-- Begin VR Signup Form --> .........................................
The second placeholder seems to be from the mobile variant. That is another problem but not responsible for the button appearing there.
The problem seems to be that the placeholder code has been messed up. Parts of it appear duplicated and there is an additional </div>, and I think the later is the main reason.
The other problem is that using the same placeholder on the mobile variant creates a duplicate ID, and that will cause problems.
I strongly recommend to create a separate form for the mobile variant and to repeat the process of adding the placeholders. If the code is still messy then you would need to contact the provider of that code.
Is there any code related to the form in the 'HTML Code (head)' under the 'Page' section in Web Properties?
No code in the head, that I can see.
That's interesting. Thanks for looking at it.
"The second placeholder seems to be from the mobile variant. That is another problem but not responsible for the button appearing there.
The problem seems to be that the placeholder code has been messed up. Parts of it appear duplicated and there is an additional </div>, and I think the later is the main reason.
The other problem is that using the same placeholder on the mobile variant creates a duplicate ID, and that will cause problems.
I strongly recommend to create a separate form for the mobile variant and to repeat the process of adding the placeholders. If the code is still messy then you would need to contact the provider of that code."
Egg, trying to attach the web file for you. Not sure if I am doing it right.
I removed the following from the form. It appears to work fine now.
Quote:
<input type="text" name="mobile_phone">
</div>
<div class="vr-submit">
<div class="vr-notice"></div>
<input type="submit" value="Sign Up">
</div>
at the bottom the duplicated lines
</form>
<link ... signup_forms.embedded-2.css">
<script ... signup_forms.embedded-2.js"></script>
<script type="text/javascript">...id: "19791209301703"...</script>
should also be removed.
And (quite surely) you still will have the problem of transferring data from the wrong form if you don't fix the duplicate ID issue.
I'm sorry, but I can't explain much better.
The problem is you duplicated the code which includes the ID of the form (see first line of the placeholder code, you will find something like ...id="vr-signup-form-19791209301710"... on both variants of the page). It is not allowed for two elements to share the exact same ID, and for a page with variants, all variants are published to the same htm file. This situation will probably result in whichever variants "sign up" button is clicked the data that is transferred will be taken from the first occurrance of the ID in the file. But there is no guarantee it will behave like that, maybe the code provided is smart enough to skip currently invisible forms, but I doubt that will be the case. At least go ahead and check what is transferred for each variants "sign up" button after setting different values to the form fields for both variants.