175 reputation
110
bio website
location Ottawa, Canada
age
visits member for 2 years, 10 months
seen Apr 16 at 19:49

Sharepoint Software Engineer and Consultant Ottawa, Ontario.


Mar
19
comment Why does SP2013 “Add a Page” place the page in parent site instead of current subsite?
If I keep the subsites from inheriting Managed Metadata navigation (or switch of Managed Metadata navigation entirely), I get more or less what I want. Part of the problem is that the "Find it at ..." field is calculated on the client. Although there's a way of changing the destination in an event receiver, there's no easy way of updating this field. More than anything else, it's this field that's supposed to give the customer visual confirmation of where the page is supposed to go.
Mar
19
comment Why does SP2013 “Add a Page” place the page in parent site instead of current subsite?
Hmmm ... just enabling Managed Metadata navigation - regardless of site/subsite structure - causes this to happen. There doesn't seem to be an easy way to influence this, short of switching off Managed Metadata navigation.
Mar
18
comment Why does SP2013 “Add a Page” place the page in parent site instead of current subsite?
I am using Managed Metadata navigation, but there's a real subsite structure behind it (thanks to a few intractable mistakes put in play before I arrived, but that's a longer story). I wonder if that has a bearing on what's happening.
Mar
18
comment Why does SP2013 “Add a Page” place the page in parent site instead of current subsite?
Cameron: no, it doesn't. It gives me the url to the parent site collection.
Mar
18
comment Why does SP2013 “Add a Page” place the page in parent site instead of current subsite?
Robert: yes, I'm absolutely sure. I navigate to the subsite, then try to add the page.
Mar
18
comment Add Publishing Pages to specfic subsites programmatically in FeatureReceiver
Hmmm ... I'd like to see it too, since I have to solve this exact problem. TIA, Josh
Mar
7
comment Best Approach for using folders in Pages in Publishing site SharePoint 2013
Custom Layouts - a couple of master pages with two or three layouts each. But far as I can tell, I can't find a way to customize the look of the page I get from "Add A Page" unless I write a custom action to override the command.
Mar
6
comment Best Approach for using folders in Pages in Publishing site SharePoint 2013
sween_sp, I was able to import the same taxonomy set to two differently-named term groups: not very elegant, but functional. But I'm still confused as to whether I need to just add a taxonomy field to the Page or modify the actual Page content type in order for the Content Organizer to recognize it, and I can't find an easy way to make it appear right under the user's nose.
Mar
5
comment Best Approach for using folders in Pages in Publishing site SharePoint 2013
"Hierarchy" is a better word for it, I guess: categories, sub-categories and sub-sub-categories, etc. Consequently there aren't really any interdependencies, although the hierarchical view of things is ingrained.
Mar
5
comment Best Approach for using folders in Pages in Publishing site SharePoint 2013
Hmmm ... Perhaps I didn't understand this correctly. It looks like I can't just add a custom property to the Pages library -- the Content Organizer seems to want it as a part of the actual Page content type. The other problem is that the property is not front and centre when I add the page -- it's hidden (so to speak) in the Page Properties dropdown, and I'm not sure the customer would remember to fill it in. Is there a way to add it to the New Page dialog? What I'm looking for, of course, is a way to make this foolproof.
Mar
4
comment Best Approach for using folders in Pages in Publishing site SharePoint 2013
Well, there's one drawback - you can't use a term set that's already used for Site Navigation. Grrr
Mar
4
comment Best Approach for using folders in Pages in Publishing site SharePoint 2013
Oops ... the questions are: (a) are edited pages considered to be "uploaded" (I imagine they are, otherwise they wouldn't work this way, but I'd rather be on the safe side and ask anyway)? (b) do you simply add the property to the page library itself? It sounds too good to be true. Have you found any drawbacks to this scheme?
Mar
4
comment Best Approach for using folders in Pages in Publishing site SharePoint 2013
What a nugget! I'd better temper my enthusiasm with a couple of questions: Thanks very much for this.
Mar
4
comment Best Approach for using folders in Pages in Publishing site SharePoint 2013
Does this help? Yes, very much, except for one thing: the organization has three levels of classification. By constructing content types in the page library, I'd be effectively flattening that down to one and probably making it unacceptably long. But it's an approach that I think I may turn to somewhere down the road. Thanks.
Jan
7
comment Is there a setting that determines the default root folder of a freshly-created SPList?
Absolutely. The codebase is exactly the same in both the before and after situations. And I'm positive that document libraries get created in Lists/
Nov
23
comment how do site collection administrators get to see items for a targeted audience?
PirateEric: Adding an SCA group with no extra permissions is quite elegant. Better yet, if this were made into an AD group, it would always be kept up to date. Thanks very much.
Nov
22
comment how do site collection administrators get to see items for a targeted audience?
I don't see the relevance of your question, sorry.
Nov
7
comment How to make minimal changes to a master page to accommodate custom CSS
Remko, it looks like the Delegate control is the path of least resistance, even though the requisite user control has to be in the 14 hive CONTROLTEMPLATES folder. Thanks, Josh
Nov
7
comment How to make minimal changes to a master page to accommodate custom CSS
Evgeny, the CSS-only limitation is a show-stopper for me 8-(
Nov
7
comment How to make minimal changes to a master page to accommodate custom CSS
Robert, from what I can tell so far, the code requirement is not too onerous. The user control still needs to live in the 14 hive, which will hopefully not be too objectionable to said risk-averse department. Thanks, Josh