jreeve

It looks like the font styles aren’t being applied–they’re there, but crossed out, so something else must be overriding them. Yet unchecking other font styles, like the site-wide font we’re using from TypeKit, doesn’t seem to have any effect–the a11y font styles are still crossed out.

Anyway, I tried loading my site on IE on a Windows computer, and everything seems to be OK, so I’ll mark this topic as resolved. It must be a VM-specific thing going on, although I can’t imagine what it might be.

Hm, that’s odd. I’ll see if I can test it on some more Windows machines, since the only ones I’ve tried it with so far are the MS-provided IE test VMs, but as far as I know, they use default security settings, since they’re just vanilla boxes. Both IEs seem to be loading custom fonts fine, since it loads the site font and WP’s Dashicons font.

Could it be an operating system thing? Both the IE 10 and 11 test VMs I used run Windows 7.

They don’t work on my site, MLA Commons (commons.mla.org), on any version of IE. I just tested it on IE 11 and IE 10, and the toolbar is there, but the icons are gone. The icons show up on all other browsers.

Mike and Ryan,

What version of bp-group-documents are you using? It would seem like this was fixed in 1.7, but if it isn’t, this will affect me, too, and I’ll look into it.

Hi lenasterg,

I fixed this issue in a pull request here:

https://github.com/wp-plugins/bp-group-documents/pull/2

Let me know if it works for you.

Crashtest,

Feel free to download my patched version, which should fix your problem:

https://github.com/mlaa/bp-group-documents/tree/escaping-fix

-Jonathan

Hi lenasterg,

Here’s some more of what I discovered about this bug:

– Double quotes, single quotes, and apostrophes are escaped with backslashes, and the backslashes appear in the final display. Ampersands and other punctuation (from what I’ve tested) don’t seem to be affected.
– The data that’s sent from the browser isn’t escaped in this way, but $_POST is getting the escaped version, so it must be something with PHP that’s causing this, unless something happens to the $_POST in bp-group-documents that I haven’t discovered.
– Some writing about this (like this stackoverflow thread) suggests that this has something to do with PHP magic quotes, yet I seem to have this disabled, and I’m still seeing this behavior. Running get_magic_quotes_gpc() on my install returns false.
– there are a few lines in templatetags.php that see to address the magic quote scenario, yet they rely on get_magic_quotes_gpc(), which is returning false in my case.
– removing the line that starts if (get_magic_quotes will properly strip backslashes from the titles of files, but not from descriptions.

Hope this helps.

Nevermind, can’t seem to reproduce this on fresh installs. Will revive this if the problem occurs again.

What I tried was:

– On /sites, the group “Sustainable Humanities” says it was “active 3 weeks ago,”
– Joined the group “Sustainable Humanities”
– /sites says the group was “active 30 seconds ago”

Maybe it’s not just any update, but membership updates that are causing this? Or maybe it’s something completely different on my end.

I think I fixed this issue in my fork here:

https://github.com/mlaa/bp-group-documents

The code that fixes the issue is here:

https://github.com/mlaa/bp-group-documents/commit/d407ca3e8688aee46beee59026badbb3cc25fc72

Seconded. The syntax highlighting appears to be broken on WordPress 3.5.1. It would be awesome if the plugin could be updated to work with the current WordPress version.