I was facing the same error recently. It turns out the tag div composer is not working on your website.
Simply go to cpanel in your hosting and delete the plugin- tag div composer. Next, do a fresh install either from the theme panel or directly through file manager.
Activate the plugin and it should work just fine.
Re-enabled the amp. Kindly check now.
Moreover, the in-line article ads are not showing up. Guessing what could be the issue. Have enabled the auto ads too.
Maybe juice up with bootstrap a lil bit? 😀
Website link?
Home page is not supported. And neither are other pages, only post types are supported.
Exactly. The mobile theme is faster enough, why lose 80% of functionality for just 0.5s speed? For me, i lose my onesignal, social shares, adsense revenue, no fb page like popup, and yeah, increased bounce rate because visitors have no clue how to navigate.
I would definitely recommend Newspaper. However, the tabs are not in the features yet. For that you will have to go with a plugin or try a bootstrap theme.
P.s- you can add your own tabs, try this- https://www.w3schools.com/howto/howto_js_tabs.asp
-
This reply was modified 8 years by
drvarun5179.
You just have to wait till google identifies your amp pages. Error comes only when your posts are not accessible on /amp pages.
Amp is not meant for home page or other pages, but only post types.
@themeforest58, you do not need to redirect. Google bot will find your website is amp ready, and your links shall become amp automatically.
Disable speed booster plugin amd try this guide once-
https://forum.tagdiv.com/topic/newspaper-theme-speedify-your-website/
I did that on my website website, and i believe there are many hosting services which do not provide free ssl cert. Like mine, Godaddy didn’t.
Apart from that, Cloudfare is really a need, it’s a good “Free” Cdn with additional speed boosting with rocket script.
Thanks for the feedback. So far, i have rolled back to non amp by simply deactivating the plugin. However, some posts were already converted to amp in serps.
Those using amp and trying to revert back, please do not use 301 redirection. Let the 404 error come, google itself will recognise your website is no more amp. Creating a 301 will tell google its not amp and will just confuse search engines and hence, loss of seo.
P.s- i believe amp is not really good for the hardwork writers do on their blogs. It will strip off your website, and the revenue share is cut off greatly (since amp ads don’t really have higher ctr). Moreover, since you lose page navigation, bounce rate will definitely increase. Rest your choices. 🙂
You don’t need to use any plugin. All you need is Free Cloudfare Cdn, it provides ssl certificate for free. Then you will have to add it on your hosting. To check the errors, you will have to do view source of page and find any element that messes with the fully https functionality.
-
This reply was modified 8 years by
drvarun5179.
You don’t really need to add ad code to all pages or use a plugin. Simply edit the template and open header.php. There add the ad code between <head> tags.
Bump*
Yeah. The update is perfect except the amp. If you need the previous version, you can ping me.
@leytol amp pages are meant for mobiles only, not for desktop browsers.
Thnx for list @epickenyan , i have been using WpFastestCache and AutoOptimize previously. But WpSuperCache is the most supported Cache plugin for Newspaper theme when using Cloudfare+CLoudfare’s Rocket script. I had to abandon the former ones because in the end, lots of plugin only adds to server load and hence a slower server response time.
Hi @dariosipos , you can try setting up mailchimp for that. Apart from that, google feedburner is the simplest idea. It’s quite easy to set up though.
-
This reply was modified 8 years by
drvarun5179.
It’s only your own browser cache that is making you see the error. Others are still seeing the correct version. Clear it and you shall too.
I guess you are using adsense at the wrong spot. Following code is the issue,just fix it:
<ins id="google_pedestal_container" style="width: 100%; z-index: -1;"><div style="height: 2626px; width: 600px; margin: auto;"><ins class="adsbygoogle" data-adsbygoogle-status="done"><ins id="aswift_6_expand" style="display:inline-table;border:none;height:2626px;margin:0;padding:0;position:relative;visibility:visible;width:600px;background-color:transparent;"><ins id="aswift_6_anchor" style="display:block;border:none;height:2626px;margin:0;padding:0;position:relative;visibility:visible;width:600px;background-color:transparent;"><iframe marginwidth="0" marginheight="0" vspace="0" hspace="0" allowtransparency="true" scrolling="no" allowfullscreen="true" onload="var i=this.id,s=window.google_iframe_oncopy,H=s&&s.handlers,h=H&&H[i],w=this.contentWindow,d;try{d=w.document}catch(e){}if(h&&d&&(!d.body||!d.body.firstChild)){if(h.call){setTimeout(h,0)}else if(h.match){try{h=s.upd(h,i)}catch(e){}w.location.replace(h)}}" id="aswift_6" name="aswift_6" style="left:0;position:absolute;top:0;width:600px;height:2626px;" class="lazyloaded" data-was-processed="true" width="600" height="2626" frameborder="0"></iframe></ins></ins></ins></div></ins>
Use this- https://screenshot.net/nodjesg
No problems 🙂
You should remove the picture insteaed, it only adds to load on website. Think in broader terms, how many people actually click on mobile menu? That was one reason i removed it too, like few hours ago. You can test my website speed here: https://medicforyou.in