cross
New Foswiki release 2.1.6 is available with important security fixes.
Sourceforge foswiki email lists being discontinued. Subscribe to the new Foswiki announce and discuss lists at MailingLists
You are here: Foswiki>Tasks Web>Item13188 (05 Jul 2015, GeorgeClark)Edit Attach

Item13188: WysiwygPlugin upload rest handler is missing - Upload fails with 404

pencil
Priority: Urgent
Current State: Closed
Released In: 2.0.0
Target Release: major
Applies To: Extension
Component: WysiwygPlugin
Branches: master
Reported By: GeorgeClark
Waiting For:
Last Change By: GeorgeClark
Attachment upload from Wysiwyg / TinyMCE editor fails with 404.

The plugin does not register an upload handler:

ERROR: (404) Invalid REST invocation - /WysiwygPlugin/upload does not refer to a known handler

  • Edit an existing topic
  • Click on paperclip, choose upload attachment
  • Select a file, press upload
  • Fails with 404

Confirmed locally and on trunk.foswiki.org

-- GeorgeClark - 06 Jan 2015

Crawford. Your checkin deleted the upload handler without providing an alternative:

commit bba8feccb71175a0e4907aba001b7be9cc13fbfb
Author: crawford <git@c-dot.co.uk>
Date:   Fri Nov 7 14:44:47 2014 +0000

    Item12705: open a can of worms, and worms will escape. Spacing in verbatim fixed, and a lot of confusion about character sets (not mine, thankfully) refactored out. There's still an issue with the TMLhtml class causing random roundtrip tests to fail, but i think it's a problem with the tests, foremost. There is one expected-to-fail test that covers it.

-- GeorgeClark - 06 Jan 2015

It's a deeper issue than at first appears.

Done, though upload doesn;t seem to save any data. Need to look again.

-- CrawfordCurrie - 07 Jan 2015

I've "cleaned" and have tried to get wysiwyg working here, and notice several problems.
  1. It's back to using the bin/rest/WysiwygPlugin/upload It lost the change I made to use bin/upload
  2. It does a GET to run the upload, rather than a POST
  3. Also check_manifest found a bunch of files in git that are not in the MANIFEST file.

-- GeorgeClark - 08 Jan 2015

  1. All can say is "no it isn't"
  2. Erm. No, it doesn't! Try clearing the browser cache.
  3. We don't ship .uncompressed.js, do we?

-- CrawfordCurrie - 08 Jan 2015
 
Topic revision: r9 - 05 Jul 2015, GeorgeClark - This page was cached on 20 Mar 2018 - 10:12.

The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License