Upgrade from 2.8 to 3.x

  • Resolved Borderguy

    (@borderguy)


    10 years ago

    We have been using WP Web Scraper for many years and our site now has well over 150 scrapes that break on our offline sandbox using the upgrade to 3.4. This includes all of the scrapes that were originally designed by you (Akshay Raje). The broken scrapes all use the now deprecated :eq() selector. Questions:

    1. What is the long term risk to staying on version 2.8? Will it continue to work indefinitely or is it likely to break sometime in the relatively near future?
    2. Given that the broken scrapes all use the :eq() selector:
    a. Is there a way you could grandfather this into the new version so we could do the upgrade and then systematically work our way through the site to modify all of the queries to the new selectors?
    b. We are not yet clear what a comparable selector would be for :eq(). Is there a generic replacement that we can simply substitute into a query to replace :eq() or do we have to redesign every query?
    c. Is there any way to do some type of global search and replace to update these queries as written?

    Thank you for your assistance.

    https://www.ads-software.com/plugins/wp-web-scrapper/

Viewing 1 replies (of 1 total)
  • Plugin Author Akshay Raje

    (@akshay_raje)

    Of the 150 off scrapes, how many would be uniquely different? Also, if the selectors end with :eq(), then there’s an equivalent eq argument in the newer versions, but if it contains :eq() somewhere in between then the only option as of now is to convert it to an xpath instead.

    I suggest you use the support form to reach out to me directly on this.

Viewing 1 replies (of 1 total)
  • The topic ‘Upgrade from 2.8 to 3.x’ is closed to new replies.