In Orchard CMS I created a menu in navigation and populated it. But when I try to get back to manage the menu I get a 404 error saying the resource is not found. I created two other menus using advanced menu without a problem.
I then tried a duplicate hoping it might prompt me that one already exists. Now I cannot get to the resource to delete it nor can I create another menu to manage without the 404 error. I have no idea where to look. Any help?
You probably created a menu with a name containing a space or some other character not valid inside a URL. You can change that manually in database - table Szmyd_Orchard_Modules_Menu_AdvancedMenuPartRecord.
Related
I am new to Sharepoint and was playing with the webparts. I downloaded a zip file called LyteBoxForSharePoint and uploaded the webpart using add a web part function. Now I am getting errors. The good thing is, that it's only my dept page. The bad thing is I have no clue what happened. All other pages beside the dept landing page is working. So, I am guessing it's only the landing page that has the issue. Is there a way to find out what code was added or to revert to old code. The error I get is the following, and it keeps on changing every time I refresh the page.
An unexpected error has occurred.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: e8eca359-70f9-42d0-b41e-834fbe0fc910
Date and Time: 2/23/2012 2:47:39 PM
Could be anything, most common error in SharePoint is authentication errors where a web part is trying to reach content the logged in user cannot reach
You should check the logs, they are available in the directory C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS
Open the last modified log file and search for your Correlation ID, e8eca359-70f9-42d0-b41e-834fbe0fc910
When you find the errors there you will now and also be able to post something that we can use to help you.
Then there is always the webpart maintenance page: /_layouts/spcontnt.aspx?url= http://sharepointserver.com/_layouts/spcontnt.aspx?url=default.aspx
Rex,
first browse the page which is giving webpart error and copy the new correlation id and go to the log folder under 14 hive and open the latest log file and find the correlation id. it should give you the error details if logging is not disabled.
also you can go to the webpart manger on the page to revert the page to the previous state by adding contents=1 as query string and in this page you will get list of webparts with checkbox against each. select the faulty one and revert to previous version if any or delete it.
you can also use SPD2010 to remove the webpart with error. alternating powershell can be also used.
One way to check if the webpart is installed is to type ?contents=1 after your url. There is also stsadm -o preupgradecheck and unfortunitely stsadm has another command to list all webparts but I cannot think of it at this time
We set up the SharePoint 12 hive folder for a custom theme with a new xml entry and folder.
Is everything required for a custom theme living in the theme folder? I'm asking because we are seeing CSS files that appear to be dynamically named rendered on SharePoint pages in the folder that are not actually in the folder.
Will we have to use SPD and custom site changes to get a custom theme to work?
I've got a designer working only in the theme folder, but he is seeing rendered css that he can't get to. He is not using SPD
That 1011-65001 squence file is found nowhere? what is that an where can I find it. Any way to have my custom theme all hard fixed name css files in that folder without using SPD?
/_themes/MYNEWFOLDER/MYNEWTHEME1011-65001.css?rev=12%2E0%2E0%2E6421
===
Update: I just realzed that css is creatd when I apply the theme and so it's in my _themes site folder. But now, when I attempt to re-apply the theme, that was working before, now i get a write error on _themes.
I can answer your first query why its dyanamic name this is because themes which you installed are ghosted version and when you apply them an unghosted version is created for the specific site where it is applied. so a dyanamic naming is required and it cannot be hard coded in MOSS even if you try using SPD you can do it but you have to remove the theming then.
the same you have also have notified in update that the css name is changed only when you apply it.
regarding your second issue of reapplying it did you try applying another them and then back to first one and is giving error then please check the 12 hive logs it will give you cause of failure and if still you are not able to figure out the same plz share the relavent log here we will try to help you
I've been getting an error in SharePoint that reads:
System.Web.UI.ScriptManager is not allwoed on this page. The type is not registered as safe.
I googled around, and the results pointed to missing AJAX server extension installations while using the asp:scriptManager tag. However upon closer inspection of my project, there was no findings of such tag. Whats even more strange, was that after I reinstall/reset the masterpage, the error went away and I was able to read my site again.
I was wondering whether the above error would appear if certain SharePoint files gets overriden? Or are there other less obvious/non-trivial reasons for it?
Thanks.
When it comes to the error, it is very likely related to your custom masterpage is not including the tag itself but it has a control or code that requires and/or inserts the tag.
Example: it is a common practice to code a custom webpart or usercontrol in order to insert the ScriptManager under the forms tag programatically in case one isn't present, and once this custom code hooks the page render with the ScriptManager, it will check for whether it is allowed in web.config -- thus you get the error.
SharePoint's web.config does not comes with Ajax enabled. Telerik has a good tutorial on that.
Help-
Any idea what would cause sharepoint's doc library's tree view navigation to break?
What-
We have a sharepoint site that uses the template Document Center to hold all of our docs. In the master page of the site there is a site hierarchy showing a tree view for all the folders in the document library. When clicking on the folders from the tree view we get a 404 error but navigating to the folder from the document viewer webpart on the child page works fine.
When-
The issue started yesterday when my boss was playing around w/ the appearance of the document library web part's Chrome type trying to add a link to the top to get better breadcrumb navigation when using the folder links in the webpart.
Example:
Clicking on the root folder of the document library named "Documents" goes to this url w/ a 404 Error:
http://portal.domain.net/firmdocs/Documents
Go here we get a listing of the items:
http://portal.domain.net/firmdocs/Documents/Forms/AllItems.aspx
What did I try
We didn't change the name of the doc library recently
I am going to do an IIS reset tonight
Tried changing the chrome type back to what it was w/ no luck.
Checked the master page and child page back up versions from a few months ago and no luck. Also the current fiels have not been edited anytime soon.
Did you modify any of the views for the DocLibray? It could be a link to an invalid view.
This usually happens when the original ListViewWebPart in the view is tampered with in some way.
Check to make sure your boss hadn't accidentally closed the original ListViewWebPart in AllItems.aspx
To do that, navigate to http://portal.domain.net/firmdocs/Documents/Forms/AllItems.aspx?contents=1 (the ?contents=1 is the important part)
You should see only one ListViewWebPart in that list.
The other thing you can try is opening AllItems.aspx in SharePoint designer. Make any change to the page (insert a space in the markup, for example) and save it, clicking yes on the prompt to customize a page from the site definition. Once it's saved, right click on it and "Revert to Site Definition."
Inside SharePoint I've previously created a site template by appending _layouts/savetmpl.aspx to the end of my site and new sites have been created correctly and work as expected.
I've now come to do the same thing again and yet this time the new site is throwing an error relating to the page layout.
The error is:
This page is not using a valid page layout. To correct the problem, edit page settings and select a valid page layout.
When I try to select a different one, there is only the one to select. This page layout is in use on other sites and they render fine.
Has anyone else seen this issue?
All the best
First, if you append the _layouts/savetmpl.aspx tho the url, i suppose you dont have it in the Site Settings options, so you are using a Publishing site. This is because Microsoft doesn´t support this option (save as template in publishing sites). And they dont support it because it has some bugs, for sure.
So, I would recommend not using this option in important sites, or if you plan to ask support to Microsoft in the future.
However that error indicates that the page layout or his associated content type (ou parent content types) are not correctly installed in the site collection. Are you using your own (custom) content types? Please confirm if the ID of the associated content type (something like 0x0100C6739B7D12DE419aA2F9A2F96CC26818) is exactly the same in the Page Layout on working sites and in the not working sites.
Hope it helps
Do the sites/site collection where the templates working have all the same features enabled as teh sites/site collection where the template isn't working?
Can you check the server logs? <12 hive>\LOGS
Did you add a custom page layout, use it, and then forget to check that "save content" checkbox when you saved your template?