🇩🇪Germany @mithun-a-sridharan

mithun-a-sridharan → created an issue.

mithun-a-sridharan → created an issue.

Dear all,

I can also confirm that this patch works. I've added my comments and screenshots to the other related issue I posted here 🐛 Major bug: Duplicate entries or incorrect duration on calendar Active . The patch seems to fix the issues I was facing. Shout out to @vinayakmk47 → for the patch and all the contributions from this community.

Thanks a ton!

Mithun A. Sridharan

Update:

The patch → provided for this issue ✨ Support for multiple standard (non smartdate) date fields Active also fixed the bugs I reported. Huge shout out to @vinayakmk47 → for the patch.

My approach:

1. Apply the patch via composer
2. Create a start and end date in the view
3. Assign the dates in the event content type
4. Clear the cache

I've attached the screenshots to this note:

- Two-Dates-View.jpg: Add start and end dates to the view
- Single-Day-Event.jpg: Start and end times on the same date for an event
- Multiple-Days-Event.jpg: Different start and end dates for an event
- Working-Outcome.jpg: Final, working calendar

Thanks a ton to all those that made this patch possible.

Mithun A. Sridharan

Looking at the patch → provided as a fix for the issue reported here ✨ Support for multiple standard (non smartdate) date fields Active , the unique events are identified based on the event ID, start and end dates.

I suspect that the issue with extended duration I observed and reported in this bug report could touch upon another bug in the end date as referred by the $event['end'] variable.

Logically, the $event['end'] should be populated from the entry in the Event content type and something's broken in between. Is there a mapping step I missed or some documentation that I overlooked?

Thanks in advance
Mithun A. Sridharan

mithun-a-sridharan → created an issue.

I can confirm the duplicate entries on the frontend when assigning start and end dates to an event. Following the comment #7 by @erutan, I removed the end date and the duplicates don't show up on the front end. I've attached screenshots that demonstrate this behavior. Please merge the fix and issue a new release.

@dieterholvoet,

It's been a while since I approached you with the issues.

The suggested fixes resolve the issues I was facing.

Thank you very much for your support.

Much appreciated!

Mithun A. Sridharan

Dear all,

Glad to see momentum on this issue.

I tried this approach and don't see errors, which is a good step closer to the solution.
However, the posts, categories and tags are not imported from the WXR file.

My approach was as follows:

# Export the entire configuration
vendor/drush/drush/drush cex

# In the config/sync folder:
# Copy the patch file to the sync folder
mkdir migrations
git apply --index 3484883-MR13.patch

# Move the yaml files back to sync folder

# Import changed configuration 
vendor/drush/drush/drush cim

Is this the right approach to apply this patch?

I wonder why such a convoluted approach - exporting, applying the patch and re-importing the configuration is a better approach than fixing the issue at source using the file_create_url approach.

Furthermore, the user experience in this approach isn't optimal, considering that these migrations mostly happen once when importing content from a different CMS.

PS: I also manually changed the data_fetcher plugin from http to file in the yaml configuration files, yet the posts are not imported.

Dear all,

I tried the approach suggested by @vaidas_a

Though the http error is fixed with this approach, the content isn't importing.

Would this plugin create the destination fields or should they be created prior to import?

@hongpong: This issue occurs with Drupal 10.3.6 and Drupal 10.3.7.

The file_create_url approach would also be my preferred option, I reckon.

Any insights re. support for Drupal 11?

mithun-a-sridharan → created an issue.

Hi Dieter,

Thanks for your responsiveness. Much appreciated!

Is there a mechanism to get all co-authors in the Twig file? The idea here is to create an authors' biography that goes after the content in the blog content type. The biography will include the co-authors' picture and a biography.

Following your inputs, I tried the following:

node.co_authors.referencedEntities and node.co_authors.referencedEntities|first.displayName

This resulted in the following error:

Twig\Sandbox\SecurityError: Calling "referencedEntities" method on a "Drupal\Core\Field\EntityReferenceFieldItemList" object is not allowed. in Drupal\Core\Template\TwigSandboxPolicy->checkMethodAllowed() (line 174 of themes/custom/rhythm/templates/node/node--nd-blog.html.twig).

This worked:

node.co_authors.entity.displayName

I'm new to Drupal, coming from the WordPress ecosystem.

Is there an alternative approach you'd recommend?

Thanks again!

Mithun A. Sridharan

Mithun-A-Sridharan → created an issue.

Mithun-A-Sridharan → created an issue.