As we said in the video tutorial, you should deactivate all caching plugins in the first time to make sure everything works correctly. And install the caching after all steps. Also, DO NOT enable the minify & combine the CSS/JS/HTML & lazyload from any plugin.
So, let's try it again as I said. If you still can't do that, please send me your WordPress site admin URL and admin account ( username and password ) - in a PRIVATE REPLY. And I will take a look at this to help you.
On recent updates of Penci AMP plugin (Not sure which one), we started seeing URLs with "/amp/" at the beginning and at the end of the URIs in our Google Analytics reports.
Checking our sites, we found that both URLs respond an AMP version of the page. For example...
I just updated from v4.2 ~> v4.3 using the zip file you sent me. After that:
- The images errors seem to be solved, without making any changes to our ReCaptcha settings.
- Both URLs are still working, with the AMP parameter at the end and at the beginning
- The only difference that I see is, if I set "Start point", Soledad uses the AMP parameter at the beginning of the URI by default... But in the end is also working.
After discussion with our dev team, here is the reply from them:
We've changed the default AMP links from start-point to end-point on version 4. In the previous time, the AMP URL format has default is start point ( domain.com/amp/your-posts/ ) now, the default is end-point ( domain.com/your-posts/amp/ ).
Why do we change it? Because the AMP end-point running stable and doesn't have issues as the AMP start-point. Some hosting configures can be caused problems with some customers using AMP start-point.. So, we recommend you change the AMP URL format to end-point for both 2 sites ( if you're using AMP start-point for your websites ) and request Google to re-index your AMP URLs again.
We've explained this some days ago. So, it's not the bug. It's related to your settings. And we do recommend you use /amp/ as an end-point, it's stable and better than the start point.
Hi there,
I just updated Soledad to v7.9.0 and all Penci's plugins to latest version.
Also, I installed and enabled "Penci Shortcodes & Performan" and "Penci Speed Optimizer" following this guide: https://optimize.pencidesign.net/1.-installation-1
"PageSpeed Optimizer" is not at Customize > Speed Optimization.
Any suggestion?
Hi,
Please send me your WordPress site admin URL and admin account ( username and password ) - in a PRIVATE REPLY. I will take a look at this to help you.
Best Regards,
PenciDesign
Hi,
As we said in the video tutorial, you should deactivate all caching plugins in the first time to make sure everything works correctly. And install the caching after all steps. Also, DO NOT enable the minify & combine the CSS/JS/HTML & lazyload from any plugin.
So, let's try it again as I said. If you still can't do that, please send me your WordPress site admin URL and admin account ( username and password ) - in a PRIVATE REPLY. And I will take a look at this to help you.
Best Regards,
PenciDesign
Hi guys,
Sorry about reopening this ticket but it's impossible to verify the purchases from envato.
How can I submit a new ticket?
TYVM
Hi,
Maybe the Ticksy system has some problem. While waiting for their fix this issue, you can post your question here.
Regards,
PenciDesign.
Hi guys,
We are running 2 blogs with Soledad, quiltsocial.com and knitmuch.com.
Both have AMP versions.
On recent updates of Penci AMP plugin (Not sure which one), we started seeing URLs with "/amp/" at the beginning and at the end of the URIs in our Google Analytics reports. Checking our sites, we found that both URLs respond an AMP version of the page. For example...
QUILTsocial:
https://quiltsocial.com/amp/making-an-easy-star-block-with-hsts/
https://quiltsocial.com/10-simple-steps-to-making-removable-cushion-covers/amp/
KNITmuch:
https://knitmuch.com/amp/wool-ease-thick-and-quick-makes-for-a-quick-knit-mitred-hat/
https://knitmuch.com/wool-ease-thick-and-quick-makes-for-a-quick-knit-mitred-hat/amp/
I suppose it is because the new "AMP URL Format" setting at Customizer AMP.
Questions:
Thank you!
Hi,
Please try to upload the Penci AMP Plugin to the latest version by download the attachment file.
For about your question:
If your problem can't resolved, please send me your site login credential in a PRIVATE reply. I'll log in and check your site.
Regards,
PenciDesign.
Hi guys,
Thanks for having a look into it so quickly.
I just updated from v4.2 ~> v4.3 using the zip file you sent me. After that:
- The images errors seem to be solved, without making any changes to our ReCaptcha settings.
- Both URLs are still working, with the AMP parameter at the end and at the beginning
- The only difference that I see is, if I set "Start point", Soledad uses the AMP parameter at the beginning of the URI by default... But in the end is also working.
Examples:
https://knitmuch.com/amp/
https://knitmuch.com/amp/wool-ease-thick-and-quick-makes-for-a-quick-knit-mitred-hat/
https://knitmuch.com/the-magical-qualities-of-nymph-make-for-some-great-summer-knitting/amp/
Hi,
Please wait for me to check this issue with the development team and send you an update soon.
Regards,
PenciDesign.
TYVM :) Please let me know when you have some news.
Regards.
Hi guys,
And extra detail which could help with this.
Setting "AMP URL Format" as "Start point":
Setting "AMP URL Format" as "End point":
Let me know if I can help.
Thank you.
Hi,
Thank you for let me know about that. I'll discuss this with the development team and send you an update as soon as I can.
Regards,
PenciDesign.
Hi,
After discussion with our dev team, here is the reply from them:
We've changed the default AMP links from start-point to end-point on version 4. In the previous time, the AMP URL format has default is start point ( domain.com/amp/your-posts/ ) now, the default is end-point ( domain.com/your-posts/amp/ ).
Why do we change it? Because the AMP end-point running stable and doesn't have issues as the AMP start-point. Some hosting configures can be caused problems with some customers using AMP start-point.. So, we recommend you change the AMP URL format to end-point for both 2 sites ( if you're using AMP start-point for your websites ) and request Google to re-index your AMP URLs again.
Best Regards,
PenciDesign
Hi guys,
Thanks for your reply.
It means that "Start point" is not an option, right?
In any case, setting "Start point" or "End point"... Both versions of the URL are responding. What can we do about it?
Hi guys,
Any news?
I see that a new version of soledad is available. Does it comes with fixes about this?
Hi,
We've explained this some days ago. So, it's not the bug. It's related to your settings. And we do recommend you use /amp/ as an end-point, it's stable and better than the start point.
Best Regards,
PenciDesign
Hi guys,
I'm not so clear about that. There are a few reasons
- It was working pretty well until version 4. Since that update, we started seeing a few errors.
- Why does your live demo use "starts with" if you strongly recommend using "end with"? https://soledad.pencidesign.net/soledad-magazine/amp/
- Using "end with" doesn't work globally. For example, page URLs don't response: https://knitmuch.com/page/134/amp/