henryqw / mercury_fulltext Goto Github PK

The plugin could instead make the endpoint configurable, so it would still be very much relevant.

Is there a reason this repo will be deprecated when people can still self-host mercury?

Thanks,

• What is the issue?

使用2023-06最新版本的docker compose，遇到异常，无法抓取全文

• What is your setup? (PHP version, database used, etc.)

PHP Version 8.1.20 (in docker)+ Azure Database for postgres(in cloud)

• Are there any error logs?

plugins.local/mercury_fulltext/init.php:279

Uncaught TypeError: property_exists(): Argument #1 ($object_or_class) must be of type object|string, null given in /var/www/plugins.local/mercury_fulltext/init.php:279
Stack trace:
#0 /var/www/plugins.local/mercury_fulltext/init.php(279): property_exists()
#1 /var/www/classes/pluginhandler.php(15): mercury_fulltext->extract()
#2 /var/www/backend.php(169): PluginHandler->catchall()
#3 {main}
  thrown

Request URI: /backend.php
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36

• How can the issue be replicated?

• Other Comments

Hey there,

I added this plugin into plugins folder, and it showed up on localhost. However, I can't update with API key. (I could see Get fulltext via Mercury Parser in each sub)

Please see screenshots below for more details.

Do you have any idea how to solve this issue? Thanks!

• What is the issue?

I've not managed to reproduce it reliably but I frequently get the attached error message

• What is your setup? (PHP version, database used, etc.)

TT-RSS on a Synology NAS & Docker

• Are there any error logs?

-->

解析部分链接， 不完整。
curl http://service.mercury:3000/parser?url=https://weexcn.com/articles/3590655

{"title":"WEEX·一起交易_全球投资策略_线上交易服务品牌_外汇,期权,期货,基金,股票,金融,投资","author":null,"date_published":null,"dek":null,"lead_image_url":null,"content":" ","next_page_url":null,"url":"https://weexcn.com/articles/3590655","domain":"weexcn.com","excerpt":"","word_count":1,"direction":"ltr","total_pages":1,"rendered_pages":1}

• What is the issue?

Plugin appears to be working up until re-writes the article content with the information returned from the mercury_api.

I can see the plugin passing the URL to the mercury_api but then the body of the articles is not being replaced with the returned results from the API.

• What is your setup? (PHP version, database used, etc.)

CentOS 6
PHP 7.1.26
MariaDB 15.1

TTRSS 19.2 (900cdbb)
Node 10.15.1 (for mercury-parser-api)

Your mercury API

• Are there any error logs?

None I can see. I can enable PHP debugging if that would be helpful and try to find something.

• How can the issue be replicated?

Subscribe to a feed, enable the mercury_fulltext plugin, wait for feed to refresh with new articles.

I am testing with: https://www.wired.com/feed/category/business/latest/rss

• Other Comments

I may find a bug. You can try:

1. Add a new feed
2. Change the feed's name
3. mf plugin will be automatically enabled on that feed
4. mf plugin can't be disabled on that feed

• What is the issue?

mercury_fulltxt插件已启用，全文搜索不支持中文

• What is your setup? (PHP version, database used, etc.)

参照此教程安装ttrss：通过 docker-compose 部署——Awesome TTRSS， PHP，database等等的具体版本不清楚，yml文件中service.一系列镜像 的版本都是latest

• Are there any error logs?

无

• How can the issue be replicated?

1、打开ttrss
2、快捷键/，输入中文。其中language默认simple
3、反馈

Search results: 央行 (Cancel search)
No articles found to display.

• Other Comments

[SOLVED] Search in Chinese Apr 10, 2019 from discourse.tt-rss.org，这边显示似乎已解决该问题，不清楚为何本机依旧失效。

谢谢

• What is the issue?

The plugin no longer appears to be working with self-hosted with the Mercury API (mercury-parser-api). It worked immediately after deployment for a few weeks and stopped after the most recent update to mercury-parser-api or the update to this project from 7 days ago.

I'm not explicitly getting an error from either tool so I'm starting here for submitting a bug report.

• What is your setup? (PHP version, database used, etc.)

CentOS 6
PHP 7.1.26
MariaDB 15.1

TTRSS 19.2 (900cdbb)
Node 10.15.1 (for mercury-parser-api)

• Are there any error logs?

This is the output I'm seeing from mercury-parser-api. Not certain how to get any error logs from the plugin itself.

Serverless: GET /parser (λ: mercuryParser)

Serverless: Warning: handler 'mercuryParser' returned a promise and also uses a callback!
This is problematic and might cause issues in your lambda.

• How can the issue be replicated?

Wait for a RSS feed I'm using mercury_fulltext with to post a new story, not see the content of that story, only the summary.

• Other Comments

Manually accessing the mercury-parser-api via: http://localhost:65518/parser?url=https://www.wired.com/story/zuckerberg-privacy-manifesto-questions/ appears to work properly with the correct content returned to the browser.

I get the same error when manually calling mercury-parser-api as the mercury_fulltext plugin appears to so that might be a red herring.

Serverless: GET /parser (λ: mercuryParser)

Serverless: Warning: handler 'mercuryParser' returned a promise and also uses a callback!
This is problematic and might cause issues in your lambda.

I have tt-rss ver. 19.2 at my vps, with mercury-api docker spun at AWS. I can access mercury parser via instance's public IP and can see it working, outpuput. ( eg. 10.14.15.17:3000/parser?url=yadayads ) but in tt-rss I can see that it's not being parsed at all, without any errors.

Hello, I have the plugin successfully installed and API key saved, is there a way for me to apply the Mercury Parser to all feeds by default vs. going into the plugin settings for each one individually where I'd like to use it?

after tt-rss has update to php8 i see this error

E_WARNING (2)	
plugins.local/mercury_fulltext/init.php:218	
Undefined property: stdClass::$content
1. plugins.local/mercury_fulltext/init.php(218): ttrss_error_handler(2, Undefined property: stdClass::$content, plugins.local/mercury_fulltext/init.php, 218)
2. plugins.local/mercury_fulltext/init.php(241): process_article([{"owner_uid":1,"guid":"1,52781401121009","guid_hashed":"{\"ver\":2,\"uid\":1,\"hash\":\"SHA1:1d5db5ad0bc86275e526925c056e86f3b336526a\"}","title":"{redacted})
3. classes/pluginhost.php(198): hook_article_filter([{"owner_uid":1,"guid":"1,52781401121009","guid_hashed":"{\"ver\":2,\"uid\":1,\"hash\":\"SHA1:1d5db5ad0bc86275e526925c056e86f3b336526a\"}","title":"{redacted}.)
4. classes/rssutils.php(818): chain_hooks_callback(hook_article_filter, {Closure}, [{"owner_uid":1,"guid":"1,52781401121009","guid_hashed":"{\"ver\":2,\"uid\":1,\"hash\":\"SHA1:1d5db5ad0bc86275e526925c056e86f3b336526a\"}","title":"{redacted})
5. update.php(238): update_rss_feed(1724, 1)

刚刚看到，我试用了一下，还不错。

Does your mercury fork support additional extractors/parsers like upstream does? Can't figure it out digging through code.
https://github.com/postlight/mercury-parser/tree/master/src

Thank your for this plugin. Works great with english feeds.

However, special characters like German Umlauts don't seem to be supported, resulting in garbled text (see screenshot attached). I don't have similar problems when e.g. using Mercury in the iOS Reeder App.

Hi,

I have properly set the mercury_fulltext plugin and filled my Mercury API, but the "Get fulltext via Mercury Parser" option still remain unchecked after every refresh.

This relapse after reinstall the plugin.

Hello WangQiru,

我已经正确的安装了插件，并设置了 Mercury API，但是插件始终无法正常工作，具体表现为：在某个 Feed 的 Plugins 选项中勾选了「Get fulltext via Mercury Parser」，页面刷新后，这个选项会回到未勾选的状态。
重新安装插件后问题仍在。请问这个问题大概是什么原因造成的？可能的解决方法？

Enable for specific feeds in the feed editor.
只是显示这一行。其他的全部空白
php=7.4

ttrss日志错误显示：
Uncaught Error: Call to undefined function Controls\hidden_tag() in /home/wwwroot/ttrss/plugins.local/mercury_fulltext/init.php:86 Stack trace: #0
/home/wwwroot/ttrss/classes/pluginhost.php(134): mercury_fulltext->hook_prefs_tab() #1