Publisher does not support the Fluid field type. Please do not contact asking when support will be available.

If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: Removing form submit button

Status Resolved
Add-on / Version Publisher 1.0.13
Severity Blocker
EE Version 2.5.5

submodal

Oct 25, 2013

When editing an entry containing a submit button in a Wygwam field, Publisher removes the button and places it below the text area (see attached).  It is possible to view source and paste the button however each time the entry is edited the button is removed again.

We’ve tested Wygwam with EE 2.5.5 and there’s no issue.  After re-enabling Publisher, the issue returns.

#1

BoldMinded (Brian)

I can see why it would do that and look into a solution. I guess my question is why put a submit button into a wysiwyg field?

#2

submodal

Submit button is for a 3rd party form. Unfortunately this issue also occurs with plain text areas as well - see 2nd screenshot.

#3

BoldMinded (Brian)

I’ll look into a fix soon, but in general I’d recommend not putting forms into a wysiwyg field. It is especially susceptible to the client messing it up. Have you considered embedding a pre-configured template?

http://devot-ee.com/add-ons/template-snippet-select

#4

BoldMinded (Brian)

Does your form submit button have the id of “submit_button”?

#5

submodal

No, it doesn’t.

<button name="submit_form" class="button-blue active">Submit</button>
#6

BoldMinded (Brian)

Are you positive disabling Publisher makes it work? I was thinking more about this last night and realized that CKEditor puts its contents into an iframe, which Publisher’s scripts don’t have access too, so I’m confused at how this could be happening.

#7

submodal

Yes, this has always worked in EE with WYGWAM / CKE and we did actually test it.

Here’s a screenshot with Publisher disabled. https://s3.amazonaws.com/uploads.hipchat.com/54100/370190/JSKiq4iybi2QiuB/screen3.jpg

#8

BoldMinded (Brian)

Would you be able to provide FTP and CP access? I can’t replicate this locally in 2 different environments :/

#9

submodal

Resolved this issue. Appears to have been a combination of Publisher and CKE. Upgrading WYGWAM/CKE fixed the issue.

#10

submodal

Please disregard #9. Publisher was disabled on our dev site which did resolve the issue. Issue returned on production and now we can confirm that it is related to Publisher and not Wygwam / CKE.

#11

Brian Litzinger

Any chance of getting CP and FTP access so I can take a closer look?

#12

submodal

Unfortunately there’s VPN in place so FTP access won’t be possible. CP may be possible but we’ll need to get permission from the client or we may be able to setup a new dev site. I’ll follow up shortly.

#13

Brian Litzinger

Can you package up the site with a db dump and share it via Dropbox?

#14

BoldMinded (Brian)

Closing this ticket b/c support moved to email, but as mentioned in the email I’m not convinced this is a Publisher issue b/c using Wyvern (CKeditor) the buttons are fine.

Login to reply