Forums › Forums › Search & Filter Pro › Upgrade from 1.4.3 to 2.1.2 – No results found
Tagged: 1.4.3, 2.1.2, no results found, upgrade
- This topic has 58 replies, 3 voices, and was last updated 8 years, 5 months ago by Trevor.
-
Anonymous(Private) June 3, 2016 at 9:39 am #47382
UPDATE.
I thought the issue was with older version so I’ve updated VC to latest one and it’s working fine now at test site: rsdasa.5notedesign.com, but still not working at main site rsdasa.com
Weird… cannot narrow it down to anything in particular.Disabled all plugins except VC, still not working.
Switched to 2015 wp theme, still same thing.I do see the following error in the Developer console:
TypeError: $template.get is not a function vc.shortcode_view<.html2element() backend.min.js:6 vc.shortcode_view<.render() backend.min.js:6 vc.visualComposerView<.addRow() backend.min.js:6 vc.visualComposerView<.addShortcode() backend.min.js:6 _() load-scripts.php:377 m() load-scripts.php:377 f() load-scripts.php:377 l.trigger() load-scripts.php:377 ListenerHelper.triggerShortcodeEvents() backend-actions.min.js:1 <anonymous> backend.min.js:6 _() load-scripts.php:377 m() load-scripts.php:377 f() load-scripts.php:377 l.trigger() load-scripts.php:377 ._onModelEvent() load-scripts.php:377 _() load-scripts.php:377 m() load-scripts.php:377 f() load-scripts.php:377 l.trigger() load-scripts.php:377 .set() load-scripts.php:377 .add() load-scripts.php:377 .create() load-scripts.php:377 vc.AddElementUIPanelBackendEditor<.createElement() backend.min.js:3 <anonymous> self-hosted:751 n.event.dispatch() load-scripts.php:3 n.event.add/r.handle() load-scripts.php:3 backend.min.js:6:16742
Trevor(Private) June 3, 2016 at 9:44 am #47384If you have the dev version of S&F, in the main menu you will have a System Status function. It would be good to see this. Also, how did you update the theme/plugins (like VC)? Did you use the WP updater or di you do it using ftp? The risk of using ftp and overwriting files is that sometimes files are left in place that are obsolete.
Anonymous(Private) June 3, 2016 at 9:55 am #47386I followed the theme instructions, asking to disabled and remove the old plugin and then via themes options install a new version of VC. As I wrote it worked just fine with test site.
I’ll try to copy files from test to live of the VC plugin and see if perhaps some files got corrupted…
Anonymous(Private) June 3, 2016 at 10:20 am #47389Yes, same server. OK, I think I found the source of the problem. Live site is using CDN, test server is not, so when I disabled CDN, the issue is gone. I guess some old files had been cached by CDN and were still sitting there in a datacenter. I think I need to purge all files from CDN files to make sure all old files are gone and then I can re-enable CDN and it should work.
What do you think?
-
AuthorPosts