Cannot make a cache safe URL for “init.js”.

September 19, 2008   11:20


Cannot make a cache safe URL for After a restore on a testing environment I bounced into the IIS error “Cannot make a cache safe URL for “init.js”, file not found. Please verify that the file exists under the layouts directory.”

You can check if the init.js file is no longer located in the layouts folder, but probably nothing is wrong with it.

It turned out that the Dutch Moss language pack was not installed on the server, which was used by the restored web application.

If you ever bump into this error, make sure you have all the required language packs installed. After you fixed that, the site collection will be fine.

Tags: , , .





String resource bug in the colleagues web part?

November 27, 2007   11:58


In one of my projects there is an issue with the colleagues web part. For one of our Dutch customers we are using the Dutch language pack. In combination with the out of the box colleagues web part, the rendering of the Add and Remove colleague links go wrong.

String resource bug in the colleagues web part

Google does not return any meaningful result for this issue. The language resource file: c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\CONFIG\Resources\sps.nl-NL.resx shows the text as:

<div class=”code”>
<data name=”QuickLinks_AddColleague_pagetitle”>
 <value>Collega’s toevoegen</value>
</data>

I thought the ‘ character should be encoded as ' inside a XML file… ???? But any alterations in these files do not reflect back to the current SharePoint environment.

To me it seems that there is an error in the code to render the url. The & character is encoded while it shouldn’t be, also the title of the web part is encoded correctly:

Correct title VS wrong url:
Collega&#39;s VS Collega&amp;#39;s

Does anyone know if this is a known SharePoint bug and if there is a way to fix it?

Tags: , , , , , .









The content expressed in this blog are those of Edwin Vriethoff and do not represent his employer's view in anyway. The contents of this blog has been carefully put together, but Edwin Vriethoff is not responsible in any way for any direct or indirect harm caused by individuals or organizations using the content of this blog in any way.