I use:
MediaWiki v1.39
Extension Page Forms 5.5.1
Extension Cargo 3.3.1
PHP 7.4 or PHP 8.0.26
When I open page Special:CreateClass, fill in a field and then click "Add field" I get a javascript error.
Uncaught TypeError: Cannot read properties of undefined (reading 'replace')
at pf.ComboBoxInput.apply (<anonymous>:86:73)
at jQuery.fn.createTemplateAddField (<anonymous>:79:26)
at HTMLSpanElement.<anonymous> (<anonymous>:84:116)
at HTMLSpanElement.dispatch (load.php?lang=nl&modules=ext.pageforms.select2%7Cjquery%2Cmoment%2Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=8i8qb:206:260)
at elemData.handle (load.php?lang=nl&modules=ext.pageforms.select2%7Cjquery%2Cmoment%2Coojs-ui-core%2Coojs-ui-widgets&skin=vector&version=8i8qb:202:877)
I also have installed the Cargo 3.3.1 extension, but get the same error whether I uncheck or check the box "Use the Cargo extension..."
When using Firefox I get the error:
apply jQuery
load.php:234:45
jQuery 23
Tried it in Chrome and Edge too but doesn't work in those either.
UPDATE 18-dec-2022:
I installed Mediawiki 1.35.8 and PageForms 5.5.1 and get the javascript error.
Solution / Workaround:
After installing PageForms 5.5 it is working in 1.39
Related
First the Environment:
Node JS 16.15.0
Web Driver io v7 (wdio)
wdio/cucumber framework
end to end testing of a website
-obviously using cucumber and feature files
using a test configuration file similar to wdio's
using wdio-chromedriver-service v7.2.6 and npm chromedriver package version ^107 to produce a browser to hit
my browser : chrome v107.0.5304.62
The Question:
an element cannot be found by webDriver as I expect, but the command causes the instance to crash
I am searching for an element that no longer appears on the page (it is a spinner element that shows the page is loading)
I call
if(await this.spinner.isDisplayed())
and then the test run hangs, the debugger tells me the command
INFO webdriver: COMMAND findElement("css selector", "i.fa-spinner")
is running and then nothing else, finally the renderer times out
WARN chromedriver: [SEVERE]: Timed out receiving message from renderer: 600.000
DEBUG webdriver: request failed due to response error: timeout
and the chrome instance crashes shortly later
I am unsure why this behavior is happening, is something wrong with my wdio configuration? or with my chrome driver?
What I have tried
I understand that
browser.setTimeout exists but
I am sure it is not set in my config anywhere.
I have done a global search (using vscode for all development) for browser.setTimeout (no results).
I have manually set browser.setTimeout({ 'implicit': 0 }) (no success).
I have also tried directly hitting a chrome driver instance by manually downloading a chrome driver exe that matched my browser version v107.0.5304.62 and removing the 'services: ['chromedriver']'
from my test config file
when this happens something very interesting occurs, I can keep running after searching for the element that broke the run before, but we dont get very far and the command still causes issues. Chrome driver is throwing errors like
error: 'no such element',
[0-0] message: 'no such element: Unable to locate element: {"method":"css selector","selector":"i.fa-spinner"}\n' +
[0-0] ' (Session info: chrome=107.0.5304.87)'
The browser closes shortly afterwards without progressing through the rest of the tests.
I find it interesting that the version that chrome driver says it is running is 107.0.5304.87 since the version of chromedriver I downloaded clearly says it is v107.0.5304.62 and my chrome version clearly states it is also v107.0.5304.62 .
though theoretically using v107.0.5304.87 shouldnt be an issue according to this
since the 107.0.5304 part matches across the board
I could use some assistance.
We had the same issue this days, seems there is a bug introduced in Chrome 106; try to change config or downgrade Chrome on the machine to use Chrome 105 as with this version is working.
I have been trying to setup automation testing for our openfin application using the below repo as base
https://github.com/openfin/webinar-automated-integration-tests
I am using Openfin (Chrome version 61.0.3163.100) and Chromedriver 2.40.565498
When I run "npm test", the openfin application opens up. But the tests don't run. After waiting for sometime, it throws the below error in console.
ERROR: unknown error: DevToolsActivePort file doesn't exist
(Driver info: chromedriver=2.40.565498 (ea082db3280dd6843ebfb08a625e3eb905c4f5ab),platform=Windows NT 10.0.16299 x86_64)
chrome
I tried using other versions of chromedriver like 2.33, 2.34, 2.37, 2.38, 2.39, 2.41. Using these versions even the application doesn't appear. So, I guess the chromedriver version I am using is correct. I have also tried adding the below arguments to chromeOptions
--remote-debugging-port=9222,--no-sandbox,--headless,--disable-gpu
They didn't solve my issue. Not sure what is causing the issue. Any help would be much appreciated. Thanks in advance. Cheers!
This error message...
ERROR: unknown error: DevToolsActivePort file doesn't exist
(Driver info: chromedriver=2.40.565498 (ea082db3280dd6843ebfb08a625e3eb905c4f5ab),platform=Windows NT 10.0.16299 x86_64)
...implies that the ChromeDriver was unable to initiate/spawn a new Browsing Context i.e. Chrome Browser session.
Your main issue is the incompatibility between the version of the binaries you are using as follows:
You are using chromedriver=2.40
Release Notes of chromedriver=2.40 clearly mentions the following :
Supports Chrome v66-68
Presumably you are using chrome=61.0
Release Notes of ChromeDriver v2.33 clearly mentions the following :
Supports Chrome 60-62
Your Selenium Client version is unknown to us.
So there is a clear mismatch between ChromeDriver v2.40 and the Chrome Browser v60.0
Solution
Ensure that:
Selenium is upgraded to current levels Version 3.141.59.
ChromeDriver is updated to current ChromeDriver v80.0 level.
Chrome is updated to current Chrome Version 80.0 level. (as per ChromeDriver v80.0 release notes)
Clean your Project Workspace through your IDE and Rebuild your project with required dependencies only.
If your base Web Client version is too old, then uninstall it and install a recent GA and released version of Web Client.
Take a System Reboot.
Execute your #Test as non-root user.
Always invoke driver.quit() within tearDown(){} method to close & destroy the WebDriver and Web Client instances gracefully.
I have recently upgraded a .net Core (2.1) / Angular 6 SPA app to the latest versions. I seemed to have done everything correctly at one point, but I made a change that broke the http (port 5000) app. I get an error:
vendor.js:1 Uncaught ReferenceError: module is not defined
at vendor.js:1
This is the first line of the vendor.js file. When I run the app using port 5001 (https), everything seems to work fine. I cannot figure out why there is a difference in the two websites as they are hitting the same code base.
To begin this upgrade, I started with the official dotnet core 2.1 Angular SPA and upgrade angular from 5 to 6.
I had this exact error and fixed it by changing the port number for the App URL in the Project Properties.
Hope this helps, however I'm still not sure what caused the issue.
I'm getting the following error when trying to deploy an app with the Microsoft Band SDK. The build config is RELEASE and the target output is ARM. If use DEBUG config, it works.
Error : DEP6810 : MdilXapCompile.exe failed with error code 2001.
I've examined the MDILXapCompileLog and the following is the where the compilation failed:
CrossGen failed
Error processing assembly [projectpath]...\obj\ARM\Release\MSIL\Microsoft.Band.dll
Raw error code: 2148733978
NOTE: The extra weird part about this situation is that if I only package the app without deploying, I can side-load it to the device and it works as expected.
Here are the csproj sections - Debug/ARM:
<PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Debug|ARM'">
<DebugSymbols>true</DebugSymbols>
<OutputPath>bin\ARM\Debug\</OutputPath>
<DefineConstants>DEBUG;TRACE;NETFX_CORE;WINDOWS_PHONE_APP</DefineConstants>
<NoWarn>;2008</NoWarn>
<DebugType>full</DebugType>
<PlatformTarget>ARM</PlatformTarget>
<UseVSHostingProcess>false</UseVSHostingProcess>
<ErrorReport>prompt</ErrorReport>
<Prefer32Bit>false</Prefer32Bit>
Release/ARM
<PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Release|ARM'">
<OutputPath>bin\ARM\Release\</OutputPath>
<DefineConstants>TRACE;NETFX_CORE;WINDOWS_PHONE_APP</DefineConstants>
<Optimize>true</Optimize>
<NoWarn>;2008</NoWarn>
<DebugType>pdbonly</DebugType>
<PlatformTarget>ARM</PlatformTarget>
<UseVSHostingProcess>false</UseVSHostingProcess>
<ErrorReport>prompt</ErrorReport>
<Prefer32Bit>false</Prefer32Bit>
The only difference I see are the debug symbols, could the Microsoft.Band.dll not have public symbols? Isn't Visual Studio supposed to created them?
I noticed that the solution still had the old Band SDK - Preview packages even after updating to the newer SDK. I manually deleted all the nuget items, forced a package refresh and the project now deploys successfully.
Here are the steps:
Close Visual Studio
Navigate to YourSolution/Packages/
Delete everything except packages.config
Reopen the solution in Visual Studio
Right click on solution and select "Manage Nuget Packages"
Click the "Restore" button that appears at the top of the dialog window
Rebuild the solution and it should deploy properly
I am a newbie and I am facing some strange issues with my Joomla 3.1.1 installation. Whenever I try to do a Joomla global check-in, I get the following error:
SQL=SELECT module FROM SOM_modules WHERE id = table-name
*This is true for all tables
Further, when I try to edit the template custom CSS file from the back-end, I get the following error:
SQL=SELECT module FROM SOM_modules WHERE id =
MTAwNTE6Y3NzL3J0X2RpYW1ldHJpY19yZXNwb25zaXZlLWN1c3RvbS5jc3M=
I am facing the same error even when I try to purge Joomla cache.
In all cases, it only says "An error has occurred" and there is a preceding 0 before the errors above. I presume that is the SQL error 0.
Kindly help. I have checked the forum and googled for hours but can't find any solution. I have also tried resetting directory and file permissions even to 777 - to test, still no luck.
Config Details:
Joomla! version: 3.1.1
PHP version: 5.3.1
MySQL version: 5.5.31
Host: Private VPS
Finally, this issue is resolved. The issue was with another extension called "Content Statistics". Somehow this extension messed up the entire backend. It took quite a lot of time to figure out which extension had caused the problem
After uninstalling the extension and all related modules and plugins, the site has become fully functional again. No more SQL=0 errors and I am being able to edit all css files from the backend. – Mangesh