PluginProbe
Yatra – Travel Booking & Tour Operator Software / 3.0.17
Yatra – Travel Booking & Tour Operator Software v3.0.17
3.0.17 3.0.16 3.0.15 3.0.14 3.0.14.1 3.0.14.2 3.0.12 3.0.13 3.0.11 3.0.10 3.0.9 3.0.8 3.0.7 3.0.6 3.0.5 3.0.5.1 3.0.4 3.0.3 3.0.2.9 3.0.2.7 3.0.2.8 3.0.2.6 trunk 1.0.0 2.0.0 All 85 releases
← All changes | app/Controllers/SettingsController.php +28 -2 3.0.15 → 3.0.17 View file →
@@ -151,9 +151,18 @@
151 151 'email_template_admin_scheduled_payment_failed' => true,
152 152 'email_template_enquiry_received' => true,
153 153 'email_template_enquiry_admin' => true,
154 154 'email_template_enquiry_response' => true,
155 - 'email_template_review_request' => true,
155 + // Off by default, unlike the other templates. A review request is the
156 + // one transactional email that is not a response to something the
157 + // customer just did, and several jurisdictions treat it as advertising
158 + // rather than service mail — in Germany the BGH (VI ZR 225/17) holds it
159 + // needs prior consent, and the existing-customer exemption in
160 + // §7 Abs. 3 UWG does not cover it. Shipping it on would have every new
161 + // site mailing customers for consent it has not collected, so the
162 + // operator turns it on once they have decided how they collect it.
163 + // Sites that already have it on are untouched.
164 + 'email_template_review_request' => false,
156 165 'email_template_abandoned_booking_recovery_first' => true,
157 166 'email_template_abandoned_booking_recovery_second' => true,
158 167 'email_template_abandoned_booking_recovery_final' => true,
159 168 'smtp_enabled' => false,
@@ -182,9 +191,13 @@
182 191 'auto_approve_reviews' => false,
183 192 'review_moderation' => true,
184 193 'min_rating' => 1,
185 194 'allow_anonymous_reviews' => false,
186 - 'review_reminder_days' => 7,
195 + 'review_reminder_days' => 3,
196 + // Never ask about a trip that ended longer ago than this. The
197 + // reminder is anchored to the tour's end date, so a backlog of
198 + // bookings completed late is skipped rather than mailed in bulk.
199 + 'review_reminder_max_age_days' => 14,
187 200
188 201 // Tax Settings
189 202 'enable_tax' => false,
190 203 'tax_name' => __('Tax', 'yatra'),
@@ -223,8 +236,14 @@
223 236 'recaptcha_protect_enquiry' => false,
224 237 'recaptcha_protect_booking' => false,
225 238 'recaptcha_protect_registration' => false,
226 239
240 + // Uninstall. Off by default and deliberately never defaulted to true:
241 + // turning this on means deleting the operator's bookings, customers and
242 + // payment history when the plugin is removed, so it has to be a decision
243 + // somebody makes on purpose.
244 + 'delete_data_on_uninstall' => false,
245 +
227 246 // Permalink Settings
228 247 'trip_base' => 'trip',
229 248 'destination_base' => 'destination',
230 249 'activity_base' => 'activity',
@@ -266,8 +285,15 @@
266 285 'seo_trip_meta_description' => '',
267 286 'seo_trip_meta_keywords' => '',
268 287 'seo_trip_meta_image' => 0,
269 288 'enable_sitemap' => true,
289 + // Which Yatra content types appear in /yatra-sitemap.xml. Defaults to
290 + // every type, so a site that never touches this keeps today's sitemap.
291 + 'sitemap_types' => ['archive', 'trip', 'destination', 'activity', 'category'],
292 + // Opt-in, and deliberately separate from the list above: dropping a type
293 + // from the sitemap is housekeeping, while noindex de-indexes pages that
294 + // may currently rank. That should never happen as a side effect.
295 + 'sitemap_noindex_excluded' => false,
270 296
271 297 // Advanced Settings
272 298 'debug_mode' => false,
273 299 'enable_logging' => false,