You may not have installed it properly, or issue with conflict with other plugin, caching issue, transients issue, etc.
You may want to start a new topic for “VC not working” which has nothing whatsoever to do with the annoying activation nag screen.
To “activate” the plugin to work with theme, you simply need to turn it on from the plugins panel in WP, and make sure you are logged in as admin.
(( I don’t work here. ))
How are you measuring that exactly?
Note Google has been changing algorithms for the new year to enable /AMP/ priority in mobile serps, mobile friendly priority, page speed priority, https priority for mobile, etc.
You may notice reads go down on your site if not optimized for speed, mobile score at 90 or above, and https vs http for mobile audience.
*** YOU DO NOT NEED to ‘activate’ the plugin with WP Bakery to use it; that is a feature they put there to get you to register for updates and support if you have a paid license.
With the bundled version, you get updates when the theme is updated. Period.
You can ignore the “nag screen to register/activate” with WP Bakery, which you cannot do, since you don’t have a paid license with the ‘bundled’ free version, which works with the theme.
Simply ignore the nag screen. 25,000 other people with the theme use it without activating it, so that should give you some measure of comfort — you do *not* need to ‘activate’ it with WP Bakery to use it. That option only applies if you paid for a separate individual license in order to activate updates and support with WP Bakery who make the plugin — since you didn’t buy a single license for the plugin, you cannot activate it for their updates/support, and have to wait for current tested version with each theme update.
The v5 version is fairly new, and does not add a gigantic number of things to the version still included.
The demos on ThemeForest are all built with the version you have, and that is the version you should use to work with the theme if you want to.
Oops. Sorry, I’m using newsmag theme.
That option should be in the post options section, as noted in the docs.
Apologies for not providing any useful answer ! (doh!!) 🙂
You can’t.
You only get latest ‘bundled’ version of the VC plugin when the theme itself is updated, not at any other point in time. Current bundled version is included with the theme in the /plugins/ folder.
Theme does not control primary category setting of a “post”; that is not part of WordPress or the theme.
Likely a plugin you’re using for that.
There is a ‘default’ category setting under WP settings > writing, I believe.
-
This reply was modified 9 years by
simchris.
1.
this is covered in the WordPress codex a bit, but
a) change name in the style.css
b) change folder name for theme
Helps to read up on how WordPress works on the official ‘codex’ on WordPress.org
All ‘posts’ have a unique ID that never changes; this helps WP redirect a story to the right page under circumstances where you change your permalink structure (which are only redirects from ID URL).
So, you can always visit a page from the story ID, regardless of “pretty permalinks” —
However, it causes no issues to have such links as they still “land” (or “resolve”) to the correct post content.
This is one of the reasons the “canonical” tag was invented; to ensure that there is one single “official” URL for your post/page which should be considered the “real one” regardless of any other link version (e.g., an /AMP/ version is also a redirect, but not canonical).
Upshot – nothing to worry about if links still work under the ?=1234 — they should and are supposed to. This is the true “permanent” link for your story regardless of what you change the slug to, the pretty permalink redirects, etc.
The pretty permalink structure is “SEO friendly,” so you’re fine. Make sure your “canonical” tag also shows that pretty permalink (name-of-post) in your meta data. That’s all you need to worry about 🙂
And, of course, the actual content is more important than the URL of the story.
-
This reply was modified 9 years by
simchris.
I’m not having that issue; but you never know 🙂
v 3.1 works with WP 4.7 just fine 🙂
Sometimes they have to update the materials on ThemeForest for license changes, fix for bundled elements, compliance with TF stuff; and when there are special promotions like when the theme was “50% off” for Black Friday recently (maybe that was Newspaper?).
I’m sure TagDiv will have better answer. But you can see the changelog on the theme page on TF to see when it was last actually updated.
Put another way; updating the TF page doesn’t mean the theme was updated.
Do clean install of plugins. Clear cache; reset transients with wp-optimize; resave permalinks.
Might be your caching setup, or your web host moved to new hardware, or system failed and they went to a backup copy of system. Always good to double check if your web host has done something.
I use FeedWordPress plugin.
Its is compatible.
You can also sign up for updates on your downloads page on TF, and you will get automatic notification the moment a new version is released.
Use FeedWordPress plugin; that’s what I do 🙂
You don’t need to do that with a responsive theme.
If you wanted to have a second version of site in a sub domain, you’d need to do separate install of WordPress, and theme in the sub-domain, then setup a browser sniffer to redirect mobile traffic to the m.site.domain.
YOu’d likely need to hire a developer to help you with that. You’d also need to use some kind of sync program to sync desktop and mobile versions of site content.
Not simple. There might be other ways of doing that, but just quick thought on how we used to do it in years past.
A complex regex rewrite setup might do that for you, but not sure.
Install it manually via ftp. Oddly when wordpress installed via server panel there can be some odd permission stuff.
What plugin are you trying to install/update ?
Just as a general follow up on this thread i started many months back prior to our dread server crash….
We did try using Facebook comments for a short time on our site, and found the amount of “make money at home…” spam was insane. FB apparently has no filtering for this repetitive spam tactic. You can see how bad this is by looking at the comments on IMDB for news items. I looked at 5 different news items the other day, and on average EVERY item had 1-3 “I made *** BIG MONEY ON BLAH *** >>> CHECK THIS LINK” kind of crap.”
We had same issue.
We actually found going back to basic simple WP comments with Akismet has been the best choice for now.
Your mileage may vary, as I like to say, but something to be aware of if you implement FB comments. Comment spam is hideous.
Make sure you setup CORS rules for fonts on your site. Google it 🙂
You might have had caching, transients, etc. “stored” in the WP settings which didn’t get cleared.
I do this when messing with turning things on/off;
when done:
a) resave permalinks
b) clear transients with WP-Optimize plugin.
Really helps!
You need to install a forum plugin.