Random partials in my projects, but they are not mine!

For a while now, I can find a couple of partials in my projects who are clearly not mine. They belong to someone else’ project (one is if a a swiss school with contact details, two of them something with data replacement) and do add some ressources to my projects (images).
I can delete them, but after reopeing the project, they are back.

How do I get rid of them?
Where do they come frome (could they be part of a stacks bundle?)

@isaiah: a bit of insight would be great :wink:

CleanShot 2021-12-18 at 15.16.15

(One of the pages is still online and made with Stacks and Foundry)

I’ve got Standard Detail and Standard List in my partials, too. No idea where they came from! :man_shrugging:

This issue has been discussed before. The consensus was that this was a Stacks and/or possibly RW problem.

I also would like to hear from @isaiah for some useful info on this issue.

I am in similar situation, only in my case, I get a bunch of externals that came with sample projects I have acquired from 3rd parties and then, they persist in any of my own projects that I base on those sample projects (copy/paste). Also some images, even though I do not use Resources. They come back after I delete them from projects.

1 Like

That’s a different topic.
This partials are not mine! They do belong to someone else projects. Set aside that I can’t delete them, they have come onto my system (and apparently others too) perhaps with stacks or themes?

I also have two Partials that show up on some projects that aren’t mine.

  • Standard Detail
  • Standard List

Looking at them with the inspector, they look to be from Poster 2:

Don’t know why they show up even on projects that don’t have Poster 2 in use. Jannis @instacks, are these yours? @isaiah, Why do they show up and why can’t we delete them.

Correct, these have been once in the Poster 2 demo project. Don’t know why they appear then always in every open project.

1 Like

So that explains where these two came from, I would imagine @dripple that the others you have seen are similar, from a demo project file.

So the real question is for @isaiah then, why do they show up in non related projects?

…and how do we delete them (including the assets, who are randomly in the projects)

I just double checked with @instacks, it looks like that my 4 partials have 3 different sources.

That’s a great question, why they don’t delete and why do they randomly appear on projects.

Unfortunately, the only person that can answer these questions is @isaiah, who other than posts about Black Friday sales has been basically M.I.A. Since last May.


Why do they appear

The why stems primarily from Stacks being a plug-in. As a plug-in there are a lot of limitations to how/when we save information to the project file. Sometimes the perfect solution is simply not possible – so we have to choose a solution that’s imperfect, but still safely saves all the project data.
Currently a partial, external, or template that is active when a project file is saved, is saved with that project file. This is an imperfect solution that ensures no data is ever lost.
But it has a side effect: when two project files are open at the same time the partials from one project file can migrate to the other. This has no impact on the published website, of course – but the library latches on to any partials it can find. The net effect is that a project file can increase in size, sometimes quite a bit.
Fixing this perfectly requires a little bit more information about the project when things are being saved than we currently have today. Currently there’s nothing like that in the RapidWeaver API and I don’t really expect there to be any changes on this front.
But there are things in the works. It requires that I really change the foundations of to the way partials work – so these aren’t small things. But I think that it may improve the situation quite a bit.

How to remove unwanted partials

  1. Open just the one project that you want to remove partials from (to make sure other partials aren’t going to jump across again). If other projects have been open already – or auto open when you start RapidWeaver then just close them, Quit RW and then start a new session from scratch.
  2. Make sure you’re not using the partial anywhere in your project. If Stacks finds the partial somewhere else in your project, then a “removed” partial will just be hidden for your current session, rather than removed permanently.
  3. Select the partials in the Stacks Library. You can use shift-click and/or command-click to select many items.
  4. Choose Remove from Library from the gear menu (or Ctrl-Click and choose it from the pop-up menu).
  5. Choose Remove from the pop-up warning.
  6. Save the document. Quit RapidWeaver.

About that warning message

I’ve reworded the pop-up warning message a few times. I think another rewording is still in order – if anyone has suggestions for a short explanation that somehow encapsulates all the info I’ve just written about above, in just a sentence or two, let me know in the comments. I’d be really happy for good suggestions.

The warning currently says, “This will remove the partial from the library but not from your document.”

I guess what I’m trying to get across to users is that if you want the partial to go away permanently, you’ll have to stop using it completely, everywhere within your document BEFORE you remove it from the library. The “Remove from Library” doesn’t ever change your document (and currently can’t – more API limitations, I’m afraid).

Last details

I should note that most of these limitations didn’t exist when Partials were first added to Stacks. RW 7 documents worked quite differently and pages loaded differently. In those days partials did not jump from document to document and removing a partial from the library would ask if you wanted to remove it everywhere in the document. The RW7.5 changes to document loading offered some great improvements, it means only loading the part of the document you’re working on – but they had some serious side effects too, especially for Stacks and things like partials/globals/etc that are designed to work across pages and be part of the document as a whole. Of course I made many pleading requests for tweaks or changes that might allow things to continue working as designed – but, well… here we are.

@isaiah, who other than posts about Black Friday sales has been basically M.I.A. Since last May.

I am still around. I’m working on the next big Stacks release. I’m keeping quiet, but if you have questions I can still be found in the usual places – or well, the usual places other than here.

There are reasons that I don’t hang around the forum anymore. I think many who have followed Stacks over the years can probably read between the lines and know what’s what. Don’t worry, this isn’t about you folks here. But I think that’s probably all I should really say.
I’d be happy to talk more about this in private with anyone that’s curious. You can always hit me up in a Twitter Direct Message or on the Stacks Slack channel.

I do pop in on occasion and answer a question when someone asks me to – but it’s probably best if that’s a limited thing. I hope you understand.

I think in the future I may try to run a Stacks specific server – something that’s community run, so that all developers feel welcome and anyone is free to ask questions, even before they’ve purchased anything. But that’s for another day.


This makes sense, but doesn’t explain why my project(s) do have partials from people and projects I don’t know!
I have two partials from @instacks, but never ever used the Poster 2 demo (or others) and two other partials from something swiss. There is no way I could have this project open at the same time, because I don’t own them.
Following your explanation, It could be that I have had a project open (demo file) that was already “suffering” from this contamination and I inherited thm?

This doesn’t work. Me (and others) tried it so many times. As this partials do not belong to any project of mine, they are obviosly not used in any of my projects and they will re-appear after launch.

Happy to share a “affected” file :wink:


1 Like

@isaiah : “This will remove the partial from the library but not from your document.” I’m not sure users will understand your meaning of “document.” I’m not aware that I create any “document” through my use of Rapid Weaver. Is your use of the word “document” here synonymous with RW “Project”? If so, perhaps that’s the terminology to use.

1 Like

It’s a common wording for Mac (and Windows app) to talk about Documents, but you’re right: RW calls it a Project.

1 Like

I think “document” is fine. The only piece I was missing was the need to have only one project open at a time when deleting the partials. I’ve been deleting the same damn 60 templates from my projects repeatedly for a year now, and it wasn’t until that tidbit in this thread, that I succeeded in ridding myself of them. Well, fingers crossed, anyway.

Add: “When deleting partials, make sure that no other projects are open, or the partials will not be permanently deleted.” That would have saved me tons of frustration.

As to the OP’s original question, I think this whole imperfect saving system that Issiah described makes it SUPER easy to accidentally add any number of partials to your library if you launch any demo or other person’s project while one of yours is open. I wouldn’t worry about that part of it, as long as you can delete them (fingers still crossed!).

Well, doesn’t work for me. I can’t delete them permanently. After saving, closing the project (and closing RW) and reopening the project, they appear again.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.