LOL: don’t get me started on Jetpack … won’t touch it.
Usually something in the sidebar breaking the “width” …
@dritanleka
best to start new topic unless that question is related to visual composer asking about activation.
See the theme docs right side of page….
read through the how to install theme, AND the plugins;
then see how to load demo “styles” to look like any of the demos.
You normally have to either use a pre-set style, or build your own layout for the home page how you want it.
You can do anything with AMP except you cannot load funky scripts in the header, you must only load https elements, and you must have clean code with no old-skool inline styles like
<p align="center">
should be
<p class="pcenteed">
and the like.
AMP ads are simple, just make a hook in your functions.php file to load the small 250px graphic from adsense, using Google’s examples on the adsense website, and several tutorials online. It cannot be done in the TagDiv theme panel as the amp endpoint not part of theme.
Easy to hire a WP developer if none of that makes sense 🙂
Nope – the bundled plugins don’t need license codes to use. They do however periodically popup a sales message to try to get you to buy it, which is dumb. Not fault of theme devs, but the plugin makers.
Just install and activate the ‘bundled’ versions included with theme in plugins folder.
You can try these options (note, theme does not create redirects)
Check your htaccess file and remove any redirects there, as first option.
Remove child theme folder; consider not using one.
Second, if you activated a bad plugin; rename your plugin folder to xplugins via FTP; this will force disable all plugins. Or, remove any ‘redirection’ plugin from the plugins folder if you recently activated one. Or, try removing Yoast SEO if you setup a bad setting for that.
If you still cannot access; delete all themes in wp-content/themes except twenty-sixteen which will force WP to ‘fall back’ to that version.
You have to customize amp template to support ads. Simplest way is using filter added to functions file. Amp template not part of theme. Just remember you can onlu use the small ad sizes for mobile.
Theme does not control amp plugin. Yoast glue adds some options. Just remember to resave your permalinks when enabling or disabling amp support since it adds new endpoint for pages.
If part of theme see the post settings page in theme panel.
Best to avoid inline styles on divs and only use css classes. If you are using some kind od ad plugin might be problem with that. Try using f12 console view for errors.
Note the hours of operation noted top of the forum.
They will be back Tuesday.
Try reading the setup docs… See link right side of page and start at beginning.
I dont work here.
I think they are working on it.
Mobile them does not need to support AMP; as AMP is separate framework and can easily be enabled with
a) Automattic AMP plugin (from people who make WordPress)
b) Yoast SEO
c) Yoast AMP glue addon (free)
This way mobile theme used for browsers not supporting AMP; and AMP used for those that do.
Note that content plays huge part in AMP compatibility; so bad content, bad plugins, etc., all have to be massaged. Which would be nightmare for the theme devs on top of all the folks who can’t read the docs.
I don’t work here; just my opinion.
We’ve been live with AMP since Feb; in beta since Nov 2015 on our high traffic 11-15 year old news portals; and works very well. Automattic AMP plugin is good baseline to use for now as it’s also used on some of the top WP-powered sites (e.g., TIME magazine, major newspapers running on AMP, etc.). It works, and you can easily test it using Chrome and the console view.
Try resaving your permalinks. Turn off any settings in Yoast SEO that remove slug words. Clear any caching. Make sure you have backup of your site dbase before doing anything else!!
Keep backups of older versions of theme/site before updating so you can ‘go back’ when possible.
Theme has nothing to do with “links” or post names/slugs; that’s a WordPress / dbase issue and usually caused by
1) settings in yoast to change link behavior
2) some kind of redirect plugin gone bad or htaccess rule setup to do regex type redirects
3) some old plugin not compatible with new version of WordPress or PHP used on your server
4) site not updated properly (e.g., when updating theme you also MUST update the included plugins!)
I don’t work here; just some advice.
I think it usually states latest version on Themeforest ..
========
\\
Version 3.1 – July 25th, 2016
UPDATE NOTICE: Please note that this version does not work with legacy Visual Composer versions.
————–
( was just downloading latest one myself; one of my sites was still on 1.6 ! )
Just use normal modern html5 tables. I usually put a class of table on the table element as default.
Lots of online tutorials on modern tables with proper opening and closing tbody tags, etc.
Also remember you need to activate the avatar option in the main wordpress settings.
We have been using the automattic amp plugin, with yoast seo and yoast seo glue. We started in beta with amp nov 2015 and so were ready at Feb 2016 roll out. Tagdiv themes work great with this setup.
Keep in mind also that many other themes load up to 20 files which also add up to a lot of css … However, when i tuned the crap out of v2 i did take out bbpress, woocommerce, translation support, and moved to mobile default font stack… Which wordpress is moving to also. Hoping tagdiv will consider adopting the new wp default font stack also as google fonts do load bunch of extra page size.
Trade off. But im used to bootstrap 2 ?
Ricky..
I changed the little text element to ‘views’ in place of ‘post_views_count’ which fixed my issue with existing counter data. Just open the one file in a text editor the upload via ftp… Downside is you have to repeat fix each time updating theme. But good time to learn how to do this stuff. Also make backups of everything!
Not fixed in latest yoast… Sheesh. Trick is either to switch to the news seo tab if using it, …or… Widen workspace to fit. Its the first default tab which does mot appear to be responsive. 3 newsmag installs, 1 newspaper, 3 other things all have this funky behavior. Reported with 3.4 not yet fixed in free or pro version apparently.
Try editing your wp-config.php file (download via FTP); and put the explicit URL for your website in the file per the WP codex on how to edit wp-config.php file.
See
https://codex.wordpress.org/Editing_wp-config.php#Blog_address_.28URL.29
You should not change the web address setting in your blog unless you know what you’re doing — obviously 😉
Actually better to do a 301 redirect to the category index the post used to live in for SEO.
Issue with Yoast, not the theme.
Happens with multiple themes, and has been widely reported on the Yoast SEO support forum on WordPress.org — always best place to look first for plugin problems 🙂
Affects some themes, and not others. This started with new version of YOAST 3.4 I believe, and not fixed with the 3.41 patch.
Hopefully fixed in Yoast 3.42
Likely good to read up on how WordPress works in general. This “theme” doens’t control how posts, categories, tags, or anything else related to dbase is managed (e.g., the ‘content’).
One strategy is to make ‘featured’ categories such as ‘breaking’ or ‘featured’ and initially post stories in those categories, then when you need to retire them and no longer want them in those feautured categories, simply revisit those posts, and change the category from featured to ‘archive’ …
There may be a plugin or script which allows you to setup a date range and automatically do that.
Normally in WP, one creates indexes or home page blocks which are date based, meaning if you have 10 featured items on home page, they are all there until item 11 is published, then item 10 drops off that module. Everything is still there in the dbase, and date based archives in WordPress, searchable, etc. URLs don’t change, for long-tail view from social, search, etc.
But not really theme related in any way.
Works fine with my site on https.
Can you describe the issue specifically you’re having with something not being secure.
Your site has to be properly setup for https and all your images possibly search/replaced if placed in code via phpmyadmin — theme cannot fix “content” for you or parts of WordPress or image folder, etc.