snyggapa

Thanks. Yes, I used a child theme and a test site beforehand so all is good.

I am not comfortable about turning off updates though as that leaves me at risk to security vulnerabilities hence I would prefer if it was considered useful for this to be an option in the core code , but I am happy with it as a solution for now.

Kind Regards

Steve

found it I think

plugins\the-events-calendar\src\views\v2\list\event\date-tag.php

I suspect I can make similar changes to achieve the same result. Be nice of this was core functionality though, as I really don’t like overriding code – too many things to break in future!

Thanks

Thanks Darian, that has given me enough to go on. I have copied the template and made some slightly different changes to get the result that I wanted, at least on that homepage widget and is visible now at https://woolacombesurflifesavingclub.org/

I changed the code to as below, so behaves differently conditional on whether the event is a single or multi day event (technically this would break if an event ran from one day of a month to the same day on the next month but that really doesn’t happen for us!) but if you look at the calendar widget on a desktop I hope you can see that it makes a big difference in “at a glance” visibility for users .

Could you please point me to were I can make the same changes for the main events calendar here – or where I can find a list of templates documented so that I can find it myself. Thanks

https://woolacombesurflifesavingclub.org/events/

<?php
/**
 * Widget: Events List Event Venue
 *
 * Override this template in your own theme by creating a file at:
 * [your-theme]/tribe/events/v2/widgets/widget-events-list/event/venue.php
 *
 * See more documentation about our views templating system.
 *
 * @link https://evnt.is/1aiy
 *
 * @version 5.2.1
 *
 * @var WP_Post $event The event post object with properties added by the tribe_get_event function.
 *
 * @see tribe_get_event() For the format of the event object.
 */

use Tribe__Date_Utils as Dates;

$display_date    = $event->dates->start_display;
$display_date_end = $event->dates->end_display;

$event_month     = $display_date->format_i18n( 'M' );
$event_day_num   = $display_date->format_i18n( 'j' );
$event_day_num_end   = $display_date_end->format_i18n( 'j' );

$event_date_attr = $display_date->format( Dates::DBDATEFORMAT );
?>
<div class="tribe-events-widget-events-list__event-date-tag tribe-common-g-col">
	<time class="tribe-events-widget-events-list__event-date-tag-datetime" datetime="<?php echo esc_attr( $event_date_attr ); ?>">
		<span class="tribe-events-widget-events-list__event-date-tag-month">
			<?php echo esc_html( $event_month ); ?>
		</span>
		<span class="tribe-events-widget-events-list__event-date-tag-daynum tribe-common-h2 tribe-common-h4--min-medium">
			<?php 
            if ($event_day_num_end == $event_day_num) 
            {echo esc_html( $event_day_num );}
             else
            {echo esc_html( $event_day_num."-".$event_day_num_end );}
            ?> 
		</span>
	</time>
</div>

–

Thanks Frank. I have tried that however . not sure if this link will work but shows what I would like to achieve: https://pasteboard.co/TIVZzIZGulgR.png

you can see that I have 2 events here that span 2 days, one with times and one with not. What I would like to add is the end date where I have annotated in red – as what people do is see the bold and assume that it is a single day event. is there a filter or hook to let me adjust this, or some other way?

Thank you

Thanks. Yes, if I can’t reproduce it I can’t do a lot and if this isn’t a known problem I just will have to hope that it is something environmental with one user.

If I can reproduce it I shall try other things out, but may as well close this ticket until that point.

Regards

Steve

Thanks Igor. Screenshot below:

https://snipboard.io/TzCce3.jpg

I have am updated to square 3.81 to 3.8.2 , I would be both disappointed and delighted if it were fixed . Delighted of course, but disappointed that the change log shows no obvious change that should fix it ??

not sure if I can get the customer to re-test as I don’t have a direct channel of communication, if I can get them to I will report back. Does the screenshot give you any clues – I guess it’s due to the way that the payment section page is rendered. If I could get it to fail myself I could do a load of digging but I can’t

Thanks

Hi there. Correct, we have been notified of one instance where the card details panel does not display. I suspect that it’s fine for 99% of people as we have only had one report of a problem, however of course we don’t know how many people have tried and not bothered to contact us.

This single know problem was on a mac. I have a partial screenshot but looks like I can’t include images here – but the section where you enter the card details was just a grey outline with no content.

No relevant status logs, woocommerce log below, I have redacted the site URL and DB prefix

Any ideas are appreciated, thanks

WordPress Environment

WordPress address (URL): https://mysite.replaced
Site address (URL): https://mysite.replaced
WC Version: 7.7.0
REST API Version: ? 7.7.0
WC Blocks Version: ? 10.0.4
Action Scheduler Version: ? 3.5.4
Log Directory Writable: ?
WP Version: 6.2.2
WP Multisite: –
WP Memory Limit: 256 MB
WP Debug Mode: –
WP Cron: ?
Language: en_GB
External object cache: –

Server Environment

Server Info: Apache
PHP Version: 8.1.17
PHP Post Max Size: 512 MB
PHP Time Limit: 120
PHP Max Input Vars: 1000
cURL Version: 7.68.0
OpenSSL/1.1.1f

SUHOSIN Installed: –
MySQL Version: 5.7.26-log
Max Upload Size: 512 MB
Default Timezone is UTC: ?
fsockopen/cURL: ?
SoapClient: ?
DOMDocument: ?
GZip: ?
Multibyte String: ?
Remote Post: ?
Remote Get: ?

Database

WC Database Version: 7.7.0
WC Database Prefix: myprefix_
Total Database Size: 20.61MB
Database Data Size: 15.72MB
Database Index Size: 4.89MB
myprefix_woocommerce_sessions: Data: 0.06MB + Index: 0.02MB + Engine InnoDB
myprefix_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
myprefix_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
myprefix_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_woocommerce_order_itemmeta: Data: 0.09MB + Index: 0.09MB + Engine InnoDB
myprefix_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
myprefix_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
myprefix_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
myprefix_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
myprefix_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_actionscheduler_actions: Data: 0.41MB + Index: 0.52MB + Engine InnoDB
myprefix_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_actionscheduler_logs: Data: 0.30MB + Index: 0.27MB + Engine InnoDB
myprefix_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
myprefix_comments: Data: 0.13MB + Index: 0.09MB + Engine InnoDB
myprefix_ff_scheduled_actions: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_fluentform_entry_details: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_fluentform_forms: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_fluentform_form_analytics: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_fluentform_form_meta: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_fluentform_logs: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_fluentform_submissions: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_fluentform_submission_meta: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_options: Data: 8.05MB + Index: 0.19MB + Engine InnoDB
myprefix_postmeta: Data: 1.50MB + Index: 1.95MB + Engine InnoDB
myprefix_posts: Data: 2.11MB + Index: 0.17MB + Engine InnoDB
myprefix_tec_events: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_tec_occurrences: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
myprefix_termmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
myprefix_terms: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
myprefix_term_relationships: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_term_taxonomy: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
myprefix_usermeta: Data: 0.05MB + Index: 0.03MB + Engine InnoDB
myprefix_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
myprefix_wc_admin_notes: Data: 0.06MB + Index: 0.00MB + Engine InnoDB
myprefix_wc_admin_note_actions: Data: 0.06MB + Index: 0.02MB + Engine InnoDB
myprefix_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_wc_customer_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
myprefix_wc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
myprefix_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
myprefix_wc_order_product_lookup: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
myprefix_wc_order_stats: Data: 0.03MB + Index: 0.05MB + Engine InnoDB
myprefix_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
myprefix_wc_product_attributes_lookup: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_wc_product_download_directories: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_wc_product_meta_lookup: Data: 0.05MB + Index: 0.09MB + Engine InnoDB
myprefix_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_woocommerce_square_customers: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_wpda_csv_uploads: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_wpda_logging: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_wpda_media: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_wpda_menus: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_wpda_project: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_wpda_project_page: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_wpda_project_table: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_wpda_publisher: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
myprefix_wpda_table_design: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_wpda_table_settings: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
myprefix_wpforms_tasks_meta: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_kv8hsd_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_kv8hsd_comments: Data: 0.02MB + Index: 0.08MB + Engine InnoDB
wp_kv8hsd_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_kv8hsd_options: Data: 1.50MB + Index: 0.03MB + Engine InnoDB
wp_kv8hsd_postmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_kv8hsd_posts: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_kv8hsd_termmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_kv8hsd_terms: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_kv8hsd_term_relationships: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_kv8hsd_term_taxonomy: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_kv8hsd_usermeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_kv8hsd_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDB

Post Type Counts

attachment: 231
custom_css: 3
customize_changeset: 14
et_body_layout: 1
et_footer_layout: 1
et_pb_layout_stashed: 8
et_template: 3
et_theme_builder: 1
fpf_fields: 1
layout: 2
nav_menu_item: 26
page: 19
post: 4
product: 43
product_variation: 135
revision: 158
shop_order: 161
shop_order_refund: 3
tribe_events: 7
tribe_venue: 6
wp_global_styles: 3
wp_navigation: 1
wpforms: 1

Security

Secure connection (HTTPS): ?
Hide errors from visitors: ?

Active Plugins (11)

Astra Pro: by Brainstorm Force – 4.1.5
DreamHost Panel Login: by DreamHost
danielbachhuber – 1.0.0

Flexible Product Fields: by WP Desk – 2.3.7
Fluent Forms: by Contact Form - WPManageNinja LLC – 4.3.25
SumUp Payment Gateway For WooCommerce: by SumUp – 1.2
The Events Calendar: by The Events Calendar – 6.0.13.1
UpdraftPlus - Backup/Restore: by UpdraftPlus.Com
DavidAnderson – 2.23.4.26

Advanced Order Export For WooCommerce: by AlgolPlus – 3.4.0
WooCommerce Square: by WooCommerce – 3.8.1 (update to version 3.8.2 is available)
WooCommerce: by Automattic – 7.7.0 (update to version 7.7.1 is available)
WP Super Cache: by Automattic – 1.9.4

Inactive Plugins (1)

User Role Editor: by Vladimir Garagulya – 4.63.3

Dropin Plugins (1)

advanced-cache.php: advanced-cache.php

Settings

API Enabled: –
Force SSL: –
Currency: GBP (￡)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: external (external)
grouped (grouped)
simple (simple)
variable (variable)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)

Connected to WooCommerce.com: –
Enforce Approved Product Download Directories: ?
HPOS feature screen enabled: –
HPOS feature enabled: –
Order datastore: WC_Order_Data_Store_CPT
HPOS data sync enabled: –

WC Pages

Shop base: #75 - /shop/
Basket: #76 - /cart/
Checkout: #77 - /checkout/
My account: ? Page does not contain the [woocommerce_my_account] shortcode.
Terms and conditions: ? Page not set

Theme

Name: WSLC theme Astra
Version: 1.0.0
Author URL: https://wpastra.com/about/
Child Theme: ?
Parent Theme Name: Astra
Parent Theme Version: 4.1.5
Parent Theme Author URL: https://wpastra.com/about/?utm_source=theme_preview&utm_medium=author_link&utm_campaign=astra_theme
WooCommerce Support: ?

Templates

Overrides: –

Square

Environment: Production
Tokenization Enabled: –
Debug Mode: Off

Admin

Enabled Features: activity-panels
analytics
coupons
customer-effort-score-tracks
import-products-task
experimental-fashion-sample-products
shipping-smart-defaults
shipping-setting-tour
homescreen
marketing
mobile-app-banner
navigation
onboarding
onboarding-tasks
remote-inbox-notifications
remote-free-extensions
payment-gateway-suggestions
shipping-label-banner
subscriptions
store-alerts
transient-notices
woo-mobile-welcome
wc-pay-promotion
wc-pay-welcome-page

Disabled Features: product-block-editor
minified-js
new-product-management-experience
product-variation-management
settings

Daily Cron: ? Next scheduled: 2023-05-31 12:46:50 +01:00
Options: ?
Notes: 70
Onboarding: completed

Action Scheduler

Complete: 1,226
Oldest: 2023-04-30 00:02:08 +0100
Newest: 2023-05-30 08:51:31 +0100

Failed: 3
Oldest: 2023-03-27 13:59:57 +0100
Newest: 2023-05-17 00:20:01 +0100

Pending: 2
Oldest: 2023-05-30 22:44:54 +0100
Newest: 2023-05-31 00:58:22 +0100

Status report information

Generated at: 2023-05-30 21:12:01 +01:00
`

excellent, enjoy your break

Hi Peter, I found the issue – one “mapped” column had a database field name that wasn’t quite right – “Script” (with a capital S) – whereas the “table” column also had the same field but without the capital S.

If I upload with “Script” as the mapped column then those 2 rows fail to import. If I drag “Script” to the right and then drag in “script” as pictured below then all rows import OK.

that column was recreated at some point (changed from varchar to TEXT ) so it is possible that it used to be Script and is now script – and WPDA kind of thinks they are the same but not the same!

Once I have saved the mapping and gone back to it, then the erroneous “Script” field is gone from the right hand list – so this looks like a really obscure issue caused by changing the case of a field name !

Thanks for your assistance

Steve

not sure if the forum will like the multiple language UTF-8 characters but here you go :). Sorry for the header.. excel!

first 2 rows go in , second two fail – Script (English) column is the troublesome one

I filled i your contact form if you could reply I can send you a fuller example if this isn’t enough. Thanks

Sport,EN Sport order,FRENCH Sport name,FR Sport order,JAPANESE Sport name,JA Sport order,Sub-Sport,FR Sub-Sport,JA Sub-Sport,Impairment Group,FR Impairment Group,JA Impairment Group,Type,Category,FR Category,JA Category,Script (English),FRENCH Script,JAPANESE Script,Button Colour,Displaygroup,Image 1,Heading 1,CharacterVid 1,Image 2,Heading 2,CharacterVid 2,Image 3,Heading 3,CharacterVid 3,Image 4,Heading 4,CharacterVid 4,Image 5,Heading 5,CharacterVid 5,Image 6,Heading 6,CharacterVid 6,Image 7,Heading 7,CharacterVid 7,Image 8,Heading 8,CharacterVid 8,Image 9,Heading 9,CharacterVid 9,Image 10,Heading 10,CharacterVid 10,In Other Sports,Video Link 1,Video Link 2,Team Size,Team Points,Team Example 1,Team GROUP 1,Team Example 2,Team GROUP 2,URL,FRENCH URL,JAPANESE URL,Summer or Winter Sport,Tokyo 2020 Event,Beijing 2022 Event,DisplayStyle,HeaderImage,Extra Info,Men’s Events,Women’s Events,Mixed Events,On-screen Class Title,,,,,,,,,,,SLOVAK Sport NAME,SK Sport Order,SK Sub-Sport,SK Impairment Group,SK Category,SLOVAK Script,slovak new url,,URL,,,FRENCH URL,,,,,,,,,,,,,,,,,,,,,,,,,,,,`

Swimming,,Natation,,水泳,,Individual Medley,Quatre nages,個人メドレー,VISUAL,VISUEL,視覚障害,,SM11,SM11,SM11,SM11?is for swimmers with near-total visual impairment.<br><br/>All swim in blacked-out goggles. Head tappers and stroke-counting are used to precisely execute the turns.,SM11 est destiné aux nageurs ayant une déficience visuelle quasi totale.<br><br/>Tous nagent avec des lunettes noircies. Pour exécuter les virages avec précision le nageur utilise le comptage de coups et l’aide d’un assistant muni d’une perche au bout rembourré.,SM11は、ほぼ完全な視覚障害の水泳選手のクラスです。<br><br/>全員が目隠しをして泳ぎます。ターンを正確に行うためヘッドタッパーとストロ－クカウンティングが使用されます。,1,22,37,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,Y,,,,,,,,,/sports/swimming/individual-medley/sm11,/fr/sports/natation/quatre-nages/sm11,/ja/sports/swimming/individual-medley/sm11,Summer,Y,,2,,,200 Individual Medley,200 Individual Medley,/,SM11,,,,,,,,,,,Plávanie,,Individuálna medza,VIZUáLNE,SM11,SM11 je pre plavcov s takmer totálnym po?kodením zraku.<br><br/>v?etky plávajú v skanzenych panách. Na presné vykonanie otá?ania sa pou?ívajú hlavové plienky a po?ítanie zdvihu.,/sk/sports/plavanie/individualna-medza/sm11,,/sports/swimming/individual-medley/sm11,/sports/swimming/individual-medley/sm11,Y,/fr/sports/natation/quatre-nages/sm11,/fr/sports/natation/quatre-nages/sm11,Y,,,,,,,,,,,,,,,,,,,,,,,,,,
Swimming,,Natation,,水泳,,Individual Medley,Quatre nages,個人メドレー,VISUAL,VISUEL,視覚障害,,SM12,SM12,SM12,SM12?is for swimmers with a visual impairment.<br/><br/>They have a restricted field of view and some cannot see the black line on the bottom of the pool. They can see the end of lane from one metre away.,Le SM12 est destiné aux nageurs malvoyants.<br/><br/>Ils ont un champ de vision restreint et certains ne peuvent pas voir la ligne noire au fond de la piscine. Ils peuvent voir le bout de la ligne de nage à un mètre de distance.,SM12は、視覚障害のある水泳選手のクラスです。<br><br/>これらの選手は、視野が限られており、プール底面の黒い線が見えない人がいます。選手たちがレーンの端を見ることができるのは、1メートル離れたところからとなります。,9,22,29,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,Y,,,,,,,,,/sports/swimming/individual-medley/sm12,/fr/sports/natation/quatre-nages/sm12,/ja/sports/swimming/individual-medley/sm12,Summer,N,,2,,,/,/,/,SM12,,,,,,,,,,,Plávanie,,Individuálna medza,VIZUáLNE,SM12,SM12 je pre plavcov s po?kodením zraku.<br/><br/>majú obmedzené zorné pole a niektorí nevidia ?iernu ?iaru na spodnej strane bazéna. M??u vidie? koniec jazdného pruhu z jedného metra smerom od neho.,/sk/sports/plavanie/individualna-medza/sm12,,/sports/swimming/individual-medley/sm12,/sports/swimming/individual-medley/sm12,Y,/fr/sports/natation/quatre-nages/sm12,/fr/sports/natation/quatre-nages/sm12,Y,,,,,,,,,,,,,,,,,,,,,,,,,,
Swimming,,Natation,,水泳,,Individual Medley,Quatre nages,個人メドレー,VISUAL,VISUEL,視覚障害,,SM13,SM13,SM13,SM13?is for swimmers with a visual impairment.<br/><br/> Their peripheral vision is restricted and/or they are able to see the end of the pool at a maximum of five metres.,SM13 est destiné aux nageurs ayant une déficience visuelle.<br/><br/>Leur vision périphérique est restreinte et / ou ils peuvent voir le bout de la piscine à un maximum de cinq mètres.,SM13は、視覚障害のある水泳選手のクラスです。<br><br/>選手たちの周辺視野が限られています、および/または、選手たちがプールの端を見ることができるのは、最大5メートル離れたところからとなります。,13,22,36,,https://vimeo.com/315833397/d2844b8397  |  https://vimeo.com/315828761/5cf5813803  | https://vimeo.com/315678125/5afe850189  |  https://vimeo.com/315819538/a600fed566,,,,,,,,,,,,,,,,,,,,,,,,,,,,Y,,,,,,,,,/sports/swimming/individual-medley/sm13,/fr/sports/natation/quatre-nages/sm13,/fr/sports/swimming/individual-medley/sm13,Summer,Y,,2,,,200 Individual Medley,200 Individual Medley,/,SM13,,,,,,,,,,,Plávanie,,Individuálna medza,VIZUáLNE,SM13,SM13 je pre plavcov s po?kodením zraku.<br/><br/> ich periférne videnie je obmedzené a/alebo m??u vidie? koniec bazéna maximálne p?? metrov.,/sk/sports/plavanie/individualna-medza/sm13,,/sports/swimming/individual-medley/sm13,/sports/swimming/individual-medley/sm13,Y,/fr/sports/natation/quatre-nages/sm13,/fr/sports/natation/quatre-nages/sm13,Y,,,,,,,,,,,,,,,,,,,,,,,,,,
Swimming,,Natation,,水泳,,Individual Medley,Quatre nages,個人メドレー,VISUAL,VISUEL,視覚障害,,SM13 (SM12-13),SM13 (SM12-13),SM13 (SM12-13),S13?is for swimmers with a visual impairment.<br/><br/> Their peripheral vision is restricted and/or they are able to see the end of the pool at a maximum of five metres.,S13 est destiné aux nageurs ayant une déficience visuelle.<br/><br/>Leur vision périphérique est restreinte et / ou ils peuvent voir le bout de la piscine à un maximum de cinq mètres.,S13は、視覚障害のある水泳選手のクラスです。<br><br/>選手たちの周辺視野が限られています、および/または、選手たちがプールの端を見ることができるのは、最大5メートル離れたところからとなります。,17,22,36,,https://vimeo.com/315833397/d2844b8397  |  https://vimeo.com/315828761/5cf5813803  | https://vimeo.com/315678125/5afe850189  |  https://vimeo.com/315819538/a600fed566,29,,,,,,,,,,,,,,,,,,,,,,,,,,,N,,,,,,,,,/sports/swimming/individual-medley/sm13-sm12-13,/fr/sports/natation/quatre-nages/sm13-sm12-13,/ja/sports/swimming/individual-medley/sm13-sm12-13,Summer,Y,,2,,,200 Individual Medley,200 Individual Medley,/,SM13,,,,,,,,,,,Plávanie,,Individuálna medza,VIZUáLNE,SM13 (SM12-13),S13 je pre plavcov s po?kodením zraku.<br/><br/> ich periférne videnie je obmedzené a/alebo m??u vidie? koniec bazéna maximálne na p?? metrov.,/sk/sports/plavanie/individualna-medza/sm13-sm12-13,,/sports/swimming/individual-medley/sm13-sm12-13,/sports/swimming/individual-medley/sm13-sm12-13,Y,/fr/sports/natation/quatre-nages/sm13-sm12-13,/fr/sports/natation/quatre-nages/sm13-sm12-13,Y,,,,,,,,,,,,,,,,,,,,,,,,,,

Hi Charles, kind offer, thanks but I can handle it for now – only two rows and I don’t intend to do this often – but possibly something that the plugin should handle (or at least review in case there is a wider issue)

Thanks

sadly it’s Excel and you get what you are given. In Microsoft’s defence, it doesn’t actually need to be quoted in the CSV as it contains no commas – and the 2 rows affected look materially no different to the 300+ that work which also are not quoted.

WPDA picks up the unquoted columns and quotes them for the Insert in 99% of the rows but these two don’t get quoted…It’s a true oddity!

update – if I catch the SQL for the 2 rows that fail in Query Monitor plugin, paste into notepad and quote the 2 string, stick a ; and carriage return on the end I can upload the .SQL into “import data/ execute scripts” part of data explorer and the two rows go in OK, so that proves that fundamentally the system is OK, just missing the quotes around one string is very odd.

Thanks, it does but in my case I tend to take the whole lot (wordpress DB and custom tables) as I have a plugin that interacts with the pages and the custom tables, so in order to keep my test and development copy consistent with production I restore the whole lot.

Most of what I am testing is the replacement of data in these custom tables with a new CSV (that starts, of course from excel – not my choice…) so checking the new imported data’s behaviour on copy of a production system is really useful, so using the same CSV import on the copy before I import it on production is key to what I am doing.

Hi Peter, I guess I won’t be sure without seeing it but it sounds promising.

I don’t use remote databases at all, everything that I do is local and in the local DB containing the wordpress data

The use case would be to be able to configure a database and a CSV import, take a backup and restore it to another wordpress installation and be able to use the CSV importer (and ideally data designer, but I can reverse engineer the table to get it back if needed)

I currently do this by editing WP_WPDA_CSV_UPLOADS table and changing the schema_name attribute. If this were possible to use [default database] or something instead of the “old_schema_name” then this would probably work ??

{“settings”:{“delimiter”:”,”,”date_format”:”%Y-%m-%d”,”has_header_columns”:”true”},”database”:{“schema_name”:”old_schema_name”,”table_name”:”blah”}

I look forward to trying it and will feed back when it is released

Thanks

Steve