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: grid and maps fields are not saving / emptied on resave
| Status | Resolved |
| Add-on / Version | Publisher 2.10.7 |
| Severity | |
| EE Version | 5.1.3 |
Silo B.V.Silo
Feb 28, 2019
Hi!
I recently updated a website from EE2 to latest. Everything looks good, however some issues are popping up. Somehow they seem related to publisher
We had a playa field that was not behaving right. Checked the docs and saw it’s not supported. Fine. So I added a grid field to replace this field. However, when i’m populating the grid field, the data isn’t saved at all. When i open the entries (in either language) the grid field remains empty.
Then there’s a maps field (by reinos). When we add the desired location in an entry, it saves properly, and also on the frontend we see the desired outcome.
Now we want to add the location also to the other language version of the entry. there we see that the location is allready entered (however this might be fallback)
When we save and close the entry, and reopen it, the location field is empty in both language versions.
We are not seeing anything in the error logs of EE or the server, nothing in the console. error reporting is turned on
BoldMinded (Brian)
Regarding your first issue, if you ran the migration scripts Relationship and Grid fields should be working fine with Publisher. A lot of people have used them to migrate successfully.
As for Maps. It looks like Maps saves its data as a base64 encoded string, probably a JSON object or something, and it looks like it is saving the data correctly to Publisher’s data table. Since it is just a text field, then it should be working fine with Maps. If a basic custom text field works, then Maps should work with Publisher, otherwise every text field on your site would be exhibiting the same behavior.
Jelle / Karres en Brands
Hi! I just tested something. I changed the contents of a simple textarea. When i click save&close;, and reopen, my edits are not there. I have removed the matrix field, and entered a new grid field. But also there, no rows are saved So it seems as if all fields are exhibiting this.
Jelle / Karres en Brands
easiest way to see this behavior is to use the (only) entry in the contact channel
BoldMinded (Brian)
And by all fields you mean even a basic text field not inside of a Grid? If that is the case then something didn’t install correctly, or you have extensions globally disabled in your config file.
BoldMinded (Brian)
Comment has been marked private.
Jelle / Karres en Brands
Hi Brian,
Just updated publisher but doesn’t help. Changes are not saved in any field
Jelle / Karres en Brands
Comment has been marked private.
BoldMinded (Brian)
Did you try a clean install of EE with just Publisher to try to replicate it? Are you sure the channel you are testing isn’t ignored?
Jelle / Karres en Brands
Hi Brian, I didn’t replicate this with a clean install. this is a site that i’ve inherited and brought up to latets version from 2.x No channels are ignored however
BoldMinded (Brian)
The reason I ask for a clean install test is to verify if there is a widespread bug (which I don’t think is the case, otherwise I’d be hearing similar reports and be able to replicate it myself), or if it is isolated to your environment. I’d also recommend backing up your database, then un-installing each other add-on 1 by 1 until hopefully you see Publisher working correctly, then that may indicate if another add-on is conflicting with Publisher. If you upgraded from an EE 2 site, make sure there are not duplicate “publisher” folders in the add-ons directory, not even “publisher-backup” or something like that, b/c it can cause serious problems. The Composer error indicates to me that something is obviously not correct with the install… perhaps missing files or directories, or maybe old publisher folders.
BoldMinded (Brian)
Also, did you try creating a new channel with a new custom field to see if the issue still persists?
Jelle / Karres en Brands
Hi Brian,
It seems this bug is related to the settings. Seems like it’s ok now. i’ve disabled drafts and set view state & save status to open and looks as fif it works as it should now.
BoldMinded (Brian)
What were the settings before you changed them?