Is there a way to change the built-in templates?
Concrete example: I want to change the template that is used when creating an event invocator. I want to change the visibility of the generated method as well as the the name.
Go to template explorer ( ReSharper > Tools > Template explorer )
Search the desired template and click on Edit Template or double click to open it.
Edit the template as you want and save it.
More info here
Related
Currently trying to write my first NETSuite PDF template, and am struggling with so many aspects of it.
I am unable to add an "End Of Page" to my template.
When I click the button, nothing happens.
I have tried...
Examining default templates in which I can add pages, and identifying the code change associated with the change. I could not find any change.
Creating a brand new template, and trying to add a new page. I was not able to.
"End of Page" just inserts a page break - <pbr />.
You can switch to Source Code view to see exactly where it's inserted, and usually it's not where you want if you're using the WYSIWYG editor. So you can move or manually enter the <pbr /> in the correct place in the Source Code editor instead.
I am creating a custom webpart using the Url Selector from kentico. I want the user to select content just from the Media Library. I went to form controls -> Url Selector -> Properties -> Dialogs_Content_Hide -> Default Value -> Yes and it still showing it in the Web Part. If I select the Dialogs_Web_Hide, Dialogs_Libraries_Hide and select the yes option in the default values, they hide, all except the Content_Dialogs.
Is this a bug? Or its something wrong?
Here is an example of the tabs
First set the form controls properties back to the way they were. If you don't, it will cause all kinds of problems later on.
Secondly, when you create the property in the webpart in the UI, select the URL selector form control for your text fields control. The scroll down just a bit and under the Editing Control Settings you'll see an "Configure" link. Click it. In there you will be able to tell the form control what tabs you want to enable and disable.
To add to Brenden's answer; if this is something you need to do a lot for your current build, then I'd also suggest making a copy of the Url selector form control and customize the properties as you originally mentioned. This way, you leave the default control in place for the system and have a control tailored to your needs. I've done this just now to check with a new form control that I called Media URL selector. Do make sure that you select the same source file as the original control in the Cloned form control file name property - Kentico by default will try to locate a new file called <original filename>_1.ascx. The reason for this is that admin section of your site also makes use of this control, so you may cause a nasty side effect somewhere else in the system.
As for why the settings had no effect; these are the default values you are setting. If you already have the form control in use, then the default setting would have been applied as they originally were. If you find one of the fields in question, you can change the control type to Text box, click Save, and then reassign it to Media URL selector.
I know you can export one GI at a time to xml, I'm wondering you can select all user GI and export to XML as a backup.
Thanks
You can do this by creating a customization project and include all the generic inquiries you need in one package. The project can be exported and imported which includes all of your attached GIs. We do this already and works great. Do not forget to update from database when making changes before re-exporting.
Simple list of steps if you have not created a project before: (using 5.30)
System > Customization > Customization Projects > create a new project (save)
Click on the hyper-link for your project name to open the customization project window.
Click on Generic Inquiries
Click the add (plus symbol) and check/select all of your GIs and click save. Note the 'RELOAD FROM DATABASE' option. Do this step when you make changes to your GI that you need to update into your package as this does not happen automatically when saving changes to your GIs.
You should see the list of Generic Inquiries include all that you selected
In the upper right under File (still in the Customization project window) select 'Export Project Package'. A zip file will be downloaded from the site which includes all of your XML for each GI
The Situation: I've got a mid-sized chunk of html/javascript that contains an authentication script/input (it's a text input, radio control, and a combo box and a few buttons). What it is is less important than the concept that it's a mass of static client side code that the marketing department can pretty easily accidentally the whole thing.
The Desire: I want the users to be able to add it as a whole to a page, but not be able to modify it. When something needs to change, I want to change it in one place and have it be changed on all the pages.
What I've Tried: Widget with a default text. It works, but feels wrong. Users can edit it, and if they do when I fix it one place it doesn't propagate to all the instances. I'm a bit of a Kentico noob, but it seems like there should be a better way to do this.
Also note: I'm using portal engine if that makes a difference.
A widget is the proper usage. What you make your widget inherit from is the key in this case. I'd suggest creating a new widget based on a static HTML webpart. This way you can set the static HTML markup and hide the property from the content editor on the front end. You can do this by going to the Properties tab of the widget and setting the visibility of the field on the form. Don't delete the field, just hide it. It should be a checkbox that says hide on public form or editing form.
** Edit **
As I read through my answer and comments, I realized I meant to say clone the static HTML webpart and set its default text to your javascript. Then create a widget based on that cloned webpart. The text will reside in the web part and will allow you to update it in one place later, if needed.
I will not do it this way because you will be not able to make changes in the future. You can better create a new webpart this can be an empty webpart and then create a custom layout. In this layout you can put you're code. In this way you can always change you're code in the future and then it will be changed on all the places where the widget is placed.
I'd use a new widget based on the Static HTML webpart (make the field read only or hide it as Brenden mentioned), but store the data in a new custom setting.
no coding needed (only a macro to read the custom setting)
able to edit the script on the fly on any instance in the settings module. If you have multiple of these settings you won't need to go through all kinds of widgets to adjust their default setting but find them on a central place.
Cheers!
David
In this case I think it makes sense to create a custom web part to store all your code in it and use it that way. If you want to achieve it without creating a custom web part, you have to store the code in some non-web part and not widget specific object. I like the suggestion of creating a custom setting. You can then access this custom setting via a macro. This macro can be used as a default property of a newly created web part (inherited e.g. from the static text web part, you'd use the text property). You may as well create a widget out of it. Another approach is to use Kentico localization keys as a workaround. you can create a key in the Localization application and access it again, via a macro, e.g. {?customkey.myhtml?}. The approach with a custom setting however sounds cleaner to me.
This syntax should be working to access a custom setting value via macro:
{%Settings.CustomSettings.xxx%}
{%Settings.CustomSettings["xxx"]%}
{%Settings.CustomSettings.GetValue("xxx")%}
I have a custom web part that has custom properties. To Edit the properties I have a custom EditorPart.
I need these properties to be able to be exported with the webpart. To do so I have to set the WebBrowsable attribute to true which makes the custom properties show up twice in the editor pane once with my editor part and my custom validation and once automatically.
Is there a way to get the properties to export with out setting WebBrowsable to true?
You might want to try setting the ExportMode property of your WebPart
There is a good explanation on MSDN here
http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.webparts.webpart.exportmode.aspx