a) make sure you update VC plugin properly by
— delete old folder in /plugins/
— upload NEW updated js-composer plugin folder via FTP into your plugins folder
b) log-in to your theme
c) clear web browser cache completely
d) clear transients with wp-optimze
e) launch visual composer
f) if your page shows [code] try preview then ‘save’ without making changes
g) read up on changes to Visual Composer in case *they* decided to deprecate/retire some feature, which no longer works and will leave an empty space or reveal dead shortcode — only option is to remove old dead shortcode, and rebuilt that element
and it goes without saying you should ALREADY have increased your default memory for WP to 96MB or more in your wp-config.php file to even use VC at all!
VC is nice to have drag and drop, but it’s a tricky little bastard… er … little fellow.
If you get white screen of death, that’s a whole ‘nuther story.
Good luck!
a) make sure you update VC plugin properly by
— delete old folder in /plugins/
— upload NEW updated js-composer plugin folder via FTP into your plugins folder
b) log-in to your theme
c) clear web browser cache completely
d) clear transients with wp-optimze
e) launch visual composer
f) if your page shows [code] try preview then ‘save’ without making changes
g) read up on changes to Visual Composer in case *they* decided to deprecate/retire some feature, which no longer works and will leave an empty space or reveal dead shortcode — only option is to remove old dead shortcode, and rebuilt that element
and it goes without saying you should ALREADY have increased your default memory for WP to 96MB or more in your wp-config.php file to even use VC at all!
VC is nice to have drag and drop, but it’s a tricky little bastard… er … little fellow.
If you get white screen of death, that’s a whole ‘nuther story.
Good luck!
a) make sure you update VC plugin properly by
— delete old folder in /plugins/
— upload NEW updated js-composer plugin folder via FTP into your plugins folder
b) log-in to your theme
c) clear web browser cache completely
d) clear transients with wp-optimze
e) launch visual composer
f) if your page shows [code] try preview then ‘save’ without making changes
g) read up on changes to Visual Composer in case *they* decided to deprecate/retire some feature, which no longer works and will leave an empty space or reveal dead shortcode — only option is to remove old dead shortcode, and rebuilt that element
and it goes without saying you should ALREADY have increased your default memory for WP to 96MB or more in your wp-config.php file to even use VC at all!
VC is nice to have drag and drop, but it’s a tricky little bastard… er … little fellow.
If you get white screen of death, that’s a whole ‘nuther story.
Good luck!
Well, they did that previously, I think back with Newspaper 4. But, NP keeps evolving since it’s one of the more popular themes out there — so, NP7 very different from NP4. Usually looking closely at the demos of both themes on themeforest with two tabs open in browser for desktop set to “wide” and then something like an iPad are good ways to compare. Differences in layout, modules, navbar, footers, category/archive pages, fonts/sizes, “preset templates” are different, etc.
Newspaper is the flagship, Newsmag is the alternate take.
a) try clearing cache on site if using one; reset update CDN if using one
b) clear cache in your web browser
c) clear transients using wp-optimize
d) make sure you have enough memory allocated to WordPress via the wp-config.php file
Closing </body> will generally be at end of the footer.php file.
e.g.,
<?php wp_footer(); ?>
</body>
</html>
===
REF – BASIC HTML INFO:
Definition and Usage
The <body> tag defines the document’s body.
The <body> element contains all the contents of an HTML document, such as text, hyperlinks, images, tables, lists, etc.
Example
A simple HTML document, with the minimum of required tags:
<html>
<head>
<title>Title of the document</title>
</head>
<body>
The content of the document......
</body>
</html>
They are usually listed in the changelog files found in the “all files” download from themeforest. Not always, but most of the time. This is usually for dot update, not “full version” changes like Newspaper going from 6 to 7 where it might be whole new theme so not applicable for listing changed files since they ALL changed.
One is more narrow and one is wider (e.g., Newspaper is “wider”, more like a newspaper); NewsMag is more narrow like a news magazine.
Look in either the header.php or footer.php files.
Ccberke..
That error is your site trying to connect to wordpress, possibly with jetpack, and it failing. Theme does not control jetpack.
See theme docs. You need to activate the ajax counter when using cache.
The new version of the theme just came out this week, so you might try updating now?
The theme *was* updated for WP 4.5x a couple of weeks ago and has been working fine over here.
You also need to update all the included plugins with the theme, and not the theme by itself; clear your caching, reswt CDN, turn off all plugins except visual composer to make sure site works with base elements.
Not sure that helps, but that is what I went through.
Looks like you have some bad HTML in there someplace … your page scrolls about 10 feet past the end of the content, which it should not !
You also have a whole bunch of errors in your code ; use F12 in Chrome or Edge to see all the errors.
e.g.,
like.php?href=https://powersellingmom.com/ebay-seo/ebay-seo-the-ultimate-guide-seo-tools-tips-best-…:3 Blocked a frame with origin “https://www.facebook.com” from accessing a frame with origin “https://powersellingmom.com”. Protocols, domains, and ports must match.n @ like.php?href=https://powersellingmom.com/ebay-seo/ebay-seo-the-ultimate-guide-seo-tools-tips-best-…:3
jquery.js?ver=1.12.3:2 Uncaught Error: Syntax error, unrecognized expression: a[href*=#]
2content.js:2 Uncaught ReferenceError: zal is not defined
That’s usually why I try it with default WP theme on your current location; if it doesn’t work with the default WP theme, it won’t work with TagDiv theme either, regardless of whether main or child theme. SO, it’s part of debug process, to eliminate one possible culprit.
It’s not a job, it’s an adventure.
🙂
Some people do this the less elegant way:
a) add common well documented functions to remove default RSS feeds from head
b) create “custom” new RSS feed such as /sitename.cde/feed=custom using common tutorials online for “new custom RSS feed” — easily tested as working due to new URL/slug/endpoint
c) hard code the RSS link in the theme header.php file; or enqueue a new function to add the custom Feed URL to header.
Not theme specific, so that’s why you got a “canned” answer from the staff here. They don’t always have time to fix unrelated WordPress issues or do custom programming for you, since that isn’t part of the theme — hacking WordPress is not theme related, so sometimes better done elsewhere or by Google Search.
Just as FYI, for most stuff like that — in my own experience — it often does not work with child themes, which is why I personally don’t use child themes due to the various mish-mash of redirects and over-rides.
Tip for hacking WordPress:
a) start with default WP theme; add your custom function to default theme to get it to work.
b) Then when you have it working, fold it into the commercial theme.
c) If it doesn’t work in child theme, use only the primary theme. Or, make sure you’re adding the custom function in the *right place* for it to work.
Not sure that helps.
Adding an additional custom RSS feed is very easy; “replacing” the built-in RSS feed is a bit more complex, as you’ve discovered.
You can ignore that ‘nag’ thing.
You can find latest bundled version in the “all files” theme download from your themeforest account.
I guess I should always preface my comment with “works for me, but you might be using something I’m not … like Video Playlists…” 😉
I’m not here that much anymore, but again this week have been doing some pesky web server upgrades for the ImageMagick exploit and we’re hardening our FTP to only work with SFTP and not allow FTP/SSL connections anymore.
There was also a YOAST SEO update this week, too.
ANyway… you won’t see me around here much anymore, but i do pop in from time to time. Glad my past comments here helped somebody.
-
This reply was modified 10 years by
simchris.
Works for me.
Good idea to learn to keep backups of your site, and installers, so you can roll back if some update does NOT work for your site.
Yes, you should just abandon support for Safari/Windows — the issue is not with the site; it’s with Safari which Apple abandoned 4 years ago (!).
So anybody using it will be having problems with the entire internet, SSL, email, Google, Amazon, Netflix, etc.
Anybody using Safari on a PC, will likely get the message by now to switch to Chrome on Windows 7/8, or Edge on Windows 10.
It’s really totally crap and doesn’t support modern security so is an easily hacked browser via malware and bad actors on the web.
It’s a fool’s errand to try to “break your site” to work with Safari/PC as that kind of hacking might break things for everything else.
You can try to add some helper elements to your header to load in legacy code, much like you can for IE6/7.
-
This reply was modified 10 years by
simchris.
Theme works fine with https … been doing so since Nov 2014 🙂