Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Came to add an image with the new Drupal 8 CKeditor image-widget and got error when trying to access the Windows (10) shortcut to the folder in which this image sits.
When I access Symlinks on my Ubuntu 15.10 on the other hand, this does not happen;
I guess some kind of allowance is needed regarding to Windows shortcuts.
Comments
Comment #2
Benia CreditAttribution: Benia commentedComment #3
thpoul CreditAttribution: thpoul at Pixual commented@benia Not sure exactly if I understand the problem. Could you please provide step by step instructions of what you experiencing?
Comment #4
Benia CreditAttribution: Benia commentedSure.
1. Create a folder somewhere under C: and put some images in it.
2. Create a shortcut for it in Desktop.
3. Try to access that shortcut with CKeditor 8, either in-place or out-place (i.e with the backend edit form).
You might see the aforementioned error. If you don't I can't explain it; It might be a problem in the host company whom I use.
Comment #5
thpoul CreditAttribution: thpoul at Pixual commented@benia thank you for the instructions. This sounds though as a Windows related issue, not a CKEditor or Drupal one.
Comment #6
Benia CreditAttribution: Benia commentedI can't think of any reason it will happen because of Win10... In Drupal 7 (IMCE or Media modules) it never happened to me.
Comment #7
Benia CreditAttribution: Benia commented.lnk files are accessed fine at your pc with the module?
Comment #8
thpoul CreditAttribution: thpoul at Pixual commented@benia: this is not something that could be caused from the CKEditor module since the DrupalImage plugin simply uses a
file
input. What is the exact error you got? Can you post some screenshots?Comment #9
Benia CreditAttribution: Benia commentedWOW, that's wired... Now shortcut links suddenly works just fine...
There wasn't a special error at the time (too bad I didn't check the console back then).
Maybe there was a temporary problem that was fixed in one of the last Windows updates... Given I used a Windows 10 Insider preview build, it is even more likely to have been a temporary problem that was set.
Anyway, I will now close this ticket. At least now we have a base to start with in case someone else will experience it.
Comment #10
thpoul CreditAttribution: thpoul at Pixual commentedThank you for your feedback. Changing to WAD to properly reflect the status of the issue.