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: Drafts not saving, Published version losing data

Status Resolved
Add-on / Version Publisher 2.7.10
Severity
EE Version 3.5.2

Paul Larson

May 03, 2018

Description:

Client makes edits to page, upon saving, ‘Published’ version loses most/all content. Draft retains the content we need, but we can’t save that content as the Published versions

Detailed steps to reproduce the issue:
1. Open problem page in admin
2. Make trivial edit, while viewing draft.
3. Save as published

 

#1

Paul Larson

Comment has been marked private.

#2

Paul Larson

“Check the exp_publisher_titles/data tables to make sure there is 1 row for open and 1 row for draft in each table for that entry”

exp_publisher_titles and exp_publisher_data currently both have 443 rows

For that entry id, 64, both Open/Draft rows exist.

#3

Paul Larson

Compare to production:

https://www.dropbox.com/s/xx6oop9s17vageq/Screenshot 2018-05-03 16.08.29.png?dl=0

https://www.dropbox.com/s/l2e5g8c7rfe2awm/Screenshot 2018-05-03 16.09.36.png?dl=0

#4

Paul Larson

Most entries do not have both an Open and Draft row.

https://www.dropbox.com/s/flsqnesehykcy9s/2018-05-03_16-12-32.png?dl=0

#5

BoldMinded (Brian)

FTP didn’t work. Possibly using something other than port 21?

#6

BoldMinded (Brian)

Ok, I think I know what is happening. The “View As” option should not be displaying if the entry does not have a draft. So in those cases, those entries only have an open version, but its letting you switch to view the draft, which doesn’t exist, but its displaying the content in the CP b/c its designed to display the open content if nothing is found. When you save it from this state, Grid, Bloqs etc are getting confused b/c it thinks its supposed to be doing something with the existing draft content in the database, but there is none, so it wipes out the existing content that it does have.

I think to “fix” the issue until I get a proper code fix in, is that you need to first save an entry as a draft, then edit the draft. If the open version is the only version there, then switching to draft and then saving as published is what I think is jacking it all up. If you’re editing an open/published entry, and it detects a newer draft, it’ll tell you so. Until you see that, there isn’t really a reason to switch the view state to draft, b/c the open and draft versions are the same at that point.

https://www.dropbox.com/s/aaz2y4vq0hetsq2/Screenshot 2018-05-04 05.52.46.png?dl=0

#7

Paul Larson

Comment has been marked private.

#8

BoldMinded (Brian)

Comment has been marked private.

#9

BoldMinded (Brian)

Comment has been marked private.

#10

BoldMinded (Brian)

Closing this ticket b/c the issue is fixed in 2.7.11

Login to reply