Been there 🙂

@Danijelmo
You don’t need to post the same thing over and over.

Try testing your site with GTMetrix.com as it will tell you specifically what your site problems are and classify them by things like “Server” “Images” etc., with explanations.

Did you setup gzip/deflate on your server? [looks like you did!]

Did you edit your htaccess file (if applicable) to add expiration headers (e.g., mod_expires settings)?

Did you install an optimization plugin for images/thumbnails or change the default setting in your functions.php file?

Are you using the tagdiv speed booster plugin?

Did you disable system hogs like jetpack? Disable all plugins you’re NOT using?

Are you using a caching plugin once all of the above is working?

————

based on this you have some issues:
http://gtmetrix.com/reports/crnjaci.com/fxrIs409

1) you’re loading images off wp.com instead of your own locale; using a CDN for un-optimized images doesn’t make them load any better
2) you need to add instruction to the functions.php file to remove query strings (see my help on that in the pagespeed sticky topic)
3) you have some ridiculously huge images….
•http://i2.wp.com/crnjaci.com/wp-content/uploads/2014/08/IMG_0380.jpg?fit=1024%2C1024 is resized in HTML or CSS from 768×1024 to 291×388. Serving a scaled image could save 253.5KiB (85% reduction).
•http://i0.wp.com/crnjaci.com/wp-content/uploads/2014/08/10250323_10152304836090758_9213683227347813057_n.jpg?fit=1024%2C1024 is resized in HTML or CSS from 1024×768 to 291×219. Serving a scaled image could save 245.6KiB (91% reduction).
•http://i1.wp.com/crnjaci.com/wp-content/uploads/2014/08/DSC03988.jpg?fit=1024%2C1024 is resized in HTML or CSS from 1024×768 to 291×219. Serving a scaled image could save 241.2KiB (91% reduction).
•http://i1.wp.com/crnjaci.com/wp-content/uploads/2014/08/IMG_0594.jpg?fit=1024%2C1024 is resized in HTML or CSS from 768×975 to 291×370. Serving a scaled image could save 238.1KiB (85% reduction).
•http://i2.wp.com/crnjaci.com/wp-content/uploads/2014/08/IMG_0213.jpg?fit=1024%2C1024 is resized in HTML or CSS from 1024×683 to 300×200. Serving a scaled image could save 228.1KiB (91% reduction).
•http://i1.wp.com/crnjaci.com/wp-content/uploads/2014/08/10568980_10150651663339953_7674800880872619968_n.jpg?fit=1024%2C1024 is resized in HTML or CSS from 960×720 to 291×219. Serving a scaled image could save 199.1KiB (90% reduction).

Looks like you need to seriously look at your image optimization problems as your images look to be way too big when actually served on the pages.

Wny would you have a 250kb+ image file? A 1024×768 image if properly optimized should be no more than maybe 75kb.

BTW: optimizing your server/site for PageSpeed is YOUR job, not the theme’s job. Good to learn how to do this by reading up on the topic on Google as well as the docs provided with the theme as a courtesy.

@Danijelmo
You don’t need to post the same thing over and over.

Try testing your site with GTMetrix.com as it will tell you specifically what your site problems are and classify them by things like “Server” “Images” etc., with explanations.

Did you setup gzip/deflate on your server?

Did you edit your htaccess file (if applicable) to add expiration headers (e.g., mod_expires settings)?

Did you install an optimization plugin for images/thumbnails or change the default setting in your functions.php file?

Are you using the tagdiv speed booster plugin?

Did you disable system hogs like jetpack? Disable all plugins you’re NOT using?

Are you using a caching plugin once all of the above is working?

Hi
theme uses a custom font for all the little icons which is more efficient than loading a graphic a million times with CSS (sprites). E.g., using FontAwesome or similar. What you’re seeing is the font not loading and hence you get “broken” icons that look like [].

The only issue with this is that for folks using a CDN, there is a cross-site security setting that most people using CDNs don’t know anything about unless they have run into this before.

In fact, there is a setting you would need to create for the font file if loading off the CDN, called a “CORS” file. You should see the docs for your CDN on how to do this.

Or, simply load the custom font file off your local server – which with many CDNs you do by creating an “exception” in your CDN setup to NOT load the font file(s) on the CDN and leave on the domain where the site happens to be. This will often be simpler method for those who don’t want to deal with setting up a CORS file.

Great article from 2013 which helped me with this issue when we were setting up a CDN; we had to create CORS entry. Later we chose to simply load off our local server (where the domain and WP are installed): (THIS EXAMPLE IS FOR AMAZON, BUT SIMILAR PRACTICE WOULD APPLY TO ALL CDNs):
http://schock.net/articles/2013/07/03/hosting-web-fonts-on-a-cdn-youre-going-to-need-some-cors/

Info from MaxCDN
http://support.maxcdn.com/how-to-use-cdn-with-webfonts/

Probably admin here will need to make a very short tutorial on this topic, since more and more people are using CDNs, without actually knowing how they work. 🙂

If you already borked your install and are getting server 500 error or similar you will need to do common procedure to reset WordPress:

1) login via FTP, manually delete both Newspaper and Newsmag themes so that all that is in theme folder is default themes; this forces WordPress to restart with default theme

2) manually delete the Visual Composer plugin so there is no VC folder in plugins

3) rename your plugins folder to pluginsX

4) login successfully

5) go to theme panel and SELECT your default twenty-twelve theme to CLEAR the prior selection in dbase of the Newspaper or Newsmag theme no longer running

6) logout

7) via FTP or server side file manager, rename plugins back to plugins

8) login and make sure site is working

9) then do CLEAN install of the Newsmag theme, plugins

(admin feel free to add this to docs if you wish)

Chris

Try this:
1) make backup of your site files, as per usual good practices; use tools to export your database from WP panel. Backup images.

Clear cache.

2) make sure you’re running latest version of WordPress (4.1); v 3.9x has cross-site scripting vulnerability; v4.0 has bugs, fixed in 4.1.

3) switch to default theme (e.g., twenty-twelve); do this before disabling visual composer!!!!!

Clear cache again, as applicable.

4) disable ALL plugins

5) DELETE the original theme folder, delete the original plugins for theme (TD speed booster, TD social, Visual Composer)

Then follow my posts on best way to install theme:

================================================
Make sure you upload only the main theme files; don’t install the “all files” zip from ThemeForest… that has docs, psd files, plugins, etc.

You want to install the smaller of the two files on Themeforest, if you’re installing via theme panel with .zip.

BEST WAY TO INSTALL WP THEMES:
Ideal way is still to
1) unzip theme folder “Newsmag” on your HD
2) upload via FTP/SFTP to your /wp-content/themes/ folder
3) upload the plugins unzipped to /wp-content/plugins/
4) switch to default theme from your old theme [should already be done for migration]
5) turn off *all* running plugins [should already be done for migration]
6) clear your cache(s), turn off caching (!),
7) activate the Visual Composer plugin
8) activate the new Newsmag theme
9) launch the theme panel
10) reactivate only the plugins you 100% need to make sure they work (some plugins WILL NOT WORK properly with WP 4.01 until you update the plugins!).

Clear the cache in your WEB BROWSER FULLY and restart web browser; this clears any CSS/Java used by your previous theme admin, and theme, so that you see the new CSS/JS properly (seriously, this is cause for huge number of “my new theme doesn’t load right” or “admin panel doesn’t have any boxes!” errors).

If you’re running WordPress older than 4.0 be aware there is a very serious cross-site scripting vulnerability (e.g., WP 3.9.2). You should be running WP 4.0+ to use this theme properly.

This is standard practice for switching to a brand new theme and good habit to get into doing it this way to ensure you clear cobwebs on old, and cleanly move to new.

Hope that helps! 🙂

Chris

==========
ADVANCED USERS:
if you or somebody else optimized your site for better PageSpeed score and increase dbase efficiency, by editing the wop-config.php file to add absolute paths to the theme folder, you will need to remove that line prior to doing any theme switch. Some people forget this step and immediately get a server error trying to change themes in the WP admin panel. You should be making backups of your wp-config.php folder periodically anyway and never hurts to open it and view from time to time.

• This reply was modified 11 years by simchris.

I did post a step by step in this forum, you just need to search for it.

Yes, when the aspect ratio of thumbnails is different from the original image, it will be cropped; this is normal and usually works perfectly on photos – not so well with logos. Usually what we do with logos is put them on a gradient background or color backing, and then leave more “white space” around the logo to fit the thumbnail sizes better. This is common to all thumbnail systems — basically if it didn’t crop in some dimension, you’d get distorted stretched image in one x or y direction.

This might not apply to your case, but that has been my own experience.

Note if loading the custom icon font off a cdn you will likely need to add CORS rules for the font files.

Social media icons and other icons on page in 1.1 working just fine over here.

Weird. Drop down menus in both Newsmag 1.0 and 1.1 work fine for me in IE11/Win7-64, Chrome Win7/64, iPad/Safari.

Might be caching issue? Perhaps double check the “menus” settings under appearance, and resave the menu choices under menus > manage locations.

Try without the speed booster plugin active.

However I don’t have the sign-in active; not sure if that might be issue. Could be a bad character in the category for the drop down for your second menu element.

Tech support folk should be back tomorrow night/Monday.

Yes, as I said. Normal behavior for the category list on the category pages is to show “related” categories when part of a topic such as “tech’ or “entertainment” or “whatever” … in your case since you have all “master” categories and no sub categories, it shows ALL the master categories since you have no sub categories.

Tech support will need to provide you a fix or option for either not showing ANY topics, or you would need to create sub categories for that to work as shown in the theme demo, and for sites like mine (and many sites) where categories and sub-categories are used.

Put another way: its default behavior is showing all sub-categories in a parent. If there is no sub-category, it’s showing all the parents.

You will need to wait for tech support to be back in tomorrow night/Monday to address possible options for your particular setup. Sub-categories are the “best” way for most sites to group together related topics, and that is how the theme is setup for default.

The only way you can “fix” this that I know of right now, is to create sub-categories for your content; meaning group your existing topics into parent topics. Then when somebody is on a child topic, that list of topics would ONLY then show those other topics in the same child topic list, not ALL the topics sitewide.

Sorry I don’t have a better solution for you.

I think for the footer full line, without menu, you’d have to modify the footer template to have the copyright line run the full span width and remove the div for the footer menu.

Tech support would need to specify exactly how to do that.

In our case, we just made really short copyright notice, then put the rest on the legal page, linked to along with privacy policy from the sub footer menu option.

Then it likely is showing “all related categories” since there are no master categories. I guess this would be normal. Many sites will put topics into categories so that things can be put together in similar topics for dropdown menus.

Not technically a bug, but I suppose you could “disable” the show all categories option somehow.

Works for me since I use main categories and sub-categories, such as having
entertainment > books
entertainment > movies
entertainment > music

tech > software
tech > hardware
tech > whatever

Works great when you have it setup something like that.

In your case, it does seem like a crazy lot of topics to show for each category page.

Maybe tech support will have suggestion on that for your case.

Groovy 🙂

You can try accessing those files in web browser to see if they are publicly reachable. Most will have 644 permissions so only readable by WP.

But again, all the CSS “class names” unique to tagdiv used throughout the code when printed on the page, could easily be figured out if somebody really wanted to know.

Keep in mind you will have to redo all these changes with an update to the theme (e.g., v 1.2), so normally you would not do this until you are 100% sure everything is working for you. And also be aware you might not want to change some things used by the speed booster plugin as that may break if it can’t find its pre-named pieces.

Security issues would be more likely an issue with cross-site scripting bugs, as found in WordPress 3.9.2, and the version of YOAST prior to the one releases this week. I’d worry more about staying on top of those kinds of vulnerabilities, but I suppose you’re doing that also if you’re going to be obsessive about hiding as much as possible.

There are some good tutorials on line related to hiding info about WordPress, which folder can be changed, setting up security to stop multiple login attempts, deleting the “admin” account for WP, etc.

Right. That is the menu setup page. Has nothing to do with your “categories” setup page.

The items showing on the category page on your site is not part of the “menu” it’s part of the site navigation, slightly different thing altogether.

If on the posts > categories page if you have “sub categories” of a main category, those sub-categories will appear on the category pages of that main category as they are doing on your site. So if you have 10 items related to WWE under a “WWE” main topic; then all the topic pages show the full list of related topics from the same main category/topic that page happens to be in.

Not sure that helps or not. 🙂

• This reply was modified 11 years by simchris.

The theme normally shows all the “sub categories” for a master category, as found in the demo; that is normal:
http://themeforest.net/item/newsmag-news-magazine-newspaper/full_screen_preview/9512331

To *also* have a “drop down” menu, you would need to create that in your menu setup.

So if you have 10 sub categories in “movies” and go to the movies page, it will show all the sub categories at top of page. Very cool.

So that is working normally.

SEARCH BUG/PROBLEM:
I just did a search on your website without any problem on the category pages; but it does *not* work on your home page or the post page, as you said.

Wait for tech support to follow up.

You may want to read up on how to use WordPress from the WordPress Codex; you *can* simply rename the theme folder and CSS name for the theme; which is how it’s done for web development, such as for a client, or better security (we do that here, changing theme name to sitename). If you’re comfortable editing the functions.php file, then changing the theme name is done simply by editing the style.css file which is where WP picks up the theme “name.”

Note it won’t change the theme style classes so somebody can very easily “figure out” which theme you’re actually using, if not the version.

Are you removing all the versioning from your site using the commonly available code to put at bottom of functions.php? That is also recommended to hide versions of WP, and also visual composer (see my separate post on how to also hide that code).

TO THE POINT (sorry!):
You can remove that “theme credit” code from functions.php without anything breaking, but be aware it makes it harder if you ask for tech support in the future if the admin here can’t figure out which version of theme you’re using when looking at your page source to debug any of your possible problems with CSS, customizations or running plugins, etc. If you’re comfortable in remembering to always “state” which version you’re using (and keep track of that somewhere), when needing support, you should be fine. 🙂

We actually use mod_pagespeed which just removes *all* commenting for faster page loading, which is recommended if your hosting provider offers that.

You can also further optimize the install by placing the explicit paths to the new name theme folder in your functions.php folder once you’re “set in stone” (obviously if you switch to another theme from admin, it may break) and also the site name URL, but that’s a bit advanced. Research the WP Codex on how to do many things like this (some of that is in my long winded comments in the Newspaper forum under the “Pagespeed” sticky topic).

Hope that helped, versus annoyed 🙂

Switch back to default theme; delete the Newsmag theme folder; delete the visual composer folder in /wp-content/plugins

Follow the install instructions here
https://forum.tagdiv.com/installation-newsmag/

Best method is to install via FTP;
where you upload the unzipped theme and manually upload the plugins. Good thing to learn if new to you; as it’s the best way to manage WP sites where sometimes “permissions” preclude install from the WP panel. Basically what can happen is that WordPress might not have “permission” to install things.

Wordpress is mis spelled.

See the theme docs on how to update.

there is a patch file in the full download, but i usally turn off plugins, delete old theme folder, upload new theme folder, reactivate theme

Obviously you need to manage your caching and cdn settings as applicable, such as clearing cache before reactivating new version.

• This reply was modified 11 years by simchris.

Note the “remove_action” section is always useful… note it refers to “visual composer” and “meta data” … this removes the comment printed in the rendered page where it shows “created with visual composer 4.3” or whatever. Annoying.

So, basically that code I posted has (3) sections
1) remove general versioning from normal version strings; might not work on all the tagdiv speedbooster enqued stuff
2) change default thumbnail compression level (default in WP is 90, which is for quality, not speed or best practices, which is the WP mindset — better vs fast …. where 70 would be better default, frankly). 50 works. I think we ended up with 60 on some sites for some odd reason (I think ’60’ worked better with mod_pagespeed on our server for WebP conversion or something). Anything is better than 90!
3) hide the visual composer comment string.

You can actually find all my various pagespeed rantings from the past year on the Newspaper forum in the pagespeed sticky post if you want the whole shebang of stuff I do. Luckily TagDiv put a bunch of that into the standard theme docs now, and they already knew most of that from optimizing the demo sites anyway.

If you want an extra little boost you can also locally host gravatars and also optimize your wp-config file; see the Newspaper forum sticky topic, and simply start at end and work backwards to see all my special tweeks, if curious. I think later in the hundreds of posts I would often “resummarize” things, as well as add tweaks for the gravatars, and such. No point in repeating all of that here again. 🙂

• This reply was modified 11 years by simchris.

I think the original sales page for the new NEWSMAG theme had an incorrect graphic showing “full width” layout, copied over from the Newspaper sales page, which might be confusing to some. It is no longer there.

That’s what I thought. I don’t think slider is able to do “double loading” — meaning it’s doing ajax or whatever to load each “slide” as an image, but cannot also do “media query check” as each slide loads, as that would mean reloading the slide every time to check for viewport. Horribly complicated and almost means having to do a viewport check, THEN load “desktop slider” vs “mobile slider” with two different setups; meaning loading both large and small images like is done with logo. Problem there, however, is what size would somebody load for mobile since the viewports vary, and traditionally loading larger image and “scaling” it was fine since you’d get benefit of more pixels for retina without having to actually load a denser image.

In our case to this issue, the solution was running mod_pagespeed on the server as this optimizes and caches the most common “rendered size” — so if 80% of your audience was coming in on iPhone, viewing in portrait, and the 1073 image was loading as 573, then mod_pagspeed would make an optimized 573 size image and cache it; which would speed things up AND help with the “resize image” technical “problem” with mobile.

I cannot stress any more highly the benefit of mod_pagespeed for this kind of issue; and the fact it can generate optimized images for Chrome and other WebP image capable platforms (WebP more efficient than jpg).

If you can use a web hosting company using mod_pagespeed you will be amazed. Of course some CDN providers are now offering this, too, if your hosting provider doesn’t yet do so.