You may want to send your login credentials to tagdiv team to login and take a look.
I’ve been using it since it was in beta quite a long time back, and use it on my own server with CentOS/Plesk, with PHP5.6, 7.2 and zero issues.
There have been known issues with some plugins — when the plugin has an issue; like Yoast having errors, etc.
Turning on DEBUG MODE in WP can help; looking at error logs for domain, etc. all useful.
(FYI – point about old vs new posts getting answered; repeat posts on same thread make the thread ‘new’ again, vs ‘old’ and the non numerical way they answer stuff here means if you “leave it be” it will get answered quicker; if you keep posting updates, or others try to help; it actually gets answered LATER… but I don’t work here; just been on here since 2013.)
They answer support queries in order received, oldest first, so reposting over and over pushes query further back.
Often problem with plugin is a conflict with something else… caching issue… or php version too old, etc. … lots of possible reasons. Not every server, hosting, or plugins used the same everywhere, hence why it works for 9 people but not the 10th.
Yes, welcome to WordPress. That is what happens when you change themes.
There are some plugins which try to address that, but WP has always done that – otherwise if you had a custom plugin or widget code running, when changing themes entire site might crash due to missing code/functions, etc.
Theme does not control that; totally part of WordPress. There is some mention on the WP dev forum that they will be trying to come up with solution for that in the big giant next version of WP (5.0).
Those are all ads. You need to remove all ad units or plugins loading ads.
You should not use inline html anymore. You need to create a style class then apply the style class to the h3 element.
See tutorials online re using css3 and html5.
You can edit the post meta shared with Facebook using the Yoast plugin .. or, always make sure you add a ‘manual excerpt’ to your posts which is what gets written the open graph og:description tag used by FB.
You can add advertising to AMP, and we do that on some sites; but also we do stuff like use a text based “related posts” plugin to inject related posts via shortcode to footer.
There is super dead simple function for the AMP plugin to ‘inject’ anything into the footer spot without touching AMP template. Trick with ads from Adsense is they need special form of java loading, but tutorials online for that. Loading your own local ads is easy, as an image or text based ad is just basic CSS. We add a text based ad for our services to bottom of the blog posts on our main site for example.
It’s work – but good to learn. We chose to stick with the ‘official’ AMP plugin, as it’s going to be most compatible with WP, not get abandoned, have bad code, etc.
Since our news sites are all news, the AMP plugin doesn’t hurt. Ad revenue is down so much we’re likely going to abandon adsense entirely this year and do local ads again instead (e.g., ‘sponsor this site… $99 per month for run of site…’ kind of thing).
Best to disable the ‘lazyload’ effect.
To learn how to optimize WordPress on your hosting account, see the tutorials section here and also try testing a post at GTMetrix.com and then read the suggestions for pagespeed improvement (ignore the yslow).
Well, the official AMP plugin from Automattic (the people who make WordPress) works very well, and there is a ‘glue’ plugin for use to connect that to Yoast SEO. I’ve been using the AMP plugin since it launched couple of years back, with zero hassles. Latest update supports pages, if needed; and has separate page or post templates which can easily be edited.
Note AMP only works if you have enough traffic to warrant it and if the pages all validate in Chrome with the AMP plugin activated. It’s NOT a full-on replacement for a responsive or mobile framework — it’s an “additional” element which only works on supported devices and if Google “blesses” the posts to add to CDN, and then will be shown in SERPS with AMP icon – and also in your Google Site Manager account (or whatever they are calling it this year).
So, worth doing – but it’s not a be-all, end-all solution for mobile at this time — simply an additional option. Frankly a normal responsive site with fast mobile speed, https, and http/2 is also as important.
( I don’t work here; just long time TagDiv user, webdev dinosaur, and WP user sicne v1)
forgot the other link
http://www.wpbeginner.com/wp-tutorials/how-to-add-post-thumbnail-to-your-wordpress-rss-feeds/
🙂
Theme has nothing to do with RSS feeds.
There is long standing documentation on the web to add a ‘function’ either via theme or plugin, to inject the featured image into the attachment based on featured image.
Also – note that if you have no featured image “inside” the post meta, there will be no image in the RSS feed.
You can easily view your RSS feed code in Chrome to “see” what is actually there. Feedburner does show images as long as the image is in the post meta and not “outside” the body — for example, some templates where the main image is in a background div, or outside the post meta — obviously is not in the post meta for the RSS feed.
It’s well known, but perhaps new to most, that you can simply create your own RSS feed by making a new post template and then publish that feed to syndicate (we do that here).
So, you might make customfeed.php as a page template, make empty page with that name, select the template; then you end up with mysite.xxx/customfeed/ as the feed.
By making a custom RSS feed, you can include the ‘large’ thumbnail for the featured image within the top of the post meta in the FEED template, so that there is always the image in the feed.
Some info
http://www.wpbeginner.com/wp-tutorials/how-to-create-custom-rss-feeds-in-wordpress/
I don’t work here — just some feedback. Theme doesn’t control the default WP RSS feeds — was the upshot; the RSS is part of WordPress, and simply pulls post meta and nothing else.
Probably need to do a clean install; turn off caching, extra plugins, etc. — See the ‘how to install’ docs…
Page view counter is just a simple hit counter; you visit page, it increments. It does nothing else. Theme has nothing to do with Google Analytics, so you might check the support forum for GA to see how they count hits/visits or get blocked by certain browsers, etc.
( I don’t work here; just some feedback. )
Changing themes doesn’t remove posts; as those are in the database. Check your ‘posts’ menu and they should all be there. Also, good idea to plan a backup strategy to make proper dbase and export backups prior to *any* major site changes so you can roll back.
( I don’t work here; just some feedback while you’re waiting. )
Official AMP plugin got major update today with pages support and direct preview button integration in main post editor.
Caching issue.
It’s only an issue with some hosting systems. WP does, in fact, micro cache a lot of that, and if you’re using a proper caching plugin, that should help as well.
I don’t work here, but just some feedback. Most people don’t actually care how many followers you have as those can be inflated by zombies/sock puppets anyway, and so are not relevant to anything except perhaps ego (my own opinion, anyway).
See the install docs.
Install just theme zip, not the ‘all files’ zip.
Useful to unzip on your PC/Mac first to see what’s there before uploading. 🙂
Welcome to WordPress!
anything that goes out — uses resources … turn everything like that OFF, then turn things back on to see how it impacts your site/hosting… folks too often turn every bell and whistle on then things crash… start with all the extras OFF, then add a little at a time and test!
Azulita
anything that makes ‘outbound’ connections has to actually “go out” and get data and bring it back; this includes anything connecting to twitter to auto populate tweets inline vs in iframe, and the ‘number of likes/shares’ elements for social media.
With shared hosting, these elements can eat up a lot of bandwidth, since a script on the host has to actually GO OUT to those sites, then populate the data on your site pages.
@Azulita
disable the twitter element and/or the ‘number of likes’ options for social stuff.
Link to docs page and api page work for me.
Usually a caching issue.
Also check the ‘status’ setting in the theme control panel.