Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Web part

  Asked By: Garrett    Date: Jul 24    Category: Sharepoint    Views: 810

I know that we all appreciate the help given in this forum..
I personally want to thank everyone who has helped me in my SharePoint
battles.

I do have another question however..
I have created a project site template..In this template is a document
library which has a column entitled "Document type." This is a choice
field which has as choices: planning, implementing, testing, etc..(you
get the idea)
On the home page of the site, are list view web parts with filters to
only show documents of each type (where column type = "plannning")
When I save the template and then create a site off of this template,
the list view web parts revert back to default and show all the
documents in the library and not what they were initially filtering.
In addition, they also show the full toolbar and not the summary
toolbar is was initially configured in the web part.

Does anyone have any ideas as to why these web parts "lose" their
initial settings and revert back to default?

Share: 

 

24 Answers Found

 
Answer #1    Answered By: Faith Delgado     Answered On: Jul 24

The Web Part settings  should be retained; I'll bet this is a bug.

 
Answer #2    Answered By: Iris Ballard     Answered On: Jul 24

It must be..because I know it has worked in the past..

Its very strange..once in a while I will be working in a web  part and
change a setting, then another, then the first setting reverts back  to
its original state..

Very strange..

 
Answer #3    Answered By: Selena Glenn     Answered On: Jul 24

All the WSS v3 betas had problems with Personalization. They only worked
it out in the RTM.

 
Answer #4    Answered By: Kalpana Ghatge     Answered On: Jul 24

I am in RTM......................

 
Answer #5    Answered By: Bobbie Rodgers     Answered On: Jul 24

Just a thought. When you created  the custom views in the original
site, were you careful to make sure they were shared views and that you
were modifying the shared page  as administrator rather than the private
view?

 
Answer #6    Answered By: Bhumi Gokhale     Answered On: Jul 24

Is there a way to change it to a shared view  in case I had accidentally
created it as a private view?

And, I just thought of this..even if it was a private view I had
created, I am still logged in as me when I test the template, and it
still reverts back  to default  settings..

But I am still looking back into the view..

 
Answer #7    Answered By: Vinay Thakur     Answered On: Jul 24

But that's why I was asking about the shared vs. personal view. Save
Site as Template doesn't save  any of the personal views, just the shared
ones. That is by design. When a new site  is created  everyone starts
off with the shared view  and customizes from there.

I don't think there is a way to change a personal view back  to a shared
view.

On another note. Did you save the site with our without content?

 
Answer #8    Answered By: Aakash Gavade     Answered On: Jul 24

I tried it both ways, with and without content..

I noticed the problem when I had the same word doc show  up in each
view..

Its quite frustrating..I don't want to have to resort to creating a
separate library  for each piece of metadata..

 
Answer #9    Answered By: Dara Hobbs     Answered On: Jul 24

I did some testing  and was able to replicate your problem. I then did
some more digging and found that this is indeed a known issue that MS
created a Hotfix for in February, 2007. Info about the issue and hotfix
can be found here:

support.microsoft.com/Default.aspx?kbid=926284

 
Answer #10    Answered By: Abhinivesh Suvarna     Answered On: Jul 24

There is no link to the actual hotfix there..

Do you know how to go about downloading the hotfix?

 
Answer #11    Answered By: Micheal Knight     Answered On: Jul 24

I've been trying to find it and can't find a download link. You may
have to call Product Support and reference the KB number to get access
to the download. If I find it I'll post a link.

 
Answer #12    Answered By: Yvonne Rodriquez     Answered On: Jul 24

You must always contact CSS (Customer Support Services) to obtain a
hotfix. They will not charge you but you will have to go thru the
process.

 
Answer #13    Answered By: Elisha Abbott     Answered On: Jul 24

How did you find this, so I know where to look next time?

 
Answer #14    Answered By: Naimish Ranganekar     Answered On: Jul 24

I hate to say it, but I just happen to be good (lucky) with Google. I
also subscribe to KBalertz (http://www.kbalertz.com/default.aspx
<http://www.kbalertz.com/default.aspx> ) to try to keep on top of these
kinds of issues.

 
Answer #15    Answered By: Caleb Gordon     Answered On: Jul 24

I am having all kinds of problems finding the download for the hotfix..

But thank you so much for all of your efforts. I will look a little
longer then will have to call Microsoft.

 
Answer #16    Answered By: Christie Carlson     Answered On: Jul 24

As a workaround, if you transform the we part  to a XSLT DataView web  part ,the
settings are retained in the .stp template

 
Answer #17    Answered By: Dorothy Farmer     Answered On: Jul 24

but I am not a developer, how would one do that?

 
Answer #18    Answered By: Jacklyn Burnett     Answered On: Jul 24

You don't need to be a developer. Pull the site  up in SharePoint
Designer. Open the default.aspx page  where you added the webparts.
Make sure they are currently set to the correct view. Then as I
remember right click on each webpart and there should be an option to
convert to a Data View. Select that option on each of your custom view
webparts. Then close and save  the page. Close Designer, navigate to
the page, and save the site as a template.

 
Answer #19    Answered By: Breann Beach     Answered On: Jul 24

Open the web  page with SharePoint Designer, right click on the web part  that you
have customized with the web browser and select Convert to XSLT dataview.

Save the site  as template, changes will be retained. This is just a workaround.
Getting the hotfix will solve the problem you had in the first place.

 
Answer #20    Answered By: Timothy Hall     Answered On: Jul 24

It was discovered by someone here that the hotfix had been pulled by
Microsoft..

Does anyone have any information about it?

 
Answer #21    Answered By: Ian Powell     Answered On: Jul 24

I called Microsoft today to try to obtain this hot fix, but the
attendant said that she couldn't find it. She then promptly asked me if
I wanted to open a ticket with an engineer, which of course, isn't
free. I decided to wait on that option.

 
Answer #22    Answered By: Osvaldo Winters     Answered On: Jul 24

It's probably a good idea to wait on opening that ticket with Microsoft.
I've found that if you have a non-ordinary issue, they tend to have a
VERY difficult time resolving the case. Just this morning they had to
admin to me that they didn't know what the issue was and refund the
support instance to me! Of course, I'd rather then have solved the
issue...

Right now MS MOSS 2007 support isn't great.

 
Answer #23    Answered By: Kylie Gill     Answered On: Jul 24

I think you are right and wise! If there is a work-around, I
will use that for now and then wait for a service pack to
correct the issue later.

A special thanks to Harry for bringing the issue to our attention! I
would have gone insane trying to figure out why that was happening.
Now I will avoid that frustrtion altogether.

 
Answer #24    Answered By: Irving Hurley     Answered On: Jul 24

I understand, but I was trying to say that there are probably still
remnant bugs.

 
Didn't find what you were looking for? Find more on Web part Or get search suggestion and latest updates.




Tagged: