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: Assets in Matrix in Low Variables losing data

Status Resolved
Add-on / Version Publisher 1.2.2
Severity Critical
EE Version 2.7.2

BoldMinded

Mar 06, 2014

Hi Brian,

This is related to an earlier ticket of mine:

https://boldminded.com/support/ticket/752

At the end of that ticket I was saying that I was struggling to get an Asset to maintain content within an Matrix in a Low Variable. I thought things were OK, but we are still having trouble - and I hope that I can give you enough info to replicate on your end.

Setup:

2 languages (English and Portuguese)
English is default (ID 1)
Low Variable: Matrix
Matrix column: Asset

At this point, you should be adding Matrix rows containing Assets fields with ease; no problem.

Now, go over to Publisher > Languages, and set Portuguese to be the default language.

Now, return to Low Variables. You *should* now see the assets columns empty.  Now, if you were to visit the front-end, the Assets would still be coming through, but in the CP, they won’t appear.

I sure hope you’re able to replicate it on your end…

Cheers,
John

#1

BoldMinded (Brian)

That is a pretty big edge case you got there 😊 Why change the default language once content entry begins?

Also, as soon as I detect “var_id” in any of the Matrix, Assets, or Playa hook queries, I immediately return the same query without modifying it. Basically I’m just passing the queries that those add-ons hooks pass to Publisher right back to the add-on. I’m not sure what is going on, but the query is the same for both default and non-default languages.

#2

JohnDWells

Yeah I totally realise this is a PITA edge case… This all goes back to when I was using that “Force default language in the Control Panel” setting. I had it set to “Yes”, and handed the site build over to the client for content entry, but he wanted to start in Portuguese first. So rather than understanding what the default language was really doing and just setting it to “No”, I reversed the default language. If you look back in the support history I believe we discussed this…

I could change the default language back, I’m just nervous of making things doubly worse. But I’ll run tests and probably do so, it seems the most reliable option moving forward.

Thanks Brian.

#3

BoldMinded (Brian)

Closing this b/c I have not had similar reports. If I get another similar report I’ll dig into this further.

Login to reply