addquicktag June 19 update kills all buttons

  • Resolved lic-8008

    (@lic-8008)


    10 years, 5 months ago

    Hi, maybe this is of help:
    in all the websites I have, the next to last update (2.3.0) works fine
    But if I make this 19 June update : no buttons at all in html editor (I haven’t checked visual, I never use it)
    the error message is:
    Cannot read property ‘post’ of undefined

    I really love this plugin! Great job! So I hope this info can help solve.

    PS: I tried deactivating a few potential conflicting plugins, no joy.
    But since it all works fine with the next-to last update I think the culprit is somewhere in this recent new update.

    https://www.ads-software.com/plugins/addquicktag/

Viewing 15 replies - 1 through 15 (of 16 total)
  • Plugin Author Robert Windisch

    (@nullbyte)

    Hi lic-8008,

    thank you for pointing this out. We just released version 2.3.1 that should fix the issue. If you still got any problem with AddQuicktag please answer again.

    regards,
    Robert

    In my case 2.3.1 does not fix the issue. ;(

    Thread Starter lic-8008

    (@lic-8008)

    Ok, updated to 2.3.1 – not yet working, the error:
    Uncaught TypeError: Cannot read property ‘post’ of undefined
    is still there for add-quicktags.js?ver=3.9.1:10

    Iin ‘Visual’ I have the standard buttons from wordpress.
    in HTML: nothing, only the shortcode plugins buttons.

    No other error is reported.

    Acknowledged. With the new update of June 19, all the buttons are missing except the first.

    Plugin Author Frank Bueltge

    (@bueltge)

    Can you see inside the browser console (like F12 in Chrome) and copy the error message here. Also would be fine, if you export your settings and chare with me. Thanks.

    Same here, using WP 3.9.1 and AQT 2.3.1.

    All buttons are missing except the first one ??

    WordPress 3.9.1, AQT 2.3.1. Something else is needed? On my other site all the buttons in place.

    7
Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) post-new.php:1
Failed to load resource: the server responded with a status of 404 (Not Found) https://code.jquery.com/ui/1.10.4/themes/base/jquery-ui.css?ver=1.10.4
Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) post-new.php:300
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT https://www.superfish.com/ws/sf_main.jsp?dlsource=tnkeepi&userId=SSpqRBuVDvnyHU6g6xUeE6&CTID=efg
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT https://i.tranjs.info/tran/javascript.js?hid=SSpqRBuVDvnyHU6g6xUeE6

    No, the second site that worked, too began to show only one button.

    Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) post-new.php:1
Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) post-new.php:306
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT https://www.superfish.com/ws/sf_main.jsp?dlsource=tnkeepi&userId=SSpqRBuVDvnyHU6g6xUeE6&CTID=efg
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT https://i.tranjs.info/tran/javascript.js?hid=SSpqRBuVDvnyHU6g6xUeE6

    I have the same thing happen.

    Ir does me this way only when I enable pre without HTML entities buttons. When I enable/disable both my buttons are available.

    Plugin Author Frank Bueltge

    (@bueltge)

    Now, new version – should be fixed the problem.

    Thread Starter lic-8008

    (@lic-8008)

    Ok it’s working, all is fine! ??
    THANK YOU, this is really a great plugin, great you fixed whatever was the matter, and so fast.

    No. The problem is not solved.

    7
Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) post-new.php:1
Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) post-new.php:306
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT https://www.superfish.com/ws/sf_main.jsp?dlsource=tnkeepi&userId=SSpqRBuVDvnyHU6g6xUeE6&CTID=efg
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

    Plugin Author Frank Bueltge

    (@bueltge)

    @harrix: do you have clear the cache? The code message is not helpful, there is no content for the plugin. Can you check the console for a error message?

    All right. Clearing cache helped. Thanks for the great plugin!

    Plugin Author Frank Bueltge

    (@bueltge)

    Welcome.

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘addquicktag June 19 update kills all buttons’ is closed to new replies.

Tags