John Brand

I’ve corrected this error.

If anyone can help co-author this, because I’m not really a developer and these new customiser changes to Worpdress is beyond my limited coding abilities.

Thanks for reporting. i’ve corrected this with your suggestion in version 2.0.6. It also includes issues with other settings api classes and it prevents issue with a conflicting icon library.

I see. However none of the folders above is generating an error with post-state-tags anywhere so it doesn’t appear to be my plugin that is generating an error. But rather the Avia Gutenberg and Enfold.

If you can tell me what customer post status you added and how then I can try to replicate this issue.

Yeah. I’m also missing this feature. Now I have to use additional blocks to “create” a simple layout like this.

This is a default wordpress listing feature. They might be using a completely custom list mechanism. I’ve seen some form builders do this. Then this plugin won’t work then. It only supports the default custom post type listing features.

• This reply was modified 5 years, 3 months ago by John Brand.

That status tags are provided by WordPress, eg draft, preview , scheduled etc. All these appear on any post type: pages, posts or any custom post type, because it’s a feature of WordPress for all types of posts and isn’t something you have to setup.

• This reply was modified 5 years, 3 months ago by John Brand.

I guess the label could be but in general I use “signup” or “contact” if the client wants their emails in there. Some clients might also use the email and social links in the pre-footer as a menu.

• This reply was modified 5 years, 4 months ago by John Brand.

Basically I just add a custom link and instead of adding in a https://xxx url I use the mailto:xxx structure.

Hmmm. I just got a message on the website for thank you. No ticket.

Hi. I logged a support ticket, but I never received an e-mail for it. So this is still and outstanding issue. There are errors on the console yes, and I gave login details in the support ticket.

That’s exactly what I’ve been doing and I cannot edit any of those inline fields. I’d i click on the default name, title or description nothing happens.

$8.25 is the same price as Netflix in South African Rand, and I can promise you that I will get a lot more enjoyment out of Netflix streaming than uploading files. That’s why I am willing to attempt to write the file uploader and give it away for free, as I don’t feel that it should be behind a paywall. I really love this plugin’s interface and the way its integrated and it will be suitable for most websites anyways. I’ll then use Caldera for sites where I need more control.

HappyForms should rather consider providing a basic file upload for free, and then put a super-duper advanced upgrade with file drag n drop, uploading progress, file renaming and even more advanced features into an upgraded file uploader.

I definitely disagree that any form plugin always conveniently “forgets” to add the basic HTML file upload button. I mean even your plugin Josh has that feature built-in.

This is problematic, because the confirmation message is structured inside the form block, so if you place the form at the bottom of the page, e.g. signup form, then it scrolls to the top, but the message is displayed inside the form block at the bottom.

Also, it would be nice if you could have an option to “hide” the form and then display the message instead, so you can’t complete the form again without a reload.

• This reply was modified 5 years, 8 months ago by John Brand.

This was happening, because my function doesn’t have a pre-check if the status already exists. I’ve added in some code to check if a default already exists for this status (e.g. those from WooCommerce are new statuses). This then avoids the index warning you are getting. Although you should set your wordpress to ignore NOTICES as these are not errors or warnings. NOTICES are merely the compiler saying that it couldn’t find something, but it knows how to continue.

NOTICE, WARNING, ERROR levels are settable in your PHP.INI or even in WordPress itself.

Install 2.0.4. Hope this fixes the notices you are getting.