Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feed.php bug #2727

Closed
dryoo opened this issue Mar 22, 2019 · 5 comments · Fixed by #3610
Closed

feed.php bug #2727

dryoo opened this issue Mar 22, 2019 · 5 comments · Fixed by #3610

Comments

@phy25
Copy link
Collaborator

phy25 commented Mar 23, 2019

I tested on my development DokuWiki (with a few pages only), and the speed looks normal. May we know the server environment and the number of pages you have in total?

@dryoo
Copy link
Contributor Author

dryoo commented Apr 12, 2019

I currently disabled feed.
but i will test again.

my server status is below.

Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40G
32 GiB System Memory (8GiB DIMM DDR3 Synchronous 1600 MHz x 4)
128GB Samsung SSD 840, 2TB WDC WD20EZRX-00D
Ubuntu 16.04.2 LTS, PHP 7.0.15-0ubuntu0.16.04.4 (cli) ( NTS ), Nginx, MariaDB

total pages : 10779
total media : 13858

openwiki.kr

@dryoo
Copy link
Contributor Author

dryoo commented Apr 14, 2019

Oh. I use currently google custom search.

but I tested dokuwiki's own search engine.
and
The answer is Yes.

then is this not a problem of feed.php?

I think normal user will not use such query. but crawling bot uses that frequently.

@phy25
Copy link
Collaborator

phy25 commented Apr 15, 2019

OK, it's just that you have too many content in your wiki and the native search should take that much time. Also the search indexes may not work with Unicode string well.

You may want to disable search functions as well, besides your already disabled feed.

⭐️ Looks like search in feed.php does not respect disableaction=search; should we enhance this a bit?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants