Also, an email was sent last week saying there was update to Newspaper. If you don’t have this email turned on, you can do so from the downloads menu for your TF account.
You can download the recent update from your Themeforest account for Newsapaper “all files”, and inside the Newspaper-tf folder (after download to your PC), you will see a plugins folder; inside that will be the updated and secured version of js-composer you need to upload over/replace the older one on your web server.
Due to all the security changes this year in WP, which are ongoing (Akismet identified this week as major security issue, allowing commenters to hack your site!), the best plan is this:
a) make changes to the core theme files (not child theme)
b) keep track of changes made, files, line number, code snippets changed where
c) to update, download new theme version, apply your mods to same files, replace old theme folder with the new version with your replicated mods;
d) if something fails, go back to the backup
Not much TagDiv or anybody can do about ongoing security patches to the Visual Composer plugin — TagDiv doesn’t make that, nor do the theme devs around the world bundling that as groovy cool way to do page layouts.
Sadly, WordPress and all the pieces which fit together have been going through major upheaval this year — and it’s good for security, but seriously you have to get annoyed when the anti-spam tool causes your site to be hacked from comments containing “emojis” which you can’t disable in WP without adding code to the functions.php file. Sheesh.
Anyway– just some feedback. Wasn’t trying to annoy or shoot you down, just some feedback that it’s not just you; WP has been a pain in the arse this year.
I’m counting something like 100+ updates since Spring on some of our sites for WP, Akismet, Yoast, Visual Composer, etc., due to security vulnerabilities. Wild.
🙂
I usually have to hack couple things for header, author template (remove comment count), 404 template, remove remote loading google fonts, add some stuff to functions.php, and minify the CSS, and make one change the default hit counter field to match our pre-existing field name “views” — so not too hideous; most of the rest is done with CSS.
In our case, just safer to get update, make mods to update work folder; then upload that to replace old version; check all works; if not roll back.
Fairly safe way to live without “hoping” updates will work (color me paranoid!) 🙂
Hmmm…. stuff shouldn’t just “disappear” unless you have a server issue where it’s timing out loading images; CDN issues, caching issue, or not enough memory for WP.
possible issues:
If you’re using a CDN, you need to set that up properly.
If you’re using local site caching, try clearing cache.
Also, perhaps try increasing default memory in the wp-config.php file from the default 40MB to 96MB, or 128MB if your host allows that.
Try disabling the lazy load option in the theme settings; this doesn’t seem to work well with some servers/browsers.
That isn’t managed by the theme, but you can Google how to modify the tag widget from WordPress; however, in my experience most people instead use one of the BETTER tag widgets found on wordpress.org — the better ones allow you to set limits, change “styles” and even font sizes without hacking the default one via your functions.php file.
see
https://wordpress.org/plugins/search.php?q=tag+widget&=Search+Plugins
example
https://wordpress.org/plugins/ultimate-tag-cloud-widget/
Hope that helped 🙂
Unless the images are included in the new dbase they won’t be seen in the media manager which is part of wordpress and not the theme.
SO, check your dbase to see if the images are actually in the dbase for the media manager or not; depending on how you “imported” your data they might not actually be there — so it looks like the new version of WP didn’t “upload and register” them.
REF
https://wordpress.org/support/topic/media-library-rebuild-after-site-move
https://wordpress.org/plugins/add-from-server/
just as general tip, you can often Google these kinds of things to quickly find answer, as I just did, without waiting for support here, for general WordPress issues — after 10 years, there is a LOT of “help!” info for WP online. For example, I just did search for “force wordpress to refresh media manager” … and found the above info for you 🙂
Hope that helps!
In future you may find the DUPLICATOR plugin is the best way to MOVE a WP site to another server or domain name. I had to do this recently, worked flawlessly 🙂
Sorry to butt in, but in my experience this is exactly why I don’t use child themes as they may change over time with major updates and kind of defeats the purpose.
You might consider modifying the “main” theme for customizations, and simply keep track of the files/folder and ‘snippets’ (e.g., line xxx, block of code) in text files, so you can replicate that after an update.
This is what I do, and proves more “consistent” and limits site failure and debugging due to the main/child being out of sync.
With all the functional changes to WP of the past year, this has proven to be even more true.
Sorry, editorial over 🙂
Best way is to use FTP, and first unzip the main ‘tf’ folder which has the additional stuff; find the theme zip, unzip it, then upload the entire “Newsmag” folder (NOT the ‘tf’ zip or folder!!), to your /wp-content/themes/ folder.
See the step by step instructions right side for the theme.
Hope that helped.
YOAST SEO does the OG tags automatically if you switch the option on from the Yoast SEO settings … go through every tab and every panel in the Yoast SEO and make sure you look at the “social” settings.
http://www.wpbeginner.com/plugins/how-to-install-and-setup-wordpress-seo-plugin-by-yoast/
Be sure to use the version of VC included with theme download this past week with security fix, and *not* the one Envato offered folks to download, which is not fully compatible with theme.
Might not be your issue, but seems to be mucking a number of things up with the Envato version.
Yes, there must be OG (open graph) tags in the META data in the head of the HTML. You can check this manually by doing “view source” in any modern web browser to SEE what is actually on the live page. FB must have an OG image tag to work properly.
I think what I did was add a CSS to add padding to the top of the div where the ad is loaded. I don’t have the CSS handy for that, but TagDiv can provide if you don’t know how to sort that on your own using something like the Chrome/Console to see the div class for the ad block in header.
I use “thumbnail upscale” which works for me … but make sure you have the GD library active on your hosting setup (and/or Imagemagick). Also make sure you consider increasing default memory for WP in the wp-config.php file if you had not already done so.
Use a SMTP plugin for WP where your plugin logins in as user to your @domainname email user, and sends as a user.
check to see if the images are still there in folder via FTP or not;
check to see if you exceeded your hosting storage space;
clear all caching;
if using a CDN, ensure the CDN is not “down” or timing out — and/or you didn’t exceed storage allocation.
Those would be best places to start.
As an fyi, those look like category numbers and post ID numbers, hence the
yoursite/123/1234
yoursite/[catid]/[postid]
where first numbers might be category ID, and second number would be post ID.
So, if your permalinks had been set that way, or if you are using nay kind of sharing tool which used/uses the IDs as some kind of shortcodes, that is how you’d end up with those URLs.
Or, if you had the permalinks set that way somehow for any period of time.
The theme does not change your permalink structure or generate those kinds of URLs.
Just some anecdotal info on what those URLS “mean” structurally. 🙂
(Apologies for any upset: I do NOT work here, nor do I represent TagDiv in any way, who do provide some of the best support in the WP community!)
awesome sauce 🙂
That is typically from using high ASCII characters in your story names which don’t translate to English web URLs. So you have an advanced language and most web servers have to swap out UTF-8 friendly characters for the web, search, social, etc.
I don’t know if there is solution for that or not — not theme related, of course.
Might need to Google “international language permalinks in WordPress” or something like that …
this may or may not help:
http://wordpress.stackexchange.com/questions/51498/wordpress-slug-issue-with-non-latin-characters
This is common issue if you installed the “demo content” then later went back and deleted it after Google had indexed all those pages. Might not be your issue, but that happens quite a bit 🙂
How to view your page source:
https://blog.kissmetrics.com/how-to-read-source-code/
Hm. Just for laughs, try disabling the “lazy loading” option, and then clear any/all caching you have.
@pawsandwhiskars
great. I will endeavor to NEVER try to help you again, since you seem unable to help yourself.
Let TagDiv “try” to explain how HTML works to you. Good luck.
Sorry you are having so many problems with your unique setup.
So long and thanks for all the fish.