aatanasov

Hi @wordmax, sorry for the delayed response.

The current refresh rate is 12 hours. The plugin relies on the fetch_feed function.

I’m planning to add an option for changing the cache duration to the next version of the plugin.

In the meantime, you can use this global WordPress filter to change the cache duration: wp_feed_cache_transient_lifetime

For example:

add_filter( 'wp_feed_cache_transient_lifetime' , function( $lifetime ) {
	return 600;
} );

The time is in seconds.

This filter will affect all feeds on the website.

Hi, you’ll need to change the arguments of the $args2 array to:

'search'         => $email,
'search_columns' => array( 'user_email' )

That way, you’ll receive the correct user.

However, if you need to fetch the data only for a single user, it is better to use the get_user_by function. For example:

$user = get_user_by( 'email', $email );

It will create a WP_User object with all the necessary information for the particular user.

Hi, you can try using the regex redirect feature of this free plugin: https://www.ads-software.com/plugins/redirection/

Basically, you’ll need to add the following redirect:

• Source URL: ^/da/artikler/*
• Target URL: https://cetinaskincare.com/artikler/

Here is an example redirect:

The Regex option should be enabled as shown in the screenshot.

I’ve tested this approach locally, and it works.

• This reply was modified 2 years, 1 month ago by aatanasov.

Hi, some custom CSS code might interface with the title field of the Block Editor.

You can inspect the title element using your browser’s developer tool (e.g. https://developer.chrome.com/docs/devtools/open/#inspect). In the styles panel, you can see if there is any CSS code that changes the color of the title.

Also, please feel free to share a screenshot of the inspected element(the styles panel). Reviewing it, we might figure out what is going on.

Based on the code you shared, it appears the website is hacked. Here is a scan report https://sitecheck.sucuri.net/results/https/www.natureplex.com/product1/ that says there is malicious code.

The website will first have to be cleaned, and then all the theme errors will need to be fixed.

Here is a helpful article regarding hacked websites: https://www.ads-software.com/support/article/faq-my-site-was-hacked/

All themes of a WordPress instance are available in the wp-content/themes folder. The folder of your active theme is natureplex.

Someone with the necessary coding skills and experience will have to deal with the issues.

Storefront is a free WooCommerce theme you can use for testing.

Here is a helpful article that explains how you can install and configure it https://woocommerce.com/document/installation-configuration/

Hi, it looks like the issue isn’t only related to the shopping cart; overall, each page takes a long time to load (when it isn’t cached).

When a cached page is served, it loads quickly. However, all add-to-cart requests aren’t cached to avoid issues with the cart information.

It can be seen that the server load time of a non-cached page is 5+ seconds. That means something happens on the server side that causes the slow server load time for all non-cached requests.

There are a lot of factors that might cause such slow loading (plugins, queries, custom code, etc.).

The website’s performance will need to be tested in a staging environment. For example, disabling plugins, enabling another theme can be used for the test, etc. There is no straightforward solution, and everything the website uses will need to be tested.

Once it is clear what causes the issue, it will need to be optimized to improve the website’s overall performance.

Also, here is a helpful plugin that can help with finding the root of the problem (https://www.ads-software.com/plugins/query-monitor/).

Hi,

Deprecated error

In order to fix the deprecated error, you’ll need to use an anonymous function instead of create_function.

For example:

// Closures can also accept regular arguments
$example = function ($arg) use ($message) {
    var_dump($arg . ' ' . $message);
};
$example("hello");

The full guide can be found at https://www.php.net/manual/en/functions.anonymous.php

Fatal Error — Call to undefined function types_render_field

It looks like your website uses Toolset.

The same error was reported on https://toolset.com/forums/topic/php-fatal-error-call-to-undefined-function-types_render_field/

Please check if their solution will work for you. If it doesn’t work, you might need to refactor the hero fragment so it doesn’t use the missing function.

The error occurs because the build process can’t find the particular resource (that is hosted on the staging URL).

The first step would be preparing your WordPress instance the Gatsby website will use for fetching data.

Currently, there are no A records added for staging.innerspiritphoto.com (https://mxtoolbox.com/SuperTool.aspx?action=a%3astaging.innerspiritphoto.com&run=toolpage), and this instance doesn’t work.

You can point the A records of staging.innerspiritphoto.com to the server responsible for the WordPress instance (you can also use another sub-domain such as wp.innerspiritphoto.com).

Once the sub-domain is configured, you can prepare your WordPress instance and then proceed with configuring the build process.

The Gatsby Cloud servers should handle only the main domains (innerspiritphoto.com and www.innerspiritphoto.com), not the WordPress instance.

• This reply was modified 2 years, 3 months ago by aatanasov.
• This reply was modified 2 years, 3 months ago by aatanasov.
• This reply was modified 2 years, 3 months ago by aatanasov.

Firstly, I’ve noticed the following:
– The website URL is https://www.innerspiritphoto.com but there is a redirect to https://innerspiritphoto.com
– There are such requests https://www.staging.innerspiritphoto.com

You can migrate all links to https://innerspiritphoto.com

Also, usually for a Gatsby website, the WordPress dashboard and the front end are separated (i.e. a Headless approach). This approach is also explained at https://www.gatsbyjs.com/blog/2020-07-07-wordpress-source-beta/

That means https://innerspiritphoto.com should only serve generated static pages without allowing the WordPress dashboard to be accessed.

Please check which WordPress instance your Gatsby website uses. It might be https://www.staging.innerspiritphoto.com/wp-login.php

On that code line, WordPress checks if there is a suitable rewrite rule for the particular request.

The warning probably appears because there is an incorrectly added rewrite rule.

Please try to refresh your permalinks from (Settings -> Permalinks). This also flushes the rewrite rules.

Before doing that, please disable all plugins that have been installed since you started to experience the issue.

• This reply was modified 2 years, 3 months ago by aatanasov.

Hi,

The code inside your .htaccess file looks suspicious. This isn’t the default one.

I’m going to explain two possible things that might cause the issue.

Plugins

There might be a plugin that automatically generates the .htaccess file when the website is visited.

Please try to disable all plugins and see if the file will be generated.

Malicious scripts

Infected files might be triggered to generate such a file.

You can scan the files inside your hosting account. Usually, hosting services offer such a tool.

Additional Solutions

You can test one of your websites with another WordPress theme to see if it will work.

You can also see what all websites that experience the issue have in common. All of them might use something that generates the file.

Hotfix

Until you find the root of the problem, as a hotfix to ensure your websites work, you can change the permissions of the .htaccess file(so it isn’t writable) and insert the default code inside the .htaccess file manually.

The default .htaccess code can be found at https://www.ads-software.com/support/article/htaccess/#basic-wp

Hi,

Admin — site speed

You can first check what is happening with the browser requests. Your dashboard might try to load something that affects the performance of your WordPress dashboard.

Here is a helpful article/video that shows how you can measure such requests: https://developer.chrome.com/docs/devtools/network/

If the initial server load is slow, it might be caused by the plugins or the theme you use. If that is the case, you’ll need to test them separately(disable/enable them until you find which one causes the issue).

Updating entries

It looks like WordPress can’t handle the Submit requests.

You can open the network tab of your browser and check if there are any errors when updating/publishing an article. If there are bad requests, you can click on any of them and see if there are any helpful error messages.

Before doing that, please enable the WP Debug mode.

Also, it is recommended to check the health of your website using https://www.ads-software.com/plugins/health-check/ — you can scan your website to identify if something is wrong.

Debugging has to happen in a staging environment.

—-

Finally, since you experience issues only with the subdomains of your WordPress multisite, they might not be configured correctly. You can try to use subdirectories and see if this approach makes a difference.

Thanks,
Aleksandar

• This reply was modified 2 years, 3 months ago by aatanasov.
• This reply was modified 2 years, 3 months ago by aatanasov.

Hi @mwebsterm,

The logo has been changed to a transparent one, but there is still space around the logo.

Please review this screenshot: https://snipboard.io/vuQX73.jpg — the white area is a transparent background, but it shows how much space it takes, which is used by the img tag.

The transparent area above and below the graphic should be removed.

If you upload a logo like this one: https://i.snipboard.io/7HKzXP.jpg

The result on mobile will be like this: https://snipboard.io/N6L230.jpg

Regarding the JavaScript question: it is currently necessary to set the correct height of the logo depending on the dimensions of the uploaded attachment logo. If the logo works as expected after cropping the logo correctly, you can keep that JavaScript functionality.

Hi @wileycoyote78,

I investigated the issue locally, and I was able to reproduce it.

It happens if the theme location menu isn’t selected through the WordPress dashboard Menu page. In our case, the top menu (defined in the wp_nav_menu function arguments: 'theme_location' => 'top',).

Here are some helpful screenshots:

• No location selected (incorrect class placement): https://snipboard.io/1G2hz5.jpg
• Location selected (correct class placement): https://snipboard.io/WlZ2pt.jpg

Please set the top location to the main menu as shown on https://snipboard.io/NeyiqV.jpg (the bottom display location checkbox) and let us know if it works.

• This reply was modified 2 years, 5 months ago by aatanasov.