John James Jacoby

Hello @mlindstedt!

Sorry that you’ve found yourself a bit stuck. I think I understand what it is that you are hoping to do.

There isn’t really a built-in way to do it, unfortunately.

You would need to write some custom PHP, to use a custom Gravity Forms field of your own design, to populate the range of allowed dates for the form. This is particularly tricky for recurring Events, where the specific sequence matters, and Sugar Calendar does not yet provide unique occurrence/sequence IDs.

Sorry, but it’s really only a complicated way to achieve it. We will eventually include this functionality into this plugin and Sugar Calendar, but it does not exist today.

If you decide to try and develop this yourself, we are happy to provide some asynchronous hints and tips via this support topic.

Hi there @jealbr75, sorry to hear you are having trouble.

The description for this plugin indicates that it requires both Sugar Calendar and WP All Import. It is, essentially, an extension of both of them, or a bridge between them. I’m happy to update the plugin description to make this more clear.

The plugin includes an example CSV file. In it are properly formatted columns and rows, that show how you can format your own values for importing.

WP All Import includes a sophisticated UI to choose how to uniquely identify Events. It will auto-detect {title[1]} but you are encouraged to select a more suitable combination or identifier that suits your specific needs.

I’ve tested with duplicate Titles and similar Start and End Dates and Times. In my testing, this is all working as expected and without any unintended results or bugs. New Events are inserted when unique IDs are not matched, and existing Events are updated when unique IDs are matched.

WP All Import has a bit of a learning curve. My best advice is to take a bit more time to learn what it is asking you for, and take care to follow its advice and instructions.

I know that you’ve given this plugin a 1 star rating (and you are entitled to your opinion) but I hope that you’ll try it again and reconsider your rating once you’ve gotten it working to your liking.

Hi @s-interact ??

I’ve removed the link per your request ??

Hey @mrwweb, thanks for the feedback. It’s all very helpful.

• Gutenberg Calendars: we have an open issue for this. It may require an upstream patch to WordPress. We’re working on it.
• Calendars in Readme: Thank you for bringing this to our attention. I’ve already changed the description in the readme to be about “Calendars” instead of “Categories”.
• Calendars taxonomy: noted, but we are unlikely to change this bit of UX. This feature using a taxonomy under the hood is similar to WordPress Menus. It is intended to be familiar, but not intended be identical to traditional Categories or Tags screens, and that is by design.
• Repeats Column: I see what you mean. I’ll make sure this column is hidden for Lite in the next release.
• Events Archive: we do have plans for this, and you’re right that WordPress does not make this easy. It will likely be an add-on to completely customize all of the archive views.
• Changelog: We do this to avoid perpetual translations churn, to reduce the size of the readme.txt file, and to keep shipping releases simple (so it does not need to be manually edited with each release). Sorry that this is as frustrating as it is for you, but there are no plans to change at this time.

We’ve deeply tested the Block Editor integration. Unfortunately, the Block Editor has incomplete coverage when it comes to WordPress APIs, and its requirements continue to change with every WordPress release. We’re committed to supporting it, but it isn’t exactly committed to supporting us. ??

Thank you again for the encouraging words. We’re working on improving Sugar Calendar each and every day. Your experience using it is important, and your feedback really matters to us. Thank you also for taking the time to write everything out so clearly. It will help make Sugar Calendar better!

This issue is now resolved in the most recent versions of Sugar Calendar.

I believe we’ve fixed this issue in the latest releases.

Thank you for your help.

These are now properly translated in versions 2.1.0 and above.

Sorry for the inconvenience!

Someone would need to write a bridge plugin between Polylang and this one.

Perhaps that’s something I can explore at a future time.

These checks are not done by this plugin. WordPress does these checks on its own. There isn’t anything I can do about that from the plugin side.

Hopefully you were able to get this figured out!

That’s pretty strange. What other plugins do you have installed?

I do not, but I can make it happen for you. I’ve been meaning to do something like this for a while now.

Hi @iamnaran. Anything can be customized with CSS!

You could try something like this:

#sc_events_calendar_head {
	position: relative;
}

#sc_event_select, #sc_event_nav_wrap {
	position: absolute;
	top: 0;
}

#sc_event_nav_wrap {
	right: 10px;
}

#sc_events_calendar_head h2 {
	display: none;
}

#sc_events_calendar_head {
	height: 40px;
}

You’ll want to tweak that CSS for your exact needs.

The truncation that is happening is stylistic only, and not related to anything with the migration. If you visit the Event, you’ll see the entire title is still there.

If you’d like to disable the truncation styling, you can do so with some CSS:

#sc_calendar td div.sc_day_div a {
    text-overflow: initial;
    overflow: initial;
    whitespace: normal;
}

Edit: Shayne’s approach will work, too! ??

Thank you!

You’re welcome!