Well, if there is malware, back doors, porn spam, etc. in the pirate version … uh, yeah, it probably will hurt your site — having no idea “where” the “friend’s copy” came from ?

You do realize this is the same as installing pirate software on your PC, there are many files, php codes, snippets, javascript — all of which can be damaging to your site if malicious.

Have you scanned your site with SECURI yet ?

https://sitecheck.sucuri.net/

Reinstalling WordPress is pretty quick if you know how to FTP stuff — unzip the clean WP installer from WordPress.org ( not from ‘a friend’ ) and then drag over all the pieces to your site “over-writing” the existing files … just to do quick safety check vs doing nothing at all. Replacing the default twenty-sixteen theme with clean version, deleting ALL other plugins and themes, is a wise choice.

Have you done anything at all, like research this on Google — it’s your site, only you can fix it if something is broken from using “borrowed” software. Theme devs can’t fix that for you.

http://www.wpbeginner.com/plugins/how-to-scan-your-wordpress-site-for-potentially-malicious-code/

Hopefully lesson learned!

Not an SEO issue. Blocks on a home page or index page which contain your story indexes need to be there for page to render. Google reads text on your page, not the DOM elements that build layouts. Even if you move your “mega menu” to external file, it still needs to load on the page when viewed by a robot or other element.

You’re better off doing “fetch as Google” and using Google PageSpeed Insights, mobile friendly check, GTMetrix.com test on your post, as barometers.

SEO is most affected by your title tags, h1 tags, actual text relevant to the title tag and permalink, the amount of original unique info on the page on topic, and external links to your site from other sources that cite your page as relevant to that, even if it’s just social sharing.

The HTML used to build the DOM, does not “hurt” your SEO, unless you have two paragraphs on a page and then a mega menu, and 50 blocks of other stuff unrelated to that one page.

Just food for thought having done SEO since March 1995.

Theme documentation is great place to start.

Note the link right side of the page >>>>> “Documentation” 🙂

See:
https://forum.tagdiv.com/breadcrumbs/

Breadcrumb format is chosen by Google based on any breadcrumbs you have on your web pages/posts.

Theme cannot control what Google puts into SERPS.

You can only do one of the following:
a) disable breadcrumbs, and Google may eventually go back to only showing name of website as link under page/post name in SERPS

b) customize your breadcrumbs using a plugin like NAVXT how you want them, and Google will “usually” follow that formatting.

Again, the theme does *not* control how your content appears in Google. You can also try using Yoast SEO breadcrumbs as another option, if already using YOAST.

However, if this is all new to you, best option is to simply disable breadcrumbs from the theme panel, and then resubmit your sitemap (if you have one) to Google from your Google Search Console account.

Good luck!

You should fully delete the pirate version your friend apparently had — I may be mistaken, but best to be safe; and do clean install of WordPress to be safe. Do it via FTP, so you can delete old versions of theme folders (all of them!), old plugins (all of them!), and do clean full install of WP. Seriously.

Note that they answer tickets in order received; so posting updates actually pushes it back further in queue; oops, I did that too.

Basically, install theme and plugins via FTP if you have permissions issues on your hosting setup (where WP cannot remove/delete stuff in folders); this way you can *see* what is actually there, remove broken install, and do clean install of theme; this is very often the issue where something broke on server when WP was unzipping the zip file, and now can’t delete it due to being messed up. It happens 🙂

Try FTP upload/install — best way, every time!

(( I don’t work here; just 3+ year user! ))

And you’re funny looking. Spread the word!!!!!

See my other reply to your post, which tries to help you.

(( I don’t work here. ))

Did you try the normal fixes to solve the issue with your WordPress setup?

a) proper install of theme and plugins; disable plugins that came with former theme
b) check enough system resources per the theme system status
c) disable plugins you might be using that conflict with Visual Composer
d) clear cache in browser and on your site
e) RTFM (read the instructions)
f) turn off ad blocking or intrusive anti-virus that blocks your own WordPress admin panel
g) be very specific in WHAT does not save, where, and what you did to try to debug why YOUR setup isn’t working
h) review other topics on here as to how folks fixed their particular problem, such as using cloudflare the wrong way, or not clearing cache, etc. — only YOU can manage your own website — theme cannot fix things unrelated to itself, nor can others
i) if you ask for help, people here try to help
j) insults and the like help no-one

Tens of thousands of people using this theme for 3+ years use it every day; but not every web hosting setup is the same. If your setup works with “normal” WordPress settings and is up to date with latest secured version of WP, theme should work if properly installed.

Tech support offers help as time permits, in order received, and they do respond to everybody and all emails. And have always done so, as I can attest as long time user.

Don’t give up! Try to check some of the things mentioned above AGAIN, if done already — try changing to different web browser (e.g., CHROME); if you’re using broken old version of Safari on Windows, or similar, that can be issue also.

Helps to describe what you are doing and HOW you are doing it, and perhaps you will get some help.

There is no real way to do this in responsive design without using tables, as CSS is designed to “float” based on browser, content width, etc. — so, if you set a fixed height and somebody did a zoom, text would be chopped off. If the browser viewport changes and the text drops onto another line, the last line would get chopped off, etc.

This is why we usually use modules where image is on top, then the headline so that the “apparent” height of the photos across a horizontal row looks more consistent.

The old way was to use tables, where the headline would be in a table cell, photo in cell, excerpt in cell; but the webdev world decided tables were bad (stupid). Bootstrap 4 is doing some cool things as workaround for this kind of issue, but in normal CSS no real way to do that very well.

Try using module with photo on top, then the headline, and see how that looks. 🙂

(( CORRECT ME IF WRONG! ))

It’s the latest version of Newsmag 😉

From your Themeforest account, “downloads.”

——–
\\
Version 3.1 – July 25th, 2016

UPDATE NOTICE: Please note that this version does not work with legacy Visual Composer versions.

new: Visual Composer plugin updated to the latest version 4.12
new: login, register and forgot password ajax windows, a complete and more modern redesign.
new: added support for full height rows, column position and content position on them in Visual Composer.
new: added support for parallax speed on rows
new: added support for equal height inner rows and content placement
new: setting to hide the author name on modules and on single posts independently. Previously there was only one global setting.
new: Added support for custom fonts in theme panel that are uploaded via the wordpress media gallery. The custom fonts can be used just like before on most of the theme’s UI without writing any code
new: the weather widget now opens an input if it’s unable to locate the user via the browser’s location API.
misc: we fully rewrote the trending now block, it’s now leaner and it works better
misc: block parameters now have a better description
misc: code improvements to the following shortcodes: td_block_big_grid_slide, td_block_homepage_full_1, td_block_ad_box and the video playlists
misc: the media gallery that is used in the theme panel is now less cluttered and without the unused options
misc: we cleaned the theme panel and the code is more organized now
misc: all the blocks now show a notice to admins on the frontend when there are missing settings that are required.
misc: the main theme loader is smoother now and has small design improvements
misc: we changed the way templates detect the Visual Composer plugin. The detection method is based on VC_ROW and it only triggers when VC_ROW is found in the content. This allows one to use shortcodes in the default templates that have sidebar + title.
misc: added font settings for post lists
misc: drop caps font settings issue fix
misc: all the advertising blocks now support an ad title
misc: various google webmaster structured data issues have been fixed
misc: better support for IE8
fix: category dropdown list with long category titles now works as expected
The list of modified files

• This reply was modified 9 years by simchris.

The “views” counter is a simple “hit counter” and has no relationship to Google Analytics.

You should use server side stats package to see “true reporting” of your visitors data.

Wow!
That was an awesome solution!! That would be a nice “option” to add to the “panel” for that plugin, for those who don’t need the “cache busting” query strings. 🙂

Hi,
just as general rule you should start moving on from “inline styles” and move to CSS classes.

e.g.,
<TABLE width="100%">
to
<TABLE class="mytable100w">

Many browsers are going to not work well with inline styles any more, and your site will fail “AMP” validation with Google’s new protocol.

Just a thought, sorry to intrude.

Ah. I minified mine to 487kb, and then when loaded via gzip/deflate on our server it’s much smaller, about 57kb. So, you can do quite a bit of trickery there 🙂

FYI, v 3.1 with the TD composer is wicked faster. You can read my long winded optimization thread on some of my tweaks after finally moving from 1.7 to 3.1, skipping the 2x gen. Very happy with 3.1 so far. 🙂

Also…
as noted in couple of my optimization threads the only way to remove ‘render blocking’ resources for mobile is to actually move the style.css to footer, de-enqueue it from header, and then manually insert the critical CSS in the header.php file manually (use a critical css generator to do this task). This is how I do it.

That is the broad stroke, but something you can explore on your own time. 🙂

You’re welcome ! 🙂

Team effort with this stuff.

Those only impact the post template.

There is now a separate “meta” data option in the templates panel. Look at the templates panels to find that; it’s not in the “post” panel.

Note, also FontAwesome changed their icons over the past several versions; but also note that TagDiv is using a “trimmed” version of FA as default font; it’s not the full FA font, since most people on a “magazine/news” portal don’t use all of the extraneous stuff.

Simple (sorta) fix is to change the function/style call for the TagDiv font to instead load the full FA fontset, if desired.

Advanced users can do this also, by downloading the full FA fontset, and/or going to fontello.com and build the set you need just for your needs.

In theory you could go to Fontello, build custom font with same name as the TD custom font and just replace it, but this is still on my personal ‘to do’ list, actually. I did this for our business site, but we have a very different in-house theme used there which is more B-2-B than TD theme.

Just food for thought on the topic 🙂

Be sure to ‘export’ your settings from the theme panel for safe keeping, as well as dbase backup, for safety.

In the ‘all files’ download in /plugins/, usually.

Ironically, I just woke up ! First cup of coffee in hand, checking email and server backups. 🙂

For your question:
You may wish to review the WordPress ‘codex’ documentation to learn how WordPress works; the theme has nothing to do with your RSS feeds.

See: https://codex.wordpress.org/WordPress_Feeds

Lots of great info in the codex to review if new to WordPress; stuff you’ll want to know!

But the short answer is that adding /feed/ to end of your sitename, category name, author index name, all creates automatic rss feed.

yoursite.000/feed/
yoursite.000/category/books/feed/

etc.

Welcome to WordPress ! 🙂

Yes 🙂

See the documentation for NEWSMAG:

https://forum.tagdiv.com/newsmag-main-menu/

Welcome I’ve been using the theme since v1.0 (switched from Newspaper) and I love it 🙂

Some people like child themes. Some “frameworks” use them as the framework doesn’t often break the CSS, and so easy to make sub-designs of main design — idea being you can update main theme and child theme changes are left alone. In practice, however with all the WP changes, security changes, etc., child themes end up changing every few major theme update –totally defeats the purpose. So, I avoid them like the plague.

You don’t have to use it; so my rule of thumb for most clients is “if you don’t know why you have a child theme option, don’t use it …” 🙂

I find its safer to make changes to the “main” theme, then keep track of those changes with each major update.

Note if you’re using the speed booster framework plugin, that might be issue; I don’t anymore.

Also note “some” plugins will add the query from their own hook into the enqueue, which can over-ride that function if loaded “later.” I ran into this with the WP YouTube Lyte plugin that snuck in the remove query thing at tail end of functions from itself (easy to hack the plugin to remove that; or de-enqueue the js, then manually add to the footer… )

Helps if you explore in the WordPress docs what some of this stuff does … note the numbers there: (10,2) ? You might need to adjust that ’10’ to “when” your function loads in relation to everything else.

Should also be self evident won’t work in child theme which is dumb CSS redirect to begin with.

$priority
(int) (Optional) Used to specify the order in which the functions associated with a particular action are executed. Lower numbers correspond with earlier execution, and functions with the same priority are executed in the order in which they were added to the action.
Default value: 10

So, in some cases depending on what other shenanigans you have going on, you might have to change the ’10’ to something like ’99’ — to load after everything else and thus actually affect the elements.

e.g.,

function project_dequeue_unnecessary_scripts() {
wp_dequeue_script( 'comment-reply' );
wp_deregister_script( 'comment-reply' );
}
add_action( 'wp_print_scripts', 'project_dequeue_unnecessary_scripts',100 );

So, play with that 🙂

ref:
https://developer.wordpress.org/reference/functions/add_filter/

• This reply was modified 9 years by simchris.