Search Results for 'other ads'

Hey Alin! Thanks, now that I’ve found the right file and I’ve added the codes as outlined above, I’m running into other issues. I followed the steps to add the code based on the field names I made (I created three hide_inline_ads, hide_top_ad and hide_bottom_ad) so it would have been easier for me to identify which is which. I placed in the code like you can see in this image:

But for some reason now when I check the posts themselves on the frontend nothing shows up (I’m currently testing this on my staging site). Any ideas what’s wrong in the code?

Here’s how the front end looks when you visit a post:

And this is the ACF fields added:

Hi

I’ve checked your site and and the image loads fine: http://screencast.com/t/5a68WVDrVor1 Please provide more details if you have another issue.

Thanks!

FYI,
Yoast SEO has had numerous bugs, check the changelog sometime to see how many bugs they have had. My contention was simply that using Yoast SEO as a “comparator” to anything else related to bugs, is not a good metric.

So, you don’t need to debunk my statement, as it’s well known. Yoast has had numerous bugs which break the site, break other plugins, and major security flaws (where they finally hired a security firm to check them).

H1 is useful on home page; H2 also useful for topical elements such as section heads, but not so much for story heads ad they are ephemeral; meaning, they change daily, so they are not sticky and therefore not relevant to long-term, long-tail SERPS placement.

The “home page” is typically not “critical” for SEO, as you want your “post” to rank higher than your home page for a specific story, including the title and excerpt, so causing them to fight each other is un-wise.

I only speak as an SEO expert having been building websites since March 1995, and widely interviewed on SEO topics by Entrepreneur, PCWorld, Monster.com, etc. And we had a highly successful SEO business for 10 years with over 2 million #1 positions in Google and Yahoo for our clients. And, oh yeah, I have two Harvey Measurement Awards for “most responsive advertising,” and a design award from Apple Computer, Inc. for marketing campaigns for Apple retail products in California, and built Oprah Winfrey’s ecom solution for her “Begin with Love” video series; but what the hell do I know?

TagDiv does provide the tools to add H1 tags to any home page and it should be up to any theme user / site developer to manage their own SEO practices. It could be needlessly confusing to have a built in H1 element on the home page template as there is no default home page template technically, since the presumption is you would be “rolling your own.” So this would require yet another set of code to check if home page and insert something in header, have toggles for on/off, and remove code for those doing their own H1 placement as we have done with WP for 10 years now. Frankly if folks can’t be aware of SEO for their own site, they are generally not that worried about it — and these are often same folk not reading the WP codex to learn how to set permalinks, etc.

One might also argue it’s useful to inspect the demo of a theme before buying it, then using it, then posting numerous times how bad it is or buggy, vs. requesting possible changes politely?

These are just my thoughts, having used Newspaper for almost 2 years now, and have great traffic, great SEO, and placement in Google News, Bing News, and syndicated worldwide through major information systems like LexisNexis, etc.

But that’s just me. Your mileage, as in all things, will vary.

• This reply was modified 11 years by simchris.

Thanks Lucian, I commented that code from td_config as suggested and it seems to works fine (site didn’t crash). My concern is always it loads another font and then my configured typekits.

The site is here.

regards,
Felipe Z.

WordPress does not support alt tags by default, not a theme issue.

I define alt tags for all of my media files. Newspaper is not using them in all of the thumbnails, which leads to a high percentage of empty alt tags. This IS a theme issue.

H1 tags can easily be added to home page to setup a desired blurb about your site…

True but H1 should not be missing in the first place. Many Newspaper users are unaware that their home pages and archive pages are getting penalized by the theme’s missing H1 and H2 tags.

Yoast has had more SEO problems than TagDiv…

The recent TagDiv page title issue was worst than anything I’ve experienced with Yoast.

The best SEO is still ORIGINAL content, posts between 800-1200 words are the “Sweet Spot” — avoid short posts and copycat of other site content and images; avoid posts with a YouTube video and one paragraph about it, etc.

The best SEO is achieved with content AND with leveraging known signals. By ignoring proper use of H1, H2 and other non-content related on-page SEO, you unnecessarily penalize your own content.

Also, I see one-paragraph posts ranking all the time.

Newspaper is an awesome theme. If I didn’t believe this, I would have just moved on already. These SEO issues need to be fixed, not defended.

Yeah these issues should without a doubt be the number one priority for tagDiv.

Also even though issues have been brought up by users many times, and in many threads, the issues seems to be dumbed down and pushed to the side as if the problem isn´t very big.

A thorough answer would be greatly appreciated regarding these issues and what the developers expect to do about it. Also love the theme and would like to continue using it, but if it comes with a loss of visitors compared to the previous version 4 of the theme the choice to use another theme isn´t very hard 🙁 (very sad face)

Good points on 1-3. I second those.

#8 – Super Socializer is a great plugin for that and more. Pretty stable with tagDiv themes and doesn’t drag as much as others. Free, available in plugin repo.

For #5 there is a plugin for that called Theia Post Slider. If you’ve ever seen slider on BleacherReport.com – this is exactly like it. Good plugin. Haven’t used it with Newspaper v6+ yet. And for #4, it’s really kind of unnecessary since it only trumps up pageviews in a way that doesn’t count for ads and such. Ads need a page refresh to count a new view. But then again, Theia Post Slider does include some functionality for this and for ads, so you might want to check it out. It’s on Code Canyon. Good price, and support.

Hi guys,

This keeps on being removed every time the theme is updated.
It’s really frustrating.

Is there a way of putting it in the theme somewhere to put ads under the actually article?
It seems like such a stock standard thing on all the news wordless news/magazine themes.

I really like the newsmag theme otherwise but this seems like something that needs to be addressed with a permanent fix.

Hi

I’ve cheeked your site and the image loads fine in posts as you can see here: http://screencast.com/t/JMr32RXTJgg http://screencast.com/t/vhTM5YucPwM6 Try to clear the cache and test the site again.
Let me Know how it’s going and if you have another issues please provide ore details.

Thanks!

HI folks … as I’m about to be enmeshed in a highly complex project for my own company, I won’t have *any* time to post “pay it forward” help around here anymore, but I thought I’d share one last thing for now — which I’d promised to do, and I just did in another post on this topic …

this is “broad strokes” on how to optimize the font loading for using Google fonts, such as OpenSans for your site; to not load the remote style sheet from Google and solve one of the issues from optimization testing related to Google fonts. This might even gain you a point in some cases!

———– SNIP————-

The theme does not load fonts via functions.php; but from the MAIN functions file used by the theme inside the /includes folder as I noted.

The following would be how we do it, in broad strokes — with idea of using OpenSans, removing roboto, and loading the CSS locally for OpenSans vs remotely.

Anybody planning to hack the theme in *any* way should explore the files in there to see what is going on with the theme.

So, to wit
theme/includes/td_wp_booster_functions.php

see around line 1318 – 1340

helps to use a proper text editor (I used “TextPad” on Windows, BBEdit on Mac).

I have not done this in awhile, but as I’m no longer going to be around here to help out, needing to move onto other things I’ll try to provide a starter point for you.

I believe I removed the whole Google fonts section; or perhaps only left in the first section as it caused error to remove it all.

————-

Next you need to search/replace any instance of Roboto from your style.css ; change the default fonts to OpenSans as you won’t be using the control panel to select it anymore.

————

‘capture’ the CSS from Google; presumably those of you who are new to HTML, webdev, etc., likely don’t understand what is going on with CSS (cascading style sheet) and how fonts are loaded.

So, basically when you “request” the fonts from Google using their API, you’re not loading the fonts, you’re loading a style sheet on their server, which in turn loads the fonts — a redirect of sorts. And this does show up as “something to fix” when doing optimization tests.

So, an old trick most of learned in the olden days of hand coding our websites from scratch is that you can put that API link into a browser window, or email it to yourself as a link also works …

Put another way if you were to go to the Google font repository, or look at the theme code, you end up with their API call, which looks something like this:

://fonts.googleapis.com/css?family=Open+Sans:300,400,600,700&subset=latin,cyrillic-ext,greek-ext,greek,vietnamese,latin-ext,cyrillic

Now if you know what you’re doing, again, you can put that URL into a browser window and it will spit out the actual “what is being loaded from that URL” … which actually looks like this:

@font-face {
  font-family: 'Open Sans';
  font-style: normal;
  font-weight: 300;
  src: local('Open Sans Light'), local('OpenSans-Light'), url(http://fonts.gstatic.com/s/opensans/v13/DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff) format('woff');
}
@font-face {
  font-family: 'Open Sans';
  font-style: normal;
  font-weight: 400;
  src: local('Open Sans'), local('OpenSans'), url(http://fonts.gstatic.com/s/opensans/v13/cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff) format('woff');
}
@font-face {
  font-family: 'Open Sans';
  font-style: normal;
  font-weight: 600;
  src: local('Open Sans Semibold'), local('OpenSans-Semibold'), url(http://fonts.gstatic.com/s/opensans/v13/MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff) format('woff');
}
@font-face {
  font-family: 'Open Sans';
  font-style: normal;
  font-weight: 700;
  src: local('Open Sans Bold'), local('OpenSans-Bold'), url(http://fonts.gstatic.com/s/opensans/v13/k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff) format('woff');
}

that is the actual CSS being loaded .. and you can put this at the bottom of your style.css file to load the fonts from your own style sheet vs loading their style sheet remotely.

So, if you combine the three things
a) search/replace your /theme/style.css to make OpenSans your default font; remove Roboto
b) remove the section in the theme main config file so that it’s NOT loading the remote style sheets
c) put your captured CSS from Google at bottom of YOUR /theme/style.css
d) there may be one instance of roboto somewhere else in the admin code files, but I forget where that is at the moment (sorry)
e) while it should be self-evident — if your site is https; change the http in above to https.

Then you have saved the redirect of the extra style sheet being loaded from Google’s server.

You can modify this procedure to use different fonts, or multiple fonts. Just setup the fonts you want on Google’s font site, get the embed code; then “capture” the actual CSS.

Try it 🙂

• This reply was modified 11 years by simchris.

The theme does not load fonts via functions.php; but from the MAIN functions file used by the theme inside the /includes folder as I noted.

The following would be how we do it, in broad strokes — with idea of using OpenSans, removing roboto, and loading the CSS locally for OpenSans vs remotely.

Anybody planning to hack the theme in *any* way should explore the files in there to see what is going on with the theme.

So, to wit
theme/includes/td_wp_booster_functions.php

see around line 1318 – 1340

helps to use a proper text editor (I used “TextPad” on Windows, BBEdit on Mac).

I have not done this in awhile, but as I’m no longer going to be around here to help out, needing to move onto other things I’ll try to provide a starter point for you.

I believe I removed the whole Google fonts section; or perhaps only left in the first section as it caused error to remove it all.

————-

Next you need to search/replace any instance of Roboto from your style.css ; change the default fonts to OpenSans as you won’t be using the control panel to select it anymore.

————

‘capture’ the CSS from Google; presumably those of you who are new to HTML, webdev, etc., likely don’t understand what is going on with CSS (cascading style sheet) and how fonts are loaded.

So, basically when you “request” the fonts from Google using their API, you’re not loading the fonts, you’re loading a style sheet on their server, which in turn loads the fonts — a redirect of sorts. And this does show up as “something to fix” when doing optimization tests.

So, an old trick most of learned in the olden days of hand coding our websites from scratch is that you can put that API link into a browser window, or email it to yourself as a link also works …

Put another way if you were to go to the Google font repository, or look at the theme code, you end up with their API call, which looks something like this:

://fonts.googleapis.com/css?family=Open+Sans:300,400,600,700&subset=latin,cyrillic-ext,greek-ext,greek,vietnamese,latin-ext,cyrillic

Now if you know what you’re doing, again, you can put that URL into a browser window and it will spit out the actual “what is being loaded from that URL” … which actually looks like this:

@font-face {
font-family: 'Open Sans';
font-style: normal;
font-weight: 300;
src: local('Open Sans Light'), local('OpenSans-Light'), url(http://fonts.gstatic.com/s/opensans/v13/DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff) format('woff');
}
@font-face {
font-family: 'Open Sans';
font-style: normal;
font-weight: 400;
src: local('Open Sans'), local('OpenSans'), url(http://fonts.gstatic.com/s/opensans/v13/cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff) format('woff');
}
@font-face {
font-family: 'Open Sans';
font-style: normal;
font-weight: 600;
src: local('Open Sans Semibold'), local('OpenSans-Semibold'), url(http://fonts.gstatic.com/s/opensans/v13/MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff) format('woff');
}
@font-face {
font-family: 'Open Sans';
font-style: normal;
font-weight: 700;
src: local('Open Sans Bold'), local('OpenSans-Bold'), url(http://fonts.gstatic.com/s/opensans/v13/k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff) format('woff');
}


that is the actual CSS being loaded .. and you can put this at the bottom of your style.css file to load the fonts from your own style sheet vs loading their style sheet remotely.

So, if you combine the three things
a) search/replace your /theme/style.css to make OpenSans your default font; remove Roboto
b) remove the section in the theme main config file so that it’s NOT loading the remote style sheets
c) put your captured CSS from Google at bottom of YOUR /theme/style.css

Then you have saved the redirect of the extra style sheet being loaded from Google’s server.

You can modify this procedure to use different fonts, or multiple fonts. Just setup the fonts you want on Google’s font site, get the embed code; then “capture” the actual CSS.

Try it 🙂

Спасибо за ответ. Про BBpress я понял, поработаю с его шаблонами для внесения нужных изменений.

Про CPT.

Для работы сайта мне необходимо создать собственный Custom Post Type (post) и Custom Taxonomy. Плагин CustomPress я взял для примера, так как он удобен. Также я могу создать CPT вручную, используя WordPress Codex.

На самом деле способ создания CPT не имеет значения, вопрос в другом, как функционал темы правильно подключить к CPT “post”, чтобы использовать все возможности темы по аналогии с Блогом?

После создания CPT, в админке для него нет следующих блоков:

http://prntscr.com/7qrqmk
http://prntscr.com/7qrqxm
http://prntscr.com/7qrr9c

При работе с Visual Composer я не вижу в фильтрах Custom Post Type и Custom Taxonomy, соответственно не могу работать с ними.

http://prntscr.com/7qrt0l

Как их правильно подключить?

—————

Thanks for the answer. About BBpress I understood his work with templates to make the necessary changes.

About CPT.

For the operation of the site I need to create Custom Post Type (post) and Custom Taxonomy. Plugin CustomPress I took as an example, as it is convenient. I can also create CPT manually using the WordPress Codex.

In fact, a way to create CPT does not matter, is another question, the functional threads are properly connected to CPT “post”, to use all the threads similar to the blog?

After creating the CPT, in the admin for him there the following units:

http://prntscr.com/7qrqmk
http://prntscr.com/7qrqxm
http://prntscr.com/7qrr9c

When working with Visual Composer I do not see filters Custom Post Type and Custom Taxonomy, respectively, I can not work with them.

http://prntscr.com/7qrt0l

How to connect them correctly?

• This reply was modified 11 years by extpress.
• This reply was modified 11 years by extpress.