Home>Support>Error after migrating WP

Error after migrating WP

By Larissa Castanheira, 2 months ago. Last reply by Alex S, 2 months ago.

Hi, after WP migration I had to reinstall wall of it, and restore .htaccess

So, almost everything is working fine, except the accordions in this page:

http://www.gabrielaassmar.com.br/sobre/
When I access the admin, I can see the accordion there, on page builder, but can’t edit it. There’s this message:

“The class ‘SiteOrigin_Widget_Field_Text’ could not be found. Please make sure you specified the correct field type and that the class exists.”

How can I fix it? It’s a lot of text, and the reviews of the content were only at WP. I have a backup of the content (XML file), does it help? If I upload it, other content will be affected?

Please, almost 5h doing this migration, can’t stand anymore.

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 2 months, 12 days ago Larissa Castanheira

    not “wall” but “all”, sorry.

  2. 2 months, 11 days ago Alex S Hi, I Work Here

    Hi Larissa,

    The provided error suggests the SiteOrigin Widgets Bundle plugin files are incomplete. Please navigate to WP AdminPluginsInstalled Plugins and deactivate and then delete SiteOrigin Widgets Bundle. Click Add New and search for and install the SiteOrigin Widgets Bundle.

  3. 2 months, 10 days ago Larissa Castanheira

    Thank you, Alex, now I can access the widgets and edit them. But, look this form:

    http://www.gabrielaassmar.com.br/contato/

    I already edited it again, but it still with a messy layout. What can I do?

  4. 2 months, 10 days ago Larissa Castanheira

    And also the accordion still doesn’t work. I cleaned the cache, set up another accordion (with the same information), and when I open the page, it’s not working.

    http://www.gabrielaassmar.com.br/sobre/

    So weird..

  5. 2 months, 10 days ago Larissa Castanheira

    I have a backup from UpdraftPlus. Is that helpful for this issue?

  6. 2 months, 10 days ago Alex S Hi, I Work Here

    Hi Larissa,

    Preface: If you need help with doing this, I would reach out to your hosting provider for assistance with this.

    Thank you for the links. Those widgets are displaying incorrectly due to missing widget CSS which is normally generated on load and stored. This issue is likely caused by incorrect permissions of the siteorigin-widgets css directory. Please FTP into your website and navigate to WordPress directory. Go to wp-content/uploads and ensure siteorigin-widgets is set to 0750 and the contents of the files are set to 0640. If there are no files present, that’s okay!

    Once you’ve adjusted the directory permissions please view one of the pages you linked too and clear any cache plugins. Does that help?

  7. 2 months, 7 days ago Larissa Castanheira

    Ok… the folder had 755 permission, so I changed to 750, but there was no files inside. Is that normal?

    So I after this changing, I tryied to put the contact form back, and still with error… I can edit on page builder, but the form is messed on page, not responding to the design config I set.

    I set up a test page for the form: http://www.gabrielaassmar.com.br/form-test/

    I send an e-mail, and nothing… before the migration it was working fine. Your plugin is the best! I already tried another, but none of them is good enough.

    Hoping can fix this. Already re-installed the WP… and also uploaded the plugins files directly from http://ftp...

  8. 2 months, 7 days ago Larissa Castanheira

    UPDATE: I got the test mail, it was in spam trash. So there’s just two things to adjust:

    – design of the form

    – how the mail arrive on main box (or at least on promotion or updates box) and not in spam.

  9. 2 months, 7 days ago Alex S Hi, I Work Here

    Hi Larissa,

    Thanks. Can you please check the permissions of wp-uploads directory. I ask as another plugin you have installed (useanyfont) is having issues storing its stylesheet. Does everything work when you navigate to WP AdminMedia?

    – how the mail arrive on main box (or at least on promotion or updates box) and not in spam.

    I would reach out to your hosting provider about this. You’ll likely need to set up SMTP mail rather than relying on your hosting provider’s mail server as it’s possible they may have been blacklisted due to spam – this is quite common with things like DigitalOcean.

  10. 2 months, 7 days ago Larissa Castanheira

    Thank you, Alex.

    wp-uploads – 755 (i’m afrid to change and than have errors in another things that is already working)

    useanyfont – it’s working fine, I set up only one font, that is needed.

    wp-admin –> media – the navigation is fine too. the url is “wp-admin/upload.php” and opens my library.

    About the mail box, I was doing some research, and have to relate this to GoDaddy, but thanks!

    So about the layout of the form, using widgets, is there any CSS that I can set up to test? Any class maybe?

    I really want to understand what is happening, and never do the same mistake again!

    I always use vantage theme with your native plugins.

  11. 2 months, 7 days ago Alex S Hi, I Work Here

    Hi Larissa,

    useanyfont – it’s working fine, I set up only one font, that is needed.

    That’s odd. It’s reporting an error for me:

    Can you please try changing one of the Contact Design settings in the Contact Form on the linked page?

  12. 2 months, 7 days ago Larissa Castanheira

    But I’m not using the “site” directory anymore, I moved the WP to the root… If you type this adress with the “woff” file, it will start a download.

    Whats is really odd… I moved WP from the “site” directory to root… and then deleted all “site” folder.

    But it keeps showing up, and I deleted it several times, it returns, and now exactly with the path “wp-content/uploads/siteorigin-widgets” and the files is

    – sow-button-flat-52cac46ddfee.css

    – sow-button-wire-01ac1ee7eb74.css

    – sow-button-wire-c773971cba49.css

    – sow-contact-form-default-812cdfdcf4d4.css

    – sow-image-default-31c423e8ff7c.css

    – sow-image-default-fae83571bfaa.css

    Should I copy these files to folder in root directory?

  13. 2 months, 7 days ago Alex S Hi, I Work Here

    Hi Larissa,

    Your website still thinks it’s meant to be in the site directory. Please navigate to WP Admin > Settings > General and ensure there are no references to the site directory.

  14. 2 months, 7 days ago Larissa Castanheira

    Alex, I verified, but there’s no reference.

    I’ll try uninstalling some other plugins. Maybe another one is making this conflict.

  15. 2 months, 7 days ago Alex S Hi, I Work Here

    Hi Larissa,

    Hm. Do you have a custom UPLOADS configuration value in your wp-config.php?

  16. 2 months, 6 days ago Larissa Castanheira

    No, I always leave it by deault…

    Its better to copy wp-config here (hiding some key information)

    <?php
    /**
     * The base configuration for WordPress
     *
     * The wp-config.php creation script uses this file during the
     * installation. You don't have to use the web site, you can
     * copy this file to "wp-config.php" and fill in the values.
     *
     * This file contains the following configurations:
     *
     * * MySQL settings
     * * Secret keys
     * * Database table prefix
     * * ABSPATH
     *
     * @link https://codex.wordpress.org/Editing_wp-config.php
     *
     * @package WordPress
     */
    
    // ** MySQL settings - You can get this info from your web host ** //
    /** The name of the database for WordPress */
    define('DB_NAME', 'HIDE');
    
    /** MySQL database username */
    define('DB_USER', 'HIDE');
    
    /** MySQL database password */
    define('DB_PASSWORD', 'HIDE');
    
    /** MySQL hostname */
    define('DB_HOST', 'localhost');
    
    /** Database Charset to use in creating database tables. */
    define('DB_CHARSET', 'utf8');
    
    /** The Database Collate type. Don't change this if in doubt. */
    define('DB_COLLATE', '');
    
    /**#@+
     * Authentication Unique Keys and Salts.
     *
     * Change these to different unique phrases!
     * You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
     * You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
     *
     * @since 2.6.0
     */
    define('AUTH_KEY',         'HIDE');
    define('SECURE_AUTH_KEY',  'HIDE');
    define('LOGGED_IN_KEY',    'HIDE');
    define('NONCE_KEY',        'HIDE');
    define('AUTH_SALT',        'HIDE');
    define('SECURE_AUTH_SALT', 'HIDE');
    define('LOGGED_IN_SALT',   'HIDE');
    define('NONCE_SALT',       'HIDE');
    
    /**
     * Other customizations.
     */
    define('FS_METHOD','direct');define('FS_CHMOD_DIR',0755);define('FS_CHMOD_FILE',0644);
    define('WP_TEMP_DIR',dirname(__FILE__).'/wp-content/uploads');
    
    /**
     * Turn off automatic updates since these are managed upstream.
     */
    define('AUTOMATIC_UPDATER_DISABLED', true);
    
    
    /**#@-*/
    
    /**
     * WordPress Database Table prefix.
     *
     * You can have multiple installations in one database if you give each
     * a unique prefix. Only numbers, letters, and underscores please!
     */
    $table_prefix  = 'wp_';
    
    /**
     * For developers: WordPress debugging mode.
     *
     * Change this to true to enable the display of notices during development.
     * It is strongly recommended that plugin and theme developers use WP_DEBUG
     * in their development environments.
     *
     * For information on other constants that can be used for debugging,
     * visit the Codex.
     *
     * @link https://codex.wordpress.org/Debugging_in_WordPress
     */
    define( 'WP_DEBUG', false );
    
    /* Multisite */
    define( 'WP_ALLOW_MULTISITE', true );
    
    /* That's all, stop editing! Happy blogging. */
    
    /** Absolute path to the WordPress directory. */
    if ( !defined('ABSPATH') )
    	define('ABSPATH', dirname(__FILE__) . '/');
    
    /** Sets up WordPress vars and included files. */
    require_once(ABSPATH . 'wp-settings.php');

    Is there anything missing? Or wrong?

  17. 2 months, 4 days ago Alex S Hi, I Work Here

    Hi Larissa,

    Thanks. Can you please clarify the path of that file? Is the WordPress index.php in the same path?

    We’re not too sure why this is happening, I would consider reaching out to WordPress directly about this issue as they’ll likely know why your website is still (internally) referencing your old path.

Please log in to post on our forums. Signing up is free.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More