I need to add an extra field to a BizTalk service call.
I added the field as an element in the input and output schemas.
Then I was going to map the input and output in the mapper.
But I was faced with this:
The old fields show as linked and they are working. But there's no visible link. I would like to add the new field and map it the same way and not link it directly.
Anyone knows how this can be linked?
I searched for the old fields in the solution and I couldn't find anything that could explain this. I guess there must be some property I don't know about but I don't see anything either.
The link is done in another page. I forgot you can scroll through pages in biztalk mapper
is there way in orchard to intercommunicate between custom widget?
Scenario :-
Suppose :- We have one widget name teacher . which can add student name . on same page we have second widget name student . while teacher add new student name it will show in second widget (student) on same page . on second page we have also dragged student widget it should be also update with new value .i would not to store value in database . Please help me out .
Thanks in advance .
Orchard does not have anything specific to do this, but neither does it get in your way of doing it if you want to.
We have similar intra-communication in some of our widgets. We do it by adding a specific property to the widget (which can be changed by editing the widget) where we input the name of the widget to link to. In our case, the widgets we are using share a JSON object (the linked widget now knows the name of the widget it's linked to, so we can work out how to get the JSON object). We then use an observable style JS framework (I believe that our frontend devs are using marionette, but pick your flavour). If widget A or Widget B updates the JSON object, then the the html is automatically updated, due to how the JS framework works. This gives nice "interactive" widgets.
Alternatively - if you only care about the linking at the loading time, then both widgets should pull data from an interface implementing IDependency (e.g. IMyService) that is "per request", then you can easily share the data that way server side.
I'm guessing from your comments to Bertrand that you are looking for the first option I listed.
I'm sure you could take these concepts significantly further and get to SharePoints "linked parts" framework where as long as you link an output / input of the same data type it allows the linking, but that would be rather harder to complete.
Is there any option to completely control a Search module with a Summary view? I am struggling to get there. I have the following settings so far:
In admin I created an Index called PublicSearch with a number of fields.
I am getting a search result which is a mixture of two content parts - Question and Expert
I have a Part view to be used in search result for Experts called ExpertSummary.cshtml. The view only contains the following elements now:
#model dynamic
<p>Expert Summary</p>
When the search result is coming I only expect the "Expert Summary" to be visible in Expert region of the Search but I am getting an additional "body" section (truncated to X characters). It seems to me because "body" is selected as a field when I created the Index it is coming up.
Each Expert record has an image of expert which is coming up in the search result and When I take out <Place Fields_MediaPicker="Content:1" /> from Placement.info it disappears, which is fine.
But I want this summary to be completely controllable in ExpertSummary.cshtml - like a two column layout where the left col will hold the expert image and the right one will hold a brief description along with some other info - but everything would be in the View - should not come from Orchard search module as defaults.
In short I want Orchard's Index and Search modules to be functional and working like it is now but the layout and information I want to control completely using custom HTML in Parts/ExpertSummary.cshtml view.
Is this at all possible? If yes, how?
Please suggest. I am completely lost my way in Orchard framework!
I'm not completely sure I understand your question... Orchards search returns a Summary view by default. So you need to control the layout of your summary. Use shape tracing to create a new alternate to change the layout of the summary view. So ExpertSummary won't control the entire layout, it will just control the Expert part. Then use placement to decide what to display. http://docs.orchardproject.net/Documentation/Understanding-placement-info
Also, tagging questions with "orchardcms" will be more useful than "orchardcms-1.7".
Orchard version is 1.6.
I created a new Content Type named Book, and added some Fields to this type.
I have 3 questions about fields in content type.
What is the difference between Input Field and Text Field?
How to bind Enumeration Field with data, for example, I want to create a Enumeration Field with data "Beijing", "Shanghai", "Guangzhou"?
I have uploaded a .docx file with Media Picker Field writing alternative text is This is my first attachment, but MediaPickerField link is displayed in webpage, not my written alternative text. How to solve it?
That is all. Thank you for your answers!
Great questions... The difference between input field and text field is that input field should not exist. :) I was strongly against it, because it would cause confusion, and it does... The input field is supposed to help you use the new html5 input types. The text field is about entering all flavors of text. One is surfacing an implementation detail, something specific to the rendering technology used, the other is about content semantics.
Not sure what you mean with the second question. What prevents you from doing that? The values are entered in the content type editor, in the settings that appear if you deploy the field (the little > next to it).
Side note: probably would have been best to create three different questions...
I'm looking to create an SDL Tridion schema with a list of repeatable links while avoiding multiple fields per link.
Hyperlink
In a rich text field I have the following options for creating a hyperlink:*
Component
Anchor
http://
mailto:
Other
When content authors create one of these hyperlinks, they have the option to select linked (visible) text as well as title and target attributes that function like typical HTML hyperlinks.
"Richtext" means a Text field with Height of the Text Area = at least 2 rows with Allow Rich Text Formatting selected.
Single Schema Field Link
When creating a single schema field, I see these options:
External Link (author options will include http://, mailto, Other)
Multimedia Link
Component Link (which can allow Multimedia Values)
Current Ideas
The best out-of-the-box (OOTB) setups I've found for this "list of links" is either offering:
a single 2-line RTF with instructions to create a hyperlink (of any type) in that field
separate fields for each type as well as additional fields for display name, target, and title (where the fields are assembled through template code), authors fill in only one of the fields (component link or external)
Question
Is there a way in the schema form designer, by updating the schema source, or through code to offer the same (RTF) hyperlink drop-down options, but in a single field? I could be missing something, but recognize this scenario isn't supported OOTB.
One question we are missing here is to consider if those links are going to be used somewhere else individually. If that's the case, multiple components would be my first choice, so we can reuse each component several times.
If you are planning to allow the editor to create a list of links that they are only going to use in a given component (not reusable), well, you have all the options mentioned in the previous answers.
To give you an idea on what's the best approach (in my humble opinion) here are things to consider:
Individual Components per link: use this approach if links are reusable.
Using embedded schemas (with the link structure) so this approach can be used in different component types (schemas)
Custom URL / Single Line Text Field: it requires an additional development effort and it is very unlikely you will keep the hard-link-references when creating internal links. As you know SDL Tridion keeps a reference to the tcm id in order to resolve links, trigger publishing, etc..
Custom URL / 2 Lines RTF: It will do the job, but you need to make sure you disable all the other RTF options from the Ribbon Tool Bar within the Schema RTF options, so you meke sure that the editors can only create links. Also, you might need to consider to add an XSLT filter to check if the edtiors entered something more than just links. These links are not reusable.
In general if you implement something custom (GUI extension + Custom URL) keep in mind all the TRIDION CMS concepts, like blueprinting (what happens when the link is inherited down), where used, etc...
My recommendation has always been to use Separated Components, but be careful with the link propagation when publishing...
I have seen this case at customers. If they consider less development effort, the idea of having a multiple embedded field is good.
You can have it as:
[text] Link Text
[Component Link] Link to anything
You would need an extra Content schema for External Links, like:
[External Link] Url
[text] target
[any extra option you need]
This means the editor would need to create a new External Link Component every time they create an external link. It is extra work, but it can also mean easier maintenance on the use of external urls within their site.
Lastly, the editor would just add multiple Component Links, those being of schema External Link of any other. It will be the template code which checks on the schema of the linked Component and add the code accordingly.
XML Name Description Field Type
[text] Text Text
[title] Title Text
[static_url] External URL Text
[component] Internal URL Component Link
In the field description for "External URL" and "Internal URL" you could add a comment to make sure that the editor doesn't get confused, only one of these two fields should be filled in. From the component, its ID can be used to create the dynamic link in the DWT. This solution has no development effort and for the editor is pretty much as intuitive as it can get. Of course this would be a multivalue embedded schema field inside the Links schema.
This use-case might work using a Custom URL field and maybe a GUI extension. The idea is to have a Custom URL that opens a popup (which might be a GUI extension). In that popup, you would select/construct your link (maybe using the same options as a normal RTF link - Component, Anchor, mailto, etc).
The popup would return a specially crafted string. The format could be anything, even an actual anchor tag (but JSon is also fine). Example: {href:'tcm:1-2',type='component'}.
Your Templates would interpret this string in order to generate something meaningful, like a dynamic link or static HTML anchor.
Also the Custom URL popup should be smart enough to 'decode' such a link (if a value was specified in that field previously) and maybe pre-populate some attributes in the RTF link constructor form.