Title: fancybug's Replies | WordPress.org

---

# fancybug

  [  ](https://wordpress.org/support/users/fancybug/)

 *   [Profile](https://wordpress.org/support/users/fancybug/)
 *   [Topics Started](https://wordpress.org/support/users/fancybug/topics/)
 *   [Replies Created](https://wordpress.org/support/users/fancybug/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/fancybug/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/fancybug/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/fancybug/engagements/)
 *   [Favorites](https://wordpress.org/support/users/fancybug/favorites/)

 Search replies:

## Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Version 5 – great step backwards](https://wordpress.org/support/topic/version-5-great-step-backwards/)
 *  [fancybug](https://wordpress.org/support/users/fancybug/)
 * (@fancybug)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/version-5-great-step-backwards/#post-10959878)
 * I hope the ‘new kids’ on the code will try not to destroy such an advanced and
   well-named CMS that is WordPress 🙂
 * Let’s contribute to make changes (at least) work ^^
    (if we can, of course)
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Gutenberg = updating failed](https://wordpress.org/support/topic/gutenberg-updating-failed-2/)
 *  Thread Starter [fancybug](https://wordpress.org/support/users/fancybug/)
 * (@fancybug)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/gutenberg-updating-failed-2/#post-10959708)
 * You’ll tell me if it’s of some use…
 * After disabling the ‘classic editor’ plugin (not deleted it), came back to the
   edition page with, of course, Gutenberg editor; tried some link insertion on 
   some text… got the ‘update fail’ on automated update, CTRL+SHIFT+J got me:
 *     ```
       Error while calling actor 'parentProcessTarget's method 'ensureCSSErrorReportingEnabled' Argument 1 of InspectorUtils.getAllStyleSheets is not an object. protocol.js:1021:5
       ensureCSSErrorReportingEnabled@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/targets/browsing-context.js:1012:9
       handler@resource://devtools/shared/base-loader.js -> resource://devtools/shared/protocol.js:1178:21
       onPacket@resource://devtools/shared/base-loader.js -> resource://devtools/server/main.js:1721:15
       send/<@resource://devtools/shared/base-loader.js -> resource://devtools/shared/transport/local-transport.js:64:11
       exports.makeInfallible/<@resource://devtools/shared/base-loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14
       exports.makeInfallible/<@resource://devtools/shared/base-loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14
       protocol.js:1024:7
       Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
       page_performance.js:18
       Unchecked lastError value: Error: Promised response from onMessage listener went out of scope page_performance.js:18
       Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
       page_performance.js:18
       Unchecked lastError value: Error: Promised response from onMessage listener went out of scope
       page_performance.js:18
       Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
       page_performance.js:18
       Unchecked lastError value: Error: Promised response from onMessage listener went out of scope page_performance.js:18
       Unchecked lastError value: Error: Promised response from onMessage listener went out of scope page_performance.js:18
       Error while calling actor 'parentProcessTarget's method 'ensureCSSErrorReportingEnabled' Argument 1 of InspectorUtils.getAllStyleSheets is not an object. protocol.js:1021:5
       ensureCSSErrorReportingEnabled@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/targets/browsing-context.js:1012:9
       handler@resource://devtools/shared/base-loader.js -> resource://devtools/shared/protocol.js:1178:21
       onPacket@resource://devtools/shared/base-loader.js -> resource://devtools/server/main.js:1721:15
       send/<@resource://devtools/shared/base-loader.js -> resource://devtools/shared/transport/local-transport.js:64:11
       exports.makeInfallible/<@resource://devtools/shared/base-loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14
       exports.makeInfallible/<@resource://devtools/shared/base-loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14
       protocol.js:1024:7
       Error while calling actor 'parentProcessTarget's method 'ensureCSSErrorReportingEnabled' Argument 1 of InspectorUtils.getAllStyleSheets is not an object. protocol.js:1021:5
       ensureCSSErrorReportingEnabled@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/targets/browsing-context.js:1012:9
       handler@resource://devtools/shared/base-loader.js -> resource://devtools/shared/protocol.js:1178:21
       onPacket@resource://devtools/shared/base-loader.js -> resource://devtools/server/main.js:1721:15
       send/<@resource://devtools/shared/base-loader.js -> resource://devtools/shared/transport/local-transport.js:64:11
       exports.makeInfallible/<@resource://devtools/shared/base-loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14
       exports.makeInfallible/<@resource://devtools/shared/base-loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:109:14
       protocol.js:1024:7
       Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
       page_performance.js:18
       Unchecked lastError value: Error: Promised response from onMessage listener went out of scope page_performance.js:18 
       ```
   
 * I’m not sure at all it’s of any use.
 * Thing is I also had some 403 each time: autosaves?_locale=user
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Downgrade Previous WP](https://wordpress.org/support/topic/downgrade-previous-wp/)
 *  [fancybug](https://wordpress.org/support/users/fancybug/)
 * (@fancybug)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/downgrade-previous-wp/#post-10957887)
 * [@giac](https://wordpress.org/support/users/giac/):
 * [https://wordpress.org/support/topic/downgrade-to-4-9-8/](https://wordpress.org/support/topic/downgrade-to-4-9-8/)
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Downgrade Previous WP](https://wordpress.org/support/topic/downgrade-previous-wp/)
 *  [fancybug](https://wordpress.org/support/users/fancybug/)
 * (@fancybug)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/downgrade-previous-wp/#post-10957845)
 * I did this : [https://wordpress.org/plugins/classic-editor/](https://wordpress.org/plugins/classic-editor/)
 * Works allright.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Downgrade to 4.9.8… Solution!](https://wordpress.org/support/topic/downgrade-to-4-9-8/)
 *  [fancybug](https://wordpress.org/support/users/fancybug/)
 * (@fancybug)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/downgrade-to-4-9-8/#post-10957838)
 * You can also use the [https://wordpress.org/plugins/classic-editor/](https://wordpress.org/plugins/classic-editor/)
 * Works great like old times for me 😉
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Gutenberg = updating failed](https://wordpress.org/support/topic/gutenberg-updating-failed-2/)
 *  Thread Starter [fancybug](https://wordpress.org/support/users/fancybug/)
 * (@fancybug)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/gutenberg-updating-failed-2/#post-10957833)
 * Ok, I’ll go: [https://wordpress.org/plugins/classic-editor/](https://wordpress.org/plugins/classic-editor/)
 * Then it works all good!
 * Damn!
    Solved!
 * PS: what a great ‘progress’ is Gutenberg ^^
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Downgrade Previous WP](https://wordpress.org/support/topic/downgrade-previous-wp/)
 *  [fancybug](https://wordpress.org/support/users/fancybug/)
 * (@fancybug)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/downgrade-previous-wp/#post-10957799)
 * Exactly!
    Gutenberg = bullet in the foot 🙁
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[FancyBox for WordPress] Gallery shows only the first picture after latest update](https://wordpress.org/support/topic/my-gallery-shows-only-the-first-picture-after-latest-update/)
 *  [fancybug](https://wordpress.org/support/users/fancybug/)
 * (@fancybug)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/my-gallery-shows-only-the-first-picture-after-latest-update/#post-10860237)
 * @mplub
 * Updated.
    Problem solved concerning the ‘direct to page’ image. Still bad borders
   applying on most images (not so annoying, just do not allow borders…) A strange
   behaviour when passing from an image to another: first image stays a bit behind
   the next/new one openned in fancybox.
 * Thanks for the quick fix anyway.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[FancyBox for WordPress] Border not fitting and strange white line](https://wordpress.org/support/topic/border-not-fitting-and-strange-white-line/)
 *  [fancybug](https://wordpress.org/support/users/fancybug/)
 * (@fancybug)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/border-not-fitting-and-strange-white-line/#post-10859895)
 * Yep, fancy box plugin is just NOT WORKING anymore 😀
 * [https://wordpress.org/support/topic/my-gallery-shows-only-the-first-picture-after-latest-update/#post-10859848](https://wordpress.org/support/topic/my-gallery-shows-only-the-first-picture-after-latest-update/#post-10859848)
 * *send vibes to a prompt resolution* 😉
 * BTW, I had too the horizontal white bar at the bottom of the image and the non-
   fitting borders on many images when using 3.1.2.
    -  This reply was modified 7 years, 6 months ago by [fancybug](https://wordpress.org/support/users/fancybug/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[FancyBox for WordPress] Gallery shows only the first picture after latest update](https://wordpress.org/support/topic/my-gallery-shows-only-the-first-picture-after-latest-update/)
 *  [fancybug](https://wordpress.org/support/users/fancybug/)
 * (@fancybug)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/my-gallery-shows-only-the-first-picture-after-latest-update/#post-10859848)
 * [@mplusb](https://wordpress.org/support/users/mplusb/)
 * I have exact same ‘direct to image page’ bug since today’s update of fancybox.
   
   Check: -http://www.lornet-design.net/les-voies-des-saigneuses/
 * And any other pages with image on this website.

Viewing 10 replies - 1 through 10 (of 10 total)