John Smith

in response to “Have you confirmed that the issue goes away when not having the Algolia integration included?” I must say yes. when I select the option “Do not use Algolia” the search pagination works properly. I also tested when Elementor template is not applied to the search result and I must say problem still exist in that case as well. at the moment I select the option “Do not use Algolia”. but I need to solve this issue. any recommendation to troubleshoot this issue?

I have reached a conclusion and I will share my findings for anyone who visits this page later and seeks an answer.

Enabling the “Watch changed fields for use in hooks” option allows the Pods plugin to keep track of changes made to the values of these fields, so that they can be referenced later using PHP hooks. In other words, when you make changes to these fields and save them, the plugin will have a record of what the previous values were. This information can then be accessed and used by other plugins or custom code via the PHP hooks provided by Pods.

in my case I did not need that so I disabled that.

The “Watch WP Metadata calls” option determines whether the plugin will monitor metadata calls made by WordPress, and the “Override WP Metadata values” option determines whether the plugin will override metadata values with the values it is tracking. If you do not use table-based Pods and only want to query metadata-based Pods or settings, you can disable these options. This will prevent the plugin from monitoring metadata calls and updating table-based fields, which can improve performance.

Table-based Pods are a type of custom content type created using the Pods plugin for WordPress. Instead of storing custom data as metadata in the WordPress database, table-based Pods store the data in separate database tables, which allows for more advanced querying and manipulation of the data.

For example, consider a movie review website that uses Pods to store information about movies. A table-based Pod could be created to store information about each movie, such as the title, release date, director, and IMDb rating. Instead of storing this information as metadata in the WordPress database, the information would be stored in a separate database table specifically for movie information. This allows the website to easily query and display information about movies without having to retrieve and process metadata from the WordPress database.

To determine if you have table-based Pods in your WordPress website while using the Pods plugin, you can follow these steps:

1. Log in to your WordPress dashboard.
2. Go to the “Pods Admin” menu in the WordPress admin menu.
3. Click on the “Pods” option.
4. In the “Pods” screen, you will see a list of all the Pods you have created for your site.
5. Look at the “Storage Type” column for each Pod. If the storage type is listed as “Table”, then it is a table-based Pod. If the storage type is listed as “Meta”, then it is a metadata-based Pod.

I checked this column for my Pods and all of them were listed as “Meta”. so I disabled this option. (by disabling this option “Override WP Metadata values” will be disabled as well.)

now I can see that the website is much faster and also search over custom post types are a lot better.

I noticed that if I disable the following options in PODs setting it will increase speed significantly. but I wonder by disabling them I am doing a right thing or not:
– Watch changed fields for use in hooks
– Watch WP Metadata calls
– Override WP Metadata values
How can I know I need them or not? can you guide me?

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

I increased time out limit from 300 to 1000 but no success.

[03-Jul-2022 16:02:43 UTC] PHP Fatal error:  require(): Failed opening required '/public_html/wp-content/plugins/woocommerce/src/Admin/Features/OnboardingTasks/TaskList.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /public_html/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 87

this is the recent error that I get.
I can not go to status page as far as it is not loading at all.
but I can mention that I use some other plugins related to WooCommrce
YITH WooCommerce Quick View

BEAR – Bulk Editor and Products Manager Professional for WooCommerce
weLaunch Framework
WooCommerce Group Attributes
WooCommerce PDF Invoices & Packing Slips
WooCommerce PDF Invoices & Packing Slips Professional

and a few others

• This reply was modified 2 years, 8 months ago by John Smith.
• This reply was modified 2 years, 8 months ago by John Smith.
• This reply was modified 2 years, 8 months ago by John Smith.
• This reply was modified 2 years, 8 months ago by John Smith.

sure thanks what should I share ?
the result is that any page does not load at all and returns server error 500. the page has this paragraph:
“Request Timeout
This request takes too long to process, it is timed out by the server. If it should not be timed out, please contact administrator of this web site to increase ‘Connection Timeout’.”
I checked log file it has no error log related to woocommerce. but I am sure that the problem is with woocommerce because I deactivated all and just woocommerce was active (v 6.6.1) and there was this issue.
at the moment there is timeout limit 300 in wp-config.php. should I increase that?
currently I use version 6.4.1 . what else should I share?

• This reply was modified 2 years, 8 months ago by John Smith.

I must mention popups are made by Elementor Pro.

we have the site below:
https://zeevou.com
we use the PODS plugin for creating custom post types.
for example, we have these archives created by PODS plugin:
https://zeevou.com/features/
https://zeevou.com/integrations/
https://zeevou.com/channels/
…
because of the importance of these archives, we need to have these pages as landing pages from search results on search engines.
so this is the reason we need advanced SEO settings for custom post type archives.
can you please guide us on how to achieve this goal?
thank you for your response in advance

thank you for your response. I already enabled the SEO setting for custom post type archives and filled the SEO title and meta description under settings for custom post type archive, which are available there, but the question is where do other SEO settings appear for these archives including focus keyword, related keyword, and synonyms then we can set them.
I have templates for custom post type archives, but the SEO setting including focus keyword, related keyword, and synonyms is not showing there.
thank you for your response in advance