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: Delete draft of an entry which doesn’t have published version get “You are not authorized to access

Status	Resolved
Add-on / Version	Publisher 1.6.1
Severity
EE Version	2.8.1

hung

Mar 12, 2015

Hi Publisher,

Please help me to resolve above issue. Also, my ticket http://boldminded.com/support/ticket/1028 was marked as resolved. So can you send us the latest source code that already fixed issue?

BoldMinded (Brian)

You can download 1.6.2 from Devot:ee now to get the latest version.

I’ll look into the draft deletion issue and see if I can replicate it.

hung

Ok, i can download latest version now. Please help us to resolve issue when deleting draft version of one entry which doesn’t have published version

hung

Hi Publisher,

I also face an other issue: 1. When i tried to save an entry of channel a i got “null” string in preview as attachment a.png 1. When i tried to save an entry of channel b i got correct menus in preview as attachment b.png

BoldMinded (Brian)

Looks like you have channel a setup to redirect to the structure page after saving it. Change it to redirect to the entry preview page instead (or remove the structure redirect option). The null is a side effect of this, I’ll try to fix this when I find time, its a very minor issue.

BoldMinded (Brian)

The null text issue will be fixed in the next release.

hung

Hi Publisher,

“Looks like you have channel a setup to redirect to the structure page after saving it. Change it to redirect to the entry preview page instead (or remove the structure redirect option). The null is a side effect of this, I’ll try to fix this when I find time, its a very minor issue.”

Question: each page has its own template then we can’t set preivew template same for all entry. How to remove the structure redirect option? It’s great if you give me video or image to guide.

hung

Hi Publisher,

We also faced a serious trouble when installed your module, after installed, our channel “pages” can’t view existing field “page content” with field type is “Content Elements”.

I am feeling that your plugin causes many trouble to my site. Please fix all my issues asap.

BoldMinded (Brian)

I will email you a new build to fix the structure issue.

As for the content elements issue you are going to need to provide a lot more information and detail about what is not working. “Please fix all my issues asap” is not a kid bug report. I have other customers using content elements without issue, so I need screenshots and a detailed explanation of what is not working. Did you upgrade to the latest version of content elements?

hung

Hi Publisher,

I am using content elements version 1.6.10

I also attached 3 images before install, after install and channel field “page content”. Please feel free to determine what’s wrong. This is urgent for us because our client is concern with us about those issues.

#10

hung

Hi Publisher,

I have detected new bug on the latest plugin you send to me thru email, please check issue preview in image “preview bug”

#11

hung

After click save, it preview in very small screen, also i can’t close the overlay.

#12

BoldMinded (Brian)

Hung, I’m unable to replicate your CE issue. I uninstalled Publisher, created an entry with a CE field, created 3 CE blocks of content. Then installed Publisher and the 3 CE blocks of content are still present in both languages. I edited the content in my second language, German, and the content saved properly. As far as I can tell, everything is working fine with CE.

Can you record a screen capture of what you are seeing, starting at step 1 and recording everything necessary to replicate the issue.

#13

BoldMinded (Brian)

I will look into the preview bug when I get a chance, could be a couple of days.

#14

BoldMinded (Brian)

Hung, it looks like you may not have updated the themes folder or may need to refresh your cache.

#15

hung

Yeah, you right. I have not update themes folder. Issue with preview has been resolved. So now just only issue with hidden value of existing field “Page content”.

#16

Paul Cripps

Sounds like we might be having the same publisher / CE issues.

Is the patch for the above thread in release 1.6.2 - I’ll test that and see how we get on.

#17

hung

Yes, it’s 1.6.2

#18

BoldMinded (Brian)

Are either one of you able to take a video of the issue you are seeing from beginning to end so I can see what exactly is happening?

#19

hung

Hi Publisher,

For issue with hidden value of existing field “Page content” please see this video https://docs.google.com/file/d/0B84pT0oJDYmEVDhLZXlPbVMxY2M/edit?usp=drivesdk
For delete draft version of an entry which doesn’t have published already please see video https://docs.google.com/file/d/0B84pT0oJDYmEcldUc2RTakdhRGs/edit?usp=drivesdk

#20

BoldMinded (Brian)

Hung, thanks for the videos. I’m still unable to replicate #1. I just un-installed and re-installed 3 times and the CE field data shows as it should after installing it. Can you repeat your process and immediately after install take a look at your exp_publisher_data table for the entry_id of the entry you saved, and see if the row exists for the entry, and if it does see if the CE field has data. The contents of the column will look something like this

a:3:{s:16:"3ZTXMcn3pPhOEK2H";a:3:{s:12:"element_type";s:8:"

I emailed a build to fix the redirect issue when deleting a draft. See if that version fixes the CE field on install too… there was a flaw in the install process.

p.s., next time you record a screen capture like that, turn off your background sound or disable sound recording 😉

#21

hung

Hi Publisher,

The latest version you sent to me, after installed, i got blank screen, can’t access CMS any more. Please double check.

#22

hung

Hi Publisher,

You can try to login to http://icebergs.projectuat.com/cms.php?/cp/login to see issue with “Content element”, i can’t detect what’s wrong. If you need i will sharing source code to you can preview.

#23

BoldMinded (Brian)

Hung, I have another customer who is having the same problem, and they received this email from the Content Element’s developer:

“it seems to by really problem on our site. i create new issue for this. Now we must schedule some time for fix this. Thanks for reporting.”

I did some investigating on my side and based on what I found I have to agree this is most likely a problem with Content Elements, not Publisher.

The issue appears to be that the content from the Rich Text field is not properly decoded by CE, so when it attempts to unserialize the data it fails and thus the field does not render.

#24

BoldMinded (Brian)

I’m going to close this ticket now b/c its a CE issue. You can use their support from here on out.

http://www.krea.com/content-elements/support

#25

hung

Hi Brian,

Can you more clear? Because it only occur after i installed your module, it means that it still can unserialize before.

#26

Brian Litzinger

Hung, the data saved by CE in the native EE tables is exactly the same as what is saved in the Publisher table, so Publisher is returning the same data… it is just a pass through. Publisher does not modify the CE data at all. I don’t know why it happens when Publisher is enabled, but I did some testing myself and could replicate it, but also could not find anything in Publisher’s code that caused the problem. I’m pretty sure the problem is deeper inside of CE, or the Rich Text field.

#27

BoldMinded (Brian)

Comment has been marked private.