Vercel永久加载问题上的Metaplex店面
我在加载Metaplex商店时遇到问题。我从主要的Metaplex-Foundation Github Master进行了直接分支，并在此处通过其说明将其部署在Vercel上： https://github.com/metaplex-foundation/metaplex/metaplex/blob/master/master/deploy.md
永远加载，无法访问或连接钱包，也无法访问网站。
我遵循上面链接的所有说明，并确保我在.env中有地址。 我什至在以前的体验中添加了在软件包/Web文件夹中添加的新CNAME文件中添加了一个URL。
我该如何解决？
I am having problem loading metaplex store. I did a direct fork from the main metaplex-foundation github master and deployed it on Vercel via their instructions here: https://github.com/metaplex-foundation/metaplex/blob/master/docs/deploy.md
It builds without errors, but when I load the site, it just keeps loading forever and wallet cannot be accessed or connected nor the site be accessible.
I followed all instructions from their link above and ensured I have the address in the.env.
I even added a URL in a new CNAME file I added in packages/web folder, from previous experience.
How can I resolve this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
对于初学者来说，Metaplex承认当前的店面（V1）有很多影响用户的问题。考虑到截至2022年5月，店面已正式贬值，将不再进行其他修复。随着您所描述的问题的高级概述如下：
启动店面（SF）（SF） ）没有拍卖，它需要扫描大量数据以找出需要显示的内容。该扫描包括对RPC的一些大幅调用，这些电话可能会根据网络状态而起作用，也可能不起作用。此步骤也有点障碍，最终可能会进入无限的加载循环。
当您启动第一次拍卖时，SF会在链条上创建一个StoreIndexer对象。该对象用于索引第一次拍卖和所有后续拍卖。
如果SF在启动时找到了StoreIndexer对象，则它绕过步骤（1）中的所有疯狂，而是使用StoreIndexer来弄清楚需要哪些数据。这不需要任何gpa（getProgramaccount）调用。
这有点像Catch-22，因为为了开始首次拍卖，您需要店面，但是您还需要拍卖以避免在步骤（1）中避免加载问题。
在第一次拍卖开始后，您应该能够像平常一样恢复使用SF。
您可以尝试此版本的店面来解决无限的加载问题。就功能而言，它是准排骨，SPL令牌有一个小数以外的小数。但是，它确实可以解决无限的加载问题，您应该能够将其首次拍卖列出。
https：//github.com/neftworld/metaplex-store-store-store-store-storefront-v1
strong>店面被弃用如此警告
For starters, metaplex acknowledges that the current storefront (v1) has quite a few issues that are impacting users. No further fixes will be forthcoming given that the storefront has been officially deprecated as of May 2022. With that out of the way, a high level overview of the issue you are describing is as follows:
when you start a storefront (SF) that has no auctions, it needs to scan quite a bit of data to figure out what it needs to display. This scan includes a few chunky calls to the RPC that may or may not work depending on the state of the network. This step is also a bit buggy and can end up in an infinite loading loop.
when you fire up the first auction, SF creates a storeindexer object on the chain. This object is used to index the first auction and all the subsequent auctions.
if SF finds a storeindexer object on startup, it bypasses all the madness in step (1) and instead uses the storeindexer to figure out what data is needed. That doesn’t require any gPA (getProgramAccount) calls either which is nice.
it’s a bit of a catch-22 because in order to start the first auction you need the storefront, but you also need an auction to avoid the loading problem in step (1).
After the first auction is up you should be able to resume using your SF as normal.
You may try this version of the storefront to get around the infinite loading problem. It's quite barebones in terms of functionality and there is an issue with SPL tokens that have decimals other than 9. However it does get around the infinite loading problem and you should be able to list your first auction with it.
https://github.com/neftworld/metaplex-storefront-v1
However, STOREFRONT IS DEPRECATED SO CAVEAT EMPTOR