147KB for the home page is no longer considered “large” by today’s standards.

15 years ago, we tried to keep pages to no more than 50kb total. But now with wireless being faster than modems back then, larger resolution displays, more images, etc. — 200 – 300kb pages are no uncommon. 1MB is a lot. 147kb is not.

Make sure your thumbnails are all as compressed as possible; change default compression level in wp-config.php or use a plugin. All the little images on home page should be very compressed as they are just visual placeholders. Make sure things like logo is very compressed also (e.g., if it’s only 4 colors, use .png vs .jpg, etc.).

Make sure you have gzip/deflate running as this compresses page for web browser automatically.

ADVANCED:

For advanced uses, consider server side compression like mod_pagespeed, or a caching plugin that might also remove blank spaces, comments, to reduce the file size of the HTML. For super advanced use, consider web host that runs both http/2 and mod_pagespeed (MPS can remove all comments, double spaces, tabs/indents, comments, and other elements that pad the page on the fly, then cache it via server side caching like opcache).

Some people set up a coming soon page on live domain.

Then build site on local development server (MAMP, etc.).

Some build their site in a folder to see how it “actually” works on server, but do so in a sub folder like
mysite.ooo/dev/ — then when done, move stuff to root

Some folks build site in place, but use a coming soon plugin, and toggle the built-in setting in WordPress admin panel “hide site from search engines” ….

Lots of articles online to set this kind of thing up.

WordPress does this with some updates of themes and the full WP upgrade if your “transients” are cleared at same time. Not a theme issue, as the them does not control the WP > settings > widgets.

It’s been an issue with WP since it was launched.

If you change themes, the widgets get reset — at least the added a moved to ‘deactivated’ section, so sometimes you can just move them back.

NORMALLY, on a live install where transients are stored, simply updating your WP version will *not* lose widget settings.

Broken pagination was a bug in WordPress no the theme — which was fixed in WP 4.4.2

Good to keep eye on WP updates as they often list fixes, severe security updates, etc. WP 4.4.1 introduced the pagination bug, not the theme. (4.4.1 is NOT a secure version.)

REF
https://codex.wordpress.org/Version_4.4.2
—
Summary
From the announcement post, WordPress versions 4.4.1 and earlier are affected by two security issues: a possible SSRF for certain local URIs, reported by Ronni Skansing; and an open redirection attack, reported by Shailesh Suthar.

#36435 HTTP: 0.1.2.3 is not a valid IP.
#36444 Better validation of the URL used in HTTP redirects.
In addition to the security issues above, WordPress 4.4.2 fixes 17 bugs from 4.4 and 4.4.1

Make sure you increase the default memory in your wp-config.php file. Visual Composer uses a lot of memory, and by default WP assumes you’re using a text-only theme like those included with the WP install.

Default is 40mb and needs to be 96mb or higher.

There was a bug in last version of WordPress which broke page numbers, unrelated to any theme.

If you have not updated your version of WordPress to the latest version, that might be good first step and then clear all site caching / CDN content cache after update of WP.

Might not be your issue, but is is *the* problem that prior version of WP introduced, and was fixed a month later with the current version of WP.

All mobile themes are “responsive” which means they are designed to move elements on “the grid” depending on viewport, and if they don’t fit, they drop down to next row in grid.

I think you can alter the “break point” to keep the sidebar on ipad portrait if that’s the sort of thing you’re thinking, but obviously a sidebar on a small phone makes no sense.

TagDiv will be able to give you heads up altering the breakpoint (this is actually one of the reasons we use the Newsmag theme, to keep the sidebar on the iPad portrait view, which it does by default).

Also note if you add a comment form that uses a reply-to submitter plugin, it’s not advisable to send back automated reply, as this can be used for spam, in order to have one person pretend to be somebody else and put spam in the form, which then gets sent to the third person as a auto-reply from your form, and then you get spam blocked.

So, good to research that a bit to fully understand the implications.

Well, that is just the div information — how is that supposed to load onto your page? Using a plugin ? Are you putting the javascript elsewhere on the page/template? Check the javascript for your site to make sure in right place and properly formatted, and actually loading on the page with that ID and class in order to load the element.

That code alone can’t possibly load anything.

Also note trying to load a leaderboard ad (728px wide) into a sidebar probably not advisable so always good to use a responsive unit site-wide if they offer it.

So what do your error logs say?

Server out of memory, CPU overloaded ?

Try further optimizations that can overload site
a) disable all pings/ XML-RPC
b) disable visual composer, and use the SHIM plugin from Radu (see my optimization thread and archives); disable loading VC on post pages
c) make sure you have plenty of RAM allocated to WP (e.g., big site, 256M vs 40M makes huge diff)
d) make sure you have system in place to stop overloads from bots, like the limit login attempts plugin that blocks IPs from bots trying to guess password for admin
e) [ etc ]

Re-read the Google page

the canonical tag tells Google which version of the URL to any page on your site is the correct one

e.g.,
http://www.yoursite.ooo/name-of-post/

vs

http//yoursite.ooo/name-of-post/

are two different URLs

and if you move to https, that introduces yet another variation.

Using the canonical link on all your pages — as per the Google docs, and hundreds of online articles you can review to self-educate yourself, tells the world “which version” is the “primary actual defacto official one and only best link to use page” … this is how you remove any confusion for which is which, and also ensures no duplicate content issues. And if you move to https, changing the canonical helps instantly identify the new corrected URL to use for an existing page, regardless of 301 redirects.

Best of luck ! 🙂

• This reply was modified 10 years by simchris.

Google “what are canonical links” ?
https://support.google.com/webmasters/answer/139066?hl=en

Use something like YOAST SEO to add them.

View your ‘page source’ in web browser, to see what is actually ‘printed’ online in your HTML.

It’s going to be at least 8 weeks before I get back to sorting this out for our sites, as I’m building a custom CMS based on WP for our company stuff, and also trying to make sure AMP works on our news portals.

IF/When I get to this I’ll make a tutorial on how to add the code to the single template, and probably best trick is to take the FB comments code for [render here] (not actual code) and put that into the place where comments normally render.

Unless somebody beats me to it 🙂

Yes, you should ideally serve ONE version of site, but normally you would setup your DNS to serve both www and non www, which it appears you’ve done, and then make sure your CANONICAL links say the one you want — this is one of the reasons that Google et al implemented the “canonical” link — this tells bots which link is the “real one” and which is another version, such as www or not www, amp, mobile, etc.

So, check your canonical links are showing on each page as the “actual” link you want the page to be “known as” and of course Google has tool to let them know also. But this needs to match on your site, your theme, your internal links, Google Search Console, G+ account, AdSense, etc.

Takes awhile for them to work.

I posted something about this on the NEwsmag forum last month …. for time being use the plugin, but ideally see that thread for the moment.

Best to do a clean install of theme theme and plugins on your working site in order to have it working properly. If you have something broken based on however you migrated stuff, obviously stuff might not work.

The default templates are in the theme panel under the normal location — see theme docs >> right side of page for how to install demos.

If demos missing then you busted something on your install !

Wish I had a one click solution, but sadly no.

🙂

Well, again a theme does not manage the directory.

Google is a marvelous resource for learning how to do this somewhat complex task:
http://www.wpbeginner.com/plugins/how-to-create-a-web-directory-in-wordpress/

some plugins to review/ explore:
https://wordpress.org/plugins/search.php?q=directory+site

example plugin
https://wordpress.org/plugins/connections/

Sites are built something like this

[server]
[hosting]
[domain]
[dbase]
[wordpress]
[theme]
[plugin]

so theme not critical – the plugin is usually what adds the functionality to create accounts, shopping, directories, forums, etc.

Just like WooCommerce is a plugin, not a ‘theme’ — point is, you have a great theme. You just need to look at the plugins, or forms/addon systems that do this. After 12 years of WordPress, you’re not first person to build a directory, so there are LOTS of resources online for “how to” do this.

Not theme specific, in other words.

Hope that helps!

🙂

(gingerbread cookies accepted in my virtual tip jar)

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

I’m assuming you’ve done all the normal stuff like updating the wp-config.php file, htaccess file, resave permalinks, import dbase, etc.

Well, one of the most robust and popular tools, although a little bit of learning curve also …

meaning, if you can’t manage to do FTP, then this won’t likely help …

but the plugin DUPLICATOR allows you to fully move a site and dbase from one place to another to “deploy” it or move to new server, or even change domain name.

So, if you have your local site setup as /1.2.3.4/test/site and are moving to /mysite.ooo — it can even help with that by rewriting the site URL to actual with proper serialized dbase rewrites.

Or — hire a developer who knows how to do this stuff 😉

(sorry not better answer)

it’s actually easier – in future – to setup your test site on a WORKING domain by using sub-directory like /futuresite/ then when ready update the config file to be /root/ on the same domain.

Not wise to build it locally, if you don’t already know how to migrate a site the way you’re attempting.

• This reply was modified 10 years by simchris.

Good point – I wonder if the support extension money goes to Tagdiv ?

Even if Envato takes 10% cut or whatever, I guess TagDiv would still get most of it ?

Hope so! I was just about to go put some money on that !

LINK WORKS
http://screencast.com/t/IJJf4eaoATr

Another great resource is several books that explain how WordPress works, how web design works, how the web actually works, etc.

Also plenty of websites, including the main WordPress.org documentation which is well written for “newbies.”

Don’t give up — but it is a learning process. 🙂

Likely need to look at how to create a directory, either via plugins, or similar.

Theme can make a directory “design” but theme doesn’t have a form that allows people to submit their information, which then gets assigned to a category.

So, first step might be going and looking for a “plugin” for WordPress that handles building directory site. This is just a theme, it’s not an “application.” A directory site, just like an ecommerce site, would have the ability to sell listings, or free listings, or both, allow people to upload a logo or similar things you would need to setup.

Best bet is to do basic install of the theme then copy over the theme “settings” from your work site to production site.

e.g., options
1) copy over the mysql dbase from your local system to server via phpmyadmin expport > import
2) copy over the settings from your theme panel for “export settings” for theme, import on working site
3) learn to use FTP to copy over your image/uploads folder from temp to live location

Lots of tutorials on web on how to move from MAMP to hosting site.