Francesca Aisha Iwa d'Ath

Hi,

you can set this in the calculation itself by adding :2, e.g.

{calc:my_calc:2}

This works for pre-calculation zeros, i.e. 0.00 instead of 0, and also works for rounding, see: How to round a calculation in 3.0 ?

Hi @hugodebe,

the following seems to work:

Under General Settings:
Minify is enabled and set to auto.

Under Minify:
HTML minify settings is not enabled.
JS minify settings is enabled and uses Default (blocking) for both options.
CSS minify settings is enabled.

I’ve tested this in multiple browsers (not logged in) with W3TC caches and browser caches primed and/or cleared.

JS minify using anything other than Default seems to cause diverse problems, and I can consistently solve them using this option.

HTML minify — irrespective of inline CSS or JS settings — seems to be the problem here, hence disabling it entirely. I also tried variations on [CDATA with no effect.

Ok, will do.

Hi Jeff,

Thanks for getting back to me. One further thing I noticed while testing:

If I’m viewing the cached site (i.e. for W3TC logged out in another browser), and go down the Blackhole, I’m shown first the (red background with whois info) Banned page, then on refreshing, the unstyled Banned page (with custom message). However, if I go back to the original page or to another cached page, I see that and not the Banned page, i.e. the opposite of the above issue, seeing pages when I should be banned.

Unlike trying to find where Banned pages are being cached (or whatever is going on), I have been able to replicate this, and it might point to where the above issue is coming from.

Thanks again!

Fixed, thanks!

Getting same error on all sites, for all report types.

Using W3TC, clearing cache makes no difference. Neither does dis/re-enabling plugin. Tried opening in Firefox (new install), same error.

Console is only giving:

[Log]  (reports.js, line 716)
********************* GADWP Log ********************* 

-31

This works for me (tested a few times on two different sites):

i. with the original cforms 14.6 running (and everything working ok) go to:
ii. wp-admin > cformsII > Global Settings
iii. in the admin bar under cforms Admin click ‘Backup / restore all settings’
iv. A popup appears, click ‘Backup all settings now!’ it will save to default downloads as all-cforms-settings.txt
v. if you like you can do this also for each form and then dump the entire database (overprecaution)
vi. disable the old cforms plugin
vii. install and enable cforms2
viii. go to wp-admin > cformsII > Form Settings. Are the forms there?
ix. No, the forms aren’t there. Go back to wp-admin > cformsII > Global Settings
x. in the admin bar again under cforms Admin click ‘Backup / restore all settings’
xi. click ‘choose file’ and select all-cforms-settings.txt, then click ‘Restore all settings now!’
xii. go back to wp-admin > cformsII > Form Settings. Are the forms there?
xiii. Yes, the forms are there. Do something else (like delete the old plugin).

If the forms aren’t there after all that, I have no idea (horrible serialised data)

It seems to authenticate and work fine for me now, thanks.

I have the same problem. For me changing bloginfo(‘url’) to site_url() in google-analyticator.php as well as adding /wordpress/ to the “Save & Continue” button seems to work, though now the UID throws “There was an Analytics API service error 400:Error fetching OAuth2 access token, message: ‘invalid_grant'”, which may or may not be connected.

i think for me it’s a specific combination of very customised theme and backend, which i can only reproduce on this one site – probably safe for everyone else.

Hi Mikkel, I’m in Berlin and would be interested. I’m @francesdath, sent you a message.

Also here, on several sites. I tried reinstalling, changing htaccess rules in case there was a conflict, but still not working.