borsaro

I have the same problem, tryied many times but still when I reload it it goes back to 2.1.8

I found the solution. Basically it was a problem to identify more precisely the field with xpath, now it is working. In order to solve the problem in case someone will get in the same trouble I did: This in order to identify the proper identify the exact path, in this case I try to scrape the placeholder: set(#yup,$plugin function("ExBrowser.dll", "$ExBrowser Scrape Element Attribute", "//*[@id=\"weight_based_shipping_rate_browser_modal\"]/form/div[2]/div[1]/div[2]/div/label/..//input[contains(@name,\"rate_name\")]", "placeholder"),"Global") And then just click and type it and it w

Hi everyone, I am trying to write inside input fields inside the admin area in shopify, with no results. With exBroswer inside the shopify admin area even trying millions of combination between "scroll to element" "move mouse" and click I just can't write inside the input fields. I can't find a way to activate it properly in order to be able write inside the input field and eventually write inside. I tried with type text, change elemnt value, etc... but nothing happens. Hopefully here someone have any ideas? Thank you!!!

Hi, I join the conversation because I have the same problem and already tried with exBrowser. It works but not everywhere. In some cases shopify open a sort of popup form to set information and there exbrowser is not able to write info inside. For some reason neither the change attribute value, nor the type text are able to perform the task. I tried to force also the activation of the field via browser, but nothing is working. Outside those kind of popups everything seems to be working fine. Any suggestion?

POSSIBLE WORK AROUND for who is experiencing that problem. I contacted the Support in order to understand what's going on. Sadly it seems that is not so easy to get to a solution because it seems some JSON issue going on behind the scene. First they pointed out that on an URL there was the ? due to URL parameters and then a * (wildcard) in the same Scrape Attribute. Something like: <href=w"https://www.example.com?post_di=2222*">,"href"),"Global") ? is interpreted like a wildcard too from the scrape command so this could create some confusion to the system. I found it could be a po

I am on a developer edition V5.9.55 and I am still getting the problem, anyone got the solution yet? Actually I noticed that it is giving me the problem each 4 pages. I am scraping atttibute in a loop inside woocommerce the variable / simple product dropdown, but I got the same problem in past with other scraping actions.