Roundcube Community Forum

News and Announcements => General Discussion => Topic started by: releasethebats on June 12, 2019, 06:53:19 AM

Title: 'view attachment' greyed out & cannot flag messages
Post by: releasethebats on June 12, 2019, 06:53:19 AM

Hello - I have roundcube working in a small office environment, all seems ok but I must have made a config error as no user can view an attachment such as pdf in any browser [can save &/or download] plus we get an error message when we attempt to flag a message [unable to mark message]
I've compared config files regarding mimetypes with other working roundcube installs and they are the same [default null settings.]
Apache has the correct mimetype file
Any ideas....it's driving me around the bend.
Using Bitnami Roundcube Stack 1.3.9-2

More info if needed.
Regards
G

Title: Re: 'view attachment' greyed out & cannot flag messages
Post by: SKaero on June 12, 2019, 08:42:28 AM

It sounds like a JS error, are there errors in the browser JS console?

Title: Re: 'view attachment' greyed out & cannot flag messages
Post by: releasethebats on June 13, 2019, 04:02:17 AM

Thanks for yr reply - I get this error when I attempt to flag a message [firefox] :

The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it.

Does this point to a config prob?
Thanks again
G

Title: Re: 'view attachment' greyed out & cannot flag messages
Post by: releasethebats on June 13, 2019, 04:58:02 AM

updated error received -
The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it. watermark.html

Title: Re: 'view attachment' greyed out & cannot flag messages
Post by: SKaero on June 13, 2019, 10:53:07 AM

Well thats not a JS error so it most likely something else. When you try to flag a message does anything show up in the Roundcube error log?

Title: Re: 'view attachment' greyed out & cannot flag messages
Post by: releasethebats on June 13, 2019, 11:10:11 AM

Hello again - unfortunately nothing corresponds with this error in any of the RC logs....