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: Ignored channel entries not updating
| Status | Resolved |
| Add-on / Version | Publisher Lite 1.0.12 |
| Severity | Critical |
| EE Version | 2.5.5 |
Nick Lane
Oct 29, 2013Hi,
We have an ignored channel (staff) that will not update on the site. Upon saving the entry, all runs as expected with no presence of Publisher. In addition, the data is saved correctly in exp_channel_data and exp_channel_titles. However, the page (which is controlled by publisher) where this listing of staff is applied (via playa) never updates. I’ve found an entry for the staff entry ID in exp_publisher_data and it has an old, un-updated version of the staff’s entry data found. I’m not sure why this would be saved here, nor why it never updates.
I can’t recall if this staff channel may have at some point in the install process been active with publisher in the past; but I can confirm it is part of the “ignored channel” listing now. It was our understanding that ignored channels will have no presence in Publisher whatsoever? Does Publisher remove this data if a channel is ignored?
Any suggestions would be appreciated.
Thanks!
Brian Litzinger
Hi, Nick. Publisher won’t remove the data or retroactively remove data. Ignored means it just saves the published/default language version of the entry to the exp_channel_data and exp_channel_titles tables, and uses that data on the front-end at all times.
Nick Lane
I see. Makes sense.
Right now, my staff channel is set as “ignored”, but our page will only display the data for these entries found in exp_publisher_data. Shouldn’t it be ignoring this table altogether until I would re-active the channel for publisher? At least that’s how I’m understanding your note.
BoldMinded (Brian)
It’ll still save data to exp_publisher_data even if its ignored. EE wants to put whatever is in the publish form in to exp_channel_* tables, so if you save a Spanish entry it’ll actually have Spanish content in EE’s main tables for a split second, then at the very end of the save process Publisher takes the published/default language value for that field and puts it back into the exo_channel_* tables.
One way to test if there is actually an issue is to modify some field contents directly in the database. Change a value or two in exp_publisher_* tables and see if that is what displays on the front-end instead of what is in the exp_channel_* tables. If it isn’t showing the correct data I can take another look into the code to see if this might be a bug.
Nick Lane
To get their entry update live, I actually did just that, I updated the entry fields in exp_publisher_data and it worked. This again for an entry in a channel that is currently marked as ignored. I wonder if because the entry is tied to a page (which does use publisher) using playa in order to be displayed in a list, is where the issue is. I did check the array for publisher’s ignored settings in the database, and this staff channel (5) is listed accurately. Hmm…
For this site, we have no translations. It’s just the pages module for a channel, along with two additional channels tied to publisher. The rest of the channels are ignored at the moment. The ignored channels are where our issues are being found.
BoldMinded (Brian)
So the correct content is showing unless its a Playa relationship?
Nick Lane
As of now, the only way to get the correct content showing is to manually update the database row in exp_publisher_data.
Upon further testing, for ignored channels, with and without a playa field, content is not updating. Content is saving just fine to exp_channel_data, but the only data being displayed is what’s found in the exp_publisher_data table. Since the channel is ignored, I believe your table doesn’t update with the entry save, but EE is still pulling data for this channel query from your table, as oppose to its own.
BoldMinded (Brian)
Ok. I’ll definitely give this another look this weekend. Thanks for the details, it’ll help.
BoldMinded (Brian)
Nick, do you have an email other than the .me account? It won’t let me send a zip file.
BoldMinded (Brian)
Also, it looks like you are using EE 2.5.5. Publisher isn’t supported in that version any more, but I do have an environment and everything seems to be working fine if you are not using the old relationships field.
Nick Lane
I recall we had this issue before with sending files. I think you sent a temporary dropbox link instead?
Correct, 2.5.5. And no, we are not using the old relationships field. Only Playa exclusively. We do have the latest version of this installed.
Nick Lane
Hi Brian,
I was just checking if you’ve tried sending a dropbox link. I hadn’t received anything yet. Just confirming.
BoldMinded (Brian)
Sent
BoldMinded (Brian)
Nick, did the new build fix this issue?
Nick Lane
Yes it did, thank you! We’ve installed and all seems well so far. What ended up being the issue?
BoldMinded (Brian)
It was actually improvements in a few places, hard to concisely recap 😊