Conflicting upserts on using templates

[nakal]

Search first

• I searched and no similar issues were found

What Happened?

Using a template on Android gives me "Conflicting upserts" error for most templates.

Reproduce the Bug

1. Create a template on a page called "Template/NewTemplate".
2. Name the Template "Template/NewTemplate" (same as page title).
3. Try to use the template on a new page.

Expected Behavior

Using the template should fill out the new page.

Screenshots

Desktop or Mobile Platform Information

Android 13
Logseq 0.9.17

Additional Context

I can use the same template on PC (Linux). It's just a problem on Android.

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)

[nakal]

More details:

1. Reindexing the graph does not fix the error.

2. Altering (I altered some text) the affected template and then reindexing the graph fixes the problem.

[nakal]

Ok, I found the reason, why it is handled weirdly. When you make a template using metadata, don't reuse the first property header to describe the properties for the page and for the template itself in one block.

You should rather made the first block about the template itself and then indent the page properties once after the template property block.

This is wrong:

This is correct:

[nakal]

Unfortunately, my suggestion does not work, either. After reindexing, the template gets destroyed (it merges both property sections and has two icon:: entries) and causes problems that can be resolved manually. It's a bit annoying.

The point is that I have 2 icons specified:

• The template itself has got an icon for templates.
• The application of the template should generate a special icon for the type of the page.

[github-actions]

Hi There! 👋

We haven't seen any activity on this issue in a while 😴, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!

If the issue has been resolved or is no longer relevant, that's great news! 🎉
We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.

Access additional Logseq 🚀 resources:

• Forum: https://discuss.logseq.com
• Blog: https://blog.logseq.com
• Docs: https://docs.logseq.com

Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!