SharePoint by default has two master pages: Seattle and Oslo. The general rule is we should not modify these default master pages. If we need any customization, we should make their copy, make modification, upload to the Master Page Gallery and then use it. However a colleague of mine modified them directly and it screwed up some JavaScript functions. It impacted Performance Point Dashboard Designer and continuously started showing JavaScript errors.
In order to resolve the issue, I renamed the default master pages to Seattle_erroneous.masterpage and Oslo_erroneous.masterpage. I also renamed their respective .html files. I copied fresh copies of Seattle.masterpage and Oslo.masterpage from another web application, also their .html files, uploaded them to the Master Page Gallery, published their major version and started them referencing in subsites. It did solve JavaScript errors.
Now I want to clean up those erroneous master pages. When I try to delete them from the gallery, I get following error.
All the subsites inherit the working master page. Also I checked master page of each site one by one. All of them were referencing the working version. There was one site whose SharePoint Server Publishing feature was not enabled. I enabled it, and confirmed it was using the working version. I cannot delete the erroneous masterpages. It is referencing somewhere where I cannot see. Please help.
You may try the solution shared by here.
My Issues with Test.html and Test.master
Go to Root Site, Site Settings->Look and Feel Section: Design
Manager. Here the Master Page Html file can be modified
what changes are we make in .master file.
But Site Settings->Look and Feel Section: Design Manager ->Edit
Master Pages Test.html was missing.(By default Seattle and Oslo will
be appear)
Open the site collection through SharePoint Designer, Right click on
Seattle.html file -> Select "Edit File in Advanced Mode" from
context menu.
Seattle.html opens in a new Tab. Select all and copy the code.
Then Go to Test.html (Right Click) -> "Edit File in Advanced Mode".
Opens in a new tab.
Replace the existing code in the "Test.html" by pasting the code
from Seattle.html
Save the file (This is done in "Check In" status)
In the Browser, Go
To Root Site, Site Settings -> Look and Feel: Design Manager ->
"Edit Master Pages" in the left side.
Now here the Test.html file will appear. Delete this file
Related
We are using Siebel citizen portal application (IP 15.12). After login, we reach in to a landing page with 3 applets. These applets have some custom fields etc, but there is no UI customization we did (ie no PM/PR etc).
Now when we login, a blank layout of the applet appears for a few seconds (especially first load or after clearing cache) and then renders the original applet with Open UI layout. Since this is a customer facing application, our client has a lot of concern on appearing the blank layout before the actual rendered applet.
Could anyone throw some light here? Is this an Open UI behavior, if so is there any workaround for this?
With IP 15.18, We had similar issue of the list applets not loading data on initial (home page load) after login. Only the list applet titles were displayed but the form applet loaded elements, showing the busy cursor forever...
We were getting "Error downloading file define:siebel/htmltmplmgr" error in the browser console. we debugged and found that the localeobject.js was not loading, which is the dependency file mentioned in htmltmplmgr.js...So we added preload define parameter in the htmltmplmgr.js in the beginning to load the localeobject.js file before even the main function starts...then it started working...try this...
On first load or after clear cahce, it needs to load all JS files (vanilla) and other required files in Open UI. So, this is the default behavior of OpenUI.
Nothing much we can do with this. Else you can tweak down all unnecessary files from downloading.
I found this blog very useful, you can check.
http://www.askmesiebel.com/category/siebel-8-1-1-10-upgrade-issue/
edit the file htmltmplmgr.js in below folders
$SIEBEL_ROOT/siebsrvr/webmaster/siebel_build/scripts/siebel/
$SIEBEL_ROOT/SWEApp/public/enu/23048/scripts/siebel/
go to define section and add dependency files inside the square brackets
define("siebel/htmltmplmgr",[]
define("siebel/htmltmplmgr",["siebel/siebelconstants.js","siebel/localeobject.js"]
Note that you have to edit the files in both folders you can create a backup before making changes. If you just replace in public folder when you restart siebel server files will be overwritten from webmaster/siebel_build folder to public folder . Hence you have to replace in both folders and restart siebel server and web server.
I have added 2 pages in the content tree - index & Home Page. It was working fine until yesterday. Unable to preview 'index' in the Content editor (CE) now.
The error message is -
The requested document was not found
However, when I do Tools > Browse > Preview, from Sitecore Rocks, it opens fine. Also, I am able to preview 'Home Page' in CE without issue.
Following Mike's Solution Here, I tried to add the user 'Everyone' and removing 'extranet/Anonymous'. But the changes never Save.
Why does it happen to this page alone. No changes made to web.config and I am using only master DB.
UPDATE:
Here is what I have observed.
When 'index' is placed outside the 'en' folder, it can be previewed. Someone suggested that Sitecore is confused by the folder name with its languages. But renaming it to Test-en, also did not work.
I also tried this. Created 'index' outside 'en' folder. Then created a copy of the same inside the 'en' with the name 'index1'. I can preview index1 now, but if 'index' is deleted, it's the same issue again.
I have seen this happen a few times. On a new instance, I don't believe it is permissions, especially if you are using SIM to install (if you aren't - try it!)
Follow these steps and it should fix your issue. Make sure all instances of your browser are closed. They are known to keep hidden instances running. Stop all those tasks. Restart your IIS instance. Log Into your sitecore site with the magical password. Preview the page. You should be able to preview and in fact get the Experience Editor.
I do agree that Sitecore is confused as to the state of that it is logged in as, that is why it is important to close all browser instances.
If you still get this error, clear your logs. Do the above steps and send me your logs. I will look at them for any oddities.
Happy Sitecoring!
When we upgraded from Sharepoint 2010 to Sharepoint 2013, our favicon was no longer being displayed. An internet search offered a couple of solutions. One method suggested placing the file in C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\IMAGES and performing an IIS reset.
Not having access to the server and not wanting to disrupt a production site with an IIS reset, I opted to handle this with an upload to a site library and master page change.
I found the following to be an easy change to make.
These are the steps I took:
Upload your .ico file to your site / siteassets library
Make note of the URL to the uploaded .ico file (right click and choose copy shortcut from the menu
In Sharepoint Designer, open your master page file - v4.master or your custom file
Search for this line: SharePoint:SPShortcutIcon.. (if you have a custom master page and this line is missing, copy it from v4.master and place it in the head section.)
Paste the URL of your .ico file from step two into the SPShortcutIcon element on the IconUrl property
Save, checkin, and approve your master page. That's it. Your .ico file will appear in browser tabs and in the URL address bar depending on your browser. If using IE, you may need to clear your cache to get it to display.
Here's the scenario:
Fresh install of Open Cart. Fresh install of vQmod. Everything is working fine. But when I upload certain theme - purchased and licensed - the site has an issue. The home page is working, but the product page goes blank.
I have tried all possible combinations of OpenCart and vQmod versions (except for 2.0 for OC because the theme doesn't support it yet). I am out of ideas.
Edit: After showing all errors as adviced I finally saw the reason : "oc_product_tab' doesn't exist"
I found a solution. It turned out that the "Extra Product Tabs Opencart Extension" is missing. This is a standart free plugin that comes with template theme but it wasn't configured. It turnes out that the theme works with it.
Go to system>users>user groups and select all for both access and modify. Save. Than go to Catalog menu and click on Extra product tabs. Click Insert and add the module. That’s it. It’s a standard opencart module which is free for use.
I am a new bee to Sitecore and here comes my first challenge at work.
In one of the website component, I want to add an image.
For this in content editor:
I'll click on browse.
Switch to folder view.
Navigate down to the folder you want to save into.
Click upload media on top left.
Click ‘Browse for media files’ and navigate to the image on the local drive and select it.
Enter alt-text and click upload media.
In Chrome the green bar for uploading never seems to finish. On IE one of the green bars changes to ‘Upload complete’. At this point there is no call to action to add the image to the module, select the module – you just don’t know what to do next.
Eventually you have to click ‘Back’ or ‘close’. Then when you go to find the image it is not in the folder you selected. It is in Upload folder. We cannot keep all of our files in ‘Upload’. We need to be able to upload into a chosen folder.
I am using Sitecore 7.2.
This works properly in a base site in Sitecore 7.2, but is not working in my website.
Is there any setting I need to change to make this work properly?
I know we can add media files into Media library directly and can use it. But we want to do it the using the above mentioned steps/ or using Page editor. The main problem is, this doesn't work while adding image from Page editor.
Hope I can get some solution!
many thanks!
I looked at the Release Notes for Sitecore 7.2 and found that there were several bugs related to Media Uploads that were resolved in Update 2 (140526), including some that relate to choosing the destination of uploaded media. From your description of the issue and the bugs that were fixed in Update 2, it sounds like you may only need to update to Revision 140526.
To find out what revision of Sitecore you are using, go to the Sitecore Desktop -> Start Menu -> Control Panel -> Administration -> Show About Sitecore Information. As you will see in the screenshot, below, there is a parenthesized revision number at the top. If that number is not 140526 then you should try to apply Update 2 to your instance.
Note that this screenshot is of an instance that is not running on Sitecore 7.2 Update 2, but is instead running on the initial release (140228).