PluginProbe
ووسلام – همگام سازی ووکامرس و باسلام / 1.10.23
ووسلام – همگام سازی ووکامرس و باسلام v1.10.23
1.10.23 1.10.22 1.10.21 1.10.19 1.10.20 1.10.18 1.10.17 1.10.15 1.10.14 1.10.13 1.10.12 1.10.10 1.10.9 1.10.8 1.10.7 1.10.6 1.10.5 1.10.4 1.10.3 1.10.2 1.10.1 1.10.0 1.9.2 1.9.1 1.9.0 All 56 releases
← All changes | CHANGELOG.md +241 -0 1.10.3 → 1.10.23 View file →
@@ -1,8 +1,249 @@
1 1 # Changelog
2 2
3 3 <details>
4 4
5 +<summary>1.10.23 - 2026-09-28</summary>
6 +
7 +### Added
8 +- Request the `vendor.financial.read` and `vendor.financial.write` scopes when connecting to Basalam
9 +
10 +### Changed / Improved
11 +- Blur and lock the financial management page when a financial API request returns HTTP 403, with a direct button to reconnect to Basalam
12 +
13 +### Note
14 +- Existing connections must reauthenticate to grant the new financial scopes
15 +
16 +</details>
17 +
18 +<details>
19 +
20 +<summary>1.10.22 - 2026-09-27</summary>
21 +
22 +### Added
23 +- Added an optional recurring full product update every 24 or 48 hours, configured beside the product sync control; new and existing stores default to 48 hours and can turn the schedule off
24 +
25 +### Changed / Improved
26 +- Automatic product connection now searches for safe title matches among Basalam products after scanning the vendor catalog
27 +- Aligned the dashboard controls and advanced settings on narrow screens, and centered the add and update product dialogs at matching mobile sizes
28 +
29 +### Fixed
30 +- The product update dialog now reads live queue status when opened and while visible, clearing completed-job messages without a page reload
31 +- Empty-queue probes no longer hold the async dispatch lease, so newly created jobs can start promptly while shutdown dispatch continues to repair the database connection
32 +
33 +</details>
34 +
35 +<details>
36 +
37 +<summary>1.10.21 - 2026-09-17</summary>
38 +
39 +### Fixed
40 +- "All fields" and "price & stock" update modes always send one complete product request with the variants array (without Basalam variation ids), matching earlier major versions; the dedicated variation endpoint is only used in "custom" mode with the variation price/stock fields enabled
41 +- Product updates now recover automatically when WooCommerce contains stale Basalam variation IDs, rebuilding and saving the current variation mapping instead of repeatedly failing with HTTP 404
42 +- Commission lookup now uses Basalam's product-specific commission API for products already connected to Basalam; new or unconnected products continue to use category-based commission lookup, with product commission responses cached during the sync request
43 +
44 +</details>
45 +
46 +<details>
47 +
48 +<summary>1.10.20 - 2026-09-17</summary>
49 +
50 +### Fixed
51 +- Basalam authorization callbacks no longer fail when Redis or Memcached drops the temporary OAuth marker; the single-use authorization proof is now carried in a signed, time-limited HttpOnly cookie
52 +
53 +</details>
54 +
55 +<details>
56 +
57 +<summary>1.10.19 - 2026-09-17</summary>
58 +
59 +### Changed / Improved
60 +- Single-product update jobs now run before bulk and full-update coordinator jobs
61 +
62 +</details>
63 +
64 +<details>
65 +
66 +<summary>1.10.18 - 2026-09-12</summary>
67 +
68 +### Fixed
69 +- Public plugin metadata, help, terms, and privacy links now use the live canonical Hamsalam and Basalam URLs instead of the retired `wp.hamsalam.ir` host
70 +- Product create and update requests now retry once without product or variation SKUs when Basalam rejects a duplicate SKU
71 +
72 +</details>
73 +
74 +<details>
75 +
76 +<summary>1.10.17 - 2026-09-09</summary>
77 +
78 +### Fixed
79 +- Async job dispatch runs during shutdown again, keeping queue probes and loopback requests out of the storefront response path
80 +- The dispatch lease is reserved before checking the queue, preventing concurrent requests from launching duplicate async runners
81 +
82 +</details>
83 +
84 +<details>
85 +
86 +<summary>1.10.16 - 2026-09-08</summary>
87 +
88 +### Fixed
89 +- Installing a newer plugin package now clears the previous version's force-update gate, allowing migrations, hooks, and the background jobs runner to start normally
90 +- Hotfix builds newer than the latest published package are no longer disabled when the version API has not registered them yet
91 +
92 +</details>
93 +
94 +<details>
95 +
96 +<summary>1.10.15 - 2026-09-08</summary>
97 +
98 +### Fixed
99 +- Large product queues no longer spawn overlapping AJAX runners from normal site traffic; one runner now owns the entire processing batch and duplicate workers exit immediately
100 +- Async runner dispatches are leased for 25 seconds instead of one second, preventing PHP worker exhaustion and storefront 503/504 errors during full or quick product updates
101 +- Installing a newer plugin package now clears the previous version's force-update gate, allowing migrations, hooks, and the background jobs runner to start normally
102 +- Hotfix builds newer than the latest published package are no longer disabled when the version API has not registered them yet
103 +
104 +</details>
105 +
106 +<details>
107 +
108 +<summary>1.10.14 - 2026-09-08</summary>
109 +
110 +### Added
111 +- Product SKUs are now sent to Basalam when creating or updating products, and variation SKUs are sent with variant payloads and per-variation updates; a new "کد محصول (SKU)" option controls the field in custom update mode (enabled by default)
112 +
113 +### Fixed
114 +- The async job runner now dispatches from init instead of shutdown, avoiding database "commands out of sync" errors caused by unread result sets left by other shutdown callbacks
115 +
116 +</details>
117 +
118 +<details>
119 +
120 +<summary>1.10.13 - 2026-09-01</summary>
121 +
122 +### Added
123 +- Added a manual vendor-status recheck button to inactive-vendor notices so store owners can immediately restore synchronization after reactivating their Basalam booth
124 +
125 +### Changed / Improved
126 +- Local environments now bypass vendor-status checks and inactive-vendor restrictions; the daily vendor-status cron is also unscheduled locally
127 +- The category detection endpoint now uses API v2.0 while preserving the existing response consumer contract
128 +
129 +</details>
130 +
131 +<details>
132 +
133 +<summary>1.10.12 - 2026-08-29</summary>
134 +
135 +### Fixed
136 +- Restored the AJAX click handlers for product update, archive, restore, and disconnect actions on the WooCommerce product editor
137 +
138 +### Changed / Improved
139 +- The authenticated Woosalam chat widget now loads on every WordPress admin screen while other Woosalam assets remain scoped to their relevant pages
140 +
141 +</details>
142 +
143 +<details>
144 +
145 +<summary>1.10.11 - 2026-08-26</summary>
146 +
147 +### Fixed
148 +- Product media MIME types are now detected from the actual file contents before checking the filename extension
149 +- Non-standard image MIME aliases such as `image/jpg`, `image/pjpeg`, and vendor-specific PNG/BMP values are normalized to the canonical values accepted by Basalam Uploadio
150 +- The media upload request and multipart file transfer now use the same canonical MIME type, preventing valid JPEG images from failing with a `422` unsupported-MIME response
151 +
152 +</details>
153 +
154 +<details>
155 +
156 +<summary>1.10.10 - 2026-08-25</summary>
157 +
158 +### Added
159 +- Added a daily vendor-status check with persistent inactive-duration tracking and automatic recovery when the vendor becomes active again
160 +- Added state-specific admin notices, dashboard badges, disabled controls, and explanatory UI for limited and suspended synchronization modes
161 +
162 +### Changed / Improved
163 +- Vendors inactive for less than 21 days can no longer create products; manual, bulk, queued, and automatic updates are restricted to price and stock
164 +- Vendors inactive for 21 days or longer can no longer create, update, archive, restore, or discount products until the vendor becomes active again
165 +- Product jobs revalidate the vendor policy at execution time so queued work cannot bypass a later status change
166 +- Improved background job dispatch and limited admin assets and notices to relevant Woosalam, product, and order screens
167 +- Aligned the connection-status header, card, and inner synchronization panel across active and inactive states
168 +
169 +</details>
170 +
171 +<details>
172 +
173 +<summary>1.10.9 - 2026-08-16</summary>
174 +
175 +### Fixed
176 +- The ticket reply access form is now shown only after site access is rejected; it stays hidden while access is pending, after approval, and when the status is missing or unknown
177 +
178 +</details>
179 +
180 +<details>
181 +
182 +<summary>1.10.8 - 2026-08-15</summary>
183 +
184 +### Added
185 +- Added independent settings for updating variation prices and variation stock
186 +
187 +### Changed / Improved
188 +- Connected variations are now updated individually through Core v4
189 +- Price-only variation updates send only `primary_price`, while stock-only updates send only `stock`
190 +- Variation price updates work independently from the product price setting
191 +- Custom update mode now requires at least one selected field and shows the plugin error toast without refreshing the page when none is selected
192 +- Full, quick, selected, and automatic updates no longer create jobs or API requests when the custom field selection is empty
193 +- Product admin JavaScript now uses a file-aware cache version so the latest validation behavior is loaded immediately after deployment
194 +
195 +</details>
196 +
197 +<details>
198 +
199 +<summary>1.10.7 - 2026-08-11</summary>
200 +
201 +### Fixed
202 +- Ticket validation and API failures are now shown as admin toasts instead of WordPress `admin-post.php` error pages
203 +- New-ticket submissions now use AJAX, preserving entered text, credentials, and uploaded-image previews when a request fails; if the ticket was created before access storage failed, retrying updates only the access data and does not create a duplicate ticket
204 +- Ticket JavaScript now uses a file-aware cache version so updated validation and submission behavior is loaded immediately after deployment
205 +
206 +</details>
207 +
208 +<details>
209 +
210 +<summary>1.10.6 - 2026-08-11</summary>
211 +
212 +### Fixed
213 +- Product images in AVIF or another image format unsupported by Basalam are now converted to JPEG before the upload request, preventing the `422` unsupported-MIME error
214 +- Temporary downloaded and converted product-image files are removed after both successful and failed uploads; when the server cannot decode the source format, the plugin now returns an actionable error instead of sending an invalid MIME type to Basalam
215 +- A copied product no longer inherits *any* Woosalam data from the product it was copied from — not the Basalam connection, and not the per-product settings (video, custom price change, gold/mobile fields, product type and value, wholesale, discount flag). Every `sync_basalam_*` / `_sync_basalam_*` meta on the duplicate and its variations is stripped before WooCommerce saves the duplicate (`woocommerce_duplicate_product_exclude_meta`), cleaned again after duplication, and also cleaned for copies made by third-party duplicate plugins (`dp_duplicate_post`, `dp_duplicate_page`, `duplicate_post_post_copy`). Individual keys can be kept via the `sync_basalam_duplicate_purge_meta_keys` filter
216 +- Disconnecting a product now removes the connection meta of every vendor id (previously only the currently configured vendor's keys were removed, so a stale, hard to find key could stay in the database) and clears `sync_basalam_variation_id` from all variations, not only from products currently typed as variable
217 +- No product data, status change, or discount is sent to Basalam while two or more WooCommerce products share one Basalam product id. The operation is stopped with a clear message instead of overwriting the wrong Basalam product (this is what made old prices and old stock reappear on Basalam)
218 +- Products with an empty Basalam product id no longer produce a malformed update request
219 +
220 +### Added
221 +- A one-time repair on update that finds WooCommerce products sharing a Basalam product id, keeps the connection on the oldest (original) product, disconnects the copies, and reports the result in an admin notice and the plugin log
222 +
223 +</details>
224 +
225 +<details>
226 +
227 +<summary>1.10.5 - 2026-08-05</summary>
228 +
229 +### Changed / Improved
230 +- Limited bulk product update API requests to a maximum of five per minute without reducing the execution rate of other background jobs
231 +
232 +</details>
233 +
234 +<details>
235 +
236 +<summary>1.10.4 - 2026-08-04</summary>
237 +
238 +### Fixed
239 +- Preserved complete URLs in new ticket messages, ticket replies, and optional access-information fields, including percent-encoded URL segments that WordPress text sanitization previously removed
240 +- Updated ticket media uploads to send `type=ticket_item` and `collection=IMAGE` as multipart form fields to the `/media` endpoint, and fixed the upload service to return the API response
241 +
242 +</details>
243 +
244 +<details>
245 +
5 246 <summary>1.10.3 - 2026-07-22</summary>
6 247
7 248 ### Changed / Improved
8 249 - "Price increase" became "price change" everywhere (code, markup, CSS classes): negative values are supported, so e.g. `-10` lowers the final Basalam price by 10% (percentages are capped at 35% increase and 35% decrease; values outside the -100..100 range are fixed Toman amounts)