Where are the properties for custom control stored? - xpages

I know how to define the properties of a custom control on the design tab but I am not seeing them on the source tab. Where are they stored? If stored elsewhere, how do they get copied when I copy the custom control?

When you open the java perspective of your designer. Go to the custom controls directory and you will find xsp-config files. These files have the same name as the custon control they belong too

Related

Issue related to layout of custom webpart

According to requirement of application, I have developed a custom web part in Kentico 9. This web part is using with same functionality at various places but we have to use with different layout structure.
As per my understanding, we can create custom layouts for a single web part from "Layout Tab" in web part configuration. As I used same things with various Kentio built in web part like Logon form, Logon-Mini form, etc.
But while trying to create new layout for my custom web part, I am getting web part loading error and when I checked into event log it is showing following error:
The file
'/CMSVirtualFiles/WebPartLayouts/=vg=87a868ce-926c-4cb3-a441-b4f1d4310afc/TDNForgottenPassword/ForgottenPassword.ascx.cs'
does not exist.
Here, internally system looking for ".CS" file under "CMSVirtualFiles" folder, which has actually under the "CMSWebParts" directory in which I have created my user control.
Is there any specific configuration required in custom web part to implement multiple layout of it? Please help me and guide me, what am I missing or doing wrong?
Check your webpart code file property in the ascx file. You need to specifically declare the full relative path to the .cs file and not just the filename. For example:
Correct
CodeFile="~/CMSWebParts/Community/GroupRegistration.ascx.cs"
Incorrect
CodeFile="GroupRegistration.ascx.cs"
Please make sure you don't have the store virtual files in the file system setting enabled.

UserControl and Feature activation

I have a sharepoint solution package with a Custom UserControl inside. When I deploy the .wsp the user control is placed in the CONTROLTEMPLATES directory. Is there any way to "delay" this step until feature is activated?
In other words what I would like my custom user control to be available only after the feature is activated.
As far as I know this is not possible. On deploy all the needed files are copied to the correct location. It is actually feature independant, because you don't even need a feature to deploy files. You will see that a feature is automatically created when you for ex. add a webpart to your solution. Not when you add a mapped folder.
What are you trying to achieve with delaying the usercontrol? What you can do is check in your usercontrol if a certain feature is active and adapt the rendering of your usercontrol accordingly. Ex. Show message that the feature should be activated before using the control.

Sharepoint2010 custom design as WSP

I am trying to get a solution for my issue. I have a set of HTML CSS and Images, which I want to apply to my sharepoint portal as a part of branding.
My concern is I want to make my design as WSP or any other kind of solution so that it can be installed in any sharepoint 2010 portal so that the user can switch back between actual sharepoint design and this custom design.
In short I have a custom HTML design which I need to implement to any sharepoint website, this design can be turned On or Off by the administrator just using the portal/Site screens.
Thanks in advance
SharePoint branding is always a tricky job. The safest way to achieve your goal is to create a separate masterpage with your new branding. So the user can choose to apply the default branding with the default masterpage and when he wants another branding your customized masterpage can be used.
Create a new SharePoint project and add the needed css inside a mapped layouts folder. Then you can reference your own css file in the new masterpage. Watch out with changing the masterpage, because it contains a lot of placeholders which will render different parts of the page. Try to work around these placeholders and make sure the masterpage works in different scenario's (ex. that the layout isn't broken when page is in edit mode, ...)
Once you are finished with the design, the user can use it by applying it in the settings. Another option to make it easier for the enduser, is to create a control that is a switch to apply your masterpage (ex. with custom action).

access localize css file through SharePoint designer 2010

1) how can i access _layout/1033/styles/custom.css file with SharePoint Designer ?
2) if i created a folder named 1033 through SharePoint Design in Style Library. What setting i have to make in master page to pick localized folder.
Thanks
_layout is a virtual directory mapped to the 14 hive. Altering of these files directly is not recommend and I believe is not supported as these files can be overwritten at runtime.
If you must use sharepoint designer then your best bet is to make a copy of this file and place it in the style library.Then update your site to use the new CSS file loaded in your style library.

SharePoint -copy library template when creating a new item

I have a document library with 4 content types, each having a default template. Users click on "New" and choose the content type for the new item.
I need WSS 3.0 to create a copy of that template (in the current folder) so that the users can edit it. I do not want WSS to open the template in a client application -I need it to leave the template right there.
How could I accomplish this?
Thank you for your help.
I wonder what you mean by EDIT the template copy, you mean setting properties? cause otherwise you must open it in a client app.
Anyway, we did t before for a client, he needed a file naming convention feature, so we added a feature that replaced the New button options with our own option, that takes the user to our custom page, where he selects the content type and fill in appropriate metadata. When clicking OK, the template is copied to the folder, given name according to the convention and assigned metadata. After that we opened the file in a client app, but you don't have to do that. The whole thing involved
Feature XML files
Layouts custom page with code behind
Custom menu customizer code to hide the New button options
Hope it helps

Resources