Burt

Tested Chrome 127.0.6533.120, and Safari 17.6 on a MacBook Pro (14″, 2021) running macOS 14.6.1 (Sonoma). No extensions in Safari. 1Password, uBlock Origin loaded in Chrome.

Both pages listed by @sahulap above loaded fine without any related console logs.

Also just tried Chrome 127.0.6533.73, and Safari 16.5.1 on macOS Ventura using BrowserStack. The content loaded fine in the Chrome browser. In Safari, the PDF viewer chrome loaded, but not the PDF itself. Error in console is:

[Error] TypeError: Promise.withResolvers is not a function. (In 'Promise.withResolvers()', 'Promise.withResolvers' is undefined)
Module Code (viewer.js:12202)

@sahulap What versions of macOS and browsers are you using?

• This reply was modified 3 months, 1 week ago by Burt.

@zemledelie I don’t know specifically if those messages apply here — they’re related to the rendering engine in Firefox. Do you happen to have security software installed that might be blocking outgoing requests under certain circumstances?

What happens if you go to this URL? https://zemledelie.org/wp-content/plugins/pdfjs-viewer-shortcode/pdfjs/web/viewer.php?file=/ebooks/conspects/01-shos.pdf

@zemledelie, the PDF at that link loads fine for me in Chrome and Firefox (Win64), as well as Chrome iOS. With this version, you shouldn’t need the extra line in .htaccess, but removing it is also not going to fix what’s not working for you. The issue appears to be local, perhaps a browser extension that’s causing a conflict, or perhaps a local cache that’s not been cleared fully.

@zemledelie, @mcyzyk,

Could you please provide a little more information related to how this isn’t working for you? What happens when you load a page with a PDF embedded? Are there any error messages shown on the page? Are there specific errors or messages listed in the browser’s dev console?

And perhaps, if possible, provide a link to a site that is failing.

• This reply was modified 3 months, 3 weeks ago by Burt.
• This reply was modified 3 months, 3 weeks ago by Burt.

@twistermc Deployed it to the same WPE staging environment, and it loaded PDFs without issue with both Chrome and Firefox on Windows. Good stuff!

@twistermc, I tested your develop tree with Firefox/WinX64 on a WP Engine staging environment and ran into this in the browser console:

Loading module from "https://example.com/wp-content/plugins/pdfjs-viewer-shortcode-master/pdfjs/web/viewer.mjs" was blocked because of a disallowed MIME type ("application/octet-stream"). viewer.php

I changed references to .mjs to .js on lines 598, 778, and 788 of pdfjs/web/viewer.js and copied pdf.sandbox.mjs to pdf.sandbox.js, and pdf.worker.mjs to pdf.worker.js in the pdfjs/build directory.

With those changes made, I’m not seeing browser errors, and the PDF is loading as expected. I’m certainly no Javascript expert, and I suspect that there might be some additional changes necessary to enable debugging, but you seem to be on a track that could work.

Cheers,
Burt

Look for the bpro_nouveau_friend_button_hide() function in the plugin’s includes/core.php file. The filter isn’t returning a value.

Don’t change the plugin code. Until the developer corrects the issue, you can add this to your theme’s functions.php file:

remove_filter( 'bp_get_add_friend_button', 'bpro_nouveau_friend_button_hide', 101, 1 );

function my_bpro_nouveau_friend_button_hide( $args ) {

  if ( ! function_exists('bp_nouveau') ) {
    return $args;
  }
  $moderated = bp_registration_get_moderation_status( get_current_user_id() );
  if ( function_exists( 'bp_displayed_user_id' ) ) {
    $displayed_moderated = bp_registration_get_moderation_status( bp_displayed_user_id() );
  }

  if ( $moderated || $displayed_moderated ) {
    if ( 'friends' === bp_nouveau()->members->button_args['component'] ) {
      bp_nouveau()->members->button_args = [];
    }
  }

  return $args;
}
add_filter( 'bp_get_add_friend_button', 'my_bpro_nouveau_friend_button_hide', 101, 1 );

This dupes the code from the original function in the plugin, and simply adds the last line, “return $args;”

Sounds like your hosting provider might be running an old version of PHP. I believe that the second parameter was added with PHP 7.0. PHP 7.4 is the WP.org recommended minimum currently.

@madtho Curious if you ever came up with a workable solution to this, that you’d be willing to share?

For anyone coming across this, and wondering how to download an older version…

If you select the “Advanced View” from the right sidebar of the plugin overview page, and then scroll to the bottom, you’ll find a dropdown list that allows you to download previous versions.

Thanks for the update @dungengronovius.

Any chance of merging in a pull request (https://github.com/codepress/column-shortcodes/pull/28) to address double slashes in the path? Apart from what @emaildano mentions, this can also cause the request to be blocked by certain Cloudflare rules.

@efran1526 Good to hear! It would have gotten uglier if that didn’t resolve it.

@efran1526 When editing the page, with the Column Shortcodes plugin enabled, hold down the CTRL key and click on the browser’s reload button. I suspect that you’re running into a local Chrome browser caching issue after making the change to the Javascript file.

If that doesn’t help, then you might want to look for the error messages in the console within the Developer Tools in Chrome.

btw, I’m not the developer of the plugin, just another user like you.

See here: https://www.ads-software.com/support/topic/failed-to-load-plugin-15/#post-13246794

That will allow you to get the plugin working again, until the developer releases an update with a similar fix applied.

Eric,

If you’re comfortable editing the plugin code, the workaround appears to be changing line 35 of assets/js/admin.js from using .live() to .on().

$( '#cpsh .insert-shortcode' ).live( 'click', function( e ) {

becomes

$( '#cpsh .insert-shortcode' ).on( 'click', function( e ) {

Hope this helps.