I have a custom facet model in my sitecore project and I want to create value providers for my custom facets. So I added third party sitcore forms extension package(Sitecore Forms Extensions for SC9.3 and SC10.0-3.2.1) to my sitecore v10.1.How do I extend the value provider classes that come with Sitecore Forms Extensions to create value providers for my custom facets.
Related
I have a TYPO3 4.7 environment which holds 3 websites.
All theses website use TemplaVoilà template engine.
We are now redesigning one of these site and I wonder if I can use Fluid and Backend Layout instead of TemplaVoilà.
It seems that I have to desactivate TemplaVoilà in the extension manager to be able to use be layout.
Dislaimer: I'm not using TemplaVoilà myself.
The TCA Overrides of EXT:templavoila replace the backend layout fields with the respecting fields of TemplaVoilà, see here.
By reading this code, it should be possible to have both the TemplaVoilà fields and the Backend Layout fields if
"Enable data structure selection" is inactive and
"Enable the classic Page module" is active
in the extension configuration in the Extension Manager.
Are there any validators for Eclipse that checks that internal links between JSF web pages in the same project refers to existing pages?
I realise this is impossible to do in more complex cases, but it should be possible to do in the standard case.
One way to achieve something similar is to create Java constants for all page source files names (for example as properties in an app scoped bean) and reference them from EL, because EL validation checks those. But to do this you have to manually add all the file names which is cumbersome.
I have a requirement to store a list of designers with logos and some bio information in my Umbraco CMS. I created a document type called 'Designer' with all those properties. I'd like to now create a dropdown list with those designer names so I can associate it with other document types. How do I create this dropdown? I'm using the v7 of umbraco.
Checkout nuPickers for Umbraco v7. Should have everything you need.
http://our.umbraco.org/projects/backoffice-extensions/nupickers
http://github.com/uComponents/nuPickers/wiki
http://www.nuget.org/packages/nuPickers
Look here for help with creating custom labels using macros
http://github.com/uComponents/nuPickers/wiki/Custom-Labels
As I understand, your intention is to let editors pick designers from the designers dropdown when editing content items in the backoffice.
If so, you may want to either use an existing data type called 'Dropdown' or create a custom data type.
If you only want the names in the dropdown, the default 'Dropdown' data type may suffice. Take a look at the article explaining how to customize the 'Dropdown' data type
Otherwise (say, if you want to show the avatar of the designer in your designer picker), you may want to implement your custom property editor (designers picker) and a custom data type related to it. Then you will be able to associate your data type with any document type you want.
A couple of useful links in this case:
how to create a custom property editor in umbraco 7
the demo which includes building a custom picker property editor to assign custom data to a document
Umbraco v7 XPathDropdownList implementation
I am developing a JIRA plugin and I'm trying to add a custom field to the Add project page. As far as I know, a custom field can be added only for an issue. Is it possible to add a custom field (a text field or a select list) at a project level?
I have found an plugin, which is able to add metadata on Project level.
Please take a glimpse at this link
Short answer: doable but not particularly easily
The way you do this is to write a WebWork plugin that changes the Java class that handles that webpage. The process is that the actions.xml file contains the AddProjects.jspa, e.g.
<action name="project.AddProject" alias="AddProject" roles-required="admin">
<view name="error">/secure/admin/views/addproject.jsp</view>
<view name="input">/secure/admin/views/addproject.jsp</view>
</action>
which tells you that the class name is AddProject, which you can extend to handle the user setting a value in this new field. Then you also need to decide how you're going to store values for each project (more info in the Practical JIRA Plugins or JIRA Development Cookbook books). The hardest part here is that the template files are .jsp files which you can't change directly with a plugin. What I usually do is write a ServletFilter to inject JavaScript to change the AddProjects page that way.
There is no elegant way, but you possibly can use Custom Project Properties for JIRA plugin.
This plugin allows to:
define list of custom fields for projects
define custom fields per project
fill custom fields on project administration page
I wanted to know how Orbeon Forms work in Liferay because the Web Forms portlet is very limited, so I visited Orbeon's website and read its documentation. Then I downloaded it and ran in a Tomcat server, I built a form with the Form Builder and then tried it with the Form Runner.
My question is, how can I export one of the forms I created with the Form Builder to include it in Liferay as a portlet for example? Is that possible? Can I export a form into a WAR for example and then deploy it into Liferay?
I know you can deploy Orbeon Forms into liferay but I only want to include a specific form, not all the application with the Form Builder, the examples etc.
Could anyone help me?
First, a clarification: if what you mean is that you just want "the form", in the sense of just the XHTML, that can't work because any form built with Orbeon Forms needs a runtime to function. If the form is created with Form Builder, that means the Form Runner runtime. Either way you will need an Orbeon Forms portlet or servlet.
The forms you create, when published, are stored into a database. By default this is the built-in eXist XML database, but you can use Oracle, MySQL, or your custom persistence layer.
In order to see forms in Liferay, you have two possibilities:
The Form Runner Liferay proxy portlet
The full Orbeon Forms portlet
I recommend you peruse these two pages for details.
How it works depends on which type of portlet you use.
If using the proxy portlet, then the portlet is very lightweight and just forwards requests to a separate webapp running the Form Runner runtime. You configure the portlet to point to a specific form.
If using the full portlet, then Form Runner runs directly as a portlet. Here the portlet will load a landing page, and you probably will want to modify that landing page to point to the forms you want your users to see.
In both cases, your published form will be found as long as Form Runner points to the right database.
In your case it seems like the proxy portlet might be your best option. Note that lots of bug fixes have taken place with the proxy portlet since 3.9, so I would recommend a nightly build. For reference here is the source of the proxy portlet.