Hot answers tagged

2

Everything looks like it is working properly in your code, you are getting the data and manipulating the DOM. So that leaves why are you are seeing the results you are. That is because you are doing $('#postBody').text(curBody); instead of $('#postBody').html(curBody);. This is taking your data and making it raw text. Use the .html to make it literal html ...


1

Rather than a timer job which "touches" all the items, consider using jsLink or other client side rendering techniques to calculate the value in real time. Of course, it depends on how you are using the values, which you don't indicate.


1

Unfortunately, this isn't possible since Calculated Columns are not recalculated on viewing, but only on creation and modification. See this article: http://blog.pentalogic.net/2008/11/truth-about-using-today-in-calculated-columns/ You will need to solve this with display logic.


1

You can do this SPServices. The $().SPServices.SPArrangeChoices method lets you define how many to put in a row.


1

I have found that the Crawler Impact rules can help with this issue. Try setting them to request 6 documents at a time for each web application. Stop all crawls. Reboot the non-responding server and retry your crawl. You can increase the documents requested until you reach the break point again.



Only top voted, non community-wiki answers of a minimum length are eligible