-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Woocommerce #54
Comments
I have the same issue. How to resolve this? System status reportWordPress EnvironmentWC Version: 8.7.0 Server EnvironmentServer Info: nginx/1.24.0 SUHOSIN Installed: – DatabaseWC Database Version: 8.7.0 Post Type Countsattachment: 10 SecuritySecure connection (HTTPS): ✔ Active Plugins (8)App Service Email: by Microsoft – 1.0.0 Inactive Plugins (1)Akismet Anti-spam: Spam Protection: by Automattic - Anti-spam Team – 5.3.2 Dropin Plugins ()advanced-cache.php: advanced-cache.php SettingsAPI Enabled: – Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog) Connected to Woo.com: ✔ LoggingEnabled: ✔ WC PagesShop base: #12 - /shop/ ThemeName: dokani WooCommerce Support: ✔ TemplatesOverrides: dokani-develop/woocommerce/archive-product.php Outdated Templates: ❌
AdminEnabled Features: activity-panels Disabled Features: customize-store Daily Cron: ✔ Next scheduled: 2024-03-24 23:56:40 +05:30 Action SchedulerComplete: 11 Failed: 1 Pending: 3 Status report informationGenerated at: 2024-03-25 02:22:41 +05:30 |
@shams-sadek1981 Vai, please check this issue and assign it to the developer. |
Your theme (dokani) contains outdated copies of some WooCommerce template files. These files may need updating to ensure they are compatible with the current version of WooCommerce. Suggestions to fix this:
Update your theme to the latest version. If no update is available contact your theme author asking about compatibility with the current WooCommerce version.
If you copied over a template file to change something, then you will need to copy the new version of the template and apply your changes again.
The text was updated successfully, but these errors were encountered: