Tagged: 

Viewing 28 posts - 1 through 28 (of 28 total)
  • Author
    Posts
  • November 29, 2018 at 11:02 am #1038882
    Klaasbaas1983

    Dear Enfold devs,

    After I upgraded Enfold to v4.5 I receive the following error when I try to login to the backend:

    Fatal error: Uncaught Error: Class 'AviaTypeFonts' not found in /home/vhosts/cityshine.org/httpdocs/new/wp-content/themes/enfold/framework/php/class-superobject.php:182 Stack trace: #0 /home/vhosts/cityshine.org/httpdocs/new/wp-content/themes/enfold/includes/admin/register-backend-advanced-styles.php(23): avia_superobject->type_fonts() #1 /home/vhosts/cityshine.org/httpdocs/new/wp-content/themes/enfold/includes/admin/register-admin-options.php(55): include('/home/vhosts/ci...') #2 /home/vhosts/cityshine.org/httpdocs/new/wp-content/themes/enfold/framework/php/class-superobject.php(198): include('/home/vhosts/ci...') #3 /home/vhosts/cityshine.org/httpdocs/new/wp-content/themes/enfold/framework/php/class-superobject.php(146): avia_superobject->_create_option_arrays() #4 /home/vhosts/cityshine.org/httpdocs/new/framework/avia_framework.php(97): avia_superobject->init() #5 /home/vhosts/cityshine.org/httpdocs/new/wp-content/themes/enfold/functions.php(143): require_once('/home/vhosts/ci...') #6 /home/vhosts/cityshine.org/httpdoc in /home/vhosts/cityshine.org/httpdocs/new/wp-content/themes/enfold/framework/php/class-superobject.php on line 182

    Can you please help me identify what I can do to fix this?
    If you need login creds, please let me know.
    Btw, the frontend is working fine, so no impact on the website itself.

    WP: 4.9.8
    Enfold: 4.5
    PHP: 7.1.23

    Thanks in advance for your support!

    Regards,
    Jeroen

    • This topic was modified 6 years ago by Klaasbaas1983. Reason: added versions of WP, Enfold & PHP
    December 1, 2018 at 10:20 am #1039579
    Rikard

    Hey Klaasbaas1983,

    Please send us a temporary admin login and login URL so that we can have a closer look. You can post the details in the Private Content section of your reply.

    Best regards,
    Rikard

    December 1, 2018 at 11:03 am #1039619
    Klaasbaas1983

    Thanks so much for your response!
    Creds are in the private content section.

    Please let me know if you need anything else!

    December 2, 2018 at 9:43 am #1039846
    Rikard

    Hi,

    Thanks for that, though I can’t login because of the error message. Did you add any customisations at all to the theme? Would you be able to restore the site back to an earlier point? Then you could update a staging version of the site instead, so that you won’t have any problems with your live site.

    Best regards,
    Rikard

    December 2, 2018 at 10:58 pm #1040054
    Klaasbaas1983

    Hi Rikard,

    I’ve made no real adjustments to the theme except for some fixes that were advised by the mods/devs to make the errors go away (known bugs) moving to 4.5. I’ve actually just uploaded all the 4.5 files again to make sure that, if I made any changes, they’d be gone now. However, I still get the same error. :(

    I have a backup (4.2) from before I upgraded to 4.5 so I’ll try to restore from that, but only as a last resort since I’m afraid my site will break including the frontend. Not really sure what you mean about the whole staging/live part?

    Thanks again for looking into this issue!

    FTP creds are in the private section in case you need that.

    • This reply was modified 6 years ago by Klaasbaas1983. Reason: added FTP creds
    December 4, 2018 at 7:15 pm #1040855
    Nikko

    Hi Klaasbaas1983,

    It would be hard to try to find the issue without affecting the frontend, the only thing we can recommend is to create a staging site (basically a clone of your live site, placed in your subdomain)
    You can check on this post regarding it: https://themeisle.com/blog/wordpress-staging-site/
    This way we can try to troubleshoot it without affecting your live site.

    Best regards,
    Nikko

    December 6, 2018 at 1:12 pm #1041628
    Klaasbaas1983

    Hi Nikko,

    Thanks for looking into it.

    In the meanwhile, I’ve tried falling back to 4.2 without any results.
    I just received a notification for 4.5.1 so was hoping this would fix the issue, it didn’t.

    With FTP, I changed the name of the enfold theme so I could access the backend again and update some plugins, etc.

    I will work on the staging site and get back to you as soon as possible.

    Thanks again for helping me out with this!

    Regards,

    Jeroen

    December 6, 2018 at 2:22 pm #1041662
    Klaasbaas1983

    Hi Nikko, Rikard,

    I’ve just set up the staging website (in private section).
    The thing is, I can log in to the backend of the staging website now, but still not to the backend of my live website.
    Wondering how this is possible since the staging website is just a clone of the live website?

    Any suggestion/help is welcome.

    Thanks!

    December 10, 2018 at 4:19 pm #1043132
    Nikko

    Hi Jeroen,

    I apologize for the late response, maybe it’s the caching that causes the error and prevents access on the live site.

    Best regards,
    Nikko

    December 13, 2018 at 1:08 pm #1044872
    Klaasbaas1983

    Hi Nikko,

    Just turned off caching (WP Super Cache) and didn’t work either.

    What might be worth mentioning is that I can access my backend as long as I’m logged in (after switching to a different theme first).
    As soon as I open a new session on a different browser or if I’m logged out I receive the class-superobject.php error.

    Did you or your devs by chance had a look at the lines from the error in class-superobject.php?

    Thanks.

    December 15, 2018 at 5:09 pm #1045673
    Nikko

    Hi Klaasbaas1983,

    Did you turn off the caching in the staging?
    What I meant is the caching in the live site.
    You’ll see it in wp-config.php:

    define('WP_CACHE', true);
define( 'WPCACHEHOME', '/home/path_to_your_wp_folder/wp-content/plugins/wp-super-cache/' );

    (I’ve renamed the path).
    As for the superobject file, yes it was checked and it was this line:

    $this->type_fonts = new AviaTypeFonts();

    which is weird, since that class is properly defined in enfold > framework > php > font-management > class-avia-type-fonts.php
    Also there is no similar issues that you’re experiencing.

    Best regards,
    Nikko

    December 18, 2018 at 1:25 pm #1046843
    Klaasbaas1983

    Hi Nikko,

    Yes, I’ve turned it off for the live site (not installed in staging), but I am still receiving the same error accessing the backend.

    December 20, 2018 at 12:43 am #1047499
    Nikko

    Hi Klaasbaas1983,

    Did you turn it off in the wp-config file?
    Can you try put wp-super-cache plugin to the root folder and those cache files and folder in the wp-content folder?
    I compared the difference between the live site you have and the stage site are those cached files.

    Best regards,
    Nikko

    January 8, 2019 at 9:44 pm #1051503
    Klaasbaas1983

    Hi Nikko,

    Apologies for the late response. I was on vacation and had no time to work on this issue.

    I’m not sure what you mean by putting the plugin in the root folder and the folder in the wp-content folder.

    Could you please explain what you mean by that?

    Thank you.

    January 9, 2019 at 9:56 am #1051674
    Nikko

    Hi Klaasbaas1983,

    With root folder what I meant was the directory in which the wp-config.php file is placed, you just need to move the wp-super-cache plugin’s folder (which is located in the plugins folder).
    Maybe to make it much simpler, in the root folder, create a folder and name it cache_backup then all the files and folders I mentioned place it there, to make sure that the pages on your site isn’t cached since I noticed that the live site is just showing a cached version of your site. Actually when I compared your live and stage site the difference only is the caching, for some reason caching is still running on your live site.

    Best regards,
    Nikko

    January 13, 2019 at 5:14 pm #1053384
    Klaasbaas1983

    Hi Nikko,

    Thanks for taking the time to explain it to me, but I’m a still a bit confused on what to do.
    How I understand it what I should do:

    – define(‘WP_CACHE’, true); >>>> should be set to define(‘WP_CACHE’, false);
    – Move ../wp-content/plugins/wp-super-cache to root directory (same as wp-config.php)
    – Move ../wp-content/cache (all files?) to root directory in a new directory called cache_backup

    Is caching causing an issue logging in to the backend?

    Thanks again for your help!

    Regards,

    Jeroen

    January 16, 2019 at 8:32 pm #1054705
    Basilis

    Hi,

    Yes that can be an issue, but if there is a conflict also with server that can be an issue.
    If u provide us with FTP details we might look deeper into it.

    Best regards,
    Basilis

    January 17, 2019 at 1:53 pm #1054990
    Klaasbaas1983
    This reply has been marked as private.
    January 22, 2019 at 1:06 am #1056952
    Basilis

    Hi,

    Can I delete the cache file on wp-content file?
    It seems that u had an other plugin around.

    Best regards,
    Basilis

    January 22, 2019 at 10:19 am #1057126
    Klaasbaas1983

    Hi Basilis,

    Yes, go ahead. I can always cache all these files later and shouldn’t have any impact on the website itself.

    Thank you!

    Jeroen

    January 30, 2019 at 9:38 pm #1060608
    Klaasbaas1983

    Hi Basilis,

    Any luck on your end?
    Anything else you need from me?

    Thank you

    February 6, 2019 at 11:38 am #1063562
    Ismael

    Hi,

    I’m very sorry for the late response.

    I would like to help you with this but I’ll need the necessary login details for both the live and the staging site. Please post the WP and FTP details for both sites in the private fields.

    Best regards,
    Ismael

    February 7, 2019 at 2:52 pm #1064148
    Klaasbaas1983

    Hi Ismael,

    Login creds are in the private content section.

    For the live site, there’s a 2FA set up. Please let me know if I need to disable this.

    If you have anything I can do to help, please let me know.

    Regards,

    Jeroen

    February 11, 2019 at 8:14 am #1065342
    Ismael

    Hi,

    Thanks for the info.

    I managed to access your file server but I’m not sure which directory to check. I get in to the “httpdocs” folder but the WP files are incomplete. All I can see is the “wp-content” folder without the config files or anything.

    Best regards,
    Ismael

    February 11, 2019 at 3:48 pm #1065465
    Klaasbaas1983

    Hi Ismael,

    Please go to httpdocs/new as my website is hosted there.

    Thanks again!

    Jeroen

    February 12, 2019 at 12:33 pm #1065925
    Ismael

    Hi,

    Thanks for the update. I checked that folder and found the theme files in the root directory. It should be inside the wp-content > themes folder. Did you upload it there? Please clean up the root directory of the “new” installation.

    Best regards,
    Ismael

    February 13, 2019 at 1:52 pm #1066484
    Klaasbaas1983

    Awesome! Thank you for that! Such a stupid mistake on my side.
    Must’ve been dragging & dropping on the wrong location when I tried to upgrade my theme last year.

    All is working fine when I moved those directories out to a temp location.

    Thanks again! Case can be closed :)

    February 14, 2019 at 2:08 am #1066721
    Nikko

    Hi Klaasbaas1983,

    Glad that we could help :)
    Thanks for using Enfold and have a great day!

    Best regards,
    Nikko

  • Author
    Posts
Viewing 28 posts - 1 through 28 (of 28 total)
  • The topic ‘Error message on wp-admin after upgrade to Enfold 4.5’ is closed to new replies.