| bio | website | |
|---|---|---|
| location | Perth, Australia | |
| age | 29 | |
| visits | member for | 1 year, 9 months |
| seen | 2 days ago | |
| stats | profile views | 25 |
Lead SharePoint developer for a major Australian mining company.
|
Mar 11 |
awarded | Popular Question |
|
Jan 23 |
accepted | “Service too busy” exception occurrs when trying to programmatically activate a sandbox feature with an attached feature receiver |
|
Jan 15 |
comment |
Programmatically add publishing page in sandbox solution? I've already got the deletions working fine. However in order to provision the pages again AFTER the existing files have been deleted, it needs to be done programmatically in the feature receiver too. I realise I could use two seperate features (one to delete the files programmatically, and a second feature to declaratively reprovision the pages) -- however that seems a little unecessary! |
|
Jan 14 |
comment |
Programmatically add publishing page in sandbox solution? Hi C. Marius. I already have modules in my solution which deploy publishing pages to all my new sites, however in this particular case I am creating a feature which needs to delete and recreate the pages of an existing site each time it's deactivated and reactivated. Declarative modules do not support this behaviour (which is confirmed at the bottom of Waldek's post that you linked) -- when a feature containing a module is reactivated, the page is never overwritten, instead multiple copies of the web parts are added to the zones / page. So I'm stuck with using a feature receiver... |
|
Jan 14 |
asked | Programmatically add publishing page in sandbox solution? |
|
Jan 3 |
answered | “Service too busy” exception occurrs when trying to programmatically activate a sandbox feature with an attached feature receiver |
|
Jan 3 |
accepted | Custom Content Query Web Part in a Sandbox Solution |
|
Jan 3 |
answered | Custom Content Query Web Part in a Sandbox Solution |
|
Jan 3 |
accepted | Dynamically registering JavaScript from within a sandbox web part |
|
Jan 3 |
answered | Dynamically registering JavaScript from within a sandbox web part |
|
Jan 3 |
comment |
Rich Text fields in New Item Dialog - IE9 I'm not sure you'd ever need two exact copies of the same function on the same page, but in either case, this solution worked great for me without having to overwrite the RTE_GetEditorInstanceVariables() function. Happy days -- thanks Matt :) PS: This, together with your other stack exchange questions on these "random" SharePoint 2010 & IE9 bugs have been the most concise and definitive set of solutions I could find on the net. If you hung them all together in a blog post somewhere, I'm sure it'd be rather popular with other dev folk like myself. |
|
Jan 2 |
comment |
Rich Text fields in New Item Dialog - IE9 Correct me if i'm wrong @Matt, but it doesn't look like there's any difference between the RTE_GetEditorInstanceVariables function you posted here and the OOTB function in form.debug.js |
|
Nov 24 |
awarded | Popular Question |
|
Nov 21 |
comment |
Programmatically find lists by template ID Answer posted... |
|
Nov 21 |
accepted | Programmatically find lists by template ID |
|
Nov 21 |
answered | Programmatically find lists by template ID |
|
Nov 9 |
comment |
Programmatically find lists by template ID Hi Hugh. I ended up just using a foreach loop to iterate through the SPWeb.Lists collection and checking each list's BaseTemplate value to get all the picture and asset libraries. The only reason we went with this approach is because I was able to change the web part requirements so that it just displays a selection of picture libraries in the current site (as apposed to the whole site collection). This is actually a major factor for us as our entire intranet is just a single site collection, and so it contains a few hundred child SPWebs -- and iterating all those could've taken ages! |
|
Nov 6 |
revised |
Programmatically find lists by template ID added 48 characters in body |
|
Nov 6 |
asked | Programmatically find lists by template ID |
|
Nov 5 |
answered | Automatically Activate Feature when subsite created |