Hello
I have just updated the theme to latest version. And I had read about the new amp developments.
1- The issue is with WP Bakery
Some functionalities are not working when tag div composer and wp bakery? For example we disabled some rows so that they are not visible on frontend. But they are still visible. Yes, tagdiv is installed and enabled.
2 – The issue with amp.
We are using WPML for multi language website. The view of homepages and posts are different than each other. Please see the screen shots here. Are we missing any steps and modifications?
https://pasteboard.co/Ic2Muad.jpg
https://pasteboard.co/Ic2MHjd.jpg
3 – When we test some posts with google amp tester, first we get non-amp submitted result but with a reference. Seeing the amo version result confirms that it is a valid amp page. Is this normal?
https://pasteboard.co/Ic2OMVE.png
https://pasteboard.co/Ic2OWpP.png
Thank you
Hi,
1. We are aware of this issue, it will be fixed. If the setting is made in a page built with WPBakery it will not work, it will work if the page is built with the tagDiv composer. This also has options to hide specific rows/columns/elements per device.
There are some other issues which may happen when both composers are active, they will all be fixed as soon as possible. This will happen by theme updates.
2. This is most unusual, the homepage uses the mobile theme while the rest of the website appears to not use it. If the mobile theme is active the whole website should use it, depends on this setting however – http://prntscr.com/nio8v8 (first two will present the mobile theme at all times, while the last only for AMP).
Such issues could happen due to caching plugins or maybe minification/compression or optimization plugins. Try if possible and if you use such plugins, to deactivate them temporarily and check if this solves it.
3. The AMP URL will be with /?amp, this should be valid when testing. Seems to be valid when I test a post – http://prntscr.com/nioalr
Thanks
Hi Simon Thank you for the update. We will check if this is a plubing compitability issue. However, shouldn’t it be better to announce this update after you hve fixed those issues? I believe many people still using WP Bakery and we have to recreate most of the pages overcome the problem. At least, it is in my case.
2- Yes, I also thought the same. Mobile + Amp is active
3- Great! no problem with that.
Please see the broken icons
https://pasteboard.co/IcOdSdT.jpg
It also does look like very differen than the AMP formats…
Hi,
I see the broken icons, quite unusual. There is an unusual error leading to the old AMP plugin included in the theme package – http://prntscr.com/njvzpm
Google seems to try to serve the icons from the old plugin, which is not possible since the plugin is not used anymore.
Google should refresh the cache eventually and the issue will fix itself, from what I can find there is no way to do a refresh for the whole website at once
– https://support.google.com/webmasters/forum/AAAA2Jdx3sUu-NxYVzwmcM/?hl=en&msgid=qIpiBA4VAwAJ&gpf=d/msg/webmasters/u-NxYVzwmcM/qIpiBA4VAwAJ
– https://getmxt.com/update-google-amp-cache
Thanks
Hi Simon
Thank you for your reply. So we will have to wait for google to update amp caches. However, from time to time our desktop results showing a strange amp format..I’m not really sure if this looks like amp but something wrong..
https://pasteboard.co/IdoMMwKK.png
Why this kind of format comes up for our posts
Hi,
Looks alright now – http://prntscr.com/nl2zw4 I have seen cases when the mobile theme was loading on desktop, usually it is caused by caching plugins, or maybe optimization plugins or settings from them. We recommend the super cache plugin, which work alright with the mobile plugin. I browsed the website for a while, for me this problem did not happen however.
WP super cache is not showing any performace on our site. We tried that plugin on many sites but It is actually slows down everysingle project of ours. And its not AMP friendly if I remember correct. w3 total cache giving a really good boost to be honest.
Only this category and only English version having the problem now. It is designed a little different than other categories.
Solution. We changed the layout of the catergory page the side bar position from no side bar to Right side bar and it seems works.
https://pasteboard.co/Ids2bxA.png
https://pasteboard.co/Ids3yD4.png
So if you change it back to no sidebar the issue will happen again? Quite unusual if that happens.
The super cache should be equal in performance with the total cache, or maybe behind by a small margin. Most reviews rate it as the second or third best caching plugin out there. But the result could be indeed different case to case. It looks like the total cache is performing good on the website, it’s quite fast.
Yes, it happens again. If any of the templates(Page template, category template etc) are choosen as Default Template in the theme panel, the site brings strange amp version to desktop, especially on the secondary language.
Yes, many people happy with WP Super Cache but it never worked with us unfortunately.
Simion, I actually sent an email to contact@tagdiv. It seems that we are eventually have to move to TagDiv composer. So we tried to create a new homepage but getting errors. So should I wait for a reply or can you help us out from here?
This is the error we get to create new page https://pasteboard.co/IdztlKP.png
If you have sent us an email we will investigate and reply by email.
Hi Simion
The issue removed. Actually we did nothing. Thank you for your help
