<ExecuteUrl> in ONET.XML not firing

[Coolpran]

Hi,

Our application consists of Project Server 2003 with WSS.
I have created a new configuration in the ONET.XML file and added an
<ExecuteUrl> element which points to a custom aspx page.
This custom page will be used to reconfigure some security settings among
other things.

I then create a site by going to the SharePoint Central Administration and
creating a top-level site.
When I go to the site and apply the template which I created above, the
custom page is executed.

However, when I create a new site (via PWA Admin or via Project Professional
client) this aspx page is not called.

Is it a known issue/limitation?
I found a reference that says so[1] but nothing in Microsoft documentation
about it.

Is there any other means of executing a custom page whenever a new project
is published?

Regards
Coolpran

P.S. I have posted to multiple newsgroups because I can't decide the exact
category this belongs to. Newsgroup police, please forgive me.

[1] http://dotnet.sys-con.com/read/48162_3.htm

 

[Daniel Larson]

ExecuteUrl doesn't work when you create the page from SPS-- it only works
with WSS site creation.

 

[Coolpran]

I am using WSS, not SPS.
And the site is created automatically by Project Client when a new project
is published.

Is there another way to execute custom scripts after creating a site
automatically from PWA or Project client?

ExecuteUrl doesn't work when you create the page from SPS-- it only works
with WSS site creation.
--
Daniel Larson
http://feeds.feedburner.com/daniellarson
http://www.portalbuilder.org

Hi,

Our application consists of Project Server 2003 with WSS.
I have created a new configuration in the ONET.XML file and added an
<ExecuteUrl> element which points to a custom aspx page.
This custom page will be used to reconfigure some security settings among
other things.

I then create a site by going to the SharePoint Central Administration
and
creating a top-level site.
When I go to the site and apply the template which I created above, the
custom page is executed.

However, when I create a new site (via PWA Admin or via Project
Professional
client) this aspx page is not called.

Is it a known issue/limitation?
I found a reference that says so[1] but nothing in Microsoft
documentation
about it.

Is there any other means of executing a custom page whenever a new
project
is published?

Regards
Coolpran

P.S. I have posted to multiple newsgroups because I can't decide the
exact
category this belongs to. Newsgroup police, please forgive me.

[1] http://dotnet.sys-con.com/read/48162_3.htm

 

[Daniel Larson]

That makes sense-- and that's why you're not getting ExecuteUrl to work.
ExecuteUrl ONLY works from sites created from the WSS web front-end
(/_layouts/1033/newsbweb.aspx) . ExecuteUrl doesn't work for sites created
with STSADM either. So, for your Project-created sites (as well as your Team
Foundation Server created sites) you'll have to come up with another
solution.

One idea is to use a WebControl that works with properties of the SPWeb
object. SPWeb has a property bag that you can store arbitrary properties in,
and you can create a property like "Initialized" and check if it's null. If
it's null and the user is an admin, redirect the response to the setup page.

Does that make sense? Let me know if you get stuck with that. I've actually
done something very similar on a previous project, where we had to call some
post-setup web services on an uninitialized SPS Area.
--
Daniel Larson
http://feeds.feedburner.com/daniellarson
http://www.portalbuilder.org

I am using WSS, not SPS.
And the site is created automatically by Project Client when a new project
is published.

Is there another way to execute custom scripts after creating a site
automatically from PWA or Project client?

ExecuteUrl doesn't work when you create the page from SPS-- it only works
with WSS site creation.
--
Daniel Larson
http://feeds.feedburner.com/daniellarson
http://www.portalbuilder.org

Hi,

Our application consists of Project Server 2003 with WSS.
I have created a new configuration in the ONET.XML file and added an
<ExecuteUrl> element which points to a custom aspx page.
This custom page will be used to reconfigure some security settings among
other things.

I then create a site by going to the SharePoint Central Administration
and
creating a top-level site.
When I go to the site and apply the template which I created above, the
custom page is executed.

However, when I create a new site (via PWA Admin or via Project
Professional
client) this aspx page is not called.

Is it a known issue/limitation?
I found a reference that says so[1] but nothing in Microsoft
documentation
about it.

Is there any other means of executing a custom page whenever a new
project
is published?

Regards
Coolpran

P.S. I have posted to multiple newsgroups because I can't decide the
exact
category this belongs to. Newsgroup police, please forgive me.

[1] http://dotnet.sys-con.com/read/48162_3.htm

 

[Coolpran]

Daniel,

Your solution sounds promising. Could you elaborate please.

Do you have a pseudo-code which does similar thing?

Do I need to add this webcontrol to the default.aspx?
If I add this webcontrol to default.aspx, won't it be visible to everyone?

That makes sense-- and that's why you're not getting ExecuteUrl to work.
ExecuteUrl ONLY works from sites created from the WSS web front-end
(/_layouts/1033/newsbweb.aspx) . ExecuteUrl doesn't work for sites created
with STSADM either. So, for your Project-created sites (as well as your Team
Foundation Server created sites) you'll have to come up with another
solution.

One idea is to use a WebControl that works with properties of the SPWeb
object. SPWeb has a property bag that you can store arbitrary properties in,
and you can create a property like "Initialized" and check if it's null. If
it's null and the user is an admin, redirect the response to the setup page.

Does that make sense? Let me know if you get stuck with that. I've actually
done something very similar on a previous project, where we had to call some
post-setup web services on an uninitialized SPS Area.
--
Daniel Larson
http://feeds.feedburner.com/daniellarson
http://www.portalbuilder.org

I am using WSS, not SPS.
And the site is created automatically by Project Client when a new project
is published.

Is there another way to execute custom scripts after creating a site
automatically from PWA or Project client?

ExecuteUrl doesn't work when you create the page from SPS-- it only works
with WSS site creation.
--
Daniel Larson
http://feeds.feedburner.com/daniellarson
http://www.portalbuilder.org


:

Hi,

Our application consists of Project Server 2003 with WSS.
I have created a new configuration in the ONET.XML file and added an
<ExecuteUrl> element which points to a custom aspx page.
This custom page will be used to reconfigure some security settings among
other things.

I then create a site by going to the SharePoint Central Administration
and
creating a top-level site.
When I go to the site and apply the template which I created above, the
custom page is executed.

However, when I create a new site (via PWA Admin or via Project
Professional
client) this aspx page is not called.

Is it a known issue/limitation?
I found a reference that says so[1] but nothing in Microsoft
documentation
about it.

Is there any other means of executing a custom page whenever a new
project
is published?

Regards
Coolpran

P.S. I have posted to multiple newsgroups because I can't decide the
exact
category this belongs to. Newsgroup police, please forgive me.

[1] http://dotnet.sys-con.com/read/48162_3.htm