• Home
  • Get help
  • Ask a question

#157 – Support for WPForms and WP Job Manager

Posted in ‘weeblrAMP’
This is a public ticket. Everybody will be able to see its contents. Only enter usernames, passwords or any other sensitive information in the Private information field.
Wednesday, 05 June 2019 03:29 UTC
mlargue
 Is there any intent to support WPForms and/or WP Job Manager in the near future?
 
Wednesday, 05 June 2019 07:17 UTC
wb_weeblrpress
Hi

Possibly WPForms but indeed nothing about WP Job Manager, sorry.

Best regards
 
Wednesday, 05 June 2019 07:23 UTC
mlargue
That sounds good. Any idea of timing?
 
Wednesday, 05 June 2019 07:26 UTC
wb_weeblrpress
Hi

We're about to release a new version today with several bug fixes, so that won't be in that. I would say it will be in next release which should happen in the next 4 weeks.

1 - Are you willing to test a pre-version?
2 - What kind of form do you have in mind? Like with Gravity forms, we likely won't support very complex forms, that's multipage or similar. Also ReCaptcha is not available yet. Do you have a link to such form you want to convert to AMP?

Best regards
 
Wednesday, 05 June 2019 07:37 UTC
mlargue
Hi Yannick

1. Yes
2. I am thinking a Contact form using their inbuilt numeric recaptcha, and a Newsletter Subscription footer-widget using the MailChimp add-on.
3. Only on a local site

Regards
Michael
 
Wednesday, 05 June 2019 07:41 UTC
wb_weeblrpress
Hi

1 - Good, I'll get in touch when something's available

2 - The numeric captcha should work on AMP I think. I don't have the Mailchimp add-on, we'll see about that.

3 - What do you mean by "local site" only?

Best regards
 
Wednesday, 05 June 2019 07:52 UTC
mlargue
I am doing a local development using Local by Flywheel - it is not publicly visible
 
Wednesday, 05 June 2019 07:53 UTC
wb_weeblrpress
Hi

Ah ok. That should not matter I think.

Best regards
 
Friday, 07 June 2019 12:35 UTC
wb_weeblrpress
Hi Michael,

I have a first go at WPForms. Please download from this online folder a development build.

It should handle:

- Honeypot-style spam prevention
- Message or redirects confirmation
- Mailchimp registration seems to work fine using the "mailchimp" standard fields in WPForms basic - which is the version I have. No Mailchimp Add-on was used but the integration is basic just a checkbox that says "Add me to the newsletter"

it is not expected that conditional logic would work as it's javascript based. It's not strictly impossible to do in AMP but that will require custom coding on a per project basis.

Let me know.

Best regards



 
Friday, 07 June 2019 12:40 UTC
mlargue
Thanks Yannick

Just about to go to bed (10:10 pm). I will give it a run tomorrow.

Michael
 
Friday, 07 June 2019 13:06 UTC
wb_weeblrpress
Hi

No problem, good night! Won't be around tomorrow so we'll speak on monday!

Cheers
 
Saturday, 08 June 2019 22:04 UTC
mlargue
Hi Yannick

I downloaded the beta and gave it a shot. I tried it on both WPForms and WPForms-Lite. Unfortunately, I didn't have much success. It appears to randomly deactivate a number of plugins as well as not to display forms created for WPForms. I am using both Astra and GeneratePress themes and pro plugins - separately obviously :)

I suspect that the environments may be a little complex, so I will create a very basic one to test on.

Regards
Michael
 
Tuesday, 11 June 2019 08:00 UTC
wb_weeblrpress
Hi

A bit odd. I did only test as usual with a standard install of WordPress and the twentynineteen theme.

It appears to randomly deactivate a number of plugins
Random should not exists here, surely there's a pattern :)

as well as not to display forms created for WPForms.
How do you displays those forms? a shortcode inside a page or a post?

Typically when testing, I would go to the "Comments and plugins" tab of weeblrAMP configuration and:

- disable the theme on AMP pages
- disable all plugins on AMP pages (except WPForms of course)

That's the configuration where plugins and theme can have the least influence on the AMP version of a page.
Then one can enable back plugins (on the AMP pages) one by one and find the most satisfying experience.

Let me know.

Best regards
 
Tuesday, 11 June 2019 09:23 UTC
mlargue
Hi Yannick

Apologies for not getting back sooner, I have been multitasking, but not very successfully. I did discover what caused the “disabled plugin” problem. It was basically a “clash of the caches” problem, underpinned by the Redis Object Cache. Unfortunately, I am busy with something a bit more pressing at the moment, but I should be able to resume testing in the next couple of days.

Please bear with me, I really do want WPForms to succeed with WeeblrPress.

Kind Regards
Michael
 
Tuesday, 11 June 2019 09:32 UTC
wb_weeblrpress
Hi

No worries. I think it should work fine but indeed other plugins may interfere. Let me know when you're ready.

Cheers
 
Friday, 21 June 2019 08:17 UTC
mlargue
Hi Yannick

I have just got back to testing. In the interim WPForms has been made AMP compatible (thanks to StudioPress and WPEngine) and released an updated WPForms-Lite plugin version 1.5.3.1. I have tested this with the default AMP plugin in conjunction with the latest Genesis 3 and Encore Pro child theme. It works!

Unfortunately, I then tested this with the revised weeblrPress plugin that you sent me, but unfortunately, the AMP version of the contact page does not display the contact form. I get the message "Go to the full page to view and submit the form".

I have also noticed that the Woocommerce shop and single pages don't work either.

I hope this helps.

Regards
Michael
 
Friday, 21 June 2019 10:23 UTC
wb_weeblrpress
Hi

Unfortunately, I then tested this with the revised weeblrPress plugin that you sent me, but unfortunately, the AMP version of the contact page does not display the contact form. I get the message "Go to the full page to view and submit the form".
Just tested again with current WPForms (not lite) and all works fine.

I have also noticed that the Woocommerce shop and single pages don't work either.
You did not say what "don't work" mean but again everything's normal for me with all those extensions and WP updated to their current versions.

Of course, for weeblrAMP to wok you would have to disable the AMP plugin and any amp-related plugins or theme or modification designed for adding AMP support to any extension.

Best regards
 
Friday, 21 June 2019 10:45 UTC
mlargue
Hi Yannick

Yep, I am aware of that. Everything was brought back to the bare minimum (even taking Woocommerce out of the equation). weeblrPress and WPForms-Lite were the only active plugins. In addition, GeneratePress was the theme active at the time and weeblrPress version 1.11.1.728 was being used.

Kind regards
Michael
 
Friday, 21 June 2019 12:20 UTC
wb_weeblrpress
Hi

GeneratePress was the theme active
Was the theme "disabled on AMP page"?

Best regards
 
Friday, 21 June 2019 12:22 UTC
wb_weeblrpress
Hi again,

Can you also make sure you use the latest development version (from the development versions download area)? There's been a few changes and fixes recently and most importantly I'd like to be sure we are talking about the same code base.

Best regards
 
Friday, 21 June 2019 19:12 UTC
mlargue
Hi Yannick

Yep, it was deactivated and I was not seeing any raw codes on AMP pages. I will download the latest and give it another try.

Regards
Michael
 
Friday, 21 June 2019 20:04 UTC
mlargue
Hi Yannick

I reverted to the Astra theme with the latest weeblrPress and WPForms-Lite plugins. Everything works except for WPForms. I also confirmed that Contact Form 7 and GeneratePress works. I established what my problem with GeneratePress was - categories for posts had not been selected. Am I missing some configuration for WPForms? It still generates the message. There may be a problem there as it was previously their interim solution for AMP.

Kind regards
Michael
 
Monday, 24 June 2019 07:09 UTC
wb_weeblrpress
HI

categories for posts had not been selected
Good to know, we might prevent some of that happening in the future.

Am I missing some configuration for WPForms? It still generates the message. There may be a problem there as it was previously their interim solution for AMP.
This would indicate they changed the way they handle this. As WPForms detects it's running on an AMP page, they would display this message instead of just rendering the form. But they also provide a way for developers to change that behavior which we do in weeblrAMP and tell WPForms to still render the form even if they detect current page is AMP.

I assume in latest WPForms lite they change this, maybe they do not allow developers to override their AMP detection. This does not happen with latest WPForms - which is used for weeblrAMP development - so this might be specific to WPForms lite. I'll test it today.

Best regards
 
Monday, 24 June 2019 09:02 UTC
wb_weeblrpress
Hi

Hmm, there's more to it. I tested also with WPForms Lite (current, ie 1.5.31) and things work perfectly fine on my end, just like with WPForms standard version.

Am I missing some configuration for WPForms?
Just installed straight from the WP plugins repository, created their standard sample "Contact form" and it worked like that.

Can't say much more just from that. If you can provide a backup (best for us is Duplicator) that we can install on a local machine and step through the PHP, we are sure to identify the source of the issue, whether in weeblrAMP or not.

Best regards
 
Monday, 24 June 2019 09:55 UTC
mlargue
Hi Yannick

I have found out what the problem is. There are two ways of putting WPForm on a page...

1. Use the WPForm block and select the form
2. Use the Shortcode block and use the form shortcode

When you use the WPForm block approach, it does not work.
When you use the Shortcode block approach, it works.


Regards
Michael
 
Monday, 24 June 2019 10:05 UTC
wb_weeblrpress
Hi

Thanks for that, indeed I am always using the shortcode. I will look into it more but to be honest I can't guarantee right now that we can provide support for blocks, it depends a lot on how WPForms implemented it.

Best regards
 
Monday, 24 June 2019 15:30 UTC
wb_weeblrpress
Hi Michael,

I just uploaded to the development versions download area a new version that handle forms created as Gutenberg blocks as well as those created with shortcodes.

Let me know.

Best regards
 
Monday, 24 June 2019 19:51 UTC
mlargue
Hi Yannick

I am happy to confirm that when using the current version of both WPForms and WPForms-Lite, that:

When I use the WPForm block approach, it works.
When I use the Shortcode block approach, it works.

Yay! That is absolutely fantastic. Thanks very much.

On another note/question...

I also tested the newsletter subscription form as a shortcode in a text widget and the WPForms widget itself, in a widget area. Neither of them worked. I am presuming that this is because you do not appear to cover off on widget areas?

Kind Regards
Michael
 
Tuesday, 25 June 2019 10:26 UTC
wb_weeblrpress
Hi

Neither of them worked. I am presuming that this is because you do not appear to cover off on widget areas?
You can use the AMP widgets areas to include WPForms in your AMP pages. The regular widgets areas are not rendered on AMP pages. When using the AMP widgets areas, note that:

- you can only use the shortcode version. I just tested this again
- the WPForms widget cannot be used directly. It does work and output a form but that form is actually removed by weeblrAMP later on because it's not "marked" as AMP and modified to be AMP-compatible (which is what we have to do on any form)

So you would use it like this:


Best regards
 
Tuesday, 25 June 2019 10:31 UTC
mlargue
Thanks Yannick

You're a star. I will get there eventually.

Regards
Michael
 
Tuesday, 25 June 2019 12:24 UTC
wb_weeblrpress
Hi Michael,

Thanks for your kind words! This version will be released publicly soon, within a few days.

Cheers
 
Wednesday, 10 July 2019 05:34 UTC
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.