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: Pending approval deny flow

Status Resolved
Add-on / Version Publisher Lite 2.6.1
Severity
EE Version 3.5.3

Harold Kuiper

Jul 27, 2017

Hi Brian,

Couple of things.
When an Editor sends a draft for approval and it’s denied it remains in the Pending Approval list. This is confusing for the Publishers because other Publishers can still approve or also deny.
When a Publisher denies an approval and deletes the Draft the Entry is nicely deleted but remains in the Pending Approval list.
The return page states a json string when an approval is denied URL: ...com?ACT=41&site_id=1 and outputs {"success":true}

Best,
Martijn

 

#1

BoldMinded (Brian)

Martjin, I wasn’t able to replicate the json string in the page. I see it when the ajax request is made, which is expected, but thats it. Could you provide a quick video screencast of it happening for you?

#2

BoldMinded (Brian)

Comment has been marked private.

#3

Harold Kuiper

Comment has been marked private.

#4

Harold Kuiper

Comment has been marked private.

#5

BoldMinded (Brian)

What about that JSON you were seeing? Is it still happening? Are there any other JS errors in the console?

#6

BoldMinded (Brian)

Just watched the video. There has to be JS errors or something else where that is messing with the ajax request/response, b/c thats not what I see locally.

#7

Harold Kuiper

Hi Brian,

I don’t know if it’s a bug or not but this only happens when logged in as SuperAdmin. It’s working fine when logged in as Publisher. Sorry, I didn’t suspect there would be a difference between those and therefor didn’t test it as Publisher.

Best, Martijn

#8

BoldMinded (Brian)

I was logged in as a Super Admin locally too and it worked fine. Did you check your JavaScript console for errors?

#9

Harold Kuiper

No JS errors showed up. And as you mentioned it’s an Ajax request. I couldn’t find the JS to handle the request when logged in as SuperAdmin. It’s because the file “publisher.cp.js” is missing. But it’s present when logged in as Publisher.

#10

BoldMinded (Brian)

Oh wow. I just found the issue. That js file is only loaded when the Publisher custom menu is added to the page, which is member group specific. It should be loaded on every page… I’ll send a new build soon.

#11

BoldMinded (Brian)

Comment has been marked private.

#12

Harold Kuiper

Thanks for the quick fix. Cheers, Martijn

Login to reply