In a web site I have written I used to copy a table from Libreoffice Calc into ckeditor4 without problems (back in June 2019). Now it is copied as an image and an image is uploaded (image uploading has been working fine by itself).
Besides starting with a very basic configuration and adding features one by one I am clueless about this behaviour change. Going back to ckeditor 4.11.4 hasn't helped. I wonder if this is caused by recent browser changes as the ckeditor configuration has been stable.
Observed with:
Firefox 70.0.1 on Linux Mint 19.1.
Firefox 70 on Windows 10.
MS Edge
Chrome on Windows
Things work correctly with:
Chromium 78.0.3904.108 on Linux Mint 19.1.
The issue should be resolved with https://github.com/ckeditor/ckeditor4/issues/3585 fix which will be available with CKEditor 4.13.1 version. The version which fix should be released very soon (i a couple of days). Follow https://ckeditor.com/blog/?category=releases&tags=CKEditor-4 for blog post about the release. If you will still struggle with the issue after upgrading to 4.13.1, report a bug on CKEditor4 Issue Tracker.
Related
We have a pretty huge HTML / JavaScript application written in a 15 year span that several programmers updated, edited and patched. We use this application on our computers (about 60 PCs) to teach languages online. The PCs that are used by our teachers are all Windows 8.1 (last update made in 2015), and the current IE version that's running the application is (it works only on IE):
Version: 11.0.9600.17937
Update version: 11.0.22
The decision to stop updating the computers was made due to the worry of compatibility issues. I'm taking over the position of the previous IT guy and I think it would be mandatory to update all machines with Windows 10 and the latest version of IE.
I would like to know your opinion and if there could be any compatibility issues between the IE11 version we are currently using and the latest version available on Windows 10.
I'm going to test myself the whole thing anyway.
Thank you for your help.
I am relatively new to Hadoop and have been trying to set up a development environment for a project I am involved with (CentOS 6.5 is the OS). I originally set up the environment using Ambari 1.7 and installing the Hortonworks Data Platform version HDP-2.2.0.0-2041.
Now, I am trying to upgrade to Ambari 2.0.1 and HDP-2.2.6.0.
Ambari upgraded with no problems at all. I also was able to register the new version of HDP through the Ambari Manage Version page. That all went fine.
The problem is when I try to finish the upgrade. The instructions say to go from the Admin menu to "Stack and Versions" then the "Versions" tab. There, I am supposed to see my registered versions and a link to complete the upgrade. However, all I get is a blank page.
FYI, I tried multiple browsers to rule out a browser issue. I tried Firefox and Opera. (I've heard that Chrome is no longer supported for CentOS so didn't try that).
Anyone know why this page would just be blank and/or how I can fix it?
Thanks!
Tom
BTW, I tried to post images, but I don't have enough reputation points so I can't. You'll have to take my word for it that Manage Versions is showing the correct versions but the Versions tab under Stack and Versions is completely blank.
Have you clicked on button on the picture? Ambari redirects me to Versions page automatically, when I am doing that:
Part 1 - Description of the problem
I have the DK2 and I am working on a VR project. This project uses FirefoxNightly. I've downloaded it and installed the WebVR Enabler Add-On
Got this from http://mozvr.com/downloads/
I have also downloaded and installed the latest SDK and Runtime for Windows from https://developer.oculus.com/downloads/
I am also getting this on the Oculus Configuration Utility (while the oculus is plugged in):
However, I have gone on another computer with windows.. installed everything just like on this windows computer and it clearly shows the Oculus Rift connected properly but the head tracking still not working.
EDIT: I just tried connecting the oculus rift to this "second" pc ( dell laptop ) and now it doesn't even recognize the oculus rift. Still no head tracking.
EDIT 2: I tried installing everything on a third PC without success. I'm getting "service unavailable" on the Oculus Configuration Utility
My display mode is set as shown in the image.
Part 2 - Questions
What am I doing wrong? Is there a step I forgot to do? The weird thing is, I have the same project running on Mac without having any problems. Yes, on windows I can see the screen through the oculus rift but head detection is just not present.
Part 3 - list of possible fixes that did not work
This reddit post talks about the firewall issue however I tried the oculus rift with the firewall disactivated without success.
This reddit post talks about a possible fix by reinstalling everything and updating certain drivers.. however I have followed this fix step by step without success.
This oculus forum post talks about the issue and one person proposes a fix that worked for him/her. I followed the fix without success.
Part 4 - System info
If you require specific translations let me know. It is in French.
Part 5 - List of things I have tried that have been thought of
I have reinstalled everything. SDK (is not even needed in fact), runtime, firefoxnightly, webvr add-on multiple times
I have rebooted my computer multiple times
I have tried the different Rift Display Mode
Basic demos from mozvr.com and other webvr based projects work fine but head tracking does not work.
My Oculus is not broken (maybe for windows), it works fine for the Mac.
I've tried using different HDMI cables and Different minUSB-USB cables without success.
Part 6 - Quotes from the forum
First post
This sounds like the same issue a lot of us are having with the 0.5
and 0.6 versions. It's not something wrong with the cables, but with
the Runtime itself. Direct-mode works flawlessly and in Extended mode
the rift still displays a picture, altho without any tracking etc from
the runtime. Hoping it'll be fixed in the next update.
I've seen head tracking break in Firefox Nightly sometimes but I can usually solve it by restarting the browser once or twice, assuming that the hardware and Oculus side of things is working correctly.
Today, most games made for the Oculus Rift are based on specific versions of the Oculus Rift. I found this GUI desktop application that seems to solve most of those problems.
The idea is to install all Oculus Rift Runtime versions and then use the GUI to switch between each version.
The link above is to a reddit post that talks about how to install the application and the different runtimes.
You must install the runtimes from oldest to newest otherwise you'll run into some difficulties, like I unfortunately did. If I'm not mistaken runtime version 0.8 is very buggy and I never really got it to work.
Good luck.
This is what I did to get the Oculus DK2 working on my Windows 10 Laptop:
Create a windows restore point before you start this.
Download oculus_runtime_rev_1_sdk_0.4.4_win.exe from the Oculus downloads page.
Run the installer. Do not restart your computer when prompted.
Go to C:\Program Files (x86)\Oculus\Service folder, right click on OVRServer_x86.exe and go to properties.
In the compatibility tab, check Windows 8 mode, and Run As Administrator.
Run OVRServer_x86.exe
That's it.
The Good News
You should now be able to run direct to rift games. The HELIX rollercoaster app works well. So does the 6000 Moons demo. Most others do not. Depending on the game, you may need to go to your windows display settings, and fiddle with the screen resolution and rotation of the Oculus display.
The Bad News
Your computer may not restart. When I did the above, and later restarted, the computer hung on the windows loading page. I had to go into advanced start mode and load a system restore point. Definitely not the best user experience, but at least I got something working.
I own a ZTE Open, UK edition. I tried upgrading from 1.0 to 1.2 following these instructions.
https://hacks.mozilla.org/2014/01/upgrading-your-zte-open-to-firefox-1-1-or-1-2-fastboot-enabled/comment-page-1/#comments
The update I installed came from ZTE themselves, and was not a custom, or third-party ROM.
The upgrade worked smoothly and had no errors, and I was prompted to reboot my device. Since then it has been in a reboot loop.
I've tried entering recovery mode and restoring to factory settings, but nothing worked. Likewise, I've tried wiping the cache from recovery mode, but with no success.
Any help would be much appreciated.
EDIT: Also worth adding that I cannot access the phone via ADB or Fastboot.
I had a similar problem when I tried to update to 1.2 using the same tutorial
(I have the US model).
The problem seems to be jumping from 1.0 to 1.2. You need to load 1.1 first, then 1.2.
The solution for me was to download both of the ZTE Official 1.1 updates linked on the
ZTE Open device page for my region (on the mozilla developer website under the heading "Upgrading Firefox OS" linked below).
Do not change the downloaded files names, just unzip them both and put both .zip files on the root of an sd card and reboot into recovery.
You should be able to flash one of the two files using the install update choice, the other will give an error (I can't read the full filenames on the phone so I'm not sure which one actually worked for me, that is why I say just try both.)
After flashing you should clear cache, wipe data and reboot.
If all goes well you should have a fresh factory load of 1.1 on you phone and you can now follow that tutorial to upgrade to the developer preview of 1.2.
If your recovery won't flash either of the official EU 1.1 updates you may have some how replaced your stock EU firmware with a stock US firmware, one update will say signature verification error and the other one will give another longer error 7 something or other. I replaced my US firmware with an EU firmware (v1.0) without realizing it and thought my phone was totally bricked because I couldn't get any US 1.1 firmware to flash and I couldn't get to fastboot or adb to manually flash a build (I loaded EU 1.0 version then used fastboot to flash a 1.4 build that wouldn't boot). The solution to that problem was to load an official EU 1.1 .zip from recovery and then load the US 1.2 developer preview from fastboot which replaces the EU recovery and let me flash an official US 1.1 .zip build.
Try not to mix and match firmwares from different regions, the Open doesn't seem to like that.
I was able to get the ZTE preview of 1.2 to work but it has a nasty bug with the notification bar so I went back to the official 1.1 build so you may want to stay at 1.1. If you do load 1.2, the key to using the notification bar is to tap and hold above the screen and slowly "roll" your finger onto the bar until you can pull it down (that might not make much sense now but if you get 1.2 loaded you will understand).
Hope that helps.
https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN
When upgrading to V1.1 before attempting to upgrade further, I might be able to explain why #Foo observed that only one of the two ZTE files worked (ZTE file links: European, US - each has two files). I didn't hit the reboot loop, but I was unable to install what looked like the right file.
The reason is that there are two links for upgrading to V1.1.0B02 - one link is labeled "(for V1.0)" and the other is labeled "(for V1.1)". This really tripped me up as I was scanning the list for 1.1 and jumping over the (right) file labeled for 1.0.
Very clearly, if you are upgrading from 1.0, then you need the "V1.1.0B02(for V1.0)" version. Just downloading both and trying each one may be easiest, but it vexed me to not understand this.
If you pick the wrong one, I found the error message (E:signature verification failed) to be very unhelpful after booting into recovery and attempt to flash from the SD card.
I just purchased a MacBook air and for some reason whenever I'm testing a project locally (on MAMP) I'm forced to refresh the page about 6 or 7 times for the changes that I've made in the text editor to be reflected in the browser. Originally I thought that this was because I wasn't using private browsing. So, I switched to chrome incognito. That didn't work. So, then I switched to firefox and then opera. That, too didn't work. These problems happen both with backend and front end code. It's very strange it makes the task of local development very very difficult and time consuming. Any ideas?
are you using MAMP 2.2 with php 5.5 enabled? Then it's likely that it's because OPcache is enabled per default. See here: Stop caching for PHP 5.5.3 in MAMP