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: Save As Button Not Displaying in IE

Status Resolved
Add-on / Version Publisher Lite 2.7.11
Severity
EE Version 4.2.3

James Carter

May 21, 2018

The “Save As” button is not displaying in IE. I get a couple of errors in the console but these don’t look like they have anything to do with Publisher (see attached). The button is appearing in Chrome, Edge, Firefox, and Safari. I didn’t see anyone else reporting this but I apologize if I missed it.

 

#1

BoldMinded (Brian)

Do you see those console errors in the other browsers? If not they could very well be stopping Publisher’s JavaScript from rendering correctly. JS errors at the top of the chain can stop additional scripts from running. If those errors aren’t happening in other browsers, then I’d lean towards them possibly causing this error. Have you tested in a channel that does not have a Fluid field? Looks like at least 1 of those errors is coming from Fluid code.

#2

Megan Miriello

No, I do not see the same errors in the console in other browsers. I don’t have any fluid fields on the website. I just recently upgraded from EE3.

#3

Megan Miriello

Is there any update on this?

#4

BoldMinded (Brian)

Nope, it’ll probably be a few weeks before I can look into this… I currently have no setup to even test IE.

#5

BoldMinded (Brian)

Can you click the blue link in those errors so it shows what file and line of code the error is occurring on? Its very possible this isn’t even a Publisher bug if JS elsewhere is throwing an error before Publisher’s code even runs.

#6

BoldMinded (Brian)

And when you say no “Save As” button isn’t showing, what is showing? Can you provide a screenshot?

#7

BoldMinded (Brian)

Also, the word “Set” and “namespace” do not appear anywhere in Publisher’s JS code, so I’m 99.99% sure this is not a Publisher bug.

#8

BoldMinded (Brian)

Based on the screenshots you emailed, I’m 100% sure this isn’t a Publisher bug. Those errors you’re seeing are preventing the rest of the JS on the page from running, which is Publisher’s code to put the buttons on the page. If you look in the Publisher tab, you’ll see those buttons. Publisher’s JS moves them from the tab to above the form, but its unable to b/c the other JS is causing problems.

#9

Megan Miriello

Good to know. Thank you!

Login to reply