An error occurred. We're sorry, but for some reason we can't open this for you.

Created on 20 March 2024, 9 months ago
Updated 3 August 2024, 5 months ago

Problem/Motivation

I'm having trouble with the Microsoft Document Viewer module on a Drupal 10 site. Every time I try to view a document on a media entity page, I get this error message: "An error occurred. We're sorry, but for some reason we can't open this for you." The module's page says it might not work locally, so I tried it on the drupal site hosted on Acquia, but the error still shows up. I even talked to Acquia to see if they could find anything wrong, but they didn't see any errors in their logs.

Steps to reproduce

  • Install the Microsoft Document Viewer module on a Drupal 9 site hosted on Acquia.
  • Go to a media entity page where the module should show a document.
  • Notice the error message: "An error occurred. We're sorry, but for some reasons we can't open this for you."

Proposed resolution

Right now, I'm not sure how to fix this because we can't find any errors that point to what's going wrong.

Remaining tasks

  • Need to figure out why the error message keeps showing up with the Microsoft Document Viewer on Acquia-hosted Drupal site.
  • Find out why there are no helpful errors in the logs.

User interface changes

The problem is with an error message showing up and not displaying the document inside the MD viewer.

API changes

No API changes.

Data model changes

No data model changes.

Additional Info

When I was trying to figure out what's wrong, I also looked at the browser's inspector on one of the media pages. I saw an error from the iframe itself, which is part of the module. It seems like the problem might be with how the iframe is set up or something else on the front end. I also want to mention that I reached out to Acquia support for help. They looked into it but couldn't find any errors in their logs that would explain why this is happening.

🐛 Bug report
Status

Closed: outdated

Version

1.0

Component

User interface

Created by

🇺🇸United States lyntechi Pennsylvania

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @lyntechi
  • 🇺🇸United States lyntechi Pennsylvania
  • 🇺🇸United States gtucker6

    I have had this issue with the gdoc_field module which does the same thing that this module does, except for Google Docs. The issue we had ultimately ended up being the .htaccess box that often appears on non-production sites to require a name and password before entering the site. Google and Microsoft can only be accessed 100% publicly, so any .htaccess restrictions that require authentication will prevent documents from showing. I hope this helps anyone debugging errors on their Pantheon and Acquia sites for these modules (gdoc_field and md_viewer).

  • Status changed to Postponed: needs info 5 months ago
  • 🇮🇳India rs.abhilash Trivandrum
  • Status changed to Closed: outdated 5 months ago
  • 🇮🇳India rs.abhilash Trivandrum
Production build 0.71.5 2024