evoweb/sessionplaner

sessionplaner's Issues

Version 4 doesn't work without a room image - stale master branch?

After updating to TYPO3 11 and installing the latest stable release v4 from march 2021 the sessionplaner doesn't work anymore and there is an exception.

This was was fixed later in this commit 8eab2f7 but this change was never officially released.
The master-branch is still from 2021 whereas the develop-branch has more/newer commits.

My question: Is there a plan to release a new official version of the extension with the mentioned fix or other fixes?

SuggestFormFactory is broken in v11.3

After upgrading to TYPO3 11.3, the suggest form is broken again.
Exception:

(Ignore our customized class, please. We need a different field setup, but this is a clone of Evoweb\Sessionplaner\Domain\Factory\SuggestFormFactory with the same factory workflow.)

Reason: ObjectManager has been removed with TYPO3 v11.3:
TYPO3/typo3@1a3fdde6a5 and
https://get.typo3.org/release-notes/11.3.0:

Removing object manager works for our customized finisher, PR is on the way...

Release v8.7 compatible version before dropping support for older versions than v9.5

Release needs to be done before we are merging:
#1

Make Dependabot happy

Dependabot sends a report every week with postcss and @babel/traverse warnings. Could you please update them? I get all the warnings and its a bit annoying.

SuggestFormFactory is broken in v11

The current initialization of the MailFinisher results in an exception when submitting the form and sending the mail.

In TYPO3 v10 the "single definition" of mail recipients was declared as deprecated, in v11 it was removed now:
https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/10.0/Deprecation-80420-EmailFinisherSingleAddressOptions.html

Therefore the initialization should be changed.
Old (v10):
form->createFinisher('EmailToReceiver', [ 'subject' => $settings['suggest']['notification']['subject'] ?? '', 'recipientAddress' => $settings['suggest']['notification']['recipientAddress'] ?? '', 'recipientName' => $settings['suggest']['notification']['recipientName'] ?? '', 'senderAddress' => $settings['suggest']['notification']['senderAddress'] ?? '', 'senderName' => $settings['suggest']['notification']['senderName'] ?? '', 'carbonCopyAddress' => $settings['suggest']['notification']['carbonCopyAddress'] ?? '', 'blindCarbonCopyAddress' => $settings['suggest']['notification']['blindCarbonCopyAddress'] ?? '', 'format' => 'html' ]);

New (v11):
$form->createFinisher('EmailToReceiver', [ 'subject' => $settings['suggest']['notification']['subject'] ?? '', 'recipients' => $settings['suggest']['notification']['recipientAddress'] ? [ $settings['suggest']['notification']['recipientAddress'] => $settings['suggest']['notification']['recipientName'], ] : [], 'senderAddress' => $settings['suggest']['notification']['senderAddress'] ?? '', 'senderName' => $settings['suggest']['notification']['senderName'] ?? '', 'carbonCopyAddress' => $settings['suggest']['notification']['carbonCopyAddress'] ?? '', 'blindCarbonCopyAddress' => $settings['suggest']['notification']['blindCarbonCopyAddress'] ?? '', 'format' => 'html' ]);
(Sorry - line breaks an indents in the editor are removed in preview and final issue. See screenshots below)

In the above code I kept the sionge definition in typoscript. Perhaps this can (should?) changed also to allow multiple recipients.

For our use case, we are already using a custom form factory, as we need a different setup of form fields anyway.

PHP: 7.4
TYPO3: 11.2.0
EXT:sessionplaner: 4.0.0

Screenshot v10:

Screenshot v11:

Feature Request: New functionality to save favorites in browser

A session plan with multiple parallel sessions gives attendees the choices which ones they want to attend. Thus, it is common to plan your individual programm in advance. A new feature could add a functionality to save some favorites sessions in the browser. I would imagine to add something like a star on the top left corner of each session. Clicking on this star will add the session e.g. to the local storage in the browser, and the next click will delete it again. Similar to that example:

Source: https://bid2022.abstractserver.com/program/#/details/sessions/128

Version 10.3.0 Bugs

It seems like there are some bugs in the extension when being used in TYPO3 version 10.3.0:

1. When selecting the folder where data is being stored, the Web View does not show the drag-and-drop timetable, but instead the following error:

The selected storage folder does not contain any rooms.
Please create days, rooms and slots previous planing sessions.
For further information consult the documentation.

2. When creating or editing sessions, it somehow adds the first speaker from "Available Items" to "Selected Items" every time I save the session.

3. The same applies to Tags. Every time I save the session, a new tag is being added.

4. In the frontend, the plugin "Sessionplaner: Sessionplan" messes up the locations and does not show all sessions for a day. Instead it seems that the location gets randomly selected and only one session is allowed for one day.

5. Unfortunately, the "Sessionplaner: Sessionplan" plugin only allows one day to be displayed in the frontend. I don't know whether this behavior is intended. But I would assume that all sessions can be displayed.

Can you help me out here?

Feature Request: Export as iCalendar file (ics)

It would be interesting to have a public possibility to export the complete session plan as a iCalendar file (ics). Nowadays, it is only possible to export all sessions to CSV or JSON in the backend. However, I would envision also an option to download the data in the frontend as ICS-file. This would enlarge the interoperability of the data and use it easily in other tools.

Ajax in backend module not working in TYPO3 11.3.2

When moving session in the backend module, their new slot position cannot be stored.
The AjaxController returns an error 500:

There is no visible error and the editor is able to to other chenges/moves, but when reloading the backend module all sessions jump back to the previous position.
The request parameters seem to be right:

A quick workaround to get this running again is to remove the "lazy" annotation from the day property of the slot domain model.
But this is not very productive and should be approved.

PHP: 7.4.20 (ddev) & 7.4.22 (production)
TYPO3: 11.3.2
EXT:sessionplaner: 4.0.0

Note:
Our website was newly build with TYPO3 11.2.0.
As far as I remember the backend module worked in 11.2.0, but I#m not 100% sure.
I already checked the complete changelog of 11.3.0, but there was no entry for me

documentation is missing

Hi,

I clicked on the link for the full documentation but the webpage is empty:

So, I'm not sure if something went wrong or if the documentation has to be created first?

Thank you and best regards.

Documentation missing

Hi,

I noticed that the documentation is completely missing. On typo3.org the documention link points to https://docs.typo3.org/p/evoweb/sessionplaner/4.0/en-us/ which just has an Introduction and Installation page. There is no information about how to set up the structure or configure the sessionplaner.

Nevertheless, I tried it and was able to create a schedule but (at least) two things didn't work.

1. The slugs/routes for the detail pages give me 404-error pages, without the route enhancer the detail pages work.
2. I can't go back from detail page to the schedule, the back link doesn't work and gives me a page with no schedule.

Maybe I missed something...

Also checked: https://github.com/evoWeb/sessionplaner/tree/develop/Documentation but there is nothing there as well.

Everything tested in TYPO3 10.4.36 with sessionplaner 3.0