I have created a custom web-part that contains telerik mossradeditor control. but this webpart is not displaying inside the add web-part page of SharePoint 2007.
this is happening only my prod environment but its working in stage and development environment.
Installed radeditorsharepoint version 5.5.1.0.
Please help me to resolve this..
Examine their online documentation and make sure you are following the appropriate steps: http://www.telerik.com/help/aspnet-ajax/moss-installing-radeditor-in-moss-2007-farm.html.
You need to have it installed on production as well, you may have missed some files.
About your own webparts, not the one Telerik provide - make sure it deploys properly. Check assembly references and make sure they use the correct versions. You may need a bindingRedirect in the site's web.config.
Related
This is the error I get
The rest of the description:
There were some changes made on the mobile version of the app,
adfs was installed and set to ifd claim base authentication,
There were also changes on site map.
Thank you
Most likely you corrupted your site map (or whoever made the edits corrupted your site map).
The only way I know how to fix this particular error is through XRM Toolbox, Sitemap Editor plugin.
You will need to get the Sitemap XML from a different CRM instance that has all of the same customizations and MSFT solutions installed (Dev or Test should suffice). Once you have that Site Map XML, copy and paste it into your "Corrupt" sitemap XML, and save/publish the changes from XRMTB. You should be back in business.
Attempting to migrate a web part solution from farm solution to sandbox solution. The steps I have seen online outline changing a property at the project level which is a boolean called 'Sandbox Solution'. However I do not see this option when I view the properties of the project. Does anyone have and ideas on how to migrate a solution which contains multiple web parts from a farm solution to sandbox?
I am afraid this can't be done. When a farm solution is created and deployed it loads extra controls into the solution that allows the solution to easily access data outside of its container. An example is the user control. This control is not allowed in a Sandbox solution as it allows access to the SharePoint root. Just changing that option isn't going to revert that option because the entire solution is geared around it even if you don't use it. It will be deployed. I found the blog post you are talking about or one similar to it and have never seen that work. This is why you define your project type at the beginning because Visual Studio applies the different controls depending on your selection. Removing the sandbox and recompiling will not work.
On another note, you can however convert a sandbox solution to a farm solution. This is because you are moving from stronger security to "less"
I have prepared an Orchard based website locally, using WebMatrix. I then published to my hosting provider.
However the deployed version isn't picking up the styles or scripts, either my theme or for the dashboard, and it's giving me 404 errors.
I guess I have to change the path somewhere to get it to pick up the files, can anyone tell me where? or is there a different solution?
I thought that this would be a setting on the website, but as it turns out it was an IIS setting.
I switched the pipeline mode from Classic to Integrated, and everything worked.
I have an installer I am modifying where we are modifying a web site in IIS. The requirements state that the end user must create the site first in IIS. We read the site information they choose from a dropdown in the installer for their site, and store the information in properties in WiX.
I have a WebSite element under a component, and have the ConfigureIfExists set to yes. A lot of this seems to be working great, it resets the directory of the site to where the website is on the drive.
The problem is that when I check the set up in IIS, the web site is not started, even when I have AutoStart = yes and StartOnInstall = yes. The problem I am seeing is that, since it is an existing web site, it creates a duplicate binding for the site, same port and everything, which is causing the site not to run.
Does anyone know why this is happening, or how to resolve it? I need it to not duplicate the binding so that the web site can be restarted when installation is complete.
I advise you to try this scenario with WiX v3.6 (take the latest available build). There were lots of fixes in IIS7 extension, and it's very likely your problem will just go away.
EDIT: now WiX 3.6 is in official beta. It is quite stable and contains lots of fixes to IIS extension.
I had a similar problem. I was able to work around it with the following method, but be advised, it is kind of a hack.
For my existing website, I match it on SiteId and set whatever configuration properties I want to change with the WebDirProperties attribute. Then, in the iis:WebAddress element, I set the Port number to some unused port (I used 8081). This will add an extra http binding in IIS7 (as you saw in your question). Then, I create a custom action that I run before InstallFinalize. The custom action basically loops through the site Bindings, looks for the one that matches the bogus port that I entered in wix and deletes it. Then the custom action starts the website and everything is good.
This was the only way I could find to get it to work in Wix 3.5. It is not the best method, but it worked for me.
Well my requirement is :
Need to develop a custom workflow,the workflow should take properties like site url, list names etc., From the client.
I am able to develop the workflow, but i need to make it available in designer. I tried the method mentioned here:
http://www.chaholl.com/archive/2010/03/13/make-a-custom-activity-available-to-sharepoint-designer-2010.aspx.
1)I have created the required action file.
2)deployed(copy-pasted) dll into gac.
3)made safe-control and authorized type entries in web.config of the corresponding web application(on which my site collection exists)
But it is not helping me out.after following the steps given,when i try to open any workflow in designer,it gives an error saying it cannot find an action(assembly) with xyz name.
If I understand correctly, you built an entire workflow and am trying to make it available to SharePoint Designer. The guide you are following deals with custom "Actions". Actions are a sub part of a workflow. This may explain why your deployment isn't working, because you're trying to deploy a workflow as an action.
If you could provide more information about your steps, we could try and figure it out.
Thanks
C
http://www.cjvandyk.com/blog