Plugin Support
Darian
(@d0153)
Hi @peter8nss
Thanks for reaching out. Let me help you with this one.
I tried replicating the issue on my test site using the CSV template for venues provided on this article, but it’s working as expected.
Could you try using the CSV template provided from the article, and see if that resolves the issue? If it doesn’t, please provide us the CSV file that you’re importing. I want to check it further on my end.
Occurs with your example file too. Simple version of my file:
"VENUE NAME","VENUE DESCRIPTION"
Venue3,"Test loading venues"
As far as I can tell, the status is being read from tribe sub-option: tribe_aggregator_default_csv_post_status rather than the value specified at import time. That value being set as part of the “CSV Import Settings”. What ever you change that to, is the value the import is saved with!
Looking inside the code, I suspect that the submitted post_status value is never copied into $meta in function handle_submit so the default setting is used instead.
Hi @peter8nss ,
Thank you for your message and the information.
I tested your CSV import to my testing environment using only The Events Calendar and the twenty-twenty-one theme and I too have not been able to reproduce the issue of the Venue importing as draft (see https://go.screenpal.com/watch/cZ606Mncn3j).
Could you provide your settings for the following in Events -> Settings -> Imports (tab)?
- Event Update Authority
- Global Import Settings / Default Status
- CSV Import Settings / Default Status
My settings are:
- Event Update Authority: Overwrite my event with any changes from the original source
- Default Status: Draft
- Default Category: None
Have you tried importing with a different status from your default? If I’m right about the fault, then it will use your default regardless of what you select for a specific import.
For example, if I set the default to “Pending review” but for my import choose “Published”, all venues are imported with status “Pending”.
Plugin Support
Darian
(@d0153)
Hi @peter8nss
I’m glad you brought this to our attention, I can see how this issue impacts your ability in importing your venues.
I’ve created an internal ticket [TECTRIA-492] to address this issue and I’ve included your specific use case in it to communicate it to our team.
We prioritize bugs by taking into consideration the number of users impacted as well as how the bug impacts one’s ability to run an event/sell tickets. I don’t have a specific timeline as to when this issue will be resolved, but trust that our team is aware. Our team communicates updates and bug fixes in our newsletter and via our changelog.
In the meantime, set the default value from the Events > Settings > Import page and set your preferred default status for importing venues.
I’m happy to help if any other questions are coming up around this topic, otherwise I’ll go ahead and close this ticket.
Thanks again for reporting this issue and for using The Events Calendar! Have a great day.
—
Internal Bug Ticket Reference: TECTRIA-492
