Hi,
If your new theme folder is named the same as your old theme folder was there should be no changes in your design.
So to correct try naming your new theme folder the same as your old one was, the old one should be named to something else.
The reason you should not just upload to the same folder is there may be a directory structure change within the theme folder, but the plugin above also works well.

Best regards,
Mike

Hi,
I updated your theme by uploading it via your cpanel file manager, it is strange that you updating to WP 5 would cause this crash.
Perhaps the update didn’t finish and some of the core files are not correct? I was able to get your front end to show, but not the backend.
I see that you are using duplicator-pro, so you could try to replace the WP core files, or replace the whole site.
Do you have a duplicator-pro backup?

Best regards,
Mike

Hi,

@info224, Thank you for your feedback

Best regards,
Mike

Hi,
Thank you for the images, if I understand correctly,
you have a custom post type and the ALB Builder is not showing for it.
I tested this on my localhost, and see that this was working for WordPress v4.9
But now not WordPress v5.0
I found that you had curly quotes in your snippet code that I corrected and now you have the portfolio fields at the bottom of your custom post type:

but you still have no ALB button, I will ask the dev team for advice.

Best regards,
Mike

Hi,
Thanks for the login, please check your page now :)

Best regards,
Mike

Hi,
I took a look at the script and found it to be small enough to include in your functions.php, and delete the js file, I believe this would be fine:

function persistent_checkboxes(){
    if ( is_page('1392') ) {
    ?>
    <script>
var PersistentCheckboxes = function(){
    var genKey, load, save, addListeners, init;

    var PAGE = window.location.href;

    genKey = function(id){
        return 'checkbox:'+ PAGE +':'+ id;
    }

    save = function(event){
        // Only inputs with an id will be saved.
        if(this.id === ""){ return; }
        localStorage.setItem(genKey(this.id), this.checked+"");
    };

    load = function(){
        jQuery('input[type="checkbox"]').each(function(i, elm){
            // Ignore checkboxes with no id.
            var key = genKey(elm.id);
            if(elm.id !== "" && key in localStorage){
                elm.checked = localStorage.getItem(key) === "true";
            }
        });
    };

    addListeners = function(){
        jQuery(document).on('change', 'input[type=checkbox]', save);
    };

    init = function(options){
        // Only supported if localStorage is available.
        if(typeof(Storage) === "undefined"){ return; }
        load();
        addListeners();
    };

    init();

    return this;
};


// Let's get this party started!
var persistentCheckboxes;
jQuery(document).ready(function(){
    persistentCheckboxes = new PersistentCheckboxes();
});
</script>
<?php
}
add_action('wp_head', 'persistent_checkboxes');

You will still want to change the page ID to the page you wish it to work on.

Best regards,
Mike

Hi,
I believe the error with contact page has to do with saving your page and reloading a couple of times, please see this sticky post
If this doesn’t help, please include a admin login in the private content area so we can take a closer look.

Best regards,
Mike

Hi,
Thanks for the login, as I took a closer look I found the your images are not the compete words, please see links in the Private Content area.
and the only images for them are very large, so they seem to be getting cropped when they are added to your tabs.
Please try uploading some smaller images for the tabs, such as 200px wide.

Best regards,
Mike

Hi,
Some user reported, that validating the token only works in incognito mode for them. One reason could be, that Envato stores cookies with login data/connection data in the browser and therefore might block requests.
Please give this a try.

Best regards,
Mike

Hi,
Glad to hear, unless there is anything else we can help with on this issue, shall we close this then?

Best regards,
Mike

Hi,
I took a look at your site and it seems to be working now, so I assume your update via ftp has solved your issue?
I couldn’t login to the backend, so if you still need help please include the admin info and the admin url.
I will assume that your ftp login is correct.

Best regards,
Mike

Hi,
I took a look at your site and see that your are using Enfold v4.4.1 with WordPress v5
Please update to Enfold v4.5.1 to use WordPress v5
Please see this sticky post.

Best regards,
Mike

Hi,
If you are using the instructions on the link above to add the script to your functions.php, then you can add the conditional statement:

if ( is_page('1392') ) {

and replace the number with your page number.
So your code would look like this:

function custom_script_name(){
if ( is_page('1392') ) {
?>
<script>
// Your script here
</script>
<?php
}
add_action('wp_head', 'custom_script_name');

If this doesn’t help, then please try including your script so we can assist further.

Best regards,
Mike

Hey KevinDuy2605,
This sounds like an error that happens when one updates via FTP and tries to overwrite the enfold folder instead of replacing the theme folder. Does this sound possible?

Please note that if you update via FTP, you will need to remove the old theme folder “enfold” first (via FTP) then upload the new “enfold” folder at /wp-content/themes/enfold/
Please don’t try to overwrite the theme folder, as this will leave old files behind and cause errors.

If this doesn’t help, please include a admin login and ftp access in the private content area so we can take a closer look.

Best regards,
Mike

Hey weddingmuseum,
I took a look at your page and found that you are getting jQuery errors from admin-amp-page-builder.js
Which is your AMP plugin.
You also have this error:

/wp-admin/admin-ajax.php:1 Failed to load resource: the server responded with a status of 404 ()

which could be a security plugin blocking access to a folder or file, or the htaccess blocking access.
Please try disabling your plugin, this this doesn’t help then ask your webhost if they see the cause in the server error log .

Best regards,
Mike