There are some “sitemap” plugins out there which can build a timeline list of stories, although that might be 100 pages for some sites, and not practical.

Technically might be easier to simply use the built in hooks to generate the equivalent of the normal WP ‘archives’ widget for showing news by date….

maybe build a “page” and use visual composer, and insert the “archives” widget which would be a list of all your indexes by year, month ?

in any case I have seen some “sitemap” plugins that do what you want, so maybe look in the plugin repository for those as first step if you don’t know how to write the loop/query code on page template yourself.

There is no built-in function in WordPress to do this.

Not really a theme support question, but basic wordpress functionality has no setting to clone sidebars since the sidebar is one thing, and the widgets setup and “assigned” to a sidebar are two totally different things.

You can clone widgets using something like this, to make it easier to copy settings from one sidebar to a new one:
https://wordpress.org/plugins/oomph-clone-widgets/

There might be a plugin out there to “Clone” a sidebar, but I’ve not seen one.

• This reply was modified 11 years by simchris.

Remember link is

yoursite/author/authornickname

not

yoursite/authornickname

Do you have an example link on a post which when clicked leads to 404 ?

Since this comes up a lot, I thought I’d list some of the plugins I use as standard fare on all our sites:

1) Thumbnail Upscale — this allows you to over-ride the stupid WordPress bult-in function to “disable” your servers natural capability with ImageMagik of “enlarging” your images to fit featured blocks/sliders.

2) Auto Post Thumbnail PRO — paid plugin which allows us to have some of our network content automatically pull from “first image in post” even if from our main hub, and make it the featured image. Awesome if converting to theme from OLD theme which used the TimThumb plugin.

3) WP-Optimize — awesome for regular optimization of dbase to clean house, on spam comments not deleted, trashed posts, and normal database clean up.

4) YOAST WordPress SEO — while we used to have an inhouse plugin for this, Yoast has done great job of putting it all together for managing meta data on global and per-post basis, setting up SEO for home page, and also OG tags for social media.

5) Awesome Weather Widget — we use this on our “state” and local news portals to add a nice local weather box to home page.

6) Limit Login Attempts — this should be built-in to WP, frankly. It helps stop people from sitting there and guessing user passwords or using a bot to hit it over and over. With IP blocking and tracking. Essential!!

7) WP External Links — in our case we need to make the majority of outbound links “rel=nofollow” and this does that automatically.

8) Auto-hyperlink URLs — we use this to control auto-linking of URLs in text, since we pull in a lot of content with visible but not anchor linked URLs in news text from our main hub. This makes all the links live, but also makes them rel=nofollow and open in blank/new window. Can also add external link icon if desired.

9) Simple Local Avatars — already noted in my optimization notes; this awesome little plugin allows you to load/cache GRAVATARS locally, as well as use local images for author pix, which will work on sidebar author blocks, author page, and in author box bottom of posts as it hooks into the main “author image” gravatar hooks; so anything which can read the normal WP gravatar image will work with this.

10) *lazy loading disqus” (not actual plugin name…) — we’re testing a recently launched plugin which uses Disqus API but loads element async and deferred and optimized to load after content and not slow down page. More later 🙂

Hope that helps somebody!!

Chris

Sorry… yes!! I meant to say “Thumbnail Upscale” plugin. Not enough sleep on Sunday 🙂

(doh!!!)

I think you can actually “turn on” support for VC on “posts” from the often overlooked (I know I ignore it), Visual Composer “settings” tab in the main theme admin (!).

Need to use images “larger” than that size, or use the “enlarge thumbnails” plugin, since WP cannot enlarge images by default to “fit spaces.”

I use the “enlarge thumbnails” plugin; and really all themes should probably “suggest” this since WordPress has chosen to disable this commonly needed function (stupidly).

I don’t know what causes that error, not seen it before myself.

Are you talking about theme activation, or entering the purchase verification code.

Theme activation is done in appearance panel, as you know.

Entering activation code removes the nag screen to confirm you bought the theme.

I think it will keep working — it just will bug you every time you load the admin.

I might suspect a caching issue there someplace.

TagDiv support closed weekends; they will be back Monday.

I am not using the sticky sidebar on home page, only on posts, so no idea on this one 🙂

The setting does note that it only works with specific content blocks, so you might want to double check that?

I think you can just edit the header file and put the block of text where the ad normally goes.

Edit the template for the layout “style” you want to use.

Okay. Looks like you didn’t do things correctly in your htaccess file then, if that is entire file. Missing the permalinks code from your WordPress setup and duplicate elements.

As to the new “download optimized…”
Dunno. That is something entirely new. Probably similar to what GTmetrix does.

You can certainly try them, then revert back if they don’t work. It’s your website.

The number of items on each index is controlled by WordPress under the settings > reading > number of posts per page.

Or, you could possibly create a custom loop on the template for the author page.

https://codex.wordpress.org/Settings_Reading_Screen

Welcome to WordPress. WP doesn’t support “enlarging of images.” They (Automattic) turn OFF the built in function of the ImageMagick module on server for their stupid philosophy that enlarged images look fuzzy. Hence need to use a plugin to allow images to be larger than the size you upload.

So, not a theme issue. But still super annoying. Hence need for a plugin to “unlock” the featured to make thumbs larger to “crop and fit” things like sliders/blocks.

Obviously you have to regenerate your thumbnails to fit the sizes used by the theme if they don’t exist.

🙂

Your site sticky sidebar works for me; when I scroll down, the bottom items stay stuck and when I scroll back up the top items stay stuck. So, seems to be working just fine.

It sticks the “bottom” of sidebar to be sticky when scrolling down, not the top.

It sticks the “top” of the sidebar to be sticky when scrolling up, not the bottom.

Perhaps I don’t get what you’re trying to say. Sorry.

TagDiv support will be back Monday 🙂

Did you save your older version? You should be saving your downloads from ThemeForest, and also making BACKUPS of your site BEFORE you update it, so you can GO BACK to prior version in case there is issue with plugin, theme, WordPress version, etc.

TagDiv is closed weekends, so you should hear back from them on Monday if you sent email request for v1.6.

Again — good idea to keep backups of all your theme and plugin installers on your local hard drive in a “work” folder for each website. This allows you to “go back” at any time you need to, such as in this case.

Okay. And ?

The htaccess file does nothing whatsoever related to “render blocking” CSS/JS; that is not its purpose.

The htaccess file gives directives for the server, running “above” the site for caching, expiration, redirects, etc.

Mod_Pagespeed settings won’t do anything unless your server has that.

Obviously your permalink structure for WordPress should be in your file (missing from your example).

You don’t need two sets of expire headers (!).

All of the above is to help with optimization of page loading — nothing to do with HOW the content loads on the page (aside from mod_pagespeed of course).

The only way to optimize for the CSS/JS render blocking is to build custom site without all the bells and whistles and custom load content in groups; and you can optimize some of that with the tagdiv speed booster plugin.

Only one continuous sidebar can “stick” not two separate sidebars.

You can create different “pages” and then choose which “page” you want active as your home page. So this allows you to have a “live” page then experiment with other layouts using preview, then if you get a new preferred layout just switch on the new page.

Probably need to edit the single post template you’re using and move that section from bottom of template to top and experiment with that. For circle image you’d need to add CSS to make a round mask.

If you don’t know how to do any of that you might have to hire a developer.

Tagdiv support back on Monday might give more specific answer.

This is a recent development this year with insights; kind of annoying; and why you get higher score with GTmetrix than insights score. With “responsive” design, images are often resized vs serving an entirely new image as traditionally it was actually faster since the server caches images, especially high request images. However, now the insights score is based on a “mobile user loading the content” as part of the “mobile first” movement, and so it seems there is going to need to be some kind of element added to all themes which load images much like the ad banners used to load the past few years prior to Google adding responsive ad units …

basically…
if viewport large = load big image
if viewport small = load thumbnail

Dumb thing is that in many cases, the larger image being loaded on mobile, e.g., iPad actually works better as a “resized” image, since it effectively makes a 640×400 96dpi image into a 340×200 200dpi image for retina displays by having larger pixel density when the large size is reduced on screen — hence why the images look so good on retina mobile devices without having to reload a “retina image…”

So….. stupidly, they are looking at “bandwidth” not “quality”…

Themes are basically going to have to be re-engineered to “by default” always make something like a 50% thumbnail and serve that on mobile devices.

Even stupider requirement because not all mobile devices have same viewport, and so it’s not practical for every page to constantly load 10 different size “featured images” based on viewport — this is what responsive design partially solved.

Upshot — you can live with suffering the warning for now — everybody is getting this — everywhere.

Not sure how TagDiv will address this, or if some super clever person comes up with plugin.

In our case we’re running mod_pagespeed and just updated last Friday (week ago), in hopes it would have solution for this as part of the “resize images” function (well, subset of “rewrite images”), and that isn’t even doing that with Google’s own technology!

(argh)….

Sorry for editorial. I started trying to deal with this April 1, and was super annoyed by the “actuality” of the issue.

Basically a featured image now has to be treated as an “ad module” and load a different size main image based on desktop v mobile. Show me any themes doing that right now. Nope. Annoying.

Hope that helped in some way …. main thing is to ensure the main images you’re uploading are as compressed as possible. I’ve been trying to make sure our larger images are no more than 25kb vs 32kb. If you have an image with 120kb that can be removed, it might be too big to start with.

No simple answer.

I think you can request an invoice from Envato/ThemeForest via your account.

Not really a theme problem. No theme developer can force Google to do anything with your content. They scrape the content based on “how their bot” sees the page. Your OG tag settings impact “hinting” for them, but they don’t always follow that.

So you have to build your page so that it works with Google’s bot; some sites will have this problem depending no how *you* setup your mega menu and post content, and featured image. You need to experiment with the menu layout to see what works with Google’s bot, unfortunately.

I think you would need to change the setting in the
theme panel under post settings > posts > show author name ?

I think the theme requires the visual editor included with the theme. I don’t think you can use the theme with two different content builders; but wait for official tagdiv support on Monday.

Disqus writes the comment count to the normal WordPress comment function. So any plugin that calls that properly will work. This is why the comment count works correctly on posts and blocks (but not the author page, oddly).

The theme doesn’t manage Disqus in any way. So basically it just reads the WP data field for comment count, a normal WP function. So, you have to wait for Disqus and WP to sync. Theme does not manage that in any way.

You can often find help on this topic on the support forum for Disqus.

We go through this also, but don’t obsess over it.