Ben Greeley

@dblincoe Your error messages imply that your theme has some custom code that tries to use the get_field() function. This function doesn’t exist in core WordPress, so it’s provided by a 3rd-party plugin. I believe that function is provided by Advanced Custom Fields, so you’d need to download and install the plugin and ensure it’s activated.

Since you moved the site over, be sure to verify that all of the plugins and themes needed on the new site are set up the same way as the original site. Sometimes if the plugin files aren’t moved with the migration or activated they can cause these sorts of issues.

If you have further issues with that error, I’d recommend looking into support from ACF or the company that created your theme.

Cheers.

• This reply was modified 3 years, 9 months ago by Ben Greeley.

@imran_kanjoo It might be that you’re hitting some timeout or file size restrictions on your WordPress website. Your exported file is approximately 50MB, which is significant and will take a long time for WordPress to execute the import, possibly timing out on the server. You have a few options to get around this:

1) Try breaking the export into separate files. You could export each post type separately, so they are smaller chunks. If those are still large, you could export by category, date range, etc.

2) Check your maximum uploaded file size on your server settings to ensure that you can upload files as big as the exports.

3) Since it seems you have a fair amount of content to export, you may want to try other methods, such as using WP-CLI (if your hosting company gives you access) to import the file. The timeout limits will likely be much larger for running CLI scripts than on your public website.

I hope you can get the import working with one of those suggestions.

• This reply was modified 3 years, 9 months ago by Ben Greeley.

@saranrock If you feel comfortable modifying your theme, you could simply remove the meta code from your theme’s functions.php file so the only meta description is the one provided by SEOPress.

The downside to this approach is any time you get a theme update, you’ll lose your custom code. Alternatively, if you want to keep the theme as-is, you could add the following code snippet in a custom plugin. What this does is it removes the action that was defined in the theme and then creates a new action where you can customize the HTML (so you have the viewport information included).

// Remove the theme hook
remove_action( 'wp_head', 'qoxag_meta_des_viewport', 1 );

/* Push google analytics code in head area (modified) */
function qoxag_meta_des_viewport_new(){
    ?>
    <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=5">
    <?php
}
add_action('wp_head', 'qoxag_meta_des_viewport_new', 1);

• This reply was modified 3 years, 9 months ago by Ben Greeley.

@jordanlevi when I try using a Twitter card validator to validate one of your articles, it ends up timing out. For some reason your website (article pages especially) is very slow. I suggest seeing if there are any plugins that could be disabled that are slowing the site.

Also, Twitter has a page that gives some suggestions of things to look into when you’re troubleshooting timeout errors: https://developer.twitter.com/en/docs/twitter-for-websites/cards/guides/troubleshooting-cards

You’re right that adding some logging to help determine what’s happening is a smart move. It’s strange that the website would go down, but there wouldn’t be any errors in the error logs.

1) The first thing to check is whether logging has been enabled. Check out this page for an overview of how to enable writing errors to an error log.
2) The Apache log you mention appears to have some good information, but from the messages, it’s unclear what would have caused it. You could reach out to your hosting company and see if they can help troubleshoot the server setup or configuration.
3) If you really want to dig into what’s going on with your server and website, you could set up an account with New Relic and set your server up to report information there. It’s a paid service that provides APM monitoring, so if anything happens with your website, it will be logged there. I’ve used it on projects in the past, and it’s super-helpful.

Otherwise, if this is the only plugin that is causing the issue, I would assume there’s something specific about the plugin that’s causing it, as you surmised. It could be due to some specific server functionality that it is getting confused about, but I wouldn’t rule out the plugin causing it just yet if it’s the only plugin that causes the issue. There could very well be a runaway script or process that brings down the server.

Good luck, and I hope you’re able to get to the bottom of it soon.

@khuramonline I’m not familiar with directory plugins, but the first thing you may want to do is see if your plugin has a support forum and ask the question there since it seems specific to that question.

Your steps for troubleshooting seem to make sense to me. Caching could certainly be at play. There are various levels of caching such as the database, server and CDN, so all of those would need to be flushed. If you wanted to see if it’s the CDN, you could pass a unique querystring to your webpage, like ?cache_busting_89 which will force the CDN to load a new version of the page. Your hosting company may also have various caching layers you’d want to flush.

It’s also very possible the plugin stores data in multiple places, so make sure you’re changing the correct value since you modified the database directly. It’s possible there’s post meta (or even a custom table) from the sounds of it that stores information used for the titles.

@aliamirali89 Adding to Steven’s suggestions, it looks like in this case the plugin ‘Hustle’ is modifying the site HTML and adding a no-scroll class to the <html> tag. If you disable that plugin it should resolve your issue.

If you need support from the plugin authors, be sure to ask on the plugin’s support forum at https://wordpress.org/support/plugin/wordpress-popup/

@clubside I did some testing on some themes on my local environment, and from what I can tell the embed stylesheets should be coming in automatically once you use responsive-embeds. It may be something specific to the way your theme is set up – as a test, maybe you could switch to a default theme such as Twenty Twenty and work backwards and see if there’s something set up in those themes that implement the CSS.

From my testing, I removed all the CSS from Twenty Twenty One and the responsive embeds still worked. The only thing I noticed that made a difference (and broke the responsiveness) is when I removed body_class() from the following section in my header.php `
<body <?php body_class(); ?>>`.

Maybe try verifying that class is there and see if it makes a difference.