imageDESIGN

I just tried downgrading to v3.4.5 and then authorizing and it worked perfectly. It appears to be an issue in the latest version – v3.4.10

FYI This issue was answered in another topic. I have over 25 GA accounts in my Google account and this fix solved the problem:

https://wpmudev.com/docs/wpmu-dev-plugins/beehive/#linking-multiple-analytics-account

Great – glad to hear it’s known and being worked on. Thanks!

Hi Mathias,
The Redirection plugin seems to solve the issue and allow me to redirect. Thanks for your assistance!

Thanks, I’ll apply those suggestions to the next update! Appreciate the feedback!

Thanks for trying this out – great to hear some feedback and that someone besides myself is using this! For some reason the .json file is no longer auto-importing properly, so as @jaappebler2 mentioned, a manual import is needed. I will update the plugin to explain this and how to do it more clearly.

Once you have the column system imported, it’s fairly easy to use. Thanks for the feedback, let me know if you got this to work for you or not @jmbalsa!

Hi Natalie,
Thanks – I know it’s a bit different, but I’ve been playing around and the free plugin is 90% there already – especially after the update you just released. The only thing I had to do was manually set the height and width of the front-end img tag in the shortcode function in class-drawattention.php (I don’t think there is a way to detect this as SVG’s don’t always have an explicit height/width).

Anyway, I just added this below line 399:

$filetype =  wp_check_filetype($img_url);
if( $filetype['ext'] == 'svg' ){
	$img_width = 1024;
	$img_height = 768;
}

So if you had a spot in the editor page to set a height & width for an SVG, it seems to work perfectly. I’ve been testing it out here if you’d like to see – https://crosslink.idhost.ca/sample-page/

The reason it has to be SVG is because the client wants to be able to zoom in on the image and see the lot dimensions – when we use a png, the small numbers are too blurry to decipher

Hi Alin,
Thanks for your patience with us users – I know support is frustrating!

If it helps, we run a dedicated server with multiple WordPress sites for our clients, we have a maintenance contract with them to keep everything up to date and secure – sites belong to the client but we do all updates and ensure everything is working for them. 9 times out of ten your plugin has the 400 error and I have to reauthorize it when I login every month. Analytics for our clients are all setup within one account, there are 100 clients in this account – this account is the one that keeps getting disconnected and requiring re-authorization. 100 is the max that Google allows in an account, we have a second account with only about 20 clients in it so far, and these seem to be staying authorized without any issues.

Let me know if you need any additional information. Thank you for the help!

@rich99 – If you’ve only got the 400 error once, it is not the same issue – you likely just need to reauthorize with Google to fix – clear authorization and then get the token key again – easy fix.

Having the same issue here – I have around 100 independent WP installations as well, all on the same dedicated server and in the same Google Analytics account. Every time I log in, each site seems to have the 400 error and I have to re-authorize. Any solutions to this would be appreciated!

Thank you for the details. We were missing the PHP Zip module which may have been a factor, however it does seem to draw some load still after enabling the module. Appreciate the tip on how to permanently block logging. My techsupport have been advising me to delete the plugin because of the 403.php load, but I’d rather not as I rely on it for a lot of htacesss protections.

I have a large number of client sites that have your BPS plugin installed and we are getting a large amount of load on our server due to the 403.php file that processes logging. I’ve turned off logging multiple times on these sites, but everytime there is an update the logging seems to get turned back on and our server load increases. Is there something I can do to make turning off logging more permanent?

Thanks!

Thanks Kyle – works great – much appreciated!

So this is still occurring – any chance you could push through an update so I don’t have to do this manually on all my sites? Great plugin otherwise – Cheers!

@dteunkens – thanks for posting the fix in the meantime- much appreciated!

This had something to do with using New Relic on the server, I disabled it and the script is now gone and the plugin works great.

Having a similar issue on one of my sites as well. Just suddenly started giving the error this week though and only to Editors – Admin can upload the same photo without error. The plugin has been active for some time and other WP sites with this plugin seem unaffected.

PHP Fatal error: Allowed memory size of 94371840 bytes exhausted (tried to allocate 18368 bytes) in /wp-content/plugins/resize-image-after-upload/class.resize.php on line 183

I solved this by adding the following to wp-config.php:
define('WP_MEMORY_LIMIT','1024M');

You may not need quite that much, but it does work.