• “The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol.”

    Since updating to 3.3.1 Dropbox tab displays white page and Firefox inspector report the above error when making any changes in the dropbox tab or when trying to create a new job with Dropbox.

    Is that a bug introduced recently?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Intresting, there is no change in that tab. The “character encoding” will be done from WordPress and is present on my test.

    Can you set WP_DEBUG to true and than have a look if there a nother error message.

    Thread Starter sarumbear

    (@sarumbear)

    The plugin dashboard says: “WordPress database error: [Got a packet bigger than ‘max_allowed_packet’ bytes]”

    However I have max_allowed_packet=999M in the /etc/my.cnf file. Surely a Gigabyte should be enough for any plugin to work!

    I can email you admin access if you want to check this yourself.

    I think you must find out what is so big in your database. BackWPup don’t store so many data in the database.

    Thread Starter sarumbear

    (@sarumbear)

    Daniel,

    This is a fresh installation. There are just 2 pages and no posts. BackWPup is the only plugin. I cannot see how the DB has any entries larger than 999MB.

    Thread Starter sarumbear

    (@sarumbear)

    Further to diagnose the issue. I have exported the DB. The size of the file is less than 4MB. It is another proof that there is no large entry in the DB as you suggested should be the case.

    I have also noticed that once the plugin produces a white screen the toggle for Dropbox tab reverses. I.e. when you tick the option the tab disappears. It appears back when you untick the option. If you go out of the plugin page and come back again this is corrected until another white screen is generated by clicking on save. In case this begaviour may aid you…

    Thread Starter sarumbear

    (@sarumbear)

    I think I owe you an apology. It was indeed caused by a dodgy DB.

    I run the WP-Optimize plugin and it found lots of issues with the DB. Once that was done your plugin behaved correctly.

    Many thanks for bearing with me.

    np 😉

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘[Plugin: BackWPup] The character encoding of the HTML document was not declared’ is closed to new replies.