lkraav

Of course not torches and pitchforks. But wp-content/debug.log is a valuable thing. By cluttering it up with tons of crap, you waste a lot people’s time around the world, trying to deliver projects with your plugin.

+1 good to know WooCommerce gallery support is on the way.

https://relatedpostsforwp.com legit known developers are behind this. Lite version at https://www.ads-software.com/plugins/related-posts-for-wp/

I think we already solved that part, Vlad.

I just discovered that activation-cycling the plugin brings the menu items back.

But not sure if it guarantees correct functionality.

OK I’m pretty sure I know this is. Dependency Minification needs to exclude your stuff. Taking a shot at that, reporting back soon.

I guess I can try that on WP Engine staging feature. Will be reporting back. Simple Maps worked fine when we first implemented it back in April 2014. This issue started some time towards the end of the year.

I’ll just paste the errors here:

“NetworkError: 403 Forbidden – https://maps.googleapis.com/maps/api/js/StaticMapService.GetMapImage?1m2&1i1916518&2i3453652&2e1&3u15&4m2&1u432&2u200&5m5&1e0&5sen-US&6sus&10b1&12b1&token=41390”

“NetworkError: 403 Forbidden – https://maps.googleapis.com/maps/api/js/ViewportInfoService.GetViewportInfo?1m6&1m2&1d30.25515284551912&2d-97.77085373882517&2m2&1d30.278133507029207&2d-97.71451405254237&2u15&4sen-US&5e0&6sm%40302000000&7b0&8e0&9b0&callback=_xdc_._3469qo&token=78578”

Finally, from: https://maps.googleapis.com/maps/api/js/AuthenticationService.Authenticate?1shttp%3A%2F%2Fwww.advadm.com%2Fpractice-assessment%2F&5e1&callback=_xdc_._o9eoou&token=121648 we get

“NetworkError: 403 Forbidden – https://maps.googleapis.com/maps/api/js/AuthenticationService.Authenticate?1shttp%3A%2F%2Fwww.advadm.com%2F&5e1&callback=_xdc_._25qrr5&token=49246”

I take this back. It’s a bit deceptive that being on Adminimize settings page disables all minimizes. This could probably be expressed more visibly with a big CAPITAL LETTERS banner up top, esp. for new users. So to test any result, you need to have another tab open to load another admin page.

I’m seeing that if I just enable to plugin on a subsite, hiding things for Admin role doesn’t seem to be doing anything for the Super Admin. I’m going to dig into the code and see how the admin role check is actually made.

Doesn’t look like the plugin is much tested for multisite at this point.

Based on https://stackoverflow.com/a/18653657/35946 I would say this is the better version:

preg_match_all( '/<iframe[^>]+>.*?<\/iframe>/', $content, $matches );

It won’t match an iframe without a closing tag. But I don’t see any ifs and buts about it: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe?redirectlocale=en-US&redirectslug=HTML%2FElement%2Fiframe#Summary says opening and closing tags are mandatory, so I’d say the plugin doesn’t need to handle invalid HTML.

Noticed the same thing. But what’s the alternative code proposition?

it is possible to easily restore functionality by writing

var ga = __gaTracker;

into custom code panel? it definitely eliminates javascript errors, but i’m still seeing event tracking flatline.

__gaTracker is ridiculously noisy to write everywhere.

Still present on 4.4.6

Duplicates:

https://www.ads-software.com/support/topic/error-you-must-activate-this-plugin-from-the-network-dashboard?replies=2

https://www.ads-software.com/support/topic/plugin-better-wp-security-multisite-problem?replies=10

It’s impossible to know whether everything related to new site creation actually fires, when iThemes Security just dies in the middle of everything.

I can confirm – only disabling 304 header fixed things again on 1.4.1.