I used the Azure portal to install an instance of Umbraco.
I need to use the Umbraco forms for a simple contact form.
The Umbraco instance contains the forms and I can perfectly create and configure everything I need about forms (fields, workflows, ...).
Problem is that I can't get to have it on any page.
The video here shows how to do it but when I click on the button as shown 23 seconds in the video, I can't find the forms and therefore not add my forms.
I tried to add the Razor line that it seem to generate based on the guid I get on the Form configuration page but when I save, the online page (I mean, the page of the actual website) is crashing (Yellow asp.net error page).
Does anybody knows what is going on here?
EDIT: Maybe I should mention that I did click on the Install button in the Forms section and waited until it refreshed the page. Surprisingly, it continues to prompt for installation now.
I found the answer.
Seems like when we installed Umbraco at first on Azure, the auto install failed at taking the database into account.
We had to manually edit the config file to make sure everything was all right.
However, some bits for the Forms were not referenced properly.
So I uninstalled the forms completely and reinstalled them from scratch and it started to work fine.
Related
Running WSS 3.0 and I've been given full access to sharepoint. I'm working on a lean initiative to clean up SP and delete old/outdated libraries from the site or at least from the main page. I've been able to get into quicklaunch where it gives me the option to remove it from quicklaunch but it's still showing on the front page. I've also found the button that lets me delete the document library but all it does is delete all the content. The link is still on the front page but when you click on it says something about the link being broken.
I'm on my own with this project and I'm not part of the IT team but I need to be able to delete document libraries and the content. Or at least edit the front page to remove these links.
I've found a lot on the internet about powershell and sharepoint designer but I don't have either of those and I'm not sure if I'd be tech savvy enough to use them. Please tell me there is some secret button I can hit to remove the useless libraries.
On my sharepoint site I am unable to add an existing basic webpart to a page where I've added webparts before. I am a site owner. I am using IE 8. I also work remotely using VPN.
The strange thing is IE won't even open up the EDIT MODE.
When I use Google Chrome, it is able to open up EDIT MODE, and it was also able to open up the Add Web Part popup, but when you actually select a web part and press ADD...nothing gets added to the main page.
The extra strange thing is from Google Chrome, I am able to delete and modify existing webparts.
I've upgraded to IE 9 and the same issue still happens.
i assume the similar issue you would be facing with firefox it seems your css is not compliant with IE8 try using ie8 in campatibility mode or use following querystring parameter at end of ur url
toolpaneview=2 and see what is the result
I had that problem and it appeared that a CSS file was messing up with the Ribbon controls.
Try to disable a CSS file at a time.
Regards,
Pedro
We had this issue (or at least a very similar one) where, in edit page mode, clicking on 'Add a Web Part' had no effect. I was assuming that it is a JavaScript issue. In, I beleive, the same day, it effected both my Production and DEV Site Collections, in IE8, Firefox and Chrome. We restarted all of our servers and ran the config wizard. No good.
We were able to create new pages which seem to be uneffected.
For an existing page, our workaround is to edit the properties of the page, then, down at the bottom, select 'Open Page in Maintenance View'. Select one of the Web Parts and Close it. Note: It seems as though if you unselected the 'Allow Close' checkbox, it wont be on this list. Then click on the 'Go Back to Web Part Page'. Click on the zone where the closed Web Part was. You may now be able to 'Add a Web Part'. If so, the last Web Part folder on the left will be 'Closed Web Parts' which I beleive you can put back (Open) the closed Web Part.
I have see this issue occur when someone else has the current page open in edit mode. Until that person either checks in or undoes there checkout you will not be able to edit the page.
Apologies if this has been answered, but I could not find a similar question:
I am developing a webpart for MOSS 2007. I am using WSPBuilder to built a visual webpart (ascx) and everything works fine, but the development/debug cycle is just painfully slow, so I'd like to know if it is possible (without being too painful) to develop the user control faster using an .Net Web Application project with all of the nice F5 debugging, then import the final product into my SharePoint visual webpart.
The user control interacts with a LOB system (SQL) and does not reference the SharePoint API at all. (The reason I am building this as a webpart is because I don't need another web app to run this one page, so putting it into a webpart on a new webpart page on my existing site is the best solution IMO.) I would obviously need to import (reference?) my data access classes into my "temp" web app, but think that would not be too much trouble.
I realize this will be extra effort to get this set up, but am thinking the payoff will be reduced development time of the actual user control using a little web application vs having to use the compile/build WSP/deploy WSP/reset ISS/test/make a change/repeat cycle that MOSS requires. (I guess SP2010/VS2010 has spoiled me with the native SharePoint tools available.)
Update:
I have successfully built a simple web app with one page and loaded up my UC on the page. (I had to comment out all of the Sharepoint Import and register statements that WSP Builder added to the UC for me when I created the webpart.) I added references to my utility classes (which I left in the obj\Debug folder in the original SharePoint project). It took me a while tinkering with everything to get it to work, but the steps ended up being pretty simple and I think I can replicate the steps quickly for future projects. Once it was set up, I was able to rapidly design the UC and build in the UC functionality using the typical F5 debug cycle. Unless someone can show me why this is not a good idea, I plan to repeat this for future projects! Thanks to everyone for thier input.
.
Update 2
Well, I am not sure what I did but moving the UC back into SharePoint proved to be troublesome. The first time I did it, I spent several hours getting it to work in SharePoint, making me question whether it was worth it. However, I am stubborn and tried it again. This time, I only copied and pasted the markup below the "header section" (the part with all of the <%# . . . %> statements) in the ascx file and everything went perfectly. I think I must have changed something inadvertantly the first time. I think I will continue this pattern as it is so much faster to build and test the UC in an ASP.NET web app. (Again, this only works if you are not referencing the Sharepoint API anywhere in the UC.)
The answer here is the SmartPart. It is perfect for just the scenario you are describing. Very easy to create a Usercontrol using "vanilla" ASP.NET and have it work as a webpart in SharePoint. I've outlined the steps to migrate from ASP.NET webpage to statically bound SmartPart on my blog.
What you intend to achieve is surely a nice idea.
Just remember to strong name your user control, drop it in your Server's GAC, update SafeControls section of your SharePoint 80's web.config.
All these setps are one off, after each successive builds (of your web control), you have to just deploy the control (used forcede deploy) in GAC and reset IIS.
You can add this control to toolbox in VS by selecting 'Choose Items' and selecting ther assembly you just deployed.
In addition you can create a test ASP.NET page to test the functionality of your control.
When adding or editing a page in a SharePoint Pages library we get the following exception:
[COMException (0x81020016): Item does not exist
The page you selected contains an item that does not exist. It may have
been deleted by another user. Click "Home" at the top of the page to return
to your Web site.]
at Microsoft.SharePoint.Library.SPrequestInternalClass.RenderColumn.
The weird thing is, when we first do "Check in" and then click the Publish button it works perfectly. But clicking "Publish" directly generates theis error, BUT NOT ALWAYS!
The Pages library has publishing and item planning on, NO workflow (seeing as the person who adds / edit pages is also the approver) and Major/ Minor versions.
We use a content type derived from publishing page and a custom PageLayout.
I'm sure you would have already checked this but is there any more information in the ULS logs?
Also have you tried setting the debugger to break on all exceptions and does this give you more information? Go to Debug, Exceptions and tick Common Language Runtime Exceptions. Then go to Tools, Options, Debugging and untick Enable Just My Code. Finally attach to w3wp.exe.
If you are running Windows Server 2008 you could also try taking a dump file at the point the debugger breaks above. ADPlus might help if you are running Server 2003 but I don't have experience with it. You should then be able to open the dump file with DumpChk or WinDbg.
Edit: As discussed in the comments, this is code deployed to production that can't have its service interrupted. The only way you could create a dump file is programmatically. Have a look at this question I asked that will hopefully help you if you need to go down this route.
Other things to try if you don't want to get down and dirty with debugging is to try deploying your custom bits to a clean server. See if you can still reproduce the problem or if it changes.
I am assuming that you are using load balancing with 2 web servers.
The fact that it does not happen always points to there being a difference between the servers.
There are then a few things that you could check:
Are all the versions and service packs are the same on both machines
Have any of the servers had beta software installed
Is your code the same on both servers
One thing you could do to test without taking the system down: Is to remove the first web server from the cluster see if the error occurs, then add it back and do the same thing with the second web server.
I am getting a random web part error, it works one refresh and then not the next:
Web Part Error: One of the properties of the web part has an
incorrect format. Windows SharePoint
services cannot deserialize the Web
Part. Check the format of the
properties and try again.
The web parts have been on the site for a long time, and I have checked Micorsoft Support, http://support.microsoft.com/kb/826786 . And it is not a permision error becuase it has been this way for a long time. The only thing changed in regards to webparts was going into Site settings > Web Parts > New and selected some webparts that were not in the list and I think I also Checked the ones that are having this random error and clicked "Populae Gallery". Any body have a clue?
This could also be because of insufficient disk space on the server where SharePoint is hosted. http://www.sharepointblogs.com/vipul/archive/2006/09/25/webpart-error-due-to-space-crunch.aspx Check the available disk space.
Hope this helps.
Have you tried rebooting your server. I have just recovered from this exact problem. One of my frontend servers ran out of disk space yesterday and I recovered 10Gb of it, however this didn't rectify the error I was receiving when trying to view or add page viewer webparts until I rebooted it. All is perfectly fine now.
but try doing this:
Go the central administration
operations
service accounts
Web application pool (radio button)
webservice (drop down); select windows sharepoint services web app
application pool (second drop down); select the site that the problems occurs on e.g. home_port_80
user name (text field): type in the account info you have used during sharepoint post installation configuration
password: at last type in the password.
hope it helps
Another thing that can cause this is an "undocumented feature" in SPD that splits the Web Part properties across two lines, like this:
<FrameType>
None</FrameType>
Just removed the line break, like this:
<FrameType>None</FrameType>
and everything started working again ...