Foroshgah - افزونه رسمی فروشگاه
| 开发者 | wikionline |
|---|---|
| 更新时间 | 2026年10月2日 04:30 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- اتصال یک‌بار مصرف و امن به سرویس فروشگاه.
- همگام‌سازی اولیه و دستی محصولات و متغیرهای عمومی WooCommerce.
- ارسال تغییرات محصول، قیمت، موجودی، وضعیت و حذف محصولات.
- مدیریت صف ارسال اطلاعات با قابلیت تلاش مجدد محدود و مدیریت خطا.
- پشتیبانی از Action Scheduler همراه با امکان استفاده از WP-Cron.
- امضای امن درخواست‌ها و ذخیره رمزگذاری‌شده اطلاعات اتصال.
- حذف اطلاعات ارسال‌شده پس از تحویل موفق برای کاهش نگهداری اطلاعات محلی.
安装:
- افزونه را از طریق پیشخوان وردپرس نصب کنید: مسیر: افزونه‌ها ← افزودن ← بارگذاری افزونه یا فایل افزونه را به‌صورت دستی در مسیر زیر قرار دهید: /wp-content/plugins/
- پس از نصب، افزونه را از بخش «افزونه‌ها» فعال کنید.
- پس از فعال‌سازی، از بخش «فروشگاه» وارد تنظیمات افزونه شوید.
- کد اتصال یک‌بار مصرف را از پنل فروشگاه دریافت کرده و در افزونه وارد کنید.
- پس از برقراری اتصال، اطلاعات محصولات، قیمت، موجودی و تغییرات فروشگاه به‌صورت خودکار همگام‌سازی خواهد شد.
- در اولین اتصال، منتظر بمانید تا فرآیند همگام‌سازی اولیه محصولات به پایان برسد.
常见问题:
Does the plugin send data immediately after activation?
On a fresh installation, no catalog transmission starts until an authorized store administrator explicitly connects the store with a one-time pairing code. If a previously connected installation is reactivated, previously authorized background delivery may resume until the integration is disconnected.
Are draft or private products sent to Foroshgah.org?
No. Draft, pending, private, and catalog-hidden products are not sent as full catalog payloads. If a product that was previously public becomes non-public, a deletion event containing only identifiers may be sent so it can be removed from the remote catalog.
Does the plugin send customer or order information?
No. The integration is for product catalog synchronization and does not intentionally transmit WooCommerce orders, customer records, customer addresses, payment data, or administrator credentials.
What happens to product payloads stored locally?
Pending and retryable messages are kept in the plugin-owned outbox until delivery succeeds or the retry limit is reached. After successful delivery, the stored payload body is cleared while minimal delivery metadata remains until the administrator clears successful history or uninstalls the plugin.
How do I stop synchronization?
Use the Disconnect action on the plugin page. This removes the local connection credential and stops authenticated catalog delivery. If the remote connection also needs to be revoked, revoke it from the Foroshgah seller service.
What happens on uninstall?
Uninstall removes plugin-owned options, scheduled jobs, local connection credentials, and the plugin outbox table. It does not delete or modify WooCommerce products, orders, customers, or WooCommerce settings.
更新日志:
- Cleaned up internal legacy CompareHub implementation identifiers without changing persisted scheduler hooks or the external API contract.
- Added backward-compatible migration for legacy connection settings.
- Preserved existing encrypted connection credentials and synchronization state; administrator re-pairing is not required.
- Preserved legacy scheduled hooks, external API headers, request signing, and credential encryption behavior.
- Fixed admin CSS loading by matching the correct top-level menu hook.
- Prepared the package for WordPress.org review.
- Documented the Foroshgah.org external service and exact data scope.
- Added WooCommerce as an explicit plugin dependency in the plugin header.
- Aligned the plugin text domain and package slug.
- Restricted full catalog payloads to published, catalog-visible products and eligible variations.
- Non-public product transitions now emit identifier-only deletion events instead of catalog payloads.
- Added WordPress Privacy Policy Guide content and an explicit connection disclosure.
- Cleared successful outbox payload bodies after delivery to reduce local data retention.
- Completed scheduled-job and pairing-error cleanup during uninstall.
- Added resilient full-sync generation and finalization recovery.
- Improved outbox recovery, retry, and schema diagnostics.
- Added secure one-time pairing and authenticated API transport.