Hi, as you likely know WordPress automatically creates archives for things like “by month” “by day” and “by year” for all your posts.

To create a custom archive, I think you need to create a new “page” then use the template options on right to select a template, then possibly use page builder to set the elements you want on that archive page. Kind of like making custom home page, but custom archive page.

Likely you could look at page source, find the classes for those blocks, then add some custom css to the theme panel to over-ride the size of those specific classes. 🙂

I don’t think so. Most of these modules are setup to show “posts” (articles, news, etc.) as on a normal newspaper or magazine website, and not “pages” which are more often where you would have info such as “about us” or “privacy policy.”

However, some people have created custom modules, and there might be a way to load “pages” vs posts in a module, however most of the modifiers such as ‘by date’ or ‘latest’ don’t apply to pages, as they do with posts, where often things are listed in a numerical order you have to specify in each page you create.

• This reply was modified 11 years by simchris.

Hi, you may find the theme documentation useful, for the mega menu:
https://forum.tagdiv.com/how-to-use-the-megamenu/

For the regular menus:
https://forum.tagdiv.com/menu/

• This reply was modified 11 years by simchris.

I use AddThis to put the social both above/below the post, but some people have also taken the code from the loop-single.php file (or whichever post template you’re using) and cloned it to above the post block.

I think it’s this code in loop-single.php (based on theme v 4.22):
<?php echo $td_mod_single->get_social_sharing();?>

Sorry.
Wait for Lucian or Marius to get in tomorrow.

I think they need to update that code on their docs page you’re referencing, which pulls list of the CSS and JS, which is what you’re looking for.

I don’t work here, just helping people as I’ve been doing webdev since 1994 and using WordPress since it launched in beta.

Hi,
that isn’t a normal function of tags in WordPress, since the tags by default go to the actual tag. Likely you would need to create some custom code, with help of a developer, or perhaps create custom function to redirect tags from the tag page to a search page. Not sure that’s good for SEO, and perhaps not good for “too many queries” to the dbase if you use a lot of tags.

Not something included with theme, and not part of the theme in any way. So, probably you would need to hire a developer to change a core function of WordPress to do that.

Since the tags which appear on the post pages are from an array, pulled from the post meta data, you’d have to either hack the WP core to redirect such links on the post page, or likely easier create custom fields for your new “s-tags” which have a URL associated with the tag, which leads to the search; then “print” your custom fields at bottom of posts, and turn off the theme function to pull the normal tags array.

Perhaps that might help point you in right direction. 🙂

Sure, if you want to pay me to replicate the steps, would be happy to. “My” guide does not include those steps, as I NEVER edit the core code, and I only use compliant WordPress functions to optimize the functions.php file and well known suggestions for htaccess directives, etc.

I never made those instructions you refer to, so I’m going to pass on any help. Sorry to have offered; I likely only added to the confusion. Sorry about that.

I’m sure one of the other contributors here using that “hack” might be able to help. Likely you will want to post the question in that thread, as the hack you’re looking to do has nothing to do with theme support, or my suggestions for PageSpeed improvement.

Sorry, I can’t be any further help on this topic. Perhaps the person who suggested that hack might be able to help – try posting in that thread for help from those of us contributing suggestions for pagespeed improvements. Maybe the person who posted the hack will follow up for you on what he/she did to use that element you’re trying to use.

And again, the tagdiv speedbooster code and plugin has been updated for September, so the July hack may no longer work. But I’ve already said that, so I’ll stop talking now. 🙂

Not all fonts support 300 weight, as 400 is “normal” much like 700 is the normal strong/bold.

Likely you would want to edit the style.css file to specify the font and the weight you want; or over ride classes with the custom css box in theme panel.

For me, I opted to edit my style.css to specify the font to use explicitly and the font weight I wanted.

For Google fonts, you can check their font site to see which fonts actually support the 300 weight, and then you probably would need to call that font weight from either adding the Google css to bottom of your style.css file, or edit the functions or fonts file depending on version of theme being used, to call the 300 weight.

Hope that made sense, or at least points you in a good starting direction to make that modification.

I never suggested adding that code to the functions.php file, so it might have been somebody else; obviously if it’s causing an error, it doesn’t work. That may have been posted by somebody using the OLD version of the theme and the OLDER version of the Tagdiv Speedbooster plugin, which has been recently updated, so that suggested code may no longer work. hence the error you’re getting.

Anything which tells you to edit core WP code should NEVER be done, in my opinion. “Generally.” But you know what you’re doing, so have at it.

Always check the DATE on any post which suggests changing theme code, in some way, outside of normal wordpress functions such as I use, and line that up with current date/version of theme and plugins. So, if something worked with v1 of a plugin, it might not work with v2 of a plugin, “generally” speaking.

• This reply was modified 11 years by simchris.

If you’re using IE11 try using Chrome; IE11 doesn’t do well with Ajax menus.

Also, be sure you deleted your old plugins and replace them with the updated ones; deleted old theme folder and updated with new one.

Some people report issues when you “over-write” the old folders with new update, which adss new files to old but doesn’t delete the deprecated files.

CLEAN install often fixes weird gremlins!

Yep, managing your updates for a theme is the best way to fix issues.

For major versions of theme update, it’s best to delete old version of theme, and install new one; delete and replace old versions of plugins with new ones.

Common sense for updating a theme. This is why the WP updater deletes old plugins before installing a new version.

Often with dot revisions you can “over write” the old version; but when you have problems, you need to delete all the old stuff, to do full upgrade to NEW version. Just like when updating WordPress itself — you don’t over-write (add to) the existing includes and admin folders, you DELETE the old folders and upload the NEW ones. Same with themes and plugins.

I would likely explore the built-in mega menu options already in theme (see the DEMO of the theme on Themeforest for examples) before trying the others.

+1 on all the great evolution of the theme. I, too, started with the theme back in2013, and have been very happy so far.

@Arved007
I “think” the new grid system might be based on Bootstrap 3, which allows you to do more things with column classes. The “old” 960/80 grid is now considered old by today’s standards. I haven’t looked at the new css file in depth, honestly.

I could be wrong, but BS3 has
750, 970, 1170 as the main containers.

Okay… wait for Marius or Lucian to get in tonight or tomorrow morning, depending on where you are in the world (I’m in Calif./USA). I don’t work for TagDiv, so my thoughts are generally just my own, but they would have an “official” help on this, or perhaps a patch to the theme if there is missing stuff.

That is part of the main WordPress install and not part of the theme, so I’d likely start by turning off your plugins, then turning them back on one by one to see if you still get that error.

You generally do *NOT* want to edit the core WordPress files inside admin, or includes, unless you know what you’re doing.

• This reply was modified 11 years by simchris.

Ah, you dont actually have a real website, just playing around.
Lucian or marius will try to help you on monday.

Wellll…. I went from 3.9.2 to 4.1 and had no issues, but I deleted the old theme folder entirely.

So, I did

1) backup dbase
2) backup “theme settings”
3) switch to twenty-twelve theme
4) delete wp-content/themes/Newspaper – folder
5) upload new theme
6) delete old visual composer folder – as noted in the update documentation on this forum
7) install new VC plugin, and new plugins from the new theme (speedbooster, etc.)
8) turn off ALL plugins
9) activate newspaper theme
10) activate visual composer theme
11) check theme settings

That worked for me.

Okay. That would be a problem 🙂

Maybe reinstall the theme, via FTP, to be safe.

If using a child theme you may need to switch to the main theme for update, then switch back to child theme, as some seem to do (I don’t use child theme methodology due to speed issues and gremlins).

• This reply was modified 11 years by simchris.

you might trying adding some basic CSS to the custom CSS box,

like

.img {border:1px solid #CCCCCC;}

but then adapt that to any of the image classes being used on the templates — do “view source” on one of your pages to see the actual tag being used for images, or existing class.

Here is a class used for full size image, placed into a post

.size-full {border:1px solid #CCCCCC; !important}

something like that ?

I have not actually tried this, but seems like something along those lines should work 🙂

Likely Lucian or Marius will follow up later Sunday/Monday when they are open again with additional info, if that didn’t help point you in right direction 🙂

• This reply was modified 11 years by simchris.

Well, that is tricky as it would require loading all those fonts from Google in order to do a preview.

Since the theme uses
1) web safe fonts, which have been around a decade
2) Google fonts easily researched on their site

I don’t see this being implemented.

For web safe fonts, you may find this useful:
http://cssfontstack.com/

For Google fonts, you may find this useful:
https://www.google.com/fonts

The above sites already preview the fonts, and have done so for many years, and are quite a bit more detailed than anything which could be added to the theme panel.

Hope that helped and welcome to the world of web development!

links to examples might be helpful ?

I have no issue with slider set to 12 items as long as I have 12 items set as featured.

Infinite scroll also partially dependent on the web browser, and caching of the browser seeing the page, speed of system to query the dbase, size of images/thumbs being served, etc.

Item 3 not clear what you mean? If you see an image on your page when previewing it, the image would be visible for site visitors viewing post also. You may have a caching problem, if using cache, which is showing image in one view, but not another. Might not apply, but hard to tell without an example 🙂

Yup. I actually changed mine to 50 recently on couple of sites which have photos and no illustrations, but 60 is what I’ve used for quite some time and works perfectly for my needs. Using 60 removed the “you need to optimize your images” warnings from PageSpeed. 🙂

Hi, did you try theme panel > responsive settings ?

Might not be the cause, but be sure to use the current HTML entity for the copyright symbol, and not simply pasting in the ASCII character.

© should work, or I think & # 169; (without the spaces) may still work also.

• This reply was modified 11 years by simchris.