Also note server “response” time is not the same as “page load time…” — meaning the time it takes the server to respond to first query for the page content.

Our sites with dedicated server with 32GB RAM and Quad Xeons is typically 0.31 seconds “server response time” on average and Google tells us THAT is still slow. They ideally want 0.2 sec or faster, if you can believe that.

But that should be your target if you have dedicated server running Linux variant. Definitely talk to your hosting provider — I can also recommend a third party support firm here in the U.S. ($150/month) to help manage the more arcane stuff that many hosting/colocation folks no longer help with.

but we’ve not done any special optimizations as I’m not a slave to Google’s nutty “best in the world” when they can’t even manage half their own web stuff properly anymore (seriously, don’t get me started … on the https site name change fiasco, or using Google paid CSE with sitesearch … etc.)

Not sure any of that helps — only anecdotal in case you needed some feedback on a good target speed for dedicated server with 32GB RAM and multicore CPUs.

Another option which helps, that folks often miss, is the switch your server is actually connected to their network with — most colocation and managed server co’s default to a 10/100 switch/port — when you really want a 10/100/1000 switch/port to have your server connect to. I’d look into that first, but also make sure you have your hosting company “audit” the server response time.

Did you regenerate your thumbnails using the ‘force regenerate’ or the “regenerate thumbnails” plugin.

Did you also first turn “on” the sizes for the modules for thumbnails ?

Yeah… some funky bug in the latest version of WordPress for both the archives and the category widget … team effort — there was fix posted last week on this …. don’t have link handy …

tagdiv provided fix for categories and I added fix for archives …

oh wait, I can just look at my custom css (duH!)….

and the magic secret sauce is:

.widget_categories label {
display: none;
}
.widget_archive label {
display: none;
}

the duplicate title appears in all themes — not just tagdiv, as I noticed the same issue on couple of my older sites too. Annoying they didn’t catch that in WP 4.2.x.

And of course the super patient awesome tagdiv support team will follow up during normal business hours …

Nope. Not author of the theme. You can, of course simply create anything in a text widget on the sidebar using CSS and by inserting your photo.

Not to be sarcastic but perhaps learn to look at the “page source” in HTML to see how things are actually done and rendered on the page, as in your example …

from the page source:

<div class="block-title"><span>About me</span></div> <div class="textwidget"><div style="text-align: center;"><img src="http://demo.tagdiv.com/newspaper_classic_blog/wp-content/uploads/2014/07/meee1.jpg" />
<h2>John Doe</h2>
I'm John and recently I've moved to Rochester, which isn't that far away, I do many things like writing articles and playing football.
</div></div>

• This reply was modified 11 years by simchris.

Try turning off all plugins except visual composer … and in normal post, in the TEXT editor, NOT the visual editor, put in the proper format code.

One presumes the link you’re inserting in wdbm=”” actually plays in the web browser if you just load the file by itself ?

Maybe try adding the preload variable?

Does the function work on another theme other than this one?

You might try the WordPress forum also.

I don’t see anything on the docs page saying you need [/video] ?

———
Maybe somebody else with your issue might pitch in on this one !

heh… the trick is putting in the “ID” for the account and not the full URL, and for G+ remembering the “+”

Well, not all plugins or WordPress function when working locally. Nature of the beast.

Works on our sites no issue on “live” sites.

Should follow this format
https://codex.wordpress.org/Video_Shortcode

Try uploading it by itself via FTP; delete any old versions in your plugins folder.

Once you activate it on the plugins panel in your WP install,
simply go to your appearance > widgets
then put the widget into your applicable sidebar

then in the widget settings put in your social media accounts per the instructions there.

Works 🙂

I don’t use Jetpack — as everything related to that is hosted on the automattic servers and you don’t really have any control over that within the theme beyond adjusting things in their control panel —

unless I’m wrong on that 🙂

As with all WordPress sites, normal practice is to make a new template and name it after the category number so that the template loads for that one category to over-ride the default category template.

See the WP docs for more info:

https://codex.wordpress.org/Category_Templates

🙂
hope that helped vs annoyed!

Yep. The only fix is to not use theme panel “over rides” for default colors, and make those changes directly to the style.css file.

Otherwise what is basically happening is
a) main CSS loads
b) CSS over-rides load

as you might expect in many situations due to the complexity of certain pages; especially with complex home page, and complex mega-menu — there is a couple msecs delay in there.

Also avoid using child theme on top of that since all child themes are basically redirects from one theme to another — which Google doesn’t recommend — but WordPress has made this their standard practice. Best to just edit the main theme, since with major theme updates, the child theme needs changes too and defeats purposes of using child theme to avoid not having to re-apply changes.

Much like WooCommerce — changes are done to functions.php — and one has to reapply them each time there is update.

Anyway — that’s been my experience. 🙂

Well…. I guess it only matters if you’re building your own theme or buying that other person’s theme. TagDiv supports it in any case as does the Yoast plugin, so not really impactful ’round these parts 🙂

Did you try

<!--nextpage-->

I think that only works on posts and not “pages” … as WP is normally setup to use pages for things like “about us” or “contact us” and long pages/articles are done as “posts” where the next page tag would be used.

For pages, you could presumably just make a new page and link to it at bottom of the first page — there might be plugin to do this — but I don’t think WordPress supports page breaks except in posts.

yes 🙂

Not really a theme question, but more on how to use basic WordPress functions.

Often you can learn to use WordPress by doing Google searches for those who have already broken the trail for you …

e.g. google – “make wordpress category private”…

example:
http://johnlaudun.org/20110113-making-a-wordpress-category-private/

http://codecanyon.net/item/privatecontent-multilevel-content-plugin/1467885

It’s included in the plugins folder inside the “all files” theme download from themeforest.

Try adding the memory line to your wp-config.php file, and bump it up to 96MB from default 40MB.

See:
https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

Well that’s dumb.

I suppose since it’s already offering in numerous plugins, and also found in YOAST SEO, and can easily be inserted into a header.php template, not a terrible thing.

But I find that somewhat hard to believe, or even justifiable — that’s like saying you can’t insert a link to your Piwik stats into a theme, or you can’t have a box to put in your AdSense codes … makes zero sense whatsoever. It’s just a box that prints the “block of text” into the header file.

Now if the theme developer is piggybacking their own GA code in the theme, THAT would be bad; but providing customers / users / admins a way to put the GA code into the theme — that’s a convenience factor for those buying themes, many of whom are newbies to WP (obviously if you read ANY support forum for themes).

I’m raising the stupid flag on this one — I can’t imagine WHAT the security issue would be with this. It’s simply a convenience — just like adding a copyright notice to footer, or adding in author meta for post authors … sheesh (!).

@davidewebcenter

and again — this issue only impacts *some* websites. Tens of thousands of websites are running themes using the Visual Composer framework. A small percentage have CPU overload issues, as we did.

If your server setup doesn’t have this issue – it’s a non-issue for you. If your server has this issue it will happen with *any* WordPress theme running Visual Composer and you’ll know right away, not months later.

The “shim” plugin provides “some” of the main elements commonly used for homepage for modules; it does not provide for ALL the VC hooks/blocks/elements. So, it’s basically a solution for those few having the CPU issue — it’s not intended to replace Visual Composer.

If you’re running VC now and not getting warnings from your web host already, then you will likely not have to even deal with this issue at all.

It’s a responsive theme — you can’t turn off responsive features technically.

You could edit out the @media sections of the style.css to hack the theme, presumably.

This has been covered in the forum before so you might search for that; or wait for official tagdiv reply.

Well, I think this is covered in the them docs, but once you install the theme, you need to use the “regenerate thumbnails” plugin (not included) — this sets all the image thumbnail sizes for the theme, which may be different sizes than from your prior theme.

see
https://wordpress.org/plugins/regenerate-thumbnails/

🙂

edit: I guess they now recommend the “force regenerate” plugin; but either way does same thing.

edit 2: and I guess they got rid of the “why don’t my images fit” topic that was once in the docs. Guess they are rewriting everything to make it better and dumped some of the oooold stuff.

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

Go to appearance > widgets
use the social icon widget and place in the top menu area section

Probably jetpack — which sucks in my opinion.
Best to serve the images from your own site vs loading off jetpack’s cdn.

(jetpack owned by automattic which makes wordpress … likely the wp.com)