Change to behaviour when creating new bodycopy divs

(Peter Sheppard) #1

I'm sure my mind isn't playing up, and my colleagues agree with me.

  1. Create a page
  2. Make it live
  3. Create a new div from the edit interface for that page



    We are absolutely certain the new div was created with the status of under construction, regardless of the parent page status, allowing you to populate it with content separately and then make it live at a future date.



    However, I've just tested and in both 3.24.1 and 4.6.2, when you create a div on a page, it always inherits that page's status.



    Furthermore, div status cannot be changed independantly of the parent page apart from to make a div live when the parent is under construction (useless), or to put one div alone into safe edit.



    Does anyone know when this behaviour changed, and why?
(Ashish Karelia) #2

[quote]
I'm sure my mind isn't playing up, and my colleagues agree with me.


  1. Create a page
  2. Make it live
  3. Create a new div from the edit interface for that page



    We are absolutely certain the new div was created with the status of under construction, regardless of the parent page status, allowing you to populate it with content separately and then make it live at a future date.



    However, I've just tested and in both 3.24.1 and 4.6.2, when you create a div on a page, it always inherits that page's status.



    Furthermore, div status cannot be changed independantly of the parent page apart from to make a div live when the parent is under construction (useless), or to put one div alone into safe edit.



    Does anyone know when this behaviour changed, and why?

    [/quote]



    Hi Peter,

    If you have workflow applied to the Parent asset (say standard page) and you create a new Div then the newly created Div is in Under construction status. But if no workflow is found while creating the new div, the status is inherited from Parent asset here. This is true only if the newly created asset is dependant asset, which in our case is TRUE.



    Hope this helps.



    Ash
(Peter Sheppard) #3

That explains it then - many thanks.


We use workflow extensively (99% of page content), but the test area we have set aside doesn't have workflow, and neither did the section I've been struggling with all day! Now to build applying then removing workflow into the import script I was testing.

(Ashish Karelia) #4

[quote]
That explains it then - many thanks.



We use workflow extensively (99% of page content), but the test area we have set aside doesn't have workflow, and neither did the section I've been struggling with all day! Now to build applying then removing workflow into the import script I was testing.

[/quote]



You are welcome. Glad to help :slight_smile:



Ash