Making live new DIV containers in a Safe Edit asset

(Iestyn Polley) #1

Hi folks,

 

When an author (using Edit+) makes a live asset 'Safe edit' and then adds a new div container, the new container has an under construction status. When the author applies for approval and gets it, the rest of the asset becomes live, but the new container remains under construction.

 

Is there any way an Edit+ user can make this dependent asset live? (without using the admin interface)

 

 

Cheers,

Iestyn.

 

- Matrix 4.14.1, Edit+

(Robin Shi) #2

As I know a new div container can only be added while the page is under construction or live.

(Edison Wang) #3

When you create a new container, the new container should inherit the status of its parent page.

In your case, it should be safe edit as well.

 

So when you push status changes later, it can cascade down the status change without a problem.

 

I can't replicate it on latest Matrix using EES/Edit+ mode or admin mode. It just creates the new div in safe edit status.

So i assume it was a problem with old version of Matrix?

(Iestyn Polley) #4

Thanks for the reply Edison. We're running 4.14.1.

 

I've asked some more authors about this issue since I posted, and they report the correct behaviour you describe.

 

We are having some performance problems at the moment where some tasks time out - perhaps a time out can cause the status to not update correctly? 

 

Iestyn.

(Robin Shi) #5

http://forums.squizsuite.net/index.php?showtopic=3222&p=16117

http://forums.squizsuite.net/index.php?showtopic=4117&p=20046

 

I guess there might have been changed.

(Edison Wang) #6

http://forums.squizsuite.net/index.php?showtopic=3222&p=16117

http://forums.squizsuite.net/index.php?showtopic=4117&p=20046

 

I guess there might have been changed.

Yes. The behaviour has changed since 3.24. Matrix will now allow editor to create new DIVs for asset under Safe Edit.

The new DIVs created during Safe Edit will be removed if Safe Edit is canceled.

 

 

I checked the code around it. I can confirm that Matrix will set the status to Safe Edit for the new container created.

There is only slight difference if the asset has a schema applied or not. If a schema is applied, it will set Safe Edit by force later in the code( to bypass the workflow check).

If there is no schema, it will create the asset naturally in Safe Edit status by inheriting parent's status.

 

I don't think performance is a factor here, because the asset creation and set status is done in a single PHP process, even through Edit+.

So i have no clue here. Have you checked if there is any trigger action or so to interfere here?

(Iestyn Polley) #7

I can check - there are some triggers on our system for cache clearing. What sort of trigger action might cause interference?

 

Cheers and thanks,

Iestyn.

(Edison Wang) #8

i mean if there is any custom script/ trigger action that would set status to UC?

Can you check Matrix's system log? In system log, it logs the actions Matrix has done to that asset. See if you can find anything there.