A mainpage in our confluence space consists of a comala workflow ("approve file"). This workflow will change the mainpage's status to "draft" if a change to the main page is saved.
Additionally to this (main) page there are several subpages. I was now asked to modify the workflow ("approve file") so when a change on a subpage is saved, the status of the main page needs to be set to "draft" as well.
So, I need to figure out how a change to a subpage can trigger the workflow of the mainpage, any ideas?
Related
I am trying to set a trigger that would be fired if users visit both page 1 and page 2 on a website. No matter which page they visit first, as long they visit both pages.
Example: Homepage URL: shop.orgalife.com
Page 1: shop.orgalife.com/collections/page_1
Page 2: shop.orgalife.com/collections/page_2
However, I tried to use trigger type "trigger group" with 2 child trigger page URL contain specific page_1 and page_2 (they are both on page URL) and it does not work.
Is there any way to configure a trigger that would fire successfully?
Thank you all
What is the best trigger type when we want to have more than 2 conditions (I watched many tests for scroll and timer at the same time and It always easily works but don't know why click event or page view event never work)
I would suggest you can set an item in localstorage when user visit page1.
Then when user goes to page2. Check the localStorage is exist or not. If yes then fire your code.
You can check the Referrer in the page2. If the Referrer is page1 and it can fire the tag you want.
I am new to TYPO3 and have a big problem. I deleted the page with the id 1 (startpage, I know its stupid) and now I woudl like to know if it is possible to restore the page somehow.
Install extension Recycler, it ships with TYPO3 by default. You can then restore pages and content you deleted using the backend UI it has.
https://docs.typo3.org/typo3cms/extensions/recycler/Introduction/Index.html
You can use the recycler that is found under the web module and click on a page in the page tree at a higher level than the deleted page. You can also set the depth to infinitive if not certain where the page used to be in the page tree. Then put a tick beside the page you want to restore and click undelete. Note that PID is 'Parent ID' (not Page ID), and UID is the ID of the deleted page.If you click on the little + you will get additional information, e.g. the original path to the deleted page. If part of the path is highlighted in red, then that indicates another deleted branch or page. Remember to leave the Recycler module with 'Depth' NOT set to 'Infinite' (leave it at 'This page' or '1-4 levels') otherwise the recycler will hang if you use it on a larger part of your page t ree. Hope this will help you.
I am a beginner at CQ5. I created a simple workflow with 2 paths - accept and reject. I created a page and set its vanity url the same as the original page url and checked the "Redirect Vanity url" text box. Next I pushed the page down the workflow. But then when I opened up the page in the browser and clicked on the workflow tab of the sidekick, it was completely blank. Removing the vanity url brought back the workflow tab contents. Can someone explain to me why this happened so? This wasn't mapped in the ConfigMgr console.
I found that the vanity url actual does something like a "Redirect". So if we add a vanity url to a page which has the same url as the vanity url, the page goes into something like an infinite loop, redirecting to itself. This causes trouble in various sorts. In my case, it was affecting the workflow.
Jahia CMS:
We are keeping default pages in the template, and these pages are created when we create a website using the template.
Now go to edit mode of the site, and delete a page from the site, and publish it.
Change something in template and deploy the new template again.
You will see the deleted page has reappeared for the edit mode, not for the published mode. Published mode is untouched.
Is it an expected behavior?
Yes it is the expected behavior.
What you mention as published mode is called "live mode". Creation of content has to be published before being available in live mode.
Only change made in templates does not have to be published.
i have a master page and a child aspx page, coneected to each other. the master page has the form in it. Now the child page has checkboxes, whose value i would like to pass to another child page with same master page behind it.
Can i change the action=abc.aspx and method=post?
How can i send all the checkbox values (checkbox.text = abc#oke.com) to the next page?
there are lots of these values that need to pass to nex tpage.
Use Button.PostBackUrl to change the page which the button posts to, and then on the target page, use Page.PreviousPage to get a reference to the source page (and therefore its controls).
By default you can use Page.PreviousPage.FindControl(...) to find a control on the source page by ID, then cast it to a checkbox and retrieve its values. You can also specify the type of the previous page with a <%# PreviousPageType %> directive, and then access the previous page's public properties.
See Cross-Page Posting for details.