Autheticate in client side code without pop-up in SharePoint 2013 online

 The authentication model has changes. Recently we had a Windows app build for integrating with SharePoint 2010 online stoped working when trying to use it with SharePoint 2013 online.

Many solutions on how to integrate involves a step where the user must enter credentials in a pop-op manually.

But how do you make a system user access a SharePoint 2013 online site without the pop-up?

I just found an excellent blog post on this (the code is wonderfully simple):
http://www.vrdmn.com/2013/01/authenticating-net-client-object-model.html

Promoted Links popup does not work on publishing pages

Today my colleague could not get new Promoted Links webpart to work when setting it to open the links in a dialog popup. Earlier the same day it worked perfectly.

The reason seems to be related to publishing pages. It works on team site pages, but not on publishing pages.

If you debug the site you get the following javascript error:
"Unable to get property 'ShowPopupDialog' of undefined or null reference"

The html a tag generated is the same for the page in SitePages (where it works) and for the page in Pages (where it doesn't work). Eg this is not the issue.

The masterpage is the same (seattle.master). Eg this is not the issue either.

Perhaps the javascript file is loaded in the page layout? Or at least the object containing the ShowPopupDialog is initialized in the pagelayout? (or in case of a master page it it clearly not loaded).

It must of cause be a bug, but unfortunately I haven't found a solution just yet. Next step is to digg into where exactly the SP.UI.ModalDialog object is initialized. Hopefully this will give some answers on why it is null.

Save as template missing

Publishing sites can NOT be saved as a template.
When you enable the publishing feature, the "Save site as temple" will disapear.

Query SharePoint 2013 (on-premise, online, 365) list WITHOUT any code deployment

As a consultant you often get a task where you need to make some shiny and neat functionality to an existing site. But you are not allowed to make code-solution or there is simply no budget for that. What to do...?

In SharePoint 2013 many of these tasks can be done with out-of-the-box webparts, some JavaScript and CSS.

Lately I had customer who wanted two dropdown boxes on a list form to be related. If you choose the option "Fruits" in dropdown box one, you should only be able to select fruits in dropdown box two:

[PICTURE]

In short

So what I basically did was to call the rest webservices to query a list with all the fruits, vegetables and other choices for the drop down with a ajax call from jQuery. I put all this "code" in a Content Editor Web Part and placed it on the "New Form" and "Edit Form" for the list containing the drop down boxes.

Step by step

La la la... (shorthand for: "coming soon")

Run as a diffenrent user account eventhough your computer is not a part of the domain

As a consultant you often need your computer is not a part of your clients domain, however you need to run programs on their servers as a domain account given to you.

"Right-click" -> "Run as" does not work..

But THIS PowerShell command will do the trick:

• runas /netonly /user:domain\username cmd.exe

TIP: How to Run Programs as a Domain User from a Non-domain Computer
Pretend You’re On The Domain With Runas /NetOnly