#203 – Update not working
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.

Andy K
Hi. I have the correct access code installed under the system tab, but when I try to upgrade, I get a "access code not installed" message. I have tried clearing my caches to no avail. Help!

wb_weeblrpress
Hi
Have you listed your site full URL under your dashboard?
Best regards
Yannick Gaultier
weeblr.com
@weeblr
Have you listed your site full URL under your dashboard?
Best regards
Yannick Gaultier
weeblr.com
@weeblr

wb_weeblrpress
Hi
Sorry about that, we recently changed our update key length and there were some left over checks. You will have to download the latest version from the Download area and install manually. Subsequent updates will be as usual, through the updater.
Best regards
Sorry about that, we recently changed our update key length and there were some left over checks. You will have to download the latest version from the Download area and install manually. Subsequent updates will be as usual, through the updater.
Best regards

Andy K
OK. That worked. Thank you.
The more I work with your AMP pages, the more I appreciate your software. The non-AMP pages are fantastic. Can you please take a look at this AMP page? https://www.ocalahomes.online/seller-guide-lp/amp
The WPform is there and appears to work fine, but a wheel keeps spinning at the bottom of the form as if more is being loaded and that may throw visitors off. Any suggestion as to what we can do to eliminate the wheel? Thanks.
Best,
Andy
The more I work with your AMP pages, the more I appreciate your software. The non-AMP pages are fantastic. Can you please take a look at this AMP page? https://www.ocalahomes.online/seller-guide-lp/amp
The WPform is there and appears to work fine, but a wheel keeps spinning at the bottom of the form as if more is being loaded and that may throw visitors off. Any suggestion as to what we can do to eliminate the wheel? Thanks.
Best,
Andy

wb_weeblrpress
Hi
Thanks for you kind words!
As for the page in question, the spinner for wpforms is showing, not sure why, that does not happen in any of my testing. Is that an option you enabled somehow?
Note that by opening the browser console you can see other errors related to Google Tag manager.

Did you create an AMP-specific GTM container? you cannot just use your regular GTM id, you need to create a separate AMP container.
Best regards
Yannick Gaultier
weeblr.com
@weeblr
Thanks for you kind words!
As for the page in question, the spinner for wpforms is showing, not sure why, that does not happen in any of my testing. Is that an option you enabled somehow?
Note that by opening the browser console you can see other errors related to Google Tag manager.

Did you create an AMP-specific GTM container? you cannot just use your regular GTM id, you need to create a separate AMP container.
Best regards
Yannick Gaultier
weeblr.com
@weeblr

Andy K
Hi Yannick,
I have been working directly with Google's Tag Manager Team and they have advised not to create a separate container. However, I am aware that Tag Manager advises that a separate container is required for AMP pages. Rather than changing what they have installed on my account, I will consult with them and get help dealing with the Tag Manager errors on my AMP pages. Unfortunately, instead of having their people work from home, they have simply shut down support as of last week. But waiting is not a serious issue for me because I have stopped my Google Ads campaigns for now. No ROI!
Anyway, I shut off Tag Manager on my AMP pages, but I don't think Tag Manager caused the issue. It is occurring on all my Elementor AMP pages save one, and that one seems no different than the others:
This page has the issue: https://www.ocalahomes.online/seller-guide-avoid-common-mistakes-lp/amp
But this page does not: https://www.ocalahomes.online/ocala-home-guide-realty-contact-page/amp
The pages seem almost identical as to format and I have tried to find the issue without success.
Best,
Andy
I have been working directly with Google's Tag Manager Team and they have advised not to create a separate container. However, I am aware that Tag Manager advises that a separate container is required for AMP pages. Rather than changing what they have installed on my account, I will consult with them and get help dealing with the Tag Manager errors on my AMP pages. Unfortunately, instead of having their people work from home, they have simply shut down support as of last week. But waiting is not a serious issue for me because I have stopped my Google Ads campaigns for now. No ROI!
Anyway, I shut off Tag Manager on my AMP pages, but I don't think Tag Manager caused the issue. It is occurring on all my Elementor AMP pages save one, and that one seems no different than the others:
This page has the issue: https://www.ocalahomes.online/seller-guide-avoid-common-mistakes-lp/amp
But this page does not: https://www.ocalahomes.online/ocala-home-guide-realty-contact-page/amp
The pages seem almost identical as to format and I have tried to find the issue without success.
Best,
Andy

wb_weeblrpress
Hi

The container type has to be AMP. I had several users trying with their regular containers, it just does not work.

I'm not sure what they do but I'd strongly advise that you disable that plugin on your AMP pages. As we discussed before, it's not really of any help on AMP pages, at least when viewed from the AMP cache.
Best regards
Yannick Gaultier
weeblr.com
@weeblr
I have been working directly with Google's Tag Manager Team and they have advised not to create a separate container. However, I am aware that Tag Manager advises that a separate container is required for AMP pages. Rather than changing what they have installed on my account, I will consult with them and get help dealing with the Tag Manager errors on my AMP pages. Unfortunately, instead of having their people work from home, they have simply shut down support as of last week. But waiting is not a serious issue for me because I have stopped my Google Ads campaigns for now. No ROI!I don't know who you talked to but there's just no way anything else than an AMP container can work:

The container type has to be AMP. I had several users trying with their regular containers, it just does not work.
The pages seem almost identical as to format and I have tried to find the issue without success.One thing I noticed is that this image is coming from your Optimole.com service:

I'm not sure what they do but I'd strongly advise that you disable that plugin on your AMP pages. As we discussed before, it's not really of any help on AMP pages, at least when viewed from the AMP cache.
Best regards
Yannick Gaultier
weeblr.com
@weeblr

Andy K
Hi Yannick,
I have shut off Optimole for pages with the amp extension. However, that had no impact on the issue. One thing I did notice is that the form I use on the page where I don't have an issue does not have a phone number field, but all on all pages where I do have the issue do have a phone number field. With respect to that, I use a standard phone number field, but where such a field exists the conversion to amp seems to replace that field with what looks like a single line text field.
See the phone number field on a non-amp page here:
https://www.ocalahomes.online/seller-guide-avoid-common-mistakes-lp/
and on the same page converted to amp here:
https://www.ocalahomes.online/seller-guide-avoid-common-mistakes-lp/amp
Could that be the issue?
Thanks.
I have shut off Optimole for pages with the amp extension. However, that had no impact on the issue. One thing I did notice is that the form I use on the page where I don't have an issue does not have a phone number field, but all on all pages where I do have the issue do have a phone number field. With respect to that, I use a standard phone number field, but where such a field exists the conversion to amp seems to replace that field with what looks like a single line text field.
See the phone number field on a non-amp page here:
https://www.ocalahomes.online/seller-guide-avoid-common-mistakes-lp/
and on the same page converted to amp here:
https://www.ocalahomes.online/seller-guide-avoid-common-mistakes-lp/amp
Could that be the issue?
Thanks.

wb_weeblrpress
Hi
The fields are the same in both cases, they are actually just text input fields.
I looked up the code for when wpforms displays that submit spinner image and it's supposed to be removed on AMP pages. However they only consider the Automattic AMP plugin and the BetterAMP plugin - please feel free to lobby them to include weeblrAMP :)
I think this can be worked around by adding a filter to your theme or child theme:
- create a /themes/xxxxx/weeblramp folder
- in the folder, create a functions.php file
- in that file, add:
If that fixes it as I suspect I can look at how to integrate this into the wpForms integration more deeply (I already use that filter at some point).
Best regards
The fields are the same in both cases, they are actually just text input fields.
I looked up the code for when wpforms displays that submit spinner image and it's supposed to be removed on AMP pages. However they only consider the Automattic AMP plugin and the BetterAMP plugin - please feel free to lobby them to include weeblrAMP :)
I think this can be worked around by adding a filter to your theme or child theme:
- create a /themes/xxxxx/weeblramp folder
- in the folder, create a functions.php file
- in that file, add:
<?php /** * Frontend functions.php for weeblrAMP */ // Security check to ensure this file is being included by a parent file. defined('WEEBLRAMP_EXEC') || die; // let original handler do its job $isAmpFilter = function ( $isAmp ) { return true; }; add_filter( 'wpforms_is_amp', $isAmpFilter );
If that fixes it as I suspect I can look at how to integrate this into the wpForms integration more deeply (I already use that filter at some point).
Best regards

wb_weeblrpress
Hi again,
After running more checks, this is not going to work. At some point, WPForms requires not to be on an AMP pages (it stops displaying the form and shows a message offering to go to the non-AMP version). However it would require that the page IS AMP to not show that spinner.
Best regards
After running more checks, this is not going to work. At some point, WPForms requires not to be on an AMP pages (it stops displaying the form and shows a message offering to go to the non-AMP version). However it would require that the page IS AMP to not show that spinner.
Best regards

wb_weeblrpress
Hi again
After running even more checks, it seems pretty difficult to prevent it from displaying this spinner. So I'd suggest for now just not displaying it. You can add the following CSS to Custom styles in weeblrAMP:
This works for me.
Best regards
After running even more checks, it seems pretty difficult to prevent it from displaying this spinner. So I'd suggest for now just not displaying it. You can add the following CSS to Custom styles in weeblrAMP:
.wpforms-submit-spinner {display:none;}
This works for me.
Best regards

wb_weeblrpress
Hi again
By the way, what causes the display of the spinner is checking "Enable AJAX form submission". That's something I consider normal in most cases, so I have added this CSS to the latets dev version (get it from the development versions download area).
Best regards
By the way, what causes the display of the spinner is checking "Enable AJAX form submission". That's something I consider normal in most cases, so I have added this CSS to the latets dev version (get it from the development versions download area).
Best regards

Andy K
Hi again, Yannick,
The code worked perfectly and the forms work perfectly as well.
Thank you and best regards.
The code worked perfectly and the forms work perfectly as well.
Thank you and best regards.

wb_weeblrpress
Hi
Glad to hear that! Closing this ticket now as it's been convering already too many different subjects. Feel free to open a new one as needed. If you do so, please mention this ticket number in the new one.
If you created any superadmin account for us, be sure to delete or block it now to avoid unnecessary risk in the future.
Best regards
Glad to hear that! Closing this ticket now as it's been convering already too many different subjects. Feel free to open a new one as needed. If you do so, please mention this ticket number in the new one.
If you created any superadmin account for us, be sure to delete or block it now to avoid unnecessary risk in the future.
Best regards
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.