Property names in graph

[theBenForce]

What happened?

I just upgraded to version 0.7.7 on MacOS and now I see all of my page property names in the graph.

Reproduce the Bug

1. Add the same property to a few different pages
2. Go to 'Graph view'
3. You'll see the name of that property in the graph

Expected Behavior

I shouldn't see page property names in the graph

Screenshots

No response

Desktop Platform Information

MacOS 12.4, Logseq 0.7.7

Mobile Platform Information

No response

Additional Context

There are a few properties that I add to most pages, like type. Since they connect to most pages their node is massive and all of the connections coming out of them make the graph pretty well unusable.

[cnrpman]

There's a config option provided

logseq/templates/config.edn

Lines 215 to 220 in a0087d7

	;; Enable all your properties to have corresponding pages
	:property-pages/enabled? true
	;; Properties to exclude from having property pages
	;; E.g. #{:duration :author}
	;; :property-pages/excludelist

[theBenForce]

Just added this to my config and I'm still seeing property pages after multiple application restarts, refreshes, and re-indexings.

 :property-pages/enabled? false

[Edmund-D]

新

I encountered the same problem

[Edmund-D]

Reproduction: Create new "Properties" → Delete "Properties" page from all pages → Re-create index → Go to "Atlas view"
Environment: win10-x64
Version: 0.7.6+nightly.20220718

[cnrpman]

Just added this to my config and I'm still seeing property pages after multiple application restarts, refreshes, and re-indexings.

 :property-pages/enabled? false

May @cldwalker have a look on this?

[WsinGithub]

With :property-pages/enabled? false, the properties-key can't be clicked anymore. However, the linked references still envolved property-pages.

[cnrpman]

Just added this to my config and I'm still seeing property pages after multiple application restarts, refreshes, and re-indexings.

 :property-pages/enabled? false

Sounds these property key pages are still linked in the linked reference section.
Ideally these pages could be removed via remove orphan pages when the config option is set to false.

[logseq-cldwalker]

@theBenForce Looks like there's a caching issue. You can workaround most of this bug by backing up your data, deleting logseq/pages-metadata.edn and then re-indexing. Your block property pages should then be deleted but page property pages won't be deleted yet. There's a bug with page property pages not respecting the config option so I'll have a fix for that soon
@cnrpman Looks like there's a separate bug where we don't delete pages on re-index if they exist in logseq/pages-metadata.edn Nevermind. Looks like deletion works consistently after two re-indexes

[theBenForce]

Thanks for working on it @logseq-cldwalker!