• Hey guys – a couple of things here:

    How about you tell us what the max file size is (not just the slider) before we start our search since the table size is listed there – you can tell us before we wait for the search.

    Second thing is, maybe you could provide some insight as to what tables to try first – i need tables for pages and posts – not rev slider but at least the rev slider table is clear and makes sense.

    I think I’m moving on to a dif search tool, at least to test, to see if i can’t get some answers and see some impact. While I’ve used this before, and you probably think it’s clear what to do, and while I do plenty of web dev, I do not a lot of db admin-ing, figuring out how to search against that table list, not conducive to affective time management for me. Espcially since I don’t know what tables are what.

    THOUGHT: Maybe instead of listing out tables and letting us pick and capping the search size – you perform the search against all tables in the db – theeeeen you say “this is what we found, where we found it, the size of the search” THEEEEN you can say, ‘bc your search exceeds X you’ll need to upgrade to pro. (Upgrade right now and get 50% off – or some special to promote “BUY NOW” – instead of letting them leave to find another tool.) But i think this approach may not only reduce your tech support messages, but also, drive more business to you.

    Just trying to help because I see a lot of support saying, “max this, max that, doesn’t work” when I’m sure it works, we’re just not using it correctly. Dumb it down for us non-backenders and offer advanced features on the backend pro version. This will also increase your demographic for the noobs and the pros.

    Thank you for all you do and create awesome tools. (off to search and replace, but I may be back) 🙂

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi @hemjesti, I’m the product manager of Better Search Replace. Thanks so much for taking the time to leave this feedback.

    How about you tell us what the max file size is (not just the slider) before we start our search since the table size is listed there – you can tell us before we wait for the search.

    To clarify, the Max Page Size setting refers to the number of records returned when the plugin searches the database; it does not refer to the overall size of the database or individual tables. This setting is not meant to limit the size of the database or tables you can search, but rather to strike the right balance between search speed and the processing power of your server. The default value of 20,000 is usually sufficient, but lowering it can help with to prevent timeouts on large databases or tables with complex data structures. It is not something that we can necessarily predict ahead of time before attempting the search.

    Maybe instead of listing out tables and letting us pick and capping the search size – you perform the search against all tables in the db…

    Thanks for raising this as our team is reconsider the appropriate default behavior. I can see the value of searching all tables by default for users who may not know exactly what type of data is stored in each table. The flip side of that argument is that users may end up affecting data in tables that they didn’t intend to affect if all tables are selected by default. The current opt-in behavior ensures that the plugin only impacts tables intentionally chosen by the user.

    If you still want to search all tables, then you might consider focusing the list of tables and then using the keyboard shortcut Command-A (Mac) or Control-A (Windows) to quickly select the entire list.

    …while I do plenty of web dev, I do not a lot of db admin-ing, figuring out how to search against that table list, not conducive to affective time management for me. Espcially since I don’t know what tables are what.

    As for which database tables to choose, you may find it helpful to review our tour of the WordPress database. For pages and posts, you’d likely want to start with the wp_posts and wp_postmeta tables.

    I’d love to learn more about how you have used Better Search Replace and hear about any of the pain points that we could improve upon. Let me know if you’d like to schedule a feedback session where we can discuss further.

    Thread Starter hemjesti

    (@hemjesti)

    Hey @kevinwhoffman I’d def be open to scheduling a feedback session. I’m in Dallas, Texas. So let me know when and where. Thank you for the detailed response. I truly appreciate it.

    Hi @hemjesti. Sounds great. Feel free to book some time here: https://calendar.app.google/jyn9FELgLNQJwMuT6

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.