Hey @saznajnovo,
thanks for your message.
Interesting topic. It seems forms need some special attention when it comes to AMP.
I will check that and if it’s enough time I’ll include it in version 3.2 which comes in a couple of days.
Best regards,
Patrick
Great, I saw you added AMP support to newest version. I tested it and not worked. DIV is rendered but there is no content in it. Take a look: https://i.imgur.com/14VZNmK.png
Hey @saznajnovo,
there should be an option in Settings->Passster->Options “AMP Support”, after activation.
It includes the necessary scripts to add the AMP support to your site and then it should render the field correctly.
I updated plugin and I got fatal error:
Fatal error: require(): Failed opening required '/srv/users/xxx/apps/xxx/public/wp-content/plugins/content-protector/vendor/composer/../../src/class-ps-settings.php' (include_path='/srv/users/xxx/apps/xxx/public/wp-content/plugins/backwpup/vendor/pear/archive_tar:/srv/users/xxx/apps/xxx/public/wp-content/plugins/backwpup/vendor/pear/console_getopt:/srv/users/xxx/apps/xxx/public/wp-content/plugins/backwpup/vendor/pear/http_request2:/srv/users/xxx/apps/xxx/public/wp-content/plugins/backwpup/vendor/pear/mail_mime:/srv/users/xxx/apps/xxx/public/wp-content/plugins/backwpup/vendor/pear/mail_mime-decode:/srv/users/xxx/apps/xxx/public/wp-content/plugins/backwpup/vendor/pear/net_url2:/srv/users/xxx/apps/xxx/public/wp-content/plugins/backwpup/vendor/pear/pear-core-minimal/src:/srv/users/xxx/apps/xxx/public/wp-content/plugins/backwpup/vendor/pear/pear_exception:.:/opt/sp/php7.1/lib/php:/srv/users/ser in /srv/users/xxx/apps/xxx/public/wp-content/plugins/content-protector/vendor/composer/autoload_real.php on line 66
After I disabled backupwp, I got this error:
Fatal error: require(): Failed opening required '/srv/users/xxx/apps/xxx/public/wp-content/plugins/content-protector/vendor/composer/../../src/class-ps-settings.php' (include_path='.:/opt/sp/php7.1/lib/php:/srv/users/xxx/apps/xxx/public/wp-content/plugins/wp-appbox/inc/phpQuery/:/srv/users/xxx/apps/xxx/public/wp-content/plugins/wp-appbox/inc/phpQuery/plugins/') in /srv/users/xxx/apps/xxx/public/wp-content/plugins/content-protector/vendor/composer/autoload_real.php on line 66
And I didn’t want to test further because I have a lot of live traffic and I can’t just disable crucial plugins.
So, after 3.2.0.1 update I can’t activate plugin because of these errors. If you need more info, I’ll be happy to help you testing.
Hey @saznajnovo,
again sorry for the problems.
The SVN repository of the repository caused some trouble for me in the update process over the weekend. Version 3.2.0.4 should now work fine again and includes the AMP option as well.
Best regards,
Patrick
@patrickposner Thanks for fast update. Now it works… sort of. When I load passster form on PC and enter password, content is shown both on PC and AMP. BUT, if I want to load form on AMP (to enter password) – no luck. So, I can only unlock content on PC and see it on PC/AMP. Unlock form is not showing on AMP, there is only empty DIV (https://i.imgur.com/14VZNmK.png)
Hey @saznajnovo,
do you use any plugin to build your AMP version? If so, which plugin do you use?
I followed the exact instructions of the AMP project for implementing form fields here: https://www.ampproject.org/docs/reference/components/amp-form
So maybe we need some kind of additional compatibility with the other plugin.
Best regards,
Patrick
@patrickposner I am using “AMP for WP” but I just saw they shut down plugin today https://ww.wp.xz.cn/plugins/accelerated-mobile-pages/
I switched to Better AMP and is visible! Now I am getting JS error: Response must contain the AMP-Access-Control-Allow-Source-Origin header but it’s about my server, not your plugin. Thanks for updates and your time to help!
Just to be sure, this is not error made by your plugin? This happens when I press button to unlock content (correct or wrong password, no difference): https://i.imgur.com/3zuOdMR.png
Failed to parse response JSON: SyntaxError: Unexpected token < in JSON at position 0
-
This reply was modified 7 years, 2 months ago by
saznajnovo.
-
This reply was modified 7 years, 2 months ago by saznajnovo.
@patrickposner Did you found something about this error?
Hey @saznajnovo,
I included a modified solution from your example code in the 3.2.0.6 version.
This should also work without the additional headers in the .htaccess.
In my test case it has worked fine with Better AMP plugin.
Best regards,
Patrick
@patrickposner Great news! I’m glad to help.
