Markdown Nested List tabs are off - list

I have a nested list in Markdown (on readme.io) that is coded as such:
1. Select **New Email** from the top right of the **Suggested Post** window.
- **Add A Photo**
- **Insert Showcase Link**: Adds a link as a central focus of the email by including an image, header, brief description and URL of the link.
*If the recipient clicks the showcase link **or any link** within the email, the action will be tracked and analytic data collected. This information can be viewed within the **Performance** section.*
- **Insert Variable**: Include a variable within the body or subject of your message. Click within the body or subject line areas then select **Insert Variable** where the variable should appear in the message. Variable information can be either **Contact** or **Agent** information. Users can select from **First Name**, **Last Name**, and **Email**.
- **Modification Rule**: A rule specifying how a post can be modified can be selected by choosing optional, prohibited or required.
* **Optional**: The text can be modified.
* **Prohibited**: The text cannot be modified. **Note**: Only email content set to **Prohibited** will appear in the Hearsay Mobile Application within the **Outreach** tab under **Email Templates**.
* **Required**: The post will have sections enclosed in brackets that require the user to edit prior to being published.
And renders fine:
Select New Email from the top right of the Suggested Post window.
Add A Photo
Insert Showcase Link: Adds a link as a central focus of the email by including an image, header, brief description and URL of the link.
If the recipient clicks the showcase link or any link within the email, the action will be tracked and analytic data collected. This information can be viewed within the Performance section.
Insert Variable: Include a variable within the body or subject of your message. Click within the body or subject line areas then select Insert Variable where the variable should appear in the message. Variable information can be either Contact or Agent information. Users can select from First Name, Last Name, and Email.
Modification Rule: A rule specifying how a post can be modified can be selected by choosing optional, prohibited or required.
Optional: The text can be modified.
Prohibited: The text cannot be modified. Note: Only email content set to Prohibited will appear in the Hearsay Mobile Application within the Outreach tab under Email Templates.
Required: The post will have sections enclosed in brackets that require the user to edit prior to being published.
However, if I add another top level bullet, the Modification Rule bullets tabs its content to be even with its sublist.
How can I correct this?
Thanks

Related

How create a template for a blank page with header, footer and classic reports?

I am using Oracle APEX 21.1. I am developing an app for clinic management. There is a page that should hold the patient's prescription and other data and a header - data displayed on every page at the top and a footer - data displayed at the bottom of every page. All regions in the page are based on classic reports. The page should be printed using Ctrl+p browser command.
I need to create a blank page that has nothing but the classic reports regions. And I need those regions to be displayed each as per to their template. I tried modifying the Standard page template by removing many <div> elements and classes but the result is not good at all.
Sometimes, the browser displays two pages to print when there is only one. Other times, the classic reports are not displayed correctly. Is there a way to create such a template that has nothing but a header, a footer and classic reports that retain their styling?
ws= eslam_ws
un= forhelp
pwd= Forhelppwd$
You don't need to modify the page template to accomplish this.
1 - Create a blank page. Go to properties. Set template to "Minimal (no navigation)".
2 - Create 3 regions:
Call the first "Header" go to properties set position to "Breadcrumb Bar".
Call the second "Body" go to properties set position to "Body"
Call the third "Footer" go to properties set position to "Footer".
Done. You can put inside these regions whatever you want.

Kentico - Editable WebPartZones on children pages?

I added a WebPartZone in the master page at the top pf the master page, this web part zone is a message bar that will display on all the pages but could be different on each page. Is it possible to have a web part zone in the template that is editable on each page? Or is a different way to do it?
Thanks
The short answer no. From the template engine prospective whatever editable in the master - is not editable in its children. All editable web parts/widgets editable on the master, are not editable in its children.
If you really want to have an editable text in the master and all its children, you probably need to clone and customize web part and form control it is based on. Or create you own web part.
P.S. You can have editable text in your page template so all page that use this template will have this editable text working.
If you can give more details on what kind thing you want to edit would be easier to provide an answer
P.P.S. You can have a work around but it will not be with editable text. You will have to edit message text at the form tab. Would that suits you?
You can add the webpart on your master, and use a macro to get the content, like {%CurrentDocument.GetValue("Message")%}, but you have to add a field to each page to store the message in.
Just throwing out one more option, if what you want to display changes from page type to page type, you can put a repeater on the master page, put a path of a period (current document), then use macros to set the page type to the current document class name and the transformation to currentdocument.classname+".mastermessage"
Using a macro, then add a transformation "mastermessage" to each page type it will encounter, then you can change the fields and format for each page type.

Cannot get Read Only Condition to work on Oracle Apex page

Trying to add a read condition to my page. Nothing I am doing works. I would like to use the PL/SQL Expression condition type but cannot get it to evaluate properly. My app is a workflow application and I want the page to display in READ mode when the status is not DRAFT. So, naturally I try to code the Expression as:
:P2_PDD_STATUS_CD != 'DRAFT'
This results in the page being opened in edit mode no matter what the status value. What am I missing? I've verified the column name several times. As a matter of testing, I was not able to get the Expression 1 = Expression 2 condition type to work either.
Getting APEX Page Item Conditional Properties to Work as Designed:
The Quick Answer: Wherever you place the page item that influences the READ-ONLY state of the text field page/region item, the change in its value/state has to happen sequentially before the event that fetches and displays the conditionally read-only text field...
The best way to make sure the state you have changed "sticks" is to associate a page redirect with that field so that the rest of the page items and dependent properties has an opportunity to recognize that the read-only page indicator value has been altered (from DRAFT to non-DRAFT, etc.)
The Test Data Schema: Speech Writer's Block App
This example uses a single table. The text-document is an oversized VARCHAR2 typed field, though it really could be anything... even a LOB/CLOB typed value for larger capacity. The schema:
The PAGE Design and Layout
The example is designed in a single page. Two regions: The speech catalog (top) and the speech editor form (bottom) are processed in the following order:
Query the speech catalog for the report display (fetch)
If a SPEECH_ID value was designated at page-load (or reload) fetch all fields for the speech document record where the speech id = the page item containing the speech id value.
If a SPEECH_Id was recently chosen (after the page is rendered), then redirect the page to itself setting page item SPEECH ID = selected speech id #.
The FORM Region Design
This defines what the "edit" button does from the report output of possible speech selections. Notice that selecting this button value sets an automatic redirect to the same page, containing the revised STATUS-MODEvalue.
Rendering Sequence Design
The rendering of the page passes through each region and design block once. If a item value is upstream (i.e., processed before) from a defining item value (such as the STATUS: DRAFT, ARCHIVE, etc.)... or it can be changed after the page render is completed, a redirect action would help in this case.
The Conditional READ-ONLY Page ITEM Property
Output and Results
Normal Speech Edit (DRAFT) Mode
Archive Mode for READ ONLY Speech Text Access
Discussion of Alternative Designs
It is possible to do this with a workflow that spans multiple pages. It might even be easier that way. For example, the determining, incoming page item properties should be set at ANY time prior to when the previous page is redirected to it.
Additional Comments (aside)
Sorry in advance for the slightly abnoxious-sized watermark-credits text on my screen-captures. I'm set up with a new tool (Skitch) and it is nearly impossible to get a sense of scale when it's finally home within a Stack Overflow post...
Enjoy anyways: Onward!

Why aren't my Content Items accepting their new Workflow?

All of my Content Items in one node have a bad reference to a workflow. I am trying to create one to replace the missing Workflow. I did these steps:
Created a new workflow
Located the common inherited template that all content items in this node use.
In the standard values I chose my new workflow for the "Workflow" and "Default Workflow" fields (I think I just need default, but I am not sure.)
Saved and Smart Published.
The content items still show the GUID for the missing Workflow. I click the template name at the top of the content item, double check the standard values on the template and everything looks great.
How do I force Content Items to retrieve the correct workflow from their Templates?
It looks like your content items have broken from their standard values which is why your new standard value WF is not getting set. What version of Sitecore are you using? You can use the reset button on each content item to bring it back to the standard value just for the workflow.
Go to the View ribbon and enable Standard Fields
For each content item that has the wrong workflow, go to the Versions ribbon and click the Reset button on the left
In the pop-up scroll all the way down to the bottom Workflow section and check the boxes to reset specific fields
Repeat this process for all of the content items
Another idea is to write code to programatically reset fields or set them to a new WF

How do you post content to a specific template position?

I purchased a template / theme from RocketTheme, but I can't figure out how to add content at a specific position.
The templates have "module positions" that collapse. I'd like to add some content at one of the module positions.
If I add articles, they seem to go into "mainbody". But I'd like to have content in other areas of the template.
How do I take some text, images, or other content, and get them to display in these other positions (i.e., TOP-A, or FEATURE-A, etc)?
I've tried this
Go to Extensions->Module Manager
Select "New", Select "Sections"
Under "Details", I select Position->Top-A
I give it a title.
Nothing seems to happen. I don't see anything new exposed in the admin UI, and I don't see a way to get any content into this newly defined section. What am I not understanding?
go to JED and look up html in module or content in module or content in component there are a bunch of them. http://extensions.joomla.org/search?q=module+content&start=20
Essentially
you create and save an article. Make sure it is saved to a section or category on your menu
open the module one of the paramaters will ask for the article id...decide which position and which pages you want it on and then publish.
You can also get modules that will take some or all of your articles in a category and then show them either as a slidedhow or one randomly when someone visits the page