- ApiUsing the Theme API in plugins
- ApiPractical example – How to add a new Block and Module
- ApiAPI – Smart Lists – Introduction
- ApiAPI – Category top section style – Introduction
- ApiAPI – Category top section template – Introduction
- Apitd_api_module::update
- Apitd_api_module::add
- ApiAPI – Modules – Introduction
Hello,
Sorry but still no go. The site cannot be reached. I have tried from my mobile device using the mobile data so the ISP was different but the site still cannot be reached. You maybe have a country block maybe. We are located in Romania.
Regarding your issue with comments, please disable all plugins except visual composer, clear cache and reset cdn files if you use it. Please also check any custom code you might have added to the theme panel or the theme files. If you use a child theme, please switch to the main theme to make sure it does not affect the proper functionality of the theme.
Thank you!
Generally, the AMP version has no relation to the main theme as the AMP endpoint is highly mobile optimized and doesn’t support any of the theme features, so kind of pointless to have as “part of the theme.”
But we all have our own thoughts on this.
What if TagDiv abandons the theme on your 100,000 page site, and no longer works with PHP 7.5? You’d need to suddenly change to an agnostic plugin. if you had been using agnostic plugin originally, it would work regardless of “theme.” I prefer that “separate” function, personally, especially if it gets added into something like http/2 as a feature.
I’d like a flying car, too, but not going to hold my breath 🙂
I’m out!
For example the mobile plugin could support non https, and support javascript, and various things which AMP does not support, ad units, TagDiv API, speed booster hooks, etc.
The only reason I’m suggesting a single plugin as a solution is because AMP for WP, when used with Automattic’s AMP plugin, can function as both an AMP plugin and the site’s mobile theme.
I can toggle a setting in AMP for WP and it will replace Newspaper with its theme (which is AMP compliant) for any mobile visitor.
That’s what I would envision Newspaper’s implementation to be like: completely transparent to the end user. For normal people who don’t know what AMP is, it would serve as a mobile theme as it does now. For those who want AMP functionality and are willing to live with the limitations it brings, they can flip a switch and everything is instantly AMP’d.
It’s not like the work hasn’t been and isn’t being done by the AMP for WP guys — everything is open source and freely available. It could literally be taken, sprinkled with a little Newspaper magic and be ready to go.
I get what you’re saying. I would think that the developers would be MORE interested than I am that websites using their theme have the best AMP experience available.
Let’s say — for the sake of argument — that Newspaper is the best desktop theme available anywhere. And, continuing this hypothetical, let’s also say that on mobile, when using the mobile plugin, it’s also the best theme money can buy. The absolute, hands-down best.
If this were true, why would the developers be okay with whatever AMP implementation a site owner wants to use?
To protect the integrity of the theme and keep it at the forefront, I’d certainly want to offer my own solution if I had my name on this theme.
But to have every experience be the best available EXCEPT when someone clicks into a site from a mobile search result? That reflects poorly on everyone involved.
I guess my point was, theme devs not going to make the theme mobile plugin setup for AMP, as this would introduce giant amount of support for people who don’t understand AMP or how it works.
For example the mobile plugin could support non https, and support javascript, and various things which AMP does not support, ad units, TagDiv API, speed booster hooks, etc.
It would be NICE if they had an AMP plugin that works like the mobile plugin, as separate paid product, perhaps, which could replace the one included with theme with specific guidelines on what it does and can never do. Two totally different things.
Making ONE mobile plugin for theme that worked for both mobile/noAMP and mobile/AMP would add huge amount of code bloat, also possible issues with adding the AMP end-points and hooks and all sorts of bizarro potential issues with folks who can’t even clear their caching when updating.
“In a perfect world…” sure, would be nice. But unlikely to happen anytime soon.
Frankly, I believe the “back end” skunkworks plan is more focused on developing a replacement for Visual Composer for their “ION” version and doing sideways dev on that which can be sold outside of ThemeForest as traditional foundry method (“direct sale”).
I got what you were saying about “wouldn’t it be nice if …” — I was just pointing out wasn’t going to happen based on working with them for 3+ years here.
The support overhead for that would be insurmountable from a business case standpoint. Look at all the issues with Facebook (“why doesn’t my photo show up…” or “why isn’t my views incrementing…” “why do I need a Facebook account to use the FB widget …” etc.). So, experienced devs already moving on making their own solution based on the available tools; newbies already confused by what AMP is, and unlikely to get the issues with search/replace of inline styles, ad unit custom inserts, etc.
It’s awesome we have so many active folk here actually “into” this stuff.
My opinions are only my own, so take all with grain of salt — sure you were doing that anyway 😉
But again, to get on with your life you really should consider this the way forward:
a) desktop > theme CSS (main URL)
b-1) mobile > theme CSS responsive (main URL)
b-2) mobile > theme plugin/CSS mobile (optional) with custom settings (main URL)
c) mobile > AMP compatible > AMP plugin + custom template (AMP endpoint)
You can only have 3 of the 4 options as it stands.
In our case we do a, b-1, c.
What you were wanting was a, b-2 – where b-2 has multi-thread option based on visitor including redirect to AMP endpoint vs normal URL.
Betcha box of gingerbread cookies you will have an eternal wait on that!
Hi,
If you would like to change the default functionality of the mobile theme, this can only be done by modifying the theme files. Please follow this topic and make the mentioned changes to the specified file
– https://forum.tagdiv.com/topic/mobile-theme-featured-posts/
Thanks
Hello,
Thank you for your appreciation.
1) I have tested your site on mac but could not see the line you mention. https://www.screencast.com/t/kHdvVpdbcJUN
2) Our theme has a custom login already which can be accessed on the front-end: https://forum.tagdiv.com/login-how-to-enable-user-registration/ – https://www.screencast.com/t/D0BiMNXRTqyG
3) sorry but there is no gradient color section for the header and footer but you can add a footer background image: https://www.screencast.com/t/rKgVA4TL
For the header it can only be done with custom css.
4) Sorry but only by using the obile theme can you have a separate menu for mobile devices.
5) The quotes can be changed from the fonts option: https://www.screencast.com/t/tcwLRz4daHU
6) and 7) It is ok as there are no restrictions in this regard. It will load all of the elements, yes, but you should not experience drastic loading speed drops. It is recommended to increase your overall loading speed by using this guide: https://forum.tagdiv.com/how-to-make-the-site-faster/ and increase your system status parameters like so: https://forum.tagdiv.com/system-status-parameters-guide/
lease only use wp super cache and these settings: https://forum.tagdiv.com/cache-plugin-install-and-configure/ if you plan on using a cdn server: https://forum.tagdiv.com/cloudflare-cdn/
8) This topic explains how to use speedbooster together with other plugins: https://forum.tagdiv.com/topic/tinymce-advanced-and-other-various-disabling-speed-boster/
9) Please provide an example as the image is not working
10) The validator also provides errors for ALL of the well known sites including google, facebook, Amazon, Yahoo, etc. We have stopped trusting it 🙂
Thanks
Hi,
I would like to use another category for the top 3 highlight grid when using the mobile theme plugin instead of Featured.
How do I do it? Thanks!
I’m sorry, I must have missed where Chris offered advice on how to achieve what I’m looking to accomplish.
I’m asking for the mobile theme that is put in place when the tagDiv mobile theme plugin is activated be AMP compliant so that when someone searches on mobile and clicks an AMP link, that is what they see.
Anything less than that is unsatisfactory and very much a brick wall.
I’m not looking for alternatives. I’m not looking to modify some existing AMP template to be close to the real thing. These are all workarounds that offer a less-than-optimal experience. Am I the only one that sees this?
What I don’t understand is why everyone seems to be so accepting of compromises and workarounds.
Just a quick note: I already have a heavily customized AMP implementation that is just as functional as the tagDiv mobile theme (maybe more so). The problem is that it ISN’T the tagDiv mobile theme. It’s not like I’m not familiar with how this works and I’m coming at this with zero knowledge which seems to have been implied in this thread.
Hello to the whole Newspaper/Newsmag team!
First I want to say, thank you very much for creating such great themes.
After 3 years I decided with my team to change the overall design of my homepage, by buying Newspaper7. The reaction of our readers and users are mostly positive. So thats a good sign.
Of course such a huge change is not that easy to handle and thats why I still have some problems and question, which should be solved.
All problems occur on the latest version of Newspaper 7.8
1) On my MacBook with the default Safari browser, I often get this annoying and bad looking line through the whole header section. How can I solve the problem?
2) Which register plugin should I use? I don’t want to let new users to set a new password on the bad looking interface of WordPress. Im sure you guys know what I mean and have a good recommendation for that. Beside that, what should I use to prevent registrations from bots?
3) Is it possible to have a gradient header and footer, instead of just one color? It looks a bit boring.
4) How can I change the menu just for the mobile page, without using td-mobile-plugin?
5) How can I change the the font style and size of quotes? At default settings it looks way too big (see here)
6) Is it ok too use the responsive options, to create one site with different blocks and grids for mobile and desktop? Im asking cause I don’t know if my site will load much longer, if it has to load information even though there are not displayed. (see details here)
7) My current page speed is a disaster (see here). Why is it so bad, since Im using kraken.io image optimizer and WP Super Cache? How can I improve the score?
8) How can I use td-speed-booster, without uninstalling my plugins? (Disqus Comment System, TablePress, TotalPoll…) I really need those plugins, but I still want to have a fast homepage!
9) If I set [Template Setting->Force Full width->Header Menu] to “No Stretch”, the logo of my site is not at the correct position.
10) validator.w3.org shows, that my page has 33 errors (see here). How can I fix them?
You can’t make a page identical to your desktop version for AMP as that defeats the purpose of the mobile friendly AMP framework. It’s supposed to be “lean and mean.”
I feel like none of you are actually listening to what I’m saying.
I’m NOT advocating that the AMP version be identical to the DESKTOP version.
I’m advocating it be identical to the mobile plugin version provided by tagDiv which, as I understand it, was developed to be “lean and mean.”
I don’t want a responsive version of my site to be the AMP version. I don’t want responsiveness at all.
I want tagDiv’s mobile plugin with AMP compliance. That is it. Until this happens, I will continue to advocate for it. And, for the third time, the first news theme for WordPress that can offer a mobile experience (NOT a desktop experience) that is also AMP compliant will win my business.
To be validated as AMP content, it must pass Google’s AMP validation, and then added to separate “map” for mobile users in SERPS, and then they are presented *only* the AMP formatted version and NO other version. Also they get a lightning bolt element in SERPS to identify it’s AMP formatted and hence “speedy.”
The only reason we’re trying to explain to you how it actually works as some of us have actually been doing it for a year and a half.
You can’t make a page identical to your desktop version for AMP as that defeats the purpose of the mobile friendly AMP framework. It’s supposed to be “lean and mean.”
If you want a desktop experience on mobile, it can’t be an AMP version.
But you likely need to experiment with this yourself to see “what actually happens” vs the theoretical idea you have in your head.
Spend some time on the Google AMP docs for more information.
Anyway — just food for thought.
Theme devs not going to add built-in support, likely, for many of the reasons already covered here by everybody who has already been down this road and are “doing it right now.”
AMP needs custom classes, compliant post meta code, special ad unit setup, custom hooks for plugins, no use of javascript stuff, https-only elements, etc., etc.
I’m out !
I’m not disputing the fact that the AMP templates can be edited. I make many customizations to mine and have to make them each time the plugin is updated.
What I would PREFER is the following:
— Someone searches Google for content and sees my site in the search results.
— Because they’re on a mobile device, they’re presented with a link to an AMP-compliant version.
— When they click the link, they are taken to a page that looks identical to any other page on my site when viewed on a mobile device.
I firmly believe that the first WordPress news-focused theme that can offer this experience will win big. I simply don’t understand why anyone here is defending a less-than-optimal experience for website visitors who come in by clicking on an AMP link in mobile search results.
I appreciate your thoughtful response. I think it’s misleading to suggest that AMP “replaces” the mobile theme. It’s offered as an alternative to the mobile theme and with proper implementation, Google will find the AMP version, show it in mobile search results and rank it higher than a corresponding non-AMP (but still optimized for mobile) page. On my site, we use AMP for SEO purposes only and as much as we can, we direct visitors to the regular mobile version of our site because this is the experience we prefer and want our visitors to have.
Just like theme authors keep up with the ins and outs of changes to WordPress and how their themes interact with various plugins, I don’t think it’s too much to ask that they keep up with AMP.
There are many plugins like AMP for WP that take what Automattic is doing with their “agnostic” plugin and greatly enhance it. For example, just in the time that I’ve been using AMP for WP, the authors have added optimizations specific to Newspaper as well as support for plugins that do not display properly with Automattic’s plugin like Tobias Bäthge’s awesome TablePress. This is all done, of course, without breaking AMP validation.
I’m not suggesting that the Newspaper developers start from scratch. Plugin authors like those behind AMP for WP have shown that AMP functionality can be extended using Automattic’s plugin as a base.
My idea would be for tagDiv’s mobile theme plugin to work in the same way — essentially allowing Automattic’s plugin to do the heavy lifting and adding Newspaper-specific design and functionality on top of it.
My website, The Apex, chose Newspaper and continues to use it because of the awesome experience afforded by the mobile theme plugin. However, that experience becomes diluted when the best experience can’t get the best search ranking due to Google’s insistence on AMP compliance.
I have seen very good AMP implementations on other sites that aren’t based on WordPress — so good, in fact, that it was nearly impossible to tell the difference between AMP and non-AMP. This demonstrates to me that it is indeed possible to offer a fully functional and well-designed experience while keeping in compliance with the evolving AMP standard.
Seeing these sites should make it abundantly clear that what is offered by Automattic’s plugin isn’t sufficient. Yes, it creates pages that validate against the AMP standard. But it doesn’t make the THEME compliant with AMP, only the site’s content. I’m doing a disservice to my site’s visitors by giving them a less-than-optimal experience. I want them to use Newspaper’s mobile theme and tagDiv should want them to use it too — but that’s not going to happen as long as AMP pages rank higher than others and tadDiv continues to see AMP as a distraction.
The best news theme for WordPress, which Newspaper undoubtedly is, will not remain the best for long if it cannot deliver a best-in-class AMP experience for its paying customers like me. SEO is critically important for sites that use themes like Newspaper and denying the importance of AMP as well as the experience when viewing an AMP-compliant page is a big mistake. tagDiv should not be content allowing the AMP experience for sites using Newspaper to be dictated by a third party.
The first major news-style theme for WordPress that offers built-in support for AMP with no difference in the experience over non-AMP mobile pages will be a winner in this space. I can’t help but think that tagDiv is missing a huge opportunity here.
No. The AMP plugin replaces the mobile theme with the AMP version, where portions of the content get cached on Google servers under high demand as a CDN structure.
If you plan on using AMP as your main mobile element, then the theme mobile support is only used for those instances where AMP is not used.
You can modify the AMP templates however you wish.
Desktop => theme template
Mobile => theme template/mobile (optional)
Mobile AMP => AMP template via plugin
AMP has very specific requirements outside the scope of the theme.
For example, WordPress allowed you to use the visual editor to add <p style="center"> which is bad HTML in modern usage. This will cause AMP validation to fail.
Theme authors cannot spend the time to support the ins/outs of AMP which change over time, and for which there would be unreasonable amount of support time provided to those who don’t understand how WP works, how AMP works, and can’t RTFM.
It ONLY makes sense to use an “agnostic” plugin like the one from Automattic (we have been using it since Nov 2015). This puts the brunt of development/compliance on the backs of WordPress devs and not theme devs, since it gets used for all the tier 1 “VIP” WordPress sites like TIME magazine, etc.
Really — anybody who wants to implement AMP should look into using the AMP plugin, then learn to tweak per the requirements as that is “best” way to go to save yourself major headaches, pain, suffering, and torment!
It’s neither economically feasible nor support-smart to build entire AMP support into the theme, which is already provided by the plugin.
(( I don’t work here. ))
The official AMP plugin offered by WordPress greatly limits the functionality of the Newspaper theme. Multi-page posts appear as one page, Smart Lists do not function properly and many other elements are missing.
I have asked the Newspaper developers to introduce native AMP support in their theme but they do not seem interested.
Again, the official AMP plugin is not a suitable solution for most instances. What is needed is an AMP-compliant version of Newspaper’s mobile theme plugin.
Hi,
as we replaced our registration process with a woocommerce register page, we want to replace the “register” URL in the mobile menu (normal webpage, not the mobile theme plugin)
Additionally we replaced the standard wordpress search with the Plugin “WPSOLR”. We want to change the code in the mobile menu for the search page, because the search plugin (WPSOLR) works with an own search page and call, not the wordpress standard.
We already changed the search magnifier on the normal page (which is located in /parts/header/header-menu.php). Could you tell me, where we can find/replace the search code for the mobile menu + the “register” URL?
Thanks in advance!
Hi,
There is the official AMP plugin created by the wordpress creators that is compatible with the newspaper theme – https://forum.tagdiv.com/topic/tutorial-getting-started-with-accelerated-mobile-pages-amp/ if you would like to use AMP for your website.
This plugin created by the wordpress developers has been tested and works properly with the theme. Please follow the discussion in the topic provided above for more information about implementation and different solutions.
Thanks
Hello,
The category tags can be removed from particular modules and blocks from the theme panel: https://www.screencast.com/t/oRn1wt1rBt
If you want to remove the tag only on mobile I can provide a css code for it but I will need a link to your site so I can see what modules and blocks you use as the code must be added for each block in particular.
Thank you!
ok found my mistake myself and put the same code to the mobile theme custom css.
works
Hi,
i write a short code to mark all my Affiliate Text Links and put it into custom css:
a[href*="/geht/"]:after {
content: "PL";
vertical-align:super;
font-size: 8px;
}
PL = Partnerlink = Affiliate Link
works fine, but only on desktop and tablet PCs. The reference works not with the mobile theme. Means, the reference it is not shown on mobiles. Where is my mistake? Can you help me?
for example: Post with and without marked links
Thanks
Hello,
You use the mobile theme plugin and that will cause the homepage to get a predefined style that shows 3 top articles showing featured posts and a list of all your posts below. Right now you have the 3 top posts and 6 posts below. Please read this guide: https://forum.tagdiv.com/the-mobile-theme/
Thank you!
Hello,
You will have to use the mobile editor when using the mobile theme plugin. If you do not add anything in the mobile editor, nothing will show up on mobile devices. Please read this guide: https://forum.tagdiv.com/the-mobile-theme/
Thank you!
Hello,
I recently switched the Jarida theme (https://themes.tielabs.com/jarida/) to the Newspaper.
I detected that the Slider and the scrolling of the main page have a certain locking in the mobile version, not smooth scroll as it is presented in the Newspaper demo.
I deactivated all the plugins and activated one by one. I have detected that the Layered Popups plugin (https://codecanyon.net/item/layered-popups-for-wordpress/5978263) is generating this problem.
I come through this support asking to help me resolve this conflict. I have been using this plugin for over 3 years and can not stop using it.
Site: https://www.diariooficialdf.com.br/
Thank you.
