Well, the theme and WP don’t control your domain name/URL.

You should try using DUPLICATOR to move from old domain to new one.

This is not theme related; you should try getting the site working at new URL with the default theme FIRST, then get the new location working with this theme.

FYI
https://codex.wordpress.org/Moving_WordPress

https://codex.wordpress.org/Changing_The_Site_URL

———–
Typically to change a site URL
you need to
a) setup new domain/hosting
b) setup testing version of WP at new location
c) at your domain registrar, point domain name at new IP for new site
d) setup redirect on old domain to redirect to new domain
e) if moving existing site and not using DUPLICATOR, you will likely need to go into the phpmyadmin and do search/replace in your MySQL dbase to replace instances in the post meta of oldsitename.vvv to newsitename.vvv for things like embedded images

Many tutorials online on how to do this.

Theme does not control changing domains or hosting in any way.

Best to do your move with default theme; then switch to this theme.

Your hosting provider can likely also help with this.

Has been for 2 years for this theme, please look again 🙂

You may need to make all the blocks visible on your page edit page, using the visibility tab [screen options] top right of the page on your edit page.

Hope that helped!

Hi,
just some input … what we do is upload images via FTP we don’t want multi-cloned; like logos, or branding, or “about us” stuff, avatar images, etc.

For posts, one way we cut down on multiple image creation is this

a) upload featured image via post panel; then select as featured image
b) additional images on post, we load via html, from FTP versions, so only ONE file exists.
c) for optimizations, we did the most common tricks
— 1) set the default WP sm/med/lg sizes to the 3 sizes we most commonly use, and set largest size to the larger block image on front page, sometimes larger than our post image (640×480)
— 2) turn “off” image sizes we are not using from theme panel, limit sizes used on sidebar to same module sizes used for smaller home page sections
— set all category, archive, 404, author, search templates to use same size images
d) normal WP image compression optimizations, as in our case we pre-optimize uploaded files, and we set the default compression for ImageMagick/GDlib used by WP to 55 or 60 vs default 90.

This helped control the sizes.

On one old site, where images had not been compressed well, and/or could not all be “regenerated” we downloaded the image folder via FTP, then applied a local application to optimize all the images then uploaded the optimized image folder back to server.

Hope some of that helped, or perhaps food for thought 🙂

also now found in the “best of forums menu” 🙂

https://forum.tagdiv.com/best-of-forums/

Best way is to edit the style.css file to set your custom font manually, then put the font loader info at bottom of the file.

Unless there is a separate font file which might conflict with that in the latest theme versions.

TagDiv may have much better answer.

But that’s how I over rode our site to run “all OpenSans”

• This reply was modified 10 years by simchris.

It’s working for our sites. Likely something you’ve “changed” on your files or if using pagination plugin has messed something up somewhere.

Yes,
you need to spend some time researching how WP works and also hosting, and other speed optimization tricks.

Theme doesn’t control your hosting setup or optimization of your site processes. It’s just a theme. Optimizing WordPress applies to *any* theme sitting on top of WP and PHP.

For example, to increase memory for WP, you have to
a) edit your wp-config.php file to specify the memory
b) specify max RAM in your hosting php.ini setup
(you need to do BOTH)

For best speed, you need to set proper gzip compression, set TTL settings, minimize external element loading (e.g., Jetpack, ads, etc.)

Note there are some resources here to help:
https://forum.tagdiv.com/how-to-make-the-site-faster/

https://forum.tagdiv.com/topic/tutorial-chriss-custom-optimizations-for-functions-php-etc/

hope that helps! It’s a process we all end up learning at some point — so be patient, read a lot, and then soldier on ! 🙂

You likely need to be more specific on what you were trying to do, exactly.

Did you change your website URL, and then move the theme files from one site to another… or ?

Usually best to do clean install on new domain, then import the dbase from old site to new; then edit the dbase to search/replace instances of old domain name with new domain name (URL).

In face, we did this recently with the “DUPLICATOR” plugin which does most of it for you automatically!

If you’re talking about changing “permalinks” that is done via the WP admin panel, not in functions or wp-config.

• This reply was modified 10 years by simchris.

You can use numerous RSS/XML import apps, like “FeedWordPress” to import content from external RSS (with permission of course).

This was fixed in the latest theme update posted 12/15.

Home page. Make a text box, and put your text in there, wrap in h1 tags, add desired h1 style for home and shazam.

Yes, a desktop image of 640 is still shown at a relative pixel “size” in dimensions of 320 when shown at half size; so it doubles the perceived density when resized (I am a ceritified Photoshop guru for 20 years, fyi).

In any case, images look great how we do it. Your mileage may vary. 🙂

The new WP process is to load “smaller” images at smaller “dimensional” sizes, not “higher resolution” images at smaller sizes.

pixel density of a web image is still ostensibly 72, 96, or 100ppi for the actual image itself. You’re not saving out web images at 300ppi; and again, relative perception of the larger image when resized at one half has an effective instant doubling of the density. Try it 🙂

(ignore my comment …. just venting today …. )

Anybody can bookmark a website/page by using the favorites/bookmark function in their iOS web browser (e.g., Safari, Chrome, etc.). You don’t need any special link.button, etc. to do that.

If you’re talking about a custom “app” — you need to build one, then have it in the App Store, then put the code in your header file to sense/inform iOS visitors you have an app.

If you’re talking about a pre-composed Apple icon, you simply put those in the root of your main public web root, and Apple devices look there for it.

If you’re talking about “web clips” — see this:
https://developer.apple.com/library/ios/documentation/AppleApplications/Reference/SafariWebContent/ConfiguringWebApplications/ConfiguringWebApplications.html

With Newsmag our images look great on retina/iphone 6 and iPad Air, and HD Apple Cinema Displays.

If you avoid uploading small images and/or over compression, and avoid stuff like Photon, there is no burning need for the new WP format images for many of us.

For example if you have a 500x375px image, which is shown at 300x188px on retina/phone as responsive, it effectively doubles the number of dots in same space and so should not look fuzzy unless you’re doing something wrong.

Just food for thought for anybody freaking out about WordPress’ method — since they finally caught up with all the theme developers like TagDiv who *already* had a solution for this. WordPress – last to catch up with tech, as per usual ;-0

You don’t need to “allow” Google to read anything — Google reads everything unless you tell them to NOT read something. So, it’s not necesssary.

Oh I guess we don’t get the fancy emoticons here … thought you could put a beer emoticon in there 😉

Still figuring out the darn emoticons — just realized I didn’t know how to put the beer icon in there either!

Anyway — glad to help.

Happy holidays!

:beer:

• This reply was modified 10 years by simchris.

Also note that WordPress automatically creates an RSS feed for each “category” on your site.

http://bettips.dk/category/spilforslag/feed/

It can’t make RSS feeds from single pages like you have in your menu/navigation. But any proper WordPress “category” or “tag” has a RSS feed simply by adding /feed/ to the end.

WP docs:
https://codex.wordpress.org/WordPress_Feeds

Can take awhile for FB to activate the stream, so check back next a.m.

• This reply was modified 10 years by simchris.

Check permissions on your media folder; should be writable.
Some auto-updates of WP can reset this with permission too low.
Try resaving the default media sizes in the WP admin panel.
Be sure to clear all caching (any plugins); *and* in your web browser.
Turn off any/all image plugins (optimizers, Photon, etc.).

Did you clear your caching, reset CDN, etc. ?

If you upgraded from 4x to 6x, it’s an all new theme.

Often simply resaving the home page layout in VC will update it.

But TagDiv will have better answer here when they get back in.

Nothing to do with theme. Theme doesn’t control the media manager.

There is 2MB file size limit, but no limit on the image size, ad WP has it set by default. You might try changing the default sizes in the WP admin panel for media?

Also clear all caching, rest any CDN, etc.

I think you’d have to edit each loop in each templtate file you’re actually using — so if you’re using post template 4, you’d likely edit the somewhat obviously named theme file: loop-single-4.php

Yes, with ACF you have to actually place the shortcodes for your custom fields into your post template(s). This is how ACF works, it doesn’t happen automatically (I use ACF 4 and 5 PRO).

So, if you’re using the “style 2” post, you’d need to look at adding your field shortcodes intto the style 2 theme files in your /newspaper/ root.

If using post template 2, try placing your shortcode(s) into

single_template_2.php
loop-single-2.php

where you want them to appear.

This is described in the ACF docs:
http://www.advancedcustomfields.com/resources/displaying-custom-field-values-in-your-theme/

• This reply was modified 10 years by simchris.

If you’re using a caching plugin, if using a hosting service which provides caching built-in (e.g., some WordPress hosting services), if using a CDN you have to “refresh” the CDN to get the new theme files.

Might not be your specific issue, but it’s working here on our site(s).

(I don’t work here, just some friendly feedback – sorry if it is not helping!) 🙂