Frequently Asked Questions
Common questions about Nexus Properties and their answers.
General Questions
What is Nexus Properties?
Nexus Properties is an Obsidian plugin that automatically manages bidirectional relationships (parent-child, related) and provides an interactive relationship graph to visualize and navigate your knowledge network.
Is it free?
Yes! Nexus Properties is completely free and open source under the MIT license.
Does it work on mobile?
The plugin is currently focused on desktop use. Mobile support is not guaranteed but may work with limitations.
What's the difference between this and Obsidian's built-in graph?
Obsidian's graph shows backlinks. Nexus Properties shows frontmatter-based relationships with automatic bidirectional sync, multiple view modes, color rules, filtering, and zoom previews.
Relationship Management
Why use frontmatter relationships instead of backlinks?
- Explicit structure: Define clear parent-child hierarchies
- Bidirectional sync: Set once, updates both sides automatically
- Typed relationships: Distinguish between parent, child, and related
- Queryable: Filter and search based on relationship properties
Can I use both backlinks and Nexus Properties?
Yes! They complement each other. Use backlinks for general references, Nexus Properties for structured relationships.
What happens if I manually edit relationships in both files?
The plugin will sync them on next file change. However, it's best to let the plugin handle bidirectional sync automatically.
Can I have multiple parents?
By default, a file can have one parent. If you need multiple, you can manually add them, but the plugin is designed for tree hierarchies (single parent).
How do I break a relationship?
- Delete the relationship from one file's frontmatter
- Plugin automatically removes it from the other file
- Or use context menu: Right-click edge → "Remove Relationship"
Graph Features
Why isn't my file showing in the graph?
Check:
- File is in an indexed directory
- File has relationships (
Parent,Child, orRelated) - Filters aren't hiding it
- View mode is appropriate (Hierarchical vs Related)
How do I see all my notes in the graph?
- Switch to "All Related" mode
- Ensure directories are scanned
- Clear any active filters
- Check that notes have relationships
Can I customize the graph layout?
Layout is automatic, but you can:
- Manually drag nodes (positions not saved)
- Adjust view mode for different layouts
- Use filtering to focus on subsets
- Configure animation duration
How do I save the graph as an image?
Use standard screenshot tools (Snipping Tool, macOS screenshots, etc.) to capture the graph view.
Performance
Does the plugin index my entire vault on startup?
Only files in configured directories are indexed. Use specific directories to limit scope.
Color Rules & Filtering
My color rule isn't working. Why?
Check:
- Expression syntax is valid JavaScript
- Property names match exactly (case-sensitive)
- Rule is enabled
- Rule order (first match wins)
- Property exists in frontmatter (use tooltips to verify)
Can I have different colors for different note types?
Yes! Create color rules based on a type property:
type === 'project' // Blue
type === 'task' // Green
type === 'note' // Purple
Learn more about color rules →
How do filters work with view modes?
Filters apply to all view modes. They hide nodes that don't match filter expressions, regardless of Hierarchical/Related/All Related mode.
Can I save filter presets?
Yes! Use Filter Presets to save commonly-used filters with names for quick access.
Node Creation
Where are new nodes created?
New nodes are created in the same folder as the source file.
Can I change where new nodes are created?
Not currently. Future versions may support template folders or configurable locations.
Why is my property not being copied to new nodes?
Check Excluded Properties:
- Property might be in default exclusions
- Property might be in path-based exclusion rule
What is a Zettel ID?
A unique timestamp-based identifier (YYYYMMDDHHmmss) assigned to each new node. Useful for Zettelkasten workflows and ensuring unique node IDs.
Can I disable Zettel ID generation?
Yes! Set the Zettel ID property to an empty string in settings.
Zoom Mode
What's the difference between Zoom Mode and Tooltips?
- Tooltips: Hover for quick property preview
- Zoom Mode: Click for full content preview with navigation
Can I edit notes in Zoom Mode?
No, Zoom Mode is read-only preview. Double-click a node or use context menu → "Open in New Tab" to edit.
How do I exit Zoom Mode?
Click the focused node again, press Escape, or click outside the graph.
Troubleshooting
My relationships aren't syncing. What's wrong?
- Check directory scanning includes both files
- Verify property names are correct
- Use wiki link format:
[[note name]] - Run full rescan to rebuild relationships
The plugin broke after updating. How do I fix it?
- Check compatibility: Ensure Obsidian is version 1.6.0+
- Reload plugin: Settings → Community plugins → Reload
- Restart Obsidian: Close and reopen completely
- Check console:
Ctrl/Cmd+Shift+Ifor error messages - Report issue: GitHub Issues
How do I reset all settings to defaults?
- Close Obsidian
- Navigate to
<vault>/.obsidian/plugins/nexus-properties/ - Delete or rename
data.json - Restart Obsidian
This resets ALL settings including color rules, filters, and exclusions. Export/backup settings first if needed.
Can I export/import settings?
Not directly through the UI. Advanced users can:
- Copy
data.jsonfile between vaults - Manually edit JSON (at your own risk)
Feature Requests & Support
How do I request a feature?
- Check GitHub Discussions for existing requests
- Open a new discussion describing your feature
- Explain use case and benefit
How do I report a bug?
- Check GitHub Issues for duplicates
- Open a new issue with:
- Steps to reproduce
- Expected vs actual behavior
- Obsidian version and plugin version
- Console errors (if any)
Is there a community forum?
Use GitHub Discussions for:
- Questions
- Feature requests
- Use case sharing
- Tips and tricks
How can I support the project?
- ⭐ Star on GitHub: Nexus Properties Repository
- 💰 Sponsor: GitHub Sponsors
- 🐛 Report bugs: Help improve quality
- 📖 Improve docs: Submit documentation PRs
- 💬 Help others: Answer questions in Discussions
Advanced Questions
Can I use this with Dataview?
Yes! Relationships are stored in frontmatter, so Dataview can query them:
LIST
WHERE Parent = [[Project Overview]]
Can I use this with Templater?
Yes! New nodes inherit properties, which can include Templater templates or Templater-created properties.
Does it work with Canvas?
Canvas notes are regular files. If they're in indexed directories with relationships, they'll appear in the graph.
Can I script relationship creation?
Yes, for advanced users:
- Modify frontmatter programmatically
- Plugin will detect changes
- Bidirectional sync happens automatically
Use app.fileManager.processFrontMatter() API.
How does it handle file conflicts?
If two users edit relationships simultaneously (e.g., in synced vaults):
- Last write wins
- May cause temporary inconsistency
- Run full rescan to fix
Migration & Compatibility
Can I migrate from another system?
If your previous system used frontmatter properties:
- Rename properties to match Nexus Properties names
- Run full rescan
- Relationships will be synced
Will it work with my existing notes?
Yes! The plugin:
- Doesn't modify notes without relationships
- Only manages specified properties
- Won't break existing structure
Can I uninstall without breaking my vault?
Yes! Relationships are stored as frontmatter. If you uninstall:
- Frontmatter remains
- Relationships still readable by humans
- You can reinstall later
- Or use another tool that reads frontmatter
What happens to my relationships if I uninstall?
They remain in frontmatter. You can:
- Keep them for future use
- Remove manually if desired
- Use other tools that read frontmatter
About This Documentation
Is the documentation completely up to date and accurate?
We strive for perfection, but Nexus Properties is a large, feature-rich project with extensive documentation. It's quite complex for one person to manage everything perfectly, so there may be occasional inaccuracies or outdated information.
If you spot something wrong, please help us!
- Create a Pull Request to fix it
- Open an issue to report it
- Suggest improvements or clarifications
Community contributions help us continuously improve the documentation and keep it accurate. Every correction, no matter how small, makes the docs better for everyone. Thank you for helping us improve! 🙏
Didn't find your answer?
- Check Troubleshooting for common issues
- Search GitHub Discussions
- Open a new discussion or issue