We use a customized version of the older free version of AdRoate over here, also.
Good choice!!

• This reply was modified 11 years by simchris.

check your php settings as it might have a limit on the size of files you can upload

1.7 running much slower on our server, which I tested today extensively and rolled the one site using it back to 1.6 as it was up to 10x slower overall based on our particular Linux/Apache/CentOS/Plesk setup.

1.6 works fine around here … 1.7 does have some issues, which I extensively tested on our server today, and rolled back to 1.6, and it’s working great for us.

3 sites no issues … running 1.6

1 site crashing and all kinds of oddities … running 1.7

So, if you went to 1.7 … GO BACK ! 🙂

• This reply was modified 11 years by simchris.

NOTE TO ALL…
a couple of us folk on the forum have done a bunch of speed testing today, and upshot overall is…

ROLL BACK TO 1.6 …

v1.7 does seem to have some issues causing CPU headroom, php crunch, and slow load times compared to 1.6.

Those who know me from these forums the past 1.5 years know I’m usually the last to say “sky is falling,” but in this case I am recommending going back to 1.6 or staying there for now.

I *DO NOT* recommend using v1.7.0 of Newsmag, at least on Linux/Apache.

NOTE TO ALL…
a couple of us folk on the forum have done a bunch of speed testing today, and upshot overall is…

ROLL BACK TO 1.6 …

v1.7 does seem to have some issues causing CPU headroom, php crunch, and slow load times compared to 1.6.

Those who know me from these forums the past 1.5 years know I’m usually the last to say “sky is falling,” but in this case I am recommending going back to 1.6 or staying there for now.

I *DO NOT* recommend using v1.7.0 of Newsmag, at least on Linux/Apache.

Obviously the quick and dirty method worked
(trick is to delete via filemanager on server; then upload via FTP)

Always amazed that works. 😉
So, 10 minutes … and I just switched back on Disqus, photo new items right side, third ad, and the pages are 10x faster at least … maybe 20x faster…

so… shazam… there you are. In our case 1.7 does NOT work well with all the snazzo-riffic hardware, bandwidth, mod_pagespeed and other stuff we have on tap. 1.6 literally rocks.

I do believe you are correct in that some other things related to php queries and whatnot are baked in someplace, as that is HUGE difference.

from theme panel, click home page button – 2 seconds in IE 11 Win7/64. Previously 20 seconds … soooooo….

okay, happy that worked.

I guess we’re not crazy, then 🙂

I’m going to try the dirty in place rollback,
which basically entails via FTP quickly deleting the theme,
replacing,
quickly deleting the td plugins
replacing,
then login see if it still works with transient settings retained.

Dirty way of doing it quickly without first disabling everything and changing themes.

Normally works if nobody logged in and going up a revision; so will see if works going back. If not, can always reset and do it the long way (as per my “how to upgrade” sticky post ….)…..

so… site going DOWN …. (!)

stay tuned…..

normal server response time is 0.31 seconds, and today it’s been averaging 1.6 seconds … which shows how much the attack has been messing with us.

After 9 years with WordPress and 20 years with webdev… and the sticky post in this forum on how to upgrade the theme … um, yeah… I updated it with fresh version.

I have to do completely fresh version as I tweak the theme for some minor things like custom field for hit counter, remove the XLRPC thing from header, minify the style.css, remove the breadcrumbs from search template, and put in our custom functions for optimization and disabling some things like not loading the visual composer CSS on post pages, etc.

So, in theory all things being equal the 1.7 site should behave just like the 1.6 sites except with lazy loading on top.

And I never use child themes, and all files are uploaded with Linux/unix line breaks vs windows, etc.

(I’m an advanced user …. obviously …)

Hence my … what the hell, man reaction with the ENC site.

So… going to roll that back once I get couple more client things done.

Basically going to use our tweaked 1.6 version – same exact thing running musewire.

Of course the dbase for ENC is hideously huge, and 10x the size of musewire, but other than that …

We have 32GB RAM, 12 cores of XEON power, and dedicated gigabit switch in Class A datacenter (SoftLayer) … so, we’ve got the juice.

ENC has 512MB allocated to PHP. So… may I just say … “sheesh!” 🙂

I just turned off whole bunch of stuff like “related posts” and removed on ad from sidebar, removed new items from footer 2 (replaced with subscribe), removed images from sidebar for new stories …

home page comes up in 6-9 seconds, vs 1-3 for the other site.

Crazy. Same server. Same php memory. Same mod_pagespeed settings.

And the 1.7 site is loading the gravatars locally, too … still hideously slow.

• This reply was modified 11 years by simchris.

I may try to roll back to 1.6 on one site as it’s deathly slow …

see:
http://enewschannels.com …… (1.7)

speedy
http://musewire.com ….. (1.6)

(and this is with server under attack right now …)

• This reply was modified 11 years by simchris.

I am noticing my 1.7 pages are loading muuuuuch slower than the 1.6 test sites.

Today I can’t fully judge as we were being slammed by yandex …. and others … from Russia.

Server processes spiked at 270 once, which surprised me it didn’t melt. Normal is 0.9 to 1.2 (!).

On 1.7 it’s taking forever right now to even preview a page. Frustrating.

Also weird is that my animated GIF keeps getting turned into a jepg even when I upload via FTP. (WTF?)

Soooooo……. we’re definitely NOT in the Summer of Speed we had going with Newspaper, that’s for darn sure.

Not quite sure what to do just yet. But it’s noticeable the speed hit visually …

I think you have some good points!

I believe there was a post yesterday morning on how to turn off the lazy loading, so you might have to find that giant thread on that topic.

I am very curious what your results would be with that OFF.

It is cool, but I had major problems with that this time last year testing lazy loading with newspaper theme and chose NOT to use it. Even though, technically it’s supposed to help with mobile…

Make sure you’re in the text editor vs visual editor …. on the post edit page.

Then you can make links normally with HTML, or using the links button in the tool bar.

If you try to write HTML on the visual editor, the brackets get converted to code and don’t work.

You can use DUPLICATOR plugin for WordPress to move site and content from one domain to another domain. This will also fix internal links to use new domain name for all internal links, images in posts, etc.

Then you setup a 301 redirect on the old domain to point everything at new domain; this is normally done via the .htaccess file … as so:

<IFModule mod_rewrite.c>
RewriteEngine on
Options +FollowSymlinks
RewriteBase /
RewriteCond %{HTTP_HOST} oldwebsitenamehere\.com
RewriteRule ^(.*) http://NEWSITE.com/$1 [L,R=301]
</IfModule>

I just did this couple of weeks ago with my 9-year old music magazine which had horribly long name, now nice shiny short one after 9 years.

Google actually has a pretty good guide on the basics of this process.

1) migrate all content to new domain name; make sure it all works; meaning images, etc.
2) add 301 redirect on old domain name to htaccess file — so anything you type for old site redirects to new site
3) add new site to Google Webmaster tools and CONFIRM/validate ownership
4) once 301 redirects work, then you can do “change site” in Webmaster tools from old to new
(NOTE: this does not work with https websites which is a whole other pain in the butt)

Hope that helps.

🙂

Clear all your caches.

You might try the simple local avatars plugin to have local copies of author images vs loading from gravtar webswite.

Not sure that helps, but just a thought.

SEE: https://wordpress.org/plugins/tags/ad-management

https://wordpress.org/plugins/tags/ad-management

That’s up to you.

You might use an ad manager plugin, or manually put in your own graphics and links in a text box.

The theme doesn’t provide an advertising sales manager or “rotation” tool.

You might try googling ad managers for WordPress.

A really good web host knows how to manage overloads and such …

our server hit a peak load of “270” today from the Yandex/Russia attack. Didn’t crash.

So, we went up to 270-times normal load (!). Newsmag and Newspaper sites still work.

Optimization is reallllllllllly important!

Using my optimization guide is definitely a “must” — that’s for sure, as well as the TagDiv docs on speeding up theme. Every little bit helps; lowering the overall footprint by 20% is what makes it “work” …

So, I’d likely try to fully optimize your site FIRST as you’ll need to do that with ANY hosting company.

You could also explore some of the “WordPress hosting” companies out there.

But – a $5 a month account is not going to likely work too well with any robust theme.

Welllll…..
here’s the thing …. if you don’t have robust hosting, I’d likely consider NOT using ANY theme running Visual Composer. All during 2014 with the Newspaper theme we’ve seen zero problems with CPU stuff, but during 2015 it seems they are using bleeding edge stuff to give power users all the stuff they have been demanding … unfortunately a lot of people want their site to do stuff that takes 500 processes and their hosting account can only do 150, and kaboom.

I’m still running the Nov. 2014 version of Newspaper for one of my blogs. Zero hassles. But I didn’t update every time a new version comes out since I didn’t need the extra 50 things added.

So, it’s kind of a tricky thing … I think VC needs to have a “developer mode” and a “deployment mode” where you have all the bells and whistles for design, then “export” your settings for a “lean” setup for actual deployment. But, it isn’t quite that clean yet.

TagDiv chose to use VC 2 years back as it was the coolest thing since sliced bread, and still is. There is another open source very very simple pagebuilder, and couple of page builders which cost $99/year (and stop working unless you keep paying!). So, for a complex layout builder like this… VC is really kind of the “standard” right this second.

Then again depends on well optimized server. I’m running multiple installs of Newsmag and Newspaper, and server not overloaded in the slightest.

Yes. Visual Composer is a memory hog.

Also if your site gets overloaded with requests. I just posted note on the Newsmag forum about our site getting slammed by the YANDEX bot and our server processes when from normal of about “1” up to “49” … which is 50x normal (!)… it’s actually worse than that. We blocked Yandex and it’s coming down to normal.