Christopher Clarke

In which case, might I respectfully suggest that the documentation available for users is temporarily changed so that people like myself don’t spend hours banging their heads against a brick wall for no good reason?

Hi Jay

Thanks for getting back to me, but please forgive me, I don’t think I understand. Your documentation doesn’t say that at all – in fact the list of placeholders in System Assistant specifies just the opposite.

Link to screenshot: https://drive.google.com/file/d/1TSD-Py0T_M2dRNpNgK5hRknQiGOOLgiz/view?usp=sharing

Am I doing something wrong?

I note that the list of GLOBAL placeholders does not include any of the CONTACT-xxx. However, CONTACT-PREFIX and CONTACT-LNAME work absolutely fine.

Then, in the list of the CONTACT placeholders, a whole load of CONTACT-xxx are listed to be available for QUOTEs, including SECADDR1, SECADDR2, SECCITY, SECCOUNTY, SECPOSTCODE and more.

I’m not sure why you would go out of your way to include some but exclude other CONTACT-xxx fields from the quote section. How can you build a proper written quote that a potential client would take seriously (either by text in an email or in a PDF) without having the proper details available on the quote?

For that matter, having custom fields generally available for quotes would seem to be very sensible too. But I accept that the nature of Custom Fields and their naming could cause conflicts.

Thanks guys

It was my host that got hacked first which allowed the hacker access to my site.

I did wonder, considering I use unique, very long passwords.

I am waiting to see if they can sort it out.

Hi Tareq

I have the same problem. My website is https://www.ashingtonvillage.co.uk.

After an update the other day there seems to be a problem on pages without any WP User Frontend shortcodes on as well as pages with it on.

I use Revolution Slider on my site and this no longer works.

By a process of elimination (activating and de-activating plugins) I discovered that it was WP User Frontend causing the problem.

Javascript stops with the error:
Uncaught TypeError: Cannot read property ‘currentStyle’ of null

The file the error is found in seems to be:
https://ashingtonvillage.co.uk/av/wp-includes/js/plupload/plupload.js?ver=1.5.5

Can you help?

PS: your plugin states that it was last updated 15,878 days ago which I make a shade over 43 years.