Search Results for 'update'

Can we get an update on this tutorial and application for Newsmag theme? Thanks.

Hi Chris
I tried to add the filter, but doesn’t seem to make a difference.
The odd thing is, that it only happened after the latest update.

Weird. It should “not” be a theme, issue but I just reproduced this by pasting the URL with open new window code into a post on my ga-ga.com site running the theme, then on my californianewswire.com site running Woo Canvas (shortly to be running Newsmag once the new update drops next Monday-ish).

The link works on my CANW site but NOT the Ga-Ga site.

So, you are indeed correct sir!

• This reply was modified 11 years by simchris.

Thank you, I think I am on an older version (4.2) because I don’t have that option on post page.

Where do I get updates?

WHEW!!! Glad you folk got it sorted. I always do the updates via FTP now… it always works, while the WP panel installer is sometimes hit/miss.

I really need to restart my web dev blog ….. (!)

(I know, folks keep asking …. been super busy ….)

• This reply was modified 11 years by simchris.

Have you tried running the theme with *only* the Visual Composer plugin activated and all other plugins off? Then checking to see what errors you might be getting? Then if none, slowly turn on each other plugin to see what happens? This is best way to debug the problem, and figure out WHAT is causing overload.

I’ve had no such problems with the theme over here, beyond the normal hiccup doing updates (see my sticky post on migrating theme).

Hi Lucian,

I would like to use your code from above to insert next to the event date “. $EM_Event->output(‘#_EVENTDATES’)” the event location #_LOCATIONTOWN in block if post is an event (if ( ‘event’ == get_post_type($this->post->ID) ).

Could you please give me any advice where to put it? Thanks very much!

if ( 'event' == get_post_type($this->post->ID) ) {
$EM_Event = em_get_event($this->post->ID, 'post_id');

$buffy .= '<time itemprop="dateCreated" class="entry-date updated' . $visibility_class . '" datetime="' . date(DATE_W3C, $td_article_date_unix) . '" >' . $EM_Event->output('#_EVENTDATES') . '</time>';
$buffy .= '<meta itemprop="interactionCount" content="UserComments:' . get_comments_number($this->post->ID) . '"/>';
} else {
$buffy .= '<time itemprop="dateCreated" class="entry-date updated' . $visibility_class . '" datetime="' . date(DATE_W3C, $td_article_date_unix) . '" >' . get_the_time(get_option('date_format'), $this->post->ID) . '</time>';
$buffy .= '<meta itemprop="interactionCount" content="UserComments:' . get_comments_number($this->post->ID) . '"/>';
}

Update: The error occurs when I add a custom font to the post content. It then doesn’t load the fonts in the menu. Please fix this error as I want to use both fonts across my posts. The theme I am using is Newspaper.

I personally would rather not have the SEO stuff tied to the theme, as I’ve changed themes all over the place the past 10 years using WordPress, and there is no guarantee a theme will be updated for new SEO tech/requirements. With YOAST SEO, they now have a business model to sell premium versions and also sell the Google News plugin (which I use with 20 site license). I can swap themes if need be, without losing settings or foobar the sitemap.

Adding additional functions might be nice for the native system, but as long as there is an option to disable it all, I’d be fine with that.

The old Yoast was merely a collection of things we used to do with functions.php frankly, and custom headers. But now, it’s evolved quite well and works well “most of the time.” But it’s kind of like saying “why not build in Visual Composer features and stop using that plugin” … well, a whole separate dev team work on that, and they make money on each license, so it continues to evolve.

I’ve used themes in past that tried to do it all, and they end up being neglected, one month delay to fix something simple, etc.

SO, for me, I’d rather let Radu and folk make sure the theme functions with WordPress properly, supports a wide variety of WP standards, and then leave the “extensions” to others. Just my thought.

I used to build my own themes, and it’s a pain in the arse (hence how I ended up here).

But as many have said, this a forum, so discussion and exchange of ideas is all good. 🙂

(and how about browser and forum designers turning off freakin’ auto correct … changing build to built… it’s not possible for me to mis-type a b next to a t on the keyboard! Argh!)

• This reply was modified 11 years by simchris.

Chris,
I think going forward the better policy would be for Tagdiv to develop their own meta data solutions to use with their themes.

In effect it would be another area to minimise using a plug-in, we wouldn’t be at the mercy of plug-in updates that may be incompatible with the theme, and would also remove unwanted ads.
Admittedly Yoast solution for meta using basic SEO tools such as Meta data etc is a good one. However, this could be done natively and built in.

In this case there is a conflict between theme and plug-in and we have tested it thoroughly – including tweaking the various settings.

Well, yes, YOAST SEO has had some on/off issues, including a security issue. Which is why I normally don’t jump on the “update” until reviewing the changelog, and then waiting for a dot revision. There was one period where they were adding all the Google analytics stuff and that caused issues, and they did five revisions in 2 days (!). But it never hampered publishing.

The issue we *did* have with publishing was the “remove stop words” function, causing some links to not work right. But we could still publish stuff.

Also had issue with trying to hide the /category/ in front of /category/catname/ to have one less path – that didn’t work well as we use a lot of sub-cats for easier navigation (e.g., book reviews, fiction, and poetry might all be under “reads” to separate from movies/tv and music).

Still, some YOAST functions do require you to actually go through each screen and tweak.

ALSO: when updating the plugin, sometimes the settings get wonked, and your sitemap suddenly doesn’t work (!). I had that happen recently.

So…. usually if I update Yoast WordPress SEO, I go through the settings and resave just to make sure the dbase entries are correct/updated for the plugin.

YOU MIGHT TRY THAT… just go through and resave settings, double check social media stuff, resave sitemap stuff (I sometimes change from 1000 per page to 999 per page to “force” refresh that). Stupid stuff like that. Couldn’t hurt 🙂

But generally (sorry to keep using that word so often) … there is no conflict between the basic functions of WordPress SEO and the theme. And none of the problems were theme related, but due to plugin problems, which might be addressed on the support page for the plugin also.

As of the latest update I still have the custom CSS for this issue and it does not seem to work without it still. Am I doing something wrong and should it be resolved now?

Please advise. Thank you.

Hi Lucian,

Yes, I noticed that today – maybe it had to have some time to update or make the information available but now we know for future.

Thanks and Happy New Year!

Best,
Stephanie