0

I have a .wsp Farm solution deployed to my web applications, as follow:-

enter image description here

enter image description here

I have created this solution using VS .Now inside my current web application I have 2 site collections. Old site collection have this solution available under “Insert>>Web Part>>Custom” + inside the “Site Setting>>Web designer Galery>>Web parts” as follow:-

enter image description here

But now I added a new site collection to my web application , but the problem I am facing is that the .wsp solution is not available inside the “Insert>>Web Part>>Custom” Nor inside the “Site Setting>>Web designer Galery>>Web parts” as follow:-

enter image description here

Can anyone advice please? Could this be a version problem ? since I have applied some CU updates from the time I deployed he wsp and when I added the new site collection ? can anyone advice please?

EDIT:-

Here are the web part setting inside the visual studio:-

enter image description here

now the site URL refers to an old site URL. Now I have deploied this wsp using the following steps:-

  • i copy the wsp from the visual studio project.
  • Then i run the following commad:- "stsadm -o addsolution –filename [c:....]\WikiKnowledgeBaseRedirect.wsp"

  • i went to "central administration>>system settings>> Manage farm solutions>>click on WikiKnowledgeBaseRedirect>>click on deploy solution >>select the web application from the “Deploy To?" drop down". and it became available to my old site collection which have the following URL "http://servername/Site/Customes" different from the site URL inside the visual studio. so seems the site URL inside the visual studio do not have any value ? is this correct?

here is the feature screen as requested :-

enter image description here ok it mentioned that its scope is site, then why it did not appear inside the site collection feature or inside the gallery>>web parts section?

EDIT 2

enter image description here enter image description here enter image description here

  • Can you please upload the feature screen in visual studio? – Amal Hashim Dec 2 '14 at 13:42
  • @AmalHashim thanks i have uploaded the screen, now it mentioned that the scope=site. so why it did not appear inside the site collection>>gallery>web parts ? – john Gu Dec 2 '14 at 14:32
  • Ok. Now open the new Site Collection features page (not site features) and check if you can see feature with name WikiKnowledgeBaseRedirect Feature1. – Amal Hashim Dec 2 '14 at 14:33
  • yes i already checked it , and it is not there. even on the site collection which have this feature inside the "WikiKnowledgeBaseRedirest Feature1" is only avilable insdie the "site setting>>web designer gallery>>web parts"..can u adivce ? – john Gu Dec 2 '14 at 14:46
  • 1
    Please post a screenshot of your sitecollection features page – Amal Hashim Dec 2 '14 at 23:33
1

The webpart is deployed as part of a feature. Activate the feature in new site collection and then the webpart will be available.

  • but the feature is not available in the site collection features. i went to "Site settings>>site collection features", there is no feature for the related wsp ? can you adivce ? – john Gu Dec 2 '14 at 13:20
  • In visual studio check which feature the webpart is associated with. Then check the scope of that feature. Then make sure that feature is deployed. – Amal Hashim Dec 2 '14 at 13:22
  • also inside the site collection which have this feature deployed the wsp is not listed inside the "site collection features",instead it is listed inside the "Web Designer Gallery"... i am now confused.. – john Gu Dec 2 '14 at 13:22
  • now when i first deploy the wsp . i did the following steps:- I run the following "stsadm -o addsolution –filename [c:\....]\WikiKnowledgeBaseRedirect.wsp" Go to central administration>>system settings>> Manage farm solutions>>click on WikiKnowledgeBaseRedirect>>click on deploy solution >>select the web application from the “Deploy To?" drop down. and it became available to my old site collection. – john Gu Dec 2 '14 at 13:27
  • Your old site collection will get this automatically because it was previous deployed and feature got activated. Try to directly deploy the solution from Visual Studio. And set the SiteURl as the new site collection. – Amal Hashim Dec 2 '14 at 13:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.