loops

When I change to 500 results per page instead of 25 I see my regex is working as it shows results and makes it through the complete wp_posts table of 123k rows.

My wp_postmeta however has 937k rows so running it on All Post Types isn’t going to work at the moment.

Maximum number of page requests has been exceeded and the search stopped. Try to be more specific with your search term.

This happened after `XHR GET https://—/wp-json/search-regex/v1/search/?searchPhrase=%3C%2Fa%3E%20%2F%20%5BabcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890%5D%28.%2A%29&searchFlags%5B0%5D=case&searchFlags%5B1%5D=regex&source%5B0%5D=posts&perPage=25&page=12500&searchDirection=forward&limit=25&_wpnonce=9e6d4f1951
[HTTP/2 200 OK 1987ms]`

Each GET takes about 1 to 2 seconds, so I had to wait 12 minutes and it did not show any results. Not sure whether the records that match the pattern were checked or not yet.

In comparison, the previous version takes about 1 second to complete and does show the results, though I do limit it to search maximum of 25k records.

• This reply was modified 4 years, 10 months ago by loops.

I can assure you it works on 1.4.16. As far as I remember I never modified any of the files of that version except adding a few list options to the search limit as I mentioned earlier.

The pattern works fine with [] delimiters, as it does with others like %, @, and also /<\/a> \/ [abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890](.*)/

I hope you can figure out why the new version stops after the page=2500, then maybe I can figure out what I’m doing wrong with the regex. Thanks!

I’ve been using that pattern for years, it works fine. You can see the result here https://pasteboard.co/J7A7CgH.png

I’m not familiar enough with regex to rebuild the regex patterns I was using in the previous version unfortunately.

With </a> / \w+ which should work just fine the console shows a bunch of successful XHR GET, with the last one being the following (I’ve replaced my website address with —)

https://---/wp-json/search-regex/v1/search/?searchPhrase=https%3A%2F%2F---%2Fproduct%2F&searchFlags%5B0%5D=case&searchFlags%5B1%5D=regex&source%5B0%5D=posts&perPage=25&page=2500&searchDirection=forward&_wpnonce=cda8f26d47

Every time I try it chokes after page=2500

Then this shows:

undefined search-regex.js:55:57309
    message https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:55
    c https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:6
    g https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:6
    tt https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:55
    Ee https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:55
    onSetError https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:55
    Ao https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:55
    ol https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    gu https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    unstable_runWithPriority https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:35
    Bo https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    mu https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    hu https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    z https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:35
    onmessage https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:35

TypeError: "a.message is undefined"
    Ea https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:55
    Ga https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    gl https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    cu https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    lu https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    Zl https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    Qo https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    unstable_runWithPriority https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:35
    Bo https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    Qo https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    qo https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    gu https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    unstable_runWithPriority https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:35
    Bo https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    mu https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    hu https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:27
    z https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:35
    onmessage https://---/wp-content/plugins/search-regex/search-regex.js?ver=2.0-32f788d37fc2989dee637ada18b75ef4:35
search-regex.js:27:82383

I tried </a> / \w+ instead because otherwise it also matches no words after the /, but unfortunately the search crashes, likely due to it taking too long to complete with 123,460 database rows to search.

Something went wrong ??

Search Regex is not working. Try clearing your browser cache and reloading this page.  If you are using a page caching plugin or service (CloudFlare, OVH, etc) then you can also try clearing that cache.

If that doesn't help, open your browser's error console and create a new issue with the details.

Please mention search, and explain what you were doing at the time

Plugin: 2.0
WordPress: 5.4.1 (single)
PHP: 7.3.17
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0
JavaScript: https://---/wp-content/plugins/search-regex/search-regex.js
REST API: https://---/wp-json/
Buster: 2.0 === 2.0

TypeError: a.message is undefined

    in Ea
    in div
    in div
    in a
    in f
    in div
    in a
    in f
    in StrictMode
    in H
    in ji

At this point I think I’ll just revert to the previous version since that works fine for me as long as I set a limit to the amount of records to be searched.

The original regex searched for patterns matching:
</a> / sometext

When using the exact same regex I now get results like the ones I mentioned in the previous post. Did something change with regards to delimiters maybe?

I run the old version on a database with some 50,000 posts, which causes problems with memory or execution time. In the old version I’ve modified /wp-content/plugins/search-regex/view/search.php to have some more limit options so I can search up to 25,000 asc/desc, which works for my server.

I don’t see the view folder in the 2.0 update so I’m not sure if I can easily limit the results limit anymore.

I’m afraid not so I’ve removed the plugin manually with FTP and removed entries from wp-options.

Fixed it for me, great!

I’m also using the classic editor. Would really appreciate a fix for this.

Great, thanks!

Fixes it for me too, but I have another problem now where when I edit a post in Quick Edit, all tags are removed when updating a post, regardless of what I changed (add/remove a tag, changing publish date, etc).

Can you guys check/confirm if this is an issue with the latest version?

Ah.. that makes sense. Works fine adding that second line.
Thanks a lot!

Same problem here, paragraph tags are inserted between div and img tags without the paragraph tag being closed as well.

While I’m waiting for a fix I have just copied the code from the 2.0.7 functions-formatting.php to the new formatting.php in wp-includes, which seems to work fine.

I might’ve broken something else by replacing the new code with the old, but in my case I haven’t noticed any problem so far…