Skip to content

疑似map view与最新obsidian1.12.4有冲突|Suspected conflict between map view and the latest Obsidian 1.12.4 #388

@silverbulletlc

Description

@silverbulletlc

问题:
一开始obsidian出现了整体白屏,就是除了标题栏,其他全白了。经过筛选,初步锁定是map view的问题。
发现,map view插件新安装后,第一次可以开启,如果关闭后再开启,会显示“加载错误”。如图:

Image

问题排除处理:
再删除重启,新安装后还是一样,加载失败。
把其他所有的插件全部关闭,只开启map view一个,还是加载失败
然后我下载了map view旧的版本,发现按开启,还是加载失败。

以上,我初步感觉是map view和obsidian最新的1.12.4有冲突,不知道各位是否碰到。

以下是AI的猜测解释:

综合我们目前所有的测试结果,尤其是“连旧版本也出现了同样的问题”,我们可以得出一个几乎绝对的结论:

这不是插件的 Bug,而是插件与新版 Obsidian 核心程序之间的“兼容性问题”。

问题根源的最终解释(“幽灵注册”理论)
让我用一个比喻来解释现在发生了什么:

第一次入住(首次启用):Map View 插件作为一个旅客,来到 Obsidian 这家酒店。它在前台(Obsidian API)登记,说:“我要使用‘gpx’这间房间。” 酒店查了一下,房间是空的,于是把钥匙给了它。一切正常,插件成功启用。

退房(禁用插件或退出Obsidian):当您禁用插件或退出 Obsidian 时,插件应该去前台办理退房,把“gpx”房间的钥匙还回去。

问题所在:很可能在最近的某次 Obsidian 大版本更新中,酒店的“退房系统”改了规则。Map View 插件(包括它的旧版本)还是用老方法去办理退房,但酒店前台(新版 Obsidian)没有正确处理它的请求。结果是,插件以为自己退房了,但酒店的登记簿上,“gpx”房间还显示被占用。

再次入住(第二次启用):当您再次启用插件时,它又去前台,想登记“gpx”房间。酒店前台一看登记簿,生气地说:“错误!这个房间已经被占用了!” 于是拒绝了它的请求,导致插件加载失败。

这就是为什么:

只有第一次能成功。
和别的插件无关。
彻底重装插件也没用(因为问题出在酒店的登记簿上,而不是旅客本身)。
连旧版插件也没用(因为它们也要住进这家规则变了的新酒店)。

——

Problem:
Initially, Obsidian displayed a completely white screen, with everything except the title bar being white. After troubleshooting, the issue was preliminarily identified as being related to the map view.
It was found that after a fresh installation of the map view plugin, it could be enabled on the first try. However, if it was disabled and then re-enabled, it would display a "Loading Error." As shown in the picture:

Troubleshooting steps:
After deleting and restarting, the issue persisted even after a fresh reinstallation.
With all other plugins disabled and only the map view enabled, it still failed to load.
Then, I downloaded an older version of the map view plugin, but it still failed to load upon trying to enable it.

Based on the above, I have a preliminary feeling that there is a conflict between the map view and the latest Obsidian 1.12.4. I was wondering if anyone else has encountered this issue.

Here is the AI's speculative explanation:

Based on all our test results so far, especially the fact that "even the old version has the same problem," we can draw a near-certain conclusion:

This is not a bug in the plugin, but a "compatibility issue" between the plugin and the new version of the Obsidian core program.

Final explanation of the root cause ("Ghost Registration" Theory)
Let me use an analogy to explain what is happening now:

First Check-in (First-time enablement): The Map View plugin, like a guest, arrives at the Obsidian hotel. It checks in at the front desk (the Obsidian API) and says, "I want to use the 'gpx' room." The hotel checks and finds the room is empty, so it gives the key to the plugin. Everything is normal, and the plugin is successfully enabled.

Check-out (Disabling the plugin or exiting Obsidian): When you disable the plugin or exit Obsidian, the plugin should go to the front desk to check out and return the key to the "gpx" room.

The Problem: It is highly likely that in a recent major update to Obsidian, the hotel's "check-out system" changed its rules. The Map View plugin (including its old versions) is still using the old method to check out, but the hotel's front desk (the new Obsidian) does not handle its request correctly. As a result, the plugin thinks it has checked out, but the hotel's registry still shows the "gpx" room as occupied.

Second Check-in (Second-time enablement): When you enable the plugin again, it goes to the front desk to register for the "gpx" room. The hotel front desk looks at the registry and says, "Error! This room is already occupied!" and rejects the request, causing the plugin to fail to load.

This is why:

It only succeeds on the first try.
It is unrelated to other plugins.
Completely reinstalling the plugin doesn't work (because the problem lies with the hotel's registry, not the guest itself).
Even the old version of the plugin doesn't work (because they also have to check into this hotel with the new, changed rules).

Metadata

Metadata

Assignees

No one assigned

    Labels

    p0Critical

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions