When opening Selenium IDE 2.2.0 in Firefox22, the following error message is displayed
"The following plugins were disabled due to errors while loading their code. See the Plugins section in the Selenium IDE Options dialog for individual plugin details.
sel-blocks#chris.noe"
On checking the Options >Plugin , it says that "ReferenceError: XML is not defined"
Sel Block version is 1.3
Can anyone let me know how should I fix the problem without
downgrading the Firefox version?
Also is there any other selenium IDE plugin with
for , foreach loop controls?
Sel Blocks 1.3 is not compatible with Firefox 22. There were suggestions that you can manually remove one line from the plugin to get it to work.
The good news is that the plugin author has mentioned that a new version has been submitted to the Mozilla addons website and is waiting approval. You can install the new latest version directly from here.
Related
I have installed Erlang OTP 25.0, erlide 0.56.0, Eclipse 2022-09 & Java 18. I have created a new Erlang project and module. I am facing 2 issues.
Issue #1:
Getting an error when I tried to launch the Eclipse after creating the Erlang project.
Issue #2:
When I tried to run the application, I am getting an exception "Launching App1 has encountered a problem. An internal error occurred during launching App1. Expected the service OtpNodeProxy 5756dc#null FAILED to be running, but the service has FAILED" as shown in the screenshot ErlangRunConfigException. Please help me in resolving the issue.
I have followed the procedure given below.
Installed Eclipse and Erlide plugin
Installed Erlang OTP 25.0 from https://www.erlang.org/patches/otp-25.0
Updated the environment PATH to refer to the Erlang installation path. I cross-checked this setting by typing "werl".
In Eclipse, Erlang InstalledRuntimes is automatically updated with the Erlang version 25.0. Refer to the screenshot ErlangInstalledRuntime
Created a Erlang project and module.
Edited the Hello.erl with HelloWorld code.
In Eclipse->RunConfguration, created an ErlangApplication (refer to the screenshot RunConfig-ErlangApp-Erlang). I set RunTime and Node name as shown in the screenshot RunConfig-ErlangApp-Runtime. Selected the Windows PATH as shown in the screenshot RunConfig-ErlangApp-Environment.
Hello.erl
```
-module(hello).
-export([hello_world/0]).
hello_world() -> io:fwrite("hello, world\n").
```
Images:
ErlangRunConfigException.png
ErlangInstalledRuntime.png
RunConfig-ErlangApp-Environment.png
RunConfig-ErlangApp-Runtime.png
werl output
RunConfig-ErlangApp-Erlang.png
Project structure
Eclipse Launching Error
Unfortunately, Erlang 25 doesn't load beam files older than v21, and the files included in erlide are that old. I am not really maintaining the project anymore, I can try to rebuild with v25, but can make no promises. Even then, the debugger will no longer work, it can be good to note.
The reported issue is seen with the latest Erlang version 25.0 and the older versions I have checked till 23.0. As a workaround, I have migrated to IntelliJ IDE.
HCL Connections has some kind of customized build of TinyMCE, which could be officially used as replacement for the old CKEditor. I'd like to know which version is installed. Especially on test systems I'm not sure which version is currently installed on which system.
Found out that this could be fetched from JS variables in the browser console:
tinymce.majorVersion + '.' + tinymce.minorVersion
"5.1.1"
But it misses the patch version 5.1.1-XX where XX is a number. Is there any other way how to find out detailled information about the installed version?
There is a test page avaliable on the following url: https://cnx.host/connections/resources/web/tiny.editors.connections/verify.html
When TinyMCE was successfully installed (may require a restart of at least the common app), you'll see something like this:
Tiny Editors for HCL Connections has been successfully installed. This
is release 4.1.0.15
The TinyMCE version in this release is 5.1.1-57.
The Textbox.io version in this release is 2.4.2.95.
This gave you four information:
The installation itself works. When enabled in config.js, you'll use TinyMCE instead of CKEditor in all Connections applications (Wikis, Blogs, ...)
The exact version numbers of TinyMCE = 5.1.1-57 (independent from Connection)
The Connections Editor version = 4.1.0.15 (HCL bundle of TinyMCE and Textbox.io editors)
The Textbox.io version = 2.4.2.95 (also independent from Connections, only relevant when using Textbox.io instead of TinyMCE)
The TinyMCE version we ship for connections isn't a customised build; our customisations are all done through public APIs and configuration options (including the premium plugins).
If you see 5.1.1-57, that should be an exact copy of the public 5.1.1 release available on our website. 57 is just an internal packaging build system number.
If you open the editor help dialog there should be version information there as well (but only the connections package version and current editor version, not both editor versions).
The help dialog also contains the version of the editor and the integration. This is true for both textbox.io and TinyMCE and the steps are roughly the same. I show images for TinyMCE below.
First open the "cog" menu and click on the "Help" entry:
Second select the "Version" tab to view the version:
This morning I was running Selenium with 2.32 and Firefox 25.0.1. Firefox updated to 26.0, and suddenly Selenium stopped working. It pops up the new browser window, but then just sits there prompting for a search or address. Is Selenium known to have a problem with this? Is it confused by the new prompt in the Firefox address bar? Has it already been fixed in a newer Selenium 2.3x?
While waiting for a fix, what is the easiest way to change my code to work with either Chrome or (yecch) IE10? I'd like to make my test code configurable so that others in my group can use their browser of choice (especially Chrome). I tried once to get Chrome to work by adding 'browser_name'=>'*chrome' to the new() method, but it never worked.
BTW, I am using the Perl language binding (Selenium::Remote::Driver 0.17).
Try updating selenium to 2.38.0 (latest one at the time of writing). I had something similar problem with firefox updating and then buttons not being clicked and upgrading the version solved it. Hope this solves it.
Update to selenium to 2.39.0 e.g:
<seleniumVersion>2.39.0</seleniumVersion>
I am also facing the same problem after upgrading my selenium to 2.39.0. I couldn’t solve my problem so I switched to Chrome.
Download the Chrome driver and give it the path where you invoke the browser. Then it’s easy in Chrome:
if (config.getProperty("Browser").equals("chrome")) {
System.setProperty("webdriver.chrome.driver", "path of the chromedriver");
dri = new ChromeDriver();
}
I am running ubuntu 12.04 64 bit, I have set up FB4Linux (FlashBuilder for Linux) and installed the »flash-installer« installer plugin via »apt-get«. I downloaded the latest version of the plugin-debugger from adobe and followed the install instructions from the included README.txt file. Running eclipse (Version: 3.7.2, Build id: I20110613-1736), creating a new as3 project works, build works, everything fine, I can start the debugger and step through the code BUT after a while the debugger just disconnects and stops. No error, no crashes, debug session just over.
Any Ideas?
.log
about:plugins:
Flash - Version: 11.2 r202
Shockwave Flash 11.2 r202
I think , this is happenning more fequently due the enhanced breakpoint listener support in eclipse.When a breakpoint is removed, it is trying to notify its "breakpoint specific" listeners, which were stored in the breakpoint. Of course, this will not work since the underlying marker has been deleted. but things will happen after removing break point. so one way to resolve this problem is to try to un-select
Window > Preferences > Java > Debug : Suspend execution on uncaught exceptions
may this will help you!!
The solution to this issue occurred as side effect after I applied the changes from the answer of this question. When I tried to set the compiler options to target version 11.2, which is actually installed on my system errors occurred because their were files missing in the sdk folder (which are the described changes) and I could only develop for version 11.1. Kind of wired but the update of the sdk made the debugger run stable.
I have had all sorts of bizarre errors, like the one in the title, happen when I am using the Android SDK and AVD Manager with Eclipse. Generally I just unplug the phone and plug it back in or close and reopen Eclipse but it is frustrating. Apparently Conversion to Dalvik format failed: Unable to execute dex: wrapper was not properly loaded first doesn't allow me to compile my app, i think it is because I was trying to run the emulator with some suggestions from emulator is so slow to no avail. thought i should add im running eclipse 3.5.2 on Ubuntu 11.04
Just restart the eclipse and run the project. The error arises while installing a new target version. After completion of the installation it will get fix automatically. Else restart eclipse.
I met with the same error on my Macbook. I tried one of the methods explained at this link http://techmologies.blogspot.com/2009/05/conversion-to-dalvik-format-failed-with_06.html and solved the problem.
Put the following 2 lines in the eclipse.ini file:
-vm
C:\Program Files\Java\jdk1.6.0_07\bin\javaw.exe
Please modify the 2nd line according to the actual situation.
If you have upgraded your SDK, and if you have not updated ADT plugin it will show this error. Please check it once by updating ADT plugin
I made a new installation of Eclipse in different folder(with the same SDK folder) and imported the code to the workspace & it started to work again.