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: Send for Approval not showing on all entries

Status Resolved
Add-on / Version Publisher Lite 2.11.1
Severity
EE Version 5.2.4

Brent Jones

Jul 03, 2019

We are trying to get a workflow in place for the site (https://ssl-dfa-site.ark.org/admin.php) and the user group permissions all appear to be correct. The users in this group see the submit for approval on some entries and then on others in the same channel, the submit for approval isn’t there. We have spent a lot of time troubleshooting on this end to no avail. Any suggestions would be appreciated.

#1

BoldMinded (Brian)

Hi, Brent. Few questions:

“user group permissions all appear to be correct” - Can you share some screenshots of the Publisher settings for the user groups you’re referring to?

“The users in this group see the submit for approval” - The users in what group??

“the submit for approval isn’t there” - Can you take screenshots of this please? The Submit for approval only works for user groups who are setup as Editors, and the entry should only be able to be saved as a Draft in this scenario.

I basically need more info from you before I can really help with this. The information you originally provided was not enough to understand your scenario. Pictures, video screengrabs etc help.

Also, I’m 99% confident this option is working as it is supposed to, and there is just a misconfiguration in Publisher’s settings somewhere.

#2

Brent Jones

Comment has been marked private.

#3

BoldMinded (Brian)

This to me sounds a bit like another add-on or something is causing a JS error, which is preventing Publisher’s JS from executing. Have you tried to replicate this issue in a new EE environment with only Publisher installed? As for that error message, you’d have to inspect that response to find out what the .match() method is being called on that is apparently null or undefined. The error message as you posted it doesn’t tell me what might be causing the problem. You can also try to backup your db, and uninstall every add-on except Publisher to see if the error is still happening. If the error goes away, then it pretty much means another add-on is conflicting in some way, or it is breaking, and causing Publisher’s JS not to execute like I previously mentioned.

#4

BoldMinded (Brian)

Following up on this b/c I haven’t heard anything back in 2+ weeks.

#5

BoldMinded (Brian)

Closing this due to inactivity.

Login to reply