Using OSclass322 and
Chrome 29
Had this problem and could not resolve it so OK - reinstalled plain vanilla 322 version.
Added no plugins/made no changes.
Cannot add item using Chrome or internet Explorer - can add item using Firefox.
Under Chrome - it happily runs through the item_add script.
I receive an email that says the item has been added - but gives an erroneous url ending in /index.php?page=item&id=0.
It then updates the category count as though an item had been added to the db using the chosen category. It does not add the item to the items table
Will work using localhost - using Chrome - will not work on webserver using Chrome.
Will work using Firefox (25) on localhost and webserver.
website currently located at http://buyitsellitswapit.net/
I have tried adding an item either as registered user, or as unregistered and it makes no difference.
Would be very grateful if someone could point me to where this script is failing please.
Edit update...after further testing
This has been quite strange - fails under Ubuntu 13.10/Chrome 29, but works in Firefox and Chromium (30)
Works when I use a WinXP/Chrome and WinXP/IE in VirtualBox under Ubuntu
Works on my son's machine - Win8/Chrome and IE
Just hope not too many clients are using Ubuntu and Chrome together.
Related
Im running chrome headless through chromedriver and selenium via python.
I've run into the following issue both on Mac and Linux.
Im starting chrome as follows:
if self.headless:
options.headless = True
options.add_argument("--headless")
if self.debug_port:
logging.info(f"Setting up remote debugging on port {self.debug_port}")
options.add_argument(f"--remote-debugging-port={self.debug_port}")
options.add_argument(f"--remote-debugging-address=0.0.0.0")
If I connect to http://localhost:9222 from another headed instance of chrome I can see the list of sessions and connect to it seamlessly. At which point i have a window opened up with a screencast of the remote session and the dev console.
Here's that successful example:
When I connect to http://192.168.1.194:9222 I get the list of sessions just fine and upon selecting one the dev console opens but it doesn't start the websocket connection to ws://192.168.1.194 so the screencast and remote debugging capabilities are not available.
Here's that failed example:
I've captured har files and uploaded them here if you want to take a look
Using the following steps I was able to debug remotely. However the screencast functionality did not work. Ultimately that's what I needed so this is only a 50% solution in my case.
So, as noted above in the comments, what's blocking remote debugging from working is that the chrome debugger links out to https://chrome-devtools-frontend.appspot.com/..... and passes a value of ws://192.168.1.194 for the websocket parameter. Any browser will inherently block this, based on it being mixed content - i.e: https + ws
What's needed here is to run the chrome dev tools frontend on a http server
and direct your chrome instance to that server instead of the appspot instance.
Solution Steps
1 Install depot_tools (pre-requisite for building)
https://commondatastorage.googleapis.com/chrome-infra-docs/flat/depot_tools/docs/html/depot_tools_tutorial.html#_setting_up
2 Checkout the devtools-frontend repo
https://github.com/ChromeDevTools/devtools-frontend/blob/master/docs/workflows.md#checking-out-source
3 Build chrome devtools frontend
https://github.com/ChromeDevTools/devtools-frontend/blob/master/docs/workflows.md#build
4 Start the devtools-frontend http server
https://github.com/ChromeDevTools/devtools-frontend/blob/master/docs/workflows.md#running-in-hosted-mode
5 Run 2 instances of chrome and use one to debug the other
5.1 Start first instance of chrome headless
...with remote debugging enabled. See the python way in the question above or do it from the command line with the same arguments
5.2 Start a second instance of chrome
...using a different user data dir --user-data-dir=<some-path>
5.3 Navigate to http://192.168.1.194:9222
Use whatever the IP address of the first chrome instance is and the port that you chose.
5.4 Create a link to the local dev server
The 2nd instance of chrome will now be showing you links to debug each of the open tabs of the 1st instance. However the links will still to go https://chrome-devtools-frontend.appspot.com/..... You'll need to copy n paste the link you want and replace the hostname with the hostname of the devtools frontend that you started in step 4
Walla!!
If you figure out how to get the screencast working please comment below! 🙏
N.B:
I also tried using the npm run server command in the devtools frontend but for some reason that server didn't work at all ¯\_(ツ)_/¯
I want to run a simple test using OxygenHQ, of opening wikipedia and then search for hello world. The script written is working fine for Chrome and Firefox but in case of IE mutiple windows are opening without the page and then it fails eventually.
Is there any way to fix this? I went through the docs provided at http://docs.oxygenhq.org/guide-web-intro.html but could not get a concrete answer on why this is only happening for IE. Here is a console output and screenshot for reference.
Console Output :
Initializing...
Starting iteration #1
UNKNOWN_ERROR - undefined: args[0].endsWith is not a function at line 1Test finished with status --> FAILED
Details:
Browser: Internet Explorer
Version: 11.535.18362.0
OS: Windows 10
This might be connected to your internet settings
make sure that the IE screen size is 100%
make sure all Internet options in Security Tab (Internet, Local Internet etc') are either with the Enable protected mode on or off (should be the same for all)
see picture
Have a look again at the Oxygen web site, it has had a major facelift and a lot of new content
My app is served on localhost. I am testing it on Browserstack: see title for browser version and OS. I'm running Chrome 59 on OSX Sierra.
I've tried entering localhost:PORT, and http://localhost:PORT but am always given a Bing search result for that string, instead of directing to my development server. I know the server is up because I'm doing manual testing on Firefox, Safari, and Chrome.
I've also attempted to change Edge settings in guides like this one, but there the button to remove bing completely does not exist.
Can anyone point me at support/docs that disable this functionality? Thanks!
I am trying to automate mobile web site, so i am using virtual browser in Testcomplete 10. But i couldnot able to map any child object from parent.
I can take main page screenshot only. Below steps i had done,
1) opend www.google.com by using virtual browser with Apple ipad or any other
2) took screenshot for main page, Name Mapping path : Aliases.browser.BrowserWindow.Chrome_RenderWidgetHostHWND
3) Trying to map Google search textbox, but could not map that child objects from parent("Chrome_RenderWidgetHostHWND").
Can any one confirm possible solution for this?
I guess you're using Chrome 34?
You need TestComplete 10.10 with the Chrome 33 patch (it works for Chrome 34, too).
Also, make sure that the TestComplete extension version in chrome://extensions is 10.10.xxx; otherwise uninstall and reinstall both Chrome and TestComplete as explained here.
A client's website was working fine, until they had some problems with their web host. Temporarily, the Apache CentOS Test Page was visible. The host claim the problem is fixed - and it seems to be - for everyone but me...
I'm using Safari 7 on OS X Mavericks and every single time when I visit their site I still see the test page.
When anyone else uses their own computer with any browser, it works fine...
When I use Chrome on my Mac it works fine... So the problem is just with Safari.
I've tried clearing Safari's cache
I've tried clearing the DNS cache
I've tried a restart
But I've got no idea why I can't access it. I need to access the site to work on it - yes I can use Chrome, but Safari is my primary browser. Any ideas?
It turned out this was caused by an issue in a Regex within Apache's Mod_Security. The Regex falsely identified a string contained within a cookie as being an SQL injection (it wasn't - purely coincidental).