March 11, 2020 at 4:45 pm #1192345
I am unable to open the Fullwidth Easy Slider element when I place it on my page. I can’t open an existing one or a new one.
This is the error I get:
An error occured
Error fetching content – please reload the page and try again
Any help would be greatly apprecited!
AshleyMarch 12, 2020 at 5:10 am #1192486
Thanks for the login details. I can’t see which version of the theme you are running since it has been changed. Could you make sure that you are running the latest version of the theme (4.7.3) please? https://kriesi.at/documentation/enfold/how-to-install-enfold-theme/#theme-update
RikardMarch 20, 2020 at 12:22 am #1194636
To give you some background, this site was built by someone else who no longer maintains it and now that is my job. I did some extensive digging and like you, I can’t for the life of me find any file in which they did not modify the version number to their own. That being said, I know it’s not and can’t update to the latest because of the amount of customization they did directly in the theme. I am currently going through file by file and trying to make a list of what they changed and properly move it to a child theme.
I was wondering, the last known modifications of the site happened around 10/4/18. Would you guys have an old version around that time that I can get access to so I can see exactly what files are original to the theme and not modified since the current version has so many updates it’s a little harder?
Thanks in advance for any help and feel free to add any advice if you have a may to easily (or easier) to check which files have been modified.
Thanks again for all your help.
AshleyMarch 20, 2020 at 6:33 am #1194729
Thanks for the update, I feel your pain. Is the date you mentioned October 4 or April 10?
RikardMarch 20, 2020 at 4:26 pm #1194813March 21, 2020 at 5:03 am #1195002
Please see private, that version was release on June 4 2018.
RikardMarch 21, 2020 at 4:54 pm #1195099
Thanks Rikard. I am going to see if I can go file by file and figure out everything that was changed and put it in a functions file or css file and see if I can update the main theme and hopefully not blow up the site. Wish me luck! :)March 21, 2020 at 5:13 pm #1195102
While comparing file I found a txt file with this:
– update layerslider.php file:
$GLOBALS[‘lsAutoUpdateBox’] = false;
define(‘LS_ROOT_URL’, get_template_directory_uri() . ‘/config-layerslider/LayerSlider’ );
– copy both sample folders to new layerslider folder
– remove all skins but “fullwidth” and “noskin” and “preview” from the new layerslider static/skins folder
I am guessing because of whatever they did is why the layerslider isn’t working now.
This project is definitely a headache. Thanks for the past version.March 21, 2020 at 5:37 pm #1195107
I also think I found the version they were working with. I found this in the framework file:
* AVIA Framework
* A flexible WordPress Framework, created by Kriesi
* This file includes the superobject class and loads the parameters neccessary for the backend pages.
* A new $avia superobject is then created that holds all data necessary for either front or backend, depending what page you are browsing
* @author Christian “Kriesi” Budschedl
* @copyright Copyright (c) Christian Budschedl
* @link http://kriesi.at
* @link http://aviathemes.com
* @since Version 1.0
* @package AviaFramework
* @version 1.9.1
define( ‘AV_FRAMEWORK_VERSION’, “2” );
* Action for plugins and functions that should be executed before any of the framework loads
do_action( ‘avia_action_before_framework_init’ );
* Config File
* Load the autoconfig file that will set some
* constants based on the installation type (plugin or theme)
require( ‘php/inc-autoconfig.php’ );
* Superobject Class
* Load the super object class, but only if it hasn’t been
* already loaded by an avia plugin with newer version
if( ! defined(‘AVIA_PLUGIN_FW’) || ! defined(‘AVIA_THEME_FW’) || ( version_compare(AVIA_THEME_FW, AVIA_PLUGIN_FW, ‘>=’) ) )
require( AVIA_PHP.’class-superobject.php’ );
* Include Backend default Function set
* Loads the autoincluder function to be able to retrieve the
* predefined page options and to be able to include
* files based on option arrays
require( AVIA_PHP.’function-set-avia-backend.php’ );
* Load the options array with manually passed functions
* in functions.php for theme or plugin specific scripts
if(isset($avia_autoload) && is_array($avia_autoload)) avia_backend_load_scripts_by_option($avia_autoload);
* Filter the base data array that is passed
* upon creation of the superobject
$avia_base_data = apply_filters( ‘avia_filter_base_data’, $avia_base_data );
* create a new superobject, pass the options name that
* should be used to save and retrieve database entries
$avia = new avia_superobject($avia_base_data);
Do you think it is possible they are really running version @version 1.9.1?
Thanks!March 30, 2020 at 4:49 am #1198996
That is actually the framework version, which is different from the actual theme version. The latest framework version is 4.6, which means that the one you’re working with is pretty old.
Using software or online tools that can compare files and directories should help.
You must be logged in to reply to this topic.