hoothin
hoothin
Okay, I'll look into it. Please let me know if you get any more info, like what's different about the environment when things are working normally vs. not.
感谢反馈，可以暂时先用Left+top，下个版本会修复。谷歌审核通过可能要等到下周
感谢反馈，修复了
这不是图，是pdf https://www.xuefeiji.org/public/uploads/files/20250220/1_202502201148485b6ba.pdf
You can use in other repositories' Issues sections, but not in this one.
https://pagetual.hoothin.com/rules/nextLinkByUrl.html { "name": "Github issues and pulls", "url": "^https:\\/\\/github\\.com\\/[^/]+\\/[^/]+\\/(?:issues|pulls)", "pageElement": "ul[role='list']", "nextLinkByUrl": [ "(&page=(\\d+))?$", "&page={$2+1}" ], "pinUrl": true, "action": 0 }
The example you provided only has 23 issues in total, so no page numbers were generated. Please refer to the rules I've given and use the third stop marker.
This is just a sample to get you started. You'll need to create your own rules, like setting up different rules based on whether or not the URL contains 'page'.
Thanks. I've updated the version, changing s3072 to s0.
目前自定义规则优先级已经是最高的了，只是缓存规则优先级更高。 假设公共规则能匹配`a1.com`、`a2.com`。自定义规则仅匹配`a1.com`。 那么当你首先访问`a2.com`的时候，`a2.com`对应的公共规则就会插入到缓存规则中。此时访问`a1.com`，因为缓存>自定义>公共规则，因此直到缓存失效，缓存都会首先命中。 解决方案是再新增一个自定义规则，复制此公共规则，但是添加exclude来排除`a1.com`，这样这个公共规则就会失效，不会再参与匹配。 因为公共规则的一部分来源于 wedata，所以我没办法去修改。你要是没有思路，可以把网址发上来。